Service framework for evaluating remote services based upon transport characteristics

• US 6,580,916 B1
• Filed: 09/15/2000
• Issued: 06/17/2003
• Est. Priority Date: 09/15/2000
• Status: Expired due to Term

• Current Assignee: ARRIS Enterprises LLC (CommScope Holding Company, Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Clayton, Mark, Bhaskaran, Parvathy, Smith, Merlin, Weisshaar, Bernhard, Liu, Kungwel Mike
• Primary Examiner(s): Chin, Vivian
• Assistant Examiner(s): Afshar, Kamran
• Application Number:
  US09/662,307
• Time in Patent Office: 1,005 Days
• Field of Search: 455/517, 455/414, 455/412, 455/450, 455/452, 455/435, 455/445, 455/560, 455/466, 455/456, 342/357.09, 701/207, 379/196, 379/211, 379/210, 375/202, 331/25, 331/16, 331/17
• US Class Current: 455/456.1
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• 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: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 68/00 User notification, e.g. alerting and paging, for incoming communication, change of service or the like
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 76/30 Connection release
• CPC Class Codes: H04W 8/005 Discovery of network devices, e.g. terminals

Abstract

In an information appliance system 100, a user device 108 comprises a client platform (200, FIG. 5) that includes a service framework (235, FIG. 5) to discover and connect with a variety of services, both remote and local, transient and persistent, and to disconnect from them when they are no longer of interest or become unavailable. The service framework 235 provides a standard, consistent, simplified way for services to make themselves available and for service-using entities to locate and connect with the services of interest to them. The service framework 235 comprises service event notification registries (254, 256, FIG. 7) in which service-requesting entities register templates defining the types of services they want to locate and connect with. However, the service framework 235, rather than connecting with any service that matches a desired service type, can further control a remote service lookup operation in accordance with various transport characteristics in the template, such as signal strength, quantity of data to be transferred, range, available bandwidth, communications cost, service location, time of day, vehicular velocity, and so forth. This conserves the platform'"'"'s memory and bandwidth resources by not connecting with services that would not satisfy a user'"'"'s request or that would be unduly transitory. Various methods of operating a service framework are also described.

Claims

1. In a communications platform comprising a service-requesting entity, a service framework and an interface with which a remote communications node can be coupled to the communications platform, the remote communications node comprising a remote service, the method comprising;

the service-requesting entity requesting the remote service;

using the interface to provide only the remote service requested by the service-requesting entity;

the service-requesting entity constructing a service template representing the remote service, the service template comprising at least one service attribute;

the service-requesting entity issuing the service template to the service framework; and

if the service framework has service objects matching the service template, the service framework returning to the service-requesting entity such service objects, otherwise returning a null.

2. In a communications platform comprising a service-requesting entity, a service framework comprising a remote lookup service frontend, and an interface with which a remote communications node can be coupled to the communications platform, the remote communications node comprising a remote service and a remote lookup service backend, the method comprising;

the service-requesting entity requesting the remote service;

using the interface to provide only the remote service requested by the service-requesting entity;

the service-requesting entity constructing a service template representing the remote service, the service template comprising at least one service attribute;

the service-requesting entity issuing the service template to the service framework; and

the remote lookup service frontend communicating with the remote lookup service backend.

3. The method recited in claim 2, wherein the remote communications node comprises at least one service attribute, the method further comprising:

the remote lookup service backend communicating the at least one service attribute in the remote communications node to the remote lookup service frontend.

4. The method recited in claim 3, the method further comprising:

the service framework determining whether the at least one service attribute in the remote communications node matches the at least one service attribute in the service template.

5. The method recited in claim 3, the method further comprising:

if and only if the at least one service attribute in the remote communications node matches the at least one service attribute in the service template, providing the remote service to the service-requesting entity.

6. A communications platform comprising:

a processor;

a wireless interface coupled to the processor to enable the communications platform to communicate with a remote node, wherein the remote node comprises at least one service attribute and a remote lookup service backend; and

a memory coupled to the processor and comprising;

a service-requesting entity to request a service on the remote node;

at least one service attribute specified by the service-requesting entity and associated with the service;

a service framework to discover the service and to provide the service to the service-requesting entity as specified by the at least one service attribute;

a remote lookup service frontend to receive information from the remote lookup service backend over the wireless interface concerning the at least one service attribute on the remote node; and

a first program module to determine whether the at least one service attribute on the remote node matches the at least one service attribute in the service template and, if so, to provide the service to the service-requesting entity.

7. A communications system comprising:

at least one remote node, wherein the at least one remote node comprises at least one service attribute and a remote lookup service backend; and

at least one communications platform comprising;

a processor;

a wireless interface coupled to the processor to enable the at least one communications platform to communicate with the at least one remote node;

a memory coupled to the processor and comprising;

a service-requesting entity to request a service on the at least one remote node;

at least one service attribute specified by the service-requesting entity and associated with the service;

a service framework to discover the service and to provide the service to the service-requesting entity as specified by the at least one service attribute;

a remote lookup service frontend to receive information from the remote lookup service backend over the wireless interface concerning the at least one service attribute on the at last one remote node; and

a first program module to determine whether the at least one service attribute on the at last one remote node matches the at least one service attribute in the service template and, if so, to provide the service to the service-requesting entity.

8. A method of providing a service to a communications platform, wherein the communications platform comprises a service-requesting entity and a service framework, wherein the communications platform further comprises an interface to which a remote communications node can be coupled, and wherein the service resides on the remote communications node, the method comprising:

the service-requesting entity constructing a service template representing a desired service, the service template comprising at least one service attribute;

the service-requesting entity issuing the service template to the service framework; and

if the service framework has service objects matching the service template, the service framework returning to the service-requesting entity an array of such service objects, otherwise returning a null.

9. The method recited in claim 8, wherein the remote communications node further comprises a remote lookup service backend, and wherein the service framework further comprises a remote lookup service frontend, the method further comprising:

the remote lookup service frontend communicating with the remote lookup service backend.

10. The method recited in claim 9, wherein the remote communications node further comprises at least one service attribute, the method further comprising:

the remote lookup service backend communicating the at least one service attribute in the remote communications node to the remote lookup service frontend.

11. The method recited in claim 10, the method further comprising:

the service framework determining whether the at least one service attribute in the remote communications node matches the at least one service attribute in the service template.

12. The method recited in claim 11, the method further comprising:

if and only if the at least one service attribute in the remote communications node matches the at least one service attribute in the service template, providing the remote service to the service-requesting entity.