Matching actionable events with goods and services providers

• US 10,171,936 B2
• Filed: 09/23/2016
• Issued: 01/01/2019
• Est. Priority Date: 09/23/2016
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Allen, Joshua S., Lavery, Andrew J., Maldari, Mario A.
• Primary Examiner(s): Brandt, Christopher M
• Application Number:
  US15/273,946
• Publication Number:
  US 20180091938A1
• Time in Patent Office: 830 Days
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04M 1/00 Substation equipment, e.g. for use by subscribers subscriber services or facilities provided at exchanges H04M3/00; prepayment telephone coin boxes H04M17/00; current supply arrangements H04M19/08
• CPC Class Codes: H04M 1/72448 with means for adapting the functionality of the device according to specific conditions
• CPC Class Codes: H04M 1/72457 according to geographic location
• CPC Class Codes: H04M 2250/22 including a touch pad, a touch sensor or a touch detector digitizers for touch screens G06F3/041
• CPC Class Codes: H04W 4/021 Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 64/00 Locating users or terminals or network equipment for network management purposes, e.g. mobility management
• CPC Class Codes: H04W 88/02 Terminal devices

Abstract

A device comprises an input component configured to receive an event identification request from a provider. The event identification request comprises one or more requirements usable to identify an actionable event for resolution. The requirements specify a geographical boundary and one or more goods. The device also comprises a processor communicably coupled to the input component. The processor is adapted to transmit the event identification request to a repository configured to match the event identification request with one or more actionable events based on the one or more requirements.

Claims

1. A first device, comprising:

a touchscreen display configured to receive an event identification request from a first user via a graphical user interface (GUI), wherein the event identification request comprises one or more requirements usable to identify one or more actionable events stored in a repository device, wherein the one or more requirements specify a geographical boundary and one or more goods or services, and wherein the one or more actionable events correspond to one or more dysfunctional devices reported by one or more second users of one or more second devices; and

a processor communicably coupled to the touchscreen display and configured to;

cause the touchscreen display to display the GUI to receive the event identification request from the first user by causing the touchscreen display to display a menu button that, when a tap by the first user is detected, causes the touchscreen display to display a drop-down menu that includes a first option that, when a selection by the first user is detected, causes the touchscreen display to display a second drop-down menu that presents different selectable request aspects to enable entry of the one or more requirements of the event identification request;

transmit the event identification request to the repository device to determine whether the repository device stores at least one actionable event of the one or more actionable events that matches the one or more requirements of the event identification request;

receive a notification indicating that the at least one actionable event matches the one or more requirements of the event identification request; and

cause the touchscreen display to provide the first user with an option to accept the at least one actionable event.

2. The first device of claim 1, wherein the processor is configured to transmit a privacy credential to the repository device, and wherein the processor is configured to receive information regarding only those actionable events associated with the privacy credential.

3. The first device of claim 1, wherein the first device is a smart phone.

4. The first device of claim 1, wherein the processor is configured to repeatedly receive information regarding matching the one or more actionable events over a period of time that is defined via the touchscreen display.

5. The first device of claim 1, wherein the processor is configured to facilitate communication between the first user and the one or more second users.

6. The first device of claim 1, wherein the one or more requirements includes a range of dates on which the one or more actionable events were reported.

7. A method, comprising:

displaying, by a touchscreen display, a graphical user interface (GUI) configured to receive event identification requests from a first user;

receiving, by the touchscreen display, an event identification request from the first user, wherein the event identification request comprises requirements usable to identify one or more actionable events stored in a repository device, wherein the requirements specify a geographical boundary and a type of repair or replacement service, wherein the one or more actionable events correspond to one or more dysfunctional devices that are reported by one or more second users of one or more second devices, and wherein receiving the event identification request includes;

displaying, by the GUI, a menu button;

receiving, by the GUI, a tapping selection from the first user;

displaying, by the GUI responsive to receiving the tapping selection, a drop-down menu that includes a first option;

receiving, by the GUI, a second tapping selection from the first user;

displaying, by the GUI and responsive to receiving the second tapping selection, a second drop-down menu that presents different selectable request aspects to enable entry of the requirements of the event identification request;

transmitting the event identification request to the repository device to determine whether the repository device stores at least one actionable event of the one or more actionable events that matches the requirements of the event identification request;

receiving a notification indicating that the at least one actionable event matches the requirements of the event identification request;

providing information regarding the at least one actionable event to the first user via the touchscreen display; and

providing, by the touchscreen display, the first user with an option to accept the at least one actionable event.

8. The method of claim 7, further comprising receiving contact data associated with the at least one actionable event when the at least one actionable event is accepted.

9. The method of claim 8, further comprising using the contact data to receive and provide communications regarding the at least one actionable event.

10. The method of claim 7, further comprising providing a signal to the repository device to change a classification of the at least one actionable event when the at least one actionable event is accepted.

11. The method of claim 7, further comprising providing the information regarding the match to the first user via the touchscreen display only if a privacy credential matches one or more privacy designations associated with the at least one actionable event.

12. A computer program product comprising a computer-readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause the processor to:

cause a touchscreen display to display a graphical user interface (GUI);

receive an event identification request from a first user via the GUI by;

causing the GUI to display a menu button;

receiving, by the GUI, a tapping selection from the first user;

displaying, by the GUI responsive to receiving the tapping selection, a drop-down menu;

receiving, by the GUI, a second tapping selection from the first user; and

displaying, by the GUI and responsive to receiving the second tapping selection, a second drop-down menu that presents different selectable request aspects to enable entry of requirements usable to identify one or more actionable events stored in a repository device, wherein the event identification request comprises the requirements, wherein the one or more actionable events correspond to one or more dysfunctional devices that are reported by one or more second users of one or more second devices, and wherein the event identification request specifies a geographical boundary and at least one of a type of good and a type of service;

provide the event identification request to the repository device to determine whether the repository device stores at least one actionable event of the one or more actionable events that matches the requirements of the event identification request;

receive a notification indicating that the at least one actionable event matches the requirements of the event identification request;

provide, by the touchscreen display, the first user with an option to accept the at least one actionable event; and

provide an acceptance signal to the repository device when the first user accepts the at least one actionable event.

13. The computer program product of claim 12, wherein the program instructions executable by the processor further cause the processor to guide the first user to a geographical location of the at least one actionable event.

14. The computer program product of claim 12, wherein the program instructions executable by the processor further cause the processor to interface with a third-party financial services vendor to obtain payment.

15. The computer program product of claim 12, wherein the processor receives the event identification request via a smart phone application.