Granted Patent B2

US 12,389,360 · App. 18/163,971 · Granted Aug 12, 2025

Inventors: Chih-Wei Su (Taipei, TW); Pei-Hsuan Lin (Taipei, TW)

Assignee: LITE-ON TECHNOLOGY CORPORATION

H04W60/04H04W8/18

Abstract

Claims (77)

1. A method for communication in service management and orchestration, comprising:

receiving, by a Non-real time radio access network (RAN) Intelligent Controller (Non-RT RIC) framework, a first subscription message from an Element Management System (EMS), wherein the first subscription message is used to request second data used to run a Non-RT RIC application (rApp);

transmitting, by the Non-RT RIC framework, a first callback message to the rApp according to the first subscription message to notify the rApp that the EMS requests the second data;

transmitting, by the rApp, a second subscription message to the Non-RT RIC framework, wherein the second subscription message is used to request first data used to generate the second data;

transmitting, by the Non-RT RIC framework, a second callback message to the EMS according to the second subscription message;

transmitting, by the EMS, the first data to the rApp according to the second callback message;

obtaining, by the rApp, the second data according to the first data; and

transmitting, by the rApp, the second data to the EMS according to the first callback message.

2. The method as claimed in claim 1 , further comprising:

reading, by the EMS, the second data, and displaying the second data on a web service page.

3. The method as claimed in claim 1 , wherein before the Non-RT RIC framework receives the first subscription message from the EMS, the method further comprises:

performing, by the EMS, a first registration procedure on the Non-RT RIC framework; and

performing, by the rApp, a second registration procedure on the Non-RT RIC framework.

4. The method as claimed in claim 3 , wherein the first registration procedure comprises the following steps:

transmitting, by the EMS, a first registration request message to the Non-RT RIC framework to request registration of the EMS;

transmitting, by the EMS, a first subscription request message to the Non-RT RIC framework to request to subscribe to the data required by the EMS;

transmitting, by the EMS, a first information type registration message to the Non-RT RIC framework to request registration of the information types provided by the EMS; and

transmitting, by the EMS, a first information producer registration message to the Non-RT RIC framework to request to register the EMS as an information producer.

5. The method as claimed in claim 3 , wherein the second registration procedure comprises the following steps:

transmitting, by the rApp, a second registration request message to the Non-RT RIC framework to request registration of the rApp;

transmitting, by the rApp, a second subscription request message to the Non-RT RIC framework to request to subscribe to the data required by the rApp;

transmitting, by the rApp, a second information type registration message to the Non-RT RIC framework to request registration of the information types provided by the rApp; and

transmitting, by the rApp, a second information producer registration message to the Non-RT RIC framework to request to register the rApp as an information producer.

6. The method as claimed in claim 1 , wherein an IP address of the EMS is included in the first subscription message and the first callback message.

7. The method as claimed in claim 1 , wherein an IP address of the rApp is included in the second subscription message and the second callback message.

8. The method as claimed in claim 1 , wherein the Non-RT RIC framework is connected with the EMS through a service management and orchestration (SMO) internal interface.

9. The method as claimed in claim 1 , wherein the Non-RT RIC framework is connected with the rApp through an R1 interface.

10. A system for communication in service management and orchestration, comprising:

an Element Management System (EMS);

a Non-real time radio access network (RAN) Intelligent Controller (Non-RT RIC) application (rApp); and

a Non-RT RIC framework, coupled to the EMS and the rApp;

wherein the Non-RT RIC framework receives a first subscription message from the EMS, wherein the first subscription message is used to request second data used to run the rApp;

the Non-RT RIC framework transmits a first callback message to the rApp according to the first subscription message to notify the rApp that the EMS requests the second data;

the rApp transmits a second subscription message to the Non-RT RIC framework, wherein the second subscription message is used to request first data used to generate the second data;

the Non-RT RIC framework transmits a second callback message to the EMS according to the second subscription message;

the EMS transmits the first data to the rApp according to the second callback message;

the rApp obtains the second data according to the first data; and

the rApp transmits the second data to the EMS according to the first callback message.

11. The system as claimed in claim 10 , wherein the system further executes the following actions:

the EMS reads the second data, and displays the second data on a web service page.

12. The system as claimed in claim 10 , wherein before the Non-RT RIC framework receives the first subscription message from the EMS, the system further executes the following actions:

the EMS performs a first registration procedure on the Non-RT RIC framework; and

the rApp performs a second registration procedure on the Non-RT RIC framework.

13. The system as claimed in claim 12 , wherein the first registration procedure comprises the following actions:

the EMS transmits a first registration request message to the Non-RT RIC framework to request registration of the EMS;

the EMS transmits a first subscription request message to the Non-RT RIC framework to request to subscribe to the data required by the EMS;

the EMS transmits a first information type registration message to the Non-RT RIC framework to request registration of the information types provided by the EMS; and

the EMS transmits a first information producer registration message to the Non-RT RIC framework to request to register the EMS as an information producer.

14. The system as claimed in claim 12 , wherein the second registration procedure comprises the following actions:

the rApp transmits a second registration request message to the Non-RT RIC framework to request registration of the rApp;

the rApp transmits a second subscription request message to the Non-RT RIC framework to request to subscribe to the data required by the rApp;

the rApp transmits a second information type registration message to the Non-RT RIC framework to request registration of the information types provided by the rApp; and

the rApp transmits a second information producer registration message to the Non-RT RIC framework to request to register the rApp as an information producer.

15. The system as claimed in claim 10 , wherein an IP address of the EMS is included in the first subscription message and the first callback message.

16. The system as claimed in claim 10 , wherein an IP address of the rApp is included in the second subscription message and the second callback message.

17. The system as claimed in claim 10 , wherein the Non-RT RIC framework is connected with the EMS through a service management and orchestration (SMO) internal interface.

18. The system as claimed in claim 10 , wherein the Non-RT RIC framework is connected with the rApp through an R1 interface.

19. A system for communication in service management and orchestration, comprising:

an Element Management System (EMS);

a Non-real time radio access network (RAN) Intelligent Controller (Non-RT RIC) application (rApp); and

a Non-RT RIC framework, coupled to the EMS and the rApp;

wherein the Non-RT RIC framework receives a first subscription message from the EMS, wherein the first subscription message is used to request second data used to run the rApp;

the Non-RT RIC framework transmits a first callback message to the rApp according to the first subscription message to notify the rApp that the EMS requests the second data; and

the rApp transmits the second data to the EMS according to the first callback message,

wherein before the Non-RT RIC framework receives the first subscription message from the EMS, the system further executes the following actions:

the EMS performs a first registration procedure on the Non-RT RIC framework; and

the rApp performs a second registration procedure on the Non-RT RIC framework,

wherein the first registration procedure comprises the following actions:

the EMS transmits a first registration request message to the Non-RT RIC framework to request registration of the EMS;

the EMS transmits a first subscription request message to the Non-RT RIC framework to request to subscribe to the data required by the EMS;

the EMS transmits a first information type registration message to the Non-RT RIC framework to request registration of the information types provided by the EMS; and

the EMS transmits a first information producer registration message to the Non-RT RIC framework to request to register the EMS as an information producer.

20. The system as claimed in claim 19 , wherein the second registration procedure comprises the following actions:

the rApp transmits a second registration request message to the Non-RT RIC framework to request registration of the rApp;

the rApp transmits a second subscription request message to the Non-RT RIC framework to request to subscribe to the data required by the rApp;

the rApp transmits a second information type registration message to the Non-RT RIC framework to request registration of the information types provided by the rApp; and

the rApp transmits a second information producer registration message to the Non-RT RIC framework to request to register the rApp as an information producer.

Assignments (1)

Priority Claims (1)

Continuity (1)

References Cited (15)