Method and system for communication in service management and orchestration

Abstract

A method for communication in service management and orchestration includes: receiving a first subscription message sent by a non-real time RAN Intelligent Controller (Non-RT RIC) framework from a component management system, wherein the first subscription message is used to request a second data required to run a Non-RT RIC application; the Non-real time RAN Intelligent Controller framework sends a first callback message to the Non-RT RIC application according to the first subscription message to notify the component management system to request the second data; and the Non-RT RIC application sends the second data to the component management system according to the first callback message. The present disclosure also relates to a system for communication in service management and orchestration.

Description

Technical Field

[0001] The present disclosure relates to Open Radio Access Network (O-RAN) technology, and more particularly to a method and system for communication in service management and orchestration. Background Art

[0002] "Softwarization of Everything" is a concept that has been widely accepted in the fields of network, computing and communication in recent years. In recent years, the theory of software defined radio has been gradually implemented in mobile communication networks. Software defined cellular networks based on key driving technologies such as "softwarization", "virtualization" and disaggregation of network functions have been regarded as key technologies that can support B5G / 6G for rapid network optimization in the future. The previous 4G network was designed in a black box manner, which will not be able to bear the highly flexible configuration conditions in the future. Many telecom operators have gradually turned their attention to the research and implementation of open radio access networks (Open RAN). The network integration and deployment of hardware and software connecting different telecom suppliers through open user interfaces has attracted much attention. The establishment of the O-RAN Alliance has solved the problem that a single manufacturer's research and development requires a lot of human resources and costs, which undoubtedly provides a great boost to the research and development of Open RAN. The O-RAN Software Community (O-RAN SC) is responsible for developing the open source software modules required for the O-RAN functional definition, and manages all software development related to the radio access network (including technical documentation, testing and integration of each open source software), program code storage, tools and developer integration testing to ensure that the software code is consistent with the open architecture and specifications of the O-RAN Alliance.

[0003] O-RAN is the version of Open RAN standardized by the O-RAN Alliance. O-RAN is built on 3GPP TS 38.401 and includes new features and open, interoperable interfaces. This new RAN architecture approach may bring some benefits related to increased supply chain diversity and reduced deployment costs, while increasing network integration costs and complexity.

[0004] Figure 1is a diagram showing the architecture of the O-RAN system 100. As shown in the figure, the O-RAN system 100 is composed of seven main parts: a service management and orchestration (SMO) framework 110 including a non-real time RAN Intelligent Controller (Non-RT RIC) 1112, a near-real time RAN Intelligent Controller (Near-RT RIC) 120, an O-RAN Central Unit (O-CU) consisting of an O-RAN Central Unit Control Plane 1302 (O-CU-CP) and an O-RAN Central Unit User Plane 1304 (O-CU-UP), an O-RAN Distributed Unit (O-DU) 140, an O-RAN Radio Unit (O-RU) 150, an O-RAN Evolved Node B 160 (O-eNB) and an O-RAN Cloud 170 (O-Cloud).

[0005] The above parts can be connected to each other through the standard interfaces O1, O2, A1, E2, Open FH M-Plane and Open FH CUS-Plane defined by O-RAN. O-CU-CP 1302, O-CU-UP 1304 and O-DU 140 can be connected to each other through interfaces E1, F1-c, F1-u, NG-u, NG-c, X2-u, X2-u, Xn-u, Xn-c defined in 3GPP TR 38.801 "Study on new radio access technology: Radio access architecture and interfaces", 3GPP TR 38.806 "Study of separation of NR ControlPlane (CP) and User Plane (UP) for split option 2", 3GPP TR 38.816 "Study on Central Unit (CU)-Distributed Unit (DU) lower layer split for NR", 3GPP TS 38.47x "series study CU / DU split architecture" and 3GPP TS 38.46x "series study control-user plane separation".

[0006] Figure 2 2 is an architecture diagram showing the SMO framework 200. The SMO framework 200 mainly includes an element management system (EMS) 210 and a non-real time RAN Intelligent Controller (Non-RT RIC) 220. The Non-RT RIC 220 is an internal function of the SMO framework 200 in the O-RAN architecture, and can provide an A1 interface for the near-real time RIC.

[0007] The O1 interface is used to connect the SMO framework 200 with the device end (O-eNB), the O2 interface is used to connect the SMO framework 200 with the O-RAN cloud, and the Open FH M-plane interface is used to connect the SMO framework 200 with the O-RAN wireless unit.

[0008] The Non-RT RIC 220 is composed of a Non-RT RIC framework 222 and Non-RT RIC applications (rApps) 224. The Non-RT RIC 220 exposes required services to the Non-RT RIC applications 224 through the R1 interface.

[0009] However, the current SMO framework 200 does not clearly define how the element management system 210 provides information to the Non-RT RIC 220. Therefore, a method and system for communication in service management and orchestration is needed to define the operation process between the element management system 210 and the Non-RT RIC 220 to make the SMO framework more complete. Summary of the invention

[0010] Therefore, the main purpose of the present disclosure is to provide a method and system for communication in service management and orchestration to make the SMO framework more complete.

[0011] The present disclosure proposes a method for communication in service management and orchestration, including: receiving, by a non-real time RAN Intelligent Controller (Non-RT RIC) framework, a first subscription message transmitted by an Element Management System (EMS), wherein the first subscription message is used to request a second data required to run a Non-RT RIC application (Non-RT RIC application, rAPP); transmitting, by the Non-real time RAN Intelligent Controller framework, a first callback message to the Non-RT RIC application according to the first subscription message to notify the Element Management System to request the second data; and transmitting, by the Non-RT RIC application, the second data to the Element Management System according to the first callback message.

[0012] In some embodiments, before the Non-RT RIC application transmits the second data to the component management system according to the first callback message, the method further includes: the Non-RT RIC application transmits a second subscription message to the non-real-time wireless access network intelligent controller framework, wherein the second subscription message is used to request to obtain a first data required to generate the second data; the non-real-time wireless access network intelligent controller framework transmits a second callback message to the component management system according to the second subscription message; the component management system transmits the first data to the Non-RT RIC application according to the second callback message; and the Non-RT RIC application obtains the second data according to the first data.

[0013] In some embodiments, the method further includes: reading the second data from the component management system, responding and displaying the second data in a web service page.

[0014] In some embodiments, before the non-RT RIC framework receives the first subscription information transmitted by the element management system, the method further includes: performing a first registration procedure with the non-RT RIC framework by the element management system; and performing a second registration procedure with the non-RT RIC framework by the Non-RT RIC application.

[0015] In some embodiments, the first registration procedure includes: the component management system transmits a first registration request message to the non-real-time wireless access network intelligent controller framework to request registration of the component management system; the component management system transmits a first subscription request message to the non-real-time wireless access network intelligent controller framework to request subscription to data required by the component management system; the component management system transmits a first data type registration message to the non-real-time wireless access network intelligent controller framework to request registration of a data type provided by the component management system; and the component management system transmits a first data provider registration message to the non-real-time wireless access network intelligent controller framework to request registration of the component management system as a data provider.

[0016] In some embodiments, the Non-RT RIC application transmits a second registration request message to the Non-RT RIC intelligent controller framework to request registration of the Non-RT RIC application; the Non-RTRIC application transmits a second subscription request message to the Non-RT RIC intelligent controller framework to request subscription to data required by the Non-RT RIC application; the Non-RT RIC application transmits a second data type registration message to the Non-RT RIC intelligent controller framework to request registration of a data type provided by the Non-RT RIC application; and the Non-RT RIC application transmits a second data provider registration message to the Non-RT RIC intelligent controller framework to request registration of the Non-RT RIC application as a data provider.

[0017] In some embodiments, an IP address of the component management system is included in the first subscription information and the first callback information.

[0018] In some embodiments, an IP address of the Non-RT RIC application is included in the second subscription information and the second callback information.

[0019] In some embodiments, the NRAN intelligent controller framework is connected to the element management system via a Service Management and Orchestration (SMO) internal interface.

[0020] In some embodiments, the non-RT RIC intelligent controller framework is connected to the Non-RT RIC application via an R1 interface.

[0021] The present disclosure provides a system for communication in service management and orchestration, the system comprising: an element management system (EMS); a non-real time RAN Intelligent Controller Application (rAPP); and a non-real time RAN Intelligent Controller (Non-RT RIC) framework connected to the element management system and the Non-RT RIC application; wherein the Non-RT RIC framework receives a first subscription message sent by the element management system, wherein the first subscription message is used to request a second data required to run the Non-RT RIC application; the Non-RT RIC framework sends a first callback message to the Non-RT RIC application according to the first subscription message to notify the element management system to request the second data; and the Non-RT RIC application sends the second data to the element management system according to the first callback message. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is an architectural diagram showing the O-RAN system.

[0023] Figure 2 Is an architectural diagram showing the SMO framework.

[0024] Figure 3 It is an architectural diagram showing the SMO framework according to an embodiment of the present disclosure.

[0025] Figure 4 is a flowchart showing a registration procedure of an element management system (EMS) and a Non-RT RIC application to a Non-RT RIC framework according to an embodiment of the present disclosure.

[0026] Figure 5 The flowchart shows a procedure for an element management system (EMS) and a Non-RT RIC application to subscribe to data from a Non-RT RIC framework according to an embodiment of the present disclosure.

[0027] Figure 6 The flowchart shows the data types that can be provided by an element management system (EMS) and a Non-RT RIC application program when registering a service with a Non-RT RIC framework according to an embodiment of the present disclosure.

[0028] Figure 71 is a flowchart showing an element management system (EMS) and a Non-RT RIC application registering with a Non-RT RIC framework as a data provider according to an embodiment of the present disclosure.

[0029] Figure 8 is a flow chart showing the interaction between an element management system (EMS) and a Non-RT RIC application through a Non-RT RIC framework according to an embodiment of the present disclosure.

[0030] Fig. 9 The present invention is a flowchart showing a method for communication in service management and orchestration according to an embodiment of the present disclosure.

[0031] Fig.10 FIG. 1 is a diagram showing an exemplary operating environment for implementing an embodiment of the present disclosure.

[0032] The reference numerals are described as follows:

[0033] 100: O-RAN system

[0034] 110: SMO Framework

[0035] 1112:Non-RT RIC

[0036] 120:Near-RT RIC

[0037] 1302: O-CU-CP

[0038] 1304: O-CU-UP

[0039] 140: O-DU

[0040] 150:O-RU

[0041] 160: O-eNB

[0042] 170: O-RAN Cloud

[0043] 200: SMO Framework

[0044] 210: Component Management System

[0045] 220: Non-RT RIC

[0046] 222: Non-RT RIC framework

[0047] 224: rApps

[0048] 300: SMO Framework

[0049] 310: Component Management System

[0050] 312: Web Services

[0051] 320:Non-RT RIC

[0052] 322: Non-RT RIC framework

[0053] 324: rApps

[0054] 3242: PCI

[0055] 3244: ANR

[0056] 3246: CCO

[0057] 330: Third-party rApps

[0058] 350: SMO internal interface

[0059] 400: Flowchart

[0060] S405, S410, S415, S420: Steps

[0061] 500: Flowchart

[0062] S505, S510, S515, S520: Steps

[0063] 600: Flowchart

[0064] S605, S610, S615, S620: Steps

[0065] 700: Flowchart

[0066] S705, S710, S715, S720: Steps

[0067] 800: Flowchart

[0068] S805, S810, S815, S820, S825, S830, S835, S840, S845, S850, S855, S860, S865, S870, S875, S880, S885, S890: Steps

[0069] 900: Flowchart

[0070] S905, S910, S915: Steps

[0071] 1000: Electronic devices

[0072] 1010: Bus

[0073] 1012: Memory

[0074] 1014: Processor

[0075] 1016: Display components

[0076] 1018: I / O port

[0077] 1020: I / O components

[0078] 1022: Power supply

[0079] O1, O2, A1, E2, Open FH M-Plane, Open FH CUS-Plane, Open FH M-Plane, E1, F1-c, F1-u, NG-u, NG-c, X2-u, X2-u, Xn-u, Xn-c, R1: Interface DETAILED DESCRIPTION

[0080] The disclosed embodiments provide a method and system for communication in service management and orchestration, defining the operation specifications between the element management system and the non-real-time radio access network intelligent controller to further improve the O-RAN function.

[0081] Figure 3 2 is a diagram showing an architecture of a SMO framework 300 according to an embodiment of the present disclosure. The SMO framework 300 mainly includes an element management system (EMS) 310 and a non-real time RAN Intelligent Controller (Non-RT RIC) 320 .

[0082] The element management system 310 provides the function of supporting the fault, configuration, audit, performance and security (FCAPS) of the O-RAN network through the O1 interface.

[0083] The main role of Non-RT RIC 320 is to optimize the intelligent RAN by providing guidance policies, ML (machine learning) model management and information to the Near-RT RTRIC so that the RAN can be optimized under certain conditions. Non-RT RIC 320 can also perform intelligent radio resource management functions in non-real-time intervals (i.e., greater than 1 second). Non-RT RIC 320 can use data analysis and AI / ML training / inference to determine the RAN optimization operations that it can utilize SMO services.

[0084] The Non-RT RIC 320 includes a Non-RT RIC framework 322 and Non-RT RIC applications (rApps) 324, wherein the Non-RT RIC framework 322 exposes the required services to the Non-RT RIC applications 324 through the R1 interface, whether from the Non-RT RIC framework 322 or the SMO framework 300, so that the Non-RT RIC applications 324 can obtain information and trigger operations (for example: assigning a physical layer ID (Physical Identity, PCI) 3242, coverage and capacity optimization (CCO) 3244, Auto Neighbor Relation (ANR) 3246, or operations provided by other third-party Non-RT RIC applications 330) through A1, O1, O2 and OpenFH M-Plane interfaces.

[0085] The component management system 310 can be connected to the web service 312. The web service 312 provides an operator to convey the management intent to the component management system 310 through a human-machine interface (e.g., in the form of a web service). The component management system 310 will convert the received intent into corresponding program instructions and trigger related actions at the bottom layer to achieve the purpose of adjustment and management. The component management system 310 is connected to the Non-RT RIC framework 322 through a Service Management and Orchestration (SMO) internal interface 350.

[0086] It should be noted that the element management system 310, Non-RT RIC framework 322 and Non-RTRIC application 324 in the SMO framework 300 can be implemented as network elements on dedicated hardware (such as a computing device, a server, or a processing circuit of a processor in a computing device or a server), or as a software instance running on dedicated hardware, or as a virtual function installed on an appropriate platform (such as a cloud infrastructure).

[0087] It should be understood that when the component management system 310, the Non-RT RIC framework 322 and the Non-RT RIC application 324 are implemented as dedicated hardware, they can be implemented via any type of electronic device, such as a reference Fig.10 The electronic device 1000 described, Fig.10 shown.

[0088] Figure 4 to Figure 7 It explains the registration procedures of the Element Management System (EMS) and Non-RT RIC Application (rAPP) to the Non-RT RIC framework, the subscription data, the types of data that the registration service can provide, and the process of registering to become a data provider.

[0089] It should be noted that Non-RT RIC applications Figure 4 to Figure 7 The operations performed therein are taken as an example of Coverage and Capacity Optimization (CCO), and a person having ordinary knowledge in the relevant technical field can make appropriate replacements or adjustments according to this embodiment.

[0090] Figure 4 4 is a flowchart 400 showing a registration process of an element management system (EMS) and a Non-RT RIC application to a Non-RT RIC framework according to an embodiment of the present disclosure.

[0091] In step S405, the EMS may send a first registration request message to the Non-RT RIC framework to request registration of the EMS, wherein the first registration request message may be an HTTP request (PUT) message, which may include an application programming interface (API) and an EMS identifier. Figure 4 The first registration request information can be expressed as "PUT / services / EMS").

[0092] In step S410, in response to receiving the first registration request message, the Non-RT RIC framework may send an HTTP reply message to the EMS. In one example, the HTTP reply message may be a 201 OK message.

[0093] In step S415, the Non-RT RIC application may send a second registration request message to the Non-RT RIC framework to request registration of the CCO, wherein the second registration request message may be an HTTP request (PUT) message, which may include an application program interface and a CCO identifier. Figure 4 The second registration request information can be expressed as "PUT / services / CCO".

[0094] In step S420, in response to receiving the second registration request message, the Non-RT RIC framework may send an HTTP reply message to the Non-RT RIC application. In one example, the HTTP reply message may be a 201 OK message.

[0095] Figure 5 5 is a flowchart showing a procedure of an element management system (EMS) and a Non-RT RIC application program subscribing to data from a Non-RT RIC framework according to an embodiment of the present disclosure.

[0096] In step S505, the EMS may send a first subscription request message to the Non-RT RIC framework to request to subscribe to the data required by the EMS, wherein the first subscription request message may be an HTTP request (PUT) message, which may include an application programming interface (API) and data required to run a Non-RT RIC application (e.g., CCO). Figure 5 The first subscription request information can be expressed as "PUT / data-consumer / v1 / info-jobs / cco_output".

[0097] In step S510, in response to receiving the first subscription request message, the Non-RT RIC framework may send an HTTP reply message to the EMS. In one example, the HTTP reply message may be a 201 OK message.

[0098] In step S515, the Non-RT RIC application may send a second subscription request message to the Non-RT RIC framework to request to subscribe to the data required by the application, wherein the second subscription request message may be an HTTP request (PUT) message, which may include an application program interface and data required to run the Non-RT RIC application (e.g., CCO). Figure 5 The second subscription request information can be expressed as "PUT / data-consumer / v1 / info-jobs / cco_input".

[0099] In step S520, in response to receiving the second subscription request message, the Non-RT RIC framework may send an HTTP reply message to the Non-RT RIC application. In one example, the HTTP reply message may be a 201 OK message.

[0100] Figure 6 600 is a flowchart showing the data types that can be provided by an element management system (EMS) and a Non-RT RIC application program when registering a service with a Non-RT RIC framework according to an embodiment of the present disclosure.

[0101] In step S605, the EMS may send a first data type registration message to the Non-RT RIC framework to request registration of the data type (Information Type) that the EMS can provide, wherein the first data type registration message may be an HTTP request (PUT) message, which may include the data type that the EMS can provide. Figure 6 The first data type registration information can be expressed as "PUT / data-producer / v1 / info-types / cco_input".

[0102] In step S610, in response to receiving the first data type registration information, the Non-RT RIC framework may send an HTTP reply message to the EMS. In one example, the HTTP reply message may be a 201 OK message.

[0103] In step S615, the Non-RT RIC application may send a second data type registration message to the Non-RT RIC framework to request to register the data type that the Non-RT RIC application can provide, wherein the second data type registration message may be an HTTP request (PUT) message, which may include the data type that the Non-RT RIC application can provide. Figure 6 The second data type registration information can be expressed as "PUT / data-producer / v1 / info-types / cco_output".

[0104] In step S620, in response to receiving the second data type registration information, the Non-RT RIC framework may send an HTTP reply message to the Non-RT RIC application. In one example, the HTTP reply message may be a 201 OK message.

[0105] Figure 7 700 is a flowchart showing an element management system (EMS) and a Non-RT RIC application registering with a Non-RT RIC framework as a data provider according to an embodiment of the present disclosure.

[0106] In step S705, the EMS may send a first data provider registration message to the Non-RT RIC framework to request to register the EMS as a data provider, wherein the first data provider registration message may be an HTTP request (PUT) message, which may indicate that the EMS is a data provider of the data type in step S605. Figure 7The first data provider registration information can be expressed as "PUT / data-producer / v1 / info-producers / smo_input".

[0107] In step S710, in response to receiving the first data provider registration information, the Non-RT RIC framework may send an HTTP reply message to the EMS. In one example, the HTTP reply message may be a 201 OK message.

[0108] In step S715, the Non-RT RIC application may send a second data provider registration message to the Non-RT RIC framework to request to register the Non-RT RIC application as a data provider, wherein the second data provider registration message may be an HTTP request (PUT) message, which may indicate that the Non-RT RIC application is a data provider of the data type in step S615. Figure 7 The second data type registration information can be expressed as "PUT / data-producer / v1 / info-producers / cco_output".

[0109] In step S720, in response to receiving the second data provider registration information, the Non-RT RIC framework may send an HTTP reply message to the Non-RT RIC application. In one example, the HTTP reply message may be a 201 OK message.

[0110] After EMS and Non-RT RIC applications complete the registration process with the Non-RT RIC framework, subscribe to data, register the data categories that the service can provide, and register to become a data provider, EMS can interact with Non-RT RIC applications in Non-RT RIC.

[0111] Figure 8 800 is a flowchart showing the interaction between an element management system (EMS) and a Non-RT RIC application via a Non-RT RIC framework according to an embodiment of the present disclosure.

[0112] It should be noted that Non-RT RIC applications are Figure 8 The operations performed therein are taken as an example of Coverage and Capacity Optimization (CCO), and a person having ordinary knowledge in the relevant technical field can make appropriate replacements or adjustments according to this embodiment.

[0113] In step S805 , the EMS may receive a signal sent by the web service, wherein the signal instructs the EMS to run a CCO in a Non-RT RIC application.

[0114] In step S810, the EMS sends a first subscription message to the Non-RT RIC framework to request a second data (cco_output) required by the CCO in a Non-RT RIC application, wherein the first subscription message may be an HTTP request (PUT) message and include the IP address of the EMS. Figure 8 The first subscription information can be expressed as "PUT / data-consumer / v1 / info-jobs / cco_output".

[0115] After receiving the first subscription information, the Non-RT RIC framework determines that the provider that can provide the second data is a Non-RT RIC application. In step S815, the Non-RT RIC framework transmits a first callback message to the Non-RT RIC application according to the first subscription information to notify the element management system to request the second data, wherein the first callback message may be an HTTP request (POST) message and include the IP address of the EMS. For example, in Figure 8 The first callback information can be expressed as "POST / data-producer / info_job / cco".

[0116] In step S820 , the Non-RT RIC application determines that it needs a first data (cco_input).

[0117] In step S825, the Non-RT RIC application sends a second subscription message to the Non-RT RIC framework, wherein the second subscription message is used to request to obtain a first data (cco_input) required to generate the second data, wherein the second subscription message may be an HTTP request (PUT) message and include the IP address of the Non-RT RIC application. Figure 8 The second subscription information can be expressed as "PUT / data-consumer / v1 / info-jobs / cco_input".

[0118] After receiving the second subscription information, the Non-RT RIC framework determines that the provider that can provide the first data is the EMS. In step S830, the Non-RT RIC framework transmits a second callback message to the EMS according to the second subscription information to notify the Non-RT RIC application to request the first data, wherein the second callback message may be an HTTP request (POST) message and include the IP address of the Non-RT RIC application. For example, Figure 8 The second callback information can be expressed as "POST / data-producer / info_job / ems".

[0119] In step S835, the EMS transmits the first data to the Non-RT RIC application according to the IP address of the Non-RT RIC application in the second callback information, wherein the first data may be an HTTP (POST) message. Figure 8 The first data can be expressed as "POST / job_result / cco_input".

[0120] In step S840, the Non-RT RIC application writes the first data.

[0121] When the Non-RT RIC application finishes writing the first data, in step S845, the Non-RT RIC application may send an HTTP reply message to the EMS in response to the first data received in step S835. In one example, the HTTP reply message may be a 200OK message.

[0122] In step S850, in response to receiving the second callback message in step S830, the EMS may send an HTTP reply message to the Non-RTRIC framework. In one example, the HTTP reply message may be a 200 OK message.

[0123] In step S855, in response to receiving the second subscription information in step S825, the Non-RT RIC framework may send an HTTP reply message to the Non-RT RIC application. In one example, the HTTP reply message may be a 200 OK message.

[0124] In step S860 , the Non-RT RIC application reads the first data and performs CCO to generate second data.

[0125] In step S865, the Non-RT RIC application sends the second data to the EMS according to the IP address of the EMS in the first callback information, wherein the second data may be an HTTP (POST) message. Figure 8 The second data can be expressed as "POST / job_result / cco_output".

[0126] In step S870, the EMS writes the second data.

[0127] After the EMS finishes writing the second data, in step S875, the EMS may send an HTTP reply message to the Non-RT RIC application in response to the second data received in step S865. In one example, the HTTP reply message may be a 200 OK message.

[0128] In step S880, in response to receiving the first callback information in step S815, the Non-RT RIC application may send an HTTP reply message to the Non-RT RIC framework. In one example, the HTTP reply message may be a 200 OK message.

[0129] In step S885, in response to receiving the first subscription information in step S810, the Non-RT RIC framework may send an HTTP reply message to the EMS. In one example, the HTTP reply message may be a 200 OK message.

[0130] In step S890 , the EMS reads the second data generated by the CCO executing the first data, and responds and displays the second data in the web service page of S805 .

[0131] Fig. 9 is a flow chart showing a method 900 for communication in service management and orchestration according to an embodiment of the present disclosure. The method may be performed as follows Figure 3 The component management system 310, the Non-RT RIC framework 322 and the Non-RT RIC application 324 are shown to be executed.

[0132] In step S905, a first subscription message sent by a component management system is received by a non-RT RIC intelligent controller framework, wherein the first subscription message is used to request a second data required to run a Non-RT RIC application, and the first subscription message includes an IP address of the component management system.

[0133] In step S910, the non-RT RIC framework transmits a first callback message to the Non-RT RIC application according to the first subscription message to notify the element management system to request the second data, wherein the first callback message includes the IP address of the element management system.

[0134] In step S915 , the Non-RT RIC application transmits the second data to the component management system according to the first callback information.

[0135] In one embodiment, the NRAN intelligent controller framework is connected to the element management system via a service management and orchestration internal interface.

[0136] As described above, the method and system for communication in service management and orchestration disclosed in the present invention connect the EMS and the Non-RT RIC framework through the internal interface of the service management and orchestration, and define the interaction specifications between the EMS, the Non-RT RIC framework and the Non-RT RIC application, thereby achieving the purpose of transmitting data between the EMS and the Non-RT RIC application in the SMO framework.

[0137] For the embodiments of the present invention that have been described, the following describes an exemplary operating environment in which the embodiments of the present invention can be implemented. Fig.10 , Fig.10 1000 is an exemplary operating environment for implementing embodiments of the present invention, which may generally be referred to as electronic device 1000. Electronic device 1000 is merely an example of a suitable computing environment and is not intended to suggest any limitation on the scope of use or functionality of the present invention. Electronic device 1000 should not be interpreted as having any dependency or requirement relating to any one or combination of illustrated elements.

[0138] The present invention may be implemented in computer program code or machine-usable instructions, which may be computer executable instructions of a program module, which is executed by a computer or other machine, such as a personal digital assistant or other portable device. Generally speaking, a program module includes routines, programs, objects, components, data structures, etc. A program module refers to a program code that performs a specific task or implements a specific abstract data type. The present invention may be implemented in a variety of system configurations, including portable devices, consumer electronics, general-purpose computers, more specialized computing devices, etc. The present invention may also be implemented in a distributed computing environment, processing devices connected by a communication network.

[0139] refer to Fig.10Electronic device 1000 includes bus 1010 that directly or indirectly couples the following devices, memory 1012, one or more processors 1014, one or more display elements 1016, input / output (I / O) ports 1018, input / output (I / O) elements 1020, and an illustrative power supply 1022. Bus 1010 represents an element that can be one or more buses (e.g., an address bus, a data bus, or a combination thereof). Although Fig.10 For simplicity, the various blocks are shown with lines. Actually, the boundaries of the various elements are not specific. For example, the presentation elements of the display device may be regarded as I / O elements; and the processor may have a memory.

[0140] The electronic device 1000 generally includes various computer-readable media. Computer-readable media can be any available media that can be accessed by the electronic device 1000, including both volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, computer-readable media can include computer storage media and communication media. Computer-readable media also includes volatile and non-volatile media, removable and non-removable media implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include but are not limited to random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage device, magnetic disk, magnetic disk storage device or other magnetic storage device, or any other media that can be used to store the desired information and can be accessed by the electronic device 1000. Computer storage media itself does not include signals.

[0141] Communication media generally contain computer readable instructions, data structures, program modules or other data in the form of modular data signals such as carrier waves or other transmission mechanisms, and include any information delivery media. The term "modular data signal" refers to a signal that has one or more characteristics set or changed in a manner that encodes information in the signal. By way of example and not limitation, communication media include wired media such as a wired network or direct wired connection and wireless media such as audio, radio frequency, infrared and other wireless media. Combinations of the above media are included within the scope of computer readable media.

[0142] Memory 1012 includes computer storage media in the form of volatile and non-volatile memory. Memory can be removable, non-removable, or a combination of the two. Exemplary hardware devices include solid-state memory, hard disk drives, optical disk drives, etc. Electronic device 1000 includes one or more processors that read data from entities such as memory 1012 or I / O components 1020. Display component 1016 displays data indications to a user or other device. Exemplary display components include display devices, speakers, printing components, vibration components, etc.

[0143] I / O port 1018 allows electronic device 1000 to be logically connected to other devices including I / O element 1020, some of which are built-in devices. Exemplary elements include microphones, rockers, game consoles, satellite dish signal receivers, scanners, printers, wireless devices, etc. I / O element 1020 can provide a natural user interface for processing gestures, sounds or other physiological inputs generated by the user. In some examples, these inputs can be transmitted to a suitable network element for further processing. Electronic device 1000 can be equipped with a depth camera, such as a stereo camera system, an infrared camera system, an RGB camera system and a combination of these systems to detect and identify objects. In addition, electronic device 1000 can be equipped with a sensor (e.g., radar, lidar) to periodically sense the surrounding environment within a sensing range, and generate sensor information indicating that it is associated with the surrounding environment. Furthermore, electronic device 1000 can be equipped with an accelerometer or gyroscope that detects motion. The output of the accelerometer or gyroscope can be provided to the electronic device 1000 for display.

[0144] In addition, the processor 1014 in the electronic device 1000 may also execute the programs and instructions in the memory 1012 to present the actions and steps described in the above embodiments, or other descriptions of the contents in the specification.

Claims

1. A method for communication in service management and orchestration, the method comprising: Receiving, by a non-real-time wireless access network intelligent controller framework, a first subscription message transmitted by a component management system, wherein the first subscription message is used to request a second data required to run a non-real-time wireless access network intelligent controller application; The non-real-time wireless access network intelligent controller framework transmits a first callback message to the non-real-time wireless access network intelligent controller application according to the first subscription message, so as to notify the element management system to request the second data; and The non-real-time wireless access network intelligent controller application transmits the second data to the component management system according to the first callback information.

2. The method of claim 1, wherein before the non-real-time wireless access network intelligent controller application sends the second data to the element management system according to the first callback message, the method further comprises: The non-real-time wireless access network intelligent controller application sends a second subscription message to the non-real-time wireless access network intelligent controller framework, wherein the second subscription message is used to request to obtain a first data required to generate the second data; The non-real-time wireless access network intelligent controller framework transmits a second callback message to the component management system according to the second subscription message; The component management system transmits the first data to the non-real-time wireless access network intelligent controller application according to the second callback information; and The non-real-time wireless access network intelligent controller application obtains the second data according to the first data.

3. The method of claim 1, further comprising: The second data is read by the component management system, and is responded and displayed in a web service page.

4. The method of claim 1, wherein before the non-real-time wireless access network intelligent controller framework receives the first subscription information transmitted by the element management system, the method further comprises: The component management system performs a first registration procedure with the non-real-time wireless access network intelligent controller framework; as well as A second registration procedure is performed by the non-real-time wireless access network intelligent controller application to the non-real-time wireless access network intelligent controller framework.

5. The method of claim 4, wherein the first registration procedure comprises: The component management system transmits a first registration request message to the non-real-time wireless access network intelligent controller framework to request registration of the component management system; The component management system transmits a first subscription request message to the non-real-time wireless access network intelligent controller framework to request to subscribe to the data required by the component management system; The component management system transmits a first data type registration message to the non-real-time wireless access network intelligent controller framework to request registration of the data type provided by the component management system; and The component management system transmits a first data provider registration message to the non-real-time wireless access network intelligent controller framework to request the component management system to register as a data provider.

6. The method of claim 4, wherein the second registration procedure comprises: The non-real-time wireless access network intelligent controller application sends a second registration request message to the non-real-time wireless access network intelligent controller framework to request registration of the non-real-time wireless access network intelligent controller application; The non-real-time wireless access network intelligent controller application sends a second subscription request message to the non-real-time wireless access network intelligent controller framework to request to subscribe to the data required by the non-real-time wireless access network intelligent controller application; The non-real-time wireless access network intelligent controller application sends a second data type registration message to the non-real-time wireless access network intelligent controller framework to request registration of the data type provided by the non-real-time wireless access network intelligent controller application; and The non-real-time wireless access network intelligent controller application sends a second data provider registration message to the non-real-time wireless access network intelligent controller framework to request to register the non-real-time wireless access network intelligent controller application to become a data provider.

7. The method of claim 1, wherein an IP address of the component management system is included in the first subscription information and the first callback information.

8. The method of claim 2, wherein an IP address of the non-real-time wireless access network intelligent controller application is included in the second subscription information and the second callback information.

9. The method of claim 1, wherein the non-real-time wireless access network intelligent controller framework is connected to the element management system through a service management and orchestration internal interface.

10. The method of claim 1, wherein the NRAN intelligent controller framework is connected to the NRAN intelligent controller application via an R1 interface.

11. A system for communication in service management and orchestration, the system comprising: - Component management system; A non-real-time wireless access network intelligent controller application; as well as A non-real-time wireless access network intelligent controller framework, connected to the above-mentioned component management system and the above-mentioned non-real-time wireless access network intelligent controller application; The non-real-time wireless access network intelligent controller framework receives a first subscription message sent by the element management system, wherein the first subscription message is used to request a second data required to run the non-real-time wireless access network intelligent controller application; The non-real-time wireless access network intelligent controller framework transmits a first callback message to the non-real-time wireless access network intelligent controller application according to the first subscription message to notify the element management system to request the second data; and The non-real-time wireless access network intelligent controller application transmits the second data to the component management system according to the first callback information.

12. The system of claim 11, wherein before the non-real-time wireless access network intelligent controller application sends the second data to the element management system according to the first callback message, the system further executes: The non-real-time wireless access network intelligent controller application sends a second subscription message to the non-real-time wireless access network intelligent controller framework, wherein the second subscription message is used to request to obtain a first data required to generate the second data; The non-real-time wireless access network intelligent controller framework transmits a second callback message to the component management system according to the second subscription message; The component management system transmits the first data to the non-real-time wireless access network intelligent controller application according to the second callback information; and The non-real-time wireless access network intelligent controller application obtains the second data according to the first data.

13. The system of claim 11, further comprising: The component management system reads the second data, responds and displays it in a web service page.

14. The system of claim 11, wherein before the non-real-time wireless access network intelligent controller framework receives the first subscription information transmitted by the element management system, the system further executes: The component management system performs a first registration procedure with the non-real-time wireless access network intelligent controller framework; and A second registration procedure is performed by the non-real-time wireless access network intelligent controller application to the non-real-time wireless access network intelligent controller framework.

15. The system of claim 14, wherein the first registration procedure comprises: The component management system transmits a first registration request message to the non-real-time wireless access network intelligent controller framework to request registration of the component management system; The component management system transmits a first subscription request message to the non-real-time wireless access network intelligent controller framework to request to subscribe to the data required by the component management system; The component management system transmits a first data type registration message to the non-real-time wireless access network intelligent controller framework to request registration of the data type provided by the component management system; and The element management system transmits a first data provider registration message to the non-real-time wireless access network intelligent controller framework to request to register the element management system as a data provider.

16. The system of claim 14, wherein the second registration procedure comprises: The non-real-time wireless access network intelligent controller application sends a second registration request message to the non-real-time wireless access network intelligent controller framework to request registration of the non-real-time wireless access network intelligent controller application; The non-real-time wireless access network intelligent controller application sends a second subscription request message to the non-real-time wireless access network intelligent controller framework to request to subscribe to the data required by the non-real-time wireless access network intelligent controller application; The non-real-time wireless access network intelligent controller application sends a second data type registration message to the non-real-time wireless access network intelligent controller framework to request registration of the data type provided by the non-real-time wireless access network intelligent controller application; and The non-real-time wireless access network intelligent controller application sends a second data provider registration message to the non-real-time wireless access network intelligent controller framework to request to register the non-real-time wireless access network intelligent controller application to become a data provider.

17. The system of claim 11, wherein an IP address of the component management system is included in the first subscription information and the first callback information.

18. The system of claim 12, wherein an IP address of the non-real-time wireless access network intelligent controller application is included in the second subscription information and the second callback information.

19. The system of claim 11, wherein the non-real-time wireless access network intelligent controller framework is connected to the element management system through a service management and orchestration internal interface.

20. The system of claim 11, wherein the NRAN intelligent controller framework is connected to the NRAN intelligent controller application via an R1 interface.

Images