Source: http://www.google.nl/patents/US20020028671
Timestamp: 2017-12-14 18:49:38
Document Index: 583588743

Matched Legal Cases: ['art 2002', 'art 2001', 'art 2010', 'art 2007', 'art 2010', 'art 2015']

Patent US20020028671 - Service delivery method and system - Google Patenten
A user (70) is pre-qualified for a service to be provided at a particular location. A service instance element (76) is stored as is location data (74) indicative of where the service is to be triggered. The service instance element (76) may be a full customized instance of the service delivery code or...http://www.google.nl/patents/US20020028671?utm_source=gb-gplus-sharePatent US20020028671 - Service delivery method and system
Publicatienummer US20020028671 A1
Aanvraagnummer US 09/881,040
Publicatiedatum 7 maart 2002
Prioriteitsdatum 17 juni 2000
Ook gepubliceerd als DE60100658D1, DE60100658T2, DE60102068D1, DE60102068T2, DE60105090D1, DE60105090T2, EP1164804A1, EP1164804B1, EP1233632A1, EP1233632B1, EP1239685A1, EP1239685B1, US7715542
Publicatienummer 09881040, 881040, US 2002/0028671 A1, US 2002/028671 A1, US 20020028671 A1, US 20020028671A1, US 2002028671 A1, US 2002028671A1, US-A1-20020028671, US-A1-2002028671, US2002/0028671A1, US2002/028671A1, US20020028671 A1, US20020028671A1, US2002028671 A1, US2002028671A1
Uitvinders Colin I' Anson, Rycharde Hawkes, James McDonnell, Andrew Thomas, Lawrence Wilcock
Oorspronkelijke patenteigenaar Colin I' Anson, Hawkes Rycharde Jeffery, Mcdonnell James Thomas Edward, Andrew Thomas, Lawrence Wilcock
Patentcitaties (17), Verwijzingen naar dit patent (20), Classificaties (5), Juridische gebeurtenissen (6)
US 20020028671 A1
A user (70) is pre-qualified for a service to be provided at a particular location. A service instance element (76) is stored as is location data (74) indicative of where the service is to be triggered. The service instance element (76) may be a full customized instance of the service delivery code or other item that provides an association between the user and an instance of the service for which the user has been qualified. Thereafter, the location of the user (70), as indicated by a mobile entity associated with the user, is periodically checked against the location data (74) and when a location match is indicated, the service instance (76) for which the user has been qualified is executed to deliver the required service to the user (70). An example is of an airline traveller buying an air ticket from a travel agent, the ticket having an associated service by which, upon the traveller arriving at the relevant airport, the traveller is contacted via his/her mobile device and guided through the check-in and boarding processes.
2. A method according to claim 1, wherein the service instance element is associated with the user by a user identifier included in the element, and with the service instance by either comprising code for implementing the instance or including a reference to such code, the user's mobile entity directly or indirectly supplying this user identifier for service delivery to be effected.
3. A method according to claim 1, wherein the service instance element is associated with the user by a service-instance identifier known to the user or the user's mobile entity, the service instance element either comprising code for implementing the service instance or including a reference to such code, the user's mobile entity directly or indirectly supplying this service-instance identifier for service delivery to be effected.
4. A method according to claim 1, wherein the service instance element is stored in a service provider system with which the user's mobile entity can communicate through a communications infrastructure, and wherein the location data is stored in one of:
a location server of the communications infrastructure,
the mobile entity,
the service provider system,
where it is compared against the current location of the mobile entity as provided by one of:
a location server associated with the communications infrastructure,
location discovery means of the mobile entity;
in order to detect a said location match; the detection of a location match causing the service provider system to identify the service instance to be delivered by matching a said identifier provided directly or indirectly by the user's mobile entity with said service instance element.
5. A method according to claim 1, wherein the service instance element associates the user and service instance by virtue of the service instance element being stored in the user's mobile entity and either comprising code for implementing the service instance or including a reference to such code.
6. A method according to claim 5, wherein the service instance element is a token which upon the user's mobile entity determining or being informed of a said location match, is passed by the mobile entity over a communications infrastructure to a service provider system where it is used to initiate service provision to the user.
7. A method according to claim 6, wherein the token includes user identity data and is digitally-signed by the party that carried out the qualification step whereby the service provider system can check the authenticity of the data in the token, the user mobile entity having an associated public-key/private-key pair and being required by the service provider system to authenticate its identity by using its private key to sign and return data proposed by the service provider system.
8. A method according to claim 1, wherein the service instance element includes customisation data customising a generic service to said service instance.
9. A method according to claim 1, wherein service delivery is conditional upon the user inputting a personal identification code.
10. A method according to claim 1, wherein service delivery only continues whilst the user's current location matches with a location indicated by the location data.
11. A method according to claim 1, wherein once initiated, service delivery is continued until completion.
12. A method according to claim 1, wherein the service instance modifies the location data as part of service delivery.
13. A method according to claim 1, wherein the location data is indicative of multiple locations.
14. A method according to claim 1, wherein multiple service instance elements associated with different service instances to be delivered to the same user, are stored in a common repository.
15. A method according to claim 1, wherein the service instance element is passed by the party that carries out the qualification step to the user or to a third-party, the service instance element being digitally signed by the party that carries out the qualification step whereby to enable an eventual service deliverer to check the origin and authenticity of the service instance element.
16. A method according to claim 1, wherein the current user location is provided by a trusted location service provider and is digitally-signed by the latter.
17. A method according to claim 1, wherein said service instance element specifies a particular number of times (including only once) that the associated service instance can be run.
19. A system according to claim 18, wherein the location description repository is incorporated in said mobile entity associated with the user.
20. A system according to claim 18, wherein the service-instance-element repository is incorporated in said mobile entity associated with the user.
21. A system according to claim 20, wherein the service execution environment is incorporated in said mobile entity associated with the user, the service instance element taking the form of service instance code to be run in the execution environment.
22. A system according to claim 20, wherein the mobile entity and service execution environment can inter-communicate via a wireless infrastructure at least when the mobile entity is positioned to give rise to a location match, the service instance element taking the form of a service token which the mobile entity is operative to pass to the execution environment upon occurrence of a said location match in order to trigger execution of the service instance.
[0024]FIG. 5 depicts two general approaches to location determination from signals present in a cellular radio infrastructure. First, it can be noted that in general both the mobile entity and the network will know the identity of the cell in which the mobile entity currently resides, this information being provided as part of the normal operation of the system. (Although in a system such as GSM, the network may only store current location to a resolution of a collection of cells known as a “location area”, the actual current cell ID will generally be derivable from monitoring the signals exchanged between the BSC 14 and the mobile entity). Beyond current basic cell ID, it is possible to get a more accurate fix by measuring timing and/or directional parameters between the mobile entity and multiple BTSs 13, these measurement being done either in the network or the mobile entity (see, for example, International Application WO 99/04582 that describes various techniques for effecting location determination in the mobile and WO 99/55114 that describes location determination by the mobile network in response to requests made by location-aware applications to a mobile location center—server—of the mobile network).
As already indicated, FIGS. 2 to 5 depict only some examples of how location determination can be achieved, there being many other possible combinations of technology used and where in the system the location-determining measurements are made and location is calculated, stored and used. Thus, the location-aware service may reside in the mobile entity whose location is of interest, in a network-connected service system 40 (as illustrated), or even in another mobile entity. Furthermore, whilst in the examples of FIGS. 2 to 5, invocation of the location-aware service has been by the mobile entity whose location is of interest, the nature of the location-aware service may be such that it is invoked by another party (including, potentially, the PLMN itself). In this case, unless the invoking party already knows the location of the mobile entity and can pass this information to the location-aware service (which may, for example, maybe situation where the PLMN invokes the service), it is the location-aware service that is responsible for obtaining the required location data, either by sending a request to the mobile entity itself or by requesting the data from a location server. Unless the location server already has the needed information in cache, the server proceeds to obtain the data either by interrogating the mobile entity or by triggering infrastructure elements to locate the mobile. For example, where a location-aware service running on service system 40 in FIG. 5 needs to find the location of mobile 20G, it could be arranged to do so by requesting this information from location server 67 which in turn requests the location data from the relevant BSC, the latter then making the necessary determination using measurements from BTSs 13.
[0044]FIG. 1 is a diagram of a known communications infrastructure usable for transferring voice and data to/from a mobile entity;
[0045]FIG. 2 is a diagram illustrating one known approach to determining the location of a mobile entity, this approach involving providing the entity with an inertial positioning system;
[0046]FIG. 3 is a diagram illustrating another known approach to determining the location of a mobile entity, this approach being based on proximity of the mobile entity to fixed-position local beacons;
[0047]FIG. 4 is a diagram illustrating a further known approach to determining the location of a mobile entity, this approach involving the use of GPS satellites;
[0048]FIG. 5 is a diagram illustrating a still further approach to determining the location of a mobile entity, this approach being based on the use of signals present in a cellular mobile radio communications system;
[0049]FIG. 6 is a diagram illustrating the main logical components of a service delivery method and system embodying the invention;
[0050]FIG. 7 is a diagram illustrating a first specific embodiment of the invention;
[0051]FIG. 8 is a diagram illustrating a second specific embodiment;
[0052]FIG. 9 is a diagram illustrating a third specific embodiment; and
[0053]FIG. 10 is a diagram illustrating a fourth specific embodiment.
US5511121 * 8 sept 1994 23 april 1996 Bell Communications Research, Inc. Efficient electronic money
US5557518 * 28 april 1994 17 sept 1996 Citibank, N.A. Trusted agents for open electronic commerce
US5568153 * 30 mei 1995 22 okt 1996 Telefonaktiebolaget Lm Ericsson Individually defined personal home area for subscribers in a cellular telecommunications network
US5594789 * 13 okt 1994 14 jan 1997 Bell Atlantic Network Services, Inc. Transaction implementation in video dial tone network
US5677955 * 7 april 1995 14 okt 1997 Financial Services Technology Consortium Electronic funds transfer instruments
US6129274 * 9 juni 1998 10 okt 2000 Fujitsu Limited System and method for updating shopping transaction history using electronic personal digital shopping assistant
US6185541 * 12 mei 1999 6 feb 2001 Supermarkets Online, Inc. System and method for providing shopping aids and incentives to customers through a computer network
US6233448 * 22 juli 1998 15 mei 2001 Ericsson Inc. System, method and apparatus for automatic feature activation/deactivation based upon positioning
US6442391 * 11 mei 1998 27 aug 2002 Telefonaktiebolaget L M Ericsson (Publ) Location security for a subscriber unit in a telecommunication system by denying a parties' location request
US6601102 * 1 april 2002 29 juli 2003 Xerox Corporation Secure token-based document server
US6625580 * 16 sept 1998 23 sept 2003 Fujitsu Limited Wireless order and delivery system
US6718328 * 28 feb 2000 6 april 2004 Akamai Technologies, Inc. System and method for providing controlled and secured access to network resources
US20040128257 * 28 maart 2001 1 juli 2004 Okamoto Steve Atsushi Method and apparatus for administering one or more value bearing instruments
US8208945 * 21 juli 2006 26 juni 2012 Sony Corporation Information processing device and method, program, and recording medium
US9098850 * 24 sept 2012 4 aug 2015 Ping Identity Corporation System and method for transaction security responsive to a signed authentication
US9113332 * 26 maart 2010 18 aug 2015 France Telecom Method and device for managing authentication of a user
US9152411 12 mei 2010 6 okt 2015 Microsoft Technology Licensing, Llc Edge computing platform for delivery of rich internet applications
US9781105 4 mei 2015 3 okt 2017 Ping Identity Corporation Fallback identity authentication techniques
US20020061011 * 7 sept 2001 23 mei 2002 Sbc Technology Resources, Inc. Internal substitution bi-level addressing for compatible public networks
US20030097444 * 8 nov 2001 22 mei 2003 Santanu Dutta Method and apparatus for authorizing internet transactions using the public land mobile network (PLMN)
US20040019571 * 26 juli 2002 29 jan 2004 Intel Corporation Mobile communication device with electronic token repository and method
US20060209823 * 24 april 2006 21 sept 2006 Sbc Technology Resources, Inc. Internal substitution bi-level addressing for compatible public networks
US20070072622 * 21 juli 2006 29 maart 2007 Yoshihito Ishibashi Information processing device and method, program, and recording medium
US20100217635 * 25 feb 2009 26 aug 2010 At&T Intellectual Property I, L.P. Package shipping method
US20120096529 * 26 maart 2010 19 april 2012 France Telecom Method and Device for Managing Authentication of a User
US20130023240 * 24 sept 2012 24 jan 2013 Avish Jacob Weiner System and method for transaction security responsive to a signed authentication
US20150073992 * 10 okt 2014 12 maart 2015 Ping Identity Corporation System and method for secure transaction process via mobile device
US20170141925 * 17 nov 2015 18 mei 2017 International Business Machines Corporation Privacy friendly location based services
WO2003028343A2 * 24 sept 2002 3 april 2003 Motorola, Inc. Communication system for location sensitive information and method therefor
WO2003028343A3 * 24 sept 2002 7 aug 2003 Motorola Inc Communication system for location sensitive information and method therefor
Classificatie in de VS 455/414.1, 455/466
Coöperatieve classificatie H04W4/02
30 sept 2003 AS Assignment
24 okt 2013 FPAY Fee payment