Granted Patent B2

US 12,375,369 · App. 18/609,018 · Granted Jul 29, 2025

Inventors: Hongkun Li (Malvern, PA); Guang Lu (Thornhill, CA); Lijun Dong (San Diego, CA); Dale N. Seed (Allentown, PA); William Robert Flynn, IV (Schwenksville, PA); Catalina M. Mladin (Hatboro, PA); Xu Li (Plainsboro, NJ)

Assignee: Convida Wireless, LLC

H04L41/5045G06F8/61G06F9/44505H04L41/5058H04W4/50

Abstract

Claims (31)

1. An apparatus for managing a service in a service layer, where the service has a service API, where the service API includes a common service API and a unique service API, where the common service API is used to retrieve service information, where the unique service API distinguishes the service from one or more other services, where the unique service API is used to access and/or utilize the service, and where the apparatus comprises circuitry configured to:

receive a request to manage, via a service enabler function of the service layer, a change of state of the service including adding, removing, activating, or deactivating the service, where the request comprises a service description;

evaluate, via the service enabler function, the service description comprising identifiers of one or more services to manage; and

identify one or more service capabilities in the service layer to assist in managing the one or more services identified in the service description, and to send a request to and/or instruct the one or more service capabilities to perform the change of state of the one or more services identified in the service description.

2. The apparatus according to claim 1 , wherein the service enabler function includes a service coordination function, service state management and configuration function and service API management function that communicate with each other.

3. The apparatus according to claim 2 , wherein the service state management and configuration function describes the capabilities of the service for discovery and utilization by an application or the one or more other services.

4. The apparatus according to claim 1 , wherein the apparatus is a network node.

5. A networked system comprising:

the apparatus according to claim 1 ; and

an application domain.

6. The apparatus of claim 1 , wherein the service layer is provided as a middleware service supporting service capabilities through a set of APIs.

7. The apparatus of claim 6 , wherein the middleware service is located on top of network protocol stacks.

8. The apparatus of claim 7 , wherein the service layer is defined accordingly to ETSI/oneM2M standards.

9. A method for managing a service in a service layer, where the service has a service API, where the service API includes a common service API and a unique service API, where the common service API is used to retrieve service information, where the unique service API distinguishes the service from one or more other services, where the unique service API is used to access and/or utilize the service, the method comprising:

receiving a request to manage, via a service enabler function of the service layer, a change of state of the service including adding, removing, activating, or deactivating the service, where the request comprises a service description;

evaluating, via the service enabler function, the service description comprising identifiers of one or more services to manage; and

identifying one or more service capabilities in the service layer to assist in managing the one or more services identified in the service description, and to send a request to and/or instruct the one or more service capabilities to perform the change of state of the one or more services identified in the service description.

10. The method according to claim 9 , wherein the service enabler function includes a service coordination function, service state management and configuration function and service API management function that communicate with each other.

11. The method according to claim 10 , wherein the service state management and configuration function describes the capabilities of the service for discovery and utilization by an application or the one or more other services.

12. The method of claim 9 , wherein the service layer is provided as a middleware service supporting service capabilities through a set of APIs.

13. The method of claim 12 , wherein the middleware service is located on top of network protocol stacks.

14. The method of claim 13 , wherein the service layer is defined accordingly to ETSI/oneM2M standards.

15. The method of claim 9 , further comprising:

integrating the service API into the service layer so the requested service can be discovered and utilized by one or more other service layers and/or applications, wherein the service API is RESTful.

16. The method of claim 9 , wherein the service enabler function translates the service API to be compatible with other services hosted in the service layer.

17. The method of claim 9 , wherein the service description is selected from any one or more of service provider ID, service ID, list of dependent services, unique RESTful service API, common RESTful service API, location of the service, authentication method, authorization and access control information, software module information, protocol support, service compatibility, charging policy or combinations thereof.

18. The method of claim 9 , further comprising:

determining, at the service enabler function, whether the service is an updated version of an existing service or a new service.

19. The method of claim 18 , wherein the determination is performed by a service state management and configuration function.

20. The method of claim 9 , further comprising:

receiving a response from the one or more of the service capabilities that a new service is enabled.

Assignments (1)

Continuity (4)

References Cited (73)