US6757262B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Service framework supporting remote service discovery and connection
Assignee: Arris Enterprises LLC
•
Filing: 2000-09-15
•
Granted: 2004-06-29
•
Expires: 2020-09-15
Abstract
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. When a service is requested from a remote server, a service frontend (281, FIG. 9) on the client platform attempts to find its corresponding service backend (282, FIG. 9) on a server providing the requested service and, if it finds it, the frontend and backend coalesce in a fully formed service that is made available to a requesting service-using entity. As a result, platform resources and security are maintained. Various methods of operating a service framework are also described.
Inventors
- 👤 Bernhard Weisshaar
- 👤 Merlin Smith
- 👤 Parvathy Bhaskaran
- 👤 Mark Clayton
- 👤 Kungwel Mike Liu
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-26 11:37
CPC Classifications
H; H04; H04L; H04L67/00; H04L67/01; H04L67/04; H04L61/00; H04L61/45; H04L67/50; H04L67/51; H04L67/52; H04L9/00; H04L9/40; H04L69/00; H04L69/30; H04L69/32; H04L69/322; H04L69/329; H04W; H04W4/00; H04W76/00; H04W76/10
Claims Analysis
Total Claims: 47
Claim 1
Independent Claim
167 words
A method of operating a communications node comprising a service framework, a service-requesting entity residing on the communications node, and a service residing on the communications node, wherein the communications node comprises a wireless interface to which a remote communications node can be coupled, the method comprising: the service-requesting entity requesting the service framework to provide access to the service; the service framework providing the service-requesting entity with access to the service; the communications node comprising a connection manager service notifying the service framework when the communications node is communicating with the remote communications node via the wireless interface; the service framework comprising a proximity daemon responsive to the connection manager service, the proximity daemon creating a remote lookup service frontend when the service framework is notified by the connection manager service; the remote lookup service frontend broadcasting a search for a remote lookup service backend; and if a remote lookup service backend is found, the remote lookup service frontend communicating with the remote lookup service backend.
Claim 2
Independent Claim
167 words
A method of operating a communications node comprising a service framework, a service-requesting entity residing on the communications node, and a service residing on the communications node, wherein the communications node comprises a wireless interface to which a remote communications node can be coupled, the method comprising: the service-requesting entity requesting the service framework to provide access to the service; the service framework providing the service-requesting entity with access to the service; the communications node comprising a connection manager service notifying the service framework when the communications node is communicating with the remote communications node via the wireless interface; the service framework comprising a proximity daemon responsive to the connection manager service, the proximity daemon creating a remote lookup service frontend when the service framework is notified by the connection manager service; the remote lookup service frontend broadcasting a search for a remote lookup service backend; and if a remote lookup service backend is found, the remote lookup service frontend communicating with the remote lookup service backend.
Claim 3
Dependent Claim
24 words
The method recited in claim 1 wherein in communicating, the remote lookup service frontend and remote lookup service backend determine whether they are compatible.
Claim 4
Dependent Claim
69 words
The method recited in claim 2 , wherein the service framework further comprises a remote lookup daemon, the method further comprising: if the remote lookup service frontend and remote lookup service backend are compatible, the remote lookup service backend determines whether a service backend corresponding to the service resides on the remote communications node; and if so, the remote lookup service backend passes parameters to the remote lookup daemon.
Claim 5
Dependent Claim
45 words
The method recited in claim 3 , the service framework further comprising a service frontend and a service registry, the method further comprising: the remote lookup daemon passing the parameters to the service frontend; and the service frontend registering the service in the service registry.
Claim 6
Dependent Claim
75 words
The method recited in claim 4 , the service framework further comprising a service event notification registry; the service-requesting entity registering a notification request for the service in the service event notification registry; the service framework determining whether the service event notification registry contains a notification request registered by the service-requesting entity for the service; and if so, the service framework notifying the service-requesting entity of the service, and the service-requesting entity invoking the service.
Claim 7
Dependent Claim
27 words
The method recited in claim 5 , the method further comprising: the service frontend communicating with the service backend to provide the service to the service-requesting entity.
Claim 8
Independent Claim
259 words
A method of operating a communications node comprising a service framework, a service-requesting entity residing on the communications node, and a service residing on the communications node, wherein the communications node comprises a wireless interface to which a remote communications node can be coupled, the method comprising: the communications node comprising a connection manager service notifying the service framework when the communications node is communicating with the remote communications node via the wireless interface; the service-requesting entity requesting the service framework to provide access to the service; the service framework providing the service-requesting entity with access to the service, wherein the service framework comprises a service frontend and a remote service event notification registry, and wherein the service framework further comprises a proximity daemon responsive to the connection manager service; the service frontend registering a notification request for a service backend in the remote service event notification registry; the proximity daemon creating a remote lookup service frontend when the service framework is notified by the connection manager service; the remote lookup service frontend determining whether the remote service event notification registry contains a notification request for the service backend registered by the service frontend; if so, the remote lookup service frontend requests a remote lookup service backend on the remote communications node to determine whether the service backend is on the remote communications node; if so, the remote lookup service backend obtains parameters necessary for the service frontend to communicate with the service backend; and the remote lookup service backend communicates the parameters to the remote lookup service frontend.
Claim 9
Independent Claim
259 words
A method of operating a communications node comprising a service framework, a service-requesting entity residing on the communications node, and a service residing on the communications node, wherein the communications node comprises a wireless interface to which a remote communications node can be coupled, the method comprising: the communications node comprising a connection manager service notifying the service framework when the communications node is communicating with the remote communications node via the wireless interface; the service-requesting entity requesting the service framework to provide access to the service; the service framework providing the service-requesting entity with access to the service, wherein the service framework comprises a service frontend and a remote service event notification registry, and wherein the service framework further comprises a proximity daemon responsive to the connection manager service; the service frontend registering a notification request for a service backend in the remote service event notification registry; the proximity daemon creating a remote lookup service frontend when the service framework is notified by the connection manager service; the remote lookup service frontend determining whether the remote service event notification registry contains a notification request for the service backend registered by the service frontend; if so, the remote lookup service frontend requests a remote lookup service backend on the remote communications node to determine whether the service backend is on the remote communications node; if so, the remote lookup service backend obtains parameters necessary for the service frontend to communicate with the service backend; and the remote lookup service backend communicates the parameters to the remote lookup service frontend.
Claim 10
Dependent Claim
74 words
The method recited in claim 7 , wherein the service framework further comprises a service event notification registry, the method further comprising: the service frontend registering the service with the service framework; the service framework determining whether the service event notification registry contains a notification request registered by the service-requesting entity for the service; and if so, the service framework notifying the service-requesting entity of the service, and the service-requesting entity invoking the service.
Claim 11
Dependent Claim
28 words
The method recited in claim 8 , the method further comprising: the service frontend communicating with the service backend to implement the service invoked by the service-requesting entity.
Claim 12
Dependent Claim
132 words
A communications node comprising: a processor; a wireless interface coupled to the processor to enable the communications node to communicate with a remote node; and a memory coupled to the processor and comprising: a connection manager service; a service-requesting entity; and a service framework to discover a service requested by the service-requesting entity, the service being on the remote node, and to connect the service-requesting entity with the service, wherein the connection manager notifies the service framework when the communications node is in proximity to the remote node, and wherein the service framework comprises a proximity daemon to create a remote lookup service frontend when the service framework is notified by the connection manager service, the remote lookup service frontend to look for a remote lookup service backend on the remote node.
Claim 13
Dependent Claim
132 words
A communications node comprising: a processor; a wireless interface coupled to the processor to enable the communications node to communicate with a remote node; and a memory coupled to the processor and comprising: a connection manager service; a service-requesting entity; and a service framework to discover a service requested by the service-requesting entity, the service being on the remote node, and to connect the service-requesting entity with the service, wherein the connection manager notifies the service framework when the communications node is in proximity to the remote node, and wherein the service framework comprises a proximity daemon to create a remote lookup service frontend when the service framework is notified by the connection manager service, the remote lookup service frontend to look for a remote lookup service backend on the remote node.
Claim 14
Dependent Claim
33 words
The communications node recited in claim 10 wherein the service framework further comprises a first program module to determine whether the remote lookup service frontend is compatible with the remote lookup service backend.
Claim 15
Dependent Claim
38 words
The communications node recited in claim 11 wherein the service framework further comprises a second program module, responsive to the first program module, to determine whether a service backend corresponding to the service resides on the remote node.
Claim 16
Dependent Claim
35 words
The communications node recited in claim 12 wherein the service framework further comprises a remote lookup daemon, responsive to the second program module, to obtain parameters from the service backend to the remote lookup daemon.
Claim 17
Dependent Claim
38 words
The communications node recited in claim 13 wherein the service framework further comprises: a service frontend responsive to the remote lookup daemon to receive the parameters; and a service registry in which the service frontend registers the service.
Claim 18
Dependent Claim
30 words
The communications node recited in claim 14 wherein the service framework further comprises a service event notification registry in which a notification request can be registered by the service-requesting entity.
Claim 19
Dependent Claim
34 words
The communications node recited in claim 15 wherein the service framework further comprises a third program module to determine whether the service event notification registry contains a notification request registered by the service-requesting entity.
Claim 20
Dependent Claim
31 words
The communications node recited in claim 16 wherein the service framework further comprises a fourth program module, responsive to the third program module, to notify the service-requesting entity of the service.
Claim 21
Dependent Claim
20 words
The communications node recited in claim 17 wherein the service-requesting entity, responsive to the fourth program module, invokes the service.
Claim 22
Dependent Claim
25 words
The communications node recited in claim 18 wherein the service frontend communicates with the service backend to implement the service invoked by the service-requesting entity.
Claim 23
Dependent Claim
35 words
The communications node recited in claim 14 wherein the service framework further comprises a remote service event notification registry in which a notification request for a service backend can be registered by the service frontend.
Claim 24
Dependent Claim
34 words
The communications node recited in claim 20 wherein the remote lookup service frontend determines whether the remote service event notification registry contains a notification request for a service backend registered by the service frontend.
Claim 25
Dependent Claim
34 words
The communications node recited in claim 21 wherein the remote lookup service frontend requests a remote lookup service backend on the remote node to determine whether the service backend is on the remote node.
Claim 26
Dependent Claim
26 words
The communications node recited in claim 22 wherein the remote lookup service backend obtains parameters necessary for the service frontend to communicate with the service backend.
Claim 27
Dependent Claim
20 words
The communications node recited in claim 23 wherein the remote lookup service backend communicates the parameter to the service frontend.
Claim 28
Dependent Claim
18 words
The communications node recited in claim 24 wherein the service frontend registers the service with the service framework.
Claim 29
Dependent Claim
30 words
The communications node recited in claim 25 wherein the service framework determines whether the service event notification registry contains a notification request registered by the service-requesting entity for the service.
Claim 30
Dependent Claim
25 words
The communications node recited in claim 26 wherein the service framework notifies the service-requesting entity of the service, and the service-requesting entity invokes the service.
Claim 31
Dependent Claim
25 words
The communications node recited in claim 27 wherein the service frontend communicates with the service backend to implement the service invoked by the service-requesting entity.
Claim 32
Dependent Claim
158 words
A communications system comprising: at least one remote node; and at least one communications node comprising: a processor; a wireless interface coupled to the processor to enable the at least one communications node to communicate with the at least one remote node; and a memory coupled to the processor and comprising: a connection manager service; a service-requesting entity; and a service framework to discover a service requested by the service-requesting entity, the service being on at least one remote node, and to connect the service-requesting entity with the service, wherein the connection manager service notifies the service framework when the communications node is in proximity to at least one remote node, and wherein the service framework comprises a proximity daemon to create a remote lookup service frontend when the service framework is notified by the connection manager service, the remote lookup service frontend to look for a remote lookup service backend on the at least one remote node.
Claim 33
Dependent Claim
158 words
A communications system comprising: at least one remote node; and at least one communications node comprising: a processor; a wireless interface coupled to the processor to enable the at least one communications node to communicate with the at least one remote node; and a memory coupled to the processor and comprising: a connection manager service; a service-requesting entity; and a service framework to discover a service requested by the service-requesting entity, the service being on at least one remote node, and to connect the service-requesting entity with the service, wherein the connection manager service notifies the service framework when the communications node is in proximity to at least one remote node, and wherein the service framework comprises a proximity daemon to create a remote lookup service frontend when the service framework is notified by the connection manager service, the remote lookup service frontend to look for a remote lookup service backend on the at least one remote node.
Claim 34
Dependent Claim
33 words
The communications system recited in claim 29 wherein the service framework further comprises a first program module to determine whether the remote lookup service frontend is compatible with the remote lookup service backend.
Claim 35
Dependent Claim
41 words
The communications system recited in claim 30 wherein the service framework further comprises a second program module, responsive to the first program module, to determine whether a service backend corresponding to the service resides on the at least one remote node.
Claim 36
Dependent Claim
30 words
The communications system recited in claim 31 wherein the service framework further comprises a remote lookup daemon, responsive to the second program module, to obtain parameters from the service backend.
Claim 37
Dependent Claim
38 words
The communications system recited in claim 32 wherein the service framework further comprises: a service frontend responsive to the remote lookup daemon to receive the parameters; and a service registry in which the service frontend registers the service.
Claim 38
Dependent Claim
30 words
The communications system recited in claim 33 wherein the service framework further comprises a service event notification registry in which a notification request can be registered by the service-requesting entity.
Claim 39
Dependent Claim
34 words
The communications system recited in claim 34 wherein the service framework further comprises a third program module to determine whether the service event notification registry contains a notification request registered by the service-requesting entity.
Claim 40
Dependent Claim
31 words
The communications system recited in claim 35 wherein the service framework further comprises a fourth program module, responsive to the third program module, to notify the service-requesting entity of the service.
Claim 41
Dependent Claim
20 words
The communications system recited in claim 36 wherein the service-requesting entity, responsive to the fourth program module, invokes the service.
Claim 42
Dependent Claim
25 words
The communications system recited in claim 37 wherein the service frontend communicates with the service backend to implement the service invoked by the service-requesting entity.
Claim 43
Independent Claim
135 words
A method of discovering a service on a communications node, wherein the communications node comprises a service-requesting entity and a service registry, wherein the communications node further comprises an interface to which a remote communications node can be coupled, a service frontend, and a remote services event notification registry, 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 a service type; the service-requesting entity issuing the service template to the service registry; the service frontend registering a notification request for a service backend in the remote service event notification registry; and if the service registry has service objects matching the service template, the service registry returning to the service-requesting entity an array of such service objects.
Claim 44
Independent Claim
135 words
A method of discovering a service on a communications node, wherein the communications node comprises a service-requesting entity and a service registry, wherein the communications node further comprises an interface to which a remote communications node can be coupled, a service frontend, and a remote services event notification registry, 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 a service type; the service-requesting entity issuing the service template to the service registry; the service frontend registering a notification request for a service backend in the remote service event notification registry; and if the service registry has service objects matching the service template, the service registry returning to the service-requesting entity an array of such service objects.
Claim 45
Dependent Claim
41 words
The method recited in claim 39 , in which the remote communications node comprises a service backend corresponding to the service, the method comprising: obtaining parameters from the service backend necessary for the service frontend to communicate with the service backend.
Claim 46
Dependent Claim
17 words
The method recited in claim 40 , the method comprising: communicating the parameters to the service frontend.
Claim 47
Dependent Claim
26 words
The method recited in claim 41 , the method comprising: the service frontend communicating with the service backend to provide the service to the service-requesting entity.
References Cited (Backward Citations)
US5805804A
Cited
US6091956A
Cited
US6611498B1
Cited
WO1999044127A1
Cited
US6226788B1
Cited
US6167255A
Cited
US6470453B1
Cited
US6604140B1
Cited
US6430599B1
Cited
US6580916B1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2007-06-29 | 2007-12-29 | 2008-06-29 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2011-06-29 | 2011-12-29 | 2012-06-29 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2015-06-29 | 2015-12-29 | 2016-06-29 | $7700.00 | Window Closed / Lapsed |