Network integration control method and device

Abstract

The present disclosure discloses a network integration control method and apparatus, in which a near real-time radio access network intelligent controller sends a control request message to a network node, the control request message including M control service types corresponding to control services and related information of one or more control operations corresponding to each control service type, and the near real-time radio access network intelligent controller receives a control confirmation message sent from the network node, the control confirmation message including an execution result of each control operation in the M control service types of the network node, where M is an integer equal to or greater than 1.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This disclosure claims priority to a Chinese patent application filed in China on October 25, 2021, with application number 202111239824.0, the entire contents of which are incorporated herein by reference. The present disclosure relates to the field of communications technology, and more particularly to a network integration control method and apparatus. [Background technology]

[0002] In an open radio access network (O-RAN), a Near Real-Time Radio Access Network Intelligent Controller (Near-RT RIC) controls an E2 node via the E2 interface based on the functions opened by the E2 node to achieve the goal of optimizing RAN radio resources. The E2 service model provides a series of RAN function open services, including Report, Insert, Control, and Policy services. The Insert service allows the E2 node to suspend normal function processes and trigger an Insert operation based on information subscribed to by the Near-RT RIC. The Control service allows the Near-RT RIC to request the RAN to perform a specified operation according to a Control message. This service can be triggered within the Near-RT RIC or can serve as feedback for the Insert operation after the Insert operation.

[0003] In the related technology, only the Insert and Control operations of the isolated single-operation control method are supported between the Near-RT RIC and the E2 node. However, the application (x Application, xApp) loaded on the Near-RT RIC has the expansion capability of multiple function integration configuration, so the method of the related technology cannot meet the requirements of the multi-input multi-output synchronization configuration of xApp. Summary of the Invention [Problem to be solved by the invention]

[0004] The present disclosure aims to provide a network integration control method and device for solving the problem that the control methods in the related art cannot meet the requirements of a multi-input multi-output synchronous configuration.

[0005] An embodiment of the present disclosure provides a network integration control method, the method comprising: A near real-time radio access network intelligent controller sends a control request message to a network node, where the control request message includes M control service types corresponding to control services and related information of one or more control operations corresponding to each control service type; The near real-time radio access network intelligent controller receives a control confirmation message sent from the network node, the control confirmation message including an execution result of each control operation in the M control service types of the network node; Here, M is an integer of 1 or more.

[0006] Optionally, the method further comprises: sending a subscription request message to the network node for subscribing to an insertion service, the subscription request message including operation definitions of one or more insertion operations corresponding to the M insertion service types to be subscribed; receiving an insertion instruction message sent from the network node, where the insertion instruction message includes related information of insertion operations corresponding to M insertion service types.

[0007] Optionally, the action definition comprises: the number of requested inserted service types, The requested insertion service type, the number of insert operations included in each insert service type; an insert operation identifier, The number of radio access network RAN ​​parameters of the insertion operation; and The information includes at least one of the RAN parameter identifiers.

[0008] Optionally, the insertion instruction message includes a first information element and a second information element; the first information element includes at least one of a terminal identifier corresponding to the network node, an insertion type of the insertion instruction message, and an event trigger condition identifier; The second information element is the number of insertion service types indicated by the insertion indication message; an insertion service type indicated by the insertion indication message; the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0009] Optionally, the insert type is a multiple configuration control request.

[0010] Optionally, transmitting the control request message to a network node comprises: and transmitting the control request message to the network node based on the insertion instruction message.

[0011] Optionally, the control request message includes a third information element and a fourth information element; the third information element includes at least one of a terminal identifier corresponding to the network node, a control type of the control request message, and a control decision; The fourth information element is the number of control service types indicated by the control request message; a control service type indicated by the control request message; the number of control operations included in each control service type; control action identifier, Control decisions for control actions, the number of RAN parameters of the control operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0012] Optionally, the control decision is used to indicate a receipt status for at least one control action in a RIC control message information element.

[0013] Optionally, the control type is a multiple configuration control.

[0014] Optionally, the control confirmation message comprises: the number of control service types included in the control confirmation message; a control service type included in the control confirmation message; the number of execution results included in the control confirmation message; control action identifier, Number of RAN parameters, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0015] Optionally, transmitting the control request message to a network node comprises: If a trigger event is detected, sending the control request message to the network node.

[0016] An embodiment of the present disclosure provides a network integration control method, the method comprising: A network node receives a control request message sent from a near real-time radio access network intelligent controller, the control request message including: M control service types corresponding to control services, and related information of one or more control operations corresponding to each control service type; The network node sends a control confirmation message to the near real-time radio access network intelligent controller based on the control request message, and the control confirmation message includes an execution result of each control operation in the M control service types of the network node; Here, M is an integer of 1 or more.

[0017] Optionally, the method further comprises: receiving a subscription request message sent from the near real-time radio access network intelligent controller, the subscription request message including operation definitions of one or more insertion operations corresponding to the M insertion service types to be subscribed; Sending an insertion instruction message to the near real-time radio access network intelligent controller, where the insertion instruction message includes related information of insertion operations corresponding to the M insertion service types.

[0018] Optionally, the action definition comprises: the number of requested inserted service types, The requested insertion service type, the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, The information includes at least one of the RAN parameter identifiers.

[0019] Optionally, the insertion instruction message includes a first information element and a second information element; the first information element includes at least one of a terminal identifier corresponding to the network node, an insertion type of the insertion instruction message, and an event trigger condition identifier; The second information element is the number of insertion service types indicated by the insertion indication message; an insertion service type indicated by the insertion indication message; the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0020] Optionally, the insert type is a multiple configuration control request.

[0021] Optionally, the control request message includes a third information element and a fourth information element; the third information element includes at least one of a terminal identifier corresponding to the network node, a control type of the control request message, and a control decision; The fourth information element is the number of control service types indicated by the control request message; a control service type indicated by the control request message; the number of control operations included in each control service type; control action identifier, Control decisions for control actions, the number of RAN parameters of the control operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0022] Optionally, the control decision is used to indicate a receipt status for at least one control action in a RIC control message information element.

[0023] Optionally, the control type is a multiple configuration control.

[0024] Optionally, the control confirmation message comprises: the number of control service types included in the control confirmation message; a control service type included in the control confirmation message; the number of execution results included in the control confirmation message; control action identifier, Number of RAN parameters, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0025] An embodiment of the present disclosure provides a network integration control device, the device including a memory, a transceiver, and a processor; The memory is configured to store a computer program, the processor is configured to read the computer program in the memory, and the transceiver transmits and receives data under the control of the processor, sending a control request message to a network node, the control request message including M control service types corresponding to control services and related information of one or more control operations corresponding to each control service type; receiving a control confirmation message sent from the network node, the control confirmation message including an execution result of the network node for each control operation in the M control service types; Here, M is an integer of 1 or more.

[0026] Optionally, the transceiver further comprises: sending a subscription request message to the network node for subscribing to an insertion service, the subscription request message including operation definitions of one or more insertion operations corresponding to the M insertion service types to be subscribed; receiving an insertion instruction message sent from the network node, where the insertion instruction message includes related information of insertion operations corresponding to the M insertion service types.

[0027] Optionally, the action definition comprises: the number of requested inserted service types, The requested insertion service type, the number of insert operations included in each insert service type; an insert operation identifier, The number of radio access network RAN ​​parameters of the insertion operation; and The information includes at least one of the RAN parameter identifiers.

[0028] Optionally, the insertion instruction message includes a first information element and a second information element; the first information element includes at least one of a terminal identifier corresponding to the network node, an insertion type of the insertion instruction message, and an event trigger condition identifier; The second information element is the number of insertion service types indicated by the insertion indication message; an insertion service type indicated by the insertion indication message; the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0029] Optionally, the insert type is a multiple configuration control request.

[0030] Optionally, the transceiver is further configured to perform transmitting the control request message to the network node based on the insertion indication message.

[0031] Optionally, the control request message includes a third information element and a fourth information element; the third information element includes at least one of a terminal identifier corresponding to the network node, a control type of the control request message, and a control decision; The fourth information element is the number of control service types indicated by the control request message; a control service type indicated by the control request message; the number of control operations included in each control service type; control action identifier, Control decisions for control actions, the number of RAN parameters of the control operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0032] Optionally, the control decision is used to indicate a receipt status for at least one control action in a RIC control message information element.

[0033] Optionally, the control type is a multiple configuration control.

[0034] Optionally, the control confirmation message comprises: the number of control service types included in the control confirmation message; a control service type included in the control confirmation message; the number of execution results included in the control confirmation message; control action identifier, Number of RAN parameters, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0035] Optionally, the transceiver is configured to perform sending the control request message to the network node if a trigger event is detected.

[0036] An embodiment of the present disclosure provides a network integration control device, the device including a memory, a transceiver, and a processor; The memory is configured to store a computer program, the processor is configured to read the computer program in the memory, and the transceiver transmits and receives data under the control of the processor, Receiving a control request message sent from a near real-time radio access network intelligent controller, where the control request message includes M control service types corresponding to control services and related information of one or more control operations corresponding to each control service type; The method is configured to: send a control confirmation message to the near real-time radio access network intelligent controller based on the control request message, wherein the control confirmation message includes an execution result of each control operation in the M control service types of the network node; Here, M is an integer of 1 or more.

[0037] Optionally, the transceiver further comprises: receiving a subscription request message sent from the near real-time radio access network intelligent controller, the subscription request message including operation definitions of one or more insertion operations corresponding to the M insertion service types to be subscribed; and sending an insertion instruction message to the near real-time radio access network intelligent controller, where the insertion instruction message includes relevant information of insertion operations corresponding to the M insertion service types.

[0038] Optionally, the action definition comprises: the number of requested inserted service types, The requested insertion service type, the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, The information includes at least one of the RAN parameter identifiers.

[0039] Optionally, the insertion instruction message includes a first information element and a second information element; the first information element includes at least one of a terminal identifier corresponding to the network node, an insertion type of the insertion instruction message, and an event trigger condition identifier; The second information element is the number of insertion service types indicated by the insertion indication message; an insertion service type indicated by the insertion indication message; the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0040] Optionally, the insert type is a multiple configuration control request.

[0041] Optionally, the control request message includes a third information element and a fourth information element; the third information element includes at least one of a terminal identifier corresponding to the network node, a control type of the control request message, and a control decision; The fourth information element is the number of control service types indicated by the control request message; a control service type indicated by the control request message; the number of control operations included in each control service type; control action identifier, Control decisions for control actions, the number of RAN parameters of the control operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0042] Optionally, the control decision is used to indicate a receipt status for at least one control action in a RIC control message information element.

[0043] Optionally, the control type is a multiple configuration control.

[0044] Optionally, the control confirmation message comprises: the number of control service types included in the control confirmation message; a control service type included in the control confirmation message; the number of execution results included in the control confirmation message; control action identifier, Number of RAN parameters, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0045] An embodiment of the present disclosure provides a network integration control device, the device including: a first sending unit and a first receiving unit; The first sending unit is configured to send a control request message to a network node, where the control request message includes M control service types corresponding to control services and related information of one or more control operations corresponding to each control service type; a first receiving unit configured to receive a control confirmation message sent from the network node, the control confirmation message including an execution result of each control operation in the M control service types of the network node; Here, M is an integer of 1 or more.

[0046] An embodiment of the present disclosure provides a network integration control device, the device including: a second receiving unit and a second sending unit; The second receiving unit is configured to receive a control request message sent from a near-real-time radio access network intelligent controller, wherein the control request message includes: M control service types corresponding to control services, and related information of one or more control operations corresponding to each control service type; the second sending unit is configured to send a control confirmation message to the near real-time radio access network intelligent controller based on the control request message, the control confirmation message including an execution result for each control operation in the M control service types of the network node; Here, M is an integer of 1 or more.

[0047] An embodiment of the present disclosure provides a processor-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the network integration control method. [Effects of the Invention]

[0048] The above technical solutions of the present disclosure have the following beneficial effects: According to the embodiments of the present disclosure, the control request message sent by the near-real-time radio access network intelligent controller to the network node it controls includes information related to multiple control operations across service types, and the control confirmation message fed back by the network node to the near-real-time radio access network intelligent controller includes the execution results of multiple operations across service types. In this way, the synchronous integrated optimization control of xApp's multi-input and multi-output is realized, which can effectively avoid problems such as the waste of interface resources and equipment processing failures caused by the interruption of some operations in a control process that is completed in a single operation sequence, thereby reducing the processing delay of the base station and the increased equipment processing complexity caused by failure handling and reconfiguration, thereby improving the optimization capability of the Near-RT RIC and meeting a wider range of use case requirements. [Brief explanation of the drawings]

[0049] [Figure 1] 1 is a schematic flow diagram of a network integration control method according to an embodiment of the present disclosure (part 1); [Figure 2] 2 is a schematic flow diagram of a network integration control method according to an embodiment of the present disclosure (part 2); [Figure 3] FIG. 1 is a schematic diagram of the input and output of an xApp according to an embodiment of the present disclosure (part 1). [Figure 4] FIG. 2 is a schematic diagram of the input and output of the xApp of an embodiment of the present disclosure (part 2). [Figure 5] 1 is a flow diagram of a network integration control method according to an embodiment of the present disclosure (part 3); [Figure 6] FIG. 4 is a schematic flow diagram of a network integration control method according to an embodiment of the present disclosure (part 4). [Figure 7] 1 is a structural schematic diagram of a network integration control device according to an embodiment of the present disclosure (part 1); [Figure 8] FIG. 2 is a structural schematic diagram of a network integration control device according to an embodiment of the present disclosure (part 2); [Figure 9]1 is a structural schematic diagram of a network integration control device according to an embodiment of the present disclosure (part 3); [Figure 10] FIG. 4 is a structural schematic diagram of a network integration control device according to an embodiment of the present disclosure (part 4); DETAILED DESCRIPTION OF THE INVENTION

[0050] To clarify the technical problems, technical solutions, and advantages of the present disclosure, the following detailed description will be provided with reference to drawings and specific embodiments. In the following description, details such as specific configurations and components are described to facilitate understanding of the present disclosure. Therefore, it will be apparent to those skilled in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Note that known functions and configurations are omitted for clarity and conciseness.

[0051] It should be understood that references throughout the specification to "one embodiment" or "one embodiment" mean that a particular feature, structure, or characteristic associated with that embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of "in one embodiment" or "in one embodiment" in various places throughout the specification are not necessarily all referring to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0052] In various embodiments of the present disclosure, the order of the numbers of the following processes does not imply the order of execution, and the order of execution of each process should be determined by its function and internal logic, and does not constitute any limitation on the implementation process of the embodiments of the present disclosure.

[0053] The term "and / or" in the embodiments of the present disclosure describes a relation between related objects and indicates that three relations can exist, for example, A and / or B can indicate three cases, such as the presence of only A, both A and B, and only B. The symbol " / " generally indicates that the preceding and following related objects have an "or"-like relationship.

[0054] The term "plurality" in the embodiments of the present disclosure refers to two or more, and other quantifiers similar thereto.

[0055] Hereinafter, the technical solutions in the embodiments of the present disclosure will be clearly and completely described with reference to the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, but not all of the embodiments. Based on the embodiments of the present disclosure, any embodiments that can be obtained by a person skilled in the art without any creative effort fall within the scope of protection of the present disclosure.

[0056] Specifically, the embodiments of the present disclosure provide a network integration control method to solve the problem that the control methods in the related art cannot meet the requirements of multi-input multi-output synchronous configuration.

[0057] As shown in FIG. 1, an embodiment of the present disclosure provides a network integration control method applicable to Near-RT RIC, which specifically includes the following steps 11 to 12.

[0058] In step 11, a near-real-time radio access network intelligent controller (Near-RT RIC) sends a control request message to a network node, where the control request message includes related information of M control service types corresponding to control services and one or more control operations corresponding to each control service type, where M is an integer greater than or equal to 1. Optionally, M is greater than or equal to 2, that is, the multiple operations included in the control request message belong to different control service types.

[0059] The network node is a network node controlled by the near-real-time radio access network intelligent controller. The network node may be an E2 node, and the Near-RT RIC can control the E2 node via an E2 interface to realize RAN radio resource optimization. Specifically, when the Near-RT RIC controls the E2 node, it can send the control request message to the E2 node, and the control request message includes related information of multiple operations corresponding to multiple control service types. For example, the control request message includes operations a1, a2, and a3 corresponding to control service type 1 and operations b1, b2, and b3 corresponding to control service type 2.

[0060] By including multiple operations across service types and related information for the operations in the control request message, it is possible to realize a control request for multiple operations across service types and perform optimized configuration of radio resources for the operations being performed by the network node.

[0061] In step 12, the near real-time radio access network intelligent controller receives a control confirmation message sent from the network node, and the control confirmation message includes the execution result of each control operation in the M control service types of the network node.

[0062] Upon receiving the control request message, the network node feeds back the execution results for each operation in the different control service types included in the control request message, i.e., sends a control confirmation message to the near real-time radio access network intelligent controller, so that the near real-time radio access network intelligent controller performs subsequent processing.

[0063] An xApp is an application program loaded into the near real-time radio access network intelligent controller, and the xApp can realize RAN optimization functions. In an embodiment of the present disclosure, the operation corresponding to the control service is an operation for controlling a network node output from the xApp. For the xApp, the control request message and the control confirmation message include multiple control operations across service types, thereby achieving synchronous control of multiple operations at once and complying with the multi-input multi-output characteristics of the xApp.

[0064] According to the embodiments of the present disclosure, the control request message sent by the near-real-time radio access network intelligent controller to the network node it controls includes information related to multiple control operations across service types, and the control confirmation message fed back by the network node to the near-real-time radio access network intelligent controller includes the execution results of multiple operations across service types. In this way, the synchronous integrated optimization control of xApp's multi-input and multi-output is realized, which can effectively avoid problems such as the waste of interface resources and equipment processing failures caused by the interruption of some operations in a control process that is completed in a single operation sequence, thereby reducing the processing delay of the base station and the increased equipment processing complexity caused by failure handling and reconfiguration, thereby improving the optimization capability of the Near-RT RIC and meeting a wider range of use case requirements.

[0065] In the embodiment of the present disclosure, the process of cross-service type multi-action integrated control may be triggered by Insert or may be triggered internally by the near real-time radio access network intelligent controller. Specific embodiments will be described below.

[0066] In one alternative embodiment, if the control process is triggered by an Insert, the method further comprises: sending a subscription request message to the network node for subscribing to an insertion service, the subscription request message including operation definitions of one or more insertion operations corresponding to the M insertion service types to be subscribed; receiving an insertion instruction message sent from the network node, where the insertion instruction message includes related information of insertion operations corresponding to M insertion service types.

[0067] In this embodiment, before executing the control process, the near real-time radio access network intelligent controller subscribes to an Insert service, which includes multiple actions of multiple service types, to a network node. The subscription request message includes related information of multiple insertion actions corresponding to the subscription service, such as action definitions of the Insert actions and trigger events of the Insert actions. The multiple actions belong to different service types. Here, the action definitions (e.g., Insert Indication Actions) are used to indicate what the Insert Indication Message of the multiple actions needs to indicate.

[0068] When the network node receives the subscription request message, it detects based on a trigger event, and if a trigger event is detected, it stops the ongoing operation, performs the requested insert service, and feeds back an insert instruction message to the near real-time radio access network intelligent controller. The insert instruction message includes related information of multiple insertion operations across service types, thereby requesting the near real-time radio access network intelligent controller to control and optimize multiple operations across service types, thereby realizing insert and control services for multiple operations belonging to different service types.

[0069] Taking the control process as an example that is triggered by an Insert service, as shown in FIG. 2, the control method of the embodiment of the present disclosure may include steps 1 to 5.

[0070] In step 1, the Near-RT RIC first subscribes to the Insert service, i.e., sends a subscription request message (RIC Subscription Request) to the E2 node, providing information related to the subscription, for example, subscribing to an Insert action that is triggered under a predetermined event, where the Action Definition specifies multiple Insert Indication Actions and related parameters across the triggered service types.

[0071] Here, the operation definition includes related information of insert operations of multiple service types, for example, service types Insert Styles (X, Y) and multiple operations for each service type: Insert Styles X: Action a1, Action a2; Insert Styles Y: Action b1, Action b2, and may further include related parameters for each operation. Specifically, the operation definition may include at least one piece of information from the following (1) to (6).

[0072] (1) The number of required insert service types; indicates how many different insert service types are included in total. This can be in the form of a list, i.e., the required sequence of insert service types for multiple actions (Sequence of Insert Styles for Multiple Actions) is listed.

[0073] (2) Requested Insert Style, i.e., each inserted service type to be included. When the requested insert service type sequence is listed, the list includes each inserted service type to be included.

[0074] (3) The number of insert operations included in each insert service type; each insert service type can support multiple insert operations. When indicating the required insert service type sequence in a list, the list can also indicate the sequence of insert operations (Sequence of Insert Indication Action Definition) corresponding to each insert service type.

[0075] (4) Insertion Operation Identifier: Each insertion operation corresponding to each service type is indicated by a respective insertion operation identifier. Because the operation definition can be used to indicate the information content that needs to be included in the insertion indication message, the insertion operation identifier can also be referred to as an Insert Indication ID.

[0076] (5) The number of radio access network RAN ​​parameters for the insertion operation: each insertion operation has a corresponding RAN parameter, and the RAN parameters for each insertion operation can be represented as a list. Since the operation definition can be used to indicate the information content that needs to be included in the insertion indication message, it can also be represented as a RAN parameter list for the insertion indication (List of RAN parameters for Insert Indication).

[0077] (6) RAN parameter identifier: The RAN parameters corresponding to each insertion operation are each identified by a RAN parameter ID.

[0078] In this embodiment, an action definition including multiple actions across service types may be expressed in the form of a list. That is, a list (Sequence of Insert Styles for Multiple Actions) is formed by related information of multiple actions for different insertion service types, and the list includes actions corresponding to each insertion service type and information content corresponding to each action. The action definition may include one or more combinations of the above information content, and may also include other information content such as a user equipment identification (UE ID). Here, the number of requested insertion service types in the list may range from 1 to the maximum number of RIC types, the number of insertion actions included in each insertion service type may range from 1 to the maximum number of insertion actions, and the number of RAN parameters for each insertion action may range from 1 to the maximum number of RAN parameters related to the action.

[0079] In this embodiment, the action definition is exemplified as a list of action definitions of a plurality of actions, as shown in Table 1.

[0080] [Table 1]

[0081] In Table 1 above, "M" indicates mandatory presence, and "O" indicates whether presence is optional.

[0082] The symbols ">", ">>", and ">>>" indicate the hierarchy of each piece of information. For example, "requested insertion service type" is the next level of "multiple operation insertion service type sequence", i.e., the list of insertion service type sequences includes the requested insertion service type; "insertion operation identifier" and "RAN parameter list for insertion operation" are the next level of "sequence of insertion operations corresponding to insertion service types", and "RAN parameter identifier" is the next level of "RAN parameter list for insertion operation", i.e., the RAN parameter list includes the identifier of each RAN parameter. The message hierarchy in the remaining lists in the embodiments of the present disclosure can be inferred sequentially and will not be described in detail here.

[0083] Here, Table 1 shows the range constraints for the number of insertion service types requested, the number of insertion operations included in each insertion service type, and the number of RAN parameters associated with each insertion operation, and the definition of each range constraint is shown in Table 2.

[0084] [Table 2]

[0085] In step 2, the E2 Node feeds back a subscription response to the Near-RT RIC based on the subscription request message, and the subscription response includes the operations that the E2 node will receive, for example, a receive operation list (which may include a receive operation identifier).

[0086] In step 3, the E2 node performs a corresponding Insert operation based on the cross-service-type multiple operation information provided by the subscription request message, that is, performs trigger event detection.

[0087] In step 4, the E2 Node suspends any ongoing normal functioning process when it detects a corresponding trigger event, such as a change in radio resources (e.g., UE context, bearer context) occurring or needing to be established.

[0088] In step 5, the E2 node triggers corresponding Insert Indication Actions according to the instructions in the Action Definition. The Insert Indication Actions can be accompanied by multiple actions for different service types to request the Near-RT RIC to optimize and control the E2 node's own processes. For example, modifying the Data Radio Bearer (DRB) Quality of Service (QoS) and mapping QoS flows to the DRB can be performed simultaneously, thereby improving radio resource utilization and ensuring user QoS needs.

[0089] Specifically, the insertion indication message includes a first information element and a second information element, the first information element being, for example, a RIC indication header information element (RIC Indication Header IE), and the second information element being, for example, a RIC insertion indication message information element (RIC Indication Message IE). The first information element includes at least one of a terminal identifier (UE ID) corresponding to the network node, an insertion type of the insertion indication message, and an event trigger condition identifier, as shown in Table 3.

[0090] [Table 3]

[0091] Here, the Event Trigger Condition ID can be used to identify that an Insert is started under a specific event trigger condition.

[0092] Optionally, the insertion type is a multiple configuration control request. In Table 3 above, the insertion type "Insert Style M" indicated in the first information element is the multiple configuration control request, which is a newly defined insertion type that can combine multiple specific functional service types as needed. "Insert Style M" in Table 3 only indicates the number of the insertion type.

[0093] Specifically, the second information element may include at least one of the following 1) to 7).

[0094] 1) The number of insert service types indicated by the insert instruction message; indicates how many different insert service types are included in total. This can be indicated in the form of a list, i.e., the sequence of indicated insert styles included in the insert instruction message is indicated in a list.

[0095] 2) The inserted service type indicated by the insert instruction message (Indicated Insert Style), i.e., each inserted service type included. When the inserted service type sequence indicated by the insert instruction message is shown as a list, each indicated inserted service type is included in the list.

[0096] 3) The number of insertion operations included in each insertion service type; each insertion service type can correspond to multiple insertion operations, and when listing the insertion service type sequence indicated by the insertion indication message, the list can also include the sequence of insertion operations (Sequence of Insert Indication Action Definition) corresponding to each insertion service type.

[0097] 4) Insertion Operation Identifier: Each insertion operation corresponding to each insertion service type is indicated by an insertion operation identifier, which can be further indicated as an Insert Indication ID.

[0098] 5) Number of RAN parameters for insertion operation; each insertion operation has corresponding RAN parameters, and the RAN parameters for each insertion operation can be indicated in a list, which can be indicated as a RAN parameter list (List of RAN parameters requested) of the operation requesting control from the Near-RT RIC.

[0099] 6) RAN Parameter ID: The RAN parameters corresponding to each insertion operation are identified by a RAN Parameter ID.

[0100] 7) RAN Parameter Value Type.

[0101] The RIC Indication Message IE may include one or more of the above information. The RIC Indication Message IE for multiple cross-service type operations may be expressed in the form of a list. That is, the second information elements corresponding to multiple operations are formed as a list, and the list is as shown in Table 4.

[0102] [Table 4]

[0103] In the above Table 4, the number of insertion service types indicated by the insertion instruction message, the number of insertion operations corresponding to the insertion service types, and the number ranges corresponding to the number of RAN parameters of the insertion operations are shown, and the number ranges can be defined as shown in Table 5.

[0104] [Table 5]

[0105] Here, the Insertion Service Type Sequence in Table 4 indicates a series of specified Insert Styles carried by the Insertion Type M during the Insert process, and multiple Insert Actions are supported under various Indicated Insert Styles, and each Insert Action is identified using an Insert Indication ID. The RAN Parameter List is the configuration parameter type that can be attached to the Insert Action.

[0106] Through the above steps 1 to 5, insert operations for multiple control actions belonging to multiple insertion service types are configured during the subscription process of the E2 node. When a specified event is triggered based on the insert operations required for the subscription, the E2 node pauses the normal process and triggers an insert indication message based on the insert operations indicated by the multiple insert indication IDs and related RAN parameters to request control operations and parameter configurations for the specified multiple service types from the Near-RT RIC. In this insert process, to realize radio resource control support for multiple insert actions across service types, the RIC Indication Header IE and RIC Indication Message IE, which are important information elements in the RIC Indication message in step 5, can be organized into the formats shown in Tables 3 and 4, respectively. Based on the above process and message mechanism, the Near-RT RIC can subscribe to the Insert service, whereby the E2 Node pauses a functional entity process and simultaneously notifies the Near-RT RIC of multiple subsequent operations that can be performed for optimization control, thereby facilitating the Near-RT RIC to perform RAN resource analysis and radio resource configuration optimization control operations, and achieving the purpose of RRM intelligent optimization control.

[0107] In step 6, the Near-RT RIC optimizes and controls the E2 Node's original process based on the synchronization configuration request in the insertion instruction message, and the control service includes a combination of integrated control of multiple operations across corresponding service types.

[0108] Specifically, step 6 includes steps 6.1 and 6.2.

[0109] In step 6.1, the control request message is sent to the network node based on the insertion instruction message, that is, the Near-RT RIC sends a control request message (RIC Control Request) to the E2Node.

[0110] In step 6.2, the Near-RT RIC receives a control acknowledgement message (RIC Control Acknowledge) sent from the network node. That is, the E2 node receives the control request, feedbacks the execution results of each control operation among the multiple operations in the multiple control styles, and sends a RIC Control Acknowledge message to the Near-RT RIC, allowing the Near-RT RIC to perform subsequent processing.

[0111] Specifically, the control request message includes a third information element and a fourth information element, where the third information element may be a RIC Control Header Information Element (RIC Control Header IE), and the fourth information element may be a RIC Control Message Information Element (RIC Control Message IE). The third information element includes at least one of a terminal identifier (UE ID) corresponding to the network node, a control type of the control request message, and a control decision of a control operation. Here, the control decision included in the third information element is used to indicate the acceptance status of at least one control operation in the RIC control message information element. In one specific embodiment, the control decision of the control operation is used to indicate the acceptance status of all control operations in the RIC control message information element, and belongs to one overall processing style. The control type is multiple configuration control, which can be represented as Control Service Style N as shown in Table 6.

[0112] [Table 6]

[0113] In Table 6 above, Multiple Configuration Control is a newly defined control service type to realize free combination of operation control across service types, and multiple specific functional service types to be controlled can be combined according to control needs. Control Service Style N is the number of "Multiple Configuration Control".

[0114] Specifically, the fourth information element may include at least one of the following 1) to 8).

[0115] 1) The number of control service types indicated by the control request message: indicates how many different inserted service types are included in total. This can be indicated in the form of a list, i.e., indicates the inserted service type sequence (Sequence of Control Styles) included in the control request message.

[0116] 2) Control service type indicated by the control request message (Indicated Control Style for Multiple Actions): that is, each control service type included. When the control service type sequence indicated by the control request message is shown as a list, each indicated control service type is included in the list.

[0117] 3) The number of control actions included in each control service type; each control service type can correspond to multiple control actions, and when the control service type sequence indicated by the control request message is listed, the list can show the sequence of control actions corresponding to each control service type.

[0118] 4) Control Action Identifier: Each control action corresponding to each control service type is indicated by a control action identifier (Control Action ID).

[0119] 5) Control decision of a control action (RIC Control decision): The control decision is used to indicate the acceptance status for one of the actions in the RIC control message information element.

[0120] 6) Number of RAN parameters of the control operation; each control operation has a corresponding RAN parameter, and the RAN parameters of each control operation can be shown in a list, which can be shown as a RAN parameter list (List of RAN parameters) of the operation for which control is requested.

[0121] 7) RAN Parameter ID: The RAN parameters corresponding to each control operation are identified by a RAN Parameter ID.

[0122] 8) RAN Parameter Value Type.

[0123] The RIC Control Message IE may be expressed in the form of a list. That is, control information for multiple operations across service types is formed as a list, for example, an Insertion Service Type Sequence (Sequence of Control Styles). The list includes each control service type, control operations included in each control service type, and RAN parameters corresponding to each control operation. Here, the number of control service types may be in the range of, for example, 1 to the maximum number of service types, the number of control operations may be in the range of, for example, 1 to the maximum number of control operations, and the number of RAN parameters may be in the range of, for example, 1 to the maximum number of associated RAN parameters. The fourth information element may be as shown in Table 7.

[0124] [Table 7]

[0125] In Table 7 above, "RAN Parameter Identifier" and "RAN Parameter Value Type" are the next level of "RAN Parameter List", where RAN Parameter Identifier contains the identifier of each RAN parameter, and RAN Parameter Value Type contains the type of each RAN parameter value. The column for Number of RAN Parameters gives the limit range of the number of RAN parameters.

[0126] In Table 7 above, range constraints for the number of control actions and the number of RAN parameters are shown, and the definition of each range constraint is shown in Table 8.

[0127] [Table 8]

[0128] In Table 7, the Sequence of Control Styles in the RIC Control Message represents other Control Styles designated to be controlled within the Control Style N. Multiple Control Actions can be supported under each designated Control Style, and each Control Action is identified by a Control Action ID. For each Control Action, the RIC Control decision is used to indicate whether to accept the Control Action indicated by the Insert Indication ID attached to the Indication message when the Control Action is used as a response to the Insert service. In this case, the List of RAN parameters is a configuration parameter that can be attached under the Control Action. In particular, if the RIC Control decision is "reject," it indicates that the control action has not been accepted by the Near-RT RIC, and RAN parameters may not be attached.

[0129] In step 6.2, the control confirmation message may include at least one of the following 1) to 7).

[0130] 1) The number of control service types included in the control confirmation message; indicates how many different control service types are included in total in the control confirmation message. This can be in the form of a list, i.e., a list of control service type sequences (Sequence of Control Styles) including the requested service types.

[0131] 2) The control service type (Indicated Control Style) included in the control confirmation message, that is, each control service type included. When the control service type sequence is indicated by a list, each inserted service type is included in the list.

[0132] 3) The number of execution results included in the control confirmation message; indicates whether the control confirmation message includes the execution results of several operations. When the control service type sequence is represented by a list, the list can also represent the sequence of execution results (Sequence of Control Actions Outcome).

[0133] 4) Control Action ID: Each control action corresponding to each control service type is represented by a control action ID.

[0134] 5) Number of RAN parameters: each control operation has a corresponding RAN parameter, and the RAN parameters of each control operation can be represented as a list (Sequence of RAN Parameters).

[0135] 6) RAN Parameter ID: The RAN parameters corresponding to each control operation are identified by a RAN Parameter ID.

[0136] 7) RAN Parameter Value Type (RAN Parameter Value).

[0137] In this embodiment, the control confirmation message may include one or more of the above information. The multiple service types and corresponding control operations included in the control confirmation message may be implemented in the form of a list. For example, the control service type sequence is shown in Table 9.

[0138] [Table 9]

[0139] Optionally, for each Control Action, if the network node receives an execution of a control action in step 6, the RAN parameter sequence is accompanied by a received timestamp of the control action. If a control action is not supported, there is no need to include the Control Action ID and related parameters.

[0140] For example, considering the multi-input multi-output characteristic of xApp, it can be stipulated that if all control actions are executed and valid, the control process is considered successful and a control acknowledgement message (RIC Control Acknowledge) feedback can be adopted; otherwise, the control process is considered unsuccessful and a control failure message (RIC Control Failure) feedback can be adopted.

[0141] The above steps 1 to 6 are an Insert-triggered Control process. The Insert service process is the input of the xApp for the Insert-triggered Control process. To achieve integrated control of multiple operations across service types of the xApp, each operation is configured as integrated control of multiple operations across service types according to needs during the Insert service subscription process. For example, the insertion type indicated by the insertion instruction message in step 5 is configured as "Insert Style M," i.e., a "multiple configuration control request." Accordingly, the Control service process is the output of the xApp. To achieve integrated control of multiple operations across service types of the xApp, integrated control of multiple operations across service types is synchronously executed during the Control service control process. For example, the control type indicated by the control request message in step 6 is "Control Style N," i.e., "multiple configuration control." The following describes how to define the insertion type and the control type.

[0142] For example, assume that the service types include Style X, Style Y, and Style Z. Style X includes Indication actions a1 and a2, Style Y includes Indication actions b1 and b2, and Style Z includes Indication actions c1 and c2. As shown in Figure 3, to achieve multi-input, multi-output processing for xApp loaded in the Near-RT RIC, it is necessary to achieve multi-action integrated control across service types for input (i.e., Insert) and output (i.e., Control). That is, Indication actions a1, a2, b1, b2, c1, and c2 are synchronously collected, and Control actions a1, a2, b1, b2, c1, and c2 are synchronously output. The Insert and Control processes within the E2 interface must be optimized to meet the needs of xApp multi-input, multi-output processing.

[0143] In the subscription process of an insertion service, each Insert Action can be configured as a cross-service type multi-action integrated control as needed. Accordingly, the Near-RT RIC can integrate the configuration of the corresponding control process for multiple insertion service type multi-actions input, and synchronize the configuration of multi-actions and corresponding parameters under multiple control service types, thereby realizing flexible configuration optimization of RAN resources.

[0144] As shown in Table 10, E2SM-RC classifies multiple Insert Styles for Insert Service based on functional classification, and proposes a new Insert Style M, i.e., multiple configuration control request, at the E2SM-RC layer level to realize flexible combination of multiple Insert Styles and corresponding Insert Indication Actions across functional classifications. Note that, to avoid restrictions on service type extension, the Insert Style number is set to M, and can take values ​​according to the number situation of the subsequent Insert Style, as shown in Figure 3.

[0145] In the Insert service process, Insert Style M can be used to combine multiple specific functional service types (e.g., Insert Styles 1-7 in Table 10) and the Insert Indication actions supported by these service types as needed. Other Insert Styles can be implemented in the message mode of Insert Style M to achieve synchronous integration.

[0146] [Table 10]

[0147] Accordingly, E2SM-RC also classifies control services into multiple Control Styles based on their functional classification. To enable free combinations across control service functional types, a new Control Style N, i.e., multiple configuration control, is proposed for the Control service. Note that the Control Style number is set to N as shown in Table 11, and can take on values ​​based on the status of the subsequent Control Style number as shown in Figure 3.

[0148] [Table 11]

[0149] The control process uses Control Style N to combine specific functional service types to be controlled (e.g., Control Styles 1 to 8 in Table 11) with the control actions supported by these service types as needed. The message mode of Control Style N can incorporate other control styles to be controlled, allowing for flexible configuration of service type and corresponding action combinations, providing scalability for the Near-RT RIC optimization process and enhancing optimization capabilities. The E2 node realizes a one-time synchronization process optimization configuration based on the integrated configuration of multiple service types and multiple actions, reducing processing delays, improving the quality of collected data, adapting to the multi-input / multi-output characteristics of xApp, enhancing intelligent control capabilities, and optimizing intelligent control effects. The base station can synchronously process and execute the integrated control commands output by xApp, eliminating the need for rollbacks or reconfigurations due to potential failures during a single sequential execution process. This reduces the increased processing complexity in the processing flow, such as failure handling and reconfiguration, and improves the efficiency of resource configuration.

[0150] A specific implementation of the control method according to the embodiment of the present disclosure used in the Control process triggered by the Insert service will be described below.

[0151] In this embodiment, the method for controlling multiple operations across service types can support the following situations 1) to 3).

[0152] Case 1: Single operation across service types 1) Style X: Action x1 2) Style Y: Action y1 Case 2: Combination of single and double operations across service types 1)Style X: Action x1, Action x2 2) Style Y: Action y1 Case 3: Combining multiple operations across service types 1)Style X: Action x1, Action x2 2)Style Y: Action y1, Action y2

[0153] For QoS optimization use cases, integrated control of radio bearers and radio access can be realized, that is, the mapping relationship between DRB parameters and QoS flows can be configured synchronously, and UE access control can be configured at the same time.

[0154] The input of this process is the relevant content attached to the Insert service, that is, Insert triggers the Near-RT RIC to initiate a Control Request command, and using Insert Style M, the key information elements included in the Insert Instruction message are as shown in Table 12.

[0155] [Table 12]

[0156] The contents of the RIC Indication Message can be set as shown in Table 13.

[0157] [Table 13]

[0158] As shown in Table 13 above, the Indication Message has two Insert Styles, namely, Style 1: Radio Bearer Control and Style 4: Radio Access Control, configured synchronously. For each Insert Style, multiple Indication Actions can be configured, and each Insert Indication Action that requires configuration includes the parameters that require configuration. For example, for Style 1: Radio Bearer Control, two actions, namely, DRB QoS configuration and QoS Flow mapping, are configured synchronously, and each action includes the configured parameters. For Style 4: Radio Access Control, one action, namely, UE Admission Control, can be configured.

[0159] The control process triggered by the Insert can provide corresponding configuration values ​​based on the control action requested in the Insert message, and the details (parts) of the RIC Control Message can be set as shown in Table 14. Compared with the control process triggered by the Near-RT RIC internal trigger, for each Control Action, the RIC Control decision indicates whether to accept the control action requested in the Insert. If not accepted, the RIC Control decision can be configured as reject, so there is no need to attach the corresponding RAN parameters.

[0160] [Table 14]

[0161] In this embodiment, for the Control process triggered by the Insert service, the Control process may be triggered by the near real-time radio access network intelligent controller.

[0162] In one alternative embodiment, sending the control request message to the network node includes sending the control request message to the network node when a trigger event is detected, that is, a Control process can be triggered when a Near-RT RIC detects a trigger event.

[0163] In this embodiment, the Control process is the output of xApp, and the input of xApp can be Report. Assuming that the input during xApp multi-input multi-output processing is Report, the Control process uses a Near-RT RIC internal trigger as its output, and the Control process triggered by the Near-RT RIC needs to realize integrated control of multiple operations across service types. For example, assuming that service types include Style X, Style Y, and Style Z, Style X includes Indication actions a1 and a2, Style Y includes Indication actions b1 and b2, and Style Z includes Indication actions c1 and c2. As shown in FIG. 4, upon collecting reported UE and / or cell measurement information, Control Actions a1, a2, b1, b2, c1, and c2 are synchronously output. To meet the needs of xApp multi-input multi-output processing, the Control process triggered by the Near-RT RIC within the E2 interface needs to be optimized.

[0164] The Control process can use Control Style N to achieve flexible combination configuration of multiple service types and multiple operations.

[0165] For example, the control process is triggered by the Near-RT RIC, and the input can be report-related content. As shown in FIG. 5, the flow for triggering the Control process by the Near-RT RIC includes the following steps 1 to 4.

[0166] In step 1, the Near-RT RIC detects an internal trigger event (the internal trigger event may be a relevant RAN resource measurement result given based on an E2 Node report).

[0167] In step 2, the Near-RT RIC performs configuration of radio resource optimization control instructions based on a specific RRM optimization target.

[0168] In step 3, the Near-RT RIC sends a control request message to the E2 node, which may include information related to multiple operations of different service types, and optimizes the radio resource configuration for the relevant content performed by the E2 node through the control action indicated by the control action and the accompanying RAN parameters. Specifically, the control request message may include a third information element and a fourth information element. The third information element may be a RIC Control Header IE (details are shown in Table 6), and the fourth information element may be a RIC Control Message IE (details are shown in Table 7). The third information element may include at least one of a terminal identifier corresponding to the network node, a control type of the control request message, and a control decision. The control type is multiple configuration control, which may be represented as Control Service Style N and is not described here.

[0169] Since this is a control command triggered by an internal trigger of the Near-RT RIC, there is no need to feed back a control decision for the Insert action regardless of the Insert process, and there is no need to attach a Call Process ID.

[0170] In step 4, the E2 node receives the control request, feeds back the execution results of multiple control operations in multiple control styles, and sends a RIC Control Acknowledge message to the Near-RT RIC for subsequent processing. The control acknowledge message is shown in Table 9, and its description is omitted here.

[0171] Below, a specific implementation mode in which the control method of the embodiment of the present disclosure is used for the Control process triggered internally by the Near-RT RIC will be described.

[0172] For QoS optimization use cases, integrated control of radio bearers and radio access can be realized, that is, the mapping relationship between DRB parameters and QoS flows can be configured synchronously, and UE access control can be configured at the same time.

[0173] Assuming the input is reported cell-level / UE-level RAN side information, initiate a Control Request command independently from within the Near-RT RIC and not related to the Insert service process:

[0174] 1) The Near-RT RIC internal process initiates the control process and sends a RIC Control Request message containing a RIC Request ID, a RAN Function ID, a RIC Control Header, and a RIC Control Message IE.

[0175] Here, if Control Style N is adopted, the contents of the RIC Control Header can be set as shown in Table 15.

[0176] [Table 15]

[0177] The contents of the RIC Control Message can be set as shown in Table 16.

[0178] [Table 16]

[0179] The control message includes two Insert Styles, namely, Style 1: Radio Bearer Control and Style 4: Radio Access Control, which are synchronously configured. For Style 1: Radio Bearer Control, two Control Actions, namely, DRB QoS configuration and QoS Flow mapping, are synchronously configured, and each Control Action includes configured parameters. For Style 4: Radio Access Control, one Control Action, namely, UE Admission Control and corresponding RAN parameters, is configured.

[0180] 2) Upon receiving the Control Request message, the E2 node locates the target functional entity based on the RAN Function ID attached to the message, starts related processes based on the specific control commands and control parameters in the RIC Control Header and Control Message, and synchronously executes related control operations to achieve optimized configuration of radio resources. The E2 node can feed back the execution results to each control action in each control style according to the processing status.

[0181] In the embodiments of the present disclosure, a Control process triggered by an Insert service and a Control process triggered by a Near-RT RIC internal trigger are described, and the Control process is the output of xApp, and the input to xApp may be Insert or Report, but Insert and Report may also be input simultaneously, or another RIC service process may be input, and the present disclosure is not limited thereto.

[0182] In addition, in the embodiment of the present disclosure, when an insertion operation of an operation of a target insertion service type is requested during an insertion service subscription, an operation control of a target control service type corresponding to the target insertion service type is performed during the control service. For example, when the subscription request message includes the service type Style M (multiple configuration control request) shown in Table 10, the corresponding operation control is performed using Control Style N (multiple configuration control) shown in Table 11 during the control service process. That is, the insertion operation requested in the insertion service process corresponds to the control operation in the control service process.

[0183] According to the embodiments of the present disclosure, the cross-service type multi-action integrated control method triggered by Insert or inside the Near-RT RIC can realize synchronous integrated optimization control of xApp multi-input and multi-output, and provides a corresponding E2 interface level insertion and cross-service type multi-action integrated configuration method and message mechanism within the control flow, solving the problem in the related art that Insert and Control in the wireless network intelligent architecture are limited by service type classification and cannot realize intelligent application integrated control, and can effectively avoid problems such as interface resource waste and equipment processing failure due to the interruption of some operations within a control process completed in a single operation sequence, reducing base station processing delays and the increased equipment processing complexity caused by fault handling and reconfiguration, thereby improving the optimization capabilities of the Near-RT RIC and meeting a wider range of use case requirements.

[0184] As shown in FIG. 6, the embodiment of the present disclosure further provides a network integration control method applied to a network node, which includes the following steps 61 to 62.

[0185] In step 61, the network node receives a control request message sent from a near-real-time radio access network intelligent controller, the control request message including M control service types corresponding to the control services and related information of one or more control operations corresponding to each control service type, where M is an integer greater than or equal to 1.

[0186] In step 62, the network node sends a control confirmation message to the near real-time radio access network intelligent controller based on the control request message, and the control confirmation message includes the execution results of the network node for each control operation in the M control service types.

[0187] In this embodiment, the network node is a network node controlled by the near-real-time radio access network intelligent controller. The network node may be an E2 node, and a Near-RT RIC can control the E2 node via an E2 interface to realize RAN radio resource optimization. Specifically, when controlling the E2 node, the Near-RT RIC can send the control request message to the E2 node, and the control request message includes related information of multiple operations corresponding to multiple control service types.

[0188] Upon receiving the control request message, the network node feeds back the execution results for each operation in the different control service types included in the control request message, i.e., sends a control confirmation message to the near real-time radio access network intelligent controller, so that the near real-time radio access network intelligent controller performs subsequent processing.

[0189] An xApp is an application program loaded into the near real-time radio access network intelligent controller, and the xApp can realize RAN optimization functions. In an embodiment of the present disclosure, the operation corresponding to the control service is an operation for controlling a network node output from the xApp. For the xApp, the control request message and the control confirmation message include multiple control operations across service types, thereby achieving synchronous control of multiple operations at once and complying with the multi-input multi-output characteristics of the xApp.

[0190] According to an embodiment of the present disclosure, a network node receives a control request message sent from a Near-RT RIC, the control request message including relevant information for multiple control operations across service types; the network node feeds back a control confirmation message to the Near-RT RIC, the control confirmation message including the execution results of multiple operations across service types; in this way, the synchronous integrated optimization control of xApp's multi-input and multi-output is realized, and problems such as the waste of interface resources and equipment processing failures due to the interruption of some operations in a control process completed in a single operation sequence can be effectively avoided, the processing delay of the base station can be reduced, and the increased complexity of equipment processing due to failure handling and reconfiguration can be reduced, the optimization capability of the Near-RT RIC can be improved, and a wider range of use case requirements can be met.

[0191] In the embodiment of the present disclosure, the process of cross-service type multi-action integrated control may be triggered by Insert or may be triggered internally by the near real-time radio access network intelligent controller. Specific embodiments will be described below.

[0192] In one alternative embodiment, when the control process is triggered by Insert, the Near-RT RIC sends a subscription request message to the network node to subscribe to an Insert service, and the method further comprises: receiving a subscription request message sent from the network node, the near real-time radio access network intelligent controller, the subscription request message including operation definitions of one or more insertion operations corresponding to the M insertion service types to be subscribed; Sending an insertion instruction message to the near real-time radio access network intelligent controller, where the insertion instruction message includes related information of insertion operations corresponding to the M insertion service types.

[0193] In this embodiment, before executing the control process, the Near-RT RIC subscribes to an Insert service, which includes multiple operations of multiple service types, to a network node. The subscription request message includes information related to the multiple insertion operations corresponding to the subscription service, such as operation definitions of the Insert operations and trigger events of the Insert operations. The multiple operations belong to different service types. Here, the operation definitions (e.g., Insert Indication Actions) are used to indicate the contents that the Insert Indication Message of the multiple operations needs to indicate.

[0194] When the network node receives the subscription request message, it detects based on a trigger event, and if a trigger event is detected, it stops the ongoing operation, performs the requested insert service, and feeds back an insert instruction message to the Near-RT RIC. The insert instruction message includes related information of multiple insertion operations across service types, thereby requesting the near-real-time radio access network intelligent controller to control and optimize multiple operations across service types, thereby realizing insert and control services for multiple operations belonging to different service types.

[0195] As an example in which the control process is triggered by an Insert service, as shown in FIG. 2, the control method of the embodiment of the present disclosure may include steps 1 to 5.

[0196] In step 1, the Near-RT RIC first subscribes to the Insert service, i.e., sends a subscription request message (RIC Subscription Request) to the E2 node and provides information related to the subscription, and the subscription request message includes multiple operations for multiple service types.

[0197] Optionally, the action definition comprises: the number of requested inserted service types, The requested insertion service type, the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, The information includes at least one of the RAN parameter identifiers.

[0198] In step 2, the E2 Node feeds back a subscription response to the Near-RT RIC based on the subscription request message, and the subscription response includes the operations that the E2 node will receive, for example, a receive operation list (which may include a receive operation identifier).

[0199] In step 3, the E2 node performs a corresponding Insert operation based on the cross-service-type multiple operation information provided by the subscription request message, that is, performs trigger event detection.

[0200] In step 4, the E2 Node suspends any ongoing normal functioning process when it detects a corresponding trigger event, such as a change in radio resources (e.g., UE context, bearer context) occurring or needing to be established.

[0201] In step 5, the E2 node triggers a corresponding insertion instruction message according to the instruction in the operation definition. The insertion instruction message can be accompanied by multiple operations of different service types to request the Near-RT RIC to optimally control the E2 node's own process. Optionally, the insertion instruction message includes a first information element and a second information element, The first information element includes at least one of a terminal identifier corresponding to the network node, an insertion type of the insertion instruction message, and an event trigger condition identifier, and the insertion type is a multiple configuration control request.

[0202] The second information element is the number of insertion service types indicated by the insertion indication message; an insertion service type indicated by the insertion indication message; the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0203] In step 6, the Near-RT RIC optimizes and controls the E2 Node's original process based on the synchronization configuration request in the insertion instruction message, and the control service includes a combination of integrated control of multiple operations across corresponding service types.

[0204] Specifically, step 6 includes steps 6.1 and 6.2.

[0205] In step 6.1, the control request message is sent to the network node based on the insertion instruction message. The network node receives the control request message sent from the Near-RT RIC.

[0206] Optionally, the control request message includes a third information element and a fourth information element; The third information element includes at least one of a terminal identifier corresponding to the network node, a control type of the control request message, and a control decision, where the control type is multiple configuration control.

[0207] The fourth information element is the number of control service types indicated by the control request message; a control service type indicated by the control request message; the number of control operations included in each control service type; control action identifier, Control decisions for control actions, the number of RAN parameters of the control operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0208] In step 6.2, the network node sends a control acknowledgement message to the Near-RT RIC, i.e., the E2 node receives the control request, feedbacks the execution results of each control operation among the multiple operations in the multiple control styles, and sends a RIC Control Acknowledgement message to the Near-RT RIC, allowing the Near-RT RIC to perform subsequent processing.

[0209] Optionally, the control confirmation message comprises: the number of control service types included in the control confirmation message; a control service type included in the control confirmation message; the number of execution results included in the control confirmation message; control action identifier, Number of RAN parameters, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0210] The above steps 1 to 6 are the Insert-triggered Control process. The Insert service process is the input of the xApp to the Insert-triggered Control process. To achieve integrated control of multiple operations across service types of the xApp, each operation is configured as integrated control of multiple operations across service types according to needs during the Insert service subscription process. For example, the insertion type indicated by the insertion instruction message in step 5 is configured as "Insert Style M," i.e., a "multiple configuration control request." Accordingly, the Control service process is the output of the xApp. To achieve integrated control of multiple operations across service types of the xApp, integrated control of multiple operations across service types is synchronously executed during the Control service control process. For example, the control type indicated by the control request message in step 6 is "Control Style N," i.e., "multiple configuration control."

[0211] As an alternative embodiment, the control process may be further triggered by a near-real-time radio access network intelligent controller, i.e., triggering the control process when the Near-RT RIC detects a trigger event, for example, as shown in Figure 5, includes the following steps 1 to 4:

[0212] In step 1, the Near-RT RIC detects an internal trigger event (the internal trigger event may be a relevant RAN resource measurement result given based on an E2 Node report).

[0213] In step 2, the Near-RT RIC performs configuration of radio resource optimization control instructions based on a specific RRM optimization target.

[0214] In step 3, the Near-RT RIC sends a control request message to the E2 node, which may include related information for multiple operations of different service types, and realizes optimized configuration of radio resources for the related content performed by the E2 node through the control action indicated by the control action and the accompanying RAN parameters.

[0215] In step 4, the E2 Node receives the control request, feeds back the execution results of multiple control operations in multiple Control Styles, and sends a RIC Control Acknowledge message to the Near-RT RIC for subsequent processing by the Near-RT RIC.

[0216] According to an embodiment of the present disclosure, a network node receives a control request message sent from a Near-RT RIC, the control request message including relevant information for multiple control operations across service types; the network node feeds back a control confirmation message to the Near-RT RIC, the control confirmation message including the execution results of multiple operations across service types; in this way, the synchronous integrated optimization control of xApp's multi-input and multi-output is realized, and problems such as the waste of interface resources and equipment processing failures due to the interruption of some operations in a control process completed in a single operation sequence can be effectively avoided, the processing delay of the base station can be reduced, and the increased complexity of equipment processing due to failure handling and reconfiguration can be reduced, the optimization capability of the Near-RT RIC can be improved, and a wider range of use case requirements can be met.

[0217] In addition, all of the above embodiments related to network nodes applied to Near-RT RIC can be applied to the embodiments applied to the network node to achieve the same technical effect, and therefore, description thereof will be omitted here.

[0218] In the above embodiment, the integrated control method of the present disclosure is described, and in the following embodiment, the corresponding device will be further described with reference to the drawings.

[0219] Specifically, as shown in FIG. 7 , an embodiment of the present disclosure provides a network integration control device 700 adapted to a near-real-time radio access network intelligent controller, which includes a first transmitting unit 710 and a first receiving unit 720.

[0220] the first sending unit 710 is configured to send a control request message to a network node, the control request message including: M control service types corresponding to control services, and related information of one or more control operations corresponding to each control service type; the first receiving unit 720 is configured to receive a control confirmation message sent from the network node, the control confirmation message including an execution result of each control operation in the M control service types of the network node; Here, M is an integer of 1 or more.

[0221] Optionally, the device further includes a third transmitting unit and a third receiving unit; the third sending unit is configured to send a subscription request message to the network node for subscribing to an insertion service, the subscription request message including operation definitions of one or more insertion operations corresponding to the M insertion service types to be subscribed; The third receiving unit is configured to receive an insertion instruction message sent from the network node, where the insertion instruction message includes related information of insertion operations corresponding to M insertion service types.

[0222] Optionally, the action definition comprises: the number of requested inserted service types, The requested insertion service type, the number of insert operations included in each insert service type; an insert operation identifier, The number of radio access network RAN ​​parameters of the insertion operation; and The information includes at least one of the RAN parameter identifiers.

[0223] Optionally, the insertion instruction message includes a first information element and a second information element; the first information element includes at least one of a terminal identifier corresponding to the network node, an insertion type of the insertion instruction message, and an event trigger condition identifier; The second information element is the number of insertion service types indicated by the insertion indication message; an insertion service type indicated by the insertion indication message; the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0224] Optionally, the insert type is a multiple configuration control request.

[0225] Optionally, the first sending unit is specifically configured to send the control request message to the network node based on the insertion indication message.

[0226] Optionally, the control request message includes a third information element and a fourth information element; the third information element includes at least one of a terminal identifier corresponding to the network node, a control type of the control request message, and a control decision; The fourth information element is the number of control service types indicated by the control request message; a control service type indicated by the control request message; the number of control operations included in each control service type; control action identifier, Control decisions for control actions, the number of RAN parameters of the control operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0227] Optionally, the control decision is used to indicate a receipt status for at least one control action in a RIC control message information element.

[0228] Optionally, the control type is a multiple configuration control.

[0229] Optionally, the control confirmation message comprises: the number of control service types included in the control confirmation message; a control service type included in the control confirmation message; the number of execution results included in the control confirmation message; control action identifier, Number of RAN parameters, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0230] Optionally, the first sending unit is specifically configured to send the control request message to the network node when a trigger event is detected.

[0231] It should be noted that the above-mentioned device according to the embodiment of the present disclosure can implement all the method steps implemented in the method embodiment applied to the near-real-time radio access network intelligent controller and achieve the same technical effects, and therefore the same parts and beneficial effects as those of the method embodiment in this embodiment will not be specifically described here.

[0232] As shown in FIG. 8 , an embodiment of the present disclosure provides a network integration control device 800 applied to a network node, which may be an E2 node, and includes a second receiving unit 810 and a second sending unit 820.

[0233] The second receiving unit 810 is configured to receive a control request message sent from the near real-time radio access network intelligent controller, where the control request message includes: M control service types corresponding to the control services, and related information of one or more control operations corresponding to each control service type; the second sending unit 820 is configured to send a control confirmation message to the near real-time radio access network intelligent controller based on the control request message, the control confirmation message including an execution result for each control operation in the M control service types of the network node; Here, M is an integer of 1 or more.

[0234] Optionally, the device further includes a fourth receiving unit and a fourth transmitting unit; a fourth receiving unit configured to receive a subscription request message sent from the near real-time radio access network intelligent controller, the subscription request message including operation definitions of one or more insertion operations corresponding to the M insertion service types to be subscribed; A fourth sending unit is configured to send an insertion instruction message to the near real-time radio access network intelligent controller, where the insertion instruction message includes relevant information of insertion operations corresponding to the M insertion service types.

[0235] Optionally, the action definition comprises: the number of requested inserted service types, The requested insertion service type, the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, The information includes at least one of the RAN parameter identifiers.

[0236] Optionally, the insertion instruction message includes a first information element and a second information element; the first information element includes at least one of a terminal identifier corresponding to the network node, an insertion type of the insertion instruction message, and an event trigger condition identifier; The second information element is the number of insertion service types indicated by the insertion indication message; an insertion service type indicated by the insertion indication message; the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0237] Optionally, the insert type is a multiple configuration control request.

[0238] Optionally, the control request message includes a third information element and a fourth information element; the third information element includes at least one of a terminal identifier corresponding to the network node, a control type of the control request message, and a control decision; The fourth information element is the number of control service types indicated by the control request message; a control service type indicated by the control request message; the number of control operations included in each control service type; control action identifier, Control decisions for control actions, the number of RAN parameters of the control operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0239] Optionally, the control decision is used to indicate a receipt status for at least one control action in a RIC control message information element.

[0240] Optionally, the control type is a multiple configuration control.

[0241] Optionally, the control confirmation message comprises: the number of control service types included in the control confirmation message; a control service type included in the control confirmation message; the number of execution results included in the control confirmation message; control action identifier, Number of RAN parameters, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0242] It should be noted that the above-mentioned apparatus according to the embodiments of the present disclosure and the method embodiments applied to the above-mentioned network nodes can realize all the method steps realized and achieve the same technical effects, and therefore the same parts and beneficial effects as those of the method embodiments in this embodiment will not be specifically described here.

[0243] The division into units in the embodiments of the present disclosure is merely an example and is merely a division of logical functions, and may have a different division scheme when actually realized. Furthermore, each functional unit in each embodiment of the present disclosure may be integrated into a single processing unit, or each unit may exist physically independent, or two or more units may be integrated into a single unit. The integrated units may be realized in the form of hardware or software functional units.

[0244] The integrated unit may be realized in the form of a software functional unit and stored in a processor-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solution of the present disclosure, essentially or in part, contributing to the related art, or all or part of the technical solution, can be expressed in the form of a software product, and the computer software product is stored in a storage medium and includes several instructions that cause a computer device (which may be a personal computer, a server, a network device, etc.) or a processor to execute all or part of the steps of the method according to each embodiment of the present disclosure. The storage medium includes various media capable of storing program code, such as a USB flash disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0245] As shown in FIG. 9 , an embodiment of the present disclosure further provides a network integration control device applied to a near real-time radio access network intelligent controller, the device including a memory 920, a transceiver 900, and a processor 910, where the memory 920 is configured to store a computer program, the processor 910 is configured to read the computer program in the memory, and the transceiver 900 transmits and receives data under the control of the processor 910, sending a control request message to a network node, the control request message including M control service types corresponding to control services and related information of one or more control operations corresponding to each control service type; receiving a control confirmation message sent from the network node, the control confirmation message including an execution result of the network node for each control operation in the M control service types; Here, M is an integer of 1 or more.

[0246] Optionally, the transceiver further comprises: sending a subscription request message to the network node for subscribing to an insertion service, the subscription request message including operation definitions of one or more insertion operations corresponding to the M insertion service types to be subscribed; receiving an insertion instruction message sent from the network node, where the insertion instruction message includes related information of insertion operations corresponding to the M insertion service types.

[0247] Optionally, the action definition comprises: the number of requested inserted service types, The requested insertion service type, the number of insert operations included in each insert service type; an insert operation identifier, The number of radio access network RAN ​​parameters of the insertion operation; and The information includes at least one of the RAN parameter identifiers.

[0248] Optionally, the insertion instruction message includes a first information element and a second information element; the first information element includes at least one of a terminal identifier corresponding to the network node, an insertion type of the insertion instruction message, and an event trigger condition identifier; The second information element is the number of insertion service types indicated by the insertion indication message; an insertion service type indicated by the insertion indication message; the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0249] Optionally, the control decision is used to indicate a receipt status for at least one control action in a RIC control message information element.

[0250] Optionally, the insert type is a multiple configuration control request.

[0251] Optionally, the transceiver is further configured to perform transmitting the control request message to the network node based on the insertion indication message.

[0252] Optionally, the control request message includes a third information element and a fourth information element; the third information element includes at least one of a terminal identifier corresponding to the network node, a control type of the control request message, and a control decision; The fourth information element is the number of control service types indicated by the control request message; a control service type indicated by the control request message; the number of control operations included in each control service type; control action identifier, Control decisions for control actions, the number of RAN parameters of the control operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0253] Optionally, the control decision is used to indicate a receipt status for at least one control action in a RIC control message information element.

[0254] Optionally, the control type is a multiple configuration control.

[0255] Optionally, the control confirmation message comprises: the number of control service types included in the control confirmation message; a control service type included in the control confirmation message; the number of execution results included in the control confirmation message; control action identifier, Number of RAN parameters, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0256] Optionally, the transceiver is configured to perform sending the control request message to the network node if a trigger event is detected.

[0257] According to the embodiments of the present disclosure, the control request message sent by the near-real-time radio access network intelligent controller to the network node it controls includes information related to multiple control operations across service types, and the control confirmation message fed back by the network node to the near-real-time radio access network intelligent controller includes the execution results of multiple operations across service types. In this way, the synchronous integrated optimization control of xApp's multi-input and multi-output is realized, which can effectively avoid problems such as the waste of interface resources and equipment processing failures caused by the interruption of some operations in a control process that is completed in a single operation sequence, thereby reducing the processing delay of the base station and the increased equipment processing complexity caused by failure handling and reconfiguration, thereby improving the optimization capability of the Near-RT RIC and meeting a wider range of use case requirements.

[0258] 9, the bus architecture may include any number of interconnected buses and bridges, specifically connecting various circuits, such as one or more processors, represented by processor 910, and memory, represented by memory 920. The bus architecture may also connect various other circuits, such as peripherals, regulators, and power management circuits, which are well known in the art and will not be described further herein. The bus interface provides an interface. The transceiver 900 may include multiple elements, namely, a transmitter and a transceiver, to provide a unit for communicating with various other devices over a transmission medium. The processor 910 is responsible for managing the bus architecture and general processing, and the memory 920 may store data used by the processor 910 when performing operations.

[0259] The processor 910 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or a complex programmable logic device (CPLD), and the processor may employ a multi-core architecture.

[0260] It should be noted that the above-mentioned device according to the embodiment of the present disclosure can implement all the method steps implemented in the method embodiment applied to the near-real-time radio access network intelligent controller and achieve the same technical effects, and therefore the same parts and beneficial effects as those of the method embodiment in this embodiment will not be specifically described here.

[0261] 10 , an embodiment of the present disclosure further provides a network integration control device applied to a network node, which may be an E2 node, and includes a memory 1020, a transceiver 1000, and a processor 1010. Here, the memory 1020 is configured to store a computer program, the processor 1010 is configured to read the computer program in the memory, and the transceiver 1000 transmits and receives data under the control of the processor 1010, Receiving a control request message sent from a near real-time radio access network intelligent controller, where the control request message includes M control service types corresponding to control services and related information of one or more control operations corresponding to each control service type; The method is configured to: send a control confirmation message to the near real-time radio access network intelligent controller based on the control request message, wherein the control confirmation message includes an execution result of each control operation in the M control service types of the network node; Here, M is an integer of 1 or more.

[0262] Optionally, the transceiver further comprises: receiving a subscription request message sent from the near real-time radio access network intelligent controller, the subscription request message including operation definitions of one or more insertion operations corresponding to the M insertion service types to be subscribed; and sending an insertion instruction message to the near real-time radio access network intelligent controller, where the insertion instruction message includes relevant information of insertion operations corresponding to the M insertion service types.

[0263] Optionally, the action definition comprises: the number of requested inserted service types, The requested insertion service type, the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, The information includes at least one of the RAN parameter identifiers.

[0264] Optionally, the insertion instruction message includes a first information element and a second information element; the first information element includes at least one of a terminal identifier corresponding to the network node, an insertion type of the insertion instruction message, and an event trigger condition identifier; The second information element is the number of insertion service types indicated by the insertion indication message; an insertion service type indicated by the insertion indication message; the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insertion operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0265] Optionally, the insert type is a multiple configuration control request.

[0266] Optionally, the control request message includes a third information element and a fourth information element; the third information element includes at least one of a terminal identifier corresponding to the network node, a control type of the control request message, and a control decision; The fourth information element is the number of control service types indicated by the control request message; a control service type indicated by the control request message; the number of control operations included in each control service type; control action identifier, Control decisions for control actions, the number of RAN parameters of the control operation, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0267] Optionally, the control decision is used to indicate a receipt status for at least one control action in a RIC control message information element.

[0268] Optionally, the control type is a multiple configuration control.

[0269] Optionally, the control confirmation message comprises: the number of control service types included in the control confirmation message; a control service type included in the control confirmation message; the number of execution results included in the control confirmation message; control action identifier, Number of RAN parameters, RAN parameter identifier, and It includes at least one of the RAN parameter value types.

[0270] According to an embodiment of the present disclosure, a network node receives a control request message sent from a Near-RT RIC, the control request message including relevant information for multiple control operations across service types; the network node feeds back a control confirmation message to the Near-RT RIC, the control confirmation message including the execution results of multiple operations across service types; in this way, the synchronous integrated optimization control of xApp's multi-input and multi-output is realized, and problems such as the waste of interface resources and equipment processing failures due to the interruption of some operations in a control process completed in a single operation sequence can be effectively avoided, the processing delay of the base station can be reduced, and the increased complexity of equipment processing due to failure handling and reconfiguration can be reduced, the optimization capability of the Near-RT RIC can be improved, and a wider range of use case requirements can be met.

[0271] 10, the bus architecture may include any number of interconnected buses and bridges, specifically connecting various circuits, such as one or more processors, represented by processor 1010, and memory, represented by memory 1020. The bus architecture may also connect various other circuits, such as peripherals, regulators, and power management circuits, which are well known in the art and will not be described further herein. The bus interface provides an interface. The transceiver 1000 may include multiple elements, namely, a transmitter and a transceiver, to provide a unit for communicating with various other devices over a transmission medium. The processor 1010 is responsible for managing the bus architecture and general processing, and the memory 1020 may store data used by the processor 1010 when performing operations.

[0272] The processor 1010 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or a complex programmable logic device (CPLD), and the processor may employ a multi-core architecture.

[0273] It should be noted that the above-mentioned apparatus according to the embodiments of the present disclosure and the method embodiments applied to the above-mentioned network nodes can realize all the method steps realized and achieve the same technical effects, and therefore the same parts and beneficial effects as those of the method embodiments in this embodiment will not be specifically described here.

[0274] In addition, specific embodiments of the present disclosure further provide a processor-readable storage medium storing a computer program, which, when executed by a processor, realizes the steps of the network integration control method, and can achieve the same technical effect, so that the description will be omitted here to avoid duplication. Here, the readable storage medium may be any available medium or data storage device accessible by a processor, including, but not limited to, magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., laser disk (Compact Disk, CD), Digital Versatile Disk (DVD), Blu-ray (registered trademark) Disk (BD), High-Definition Versatile Disk (HVD)), and semiconductor memory (e.g., ROM, Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), non-volatile memory (NAND FLASH), solid state disk (SSD)).

[0275] Those skilled in the art will appreciate that embodiments of the present disclosure may be provided as a method, a system, or a computer program product. Therefore, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. The present disclosure may also take the form of a computer program product embodied in one or more computer-usable storage media (including, but not limited to, magnetic disk memory, optical memory, etc.) containing computer-usable program code.

[0276] The present disclosure will be described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present disclosure. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and combinations of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate an apparatus, and the instructions executed by the processor of the computer or other programmable data processing device generate an apparatus for implementing the function(s) specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.

[0277] These processor-executable instructions may be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, and the instructions stored in the processor-readable memory may produce an article of manufacture that includes an instruction apparatus, which implements the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0278] These processor-executable instructions may also be loaded into a computer or other programmable data processing device and cause the computer or other programmable device to perform a series of operational steps to produce a computer-implemented process, whereby the instructions executed by the computer or other programmable device provide steps for implementing the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0279] It should be understood that the division of each module described above is merely a division of logical functions, and that in actual implementation, all or part of the modules may be integrated into a single physical entity or physically separated. Furthermore, these modules may all be implemented in a form in which they are called by a software processing element, or all in a form of hardware, or some modules may be implemented in a form in which a processing element calls software, or some modules may be implemented in a form of hardware. For example, the decision module may be a separately established processing element, or may be integrated into a chip of the device, or may be stored in the memory of the device in the form of program code, and may be executed by a processing element of the device calling the function of the decision module. The same applies to the implementation of other modules. It should be noted that these modules may all or partly be integrated or implemented independently. The processing elements described herein may be integrated circuits capable of processing signals. In the implementation process, each step of the above method or each module may be completed by a hardware integrated logic circuit in a processor element or by instructions in software form.

[0280] For example, each module, unit, sub-unit, or sub-module may be configured as one or more integrated circuits that implement the above method, such as one or more application specific integrated circuits (ASICs), one or more microprocessors (digital signal processors (DSPs)), or one or more field programmable gate arrays (FPGAs). Furthermore, for example, when a certain module is implemented in a form in which a processing element calls a program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or a processor capable of calling other program code. Furthermore, for example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0281] Terms such as "first," "second," and the like in the specification and claims of this disclosure are not used to describe a particular order or sequence, but rather to distinguish between similar objects. It should be understood that such terms may be appropriately interchanged so that the embodiments of the disclosure described herein are performed in other orders than those illustrated or described herein. Furthermore, the terms "comprise" and "have," and any variations thereof, are intended to be non-exclusive. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly recited, but may include other steps or units not explicitly recited or inherent in the process, method, product, or apparatus. Furthermore, "and / or," as used in the specification and claims, means at least one of the connected objects. For example, A and / or B and / or C includes seven cases: A alone, B alone, C alone, both A and B present, both B and C present, both A and C present, and both A, B, and C present. Similarly, "at least one of A and B" as used in this specification and claims should be understood as "there is A alone, B alone, or both A and B."

[0282] Obviously, those skilled in the art can make various modifications and variations to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure also intends to include these modifications and variations.

Claims

1. A network integration control method, A near real-time radio access network intelligent controller sends a control request message to a network node, where the control request message includes related information of a plurality of control service types corresponding to control services and one or more control operations corresponding to each control service type; The near real-time radio access network intelligent controller receives a control confirmation message sent from the network node, the control confirmation message including an execution result of each control operation in the plurality of control service types of the network node.

2. The method further comprises: sending a subscription request message to the network node for subscribing to an insertion service, the subscription request message including a plurality of insertion service types to be subscribed to and operation definitions of one or more insertion operations corresponding to each insertion service type; 2. The method of claim 1, comprising: receiving an insertion instruction message sent from the network node, the insertion instruction message including a plurality of insertion service types and related information of an insertion operation corresponding to each insertion service type.

3. The operational definition is: the number of requested inserted service types, The requested insertion service type, the number of insert operations included in each insert service type; an insert operation identifier, the number of radio access network RAN ​​parameters of the insertion operation, and The method of claim 2 , including at least one information of a RAN parameter identifier.

4. the insertion instruction message includes a first information element and a second information element; the first information element includes at least one of a terminal identifier corresponding to the network node, an insertion type of the insertion instruction message, and an event trigger condition identifier; The second information element is the number of insertion service types indicated by the insertion indication message; an insertion service type indicated by the insertion indication message; the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insert operation, a RAN parameter identifier, and The method of claim 2 , including at least one of a RAN parameter value type.

5. transmitting the control request message to a network node, The method of claim 2 , further comprising: transmitting the control request message to the network node based on the insertion indication message.

6. the control request message includes a third information element and a fourth information element; the third information element includes at least one of a terminal identifier corresponding to the network node, a control type of the control request message, and a control decision; The fourth information element the number of control service types indicated by the control request message; a control service type indicated by the control request message; the number of control operations included in each control service type; control action identifier, Control decisions for control actions, the number of RAN parameters of the control operation, a RAN parameter identifier, and The method of claim 1 , including at least one of a RAN parameter value type.

7. 7. The method of claim 6, wherein the control decision is used to indicate a receive status for at least one control action corresponding to at least one insert service type in a RIC control message information element.

8. The method of claim 6 , wherein the control type is a multiple configuration control.

9. The control confirmation message the number of control service types included in the control confirmation message; a control service type included in the control confirmation message; the number of execution results included in the control confirmation message; control action identifier, Number of RAN parameters, a RAN parameter identifier, and The method of claim 1 , including at least one of a RAN parameter value type.

10. A network integration control method, A network node receives a control request message sent from a near real-time radio access network intelligent controller, the control request message including: a plurality of control service types corresponding to control services, and related information of one or more control operations corresponding to each control service type; The network node sends a control confirmation message to the near real-time radio access network intelligent controller based on the control request message, and the control confirmation message includes an execution result of each control operation in the plurality of control service types of the network node.

11. The method further comprises: receiving a subscription request message sent from the near real-time radio access network intelligent controller, the subscription request message including a plurality of insertion service types to be subscribed to and operation definitions of one or more insertion operations corresponding to each insertion service type; 11. The method of claim 10, comprising: sending an insertion instruction message to the near real-time radio access network intelligent controller, wherein the insertion instruction message includes a plurality of insertion service types and related information of insertion operations corresponding to each insertion service type.

12. The operational definition is: the number of requested inserted service types, The requested insertion service type, the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insert operation, The method of claim 11 , including at least one information of a RAN parameter identifier.

13. the insertion instruction message includes a first information element and a second information element; the first information element includes at least one of a terminal identifier corresponding to the network node, an insertion type of the insertion instruction message, and an event trigger condition identifier; The second information element is the number of insertion service types indicated by the insertion indication message; an insertion service type indicated by the insertion indication message; the number of insert operations included in each insert service type; an insert operation identifier, the number of RAN parameters for the insert operation, a RAN parameter identifier, and The method of claim 11 , including at least one of a RAN parameter value type.

14. the control request message includes a third information element and a fourth information element; the third information element includes at least one of a terminal identifier corresponding to the network node, a control type of the control request message, and a control decision; The fourth information element the number of control service types indicated by the control request message; a control service type indicated by the control request message; the number of control operations included in each control service type; control action identifier, Control decisions for control actions, the number of RAN parameters of the control operation, a RAN parameter identifier, and The method of claim 10 , including at least one of a RAN parameter value type.

15. 15. The method of claim 14, wherein the control decision is used to indicate a receipt status for at least one control action in a RIC control message information element.

16. The method of claim 14 , wherein the control type is a multiple configuration control.

17. A network integration control device, a first transmitting unit and a first receiving unit; the first sending unit is configured to send a control request message to a network node, the control request message including a plurality of control service types corresponding to control services and related information of one or more control operations corresponding to each control service type; A network integration control device, wherein a first receiving unit is configured to receive a control confirmation message transmitted from the network node, the control confirmation message including an execution result for each control operation in the plurality of control service types of the network node.

18. A network integration control device, a second receiving unit and a second transmitting unit; The second receiving unit is configured to receive a control request message sent from a near-real-time radio access network intelligent controller, the control request message including: a plurality of control service types corresponding to control services, and related information of one or more control operations corresponding to each control service type; The second sending unit is configured to send a control confirmation message to the near real-time radio access network intelligent controller based on the control request message, and the control confirmation message includes an execution result for each control operation in the plurality of control service types of the network node.

Images