CN114449459A - Message transmission method, platform function application function - Google Patents

Abstract

Embodiments of the present invention provide a message transmission method, a platform function, and an application function. The method includes: performing message interaction with at least one application function through a near real-time wireless intelligent control application program interface included in the platform function; the embodiment of the present invention The communication between the platform function and the application function adopts a unified near-real-time wireless intelligent control application program interface, and the platform function can handle the external input or output related E2, A1 and O1 interfaces; the application function only needs to support the near-real-time wireless intelligent control application The program interface does not need to support the E2, A1 and O1 interfaces; the general protocol processing part of the E2, A1 and O1 interfaces is only processed once by the platform function, and the application function does not need to be processed repeatedly. And the conflict resolution function in the platform function only needs to parse the E2 information output by the application function based on the near real-time wireless intelligent control application program interface, and does not need to parse the E2AP and E2SM information separately, which improves the processing efficiency.

Description

Message transmission method, platform function application function

technical field

The present invention relates to the technical field of communication, in particular to a message transmission method, platform function and application function.

Background technique

Open and Intelligent Radio Access Network (O-RAN) Compared with the existing radio access network architecture and functions, O-RAN proposes a wireless intelligent controller. The goal is to endow wireless networks with a certain level of intelligence by introducing wireless big data, artificial intelligence technology and an open platform for wireless capabilities, and to use big data and artificial intelligence (AI) capabilities to flexibly and efficiently support complex and diverse vertical industry businesses and slicing To meet the requirements, realize efficient and automated network management and efficient utilization of spectrum resources in a complex networking environment, improve wireless network performance and reduce wireless network energy consumption while reducing the complexity of existing wireless resource management and scheduling algorithms.

Wireless intelligent controllers include non-real-time wireless intelligent controllers and near real-time wireless intelligent controllers. From the perspective of management, the near real-time wireless intelligent controller receives information from the network management and the non-real-time wireless intelligent controller, and feeds back relevant information. In terms of network functions, at present, near real-time wireless intelligent controllers are connected to base stations or base station subsystems, send configuration or control information, and receive measurements and other information provided by base station or base station subsystem functions.

Near real-time RAN intelligence controller (Near-RT RIC) plays an important role in two aspects: one is to receive data from the base station or base station subsystem according to the available information and scene requirements, and send The second is to provide near real-time wireless services for functions other than wireless network functions according to the available information and scenario requirements. In terms of deployment form, Near-RT RICs are available in two types: stand-alone and non-stand-alone. The so-called stand-alone means that the Near-RT RIC is an independent device form independent of the base station equipment; non-stand-alone means that the Near-RT RIC and the base station are combined to form a device. For use cases such as allocation, monitoring, control and management of wireless resources, it can complete the near real-time information collection and control delivery of wireless access network. The near real-time wireless intelligent controller will provide the basic platform functions to support the deployment and operation of the application. The so-called application refers to an xApp that solves a certain problem for a certain application scenario, such as load balancing, load prediction, video key quality indicator (Key Quality Indicators, KQI) prediction, quality of service (Quality of Service, QoS) and quality of experience (Quality) of Experience, QoE) optimization, etc.

Therefore, the E2 interface between the near real-time wireless intelligent controller and the base station (or base station subsystem) is oriented to telecommunication equipment, and the definition of its process and information element refers to the Ng and F1 interface methods, and the goal is to open the base station as much as possible. Near real-time information data and control capabilities. xApp is a problem oriented to a specific application scenario. It only needs to know the input and output information of the problem in charge of the previous E2 issue, and does not need to know all the information on the E2 interface between the near real-time wireless intelligent controller and the base station. Moreover, the near real-time wireless intelligent controller and the base station E2 interface are defined in the form of E2AP (E2application protocol) and E2SM (E2 service model). E2AP provides an interface framework, and some message fields of E2AP messages are defined by E2SM . At present, both E2AP and E2SM use ASN.1 as the abstract syntax and serialization (the process of converting structured data into bitstream), and subsequent E2SM may also use methods other than ASN.1 for abstract syntax expression and serialization. At the same time, xApp also needs part of the information transmitted on the O1 and A1 interfaces to implement the policies of A1 or the configuration information of O1.

The prior art has at least the following problems:

1) xApp is an application program oriented to specific needs, focusing on specific algorithms, while in the prior art solution, xApp needs to parse and encapsulate carrier-class equipment interfaces such as E2, A1, and/or O1, which results in a large overhead for processing additional interfaces of xApp. .

2) Since the E2, A1 and O1 interfaces are defined to meet the needs of all xApps, the extension or update of the E2, A1 and O1 interfaces due to new xApps will affect the service interruption or upgrade of the existing xApps. Existing extensions or updates of other xApps may also cause service interruptions or forced synchronous upgrades of xApps that do not require extensions or updates.

3) Since the definition of interfaces such as E2 and A1 does not include xApp-related information, that is, xApp is invisible to the non-real-time wireless intelligent controller and base station side, so the platform needs to process the messages of interfaces such as E2 and A1, and send them to A suitable xApp. This feature of the platform means that the platform must process E2, A1, and O1 messages before it can determine which xApp or xApps to send to. In the existing solution, xApp directly uses E2, A1 and O1 interfaces, and xApp also needs to process E2, A1 and O1 messages. Therefore, the messages on the same E2, A1 and O1 in the existing solution are processed once by the platform and xApp each within Near-RT, especially for the general protocol processing part of the interface, the platform and xApp process these exactly the same , then this part of the two processing is completely repeated.

4) In the prior art solution, when different xApps require the same input data, two identical messages will be generated on the E2 interface, and two copies of data will be reported, resulting in poor interaction efficiency and redundancy in transmission information. For example, xApp1 requires the number of activated users in the cell connected to the near real-time wireless intelligent controller, and xApp2 also requires the number of activated users in the cell connected to the near real-time wireless intelligent controller. In the existing solution, two xApps will generate two similar E2 messages. As a result, the base station needs to parse two messages and report the number of cell activated users twice through the E2 interface.

5) For the platform function, the conflict mitigation function in the platform needs to decode the E2 information output by xApp twice, one is the decoding of E2AP, and the other is the decoding of E2SM. After the conflict resolution optimizes and modifies the output information, the newly generated optimized message needs to be encapsulated again according to the E2 interface definition. Therefore, xApp directly parses and encapsulates E2 interface messages, which leads to additional message parsing overhead for the platform conflict resolution function, and performs 2 E2 message encapsulation in the case of optimizing and modifying conflict resolution, which is inefficient and may not be able to meet the near real-time control loop. road requirements.

SUMMARY OF THE INVENTION

The purpose of the embodiments of the present invention is to provide a message transmission method and a platform function application function, so as to solve the problems of high interface processing overhead, passive upgrade service interruption, E2/A1/O1 application function in the near real-time wireless intelligent controller in the prior art The common interface protocol handles the problems of duplication, E2 interface subscription data duplication and conflict resolution inefficiency.

In order to solve the above problem, an embodiment of the present invention provides a message transmission method, which is applied to the platform function of a near real-time wireless intelligent controller, including:

Perform message interaction with at least one application function through a near real-time wireless intelligent control application program interface;

Wherein, the at least one application function is an application function inside the near real-time wireless intelligent controller.

Wherein, the near real-time wireless intelligent control application program interface includes at least one of the following:

a first API associated with the E2 interface;

a second API associated with the A1 interface;

a third application program interface related to the management function interface;

A fourth API related to the shared data layer.

Wherein, performing message interaction with at least one application function through the near real-time wireless intelligent control application program interface included in the platform function includes:

receiving a first message transmitted by at least one application function through the near real-time wireless intelligent control API;

The first message is processed, and the first message is mapped to an E2 interface, an A1 interface, a management function interface, an internal interface or an upper-layer service interface.

Wherein, the first message includes:

the identifier of the application function;

The message body of the first message.

Wherein, the first message further includes at least one of the following:

the identification of the platform function;

API version number;

message type.

Wherein, after receiving the first message transmitted by at least one application function through the near real-time wireless intelligent control application program interface, the method further includes;

Send a first response message to the application function, where the first response message includes:

the identifier of the application function;

API version number;

The message body of the first response message.

Wherein, the first response message further includes:

message type.

Wherein, the first message is at least one of the following:

A1 interface related messages;

E2 interface related messages;

Management function interface related messages;

Internal logic messages for near real-time wireless smart controllers.

Wherein, the messages related to the A1 interface include: A1 messages that are not encapsulated by the A1 interface;

and / or,

The messages related to the management function interface include: O1 messages that are not encapsulated by the O1 interface;

and / or,

The E2 interface related message includes at least one of the following:

E2 messages that are not encapsulated by the E2AP interface;

E2SM encapsulated message;

Messages in non-E2SM encapsulated form.

Wherein, when the request message body of the first message is data in the form of E2SM encapsulation, the first message further includes:

E2SM identification, the E2SM identification is used to assist subscription management and conflict resolution.

Wherein, when the request message body of the first message is non-E2SM encapsulated data, the messages transmitted on the near real-time wireless intelligent control application program interface all adopt a unified interface abstract syntax and serialization.

Wherein, performing message interaction with at least one application function through the near real-time wireless intelligent control application program interface included in the platform function includes:

Obtaining external input or the second message transmitted on at least one of the E2 interface, the A1 interface and the O1 interface generated inside the near real-time wireless intelligent controller;

The second message is processed to generate a third message that can be transmitted in the near real-time wireless intelligent control application program interface, and is transmitted to the corresponding application function.

Wherein, when the second message is a message of the A1 interface or the O1 interface, the third message includes:

the identifier of the application function;

API version number;

The message body of the third message.

Wherein, the third message further includes at least one of the following:

the address of the conflict resolution service;

the address of the database service;

The application function can obtain a list of network devices for data or control.

Wherein, when the second message is an E2 interface message, the message body of the third message includes:

E2SM encapsulated message;

Messages in non-E2SM encapsulation form; messages in non-E2SM encapsulation form use the same abstract syntax and serialization as the near real-time wireless intelligent control application program interface.

The embodiment of the present invention also provides a message transmission method, which is applied to the application function inside the near real-time wireless intelligent controller, including:

Through the near-real-time wireless intelligent control application program interface, message interaction with the platform function inside the near-real-time wireless intelligent controller is carried out.

Wherein, the near real-time wireless intelligent control application program interface includes at least one of the following:

a first API associated with the E2 interface;

a second API associated with the A1 interface;

a third application program interface related to the management function interface;

A fourth API related to the shared data layer.

Wherein, the method also includes:

Through an open interface with other application functions inside the near real-time wireless intelligent controller, message interaction is performed with the other application functions.

Wherein, when the application function and other application functions perform message interaction through the second open interface, the exchanged messages include:

message type, used to indicate that the message is an interaction message between application functions;

Identification of other application functions.

Among them, through the near-real-time wireless intelligent control application program interface, message interaction with the platform functions inside the near-real-time wireless intelligent controller, including:

The first message is transmitted to the platform function through the near real-time wireless intelligent control application program interface; the platform function processes the first message and maps the first message to the E2 interface, A1 interface, Management function interface, internal interface or upper-layer business interface.

Wherein, the first message includes:

the identifier of the application function;

The message body of the first message.

Wherein, the first message further includes at least one of the following:

the identification of the platform function;

API version number;

message type.

Wherein, after transmitting the first message to the platform function through the near real-time wireless intelligent control application program interface, the method further includes:

Receive a first response message sent by the platform function, where the first response message includes:

the identifier of the application function;

API version number;

The message body of the first response message.

Wherein, the first response message further includes:

message type.

Wherein, the first message is at least one of the following:

A1 interface related messages;

E2 interface related messages;

Management function interface related messages;

Internal logic messages for near real-time wireless smart controllers.

Wherein, the messages related to the A1 interface include: A1 messages that are not encapsulated by the A1 interface;

and / or,

The messages related to the O1 interface of the management function include: O1 messages that are not encapsulated by the O1 interface;

and / or,

The E2 interface related message includes at least one of the following:

E2 messages that are not encapsulated by the E2AP interface;

E2SM encapsulated message;

Messages in non-E2SM encapsulated form.

Wherein, when the request message body of the first message is data in the form of E2SM encapsulation, the first message further includes:

E2SM identification, the E2SM identification is used to assist subscription management and conflict resolution.

Wherein, when the request message body of the first message is non-E2SM encapsulated data, the messages transmitted on the near real-time wireless intelligent control application program interface all adopt a unified interface abstract syntax and serialization.

Among them, through the near-real-time wireless intelligent control application program interface, message interaction with the platform functions inside the near-real-time wireless intelligent controller, including:

A third message transmitted by the platform function via the near real-time wireless intelligent control API is received.

Wherein, the third message includes:

the identifier of the application function;

API version number;

The message body of the third message.

Wherein, the third message further includes at least one of the following:

the address of the conflict resolution service;

the address of the database service;

The application function can obtain a list of network devices for data or control.

Wherein, the message body of the third message includes:

E2SM encapsulated message;

Messages in non-E2SM encapsulation form; messages in non-E2SM encapsulation form use the same abstract syntax and serialization as the near real-time wireless intelligent control application program interface.

The embodiment of the present invention also provides a message transmission device, which is applied to the platform function of the near real-time wireless intelligent controller, including:

a first interaction module, used for a near real-time wireless intelligent control application program interface, to perform message interaction with at least one application function;

Wherein, the at least one application function is an application function inside the near real-time wireless intelligent controller.

The embodiment of the present invention also provides a platform function, the platform function is a platform function of a near real-time wireless intelligent controller, including a processor and a transceiver, the transceiver receives and sends data under the control of the processor, the The processor is used to do the following:

Perform message interaction with at least one application function through a near real-time wireless intelligent control application program interface;

Wherein, the at least one application function is an application function inside the near real-time wireless intelligent controller.

Wherein, the near real-time wireless intelligent control application program interface includes at least one of the following:

a first API associated with the E2 interface;

a second API associated with the A1 interface;

a third application program interface related to the management function interface;

A fourth API related to the shared data layer.

The embodiment of the present invention also provides a message transmission device, which is applied to the application functions inside the near real-time wireless intelligent controller, including:

The second interaction module is used for message interaction with the platform function inside the near-real-time wireless intelligent controller through the near-real-time wireless intelligent control application program interface.

The embodiment of the present invention also provides an application function, the application function is an application function inside the near real-time wireless intelligent controller, including a processor and a transceiver, the transceiver receives and sends data under the control of the processor, so The processor described is used to perform the following actions:

Through the near-real-time wireless intelligent control application program interface, message interaction with the platform function inside the near-real-time wireless intelligent controller is carried out.

Wherein, the processor is further configured to perform the following operations:

Through an open interface with other application functions inside the near real-time wireless intelligent controller, message interaction is performed with the other application functions.

Wherein, when the application function and other application functions perform message interaction through the open interface, the exchanged messages include:

message type, used to indicate that the message is an interaction message between application functions;

Identification of other application functions.

Embodiments of the present invention further provide a near real-time wireless intelligent controller, including the platform function as described above and at least one application function as described above.

An embodiment of the present invention further provides a communication device, including a memory, a processor, and a program stored on the memory and executable on the processor, and the processor implements the above message when executing the program transfer method.

Embodiments of the present invention further provide a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, implements the steps in the above message transmission method.

The above-mentioned technical scheme of the present invention has at least the following beneficial effects:

In the message transmission method and the platform function application function of the embodiments of the present invention, the communication between the platform function and the application function adopts a unified near real-time wireless intelligent control application program interface, and the platform function can process the external input or output related E2, A1 and O1 interface, according to the interaction needs with the application function, the platform function generates the message transmitted in the near real-time wireless intelligent control API; the application function only needs to support the near real-time wireless intelligent control API, and does not need to support E2, A1 and O1 interface; the general protocol processing part of the interface of E2, A1 and O1 is only processed once by the platform function, and the application function does not need to be processed repeatedly. And the conflict resolution function in the platform function only needs to parse the E2 information output by the application function based on the near real-time wireless intelligent control application program interface, and does not need to parse the E2AP and E2SM information separately, which improves the processing efficiency.

Description of drawings

1 shows a schematic structural diagram of a near real-time wireless intelligent controller provided by an embodiment of the present invention;

FIG. 2 shows one of the schematic diagrams of the steps of a message transmission method provided by an embodiment of the present invention;

3 shows one of the schematic diagrams of the internal interaction of the near real-time wireless intelligent controller in the message transmission method provided by the embodiment of the present invention;

4 shows the second schematic diagram of the internal interaction of the near real-time wireless intelligent controller in the message transmission method provided by the embodiment of the present invention;

5 shows the third schematic diagram of the internal interaction of the near real-time wireless intelligent controller in the message transmission method provided by the embodiment of the present invention;

FIG. 6 shows the second schematic diagram of the steps of a message transmission method provided by an embodiment of the present invention;

FIG. 7 shows one of the schematic structural diagrams of a message transmission apparatus provided by an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a platform function provided by an embodiment of the present invention;

FIG. 9 shows the second schematic structural diagram of a message transmission apparatus provided by an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of an application function provided by an embodiment of the present invention.

Detailed ways

In order to make the technical problems, technical solutions and advantages to be solved by the present invention more clear, the following will be described in detail with reference to the accompanying drawings and specific embodiments.

As shown in FIG. 1 and FIG. 2 , an embodiment of the present invention provides a message transmission method, which is applied to a platform function of a near real-time wireless intelligent controller, including:

Step 21, through a near real-time wireless intelligent control application program interface, perform message interaction with at least one application function;

Wherein, the at least one application function is an application function inside the near real-time wireless intelligent controller.

In the embodiment of the present invention, the near-real-time wireless intelligent controller provides an open interface (ie, a near-real-time wireless intelligent control application program interface), which allows hosting the application functions of the near-real-time wireless intelligent controller and the application functions of third parties.

The platform function of the near real-time wireless intelligent controller (Near-RT RIC) provided by the embodiment of the present invention completes the processing of the E2 interface function, the A1 interface function and the O1 interface function; that is, the platform function can analyze the E2 interface function, the A1 interface function and the O1 interface function Messages on interface functions. For the E2 interface function, A1 interface function and O1 interface function generated inside the near real-time wireless intelligent controller, the platform function generates interactive messages on the corresponding interface according to the definition of each interface, and the platform function provides a unified near real-time wireless interface to all application functions. Smart Control API.

As an optional embodiment, the near real-time wireless intelligent control application program interface includes at least one of the following:

a first API associated with the E2 interface;

a second API associated with the A1 interface;

a third application program interface related to the management function interface;

A fourth API related to the shared data layer.

In the embodiment of the present invention, the message transmitted by the application function-oriented near real-time wireless intelligent control application program interface at least includes the identification of the application function, and also needs to include the identification of the platform function when the application function interacts with the platform function. If the application function only supports interaction with a unique platform function, the identification of the platform function may be completed during initialization, and the interaction may not carry the identification of the platform function if the subsequent platform does not change.

Because Near-RT RIC supports E2, A1, and O1, as well as multiple types of message interaction such as internal subscription management and conflict resolution, the near real-time wireless intelligent control application program interface of the embodiment of the present invention supports interactive message classification, so as to facilitate the message Map to different interfaces in platform capabilities. For example, it can be divided into three categories, namely E2 related messages, A1 related messages and management (or O1) related messages. It may also be necessary to further differentiate the logical functions within the Near-RT RIC, such as subscription management for removing duplicate subscriptions, conflict resolution for resolving conflicts between application functions, database functions for data access, and internal message transmission The message type can be extended to support the processing message type supported by other logical function types.

As an optional embodiment, step 21 includes:

receiving a first message transmitted by at least one application function through the near real-time wireless intelligent control API;

The first message is processed, and the first message is mapped to an E2 interface, an A1 interface, a management function interface, an internal interface or an upper-layer service interface.

For example, the first message is a subscription request message; that is, the application function sends a request to the platform function to subscribe to related data, and the first message includes:

The identifier of the application function; the identifier may be a uniform resource identifier (Uniform ResourceIdentifier, URI) or a uniform resource locator (Uniform Resource Locator, URL) or the name of the application function, which is in the form of characters. It can also be a number number within a certain range, in this case it is an integer form;

The message body of the first message.

Optionally, the first message further includes at least one of the following:

The identifier of the platform function; the identifier may be a uniform resource identifier (Uniform ResourceIdentifier, URI) or a uniform resource locator (Uniform Resource Locator, URL), which is in the form of characters. It can also be a number number within a certain range, in this case it is an integer form;

API version number (Version);

message type.

As shown in Table 1, the first message includes the following information:

Table 1

Further, in the above-mentioned embodiment of the present invention, after receiving the first message transmitted by at least one application function through the near real-time wireless intelligent control application program interface, the method further includes;

Send a first response message to the application function, where the first response message includes:

The identifier of the application function; the identifier can be a uniform resource identifier (Uniform ResourceIdentifier, URI) or a uniform resource locator (Uniform Resource Locator, URL) or the name of the xApp, in these cases it is in the form of characters. It can also be a number number within a certain range, in this case it is an integer form;

The message body of the first response message.

Optionally, the first response message further includes at least one of the following:

message type;

The API version number (Version).

As shown in Table 2, the first response message includes the following information:

Table 2

As an optional embodiment, the first message is at least one of the following:

A1 interface related messages;

E2 interface related messages;

Management function interface related messages;

Internal logic messages for near real-time wireless smart controllers.

Wherein, the messages related to the A1 interface include: A1 messages that are not encapsulated by the A1 interface;

and / or,

The messages related to the management function interface include: O1 messages that are not encapsulated by the O1 interface;

and / or,

The E2 interface related message includes at least one of the following:

E2 messages that are not encapsulated by the E2AP interface;

E2SM encapsulated message;

Messages in non-E2SM encapsulated form.

For A1 or O1 related messages, from the point of view of the messages sent by the application function to the platform function, the message is the A1 or O1 information generated by the application function, and the A1 or O1 interface is not encapsulated. Or a message sent to a logical function inside a platform function.

As for E2 related messages, from the point of view of the messages sent by the application function to the platform function, the message is E2 information generated by the application function, and is not encapsulated by the E2AP interface. The information may be sent to the platform function in the form of E2SM encapsulation, or may be sent to the platform function in the form of non-E2SM encapsulation.

On the one hand, when the request message body of the first message is data in the form of E2SM encapsulation, the first message further includes:

E2SM identification, the E2SM identification is used to assist subscription management and conflict resolution.

In other words, when the data in the form of E2SM encapsulation is used as the message body on the near real-time wireless intelligent control application program interface oriented to the application function, the definition of IE by the E2SM on the existing E2 interface can be reused. E2SM logos, such as E2SM-NI, E2SM-KPM, can be added to the interactive messages of the near real-time wireless intelligent control application program interface. Through the identification of E2SM, the platform facilitates subscription management and conflict resolution. On the one hand, the platform function may not perform subscription management for different E2SM identification messages, so the data items provided by different E2SMs are different. On the other hand, E2SM parsing is performed for messages with the same E2SM identification, and subscription management and conflict resolution are performed.

On the other hand, when the request message body of the first message is non-E2SM encapsulated data, the messages transmitted on the near real-time wireless intelligent control application program interface all adopt a unified interface abstract syntax and serialization.

In other words, when the non-E2SM-encapsulated data is used as the message body on the application-oriented near real-time wireless intelligent control application program interface, the E2-related messages may not use the existing E2SM solution. For all messages on the near real-time wireless intelligent control application program interface, a unified interface abstract syntax and serialization can be used, and the application function does not need to support multiple schemes, which is beneficial to the simplified design of the application function. In addition, since there is no one-to-one mapping relationship between the definition of E2SM and the application function, there is a situation that one application function uses multiple E2SMs or multiple application functions use one E2SM. Therefore, when multiple E2SMs use different abstract syntax and serialization schemes, this E2-related interface scheme can still maintain the uniqueness of abstract syntax and serialization. When multiple application functions use one E2SM, if the E2SM is expanded due to the newly introduced application function, the embodiment of the present invention can parse the E2SM through the platform function to shield the change of the E2SM without affecting the existing application function.

As another optional embodiment, step 21 includes:

Obtaining external input or the second message transmitted on at least one of the E2 interface, the A1 interface and the O1 interface generated inside the near real-time wireless intelligent controller;

The second message is processed to generate a third message that can be transmitted in the near real-time wireless intelligent control application program interface, and is transmitted to the corresponding application function.

Optionally, when the second message is a message of the A1 interface or the O1 interface, the third message includes:

The identifier of the application function; the identifier can be a uniform resource identifier (Uniform ResourceIdentifier, URI) or a uniform resource locator (Uniform Resource Locator, URL) or the name of the xApp, in these cases it is in the form of characters. It can also be a number number within a certain range, in this case it is an integer form;

API version number (Version);

The message body of the third message.

Optionally, the third message further includes at least one of the following:

the address of the conflict resolution service;

the address of the database service;

The application function can obtain a list of network devices for data or control.

From the message sent by the platform function to the application function, the source of the message may be the A1 interface or O1 interface message received from the Near-RT RIC or the message inside the Near-RT RIC platform. If the A1 or O1 interface message is received from the Near-RT RIC, the received A1 or O1 message must be processed by the platform A1 or O1 interface. The A1 or O1 interface processing at least includes parsing the A1 JSON encoding or the O1Netconf protocol. According to A1 Or the content of the message header or message body of O1, which decides which application function or functions to send to. If it is a message inside the Near-RT RIC platform, the corresponding message body content is generated according to the logical function requirements for generating the message. For example, the platform configures the initialized service information to xApp.

As shown in Table 3, the third message includes the following information.

table 3

Wherein, when the second message is an E2 interface message, the message body of the third message includes:

E2SM encapsulated message;

Messages in non-E2SM encapsulation form; messages in non-E2SM encapsulation form use the same abstract syntax and serialization as the near real-time wireless intelligent control application program interface.

For E2 related messages, there are various internal processing procedures of platform functions due to related processing procedures. For example, as shown in Figure 3, one is that the application function only interacts with the E2 interface processing function, and the E2 interface processing function interacts with other internal logic functions (such as subscription management, conflict resolution, and database) according to the situation; as shown in Figure 4, The other is that the application function directly interacts with subscription management, conflict resolution, database, etc.; then each module interacts with the E2 interface processing function if there is an E2 interface message interaction requirement; it may also be a mixed form of the above two, as shown in Figure 5 shown. Taking the subscription request and subscription data report of the application function as an example, the above three processing flows are as follows

Therefore, if the application program interface of the application-oriented near-real-time wireless intelligent control inside the Near-RT RIC is defined with the application function and the Near-RT RIC as the interface, the consistency of the interface information definition is better, and it can be compatible with different Near-RT RICs. -RT RIC's platform function internal processing. The internal processing of the platform functions of different Near-RT RICs can be specifically supported by the number and meanings defined by the above message types.

For E2 interface related messages, this embodiment of the present invention can support two types of E2 interface related messages. One is to reuse the information definition of the existing E2SM in the message body of the E2 interface related message; the other is to use the abstract syntax expression and serialization scheme consistent with the platform interface.

From the message sent by the platform function to the application function, the source of the message may be the E2 interface message received from the Near-RT RIC or the message inside the Near-RT RIC platform. If the E2 interface message is received from the Near-RT RIC, the received E2 message must be processed by the platform E2 interface. The E2 interface processing at least includes parsing E2AP parsing (including ASN.1 decoding). Then, the original information of the E2SM and the fields in the E2AP for assisting E2SM parsing are sent to the application function through the application-oriented open interface. Further, the platform function of the Near-RT RIC may further parse the E2SM, and send the data items subscribed by the application function and the corresponding instructions to the application function through the application-oriented open interface. If it is an internal message of the platform function of the Near-RT RIC, then according to the logical function requirements for generating the message, the corresponding message body content is generated. For example, the platform sends a conflict resolution response message to xApp as shown in Table 4.

Table 4

To sum up, the messages sent or received on the near real-time wireless intelligent control application program interface include one or more of the following: parsing the information encapsulated by E2AP or information not encapsulated as E2AP, parsing the information encapsulated by E2SM or not encapsulated as E2SM information generated by databases, messaging infrastructure, platform subscription management or conflict resolution.

To sum up, in the embodiment of the present invention, the interface scheme oriented to the internal application function of the Near-RT RIC has high overhead, passive upgrade service interruption, repeated E2/A1/O1 general interface protocol processing, repeated E2 interface subscription data, and low conflict resolution efficiency. Therefore, an open interface scheme oriented to application functions is proposed. The open interface solution provides a unified interface for application functions, and further solves the above problems through the design of the open interface. The embodiments of the present invention include at least the following effective effects:

Application functions do not need to parse and encapsulate carrier-class device interfaces such as E2, A1, and/or O1, and only need to support open interfaces oriented to application functions, and the processing overhead of additional interfaces for application functions is small. Introducing the identification of application functions on the open interface, the platform’s identification based on application functions makes it easier to interact with interface messages such as E2, A1 and O1 and platform internal messages with different application functions, avoiding multiple processing of E2, A1 and O1 messages. . The definition of open interface shields the influence of O1, A1 and E2 interface expansion on existing application functions caused by new application functions, and ensures the continuity of services. When E2-related messages in the open interface are encapsulated by non-E2SM, it is helpful to unify the structured syntax and serialization scheme. The definition of open interfaces helps to improve the efficiency of subscription management and conflict resolution.

As shown in FIG. 6 , an embodiment of the present invention further provides a message transmission method, which is applied to an application function inside a near real-time wireless intelligent controller, including:

Step 61 , through the near-real-time wireless intelligent control application program interface, perform message interaction with the platform function inside the near-real-time wireless intelligent controller.

As an optional embodiment, the method further includes:

Through an open interface with other application functions inside the near real-time wireless intelligent controller, message interaction is performed with the other application functions.

Wherein, the near real-time wireless intelligent control application program interface includes at least one of the following:

a first API associated with the E2 interface;

a second API associated with the A1 interface;

a third application program interface related to the management function interface;

A fourth API related to the shared data layer.

Wherein, when the application function and other application functions perform message interaction through the open interface, the exchanged messages include:

message type, used to indicate that the message is an interaction message between application functions;

The identification of other application functions, that is, the identification of the target application function; it is unique. It can be a uniform resource identifier (Uniform Resource Identifier, URI) or a uniform resource locator (Uniform Resource Locator, URL) or the name of the application function, which is in character form. It can also be a number number within a certain range, in this case it is an integer form.

In this embodiment of the present invention, the information that one application function can provide to other application functions is: parsed A1/O1 information or information that is not encapsulated in an A1/O1 interface format.

Wherein, step 61 includes:

The first message is transmitted to the platform function through the near real-time wireless intelligent control application program interface; the platform function processes the first message and maps the first message to the E2 interface, A1 interface, Management function interface, internal interface or upper-layer business interface.

Wherein, the first message includes:

The identifier of the application function; the identifier may be a uniform resource identifier (Uniform ResourceIdentifier, URI) or a uniform resource locator (Uniform Resource Locator, URL), in these cases, it is in the form of characters. It can also be a number number within a certain range, in this case it is an integer form;

The message body of the first message.

Optionally, the first message further includes at least one of the following:

the identification of the platform function;

API version number (Version);

message type.

Wherein, after transmitting the first message to the platform function through the near real-time wireless intelligent control application program interface, the method further includes:

Receive a first response message sent by the platform function, where the first response message includes:

The identifier of the application function; the identifier can be a uniform resource identifier (Uniform ResourceIdentifier, URI) or a uniform resource locator (Uniform Resource Locator, URL) or the name of the xApp, in these cases it is in the form of characters. It can also be a number number within a certain range, in this case it is an integer form;

API version number (Version);

The message body of the first response message.

Optionally, the first response message further includes:

message type.

Wherein, the first message is at least one of the following:

A1 interface related messages;

E2 interface related messages;

Management function interface related messages;

Internal logic messages for near real-time wireless smart controllers.

Wherein, the messages related to the A1 interface include: A1 messages that are not encapsulated by the A1 interface;

and / or,

The messages related to the management function interface include: O1 messages that are not encapsulated by the O1 interface;

and / or,

The E2 interface related message includes at least one of the following:

E2 messages that are not encapsulated by the E2AP interface;

E2SM encapsulated message;

Messages in non-E2SM encapsulated form.

For A1 or O1 related messages, from the point of view of the message sent by the application function to the platform function, the message is the A1 or O1 information generated by the application function, and the A1 or O1 interface is not encapsulated. Or a message sent to a logical function inside a platform function.

As for E2 related messages, from the point of view of the messages sent by the application function to the platform function, the message is E2 information generated by the application function, and is not encapsulated by the E2AP interface. The information may be sent to the platform function in the form of E2SM encapsulation, or may be sent to the platform function in the form of non-E2SM encapsulation.

On the one hand, when the request message body of the first message is data in the form of E2SM encapsulation, the first message further includes:

E2SM identification, the E2SM identification is used to assist subscription management and conflict resolution.

In other words, when the data in the form of E2SM encapsulation is used as the message body on the near real-time wireless intelligent control application program interface oriented to the application function, the definition of IE by the E2SM on the existing E2 interface can be reused. E2SM logos, such as E2SM-NI, E2SM-KPM, can be added to the interactive messages of the near real-time wireless intelligent control application program interface. Through the identification of E2SM, the platform facilitates subscription management and conflict resolution. On the one hand, the platform function may not perform subscription management for different E2SM identification messages, so the data items provided by different E2SMs are different. On the other hand, E2SM parsing is performed for messages with the same E2SM identification, and subscription management and conflict resolution are performed.

On the other hand, when the request message body of the first message is non-E2SM encapsulated data, the messages transmitted on the near real-time wireless intelligent control application program interface all adopt a unified interface abstract syntax and serialization.

In other words, when the non-E2SM encapsulated data is used as the message body on the near real-time wireless intelligent control application program interface oriented to the application function, the E2-related messages may not use the existing E2SM solution. For all messages on the near real-time wireless intelligent control application program interface, a unified interface abstract syntax and serialization can be used, and the application function does not need to support multiple schemes, which is beneficial to the simplified design of the application function. In addition, since there is no one-to-one mapping relationship between the definition of E2SM and application functions, there is a situation that one application function uses multiple E2SMs or multiple application functions use one E2SM. Therefore, when multiple E2SMs use different abstract syntax and serialization schemes, this E2-related interface scheme can still maintain the uniqueness of abstract syntax and serialization. When multiple application functions use one E2SM, if the E2SM is expanded due to the newly introduced application function, the embodiment of the present invention can parse the E2SM through the platform function to shield the change of the E2SM without affecting the existing application function.

As another optional embodiment, step 61 includes:

A third message transmitted by the platform function via the near real-time wireless intelligent control API is received.

Wherein, the third message includes:

The identifier of the application function; the identifier can be a uniform resource identifier (Uniform ResourceIdentifier, URI) or a uniform resource locator (Uniform Resource Locator, URL) or the name of the xApp, in these cases it is in the form of characters. It can also be a number number within a certain range, in this case it is an integer form;

API version number (Version);

The message body of the third message.

Optionally, the third message further includes at least one of the following:

the address of the conflict resolution service;

the address of the database service;

The application function can obtain a list of network devices for data or control.

From the message sent by the platform function to the application function, the source of the message may be the A1 interface or O1 interface message received from the Near-RT RIC or the message inside the Near-RT RIC platform. If the A1 or O1 interface message is received from the Near-RT RIC, the received A1 or O1 message must be processed by the platform A1 or O1 interface function. The A1 or O1 interface function processing at least includes parsing A1 JSON encoding or O1 Netconf protocol , according to the content of the message header or message body of A1 or O1, decide which application function or functions to send to. If it is a message inside the Near-RT RIC platform, the corresponding message body content is generated according to the logical function requirements for generating the message. For example, the platform configures the initialized service information to xApp.

Wherein, the message body of the third message includes:

E2SM encapsulated message;

Messages in non-E2SM encapsulation form; messages in non-E2SM encapsulation form use the same abstract syntax and serialization as the near real-time wireless intelligent control application program interface.

For E2 interface related messages, this embodiment of the present invention can support two types of E2 interface related messages. One is to reuse the information definition of the existing E2SM in the message body of the E2 interface related message; the other is to use the abstract syntax expression and serialization scheme consistent with the platform interface.

From the message sent by the platform function to the application function, the source of the message may be the E2 interface message received from the Near-RT RIC or the message inside the Near-RT RIC platform. If the E2 interface message is received from the Near-RT RIC, the received E2 message must be processed by the platform E2 interface function. The E2 interface function processing at least includes parsing E2AP parsing (including ASN.1 decoding). Then, the original information of the E2SM and the fields in the E2AP for assisting E2SM parsing are sent to the application function through the application-oriented open interface. Further, the platform function of the Near-RT RIC may further parse the E2SM, and send the data items subscribed by the application function and the corresponding instructions to the application function through the application-oriented open interface. If it is an internal message of the platform function of the Near-RT RIC, then according to the logical function requirements for generating the message, the corresponding message body content is generated.

To sum up, in the embodiment of the present invention, the interface scheme oriented to the internal application function of the Near-RT RIC has high overhead, passive upgrade service interruption, repeated E2/A1/O1 general interface protocol processing, repeated E2 interface subscription data, and low conflict resolution efficiency. Therefore, an open interface scheme oriented to application functions is proposed. The open interface solution provides a unified interface for application functions, and further solves the above problems through the design of the open interface.

The embodiments of the present invention include at least the following effective effects:

Application functions do not need to parse and encapsulate carrier-class device interfaces such as E2, A1, and/or O1, and only need to support open interfaces oriented to application functions, and the processing overhead of additional interfaces for application functions is small. Introducing the identification of application functions on the open interface, the platform’s identification based on application functions makes it easier to interact with interface messages such as E2, A1 and O1 and platform internal messages with different application functions, avoiding multiple processing of E2, A1 and O1 messages. . The definition of open interface shields the influence of O1, A1 and E2 interface expansion on existing application functions caused by new application functions, and ensures the continuity of services. When E2-related messages in the open interface are encapsulated by non-E2SM, it is helpful to unify the structured syntax and serialization scheme. The definition of open interfaces helps to improve the efficiency of subscription management and conflict resolution.

As shown in FIG. 7 , an embodiment of the present invention further provides a message transmission device, which is applied to the platform function of the near real-time wireless intelligent controller, including:

The first interaction module 71 is configured to perform message interaction with at least one application function through a near real-time wireless intelligent control application program interface;

Wherein, the at least one application function is an application function inside the near real-time wireless intelligent controller.

As an optional embodiment, the platform function further includes: the near real-time wireless intelligent control application program interface includes at least one of the following:

a first API associated with the E2 interface;

a second API associated with the A1 interface;

a third application program interface related to the management function interface;

A fourth API related to the shared data layer.

As an optional embodiment, the first interaction module includes:

a first submodule, configured to receive a first message transmitted by at least one application function through the near real-time wireless intelligent control application program interface;

The second sub-module is configured to process the first message and map the first message to the E2 interface, the A1 interface, the management function interface, the internal interface or the upper-layer service interface.

As an optional embodiment, the first message includes:

the identifier of the application function;

The message body of the first message.

As an optional embodiment, the first message further includes at least one of the following:

the identification of the platform function;

API version number;

message type.

As an optional embodiment, the apparatus further includes:

A response sending module, configured to send a first response message to the application function, where the first response message includes:

the identifier of the application function;

API version number;

The message body of the first response message.

As an optional embodiment, the first response message further includes:

message type.

As an optional embodiment, the first message is at least one of the following:

A1 interface related messages;

E2 interface related messages;

Management function interface related messages;

Internal logic messages of near real-time wireless intelligent controllers;

As an optional embodiment, the A1 interface-related messages include: A1 messages that are not encapsulated by the A1 interface;

and / or,

The messages related to the management function interface include: O1 messages that are not encapsulated by the O1 interface;

and / or,

The E2 interface related message includes at least one of the following:

E2 messages that are not encapsulated by the E2AP interface;

E2SM encapsulated message;

Messages in non-E2SM encapsulated form.

As an optional embodiment, when the request message body of the first message is data in the form of E2SM encapsulation, the first message further includes:

E2SM identification, the E2SM identification is used to assist subscription management and conflict resolution.

As an optional embodiment, when the request message body of the first message is data in a non-E2SM encapsulation form, the messages transmitted on the near real-time wireless intelligent control application program interface all adopt a unified interface abstract syntax and sequence change.

As an optional embodiment, the first interaction module includes:

The third sub-module is used to obtain the second message transmitted on at least one of the E2 interface, the A1 interface and the O1 interface generated by the external input or the near real-time wireless intelligent controller;

The fourth sub-module is configured to process the second message, generate a third message that can be transmitted in the near real-time wireless intelligent control application program interface, and transmit it to the corresponding application function.

As an optional embodiment, when the second message is a message of the A1 interface or the O1 interface, the third message includes:

the identifier of the application function;

API version number;

The message body of the third message.

As an optional embodiment, the third message further includes at least one of the following:

the address of the conflict resolution service;

the address of the database service;

The application function can obtain a list of network devices for data or control.

As an optional embodiment, when the second message is a message of the E2 interface, the message body of the third message includes:

E2SM encapsulated message;

Messages in non-E2SM encapsulation form; messages in non-E2SM encapsulation form use the same abstract syntax and serialization as the near real-time wireless intelligent control application program interface.

To sum up, in the embodiment of the present invention, the interface scheme oriented to the internal application function of the Near-RT RIC has high overhead, passive upgrade service interruption, repeated E2/A1/O1 general interface protocol processing, repeated E2 interface subscription data, and low conflict resolution efficiency. Therefore, an open interface scheme oriented to application functions is proposed. The open interface solution provides a unified interface for application functions, and further solves the above problems through the design of the open interface. The embodiments of the present invention include at least the following effective effects:

Application functions do not need to parse and encapsulate carrier-class device interfaces such as E2, A1, and/or O1, and only need to support open interfaces oriented to application functions, and the processing overhead of additional interfaces for application functions is small. Introducing the identification of application functions on the open interface, the platform’s identification based on application functions makes it easier to interact with interface messages such as E2, A1 and O1 and platform internal messages with different application functions, avoiding multiple processing of E2, A1 and O1 messages. . The definition of open interface shields the influence of O1, A1 and E2 interface expansion on existing application functions caused by new application functions, and ensures the continuity of services. When E2-related messages in the open interface are encapsulated by non-E2SM, it is helpful to unify the structured syntax and serialization scheme. The definition of open interfaces helps to improve the efficiency of subscription management and conflict resolution.

It should be noted that the message transmission device provided by the embodiment of the present invention is a device capable of executing the above message transmission method, and all the above message transmission method embodiments are applicable to the device, and can achieve the same or similar beneficial effects.

As shown in FIG. 8 , an embodiment of the present invention further provides a platform function. The platform function is a platform function of a near real-time wireless intelligent controller, including a processor 800 and a transceiver 810. The transceiver 810 is connected to the processor 800. To receive and transmit data under the control of the processor 800, the processor 800 is configured to perform the following operations:

Perform message interaction with at least one application function through a near real-time wireless intelligent control application program interface;

Wherein, the at least one application function is an application function inside the near real-time wireless intelligent controller.

As an optional embodiment, the near real-time wireless intelligent control application program interface includes at least one of the following:

a first API associated with the E2 interface;

a second API associated with the A1 interface;

a third application program interface related to the management function interface;

A fourth API related to the shared data layer.

As an optional embodiment, the processor 800 is further configured to perform the following operations:

receiving a first message transmitted by at least one application function through the near real-time wireless intelligent control API;

The first message is processed, and the first message is mapped to an E2 interface, an A1 interface, a management function interface, an internal interface or an upper-layer service interface.

As an optional embodiment, the first message includes:

the identifier of the application function;

API version number;

The message body of the first message.

As an optional embodiment, the first message further includes at least one of the following:

the identification of the platform function;

message type.

As an optional embodiment, the processor 800 is further configured to perform the following operations:

Send a first response message to the application function, where the first response message includes:

the identifier of the application function;

API version number;

The message body of the first response message.

As an optional embodiment, the first response message further includes:

message type.

As an optional embodiment, the first message is at least one of the following:

A1 interface related messages;

E2 interface can related messages;

Management function interface related messages;

Internal logic messages for near real-time wireless smart controllers.

As an optional embodiment, the A1 interface-related messages include: A1 messages that are not encapsulated by the A1 interface;

and / or,

The messages related to the management function interface include: O1 messages that are not encapsulated by the O1 interface;

and / or,

The E2 interface related message includes at least one of the following:

E2 messages that are not encapsulated by the E2AP interface;

E2SM encapsulated message;

Messages in non-E2SM encapsulated form.

As an optional embodiment, when the request message body of the first message is data in the form of E2SM encapsulation, the first message further includes:

E2SM identification, the E2SM identification is used to assist subscription management and conflict resolution.

As an optional embodiment, when the request message body of the first message is data in a non-E2SM encapsulation form, the messages transmitted on the near real-time wireless intelligent control application program interface all adopt a unified interface abstract syntax and sequence change.

As an optional embodiment, the processor 800 is further configured to perform the following operations:

Obtaining external input or the second message transmitted on at least one of the E2 interface, the A1 interface and the O1 interface generated inside the near real-time wireless intelligent controller;

The second message is processed to generate a third message that can be transmitted in the near real-time wireless intelligent control application program interface, and is transmitted to the corresponding application function.

As an optional embodiment, when the second message is a message of the A1 interface or the O1 interface, the third message includes:

the identifier of the application function;

API version number;

The message body of the third message.

As an optional embodiment, the third message further includes at least one of the following:

the address of the conflict resolution service;

the address of the database service;

The application function can obtain a list of network devices for data or control.

As an optional embodiment, when the second message is a message of the E2 interface, the message body of the third message includes:

E2SM encapsulated message;

Messages in non-E2SM encapsulation form; messages in non-E2SM encapsulation form use the same abstract syntax and serialization as the near real-time wireless intelligent control application program interface.

To sum up, in the embodiment of the present invention, the interface scheme oriented to the internal application function of the Near-RT RIC has high overhead, passive upgrade service interruption, repeated E2/A1/O1 general interface protocol processing, repeated E2 interface subscription data, and low conflict resolution efficiency. Therefore, an open interface scheme oriented to application functions is proposed. The open interface solution provides a unified interface for application functions, and further solves the above problems through the design of the open interface. The embodiments of the present invention include at least the following effective effects:

Application functions do not need to parse and encapsulate carrier-class device interfaces such as E2, A1, and/or O1, and only need to support open interfaces oriented to application functions, and the processing overhead of additional interfaces for application functions is small. Introducing the identification of application functions on the open interface, the platform's identification based on application functions makes it easier to interact with interface messages such as E2, A1 and O1 and platform internal messages with different application functions, avoiding multiple processing of E2, A1 and O1 messages. . The definition of open interface shields the influence of O1, A1 and E2 interface expansion on existing application functions caused by new application functions, and ensures the continuity of services. When E2-related messages in the open interface are encapsulated by non-E2SM, it is helpful to unify the structured syntax and serialization scheme. The definition of open interfaces helps to improve the efficiency of subscription management and conflict resolution.

It should be noted that the platform function provided by the embodiment of the present invention is a platform function capable of executing the above message transmission method, and all the above-mentioned embodiments of the message transmission method are applicable to this platform function, and can achieve the same or similar beneficial effects .

As shown in FIG. 9 , an embodiment of the present invention further provides a message transmission device, which is applied to an application function inside a near real-time wireless intelligent controller, including:

The second interaction module 91 is configured to perform message interaction with the platform function inside the near-real-time wireless intelligent controller through the near-real-time wireless intelligent control application program interface.

As an optional embodiment, the near real-time wireless intelligent control application program interface includes at least one of the following:

a first API associated with the E2 interface;

a second API associated with the A1 interface;

a third application program interface related to the management function interface;

A fourth API related to the shared data layer.

As an optional embodiment, the device further includes:

The third interaction module is configured to perform message interaction with other application functions within the near real-time wireless intelligent controller through an open interface with the other application functions.

As an optional embodiment, when the application function interacts with other application functions through the open interface, the exchanged messages include:

message type, used to indicate that the message is an interaction message between application functions;

Identification of other application functions.

As an optional embodiment, the second interaction module includes:

a fifth submodule, configured to transmit a first message to the platform function through the near real-time wireless intelligent control application program interface; to process the first message by the platform function, and map the first message To the E2 interface, A1 interface, management function interface, internal interface or upper-layer service interface.

As an optional embodiment, the first message includes:

the identifier of the application function;

The message body of the first message.

As an optional embodiment, the first message further includes at least one of the following:

the identification of the platform function;

API version number;

message type.

As an optional embodiment, the device includes:

A response receiving module, configured to receive a first response message sent by the platform function, where the first response message includes:

the identifier of the application function;

API version number;

The message body of the first response message.

As an optional embodiment, the first response message further includes:

message type.

As an optional embodiment, the first message is at least one of the following:

A1 interface related messages;

E2 interface related messages;

Management function interface related messages;

Internal logic messages for near real-time wireless smart controllers.

As an optional embodiment, the A1 interface-related messages include: A1 messages that are not encapsulated by the A1 interface;

and / or,

The messages related to the management function interface include: O1 messages that are not encapsulated by the O1 interface;

and / or,

The E2 interface related message includes at least one of the following:

E2 messages that are not encapsulated by the E2AP interface;

E2SM encapsulated message;

Messages in non-E2SM encapsulated form.

As an optional embodiment, when the request message body of the first message is data in the form of E2SM encapsulation, the first message further includes:

E2SM identification, the E2SM identification is used to assist subscription management and conflict resolution.

As an optional embodiment, when the request message body of the first message is data in a non-E2SM encapsulation form, the messages transmitted on the near real-time wireless intelligent control application program interface all adopt a unified interface abstract syntax and sequence change.

As an optional embodiment, the second interaction module includes:

The fourth sub-module is configured to receive the third message transmitted by the platform function through the near real-time wireless intelligent control application program interface.

As an optional embodiment, the third message includes:

the identifier of the application function;

API version number;

The message body of the third message.

As an optional embodiment, the third message further includes at least one of the following:

the address of the conflict resolution service;

the address of the database service;

The application function can obtain a list of network devices for data or control.

As an optional embodiment, the message body of the third message includes:

E2SM encapsulated message;

Messages in non-E2SM encapsulation form; messages in non-E2SM encapsulation form use the same abstract syntax and serialization as the near real-time wireless intelligent control application program interface.

To sum up, in the embodiment of the present invention, the interface scheme oriented to the internal application function of the Near-RT RIC has high overhead, passive upgrade service interruption, repeated E2/A1/O1 general interface protocol processing, repeated E2 interface subscription data, and low conflict resolution efficiency. Therefore, an open interface scheme oriented to application functions is proposed. The open interface solution provides a unified interface for application functions, and further solves the above problems through the design of the open interface. The embodiments of the present invention include at least the following effective effects:

Application functions do not need to parse and encapsulate carrier-class device interfaces such as E2, A1, and/or O1, and only need to support open interfaces oriented to application functions, and the processing overhead of additional interfaces for application functions is small. Introducing the identification of application functions on the open interface, the platform's identification based on application functions makes it easier to interact with interface messages such as E2, A1 and O1 and platform internal messages with different application functions, avoiding multiple processing of E2, A1 and O1 messages. . The definition of open interface shields the influence of O1, A1 and E2 interface expansion on existing application functions caused by new application functions, and ensures the continuity of services. When E2-related messages in the open interface are encapsulated by non-E2SM, it is helpful to unify the structured syntax and serialization scheme. The definition of open interfaces helps to improve the efficiency of subscription management and conflict resolution.

It should be noted that the message transmission device provided by the embodiment of the present invention is a device capable of executing the above message transmission method, and all the above message transmission method embodiments are applicable to the device, and can achieve the same or similar beneficial effects.

As shown in FIG. 10 , an embodiment of the present invention further provides an application function, where the application function is an application function inside the near real-time wireless intelligent controller, including a processor 100 and a transceiver 110, where the transceiver 110 is in the processor Receive and transmit data under the control of 100, the processor 100 is configured to perform the following operations:

Through the near-real-time wireless intelligent control application program interface, message interaction with the platform function inside the near-real-time wireless intelligent controller is carried out.

As an optional embodiment, the near real-time wireless intelligent control application program interface includes at least one of the following:

a first API associated with the E2 interface;

a second API associated with the A1 interface;

a third application program interface related to the management function interface;

A fourth API related to the shared data layer.

As an optional embodiment, the processor 100 is further configured to perform the following operations:

Through an open interface with other application functions inside the near real-time wireless intelligent controller, message interaction is performed with the other application functions.

As an optional embodiment, when the application function interacts with other application functions through the open interface, the exchanged messages include:

message type, used to indicate that the message is an interaction message between application functions;

Identification of other application functions.

As an optional embodiment, the processor 100 is further configured to perform the following operations:

The first message is transmitted to the platform function through the near real-time wireless intelligent control application program interface; the first message is processed by the platform function, and the first message is mapped to the E2 interface, A1 interface, Management function interface, internal interface or upper-layer business interface.

As an optional embodiment, the first message includes:

the identifier of the application function;

The message body of the first message.

As an optional embodiment, the first message further includes at least one of the following:

the identification of the platform function;

API version number;

message type.

As an optional embodiment, the processor is further configured to perform the following operations:

Receive a first response message sent by the platform function, where the first response message includes:

the identifier of the application function;

API version number;

The message body of the first response message.

As an optional embodiment, the first response message further includes:

message type.

As an optional embodiment, the first message is at least one of the following:

A1 interface related messages;

E2 interface related messages;

Management function interface related messages;

Internal logic messages for near real-time wireless smart controllers.

As an optional embodiment, the A1 interface-related messages include: A1 messages that are not encapsulated by the A1 interface;

and / or,

The messages related to the management function interface include: O1 messages that are not encapsulated by the O1 interface;

and / or,

The E2 interface related message includes at least one of the following:

E2 messages that are not encapsulated by the E2AP interface;

E2SM encapsulated message;

Messages in non-E2SM encapsulated form.

As an optional embodiment, when the request message body of the first message is data in the form of E2SM encapsulation, the first message further includes:

E2SM identification, the E2SM identification is used to assist subscription management and conflict resolution.

As an optional embodiment, when the request message body of the first message is data in a non-E2SM encapsulation form, the messages transmitted on the near real-time wireless intelligent control application program interface all adopt a unified interface abstract syntax and sequence change.

As an optional embodiment, the processor 100 is further configured to perform the following operations:

A third message transmitted by the platform function via the near real-time wireless intelligent control API is received.

As an optional embodiment, the third message includes:

the identifier of the application function;

API version number;

The message body of the third message.

As an optional embodiment, the third message further includes at least one of the following:

the address of the conflict resolution service;

the address of the database service;

The application function can obtain a list of network devices for data or control.

As an optional embodiment, the message body of the third message includes:

E2SM encapsulated message;

Messages in non-E2SM encapsulation form; messages in non-E2SM encapsulation form use the same abstract syntax and serialization as the near real-time wireless intelligent control application program interface.

To sum up, in the embodiment of the present invention, the interface scheme oriented to the internal application function of the Near-RT RIC has high overhead, passive upgrade service interruption, repeated E2/A1/O1 general interface protocol processing, repeated E2 interface subscription data, and low conflict resolution efficiency. Therefore, an open interface scheme oriented to application functions is proposed. The open interface solution provides a unified interface for application functions, and further solves the above problems through the design of the open interface.

The embodiments of the present invention include at least the following effective effects:

Application functions do not need to parse and encapsulate carrier-class device interfaces such as E2, A1, and/or O1, and only need to support open interfaces oriented to application functions, and the processing overhead of additional interfaces for application functions is small. Introducing the identification of application functions on the open interface, the platform's identification based on application functions makes it easier to interact with interface messages such as E2, A1 and O1 and platform internal messages with different application functions, avoiding multiple processing of E2, A1 and O1 messages. . The definition of open interface shields the influence of O1, A1 and E2 interface expansion on existing application functions caused by new application functions, and ensures the continuity of services. When E2-related messages in the open interface are encapsulated by non-E2SM, it is helpful to unify the structured syntax and serialization scheme. The definition of open interfaces helps to improve the efficiency of subscription management and conflict resolution.

It should be noted that the application function provided by the embodiment of the present invention is an application function capable of executing the above-mentioned message transmission method, and all embodiments of the above-mentioned message transmission method are applicable to this application function, and can achieve the same or similar beneficial effects .

As shown in FIG. 1 , an embodiment of the present invention further provides a near real-time wireless intelligent controller, which includes the above-mentioned platform function and at least one of the above-mentioned application functions.

It should be noted that all embodiments of the above platform function and the above application function are applicable to the near real-time wireless intelligent controller, and can achieve the same or similar beneficial effects, which are not repeated here.

An embodiment of the present invention also provides a communication device, including a memory, a processor, and a computer program stored on the memory and running on the processor, where the processor implements the above-mentioned program when executing the program The various processes in the embodiments of the message transmission method can achieve the same technical effect, and are not repeated here in order to avoid repetition.

Embodiments of the present invention also provide a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, each process in the above-described embodiment of the message transmission method can be implemented, and the same technical effect can be achieved. , in order to avoid repetition, it will not be repeated here. The computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk, or an optical disk.

As will be appreciated by one skilled in the art, the embodiments of the present application may be provided as a method, a system or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-readable storage media having computer-usable program code embodied therein, including but not limited to disk storage, optical storage, and the like.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present application. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow and/or a block or blocks of the flowchart.

These computer program instructions may also be stored in a computer-readable storage medium capable of directing a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce a paper product comprising the instruction means, The instruction means implements the functions specified in the flow or flows of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded onto a computer or other programmable data processing device to cause the computer or other programmable device to perform a series of operational steps to produce a computer-implemented process, whereby the instructions to be executed on the computer or other programmable device Steps are provided for implementing the functions specified in a flow or flows of the flowcharts and/or a block or blocks of the block diagrams.

The above is the preferred embodiment of the present invention. It should be pointed out that for those skilled in the art, without departing from the principle of the present invention, several improvements and modifications can be made. These improvements and modifications It should also be regarded as the protection scope of the present invention.

Claims (40)

1. A message transmission method is applied to the platform function of a near-real-time wireless intelligent controller, and is characterized by comprising the following steps:

performing message interaction with at least one application function through a near real-time wireless intelligent control application program interface;

wherein the at least one application function is an application function inside the near real-time wireless intelligent controller.

2. The method of claim 1, wherein the near real-time wireless intelligent control application program interface comprises at least one of:

a first application program interface associated with the E2 interface;

a second application program interface associated with the a1 interface;

a third application program interface associated with the management function interface;

a fourth application program interface associated with the shared data layer.

3. The method of claim 2, wherein the performing message interaction with at least one application function through a near real-time wireless intelligent control application program interface included in the platform function comprises:

receiving a first message transmitted by at least one application function through the near-real-time wireless intelligent control application program interface;

and processing the first message, and mapping the first message to an E2 interface, an A1 interface, a management function interface, an internal interface or an upper-layer service interface.

4. The method of claim 3, wherein the first message comprises:

an identification of the application function;

a message body of the first message.

5. The method of claim 4, wherein the first message further comprises at least one of:

an identification of the platform function;

an application program interface version number;

the type of message.

6. The method of claim 3, wherein after receiving a first message transmitted by at least one application function through the near real-time wireless intelligent control application program interface, the method further comprises;

sending a first response message to the application function, the first response message comprising:

an identification of the application function;

an application program interface version number;

a message body of the first response message.

7. The method of claim 3, wherein the first message is at least one of:

a message related to the a1 interface;

e2 interface related messages;

managing functional interface related messages;

internal logic messages of the near real-time wireless intelligent controller.

8. The method of claim 7, wherein the a1 interface-related message comprises: a1 message without encapsulation of the a1 interface;

and/or the presence of a gas in the gas,

the management function interface related message comprises: an O1 message without O1 interface encapsulation;

and/or the presence of a gas in the gas,

the E2 interface related message includes at least one of:

an encapsulated E2 message without an E2AP interface;

e2SM message in encapsulated form;

non-E2 SM encapsulated form messages.

9. The method of claim 8, wherein when the request message body of the first message is data encapsulated in the form of E2SM, the first message further comprises:

e2SM identifies, the E2SM identification is used to assist subscription management and conflict resolution.

10. The method of claim 8, wherein when the request message body of the first message is data in a form other than E2SM package, the messages transmitted on the near-real-time wireless intelligent control application program interface all adopt a uniform interface abstract syntax and serialization.

11. The method of claim 2, wherein the performing message interaction with at least one application function through a near real-time wireless intelligent control application program interface included in the platform function comprises:

acquiring a second message transmitted on at least one interface of an E2 interface, an A1 interface and an O1 interface which are externally input or generated in the near real-time wireless intelligent controller;

and processing the second message to generate a third message which can be transmitted at the near-real-time wireless intelligent control application program interface, and transmitting the third message to a corresponding application function.

12. The method of claim 11, wherein when the second message is a message of an a1 interface or an O1 interface, the third message comprises:

an identification of the application function;

an application program interface version number;

a message body of the third message.

13. The method of claim 12, wherein the third message further comprises at least one of:

an address of a conflict resolution service;

an address of a database service;

the application function may obtain a list of network devices for data or control.

14. The method of claim 11, wherein when the second message is a message of an E2 interface, the message body of the third message comprises:

e2SM message in encapsulated form;

messages in non-E2 SM encapsulated form; messages in a non-E2 SM encapsulated form take on the same abstract syntax and serialization as the near real-time wireless intelligent control application program interface.

15. A message transmission method is applied to the application function in a near-real-time wireless intelligent controller, and is characterized by comprising the following steps:

and performing message interaction with the platform function inside the near real-time wireless intelligent controller through the near real-time wireless intelligent control application program interface.

16. The method of claim 15, wherein the near real-time wireless intelligent control application program interface comprises at least one of:

a first application program interface associated with the E2 interface;

a second application program interface associated with the a1 interface;

a third application program interface associated with the management function interface;

a fourth application program interface associated with the shared data layer.

17. The method of claim 15, further comprising:

and performing message interaction with other application functions in the near real-time wireless intelligent controller through an open interface between the near real-time wireless intelligent controller and the other application functions.

18. The method of claim 17, wherein when the application function performs message interaction with other application functions through the open interface, the message of the interaction comprises:

a message type for indicating that the message is an interactive message between application functions;

identification of other application functions.

19. The method of claim 16, wherein the message interaction with the platform function inside the near-real-time wireless intelligent controller through the near-real-time wireless intelligent control application program interface comprises:

transmitting a first message to the platform function through the near real-time wireless intelligent control application program interface; to process the first message by the platform function, to map the first message to an E2 interface, an A1 interface, a management function interface, an internal interface, or an upper layer traffic interface.

20. The method of claim 19, wherein the first message comprises:

an identification of the application function;

a message body of the first message.

21. The method of claim 20, wherein the first message further comprises at least one of:

an identification of the platform function;

an application program interface version number;

the type of message.

22. The method of claim 19, wherein after transmitting the first message to the platform function via the near real-time wireless intelligent control application program interface, the method further comprises:

receiving a first response message sent by the platform function, wherein the first response message comprises:

an identification of the application function;

an application program interface version number;

a message body of the first response message.

23. The method of claim 19, wherein the first message is at least one of:

a message related to the a1 interface;

e2 interface related messages;

managing functional interface related messages;

internal logic messages of the near real-time wireless intelligent controller.

24. The method according to claim 23, wherein the a1 interface-related message comprises: a1 message without encapsulation of the a1 interface;

and/or the presence of a gas in the gas,

the management function interface related message comprises: an O1 message without O1 interface encapsulation;

and/or the presence of a gas in the gas,

the E2 interface related message includes at least one of:

an encapsulated E2 message without an E2AP interface;

e2SM message in encapsulated form;

non-E2 SM encapsulated form messages.

25. The method of claim 24, wherein when the request message body of the first message is data encapsulated in E2SM, the first message further comprises:

e2SM identifies, the E2SM identification is used to assist subscription management and conflict resolution.

26. The method of claim 24, wherein when the request message body of the first message is data in a form other than E2SM package, the messages transmitted on the near-real-time wireless intelligent control application program interface all adopt a uniform interface abstract syntax and serialization.

27. The method of claim 18, wherein the message interaction with the platform function inside the near-real-time wireless intelligent controller through the near-real-time wireless intelligent control application program interface comprises:

and receiving a third message transmitted by the platform function through a near real-time wireless intelligent control application program interface.

28. The method of claim 27, wherein the third message comprises:

an identification of the application function;

an application program interface version number;

a message body of the third message.

29. The method of claim 28, wherein the third message further comprises at least one of:

an address of a conflict resolution service;

an address of a database service;

the application function may obtain a list of network devices for data or control.

30. The method of claim 27, wherein the message body of the third message comprises:

e2SM message in encapsulated form;

messages in non-E2 SM encapsulated form; messages in a non-E2 SM encapsulated form take on the same abstract syntax and serialization as the near real-time wireless intelligent control application program interface.

31. A message transmission device is applied to the platform function of a near real-time wireless intelligent controller and is characterized by comprising:

the first interactive module is used for carrying out message interaction with at least one application function through a near real-time wireless intelligent control application program interface;

wherein the at least one application function is an application function inside the near real-time wireless intelligent controller.

32. A platform function of a near real-time wireless intelligent controller, comprising a processor and a transceiver, the transceiver receiving and transmitting data under the control of the processor, wherein the processor is configured to:

performing message interaction with at least one application function through a near real-time wireless intelligent control application program interface;

wherein the at least one application function is an application function inside the near real-time wireless intelligent controller.

33. The platform functionality according to claim 32, wherein said near real-time wireless intelligent control application program interface comprises at least one of:

a first application program interface associated with the E2 interface;

a second application program interface associated with the a1 interface;

a third application program interface associated with the management function interface;

a fourth application program interface associated with the shared data layer.

34. The utility model provides a message transmission device, is applied to near real-time wireless intelligent controller inside application function, its characterized in that includes:

and the second interaction module is used for performing message interaction with the platform function in the near real-time wireless intelligent controller through the near real-time wireless intelligent control application program interface.

35. An application function inside a near real-time wireless intelligent controller, comprising a processor and a transceiver, the transceiver receiving and transmitting data under the control of the processor, wherein the processor is configured to:

and performing message interaction with the platform function inside the near real-time wireless intelligent controller through the near real-time wireless intelligent control application program interface.

36. The application function of claim 35, wherein the processor is further configured to:

and performing message interaction with other application functions in the near real-time wireless intelligent controller through an open interface between the near real-time wireless intelligent controller and the other application functions.

37. The application function of claim 36, wherein when the application function performs message interaction with other application functions through the open interface, the message of the interaction comprises:

a message type for indicating that the message is an interactive message between application functions;

identification of other application functions.

38. A near real-time wireless intelligent controller, characterized in that it comprises a platform function according to claim 32 or 33 and at least one application function according to any of claims 35-37.

39. A communication device comprising a memory, a processor, and a program stored on the memory and executable on the processor; wherein the processor, when executing the program, implements the message transmission method of any one of claims 1-14; alternatively, the processor implements the message transmission method according to any one of claims 15 to 30 when executing the program.

40. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, carries out the steps of the message transmission method according to any one of claims 1 to 14; alternatively, the program realizes the steps in the message transmission method according to any one of claims 15 to 30 when executed by a processor.

Images