Computer system, E2 node and method thereof

Abstract

A RAN Intelligent Controller (RIC) (1) configures a first subscription to a reporting service provided to an E2 node (2) between the RIC (1) and the E2 node (2). In the event that the first subscription has been configured, the RIC (1) sends a first message to the E2 node (2) that requests an update of one or both of an event trigger definition and an action definition that have been agreed in the first subscription in relation to the reporting action. For example, this may provide an enhancement to enable updating of a report type subscription on an open radio access network (O-RAN) E2 interface.

Description

Technical Field

[0001] The present disclosure relates to radio communication systems and in particular to an interface between a radio access network node and a control node, system or platform. Background Art

[0002] The Open Radio Access Network (O-RAN) Alliance is a community of mobile operators, vendors, and research and academic institutions, and its mission is to reshape the Radio Access Network (RAN) to be more intelligent, open, virtualized, and fully interoperable. The O-RAN Working Group 3 (WG3) has conducted technical discussions and provided technical specifications for a near real-time (near RT) RAN intelligent controller (RIC) and an E2 interface (e.g., see non-patent documents 1 to 6).

[0003] The Near RT RIC is a logical function that enables near real-time control and optimization of RAN elements and resources through fine-grained (e.g., user equipment (UE)-based, cell-based) data collection and actions on the E2 interface. The Near RT RIC hosts a collection of applications called xApps, and provides a collection of platform functions that are commonly used to support specific functions hosted by xApps. The collection of platform functions includes database and shared data layer (SDL), xApp subscription management, conflict mitigation, messaging infrastructure, interface termination, and application programming interface (API) enablement. The interface termination includes E2 termination, A1 termination, and O1 termination, which provide termination of the E2 interface, A1 interface, and O1 interface, respectively.

[0004] The E2 interface connects the Near RT RIC to one or more E2 nodes. An E2 node is a logical node that terminates the E2 interface. An E2 node is a RAN node that exposes one or more RAN functions to the Near RT RIC and hosted xApps. For NR access, the E2 node includes one or more O-RAN Central Unit-Control Plane (O-CU-CP), one or more O-RAN Central Unit-User Plane (O-CU-UP), one or more O-RAN Distributed Units (O-DU), or any combination thereof. On the other hand, for Evolved Universal Terrestrial Radio Access (E-UTRA) access, the E2 node includes one or more O-RAN eNodeBs (O-eNBs).

[0005] The E2 node provides one or more services to the near-RT RIC to allow access to messages and measurement results, or to allow control of the E2 node from the near-RT RIC, or both. These services are called RIC services. The RIC services provided by the E2 node and available for the near-RT RIC include four services: a report (REPORT) service, an insert (INSERT) service, a control (CONTROL) service, and a policy (POLICY) service. These RIC services can be combined in different ways to implement the E2 service model (E2SM). The E2 service model depends on the RAN functions and radio access technology (RAT) of the E2 node, and describes the functions in the E2 node that can be controlled by the near-RT RIC and the related processes. Currently, the E2 service model includes E2SM key performance measurements (E2SM-KPM), E2SM network interfaces (E2SM-NI), and E2SM RAN control (E2SM-RC).

[0006] The E2 interface provides E2 Application Protocol (E2AP) procedures that enable the exchange of control signaling information between endpoints, provide RIC services, and allow near-RT RIC and hosted xApp applications to use the set of services described in the E2 service model. These E2AP procedures include, but are not limited to, RIC subscription, RIC subscription deletion, RIC control, and RIC indication.

[0007] The Near RT RIC uses the RIC Subscription process to subscribe to reporting services, insertion services, or policy services. For reporting services, the Near RT RIC platform function (i.e., xApp Subscription Management) receives a subscription request from the xApp via the E2 related API. The request from the xApp specifies a list of E2 nodes, RAN functions, event triggers, and action lists. In response to the request from the xApp, the platform function (i.e., xApp Subscription Management and E2 Termination) uses the RIC Subscription process to request the E2 node to send an INDICATION message to the Near RT RIC.

[0008] The xApp subscription management in the near-RT RIC is able to merge multiple identical subscriptions related to the reporting service from different xApps into a single subscription toward the E2 node (e.g., see Section 9.3.2.1 in Non-Patent Literature 1). Specifically, the xApp subscription management detects whether the new subscription requested by the xApp via the E2-related API is a duplication of an existing subscription that has been configured, created, or established with the E2 node (or is identical to the existing subscription). In other words, the xApp subscription management detects whether the new subscription requested by the xApp has the same content as the existing subscription. If the new subscription is a duplication of an existing subscription, the xApp subscription management does not perform a redundant RIC subscription process for the E2 node to add the duplicate subscription. Instead, the xApp subscription management only requests E2 to terminate the addition of the xApp ID of the new xApp to the distribution list associated with the existing subscription, and sends the subscription response (success) to the new xApp via the E2-related API.

[0009] In other words, xApp subscription management allows the merging of multiple identical subscriptions related to reporting services.

[0010] Citation List

[0011] Non-patent literature

[0012] Non-patent document 1: O-RAN.WG3.RICARCH-v02.01 “O-RAN Working Group 3 Near-Real-time RAN Intelligent Controller Near-RT RIC Architecture”, March 2022

[0013] Non-patent document 2: O-RAN.WG3.E2GAP-v02.01 “O-RAN Working Group 3Near-Real-time RAN Intelligent Controller Architecture&E2 General Aspects and Principles”, March 2022

[0014] Non-patent document 3: O-RAN.WG3.E2AP-v02.01 “O-RAN Working Group 3, Near-Real-time RAN Intelligent Controller, E2 Application Protocol (E2AP)”, March 2022

[0015] Non-patent document 4: O-RAN.WG3.E2SM-v02.01 “O-RAN Working Group 3Near-Real-timeRAN Intelligent Controller E2 Service Model (E2SM)”, March 2022

[0016] Non-patent document 5: O-RAN.WG3.E2SM-KPM-v02.01 “O-RAN Working Group3 Near-Real-time RAN Intelligent Controller E2 Service Model (E2SM) KPM”, March 2022

[0017] Non-patent document 6: O-RAN.WG3.E2SM-RC-v01.01 “O-RAN Working Group 3Near-Real-time RAN Intelligent Controller E2 Service Model (E2SM), RAN Control”, March 2022 Summary of the invention

[0018] Problem that the invention aims to solve

[0019] The inventors explored the technical specifications of the near-RT RIC and E2 interfaces and found several problems. One of these problems is related to xApp subscription management. As described above, xApp subscription management allows the merging of multiple identical subscriptions related to reporting services. This can help avoid redundant E2AP transactions between near-RT RIC and E2 nodes. xApp subscription management can also allow E2 nodes to avoid unnecessary actions of sending multiple identical RIC indication (RIC INDICATION) messages using the same trigger. However, if the new subscription requested by the xApp is not exactly the same as the existing subscription, the RIC subscription process is performed for the new subscription, and the E2 node should additionally send a RIC indication message for the new subscription. This may lead to the problem of not being able to fully reduce the number of RIC indication messages that the E2 node should send.

[0020] Consider several cases where the trigger definition and action definition of a new subscription partially overlap with the trigger definition and action definition of an existing subscription. One example is that multiple subscriptions have the same trigger definition (e.g., the same reporting period for periodic reporting, or the same trigger event for aperiodic reporting), but have different action definitions (e.g., different measurement items, different specific cell designations, or different specific (one or more than one) UE designations). In this case, the E2 node needs to send multiple RIC indication messages with different contents at the same time based on the same trigger definition. If these multiple RIC indication messages can be integrated into one RIC indication message, the load on the E2 node can be reduced.

[0021] In other cases, there may be multiple subscriptions with the same action definition but different trigger definitions. For example, if the reporting period of the first subscription is an integer multiple of the reporting period of the second subscription, the E2 node may need to send multiple RIC indication messages with the same content at the same time.

[0022] Other issues discovered by the inventors are related to updating report type subscriptions. In the current O-RAN WG3 technical specifications, report type subscriptions cannot be updated or modified. If a report type subscription needs to be updated or modified, the previously created subscription must first be deleted. Specifically, the xApp should first request the xApp subscription management to delete the existing report type subscription, and then request the xApp subscription management to create a new, updated report type subscription.

[0023] This limitation on updates to report type subscriptions in the current O-RAN WG3 technical specification may be a necessary trade-off to allow internal merging of multiple identical subscriptions. This is because, while multiple identical subscriptions from multiple xApps are internally merged into a single subscription towards the E2 node, if that single subscription is updated in response to a request from one of these xApps, the remaining xApps will no longer be able to receive indications generated by the desired trigger or with the desired content. Resolving these issues and allowing updates to existing report type subscriptions can potentially help reduce the number of E2AP transactions required to update report type subscriptions.

[0024] One of the purposes of the example embodiments disclosed herein is to provide devices, methods and programs that help solve at least one of the multiple problems including the above-mentioned problems. It should be noted that this purpose is only one of the purposes of the example embodiments disclosed herein. Other purposes or problems and novel features will become apparent from the following description and drawings.

[0025] Solutions for solving problems

[0026] In a first aspect, a computer system comprises: at least one memory; and at least one processor coupled to the at least one memory. The at least one processor is configured to provide a plurality of platform functions associated with a RIC. The at least one processor is configured to configure, create or establish a first subscription to a reporting service provided to the E2 node between the RIC and an E2 node. The at least one processor is further configured to, when the first subscription has been configured, created or established, send a first message to the E2 node, the first message requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription.

[0027] In a second aspect, a method performed by a computer system comprises the following steps:

[0028] (a) Provide multiple platform functions associated with RIC;

[0029] (b) configuring, creating or establishing, through the plurality of platform functions, between the RIC and the E2 node, a first subscription to a reporting service provided to the E2 node; and

[0030] (c) when the first subscription has been configured, created or established, sending a first message to the E2 node, the first message requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription.

[0031] In a third aspect, an E2 node comprises: at least one memory; and at least one processor coupled to the at least one memory. The at least one processor is configured to configure, create or establish a first subscription to a reporting service provided to the E2 node between the RIC and the E2 node. The at least one processor is configured to receive a first message from the RIC when the first subscription has been configured, created or established, the first message requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription. The at least one processor is also configured to update the content of a RIC indication message associated with the reporting action, or a trigger condition for sending a RIC indication message associated with the reporting action, or both, based on the first message.

[0032] In a fourth aspect, a method performed by an E2 node comprises the following steps:

[0033] (a) configuring, creating or establishing a first subscription between the RIC and the E2 node for a reporting service provided to the E2 node;

[0034] (b) receiving, where the first subscription has been configured, created or established, a first message from the RIC requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription; and

[0035] (c) based on the first message, updating the content of the RIC indication message associated with the reporting action, or the triggering condition for sending the RIC indication message associated with the reporting action, or both.

[0036] In a fifth aspect, a program includes instructions (or software codes), which, when loaded into a computer, cause the computer to perform the method according to the second aspect or the fourth aspect above.

[0037] Effects of the Invention

[0038] According to the above aspects, an apparatus, method, and program may be provided that help solve at least one of a number of problems associated with near-RT RIC and E2 interfaces, including the above-mentioned problems. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 shows an example structure of a near-RT RIC and an E2 node according to an example embodiment;

[0040] Figure 2 is a flow chart illustrating an example of the operation of a near-RT RIC according to an example embodiment;

[0041] Figure 3 is a flow chart illustrating an example of the operation of an E2 node according to an example embodiment;

[0042] Figure 4 is a sequence diagram illustrating an example of the operation of a near-RT RIC and an E2 node according to an example embodiment;

[0043] Figure 5 is a flow chart illustrating an example of the operation of a near-RT RIC according to an example embodiment;

[0044] Figure 6 is a sequence diagram illustrating an example of the operation of a near-RT RIC and an E2 node according to an example embodiment;

[0045] Figure 7 is a sequence diagram illustrating an example of the operation of a near-RT RIC and an E2 node according to an example embodiment;

[0046] Figure 8 is a sequence diagram illustrating an example of the operation of a near-RT RIC and an E2 node according to an example embodiment;

[0047] Fig. 9 is a flow chart illustrating an example of the operation of a near-RT RIC according to an example embodiment;

[0048] Fig.10 is a sequence diagram illustrating an example of the operation of a near-RT RIC and an E2 node according to an example embodiment;

[0049] Fig.11 is a block diagram illustrating an example structure of a near-RT RIC according to an example embodiment; and

[0050] Fig.12 is a block diagram illustrating an example structure of an E2 node according to an example embodiment. DETAILED DESCRIPTION

[0051] Specific exemplary embodiments will be described in detail below with reference to the accompanying drawings. Throughout the drawings, the same or corresponding elements are represented by the same symbols, and for the sake of clarity, repeated descriptions are omitted as needed.

[0052] The multiple example embodiments described below can be implemented independently or appropriately in combination. These example embodiments include novel features that are different from each other. Therefore, these example embodiments help to achieve different goals or solve different problems from each other, and help to achieve different advantages from each other.

[0053] The following exemplary embodiments are mainly described for near-RT RIC and E2 nodes that comply with O-RAN technical specifications. However, these exemplary embodiments can be applied to other systems that support technologies similar to near-RT RIC and E2 nodes.

[0054] As used in this specification, depending on the context, "if" may be interpreted to mean "in the case of," "at or around a certain time," "after," "according to," "in response to determining as," "in response to determining as," or "in response to detecting." Depending on the context, these expressions may be interpreted to mean the same.

[0055] First, the structure and operation of various elements common to various exemplary embodiments are described. Figure 1 An example structure of a system according to multiple example embodiments is shown. Figure 1 In the example in , the system includes near RT RIC 1 and E2 node 2. Figure 1 The elements shown may be implemented, for example, as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functions instantiated on an application platform. Figure 1The elements shown can be implemented as a computer system with one or more memories and one or more processors. The computer system can be a single computer system or a (dispersed) plurality of computer systems. The computer system can be a stand-alone computer or can include one or more networked computers.

[0056] The Near RT RIC 1 is a logical function that enables near real-time control and optimization of RAN elements and resources through fine-grained (e.g., user equipment (UE) basis, cell basis) data collection and actions on the E2 interface. The Near RT RIC hosts one or more xApps 11 and provides a collection of platform functions that are collectively used to support specific functions hosted by the xApps 11. By way of example and not limitation, Figure 1 As shown, the set of platform functions includes a messaging infrastructure 12, xApp subscription management 13, E2 termination 14, a shared data layer (SDL) 15, and a database 16. The set of platform functions may also include other functions such as conflict mitigation, A1 termination, O1 termination, and API enablement. The E2 termination 14 terminates at least the E2 interface 3 with the E2 node 2.

[0057] The E2 node 2 provides one or more services to the near RT RIC 1 to allow access to messages and measurement results, or to allow control of the E2 node 2 from the near RT RIC 1, or both. These services are referred to as RIC services. In an example embodiment, the RIC services provided by the E2 node 2 and available for the near RT RIC 1 include at least a RIC reporting service. The RIC reporting service includes the sending of a RIC indication message from the E2 node 2 to the near RT RIC 1. The E2 node 2 may also provide one or more services among an insertion service, a control service, and a policy service. These RIC services may be combined in different ways to implement an E2 service model (E2SM).

[0058] Regarding the E2 interface, the E2 node 2 includes one or more RAN functions 21 and an E2 agent 22. The one or more RAN functions 21 support one or more RIC services and can be controlled by the near-RT RIC 1. The E2 agent 22 terminates the E2 interface 3 with the near-RT RIC 1 and is used to forward and receive E2 messages. This allows the E2 node 2 to expose one or more RAN functions 21 to the near-RT RIC 1 and the hosted xApp 11 via the E2 agent 22.

[0059] The E2 node 2 may also be referred to as a RAN node. The E2 node 2 may be an O-CU-CP, O-CU-UP, or O-DU for NR access. Alternatively, the E2 node 2 may be an O-eNB for Evolved Universal Terrestrial Radio Access (E-UTRA) access.

[0060] The E2 interface 3 provides E2AP procedures that enable the exchange of control signaling information between endpoints, provide RIC services, and allow the near-RT RIC 1 and the hosted xApp applications 11 to use the set of services described in the E2 service model. These E2AP procedures include, but are not limited to, RIC subscription, RIC subscription deletion, RIC control, and RIC indication.

[0061] The near-RT RIC 1 uses the RIC subscription process to subscribe to a reporting service, an insertion service, or a policy service. For the reporting service, the near-RT RIC platform function (i.e., xApp subscription management 13) receives a subscription request or proposal from one of the xApps 11 via an E2-related API provided by the messaging infrastructure 12. The request or proposal from the xApp specifies a list of E2 nodes, RAN functions, event triggers, and an action list. In an example embodiment, the list of E2 nodes includes at least E2 node 2. In response to the request or proposal from the xApp, the platform function (i.e., xApp subscription management 13 and E2 termination 14) uses the RIC subscription process to request the E2 node 2 to send an indication message to the near-RT RIC 1.

[0062] The xApp subscription management 13 in the near-RT RIC 1 is able to merge multiple identical subscriptions related to the reporting service from different xApps into a single subscription toward the E2 node 2. Specifically, the xApp subscription management 13 detects whether the new subscription requested or proposed by the xApp via the E2-related API is a duplication of an existing subscription that has been configured, created or established with the E2 node 2 (or is identical to the existing subscription). In other words, the xApp subscription management 13 detects whether the new subscription requested by the xApp has the same content as the existing subscription (i.e., the same event trigger definition and the same action definition). If the new subscription is a duplication of the existing subscription, the xApp subscription management 13 does not perform a redundant RIC subscription process for adding a duplicate subscription to the E2 node 2. Instead, the xApp subscription management 13 only requests the E2 termination 14 to add the xApp ID of the new xApp to the distribution list associated with the existing subscription, and sends a subscription response (success) to the new xApp via the E2-related API.

[0063] In other words, xApp subscription management 13 allows multiple identical subscriptions related to reporting services to be merged internally. This helps avoid redundant E2AP transactions between near-RT RIC 1 and E2 node 2. xApp subscription management 13 also allows E2 node 2 to avoid the unnecessary action of sending multiple identical RIC indication messages with the same trigger.

[0064] First exemplary embodiment

[0065] An example structure of a radio communication system according to this example embodiment may be Figure 1 The example shown is the same. This example embodiment provides an enhancement that allows the Near RT RIC 1 and E2 Node 2 to update existing report type subscriptions.

[0066] Figure 2 An example of the operation of the near-RT RIC 1 in this example embodiment is shown. In step 201, the near-RT RIC 1 configures a first subscription to a reporting service provided to the E2 node 2. Specifically, in response to an xApp request or proposal for a reporting type subscription, the platform function of the near-RT RIC 1 (i.e., xApp subscription management 13 and E2 termination 14) performs a RIC subscription process to the E2 node 2 to configure, create or establish the first subscription. The platform function can detect whether the subscription proposed by the xApp is a new subscription that does not overlap with an existing subscription. If the subscription proposed by the xApp does not overlap with any existing subscription, the platform function can initiate a RIC subscription process to the E2 node 2.

[0067] In step 202, the near RT RIC 1 sends an E2AP message to the E2 node 2 requesting an update of one or both of the event trigger definition and the action definition for the report action agreed in the first subscription. In other words, the near RT RIC 1 requests the E2 node 2 to update the existing report type subscription.

[0068] In order to inform the E2 node 2 that the E2AP message is for the purpose of updating the existing first subscription, the E2AP message may specify the RIC request ID (RIC REQUEST ID) associated with the first subscription when configuring, creating or establishing the first subscription. More specifically, the E2AP message may specify the same RIC request ID and the same RIC action ID (RIC ACTION ID) as those specified in the previous RIC subscription request message sent when configuring, creating or establishing the existing first subscription. In addition, the E2AP message may specify an event trigger definition and an action definition that partially overlap (or partially differs from) the event trigger definition and the action definition specified when configuring, creating or establishing the existing first subscription.

[0069] The E2AP message may be a RIC subscription request message. In this case, the RIC subscription request message may specify the same RIC request ID and the same RIC action ID as those specified in a previous RIC subscription request message sent when configuring, creating or establishing an existing first subscription, and may also specify an event trigger definition and an action definition that partially overlap with the event trigger definition and the action definition specified in the previous RIC subscription request message. In other words, the process for updating the existing first subscription may be a (modified) RIC subscription process. Alternatively, the E2AP message may be a newly defined message that is different from the RIC subscription request message. The name of the newly defined message may be, but is not limited to, a RIC subscription update message. In other words, the process for updating the existing first subscription may be a newly defined E2AP process (e.g., a RIC subscription update process).

[0070] In a first implementation, the platform function of the near RT RIC 1, in response to receiving a request or proposal to update an existing first subscription from one of the one or more xApps associated with the existing first subscription via an E2-related API, may perform Figure 2 Step 202. The request or proposal from the xApp to update the existing first subscription may specify an E2 request ID to identify the existing active subscription. In addition, the request or proposal from the xApp to update the existing first subscription may specify an E2 action ID to identify one of one or more actions associated with the existing active subscription. The platform function of the near-RT RIC 1 maintains a mapping of the E2 request ID and the E2 action ID used in the E2-related API to the RIC request ID and the RIC action ID used in the E2 interface. Therefore, the platform function of the near-RT RIC 1 can determine the RIC request ID (and RIC action ID) of the existing first subscription associated with the E2 request ID (and E2 action ID) specified by the update request or proposal received on the E2-related API.

[0071] The first implementation allows the near RT RIC 1 to update an existing report type subscription. If the existing first subscription is associated with only one xApp, the platform function of the near RT RIC 1 only needs to send the content of the RIC indication message based on the updated subscription to the one xApp. In contrast, if the existing first subscription is updated based on a request or proposal from one xApp during the period when multiple identical subscriptions used by multiple xApps are internally merged into a single first subscription, the platform function of the near RT RIC 1 can perform additional actions related to the handling of the RIC indication message. Specifically, the platform function of the near RT RIC 1 can selectively send the RIC indication message received from the E2 node 2 only to a subset of the multiple xApps associated with the first subscription. Alternatively, the platform function of the near RT RIC 1 can send a first split indication message containing only some of the report items contained in the RIC indication message to some of the multiple xApps, and send a second split indication message containing the remaining report items to the remaining xApps. The details of this handling of the RIC indication message are described in the following example embodiments.

[0072] In a second implementation, the platform function of the near-RT RIC 1 may perform step 202 in response to a second xApp requesting or proposing a new second subscription that is different from one or more xApps (first xApp) associated with an existing first subscription. In this case, the new second subscription request or proposal from the second xApp specifies event trigger definitions and action definitions that partially overlap (or partially differ) with the event trigger definitions and action definitions agreed upon in the existing first subscription.

[0073] For example, the event trigger definition of the second subscription may be the same as the event trigger definition of the first subscription, while the action definition of the second subscription may be partially or completely different from the action definition of the first subscription. Different action definitions may be, for example, different measurement items, different specific cell designations, or different specific (one or more than one) UE designations, or any combination of these. Different action definitions mean that the report items that the xApp wishes to receive in the RIC indication message are different. Therefore, in this example, the E2AP message in step 202 causes the E2 node 2 to send a common RIC indication message to the near-RT RIC 1, which contains both the first report item for the first subscription and the second report item for the second subscription.

[0074] Additionally or alternatively, the action definition of the second subscription may be the same as the action definition of the first subscription, while the event trigger definition of the second subscription may be partially different from the event trigger definition of the first subscription. Both the event trigger definition of the first subscription and the event trigger definition of the second subscription may be periodic reports, but the reporting period of the second subscription may be a multiple (i.e., an integer multiple) or a divisor of the reporting period of the first subscription. Alternatively, both the event trigger definition of the first subscription and the event trigger definition of the second subscription may be aperiodic reports. In this case, one or more aperiodic report triggering events for the second subscription may overlap partially and differ partially from one or more aperiodic report triggering events for the first subscription. Therefore, in this example, the E2AP message in step 202 causes the E2 node 2 to send a first RIC indication message and a second RIC indication message to the near-RT RIC 1. The first RIC indication message is based on a first trigger condition according to the first subscription, and on the other hand, the second RIC indication message is based on a second trigger condition according to the second subscription. The first RIC indication message and the second RIC indication message each specify the same RIC request ID and the same RIC action ID.

[0075] The second implementation allows the near RT RIC 1 to update an existing report type subscription. In addition, according to the second implementation, the platform function of the near RT RIC 1 may internally merge requests or proposals from the xApp for multiple report type subscriptions with partially overlapping (but not identical) trigger definitions and action definitions into a single subscription towards the E2 node. The platform function of the near RT RIC 1 may perform Figure 2 Step 202 of merging multiple partially different subscriptions from the xApp internally into a single subscription towards the E2 node.

[0076] In the second implementation, as described with respect to the first implementation, the platform function of the near RT RIC 1 may also perform additional operations related to the handling of RIC indication messages. Details of this handling of RIC indication messages are described in the following example embodiments.

[0077] The second implementation can help reduce the number of RIC indication messages that the E2 node 2 should send. For example, consider the case where the event trigger definition of the second subscription is the same as the event trigger definition of the first subscription, and the action definition of the second subscription is partially or completely different from the action definition of the first subscription. In this case, the E2 node 2 can use a single RIC indication message to report both the first report item for the first subscription and the second report item for the second subscription to the near-RT RIC 1. Therefore, this can help reduce the number of RIC indication messages that the E2 node 2 needs to send.

[0078] Next, consider the case where the action definition of the second subscription is the same as the action definition of the first subscription, and the event trigger definition of the second subscription is partially different from the event trigger definition of the first subscription. When the second reporting period of the second subscription is a multiple (i.e., an integer multiple) or a divisor of the first reporting period of the first subscription, the near-RT RIC 1 can internally merge the two subscriptions by updating the first subscription. In this case, the near-RT RIC 1 can update the reporting period of the existing first subscription with the smaller of the first reporting period and the second reporting period. As a result, every few RIC indication messages can be used to report both the first subscription and the second subscription. Therefore, this can help reduce the number of RIC indication messages that the E2 node 2 needs to send.

[0079] In a third implementation, when the first report type subscription and the second report type subscription have been internally merged according to the second implementation described above, the platform function of the near RT RIC 1 may perform step 202 to delete one of the first subscription and the second subscription. Specifically, if the xApp proposes the deletion of the second subscription, the platform function of the near RT RIC 1 may detect that the second subscription is not associated with any other xApp. The platform function may then update the existing single subscription with the E2 node 2 to remove the event trigger definition or action definition associated with the second subscription while retaining the event trigger definition or action definition for the first subscription.

[0080] Figure 3 An example of the operation of E2 node 2 is shown. In step 301, E2 node 2 configures a first subscription to a reporting service provided to E2 node 2. Specifically, E2 node 2 performs a RIC subscription procedure initiated by near RT RIC 1 for a report type subscription to configure, create or establish a first subscription.

[0081] In step 302, the E2 node 2 receives an E2AP message from the near RT RIC 1, the E2AP message requesting to update either or both of the event trigger definition and the action definition for the report action agreed upon in the first subscription. In other words, the E2 node 2 receives a request from the near RT RIC 1 to update an existing report type subscription. Specific examples of the E2AP message and specific examples of the content in the E2AP message can be found in the description of the first subscription. Figure 2 The examples described are the same.

[0082] In step 303, based on the E2AP message of step 302, the E2 node 2 updates the configuration for the existing first subscription. Specifically, the E2 node 2 updates the content of the RIC indication message associated with the report action for the first subscription, or the triggering condition for sending the RIC indication message associated with the report action, or both.

[0083] Figure 4 An example of the operation of the near RT RIC 1 and the E2 node 2 is shown. Step 401 and Figure 2 Step 201 and Figure 3 In step 401, the near RT RIC 1 and the E2 node 2 perform a RIC subscription procedure to configure, create or establish a first subscription to the reporting service. The near RT RIC 1 sends a RIC SUBSCRIPTION REQUEST message to the E2 node 2, and the E2 node 2 responds to the near RT RIC 1 with a RIC SUBSCRIPTION RESPONSE message.

[0084] The RIC subscription request message of step 401 includes a RIC request ID information element (IE) and also includes a RIC subscription details IE. The RIC request ID IE specifies the RIC request ID number used to identify the first subscription. The RIC subscription details IE includes a RIC event trigger definition IE and also includes an action list (action sequence).

[0085] The RIC Event Trigger Definition IE indicates a RIC Event Trigger Description that conforms to the style type and format specified in the E2SM. In the case of E2SM-KPM, the RIC Event Trigger Definition IE specifies an integer value representing a reporting period expressed in units of 1 millisecond. In the case of E2SM-RC, the RIC Event Trigger Definition IE specifies a trigger event for aperiodic reporting.

[0086] An action list (action sequence) is a list of one or more reporting actions. For each action, the action list contains a RIC action ID IE (RIC ACTION ID IE), a RIC action type IE, and a RIC action definition IE. The RIC action ID IE specifies a unique action ID number within a given RIC request ID. The RIC action type IE specifies the type of action (such as report, insert, or policy, etc.). Here, the RIC action type IE specifies the report type. The RIC action definition IE defines one or more report items to be reported by the E2 node 2. The RIC action definition IE provides parameters to be used when performing the reporting service according to the style type and format specified in the E2SM. In the case of E2SM-KPM, the RIC action definition IE specifies the measurement information list (measurement information list IE) together with other information elements. In the case of E2SM-RC, the RIC action definition IE specifies a list of parameters to be reported (parameter list to be reported IE).

[0087] The RIC subscription response message in step 401 includes a RIC request ID IE and an accepted RIC action list IE, and may optionally include a non-accepted RIC action list IE. The RIC request ID IE specifies the RIC request ID number used to identify the first subscription. The accepted RIC action list IE specifies (one or more) RIC action IDs of (one or more) actions accepted by the E2 node 2 among the one or more actions requested in the RIC subscription request message. The non-accepted RIC action list IE specifies (one or more) RIC action IDs of (one or more) actions not accepted by the E2 node 2 among the one or more actions requested in the RIC subscription request message.

[0088] Step 402 and Figure 2 Step 202 in Figure 3 . In step 402, a RIC subscription update procedure is performed to update the existing first subscription. In the example, the near-RT RIC 1 sends a RIC subscription update (RICSUBSCRIPTION UPDATE) message to the E2 node 2, and the E2 node 2 responds to the near-RT RIC 1 with a RIC subscription update response (RICSUBSCRIPTION UPDATE RESPONSE) message. However, as previously explained, the update of the existing first subscription can be performed through the (modified) RIC subscription procedure. In this case, the near-RT RIC 1 sends a RIC subscription request message to the E2 node 2, and the E2 node 2 responds to the near-RT RIC 1 with a RIC subscription response message.

[0089] The E2AP message sent by the near-RT RIC 1 in step 402 indicates to the E2 node 2 the update of the existing first subscription. To achieve this update, the E2AP message specifies the same RIC request ID as the RIC request ID indicated by the RIC subscription request message in step 401. The E2AP message also includes an updated RIC subscription details IE. The RIC subscription details IE is used to update one or both of the event trigger definition and the action definition specified in the RIC subscription request message in step 401. The RIC subscription details IE in step 402 includes a RIC action ID IE that specifies the same number as the RIC subscription details IE in step 401. The RIC subscription details IE in step 402 includes a RIC event trigger definition IE and a RIC action definition IE, and one or both of the RIC event trigger definition IE and the RIC action definition IE contain updated content compared to one or both of the RIC event trigger definition IE and the RIC action definition IE in the RIC subscription details IE in step 401.

[0090] Figure 4 The example shown may provide details of the E2AP procedure for updating an existing report-type subscription.

[0091] The following is a specific example of conditions that can merge multiple subscriptions with partially overlapping (or partially different) event trigger definitions and action definitions. A platform function of the near-RT RIC 1 (e.g., xApp subscription management 13) can determine whether a request or offer from an xApp for multiple subscriptions meets these conditions.

[0092] (1) E2SM-KPM REPORT Service Types 1 to 5

[0093] If the event trigger definitions (i.e., reporting periods) of the first subscription and the second subscription are different, whether these subscriptions can be merged depends on the details of the action definition (specifically, the measurement items to be collected). For example, if the platform function can generate the value of the measurement item to be reported to the xApp by averaging the measurement values ​​reported by multiple indication messages, the platform function can merge multiple subscriptions. In the case where merging is possible, if the reporting period of one subscription is a multiple (i.e., an integer multiple) of the reporting period of another subscription, the platform function can internally merge the two subscriptions into a single subscription to E2 node 2 and set the reporting period to the smaller of the two reporting periods.

[0094] (2) E2SM-KPM Report Service Style 1: E2 Node Measurement

[0095] If the action definitions of the first subscription and the second subscription are partially different, the platform function can merge the multiple subscriptions. For example, the second subscription has the same (one or more) target cells for collecting measurement information as the first subscription, but the measurement information list ((one or more) report items) of the second subscription is partially or completely different from the measurement information list of the first subscription. In this case, the platform function adds one or more additional measurement types specified in the measurement information list of the second subscription to the measurement information list IE of the E2SM-KPM action definition format 1.

[0096] In another example, the second subscription has a different (one or more) target cell for collecting measurement information than the first subscription. In this case, the near-RT RIC 1 and the E2 node 2 use the E2SM-KPM action definition format 1 extended to specify a cell global ID list. The platform function of the near-RT RIC 1 adds the additional (one or more) cell IDs associated with the second report item of the second subscription to the cell global ID list IE of the extended E2SM-KPM action definition format 1.

[0097] (3) E2SM-KPM reporting service style 2: E2 node measurement for a single UE

[0098] If the action definitions of the first subscription and the second subscription are partially different, the platform function can merge the multiple subscriptions. For example, the second subscription has the same (one or more) target UEs for collecting measurement information as the first subscription, but the measurement information list ((one or more) reporting items) of the second subscription is partially or completely different from the measurement information list of the first subscription. In this case, the platform function adds one or more additional measurement types specified in the measurement information list of the second subscription to the measurement information list IE of the E2SM-KPM action definition format 2.

[0099] (4) E2SM-KPM reporting service style 3: Condition-based UE-level E2 node measurement

[0100] If the action definitions of the first subscription and the second subscription are partially different, the platform function can merge the multiple subscriptions. For example, the second subscription has the same (one or more) target cells for collecting measurement information as the first subscription, but the list of matching conditions of the second subscription is partially or completely different from the list of matching conditions of the first subscription. In this case, the platform function adds one or more additional matching conditions specified in the matching condition IE of the second subscription to the measurement information list IE of the E2SM-KPM action definition format 2.

[0101] (5) E2SM-KPM reporting service style 5: E2 node measurement for multiple UEs

[0102] If the action definitions of the first subscription and the second subscription are partially different, the platform function can merge the multiple subscriptions. For example, the second subscription has the same target UE for collecting measurement information as the first subscription, but the measurement information list ((one or more) report items) of the second subscription is partially or completely different from the measurement information list of the first subscription. In this case, the platform function adds one or more additional measurement types specified in the measurement information list of the second subscription to the measurement information list IE of the E2SM-KPM action definition format 2. In another example, the second subscription has the same measurement information list ((one or more) report items) as the first subscription, but the target UE for collecting measurement information of the second subscription is partially or completely different from the target UE for collecting measurement information of the first subscription. In this case, the platform function adds one or more additional UEs specified in the list of target UEs used for the second subscription to the UE ID list IE of the subscription of the E2SM-KPM action definition format 5.

[0103] The near-RT RIC 1 and the E2 node 2 may use the E2SM-KPM action definition format 5, which is extended so that the minimum value of the UE ID that can be included in its subscribed UE ID list is 1. When the xApp requests a report type subscription according to the E2SM-KPM reporting service style 2 (E2 node measurements for a single UE), the near-RT RIC 1 may send a RIC subscription request message containing an action definition IE according to the extended E2SM-KPM action definition format 5 to the E2 node 2. This allows the near-RT RIC 1 to internally merge a second subscription related to multiple UEs with an existing first subscription related to a single UE.

[0104] (6) E2SM-RC REPORT Service Style 1: Message Copy

[0105] In the example, the second subscription has the same event trigger definition as the first subscription (i.e., (one or more) messages that trigger aperiodic reporting), but the action definition of the second subscription (i.e., (one or more) parameters to be reported) is partially or completely different from the action definition of the first subscription. In this case, the platform function adds one or more additional RAN parameter IDs related to the second report item of the second subscription (i.e., (one or more) parameters to be reported) to the Parameter List to Report IE of the E2SM-RC Action Definition Format 1.

[0106] In another example, the second subscription has the same action definition as the first subscription (i.e., (one or more) parameters to be reported), but the event trigger definition of the second subscription (i.e., (one or more) messages that trigger aperiodic reporting) is partially different from the event trigger definition of the first subscription. In this case, the platform function adds the difference between the one or more triggering events of the second subscription and the one or more triggering events of the first subscription to the message sequence IE for event triggering of the E2SM-RC event trigger definition format 1.

[0107] (7) E2SM-RC Report Service Style 3: E2 Node Information

[0108] In the example, the second subscription has the same event trigger definition as the first subscription (i.e., (one or more) cells that trigger aperiodic reporting), but the action definition of the second subscription (i.e., (one or more) parameters to be reported) is partially or completely different from the action definition of the first subscription. In this case, the platform function adds one or more additional RAN parameter IDs related to the second report item of the second subscription (i.e., (one or more) parameters to be reported) to the Parameter List to Report IE of the E2SM-RC Action Definition Format 1.

[0109] In another example, the second subscription has the same action definition as the first subscription (i.e., (one or more) parameters to be reported), but the event trigger definition of the second subscription (i.e., (one or more) cells that trigger aperiodic reporting) is partially different from the event trigger definition of the first subscription. In this case, the platform function adds the difference between the one or more triggering events of the second subscription and the one or more triggering events of the first subscription to the E2 Node Information Change Sequence IE of the E2SM-RC Event Trigger Definition Format 3.

[0110] (8) E2SM-RC reporting service style 4: UE information

[0111] In the example, the second subscription has the same event trigger definition as the first subscription (i.e., (one or more) UEs that trigger aperiodic reporting), but the action definition of the second subscription (i.e., (one or more) parameters to be reported) is partially or completely different from the action definition of the first subscription. In this case, the platform function adds one or more additional RAN parameter IDs related to the second report item of the second subscription (i.e., (one or more) parameters to be reported) to the Parameter List to Report IE of the E2SM-RC Action Definition Format 1.

[0112] In another example, the second subscription has the same action definition as the first subscription (i.e., (one or more) parameters to be reported), but the event trigger definition of the second subscription (i.e., (one or more) UEs that trigger aperiodic reporting) is partially different from the event trigger definition of the first subscription. In this case, the platform function adds the difference between the one or more triggering events of the second subscription and the one or more triggering events of the first subscription to the UE Information Change Sequence IE of the E2SM-RC Event Trigger Definition Format 4.

[0113] Second exemplary embodiment

[0114] An example structure of a radio communication system according to this example embodiment may be Figure 1 The examples shown are the same. This example embodiment provides enhanced details that allow the Near RT RIC 1 and E2 Node 2 to update existing report type subscriptions described in the first example embodiment.

[0115] Figure 5 An example of the operation of the near RT RIC 1 in this exemplary embodiment is shown. In step 501, the near RT RIC 1 configures a first subscription to a reporting service provided to the E2 node 2. Step 501 is similar to Figure 2 The process is similar to step 201 in , so the detailed description of this step is omitted.

[0116] In step 502, the platform function of the near RT RIC 1 receives a new second subscription request or proposal from the xApp. In step 503, the platform function detects that the event trigger definition and action definition for the report action requested or proposed in the second subscription partially overlap with the event trigger definition and action definition for the report action agreed in the existing first subscription. In other words, the platform function detects that the event trigger definition and action definition of the second subscription are partially different from the event trigger definition and action definition of the existing first subscription.

[0117] In step 504, the near RT RIC 1 sends an E2AP message to the E2 node 2, the E2AP message requesting an update of one or both of the event trigger definition and the action definition for the report action agreed upon in the first subscription. In other words, the near RT RIC 1 requests the E2 node 2 to update the existing report type subscription. Step 504 is the same as Figure 2 The process is similar to step 202 in , so the detailed description of this step is omitted.

[0118] Figure 6 An example of the operation of the near RT RIC 1 and the E2 node 2 related to establishment and updating of subscriptions is shown. Figure 6 Steps 601, 602 and 603 in Figure 5 . In step 601, xApp subscription management 13 receives a first subscription request or proposal (e.g., E2 subscription (request, E2 node ID)) for a reporting service provided by E2 node 2 from xApp 11A via an E2-related API. In step 602, xApp subscription management 13 requests E2 termination 14 to perform an E2AP process for a new subscription. In step 603, E2 termination 14 performs an RIC subscription process with E2 node 2 to configure, create or establish a first subscription. Although in Figure 6 Not shown, but after step 603, a message is sent from E2 Termination 14 to xApp Subscription Management 13 regarding the success of the first subscription, and then a message is sent from xApp Subscription Management 13 to xApp 11A.

[0119] Figure 6 Steps 604 to 607 in Figure 5. In step 604, xApp subscription management 13 receives a second subscription request or proposal (e.g., E2 subscription (request, E2 node ID)) for the reporting service provided by E2 node 2 from xApp 11B via the E2-related API. In step 605, xApp subscription management 13 detects that the event trigger definition and action definition of the proposed second subscription partially overlap with the event trigger definition and action definition of the existing first subscription. xApp subscription management 13 can determine whether the partially overlapping relationship between the first subscription and the second subscription is suitable for internal merging of subscriptions.

[0120] In step 606, xApp subscription management 13 requests E2 termination 14 to perform an E2AP procedure to update one or both of the event trigger definition and the action definition of the existing first subscription. In step 607, E2 termination 14 performs an RIC subscription update procedure with E2 node 2 to update the first subscription for the reporting service. As described in the first exemplary embodiment, the procedure in step 607 may be an RIC subscription procedure initiated by a RIC subscription request message that explicitly specifies the RIC request ID of the existing first subscription. Although in Figure 6 Not shown in FIG, but after step 607, a message is sent from E2 Termination 14 to xApp Subscription Management 13 regarding the success of updating the first subscription, and a message is sent from xApp Subscription Management 13 to xApp 11B.

[0121] Figure 7 An example of the operation of the near RT RIC 1 and the E2 node 2 related to the delivery of the RIC indication message is shown. In step 701, the E2 node 2 sends an E2AP RIC indication (E2AP RIC INDICATION) message associated with the report type subscription to the E2 termination 14. The E2AP RIC indication message includes a RIC request ID IE, a RIC action ID IE, a RIC indication type IE, a RIC indication header IE, and a RIC indication message IE.

[0122] If the RIC request ID number specified in the RIC request ID IE of the E2AP RIC indication message is associated with multiple partially different subscriptions that have been internally merged, the E2 termination 14 performs steps 702 to 704. More specifically, if multiple subscriptions with the same event trigger definition but different action definitions have been merged, the E2 termination 14 performs steps 702 to 704.

[0123] In step 702, E2 termination 14 divides the report items (e.g., the measurement values ​​of multiple measurement items) contained in the RIC indication message IE and generates multiple indication messages, each of which points to a corresponding subscription in the multiple subscriptions. Then, E2 termination 14 sends the generated multiple indication messages to the corresponding multiple xApps via the E2 related API. Figure 7 In the example of , E2 Terminate 14 sends an indication message containing a first portion of the split report item to xApp 11A (step 703), and sends an indication message containing a second portion of the split report item to xApp 11B (step 704).

[0124] The processing of step 702 may be performed by another platform function other than E2 termination 14, or by a dedicated xApp. Similarly, the processing of steps 703 and 704 may be performed by another platform function other than E2 termination 14, or by a dedicated xApp.

[0125] Figure 8 Another example of the operation of the near RT RIC 1 and the E2 node 2 related to the delivery of the RIC indication message is shown. Step 801 and Figure 7 The process is similar to step 701 in FIG.

[0126] If the RIC request ID number specified in the RIC request ID IE of the E2AP RIC indication message is associated with multiple partially different subscriptions that have been internally merged, the E2 termination 14 performs step 802 and selectively performs one of steps 803 to 805. More specifically, if multiple subscriptions with the same action definition but different event trigger definitions have been merged, the E2 termination 14 performs step 802 and performs one of steps 803 to 805.

[0127] In step 802, the E2 termination 14 selects one or more destination xApps from the multiple xApps associated with the merged multiple subscriptions, wherein the report items contained in the RIC indication message IE of the E2AP RIC indication message of step 801 are to be delivered to the one or more destination xApps. Specifically, in order to determine the (one or more) destination xApps to which the periodic report is to be delivered, the E2 termination 14 may refer to the start time (timestamp information) of the measurement collection indicated by the collection start time IE in the RIC indication header IE of the E2AP RIC indication message. Alternatively, in order to determine the (one or more) destination xApps to which the non-periodic report is to be delivered, the E2 termination 14 may refer to the event trigger condition indicated by the event trigger condition ID IE in the RIC indication header IE of the E2AP RIC indication message.

[0128] E2 Termination 14 sends the report item contained in the RIC Indication Message IE to the determined (one or more than one) destination xApp. Figure 8 In the example in , E2 terminates 14 to send the report item only to xApp 11A (step 803), to send the report item only to xApp 11B (step 804), or to send the report item to both xApp 11A and xApp 11B (step 805).

[0129] The processing of step 802 may be performed by another platform function other than E2 termination 14, or by a dedicated xApp. Similarly, the processing of steps 803 to 805 may be performed by another platform function other than E2 termination 14, or by a dedicated xApp.

[0130] According to the operation described in this example embodiment, the near RT RIC 1 may merge multiple subscriptions that partially overlap in trigger definition and action definition, and this may help reduce the number of RIC indication messages that the E2 node 2 needs to send.

[0131] Third exemplary embodiment

[0132] An example structure of a radio communication system according to this example embodiment may be Figure 1 The examples shown are the same. This example embodiment provides enhanced details that allow the Near RT RIC 1 and E2 Node 2 to update existing report type subscriptions described in the first example embodiment.

[0133] Fig. 9 FIG. 9 is a diagram showing an example of the operation of the near RT RIC 1 in this exemplary embodiment. In step 901, the near RT RIC 1 configures a first subscription to a reporting service provided to the E2 node 2. Step 901 is similar to Figure 2The process is similar to step 201 in , so the detailed description of this step is omitted.

[0134] In step 902, the platform function of the near-RT RIC 1 receives a request or proposal to update the first subscription from one of the one or more xApps associated with the first subscription. As described in the first example embodiment, the request or proposal to update the existing first subscription can specify an E2 request ID to identify the existing active subscription. In addition, the request or proposal from the xApp to update the existing first subscription can specify an E2 action ID to identify one of the one or more actions associated with the existing active subscription. The platform function of the near-RT RIC 1 maintains a mapping of the E2 request ID and the E2 action ID used in the E2-related API to the RIC request ID and the RIC action ID used in the E2 interface. Therefore, the platform function of the near-RT RIC 1 can determine the RIC request ID (and RIC action ID) of the existing first subscription associated with the E2 request ID (and E2 action ID) specified by the update request or proposal received on the E2-related API.

[0135] In step 903, the platform function sends an E2AP message to E2 node 2, which requests an update of one or both of the event trigger definition and the action definition for the report action agreed in the first subscription. In other words, the near RT RIC 1 requests E2 node 2 to update the existing report type subscription. Step 903 is the same as Figure 2 The process is similar to step 202 in , so the detailed description of this step is omitted.

[0136] Fig.10 An example of the operation of the near RT RIC 1 and the E2 node 2 related to the establishment and update of subscriptions is shown. Steps 1001 and 1002 are related to Fig. 9 In step 1001, xApp subscription management 13 receives a proposal or request for an E2 subscription from xApp 11A via an E2-related API, including an E2 request ID (and one or more E2 action IDs) associated with an existing first subscription. In step 1002, xApp subscription management 13 detects that the message in step 1001 requests or proposes to update one or both of the event trigger definition and the action definition of the existing first subscription.

[0137] Steps 1003 to 1005 and Fig. 91003. In step 1003, xApp subscription management 13 assigns a RIC request ID associated with the E2 request ID indicated in the message of step 1001. In step 1004, xApp subscription management 13 requests E2 termination 14 to perform an E2AP process for updating one or both of the event trigger definition and the action definition of the existing first subscription. In step 1005, E2 termination 14 performs a RIC subscription update process with E2 node 2 to update the first subscription for the reporting service. As described in the first example embodiment, the process in step 1005 can be a RIC subscription process initiated by a RIC subscription request message that explicitly specifies the RIC request ID of the existing first subscription.

[0138] In step 1006, E2 Termination 14 sends the result of the E2AP process to xApp Subscription Management 13. In step 1007, xApp Subscription Management 13 sends the result of updating the existing subscription requested or proposed in step 1001 to xApp 11A via the E2-related API.

[0139] As described in the first exemplary embodiment, if the existing first subscription is associated with multiple xApps, the platform function of the near RT RIC1 may perform additional operations related to the handling of the RIC indication message. These operations may be similar to those described in the second exemplary embodiment. Figure 7 and Figure 8 The operation described is the same.

[0140] The following provides examples of structures of the near-RT RIC 1 and the E2 node 2 according to the above-described multiple example embodiments. Fig.11 is a block diagram showing an example structure of a near-RT RIC 1. Fig.11 In the example in , the near RT RIC 1 is implemented as a computer system. The computer system includes one or more processors 1110, a memory 1120, and a large-capacity storage unit 1130, and the one or more processors 1110, the memory 1120, and the large-capacity storage unit 1130 communicate with each other via a bus 1170. The one or more processors 1110 may include, for example, one or both of a central processing unit (CPU) and a graphics processing unit (GPU). The computer system may include other devices, such as one or more output devices 1140, one or more input devices 1150, and one or more peripheral devices 1160. One or more peripheral devices 1160 may include a modem or a network adapter, or any combination thereof.

[0141] One or both of the memory 1120 and the mass storage 1130 include a computer-readable medium storing one or more sets of instructions. Some or all of these instructions may be stored in a memory in one or more processors 1110. When these instructions are executed in one or more processors 1110, one or more processors 1110 provide the functionality of the near-RT RIC 1 or the platform functionality of the near-RT RIC 1 described in the above example embodiments.

[0142] Fig.12 An example structure of E2 node 2 is shown. Fig.12 , the E2 node includes a network interface 1201, a processor 1202 and a memory 1203.

[0143] The network interface 1201 is used, for example, to communicate with network elements (eg, Near RT RIC 1, other RAN nodes). The network interface 1201 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series.

[0144] The processor 1202 may be, for example, a microprocessor, an MPU, or a CPU. The processor 1202 may include a plurality of processors.

[0145] The memory 1203 is composed of a volatile memory and a non-volatile memory. The memory 1203 may include a plurality of physically independent memory devices. The volatile memory is, for example, a static random access memory (SRAM), a dynamic RAM (DRAM) or a combination thereof. The non-volatile memory is, for example, a mask read-only memory (MROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a hard disk drive or any combination thereof. The memory 1203 may include a storage unit located separately from the processor 1202. In this case, the processor 1202 may access the memory 1203 via the network interface 1201 or the I / O interface.

[0146] The memory 1203 may store one or more software modules (or computer programs) 1204, which include instructions and data for performing the processing of the E2 node 2 described in the above example embodiments. In some implementations, the processor 1202 may be configured to load one or more software modules 1204 from the memory 1203 and execute the loaded software modules, thereby performing the processing of the E2 node 2 described in the above example embodiments.

[0147] If using Fig.11 and Fig.12As described, each of the processors included in the near-RT RIC 1 and the E2 node 2 according to the above-described example embodiment is capable of executing one or more programs containing a set of instructions for causing a computer to perform the algorithm described with reference to the accompanying drawings. (One or more) programs contain a set of instructions (or software code) that, when loaded into a computer, causes the computer to perform one or more of the functions described in the example embodiment. (One or more) programs may be stored in a non-transitory computer-readable medium or a tangible storage medium. As an example and not a limitation, a non-transitory computer-readable medium or a tangible storage medium may include a random access memory (RAM), a read-only memory (ROM), a flash memory, a solid-state drive (SSD) or other memory technology, a CD-ROM, a digital versatile disk (DVD), a Blu-ray (Blu-ray, registered trademark) disk or other optical disk storage, a magnetic cassette, a magnetic tape, a magnetic disk storage or other magnetic storage device. (One or more) programs may be transmitted on a transient computer-readable medium or a communication medium. By way of example, and not limitation, transitory computer readable media or communications media may include electrical, optical, acoustical, or other forms of propagated signals.

[0148] Other Example Embodiments

[0149] In the example embodiment described above, if an update of an existing report-type subscription fails, the near-RT RIC 1 and E2 node 2 may continue to operate according to the existing subscription prior to initiating the update.

[0150] As described in the above exemplary embodiment, the near RT RIC 1 can merge multiple report type subscriptions that are partially different in event trigger definition and action definition into a single subscription toward the E2 node 2. At this time, the merging result of multiple report type subscriptions may be different depending on the order in which these subscriptions are requested or proposed by the xApp.

[0151] If the list specified in the action definition format (e.g., measurement information list, UE list) exceeds its maximum size by merging multiple report type subscriptions with partially different event trigger definitions and action definitions, the near RT RIC 1 does not need to perform a merging operation. In this case, the near RT RIC 1 can initiate a normal RIC subscription process to configure a new subscription with the E2 node 2.

[0152] The above-described exemplary embodiments are merely examples of application of the technical ideas obtained by the inventors. These technical ideas are not limited to the above-described exemplary embodiments, and various modifications can be made to these exemplary embodiments.

[0153] For example, all or part of the exemplary embodiments disclosed above may be described as, but not limited to, the following supplementary descriptions.

[0154] (Supplementary Note 1)

[0155] A computer system comprising:

[0156] at least one memory; and

[0157] at least one processor coupled to the at least one memory and configured to:

[0158] Provides multiple platform functions associated with the RAN Intelligent Controller or RIC, RAN is the Radio Access Network;

[0159] configuring, creating or establishing between the RIC and the E2 node a first subscription to a reporting service provided to the E2 node; and

[0160] In case the first subscription has been configured, created or established, a first message is sent to the E2 node, the first message requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription.

[0161] (Supplementary Note 2)

[0162] A computer system according to Supplementary Note 1, wherein the at least one processor is configured to send the first message to the E2 node in response to receiving a request or proposal for a new second subscription from a second application, wherein the event trigger definition and action definition related to the reporting action of the new second subscription partially overlap with the event trigger definition and action definition related to the reporting action agreed upon in the first subscription.

[0163] (Supplementary Note 3)

[0164] The computer system according to Supplementary Note 2, wherein the first message causes the E2 node to send a common RIC indication message to the RIC, the common RIC indication message containing both a first report item related to the first subscription and a second report item related to the second subscription.

[0165] (Supplementary Note 4)

[0166] The computer system according to Supplementary Note 3, wherein the at least one processor is configured to:

[0167] receiving the common RIC indication message from the E2 node;

[0168] sending a first split indication message including the first report item but not including the second report item to a first application associated with the first subscription; and

[0169] A second segmentation indication message including the second report item but not including the first report item is sent to the second application.

[0170] (Supplementary Note 5)

[0171] A computer system according to Supplementary Note 3 or 4, wherein the at least one processor is configured to include a RIC action definition information element, i.e., a RIC action definition IE, in the first message, wherein the RIC action definition IE indicates that reporting of the second report item is required in addition to the first report item.

[0172] (Supplementary Note 6)

[0173] A computer system according to Supplementary Note 5, wherein the at least one processor is configured to add one or more additional measurement types associated with the second report item to a measurement information list IE of E2 service model key performance measurement, i.e., E2SM-KPM action definition format 1, 2, 3, 4 or 5.

[0174] (Supplementary Note 7)

[0175] The computer system according to Supplementary Note 5, wherein the at least one processor is configured to add the additional tag information associated with the second report item to a tag list IE associated with an existing measurement type IE of E2SM-KPM action definition format 1.

[0176] (Supplementary Note 8)

[0177] The computer system according to Supplementary Note 5, wherein the at least one processor is configured to:

[0178] Use E2SM-KPM action definition format 1 extended to specify a list of cell global IDs; and

[0179] An additional cell ID associated with the second report item is added to the cell global ID list.

[0180] (Supplementary Note 9)

[0181] The computer system according to Supplementary Note 5, wherein the at least one processor is configured to add one or more additional UE IDs associated with the second report item to the Subscribed UE ID List IE of the E2SM-KPM Action Definition Format 5.

[0182] (Supplementary Note 10)

[0183] The computer system according to Supplementary Note 9, wherein the at least one processor is configured to use the E2SM-KPM action definition format 5 extended so that a minimum value of UE IDs included in the subscribed UE ID list is 1.

[0184] (Supplementary Note 11)

[0185] The computer system according to Supplementary Note 5, wherein the at least one processor is configured to add one or more additional RAN parameter IDs associated with the second report item to a list of parameters to be reported in E2SM RAN Control, i.e., E2SM-RC Action Definition Format 1.

[0186] (Supplementary Note 12)

[0187] The computer system according to Supplementary Note 2, wherein the first message causes the E2 node to send a first RIC indication message based on a first trigger condition according to the first subscription and a second RIC indication message based on a second trigger condition according to the second subscription to the RIC.

[0188] (Supplementary Note 13)

[0189] The computer system according to Supplementary Note 12, wherein the first RIC indication message and the second RIC indication message each indicate exactly the same RIC request ID and exactly the same RIC action ID.

[0190] (Supplementary Note 14)

[0191] The computer system according to Supplementary Note 12 or 13, wherein the at least one processor is configured to:

[0192] selectively sending an indication message included in the first RIC indication message to a first application associated with the first subscription, but not sending the indication message to a second application associated with the second subscription; and

[0193] The indication message included in the second RIC indication message is selectively sent to the second application without sending the indication message to the first application.

[0194] (Supplementary Note 15)

[0195] The computer system according to Supplementary Note 14, wherein:

[0196] The first trigger condition is related to periodic reporting and specifies a first reporting period,

[0197] The second trigger condition is related to periodic reporting and specifies a second reporting period, and

[0198] The at least one processor is configured to set the reporting period IE of E2SM-KPM event trigger definition format 1 to specify the smaller of the first reporting period and the second reporting period if the second reporting period is a multiple or a submultiple of the first reporting period.

[0199] (Supplementary Note 16)

[0200] The computer system according to Supplementary Note 14, wherein:

[0201] The first trigger condition specifies one or more first trigger events for aperiodic reporting,

[0202] The second trigger condition specifies one or more second trigger events for aperiodic reporting, and

[0203] The at least one processor is configured to add the difference between the one or more first trigger events and the one or more second trigger events to a message sequence for event triggering of E2SM-RC event trigger definition format 1, an E2 node information change sequence of E2SM-RC event trigger definition format 3, or a UE information change sequence of E2SM-RC event trigger definition format 4.

[0204] (Supplementary Note 17)

[0205] A computer system according to Supplementary Note 1, wherein the at least one processor is configured to send the first message to the E2 node in response to receiving a request or proposal to update the first subscription from any one of one or more applications associated with the first subscription.

[0206] (Supplementary Note 18)

[0207] The computer system according to Supplementary Note 1, wherein:

[0208] When configuring, creating or establishing the first subscription, the first message specifies a RIC request ID associated with the first subscription, and

[0209] The first message also specifies event trigger definitions and action definitions that partially overlap with event trigger definitions and action definitions specified when configuring, creating or establishing the first subscription.

[0210] (Supplementary Note 19)

[0211] A computer system according to Supplementary Note 18, wherein the first message is a RIC subscription request message, which specifies the same RIC request ID and the same RIC action ID as the RIC request ID and RIC action ID specified in a previous RIC subscription request message sent to configure, create or establish the first subscription.

[0212] (Supplementary Note 20)

[0213] The computer system according to Supplementary Note 1, wherein the first message is a newly defined RIC subscription update message different from the RIC subscription request message.

[0214] (Supplementary Note 21)

[0215] The computer system according to Supplementary Note 1, wherein the reporting service includes sending a RIC indication message from the E2 node to the RIC.

[0216] (Supplementary Note 22)

[0217] The computer system according to Supplementary Note 1 or 21, wherein the RIC is a near-RT RIC.

[0218] (Supplementary Note 23)

[0219] The computer system according to Supplementary Note 1 or 21, wherein the E2 node is an O-RAN central unit-control plane, i.e., O-CU-CP, an O-RAN central unit-user plane, i.e., O-CU-UP, an O-RAN distributed unit, i.e., O-DU, or an O-RAN eNodeB, i.e., O-eNB.

[0220] (Supplementary Note 24)

[0221] An E2 node, comprising:

[0222] at least one memory; and

[0223] at least one processor coupled to the at least one memory and configured to:

[0224] configuring, creating or establishing a first subscription between a RAN intelligent controller (RIC) and the E2 node for a reporting service provided to the E2 node, RAN being a radio access network;

[0225] receiving, with the first subscription configured, created or established, a first message from the RIC requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription; and

[0226] Based on the first message, content of the RIC indication message associated with the reporting action, or a trigger condition for sending the RIC indication message associated with the reporting action, or both are updated.

[0227] (Supplementary Note 25)

[0228] The E2 node according to Supplementary Note 24, wherein

[0229] When configuring, creating or establishing the first subscription, the first message specifies a RIC request ID associated with the first subscription, and

[0230] The first message also specifies event trigger definitions and action definitions that partially overlap with event trigger definitions and action definitions specified when configuring, creating or establishing the first subscription.

[0231] (Supplementary Note 26)

[0232] An E2 node according to Supplementary Note 25, wherein the first message is a RIC subscription request message, and the RIC subscription request message specifies the same RIC request ID and the same RIC action ID as the RIC request ID and RIC action ID specified in a previous RIC subscription request message sent to configure, create or establish the first subscription.

[0233] (Supplementary Note 27)

[0234] The E2 node according to Supplementary Note 24, wherein the first message is a newly defined RIC subscription update message different from the RIC subscription request message.

[0235] (Supplementary Note 28)

[0236] The E2 node according to any one of Supplementary Notes 24 to 27, wherein the reporting service comprises sending a RIC indication message from the E2 node to the RIC.

[0237] (Supplementary Note 29)

[0238] The E2 node according to any one of Supplementary Notes 24 to 27, wherein the RIC is a near-RT RIC.

[0239] (Supplementary Note 30)

[0240] According to the E2 node described in any one of Supplementary Notes 24 to 27, the E2 node is an O-RAN central unit-control plane, i.e., O-CU-CP, an O-RAN central unit-user plane, i.e., O-CU-UP, an O-RAN distributed unit, i.e., O-DU, or an O-RAN eNodeB, i.e., O-eNB.

[0241] (Supplementary Note 31)

[0242] A method performed by a computer system, the method comprising:

[0243] Provides multiple platform functions associated with the RAN Intelligent Controller or RIC, RAN is the Radio Access Network;

[0244] configuring, creating or establishing, through the plurality of platform functions, between the RIC and the E2 node, a first subscription to a reporting service provided to the E2 node; and

[0245] In case the first subscription has been configured, created or established, a first message is sent to the E2 node, the first message requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription.

[0246] (Supplementary Note 32)

[0247] A method performed by an E2 node, the method comprising:

[0248] configuring, creating or establishing a first subscription between a RAN intelligent controller (RIC) and the E2 node for a reporting service provided to the E2 node, RAN being a radio access network;

[0249] receiving, with the first subscription configured, created or established, a first message from the RIC requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription; and

[0250] Based on the first message, content of the RIC indication message associated with the reporting action, or a trigger condition for sending the RIC indication message associated with the reporting action, or both are updated.

[0251] (Supplementary Note 33)

[0252] A non-transitory computer readable medium storing a program for causing one or more processors of a computer system to perform a method comprising:

[0253] Provides multiple platform functions associated with the RAN Intelligent Controller or RIC, RAN is the Radio Access Network;

[0254] configuring, creating or establishing, through the plurality of platform functions, between the RIC and the E2 node, a first subscription to a reporting service provided to the E2 node; and

[0255] In case the first subscription has been configured, created or established, a first message is sent to the E2 node, the first message requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription.

[0256] (Supplementary Note 34)

[0257] A non-transitory computer readable medium storing a program for causing one or more processors of an E2 node to perform a method comprising:

[0258] configuring, creating or establishing a first subscription between a RAN intelligent controller (RIC) and the E2 node for a reporting service provided to the E2 node, RAN being a radio access network;

[0259] receiving, with the first subscription configured, created or established, a first message from the RIC requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription; and

[0260] Based on the first message, content of the RIC indication message associated with the reporting action, or a trigger condition for sending the RIC indication message associated with the reporting action, or both are updated.

[0261] This application is based upon and claims the benefit of priority from Japanese patent application No. 2022-099686, filed on Jun. 21, 2022, the disclosure of which is incorporated herein in its entirety by reference.

[0262] Reference numerals list

[0263] 1 Near RT RIC

[0264] 2E2 Node

[0265] 3E2 interface

[0266] 11xApp

[0267] 13xApp Subscription Management

[0268] 14E2 Termination

[0269] 21RAN Function

[0270] 22E2 Proxy

[0271] 1110 processor

[0272] 1120 Memory

[0273] 1130 Mass Storage Department

[0274] 1202 Processor

[0275] 1203 Memory

Claims

1. A computer system comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to: Provides multiple platform functions associated with the RAN Intelligent Controller or RIC, RAN is the Radio Access Network; configuring, creating or establishing between the RIC and the E2 node a first subscription for a reporting service provided to the E2 node; as well as In case the first subscription has been configured, created or established, a first message is sent to the E2 node, the first message requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription.

2. The computer system according to claim 1, wherein: The at least one processor is configured to send the first message to the E2 node in response to receiving a request or proposal for a new second subscription from a second application, wherein the event trigger definition and action definition related to the reporting action of the new second subscription partially overlap with the event trigger definition and action definition related to the reporting action agreed upon in the first subscription.

3. The computer system according to claim 2, wherein: The first message causes the E2 node to send a common RIC indication message to the RIC, the common RIC indication message containing both a first report item related to the first subscription and a second report item related to the second subscription.

4. The computer system according to claim 3, wherein: The at least one processor is configured to: receiving the common RIC indication message from the E2 node; sending a first split indication message including the first report item but not including the second report item to a first application associated with the first subscription; as well as A second segmentation indication message including the second report item but not including the first report item is sent to the second application.

5. The computer system according to claim 3 or 4, wherein: The at least one processor is configured to include a RIC action definition information element (RIC action definition IE) in the first message, the RIC action definition IE indicating that reporting of the second report item is required in addition to the first report item.

6. The computer system according to claim 5, wherein: The at least one processor is configured to add one or more additional measurement types associated with the second report item to a measurement information list IE of E2 Service Model Key Performance Measurement, ie, E2SM-KPM Action Definition format 1, 2, 3, 4 or 5.

7. The computer system according to claim 5, wherein: The at least one processor is configured to add additional tag information associated with the second report item to a tag list IE associated with an existing measurement type IE of E2SM-KPM action definition format 1.

8. The computer system according to claim 5, wherein: The at least one processor is configured to: Use E2SM-KPM action definition format 1 extended to specify a list of cell global IDs; and An additional cell ID associated with the second report item is added to the cell global ID list.

9. The computer system according to claim 5, wherein: The at least one processor is configured to add one or more additional UE IDs associated with the second report item to the Subscribed UEID List IE of the E2SM-KPM Action Definition Format 5.

10. The computer system according to claim 9, wherein: The at least one processor is configured to use the E2SM-KPM action definition format 5 extended so that a minimum value of UE IDs included in the subscribed UE ID list is 1.

11. The computer system according to claim 5, wherein: The at least one processor is configured to add one or more additional RAN parameter IDs associated with the second report item to a list of parameters to be reported of an E2SM RAN Control, ie, E2SM-RC, action definition format 1.

12. The computer system according to claim 2, wherein: The first message causes the E2 node to send a first RIC indication message based on a first trigger condition according to the first subscription and a second RIC indication message based on a second trigger condition according to the second subscription to the RIC.

13. The computer system according to claim 12, wherein: The first RIC indication message and the second RIC indication message each indicate the same RIC request ID and the same RIC action ID.

14. The computer system according to claim 12 or 13, wherein: The at least one processor is configured to: selectively sending an indication message included in the first RIC indication message to a first application associated with the first subscription, but not sending the indication message to a second application associated with the second subscription; and The indication message included in the second RIC indication message is selectively sent to the second application without sending the indication message to the first application.

15. The computer system of claim 14, wherein: The first trigger condition is related to periodic reporting and specifies a first reporting period, The second trigger condition is related to periodic reporting and specifies a second reporting period, and The at least one processor is configured to set the reporting period IE of E2SM-KPM event trigger definition format 1 to specify the smaller of the first reporting period and the second reporting period if the second reporting period is a multiple or a submultiple of the first reporting period.

16. The computer system of claim 14, wherein: The first trigger condition specifies one or more first trigger events for aperiodic reporting, The second trigger condition specifies one or more second trigger events for aperiodic reporting, and The at least one processor is configured to add the difference between the one or more first trigger events and the one or more second trigger events to a message sequence for event triggering of E2SM-RC event trigger definition format 1, an E2 node information change sequence of E2SM-RC event trigger definition format 3, or a UE information change sequence of E2SM-RC event trigger definition format 4.

17. The computer system of claim 1, wherein: The at least one processor is configured to send the first message to the E2 node in response to receiving a request or proposal to update the first subscription from any of the one or more applications associated with the first subscription.

18. The computer system of claim 1, wherein: When configuring, creating or establishing the first subscription, the first message specifies a RIC request ID associated with the first subscription, and The first message also specifies event trigger definitions and action definitions that partially overlap with event trigger definitions and action definitions specified when configuring, creating or establishing the first subscription.

19. The computer system of claim 18, wherein: The first message is a RIC subscription request message that specifies the same RIC request ID and the same RIC action ID as specified in a previous RIC subscription request message sent to configure, create or establish the first subscription.

20. The computer system of claim 1, wherein: The first message is a newly defined RIC subscription update message different from the RIC subscription request message.

21. The computer system of claim 1, wherein: The reporting service includes sending a RIC indication message from the E2 node to the RIC.

22. The computer system according to claim 1 or 21, wherein: The RIC is a near RT RIC.

23. The computer system according to claim 1 or 21, wherein: The E2 node is an O-RAN central unit-control plane, namely O-CU-CP, an O-RAN central unit-user plane, namely O-CU-UP, an O-RAN distributed unit, namely O-DU, or an O-RAN eNodeB, namely O-eNB.

24. An E2 node, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to: configuring, creating or establishing a first subscription between a RAN intelligent controller (RIC) and the E2 node for a reporting service provided to the E2 node, RAN being a radio access network; receiving, in the case where the first subscription has been configured, created or established, a first message from the RIC requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription; as well as Based on the first message, content of the RIC indication message associated with the reporting action, or a trigger condition for sending the RIC indication message associated with the reporting action, or both are updated.

25. The E2 node according to claim 24, wherein: When configuring, creating or establishing the first subscription, the first message specifies a RIC request ID associated with the first subscription, and The first message also specifies event trigger definitions and action definitions that partially overlap with event trigger definitions and action definitions specified when configuring, creating or establishing the first subscription.

26. The E2 node according to claim 25, wherein: The first message is a RIC subscription request message that specifies the same RIC request ID and the same RIC action ID as specified in a previous RIC subscription request message sent to configure, create or establish the first subscription.

27. The E2 node according to claim 24, wherein: The first message is a newly defined RIC subscription update message different from the RIC subscription request message.

28. The E2 node according to any one of claims 24 to 27, wherein: The reporting service includes sending a RIC indication message from the E2 node to the RIC.

29. The E2 node according to any one of claims 24 to 27, wherein: The RIC is a near RT RIC.

30. The E2 node according to any one of claims 24 to 27, wherein: The E2 node is an O-RAN central unit-control plane, namely O-CU-CP, an O-RAN central unit-user plane, namely O-CU-UP, an O-RAN distributed unit, namely O-DU, or an O-RAN eNodeB, namely O-eNB.

31. A method performed by a computer system, the method comprising: Provides multiple platform functions associated with the RAN Intelligent Controller or RIC, RAN is the Radio Access Network; configuring, creating or establishing, through the plurality of platform functions, between the RIC and the E2 node, a first subscription to a reporting service provided to the E2 node; as well as In case the first subscription has been configured, created or established, a first message is sent to the E2 node, the first message requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription.

32. A method performed by an E2 node, the method comprising: configuring, creating or establishing a first subscription between a RAN intelligent controller (RIC) and the E2 node for a reporting service provided to the E2 node, RAN being a radio access network; receiving, in the case where the first subscription has been configured, created or established, a first message from the RIC requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription; as well as Based on the first message, content of the RIC indication message associated with the reporting action, or a trigger condition for sending the RIC indication message associated with the reporting action, or both are updated.

33. A non-transitory computer readable medium storing a program for causing one or more processors of a computer system to perform a method comprising: Provides multiple platform functions associated with the RAN Intelligent Controller or RIC, RAN is the Radio Access Network; configuring, creating or establishing, through the plurality of platform functions, between the RIC and the E2 node, a first subscription to a reporting service provided to the E2 node; as well as In case the first subscription has been configured, created or established, a first message is sent to the E2 node, the first message requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription.

34. A non-transitory computer readable medium storing a program for causing one or more processors of an E2 node to perform a method comprising: configuring, creating or establishing a first subscription between a RAN intelligent controller (RIC) and the E2 node for a reporting service provided to the E2 node, RAN being a radio access network; receiving, in the case where the first subscription has been configured, created or established, a first message from the RIC requesting an update of one or both of an event trigger definition and an action definition related to a reporting action agreed upon in the first subscription; as well as Based on the first message, content of the RIC indication message associated with the reporting action, or a trigger condition for sending the RIC indication message associated with the reporting action, or both are updated.

Images