Obtaining location information using a rejection model

• US 20040064565A1
• Filed: 02/06/2002
• Published: 04/01/2004
• Est. Priority Date: 02/06/2002
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Hennessy, James P., Gdaniec, Joseph M., Bennett, Valerie M., Batra, Virinder M., Capella, Andrew N., Gamble, Peter R., Feustel, Stephen V., Howland, Michael J., Brocious, Larry A.
• Application Number:
  US10/068,362
• Publication Number:
  US 20040064565A1
• Time in Patent Office: Days
• US Class Current: 709/228
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services

Abstract

A method of requesting location-based services using a rejection model. Responsive to receiving from a pervasive device a network request for location-based processing, the received network request can be stored prior to being forwarded to a selected location-based application. A rejection response to the forwarded network request can be received subsequently and a request for required location information can be identified in the rejection response. The required location information can be identified within the stored network request and a specific network request can be formulated with the required location information. Finally, the specific network request can be forwarded to the selected location-based application. The selected location-based application, in turn, can perform the requested location-based processing using the required location information provided in the specific network response.

Claims

1. A method of requesting location-based services comprising the steps of:

responsive to receiving a network request for location-based processing from a pervasive device, storing said received network request and forwarding said received network request to a selected location-based application;

receiving a rejection response to said forwarded network request and identifying in said rejection response a request for required location information; and

,

locating said required location information from within said stored network request, formulating an augmented network request with said required location information, and forwarding said augmented network request to said selected location-based application, said selected location-based application performing said location-based processing using said required location information provided in said augmented network response.

2. The method of claim 1, wherein said network requests are hypertext transfer protocol (HTTP) requests and said rejection response is a class 4xx HTTP rejection response.

3. The method of claim 1, further comprising, the steps of:

caching said augmented network requests in a cache.

4. The method of claim 3, wherein said steps of storing and forwarding said received network request comprises the steps of:

determining whether a valid augmented network request associated with said received network request can be located within said cache; and

,

if said valid augmented network request can be located within said cache, forwarding said valid augmented network request to said selected location based application; and

,

if a valid augmented network request cannot be located within said cache, storing said received network request and forwarding said received network request to said selected location-based application.

5. The method of claim 4, further comprising the steps of:

recognizing a pattern of received network requests which result in a particular rejection response;

associating a particular formulated augmented network request with said recognized pattern; and

,

storing said particular formulated augmented network request in said cache according to said association.

6. The method of claim 4, further comprising the steps of:

recognizing a pattern of received network requests which result in a rejection response for which said required location information cannot be provided to said selected location based application as requested in said rejection response;

associating a particular formulated augmented network request with said recognized pattern, said particular formulated augmented network request indicating that said required location information cannot be provided to said selected location based application; and

,

storing said particular formulated augmented network request in said cache according to said association.

7. A machine readable storage having stored thereon a computer program for requesting location-based services, the computer program comprising a routine set of instructions for causing the machine to perform the steps of:

responsive to receiving a network request for location-based processing from a pervasive device, storing said received network request and forwarding said received network request to a selected location-based application;

receiving a rejection response to said forwarded network request and identifying in said rejection response a request for required location information; and

,

locating said required location information from within said stored network request, formulating an augmented network request with said required location information, and forwarding said augmented network request to said selected location-based application, said selected location-based application performing said location-based processing using said required location information provided in said augmented network response.

8. The machine readable storage of claim 7, wherein said network requests are hypertext transfer protocol (HTTP) requests and said rejection response is a class 4xx HTTP rejection response.

9. The machine readable storage of claim 7, further comprising the steps of:

caching said augmented network requests in a cache.

10. The machine readable storage of claim 9, wherein said steps of storing and forwarding said received network request comprises the steps of:

determining whether a valid augmented network request associated with said received network request can be located within said cache; and

,

if said valid augmented network request can be located within said cache, forwarding said valid augmented network request to said selected location based application; and

,

if a valid augmented network request cannot be located within said cache, storing said received network request and forwarding said received network request to said selected location-based application.

11. The machine readable storage of claim 10, further comprising the steps of:

recognizing a pattern of received network requests which result in a particular rejection response;

associating a particular formulated augmented network request with said recognized pattern; and

,

storing said particular formulated augmented network request in said cache according to said association.

12. The machine readable storage of claim 10, further comprising the steps of:

recognizing a pattern of received network requests which result in a rejection response for which said required location information cannot be provided to said selected location based application as requested in said rejection response;

associating a particular formulated augmented network request with said recognized pattern, said particular formulated augmented network request indicating that said required location information cannot be provided to said selected location based application; and

,

storing said particular formulated augmented network request in said cache according to said association.