Monitoring of location-associated events

• US 20010029184A1
• Filed: 04/10/2001
• Published: 10/11/2001
• Est. Priority Date: 04/11/2000
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Company (HP Inc.)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Wilcock, Lawrence, McDonnell, James Thomas Edward, Hawkes, Rycharde Jeffery, Crouch, Simon E., IʼAnson, Colin
• Application Number:
  US09/828,977
• Publication Number:
  US 20010029184A1
• Time in Patent Office: Days
• US Class Current: 455/456.2
• CPC Class Codes: G08B 2001/085 Partner search devices
• CPC Class Codes: H04W 4/02 Services making use of location information
• 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 4/12 Messaging; Mailboxes; Announcements

Abstract

A method is provided for monitoring location-associated events such as the availability for collection at business premises of items previously ordered by a customer. The method involves storing a descriptor of the event of interest to the customer, the descriptor being stored, for example, in a third-party service system (40) by the business concerned. The descriptor explicitly or implicitly includes details of the parties and the location of the premises (70). Subsequently, when the customer comes near the business premises (70), the service system (40) determines a match with the event descriptor and thereupon carries out an event status check using status data provided by the business. The result of the status check is reported to the customer (115).

Claims

1. A method of monitoring location-associated events, comprising the steps of:

(a) storing an event descriptor concerning an event of interest to a first party that is expected to occur at the premises of a second party, the event descriptor explicitly or implicitly identifying the parties and the location of the premises;

(b) determining when an event descriptor is matched by the identity and location of the first party and in response to such a match, checking the status of the corresponding expected event with status data provided by the second party.

2. A method according to

claim 1

, wherein the event descriptor is stored by the second party in a third-party service system, the location of the first party being provided to the third-party service system for effecting the step (b) determination either by the first party or by a location server.

3. A method according to

claim 1

, wherein the event descriptor is stored by the first party in a third-party service system, the location of the first party being provided to the third-party service system for effecting the step (b) determination either by the first party or by a location server.

4. A method according to

claim 1

, wherein the event descriptor is stored by the first party in a mobile entity of the first party, the mobile entity including location discovery means for providing the location of the first party to the determination carried out in step (b).

5. A method according to

claim 1

, wherein the event descriptor is stored by the first party in a mobile entity of the first party, the mobile entity including short-range wireless communication means for receiving signals from corresponding means at the premises of the second party, the receipt of such signals being used in the determination carried out in step (b) to indicate a match for the event descriptor.

6. A method according to

claim 1

, wherein the status data is held in a status database maintained by the second party, the status check carried out in step (b) being effected by accessing the status database.

7. A method according to

claim 2

, wherein the status data is provided by the second party to the third-party service system where it is stored, the status check carried out in step (b) being effected by accessing the status data held by the third-party service system.

8. A method according to

claim 1

, wherein the result of the status check carried out in step (b) is reported to the first party.

9. A method according to

claim 1

, wherein the event concerns the availability of an item for collection at the premises.

10. A method according to

claim 9

, wherein step (b) further involves reporting the result of the status check to the first party at least when this check indicates that the item is available for collection.

11. A method according to

claim 10

, wherein the event descriptor includes date data specifying an expected date when the item will be available for collection, step (b) further involving checking whether the item is overdue and not available for collection, and reporting such circumstances to the first party.

12. A method according to

claim 10

, wherein the first party on receiving a report that said item is available for collection, informs the second party of a planned collection time.

13. A method according to

claim 2

, wherein the location of the first party is only provided to the third-party service system upon specific action by the first party indicating that any match is to be identified.

14. A method according to

claim 2

, wherein the second party is given no indication of the location of the first party by the third-party service system except to the extent that a said match is directly or indirectly indicated to the second party.

15. A method according to

claim 3

, wherein the second party is given no indication of the location of the first party by the third-party service system except to the extent that a said match is directly or indirectly indicated to the second party.

16. A computer program product for use in monitoring location-associated events, the product comprising:

a first component which when run by general-purpose processing means provides;

a database interface for storing and retrieving event descriptors each concerning an event of interest to a first party that is expected to occur at the premises of a second party, the event descriptor explicitly or implicitly identifying the parties and the location of the premises, and

a match subsystem for determining when an event descriptor is matched by the identity and location of the first party; and

a second component which when run by general-purpose processing means provides;

database interface for storing and retrieving event status data provided by the second party,

a status-check subsystem that in response to the match subsystem determining a match, is operative to check the status of the corresponding expected event as indicated by the event status data.

17. A computer program product according to

claim 16

, further comprising a third component which when run by general-purpose processing means provides an output subsystem for reporting the result of the status check to the first party.

18. A computer program product according to

claim 16

, wherein the events concern the availability of items for collection at the premises, the computer program product further comprising a third component which when run by general-purpose processing means provides an output subsystem for reporting the result of the status check to the first party at least when this check indicates that the item is available for collection.

19. A computer program product according to

claim 16

, wherein the events concern the availability of items for collection at the premises, the computer program product further comprising a third component which when run by general-purpose processing means provides an output subsystem for reporting to the first party as a result of the status check when an item will be available for collection.

20. An arrangement for using the computer program product of

claim 16

, the arrangement comprising:

a service system having general purpose processing means on which said first component is installed, and a database subsystem for holding the event descriptors;

a data-processing system associated with the second party and having general purpose processing means on which said second component is installed, and a database subsystem for holding the event status data.

21. A system for using the computer program product of

claim 16

, the system comprising:

general purpose processing means on which said first and second components are installed, and

a database subsystem for holding the event descriptors and event status data.