Method and apparatus for determination of device capabilities on a network

• US 20040024867A1
• Filed: 10/28/2002
• Published: 02/05/2004
• Est. Priority Date: 06/28/2002
• Status: Abandoned Application

• Current Assignee: Unwired Planet LLC (JP Morgan Chase & Co)
• Original Assignee: Openwave Systems Incorporated (JP Morgan Chase & Co)
• Inventors: Kjellberg, Rikard M.
• Application Number:
  US10/282,557
• Publication Number:
  US 20040024867A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 3/42178 by downloading data to substation equipment
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities

Abstract

The disclosed system determines capabilities of client devices on a network to facilitate responses to requests from the client devices. The system attempts to use information in or associated with a request, such as a session identifier or a header of the request, to search for matching information in a device capabilities database. If found, the system maps the information to a set of stored device capabilities of the client device. If the system is unable to find an exact match for the information, the system attempts to find an approximate match. If an approximate match is found, the system takes the stored device capabilities associated with the stored matching information to be the capabilities of the client device. The new association is then recorded for future use. Any capabilities specified in the request are also added to the set of stored capabilities associated with the client device.

Claims

1. A method comprising:

receiving a request from a client device on a network; and

in response to the request, identifying device capabilities of the client device by using information which neither specifies device capabilities nor directly identifies the client device to associate a set of stored device capabilities with the client device.

2. A method as recited in claim 1, wherein said identifying device capabilities of the client device comprises:

using information from the request as a first identifier to search for the first identifier in a database; and

if the first identifier is not found,

identifying a stored second identifier that only partially matches the first identifier, and

associating with the client device a set of stored device capabilities that are associated with the second identifier.

3. A method as recited in claim 2, further comprising associating said set of stored device capabilities with a device identifier of the client device.

4. A method as recited in claim 2, wherein information from the request is from a header of the request.

5. A method as recited in claim 2, further comprising:

identifying a capability of the client device specified in the request; and

adding the capability specified in the request to the set of stored device capabilities in association with the client device.

6. A method as recited in claim 1, wherein said identifying device capabilities of the client device comprises:

searching a database for an identifier associated with the client device using information from the request as a search criterion; and

if no exact match of the search criterion is found but an identifier which approximately matches the search criterion is found, then associating with the client device a stored set of device capabilities associated with the identifier that approximately matches the search criterion.

7. A method as recited in claim 6, wherein the information from the request is from a header of the request.

8. A method as recited in claim 6, wherein said identifying device capabilities of the client device comprises, if an exact match of the search criterion is found, using a device capabilities set associated with the identifier that matches the search criterion as the device capabilities of the client device.

9. A method as recited in claim 6, wherein the database comprises a cache and a primary storage.

10. A method as recited in claim 9, wherein said searching in a database for an identifier comprises:

first searching for the identifier in the cache; and

if the identifier is not found in the cache, then searching for the identifier in the primary storage.

11. A method as recited in claim 10, wherein said associating with the client device a stored set of device capabilities comprises:

storing, in the cache and the primary storage, a device identifier of the client device in association with the set of device capabilities associated with the identifier that approximately matches the search criterion.

12. A method of determining device capabilities of a client device on a network, the method comprising:

identifying a predetermined header in a request from the client device;

using at least a portion of the header as an attribute identifier of the request;

searching in a database for an identifier that matches the attribute identifier;

if an exact match of the attribute identifier is found in the database, then taking a set of stored device capabilities associated with the attribute identifier to be the device capabilities of the client device;

if no exact match of the attribute identifier is found, then searching in the database for an identifier that approximately matches the attribute identifier; and

if an identifier that approximately matches the attribute identifier is found in the database, then taking a set of stored device capabilities associated with the identifier that approximately matches the attribute identifier to be the device capabilities of the client device, including storing in the database, in association with the attribute identifier, the set of device capabilities associated with the identifier that approximately matches the attribute identifier.

13. A method as recited in claim 12, wherein said storing comprises:

storing, in the database, a device identifier of the client device in association with the set of device capabilities associated with the identifier that approximately matches the attribute identifier.

14. A method as recited in claim 13, further comprising adding a capability of the client device specified in the request to the set of stored device capabilities, in association with the client device.

15. A method as recited in claim 12, further comprising:

determining whether a session identifier is associated with the request, prior to said searching for an identifier that matches the attribute identifier;

wherein said searching for an identifier that matches the attribute identifier is done only upon determining that no session identifier is associated with the request.

16. A method as recited in claim 15, further comprising, if a session identifier is determined to be associated with the request, then:

using the session identifier to look up a set of stored device capabilities associated with the session identifier; and

taking the set of stored device capabilities associated with the session identifier to be the device capabilities of the client device.

17. A method as recited in claim 12, further comprising, if the request is determined not to include a predetermined header, then:

determining a user identifier associated with the request;

determining whether a set of stored device capabilities is associated with the user identifier; and

if a set of stored device capabilities is determined to be associated with the user identifier, then taking the set of stored device capabilities associated with the user identifier to be the device capabilities of the client device.

18. A method as recited in claim 12, wherein the database comprises a cache and a primary storage.

19. A method as recited in claim 18, wherein said searching in a database for an identifier that matches the attribute identifier comprises:

searching for an identifier that matches the attribute identifier in the cache; and

if an identifier that matches the attribute identifier is not found in the cache, then searching for an identifier that matches the attribute identifier in the primary storage.

20. A method as recited in claim 19, wherein said storing comprises:

storing, in both the primary storage and the cache, in association with the attribute identifier, the set of device capabilities associated with the identifier that approximately matches the attribute identifier.

21. A method of determining device capabilities of a client device on a network, the method comprising:

receiving a request from the client device;

determining whether a session identifier is associated with the request;

if a session identifier is determined to be associated with the request, using the session identifier to look up a set of stored device capabilities associated with the session identifier, and taking the set of stored device capabilities to represent the device capabilities of the client device;

if no session identifier is determined to be associated with the request, then determining whether the request includes a predetermined header;

if the request is determined to include the predetermined header, then

using at least a portion of the header as an attribute identifier of the request,

searching for an identifier that matches the attribute identifier in a cache and, if not found in the cache, in a primary storage,

if an exact match of the attribute is found in either the cache or the primary storage, then taking a set of stored device capabilities associated with the attribute identifier to be the device capabilities of the client device, and

if no exact match of the attribute identifier is found in either the cache or the primary storage, then searching for an identifier that approximately matches the attribute identifier in the primary storage;

if an identifier that approximately matches the attribute identifier is found in the primary storage, then taking a set of stored device capabilities associated with the identifier that approximately matches the attribute identifier to be the device capabilities of the client device, including storing in the primary storage and the cache, the set of device capabilities associated with the identifier that approximately matches the attribute identifier, in association with the attribute identifier;

if the request is determined not to include a predetermined header, then;

determining a user identifier associated with the request,

determining whether a set of stored device capabilities is associated with the user identifier, and

if a set of stored device capabilities is determined to be associated with the user identifier, then taking the set of stored device capabilities associated with the user identifier to be the device capabilities of the client device; and

if no set of stored device capabilities is determined to be associated with the user identifier, then determining the device capabilities of the client device by interrogating a user of the client device.

22. A method as recited in claim 21, further comprising:

identifying a capability of the client device specified in the request; and

adding the capability specified in the request to the set of device capabilities associated with the identifier that approximately matches the attribute identifier, in association with the client device.

23. A system comprising:

a request router to receive and route a request from a client device on a network;

a database coupled to the request router and containing device capabilities information for a plurality of devices on the network; and

a device capability manager, coupled to the request router, to;

use information associated with the request as a first request attribute identifier to search for the first request attribute identifier in the database, and if the first request attribute identifier is not found, to

identify a stored second request attribute identifier that only partially matches the first request attribute identifier, and

associate with the client device a set of stored device capabilities associated with the second request attribute identifier.

24. A system as recited in claim 23, wherein the device capability manager further is to associate said set of stored device capabilities with a device identifier of the client device.

25. A system as recited in claim 23, wherein information associated with the request is from a header of the request.

26. A system as recited in claim 23, wherein the device capability manager further is to:

identify a capability of the client device specified in the request; and

add the capability specified in the request to the set of stored device capabilities in association with the client device.

27. A system as recited in claim 23, wherein the database comprises a cache and a primary storage.

28. A system as recited in claim 27, wherein the device manager is to use the information associated with the request to search for the first request attribute identifier by:

first searching for the first request attribute identifier in the cache; and

if the first request attribute identifier is not found in the cache, then searching for the first request attribute identifier in the primary storage.

29. A system as recited in claim 28, wherein the device manager is to associate with the client device the set of stored device capabilities associated with the second request attribute identifier by:

storing, in the cache and the primary storage, a device identifier of the client device in association with the set of device capabilities associated with the second request attribute identifier.

30. A system as recited in claim 23, further comprising:

a session manager to manage sessions of the devices on the network, including assigning a session identifier to each session;

wherein the device capabilities manager further is to determine whether a session identifier is associated with the request from the client device prior to the search for the first request attribute identifier; and

wherein the search for the first request attribute identifier is done only upon determining that no session identifier is associated with the request.

31. A system as recited in claim 30, wherein the device capabilities manager further is to:

if a session identifier is determined to be associated with the request, use the session identifier to look up a set of stored device capabilities associated with the session identifier, and take the set of stored device capabilities associated with the session identifier to be the device capabilities of the client device.

32. A system as recited in claim 23, further comprising:

a user manager to authenticate users of the devices on the network, including storing user identifiers associated with the users;

wherein the device capabilities manager further is to

receive a user identifier associated with a request from one of the devices on the network,

determine whether the database includes a set of stored device capabilities associated with the user identifier, and

if the database includes a set of stored device capabilities associated with the user identifier, to take the set of stored device capabilities associated with the user identifier to be the device capabilities of said one of the devices.

33. A processing system comprising:

a processor;

a data communication device to communicate data via a network; and

a storage device storing instructions which, when executed by the processor, cause the processing system to execute a process of determining device capabilities of a client device on the network, the process comprising

identifying a predetermined header in a request from the client device,

using at least a portion of the header as an attribute identifier of the request,

searching in a database for an identifier that matches the attribute identifier,

if an exact match of the attribute identifier is found in the database, then taking a set of stored device capabilities associated with the attribute identifier to be the device capabilities of the client device,

if no exact match of the attribute identifier is found, then searching in the database for an identifier that approximately matches the attribute identifier, and

if an identifier that approximately matches the attribute identifier is found in the database, then taking a set of stored device capabilities associated with the

identifier that approximately matches the attribute identifier to be the device capabilities of the client device, including storing in the database, in association with the attribute identifier, the set of device capabilities associated with the identifier that approximately matches the attribute identifier.

34. An apparatus comprising:

means for receiving a request from a client device on a network; and

means for identifying, in response to the request, device capabilities of the client device by using information which neither specifies device capabilities nor directly identifies the client device to associate a set of stored device capabilities with the client device.