Wireless communication node, RIC, communication method, and program

Abstract

The purpose of the present invention is to provide a wireless communication node that manages a plurality of RIC Subscriptions and is capable of executing processing for resetting a portion of the RIC Subscriptions. A wireless communication node according to the present disclosure comprises: a management unit that manages a plurality of pieces of management information in which an event and an operation that occurs by being triggered by the event are associated with each other; and a communication unit that transmits, to a RAN Intelligent Controller (RIC), a message indicating that at least one piece of management information among the plurality of pieces of management information is to be reset. The message includes information with which it is possible to identify second management information that is not to be reset.

Description

Wireless communication node, RIC, communication method and program

[0001] The present disclosure relates to a wireless communication node, a RIC, a communication method, and a program.

[0002] In recent years, radio access networks have been adopted that separate the baseband and radio sections of base stations and connect them via a fronthaul. The O-RAN (Open-Radio Access Network) fronthaul specifications, established by the O-RAN Alliance, define the fronthaul specifications between the O-RU (Radio Unit), which corresponds to the radio section, and the O-DU (Distributed Unit) and O-CU (Central Unit), which correspond to the baseband section. One of the goals of the O-RAN fronthaul specifications is to facilitate the connection of O-RUs from different vendors to O-DUs, thereby realizing multi-vendor radio access networks. Furthermore, specifications for the RAN Intelligent Controller (RIC) are also being considered to realize RAN intelligence.

[0003] Non-Patent Document 1, for example, specifies the functions of a Near-RT RIC (Near-Real Time RAN Intelligent Controller) as a node for realizing RAN intelligence that realizes autonomous RAN operation. Non-Patent Document 1 also specifies the functions of the E2 interface between the Near-RT RIC and an E2 node including an O-CU and an O-DU.

[0004] The Near-RT RIC executes the RIC Subscription procedure between itself and the E2 node to collect various information from the E2 node in response to an event that has occurred. Execution of the RIC Subscription procedure generates a RIC Subscription in the E2 node. The RIC Subscription is information that associates an event with an action corresponding to the event.

[0005] Non-Patent Document 1 further discloses an E2 Reset procedure for resetting all RIC Subscriptions managed in an E2 node.

[0006] Furthermore, Patent Document 1 discloses an E2 Service Update procedure between a Near-RT RIC and an E2 node.

[0007] Special Publication No. 2022-551708

[0008] O-RAN.WG3.E2GAP-R003-v04.01

[0009] The E2 Reset procedure disclosed in Non-Patent Document 1 is premised on the assumption that all of the multiple RIC Subscriptions managed in the E2 node are reset. On the other hand, it is desirable that the E2 node executes a process to exclude RIC Subscriptions that are normally managed or operating normally from the reset target. However, a wireless communication node that executes the process defined in Non-Patent Document 1 has a problem in that it cannot execute a process to reset some of the RIC Subscriptions.

[0010] In view of the above-mentioned problems, an object of the present disclosure is to provide a wireless communication node, a RIC, a communication method, and a program that can execute a process to reset some of the RIC Subscriptions in a wireless communication node that manages multiple RIC Subscriptions.

[0011] A wireless communication node according to the present disclosure includes a management unit that manages a plurality of pieces of management information in which events are associated with actions that occur as triggers of the events, and a communication unit that transmits a message to a RAN Intelligent Controller (RIC) indicating that at least one piece of management information among the plurality of pieces of management information is to be reset, and the message includes information that can identify a second piece of management information that is not to be reset.

[0012] The RIC of the present disclosure includes a receiving unit that receives a message indicating that at least one of the management information is to be reset from a wireless communication node having multiple pieces of management information in which an event is associated with an action that occurs as a trigger of the event, and a transmitting unit that transmits a second message to the wireless communication node, the message including information that can identify second management information that is not to be reset, to initiate setting of first management information that is to be reset.

[0013] The communication method according to the present disclosure manages a plurality of pieces of management information in which events are associated with actions triggered by the events, and transmits a message to a RAN Intelligent Controller (RIC) indicating that at least one piece of management information among the plurality of pieces of management information is to be reset, the message including information capable of identifying a second piece of management information that is not to be reset.

[0014] The program according to the present disclosure manages a plurality of pieces of management information in which events are associated with actions that occur as triggers of the events, and causes a computer to transmit to a RAN Intelligent Controller (RIC) a message indicating that at least one piece of management information is to be reset, the message including information that can identify second management information that is not to be reset.

[0015] The present disclosure makes it possible to provide a wireless communication node, a RIC, a communication method, and a program that can execute a process to reset some of the RIC Subscriptions in a wireless communication node that manages multiple RIC Subscriptions.

[0016] FIG. 1 shows an example configuration of a wireless communication node according to the present disclosure. FIG. 2 shows the flow of communication processing executed in the wireless communication node. FIG. 3 shows an example configuration of a RIC according to the present disclosure. FIG. 4 shows the flow of communication processing executed in the RIC. FIG. 5 is a diagram showing an example configuration of a communication system. FIG. 6 shows that multiple pieces of management information are managed. FIG. 7 is a diagram showing the flow of processing in a RIC Subscription procedure. FIG. 8 is a diagram showing the flow of processing in a RESET procedure. FIG. 9 shows the flow of processing in a RESET procedure executed in an E2 node. FIG. 10 shows the flow of processing in a RESET procedure executed in an E2 node. FIG. 11 is a block diagram showing example configurations of a wireless communication node, a RIC, an E2 node, and a Near-RTRIC.

[0017] 1 shows a configuration example of a wireless communication node 10 according to the present disclosure. The wireless communication node 10 may be a computer device that operates when a processor executes a program stored in a memory.

[0018] The wireless communication node 10 may be, for example, an E2 node whose specifications are defined by the O-RAN Alliance. The wireless communication node 10 may be either an O-CU or an O-DU included in the E2 node. The O-CU and O-DU may simply be referred to as a CU device and a DU device.

[0019] The wireless communication node 10 includes a management unit 11 and a communication unit 12. The management unit 11 and the communication unit 12 may be software or modules that are executed by a processor executing a program stored in a memory, or may be hardware such as a circuit or a chip.

[0020] The management unit 11 may be used as a management means for managing information, and the communication unit 12 may be used as a communication means for transmitting or receiving information.

[0021] The management unit 11 manages a plurality of pieces of management information in which events are associated with actions triggered by the events. The events may be referred to as event triggers. The event trigger may be an event-type trigger.

[0022] An event may be a communication terminal or a wireless communication node 10 that controls wireless communication performed by the communication terminal entering a predetermined state. Entering a predetermined state may be rephrased as entering a specific state, transitioning to a specific state, or transitioning to a specific state. Alternatively, an event may be an application executed by the communication terminal or the wireless communication node 10 entering a predetermined state. Alternatively, an event may be a communication state in the communication terminal or the wireless communication node 10 reaching a specific state. Alternatively, an event may be a change in the environment surrounding the communication terminal. Alternatively, an event may be a change in information held or managed by the communication terminal or the wireless communication node 10. Alternatively, an event may be a change in information specific to the communication terminal or the wireless communication node 10.

[0023] For example, the event may be when the amount of data transmitted or received by the communication terminal reaches a predetermined amount, or when the amount of data held by the communication terminal as data to be transmitted reaches a predetermined amount, or when the identification information of the communication terminal or the wireless communication node 10 changes.

[0024] The operation triggered by an event may be, for example, the wireless communication node 10 notifying the RIC 20 that an event has been detected. Furthermore, when an event is detected, the wireless communication node 10 may transmit information indicating the cause of the event detection. The information indicating the cause of the event detection may be, for example, information indicating the state of the communication terminal or the wireless communication node 10, information specific to the changed communication terminal or the wireless communication node 10, information indicating a change that has occurred in the communication terminal or the wireless communication node 10, etc.

[0025] The management unit 11 manages a plurality of pieces of management information. Each time the wireless communication node 10 detects an event included in the management information, the wireless communication node 10 executes an operation triggered by the detected event.

[0026] The communication unit 12 transmits to the RIC 20 a message indicating that at least one piece of management information among the multiple pieces of management information is to be reset. Resetting the management information may mean deleting the management information. Alternatively, resetting the management information may mean releasing resources allocated to the management information. The resources may be, for example, system resources. The system resources may be memory resources, processor resources, etc. The memory resources may be memory areas. The processor resources may be indicated using processor usage rates, processor processing speeds, etc.

[0027] Alternatively, resetting the management information may mean stopping the use of the management information without deleting the management information. For example, the wireless communication node 10 may not detect events included in the management information whose use has been stopped.

[0028] The message includes information that can identify second management information that is not to be reset among the multiple pieces of management information. For example, the message may include information that identifies the second management information. Alternatively, the message may include first management information associated with information indicating that it is to be reset, and second management information associated with information indicating that it is not to be reset. The information indicating that it is to be reset or the information indicating that it is not to be reset may be indicated using a flag or the like. Alternatively, the message may include only the first management information that is to be reset, thereby making it possible to identify the second management information that is not to be reset. There may be one or more pieces of first management information and second management information.

[0029] The management information may be identified by only one piece of identification information, or may be identified by a plurality of pieces of identification information.

[0030] Next, a description will be given of a communication method executed in the wireless communication node 10. FIG.

[0031] First, the management unit 11 manages a plurality of pieces of management information in which events are associated with actions triggered by the events (S11). Next, the communication unit 12 transmits a message to the RIC 20 indicating that at least one piece of management information is to be reset (S12). The message includes information that can identify a second piece of management information that is not to be reset among the plurality of pieces of management information.

[0032] Next, the RIC 20 will be described. Fig. 3 shows an example configuration of the RIC 20 according to the present disclosure. The RIC 20 may be a computer device that operates when a processor executes a program stored in a memory. The RIC 20 may be a Near-RT RIC or a Non-RT RIC.

[0033] The RIC 20 has a receiving unit 21 and a transmitting unit 22. The receiving unit 21 and the transmitting unit 22 may be software or modules that are executed by a processor executing a program stored in a memory, or may be hardware such as a circuit or a chip.

[0034] The receiving unit 21 may be used as a receiving means for receiving information. The transmitting unit 22 may be used as a transmitting means for transmitting information. The receiving unit 21 and the transmitting unit 22 may be a communication unit. The communication unit may be used as a communication means for transmitting or receiving information.

[0035] The receiving unit 21 receives a message indicating that at least one piece of management information among the plurality of pieces of management information is to be reset from the wireless communication node 10. The message received from the wireless communication node 10 includes information capable of identifying the management information not to be reset.

[0036] The transmitter 22 transmits a message to the wireless communication node 10 to start setting the management information to be reset. The management information to be reset is management information that has been reset in the wireless communication node 10. Starting the setting of the management information to be reset may mean requesting the resumption of management of the management information to be reset. Alternatively, starting the setting of the management information to be reset may mean requesting the generation of the management information to be reset.

[0037] Next, a description will be given of a communication method executed in the RIC 20. FIG.

[0038] First, the receiving unit 21 receives a message from the wireless communication node 10 indicating that at least one of the plurality of pieces of management information is to be reset (S21). The message includes information that can identify the management information that is not to be reset. Next, the transmitting unit 22 transmits a message to the wireless communication node 10 indicating that setting of the management information to be reset is to be started (S22).

[0039] As described above, the wireless communication node 10 resets part of the management information included in the plurality of pieces of management information. In this case, the wireless communication node 10 transmits a message indicating that part of the management information included in the plurality of pieces of management information is to be reset to the RIC 20.

[0040] By receiving a message from the wireless communication node 10, the RIC 20 can recognize that some of the management information included in the multiple pieces of management information will be reset, and further recognize which management information is to be reset and which management information is not to be reset.

[0041] Furthermore, by recognizing the management information to be reset or the management information not to be reset, the RIC 20 can request the wireless communication node 10 to set the reset management information. In other words, the RIC 20 does not need to request the setting of all the management information, but only needs to request the setting of part of the management information that has been reset among all the management information. As a result, the processing load on the wireless communication node 10 and the RIC 20 related to the management information setting process is reduced. Furthermore, the reduction in the processing load also makes it possible to, for example, save power in the wireless communication node 10 and the RIC 20.

[0042] (Embodiment 2) Fig. 5 is a diagram showing an example of the configuration of a communication system. The communication system in Fig. 5 includes an E2 node 50, an O-RU 80, an SMO (Service Management and Orchestration) 90, a Near-RT (Near-Real-Time) RIC 110, and a UE 120. Furthermore, the E2 node 50 includes an O-CU 60 and an O-DU 70. Furthermore, the SMO 90 includes a Non-RT (Non-Real-Time) RIC 100. Each device included in the communication system may be a computer device that operates when a processor executes a program stored in a memory.

[0043] The UE 120 is used as a general term for a communication terminal. For example, the UE 120 may be a mobile phone terminal, a smartphone terminal, or an IoT (Internet of Things) terminal. The UE 120 may support a wireless communication standard known as 5G in order to perform wireless communication with the O-RU 80.

[0044] The E2 node 50 is a logical node that terminates the E2 interface. The E2 interface is an interface defined between the E2 node 50 and the Near-RT RIC 110. In other words, the E2 interface is an interface defined between the O-CU 60 and the Near-RT RIC 110, and further between the O-DU 70 and the Near-RT RIC 110. The E2 node 50 may be a physical device corresponding to either the O-CU 60 or the O-DU 70, or may be a physical device in which the O-CU 60 and the O-DU 70 are integrated. When the E2 node 50 is a physical device in which the O-CU 60 and the O-DU 70 are integrated, the E2 interface is an interface defined between the Near-RT RIC 110 and the physical device in which the O-CU 60 and the O-DU 70 are integrated.

[0045] The O-CU 60 may be, for example, a logical node that hosts RRC (Radio Resource Control) and PDCP (Packet Data Convergence Protocol). Alternatively, the O-CU 60 may be a physical device that includes the O-CU, which is a logical node. Hosting the RRC and PDCP may be rephrased as terminating the RRC protocol and PDCP, or executing processing related to the RRC protocol and PDCP, etc. Furthermore, hosting the RRC and PDCP by the O-CU 60 may be rephrased as executing processing related to the RRC layer and the PDCP layer, etc. In the following description, the term "host" may be rephrased as described above.

[0046] An O-CU that performs processing related to the C-Plane (Control Plane) part of the PDCP may be referred to as an O-CU-CP (C-Plane).Furthermore, an O-CU that performs processing related to the U-Plane (User Plane) part of the PDCP may be referred to as an O-CU-UP (U-Plane).

[0047] The O-DU 70 may be a logical node that hosts Radio Link Control (RLC) and Media Access Control (MAC). Furthermore, the O-DU 70 may be a logical node that hosts higher-level functions of the physical (PHY) layer. Alternatively, the O-DU 70 may be a physical device that incorporates the O-DU, which is a logical node. Furthermore, the O-DU 70 may perform PDCP-related processing instead of or together with the O-CU 60. The higher-level functions of the physical layer may be, for example, encoding and modulation processing, and further, decoding and demodulation processing.

[0048] The O-RU 80 may be a logical node that hosts or executes lower-level physical layer functions and RF (Radio Frequency) processing. Alternatively, the O-RU 80 may be a physical device that incorporates the O-RU, which is a logical node. The lower-level physical layer functions may be, for example, Fast Fourier Transform (FFT) / Inverse FFT (IFFT) processing, Beam Forming (BF) processing, etc.

[0049] The SMO 90 manages or supports the RAN domain. In other words, the SMO 90 performs control or optimization of the RAN domain. The RAN domain may be, for example, a network including the O-CU 60, the O-DU 70, and the O-RU 80.

[0050] For example, the SMO 90 may support FCAPS for the Near-RT RIC 110, the O-CU 60, and the O-DU 70 via the O1 interface. FCAPS indicates functions for performing fault management, configuration management, accounting management, performance management, and security management. The SMO 90 may also support FCAPS for the O-RU 80.

[0051] Furthermore, the Non-RT RIC 100 included in the SMO 90 may execute processing related to RAN optimization by, for example, communicating with the Near-RT RIC 110 via the A1 interface. RAN optimization may involve, for example, generating a control policy related to the RAN and notifying the Near-RT RIC 110 of the control policy.

[0052] The Near-RT RIC 110 is a logical function that performs near real-time control and optimization of RAN elements and resources. Alternatively, the Near-RT RIC 40 may be a physical device equipped with a logical function that performs near real-time control and optimization of RAN elements and resources. The RAN elements may be, for example, the O-CU 60 and the O-DU 70. Specifically, the Near-RT RIC 110 collects fine-grained data from the O-CU 60 or the O-DU 70 via the E2 interface. The near-real-time control may be performed, for example, at a cycle of approximately 10 ms to 1 s. The detailed data may be referred to, for example, as near-real-time information. The near-real-time information may be, for example, information on a UE basis or a cell basis.

[0053] In the following description, the RIC 20 in FIG. 1 corresponds to the Near-RT RIC 110. The Near-RT RIC 110 has the same configuration as the RIC 20. Furthermore, the wireless communication node 10 in FIG. 1 corresponds to the E2 node 50. The E2 node 50 has the same configuration as the wireless communication node 10. Furthermore, the wireless communication node 10 may be an O-CU 60 or an O-DU 70.

[0054] Here, the management information managed by the management unit 11 in the E2 node 50 will be described. Fig. 6 shows that a plurality of pieces of management information are managed. In Fig. 6, the management information is shown as Subscription. A Subscription is generated in the E2 node 50 by executing a RIC Subscription procedure between the Near-RT RIC 110 and the E2 node 50. A Subscription may also be referred to as a RIC Subscription.

[0055] Here, the RIC Subscription procedure will be described. FIG. 7 is a diagram showing the processing flow of the RIC Subscription procedure. First, the Near-RT RIC 110 transmits a RIC Subscription request message to the E2 node 50 (S31). The RIC Subscription request message includes a RIC Request ID that identifies the RIC Subscription procedure. The RIC Request ID is assigned by the Near-RT RIC 110. The RIC Subscription request message also includes a RAN Function ID. The RAN Function ID is an ID that identifies a RAN Function that the E2 node 50 can execute. The RAN Function may be, for example, a function that terminates a predetermined interface, a function that controls a UE or a cell, or the like. The RIC Subscription request message also includes an event trigger and an operation (Sequence of RIC Service Actions) to be performed when the event trigger is detected. The event trigger is information that serves as a condition for executing a desired operation. The operation to be performed when an event trigger is detected may be, for example, an operation defined as REPORT, INSERT, CONTROL, POLICY, or QUERY. These operations may also be referred to as RIC Services. The RIC Subscription request message includes a RIC EVENT TRIGGER DEFINITION IE and a RIC ACTION DEFINITION IE as information elements. The RIC Request ID and the RAN Function ID correspond to information that can identify management information that is not subject to reset.

[0056] REPORT may be the E2 node 50 transmitting information indicating the state of the UE 120 or the E2 node 50 when an event trigger is detected to the Near-RT RIC 110. INSERT may be the E2 node 50 stopping a predetermined process when an event trigger is detected in the E2 node 50. CONTROL may be the Near-RT RIC 110 instructing the E2 node 50 to start a new process or procedure or to resume a stopped process. POLICY may be the E2 node 50 executing a process or procedure to satisfy a specific policy when an event trigger is detected. QUERY may be the E2 node 50 extracting information related to the RAN or information related to the UE.

[0057] Next, the E2 node 50 transmits a RIC Subscription response message to the Near-RT RIC 110 (S32).

[0058] Subscriptions generated as a result of executing the RIC Subscription procedure are managed in the management unit 11 in association with a RIC Request ID and a RAN Function ID, as shown in Fig. 6. Fig. 6 shows that three Subscriptions with different RIC Request IDs and RAN Function IDs are managed. Fig. 6 shows an example in which the RIC Request ID and RAN Function ID for each Subscription are different from those of other Subscriptions, but for example, a common value or information may be set for the RAN Function ID for two or three Subscriptions. Furthermore, each Subscription is associated with an event trigger and an action to be taken when the event trigger is detected.

[0059] Next, the RESET procedure will be described. Fig. 8 is a diagram showing the processing flow of the RESET procedure. The RESET procedure may be executed, for example, to initialize the E2 node 50 when a failure occurs in the E2 node 50. The failure may be, for example, a software failure or a hardware failure.

[0060] A software failure may be, for example, a failure of a container or a virtual machine that constitutes an E2 node 50 operating in a virtualized environment. Furthermore, multiple containers that constitute an E2 node 50 may be managed using at least one pod. That is, one pod may include at least one container. A pod may be a logical element used to group at least one container.

[0061] Furthermore, the subscriptions managed by the E2 node 50 may be associated with pods. Being associated may be rephrased as being associated with or included in. For example, as shown in FIG. 6, Subscription #1 may be included in pod #1, Subscription #2 may be included in pod #2, and Subscription #3 may be included in pod #3. Alternatively, Subscriptions #1 and #2 may be included in pod #1. In other words, there may be a one-to-one correspondence between subscriptions and pods, or multiple subscriptions may correspond to one pod.

[0062] In an E2 node 50 that includes multiple Pods, if a failure occurs in one of the Pods, the Subscriptions included in the failed Pod also enter a state in which a failure has occurred. In other words, if a failure occurs in a Pod, the E2 node 50 will no longer be able to manage the Subscriptions associated with the failed Pod. A state in which a Subscription has failed can also be said to be a state in which the Subscription cannot be managed.

[0063] If a failure occurs in some of the Subscriptions, the E2 node 50 will include Subscriptions that are not experiencing a failure and Subscriptions that have experienced a failure. In other words, the E2 node 50 will include Subscriptions that are being managed normally and Subscriptions that cannot be managed. In yet other words, the E2 node 50 will include Subscriptions that are in a normal state and Subscriptions that are in an abnormal state.

[0064] First, the E2 node 50 sends a RESET REQUEST message to the Near-RT RIC 110 (S41). The RESET REQUEST message may include, for example, a pair of a RIC Request ID and a RAN Function ID associated with a Subscription that is not to be reset. One Subscription is identified by a pair of a RIC Request ID and a RAN Function ID. The RESET REQUEST message may include multiple pairs of a RIC Request ID and a RAN Function ID to specify multiple Subscriptions that are not to be reset. A Subscription that is to be reset is a Subscription in which a failure has occurred (a Subscription that cannot be managed or a Subscription in an abnormal state). A Subscription that is not to be reset is a Subscription in which no failure has occurred (a Subscription that is being managed normally or a Subscription in a normal state).

[0065] The RESET REQUEST message may also include a pair of a RIC Request ID and a RAN Function ID associated with the Subscription to be reset. Alternatively, the RESET REQUEST message may include all pairs of RIC Request IDs and RAN Function IDs, each indicating whether they are to be reset or not. All RIC Request IDs and RAN Function IDs may be, for example, RIC Request IDs and RAN Function IDs that respectively identify all Subscriptions managed in the E2 node 50 before the failure occurred.

[0066] Next, the Near-RT RIC 110 transmits a RESET RESPONSE message to the E2 node 50 (S42). The RESET RESPONSE message may include the RIC Request ID and RAN Function ID included in the RESET REQUEST message. The RESET RESPONSE message may also include the RIC Request ID and RAN Function ID included in the RESET REQUEST message to indicate that the Subscription identified in the RESET RESPONSE message has been recognized as normal.

[0067] Alternatively, the RESET RESPONSE message may include a RIC Request ID and a RAN Function ID that identify, among the Subscriptions identified in the RESET REQUEST message, Subscriptions that the Near-RT RIC 110 desires to continue to manage in the E2 node 50. In other words, the Near-RT RIC 110 may include a RIC Request ID and a RAN Function ID that identify Subscriptions that are not to be reset, excluding Subscriptions that are no longer needed.

[0068] Alternatively, the RESET RESPONSE message may not include the RIC Request ID and RAN Function ID that identify the Subscription.

[0069] Next, a description will be given of the RESET procedure executed in the E2 node 50. FIG.

[0070] First, the management unit 11 detects Subscriptions in a normal state when a failure occurs (S51). For example, when a failure occurs in a Pod, the management unit 11 may detect Subscriptions that can be managed as Subscriptions in a normal state. Alternatively, the management unit 11 may detect Subscriptions that can no longer be managed as Subscriptions in an abnormal state. Furthermore, detecting Subscriptions in a normal state may also mean detecting or identifying Subscriptions in an abnormal state. The failure may be a software-related failure or a hardware-related failure. Alternatively, the failure may be a virtualization environment-related failure.

[0071] Next, the communication unit 12 transmits a RESET REQUEST message including information for identifying a Subscription in a normal state to the Near-RT RIC 110 (S52). The information for identifying a Subscription in a normal state may be a pair of information of a RIC Request ID and a RAN Function ID associated with a Subscription that is not in an abnormal state.

[0072] Next, the management unit 11 resets the Subscription to be reset (S53). The Subscription to be reset may be, for example, a Subscription in an abnormal state. If there are multiple Subscriptions to be reset, the management unit 11 resets the multiple Subscriptions to be reset.

[0073] Resetting a subscription may be, for example, deleting information indicating the state of UE 120 or E2 node 50, etc., that should be transmitted to Near-RT RIC 110 when a trigger defined in the subscription to be reset is detected. Alternatively, resetting a subscription may be deleting information indicating the state of UE 120 or E2 node 50, etc., that has already been transmitted to Near-RT RIC 110 when a trigger defined in the subscription to be reset is detected. Alternatively, resetting a subscription may be removing the subscription to be reset from the list of subscriptions shown in FIG. 6 that are to be managed, or may be deleting it.

[0074] Next, the communication unit 12 receives a RESET RESPONSE message from the Near-RT RIC 110 (S54). The communication unit 12 may receive the RESET RESPONSE message before step S53. In other words, the process of resetting the Subscription and the process of receiving the RESET RESPONSE message may be independent processes that are not dependent on each other.

[0075] Next, the RESET procedure executed in the Near-RT RIC 110 will be described. Fig. 10 shows the processing flow of the RESET procedure executed in the E2 node 50. First, the receiving unit 21 receives a RESET REQUEST message from the E2 node 50 (S61). The RESET REQUEST message includes information for identifying a Subscription that is managed as being in a normal state in the E2 node 50. The information for identifying a Subscription that is managed as being in a normal state may be a RIC Request ID and a RAN Function ID associated with the Subscription that is managed as being in a normal state.

[0076] Next, the Near-RT RIC 110 notifies the application of the Subscriptions that are managed as being in a normal state (S62). The application may be, for example, an xApp defined in the O-RAN Alliance. The xApp may analyze information about the UE 120 or the E2 node 50 that the Near-RT RIC 110 acquires in a Report from the E2 node 50. The xApp may be installed in the same device as the Non-RT RIC 100, or may be installed in a device different from the Non-RT RIC 100. The Near-RT RIC 110 may notify the application of the Subscriptions that are in an abnormal state and are to be reset. Alternatively, the Near-RT RIC 110 may notify the application of all Subscriptions managed in the E2 node 50, distinguishing between Subscriptions to be reset and Subscriptions that are not to be reset.

[0077] Next, the transmitter 22 transmits a RESET RESPONSE message to the E2 node 50 (S63). Before transmitting the RESET RESPONSE message, the Near-RT RIC 110 may exclude from its management those Subscriptions that are to be reset in the E2 node 50, among the Subscriptions managed by the Near-RT RIC 110. Alternatively, after transmitting the RESET RESPONSE message, the Near-RT RIC 110 may exclude from its management those Subscriptions that are to be reset in the E2 node 50, among the Subscriptions managed by the Near-RT RIC 110. Excluding a Subscription from its management may mean deleting the Subscription or releasing resources that were used to manage the Subscription. By the Near-RT RIC 110 excluding from its management those Subscriptions that are to be reset in the E2 node 50, the Subscriptions managed by the Near-RT RIC 110 and the E2 node 50 become the same.

[0078] Next, the transmitter 22 starts the RIC Subscription procedure for the Subscription to be reset (S64). Specifically, the transmitter 22 sends a RIC Subscription Request message shown in FIG. 6 to the E2 node 50. At this time, the transmitter 22 starts the RIC Subscription procedure to resume or create the Subscription to be reset. If there are multiple Subscriptions to be reset, the RIC Subscription procedure is executed repeatedly the same number of times as the number of Subscriptions to be reset.

[0079] As described above, the E2 node 50 resets only the Subscriptions that are in an abnormal state among the multiple Subscriptions. In addition, the E2 node 50 transmits a RESET RESPONSE message including information identifying the Subscriptions that are in a normal state or the Subscriptions that are in an abnormal state to the Near-RT RIC 110.

[0080] The Near-RT RIC 110 resumes or sets the subscriptions as a result of the subscription being reset in the E2 node 50. At this time, if the Near-RT RIC 110 resumes all subscriptions that have been set in the E2 node 50 by the RIC subscription procedure, it needs to execute the RIC subscription procedure as many times as the number of subscriptions. On the other hand, by receiving the RESET REQUEST message, the Near-RT RIC 110 can determine which subscriptions are being managed correctly in the E2 node 50. Therefore, the Near-RT RIC 110 can omit the RIC subscription procedure for subscriptions that are being managed correctly.

[0081] FIG. 11 is a block diagram showing an example configuration of a wireless communication node 10, a RIC 20, an E2 node 50, and a Near-RT RIC 110 (hereinafter referred to as Near-RT RIC 110, etc.). Referring to FIG. 11, the RIC 10, etc. includes a network interface 1201, a processor 1202, and a memory 1203. The network interface 1201 is used to communicate with each other's network nodes. The network interface 1201 may include, for example, a network interface card (NIC) conforming to the IEEE 802.3 series. Here, IEEE stands for Institute of Electrical and Electronics Engineers.

[0082] The processor 1202 reads and executes software (computer programs) from the memory 1203 to perform the processing of the Near-RT RIC 110 and the like described using the flowcharts. The processor 1202 may be, for example, a microprocessor, an MPU, or a CPU. The processor 1202 may include multiple processors.

[0083] The memory 1203 is configured by a combination of volatile memory and non-volatile memory. The memory 1203 may include storage located remotely from the processor 1202. In this case, the processor 1202 may access the memory 1203 via an I / O (Input / Output) interface (not shown).

[0084] 11, the memory 1203 is used to store software modules. The processor 1202 reads and executes these software modules from the memory 1203, thereby performing the processing of the Near-RT RIC 110 and the like described in the above-described embodiment.

[0085] As explained using FIG. 11, each of the processors of the Near-RT RIC 110 and the like in the above-described embodiments executes one or more programs including a set of instructions for causing a computer to perform the algorithm explained using the drawings.

[0086] In the above examples, the program includes instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more functions described in the embodiments. The program may be stored on a non-transitory computer-readable medium or a tangible storage medium. By way of example and not limitation, computer-readable medium or tangible storage medium includes random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disc (DVD), Blu-ray disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The program may also be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, transitory computer-readable medium or communication medium includes electrical, optical, acoustic, or other forms of propagated signals.

[0087] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above-described embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0088] Each drawing is merely an example for describing one or more embodiments. Each drawing may not relate to only one particular embodiment, but may also relate to one or more other embodiments. As will be understood by those skilled in the art, various features or steps described with reference to any one drawing can be combined with features or steps shown in one or more other drawings to create, for example, an embodiment not explicitly shown or described. Not all features or steps shown in any one drawing are necessary to describe an exemplary embodiment, and some features or steps may be omitted. The order of steps described in any drawing may be changed as appropriate.

[0089] Some or all of the above embodiments can be described as, but are not limited to, the following supplementary notes. (Supplementary Note 1) A wireless communication node comprising: a management unit that manages a plurality of pieces of management information, each of which associates an event with an operation triggered by the event; and a communication unit that transmits a message indicating that at least one piece of management information among the plurality of pieces of management information will be reset to a RAN Intelligent Controller (RIC), wherein the message includes information that can identify second management information that is not to be reset. (Supplementary Note 2) The wireless communication node according to Supplementary Note 1, wherein the information that can identify the second management information that is not to be reset is identification information of the second management information. (Supplementary Note 3) The wireless communication node according to Supplementary Note 2, wherein the identification information of the second management information is a RIC Request ID and a RAN Function ID of the second management information. (Supplementary Note 4) The wireless communication node according to any one of Supplements 1 to 3, wherein the management unit resets first management information that is to be reset among the plurality of pieces of management information. (Supplementary Note 5) The wireless communication node according to Supplementary Note 4, wherein the management unit resets the first management information after transmitting the message. (Supplementary Note 6) The wireless communication node according to any one of Supplementary Notes 1 to 5, wherein the communication unit receives from the RIC a second message indicating that setting of first management information of at least one reset target that has been reset is to be started, and the management unit sets the first management information specified in the second message. (Supplementary Note 7) The RIC includes: a receiving unit that receives, from a wireless communication node having a plurality of pieces of management information in which an event is associated with an action that occurs as a trigger of the event, a first message indicating that at least one management information among the plurality of pieces of management information is to be reset; and a transmitting unit that transmits to the wireless communication node a second message indicating that setting of the first management information of the reset target is to be started, the first message including information that can identify second management information that is not to be reset. (Supplementary Note 8) The RIC according to Supplementary Note 7, wherein the information that can identify the second management information that is not to be reset is identification information of the second management information.(Supplementary Note 9) The RIC according to Supplementary Note 7 or 8, wherein the identification information of the second management information is a RIC Request ID and a RAN Function ID of the second management information. (Supplementary Note 10) A communication method comprising: managing a plurality of pieces of management information in which an event and an operation triggered by the event are associated with each other; transmitting a message indicating that at least one piece of management information among the plurality of pieces of management information is to be reset to a RIC (RAN Intelligent Controller), the message including information capable of identifying second management information that is not to be reset. (Supplementary Note 11) A communication method comprising: receiving a first message indicating that at least one piece of management information among the plurality of pieces of management information is to be reset from a wireless communication node having a plurality of pieces of management information in which an event and an operation triggered by the event are associated with each other; the first message including information capable of identifying second management information that is not to be reset; and transmitting a second message to the wireless communication node to start setting of the first management information that is to be reset. (Supplementary Note 12) A program causing a computer to manage a plurality of pieces of management information in which events and operations triggered by the events are associated with each other, and to transmit to a RAN Intelligent Controller (RIC) a message indicating that at least one piece of management information among the plurality of pieces of management information is to be reset, the message including information by which second management information not to be reset can be identified. (Supplementary Note 13) A program causing a computer to receive, from a wireless communication node having a plurality of pieces of management information in which events and operations triggered by the events are associated with each other, a first message indicating that at least one piece of management information among the plurality of pieces of management information is to be reset, the first message including information by which second management information not to be reset can be identified, and to transmit to the wireless communication node a second message starting setting of the first management information to be reset.

[0090] Some or all of the elements (e.g., configurations and functions) described in Supplementary Notes 2 to 6 that are dependent on Supplementary Note 1 may also be dependent on Supplementary Notes 10 and 12 in the same dependency relationship as Supplementary Notes 2 to 6. Some or all of the elements (e.g., configurations and functions) described in Supplementary Notes 8 to 9 that are dependent on Supplementary Note 7 may also be dependent on Supplementary Notes 11 and 13 in the same dependency relationship as Supplementary Notes 8 to 9. Some or all of the elements described in any Supplementary Note may be applicable to various hardware, software, recording means for recording software, systems, and methods.

[0091] Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the invention.

[0092] This application claims priority based on Japanese Patent Application No. 2024-45800, filed March 22, 2024, the disclosure of which is incorporated herein in its entirety by reference.

[0093] 10 Wireless communication node 11 Management section 12 Communication section 20 RIC 21 Receiving section 22 Transmission section 50 E2 node 51 Communication section 52 Management section 60 O-CU 70 O-DU 80 O-RU 90 SMO 100 Non-RT RIC 110 Near-RT RIC 120 UE

Claims

1. A wireless communication node comprising: a management means for managing a plurality of pieces of management information in which events are associated with actions triggered by the events; and a communication means for transmitting a message to a RIC (RAN Intelligent Controller) indicating that at least one piece of management information among the plurality of pieces of management information is to be reset, wherein the message includes information capable of identifying a second piece of management information that is not to be reset.

2. The wireless communication node according to claim 1, wherein the information that can identify the second management information that is not to be reset is identification information of the second management information.

3. The wireless communication node according to claim 1 or 2, wherein the identification information of the second management information is a RIC Request ID and a RAN Function ID of the second management information.

4. The wireless communication node according to claim 1 or 2, wherein the management means resets first management information to be reset among the plurality of pieces of management information.

5. The wireless communication node according to claim 4, wherein said management means resets said first management information after transmitting said message.

6. A wireless communication node as described in claim 1 or 2, wherein the communication means receives a second message from the RIC to initiate setting of first management information for at least one reset target, and the management means sets the first management information specified in the second message.

7. A RIC comprising: a receiving means for receiving, from a wireless communication node having a plurality of pieces of management information in which an event is associated with an action triggered by the event, a first message indicating that at least one of the plurality of pieces of management information is to be reset; and a transmitting means for transmitting, to the wireless communication node, a second message including information capable of identifying second management information that is not to be reset, the second message initiating the setting of the first management information that is to be reset.

8. The RIC according to claim 7, wherein the information capable of identifying the second management information not to be reset is identification information of the second management information.

9. The RIC according to claim 7 or 8, wherein the identification information of the second management information is a RIC Request ID and a RAN Function ID of the second management information.

10. A communication method comprising: managing a plurality of pieces of management information in which events are associated with actions triggered by the events; transmitting a message to a RAN Intelligent Controller (RIC) indicating that at least one piece of management information among the plurality of pieces of management information is to be reset; and the message including information capable of identifying a second piece of management information that is not to be reset.

11. A communication method comprising: receiving, from a wireless communication node having a plurality of pieces of management information in which events are associated with actions triggered by the events, a first message indicating that at least one piece of management information among the plurality of pieces of management information is to be reset; the message including information capable of identifying second management information that is not to be reset; and transmitting to the wireless communication node a second message that initiates setting of the first management information to be reset.

12. A program that causes a computer to manage multiple pieces of management information in which events are associated with actions that occur when the events are triggered, and to send to a RAN Intelligent Controller (RIC) a message indicating that at least one piece of management information is to be reset, the message including information that can identify second management information that is not to be reset.

13. A program that causes a computer to receive, from a wireless communication node having multiple pieces of management information in which events are associated with actions triggered by the events, a first message indicating that at least one of the multiple pieces of management information is to be reset, the first message including information that can identify second management information that is not to be reset, and to send to the wireless communication node a second message that starts setting the first management information that is to be reset.

Images