IP Library Granted Patent US 11,570,065
Granted Patent B2
US 11,570,065 · App. 15/302,545 · Granted Jan 31, 2023

Service enabler function

Inventors: Hongkun Li (Malvern, PA); Guang Lu (Ontario, 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
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,570,065
App. No.
15/302,545
Granted
Jan 31, 2023
Kind
B2
Abstract

The present application describes a method and apparatus for updating a service in a service layer function of a network. In particular, a method for adding a service is disclosed. Initially, a request is received at a service enabler function located in the service layer function to add the service. A service description of the requested service is reviewed to understand its capabilities. A verification request is sent to a service capability located in the service layer function. Further, another service layer function or application is notified that the requested service is enabled.

Claims (39)

1. A computer-implemented method for managing a service in a service layer comprising:

receiving a request at a service enabler function located in the service layer to manage a change of state of the service through a service API, where the service API includes a common service API and a unique service API, the common service API retrieves service information, the unique service API distinguishes the service from one or more other services, the unique service API accesses and/or utilizes the service or the one or more other services, and the change of state includes one or more of adding, removing, activating, and deactivating the service;

reviewing and parsing, at the service enabler function, a service description indicating one or more service capabilities to recognize and utilize the requested service;

based on the service description, identifying the one or more service capabilities in the service layer, and sending a request to and/or instructing the one or more service capabilities to ensure the requested service is enabled and supported by the service layer for the change of state;

notifying one or more applications and/or other service layers that the service has changed its state.

2. The method according to claim 1 , further comprising.

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

3. The method according to claim 1 , wherein the service enabler function translates the service API to be compatible with other services hosted in the service layer.

4. The method according to claim 1 , wherein the service description is selected from 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 and combinations thereof.

5. The method according to claim 1 , further comprising:

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

6. The method according to claim 5 , wherein the determining step is performed by a service state management and configuration function.

7. The method according to claim 1 , further comprising:

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

8. The method according to claim 1 , further comprising:

determining, at the service enabler function, which of the other service layer or the application to notify about the requested service.

9. The method according to claim 8 , wherein the determining step is performed by a service coordination function.

10. A computer-implemented method for managing removal of a service in a Service layer comprising:

receiving a request at a service enabler function located in the service layer to manage removal of the service through a service API, where the service API includes a common service API and a unique service API, the common service API retrieves service information, the unique service API distinguishes the service from one or more other services, the unique service API accesses and/or utilizes the service or the one or more other services, where the service includes a service description indicating one or more service capabilities to recognize and utilize the service;

identifying and parsing, at the service enabler function, the service to be removed;

sending a service state update request to a service state management and configuration function;

notifying the one or more service capabilities in the service layer that the service has been removed; and

notifying one or more applications and/or other service layers that the service has been removed.

11. The method according to claim 10 , wherein the request includes a service description attribute selected from a service provider ID, service ID, software module information, RESTful service API, and combinations thereof.

12. The method according to claim 10 , further comprising:

determining whether a version of the service or the entire service is to be removed.

13. The method according to claim 10 , further comprising:

sending a request to a service API management function for removing the service API of the service.

14. A computer-implemented apparatus on a network comprising:

a computer readable storage medium including instructions for managing a service in a service layer through a service API that, where the service API includes a common service API and a unique service API, the common service API retrieves service information, the unique service API distinguishes the service from one or more other services, the unique service API accesses and/or utilizes the service or the one or more other services, when executed by a processor causes the processor to:

manage, via a service enabler function, a change of state of the service including adding, removing, activating, and deactivating the service;

evaluate a service description indicating one or more service capabilities to recognize and utilize the service; and

based on the service description, identify one of the service capabilities in the service layer, and send a request to and/or instruct the one or more service capabilities to ensure the service is enabled and supported by the service layer for the change of state.

15. The apparatus according to claim 14 , 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.

16. The apparatus according to claim 15 , wherein the service state management and configuration function describes the capabilities of the service for discovery and utilization by the an application or other service.

17. The apparatus according to claim 14 , wherein the apparatus is a network node.

18. A networked system comprising:

the apparatus according to claim 14 ; and

an application domain.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 9, 2025
From: CONVIDA WIRELESS,LLC
To: IPLA HOLDINGS INC.
Reel/Frame 073903/0733 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 24, 2017
From: LI, HONGKUN; LU, GUANG; DONG, LIJUN; SEED, DALE N.; FLYNN, WILLIAM ROBERT, IV; MLADIN, CATALINA M.; LI, XU
To: CONVIDA WIRELESS, LLC
Reel/Frame 041367/0439 →
Continuity (2)
Provisional Application 61977382 · Apr 9, 2014
Related Publication 20170034015A1 · Feb 2, 2017