RIC, communication system, communication method, and program

Abstract

The purpose of the present invention is to provide an RIC capable of efficiently deleting corresponding information. An RIC according to the present disclosure comprises a transmission unit that transmits a request message for requesting the deletion of a plurality of pieces of management information to a wireless communication node that has management information in which an event trigger and an operation at the time when the event trigger is detected are associated with each other.

Description

RIC, communication system, communication method and program

[0001] The present disclosure relates to a RIC, a communication system, 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, defines 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 defines a RIC Subscription procedure, which is a procedure by which the Near-RT RIC collects various information from E2 nodes including O-CU and O-DU in response to an event that occurs.

[0004] O-RAN.WG3.E2AP-R003-v04.00

[0005] When the RIC Subscription procedure is executed, the E2 node manages management information that corresponds to an event that triggers the transmission of information to the Near-RT RIC and the action to be taken when the event occurs. Also, when multiple RIC Subscription procedures are executed, the E2 node manages multiple pieces of management information. On the other hand, when management information is no longer needed, the Near-RT RIC requests the E2 node to delete the management information. However, when the Near-RT RIC requests the deletion of multiple pieces of management information managed by the E2 node, there is a problem in that as the number of pieces of management information to be deleted increases, the processing burden on the Near-RT RIC and the E2 node associated with deleting the management information increases.

[0006] In view of the above-mentioned problems, an object of the present disclosure is to provide a RIC, a communication system, a communication method, and a program that can efficiently delete management information.

[0007] The RIC according to the present disclosure includes a transmitting unit that transmits a request message to a wireless communication node having management information that associates an event with an action that occurs as a trigger of the event, requesting the deletion of multiple pieces of management information.

[0008] The communication system according to the present disclosure includes a RIC that transmits a request message requesting the deletion of multiple pieces of management information that correspond to an event and an action that occurs as a trigger of the event, and a wireless communication node that deletes the multiple pieces of management information when the request message is received.

[0009] The communication method according to the present disclosure includes sending a request message to a wireless communication node that manages management information that associates events with actions that occur as triggers of the events, requesting the deletion of multiple pieces of management information, and receiving a response message to the request message.

[0010] The program of the present disclosure causes a computer to send a request message to a wireless communication node that manages management information that associates events with actions that occur as triggers of the events, requesting the deletion of multiple pieces of management information, and receive a response message to the request message.

[0011] The present disclosure makes it possible to provide a RIC, a communication system, a communication method, and a program that can efficiently delete correspondence information.

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

[0013] (First Embodiment) Fig. 1 shows an example configuration of a RIC 10 according to the present disclosure. The RIC 10 may be a computer device that operates when a processor executes a program stored in a memory. The RIC 10 may be a single computer device or a group of computers configured from multiple computers. The RIC 10 may be a Near-RT RIC or a Non-RT RIC.

[0014] The RIC 10 has a transmitting unit 11. The transmitting unit 11 may be software or a module that performs processing by a processor executing a program stored in a memory. Alternatively, the transmitting unit 11 may be hardware such as a circuit or a chip. The transmitting unit 11 may be used as a transmitting means for transmitting information. The transmitting unit 11 may also be referred to as a communication unit.

[0015] The transmitting unit 11 transmits a request message to the wireless communication node 20 having management information in which events and actions triggered by the events are associated with each other, requesting deletion of a plurality of pieces of management information. The events may be called event triggers. The event trigger is an event-type trigger.

[0016] The event trigger may be a communication terminal or a wireless communication node 20 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, the event trigger may be an application executed by the communication terminal or the wireless communication node 20 entering a predetermined state. Alternatively, the event trigger may be a communication state in the communication terminal or the wireless communication node 20 reaching a specific state. Alternatively, the event trigger may be a change in the environment surrounding the communication terminal. Alternatively, the event trigger may be a change in information held or managed by the communication terminal or the wireless communication node 20. Alternatively, the event trigger may be a change in information specific to the communication terminal or the wireless communication node 20.

[0017] For example, the event trigger 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 20 changes.

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

[0019] It is assumed that the wireless communication node 20 has a plurality of pieces of management information. That is, the wireless communication node 20 has a plurality of event triggers. Therefore, every time the wireless communication node 20 detects an event trigger, it executes an operation associated with the event trigger.

[0020] The wireless communication node 20 may be an E2 node. Alternatively, the wireless communication node 20 may be either an O-CU or an O-DU included in an E2 node. The O-CU and O-DU may simply be referred to as a CU device and a DU device.

[0021] The request message may include, for example, multiple pieces of identification information indicating multiple pieces of management information to be deleted. Alternatively, the request message may include common identification information assigned to the multiple pieces of management information. Alternatively, the request message may include information common to the multiple pieces of management information to be deleted. The information common to the multiple pieces of management information may be, for example, information indicating an event trigger common to the multiple pieces of management information, or information indicating an operation common to the multiple pieces of management information. Alternatively, the information common to the multiple pieces of management information may be a communication terminal or wireless communication node 20 to be monitored for an event trigger.

[0022] Next, a description will be given of the flow of communication processing executed in the RIC 10. FIG.

[0023] First, the transmitter 11 transmits a request message to the wireless communication node 20 having management information in which an event trigger is associated with an action to be taken when the event trigger is detected, requesting the deletion of multiple pieces of management information (S11). Next, the RIC 10 receives a response message to the request message (S12). The response message may be, for example, a message indicating that the deletion of the multiple pieces of management information has been completed.

[0024] As described above, the RIC 10 transmits a request message to the wireless communication node 20 requesting the deletion of multiple pieces of management information managed in the wireless communication node 20. This allows the wireless communication node 20 to delete the multiple pieces of management information specified in the request message. As a result, when deleting multiple pieces of management information, the number of messages transmitted between the RIC 10 and the wireless communication node 20 can be reduced compared to when the RIC 10 transmits a request message for each piece of management information to be deleted. This makes it possible to save power in communications including the RIC and the wireless communication node.

[0025] (Embodiment 2) Fig. 3 is a diagram showing an example of the configuration of a communication system. The communication system of Fig. 3 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.

[0026] 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.

[0027] 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.

[0028] 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.

[0029] 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).

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] In the following description, the RIC 10 in Fig. 1 corresponds to the Near-RT RIC 110. Furthermore, the wireless communication node 20 in Fig. 1 corresponds to the E2 node 50. Furthermore, the wireless communication node 20 may be an O-CU 60 or an O-DU 70.

[0037] 4 shows an example of the configuration of an E2 node 50. The E2 node 50 may be a computer device that operates when a processor executes a program stored in a memory. The E2 node 50 may be a single computer device or a group of computers configured from multiple computer devices.

[0038] The E2 node 50 has a communication unit 51 and a management unit 52. The communication unit 51 and the management unit 52 may be software or modules that perform processing when a processor executes a program stored in a memory. Alternatively, the communication unit 51 and the management unit 52 may be hardware such as a circuit or a chip. The communication unit 51 may be used as a means for transmitting or receiving information. The management unit 52 may be used as a means for managing information.

[0039] The communication unit 51 transmits messages to the Near-RT RIC 110 and further receives messages from the Near-RT RIC 110. The management unit 52 manages management information in which event triggers are associated with actions to be taken when the event triggers are detected. For example, the management unit 52 may record, memorize, store, or preserve the management information in a memory or the like within the E2 node 50. The management unit 52 may add management information to a memory or the like within the E2 node 50, or delete management information from a memory or the like within the E2 node 50, and may also update the management information stored in a memory or the like within the E2 node 50.

[0040] Here, the management information managed by the management unit 52 will be described. Fig. 5 shows that a plurality of pieces of management information are managed. In Fig. 5, 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.

[0041] Here, the RIC Subscription procedure will be described. FIG. 6 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 (S21). 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.

[0042] 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.

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

[0044] Subscriptions generated as a result of executing the RIC Subscription procedure are managed in the management unit 52 in association with a RIC Request ID and a RAN Function ID, as shown in Fig. 5. Fig. 5 shows that three subscriptions with different RIC Request IDs and RAN Function IDs are managed. Fig. 5 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.

[0045] Next, the process of deleting a subscription will be described. Fig. 7 is a diagram showing the process flow of the RIC Subscription Delete procedure. First, the Near-RT RIC 110 sends a RIC SUBSCRIPTION DELETE REQUEST message to the E2 node 50 (S31). The RIC SUBSCRIPTION DELETE REQUEST message includes multiple pairs of RIC Request IDs and RAN Function IDs associated with the SUBSCRIPTION to be deleted.

[0046] The RIC SUBSCRIPTION DELETE REQUEST message may include, for example, multiple pairs associated with each SUBSCRIPTION to be deleted. For example, a case will be described in which three SUBSCRIPTIONs, SUBSCRIPTION #1 to #3 shown in FIG. 5, are to be deleted.

[0047] For example, the RIC SUBSCRIPTION DELETE REQUEST message may include an information element called a Pair ID List. Three pairs may be set in the Pair ID List, such as (RIC Request ID: RAN Function ID = 1:1, 2:2, 3:3). Alternatively, the RIC SUBSCRIPTION DELETE REQUEST message may include an information element called a RIC Request ID List and an information element called a RAN Function ID List. RIC Request IDs may be set in the RIC Request ID List, such as (RIC Request ID = 1, 2, 3), and RAN Function IDs may be set in the RAN Function ID List, such as (RAN Function ID = 1, 2, 3). In this case, the first ID in each list becomes a pair, and similarly, the second ID and the third ID become a pair.

[0048] Alternatively, the RIC SUBSCRIPTION DELETE REQUEST message may include a RIC Request ID, one RAN Function ID, and a Pair ID List. In this case, for example, the RIC SUBSCRIPTION DELETE REQUEST message may include information elements such as RIC Request ID = 1, RAN Function ID = 1, and a Pair ID List of (RIC Request ID:RAN Function ID = 2:2, 3:3).

[0049] Alternatively, the RIC SUBSCRIPTION DELETE REQUEST message may include one RIC Request ID and one RAN Function ID, and may further include a RIC Request ID List and a RAN Function ID List. In this case, for example, the RIC SUBSCRIPTION DELETE REQUEST message may include a RIC Request ID = 1 and a RAN Function ID = 1. Furthermore, the RIC SUBSCRIPTION DELETE REQUEST message may include information elements with a RIC Request ID List (RIC Request ID = 2, 3) and a RAN Function ID List (RAN Function ID = 2, 3).

[0050] Furthermore, when deleting multiple subscriptions that share a common RAN function, the RIC SUBSCRIPTION DELETE REQUEST message may include only the RAN Function ID, without including the RIC Request ID. Alternatively, when deleting multiple subscriptions that are associated with a common event trigger, the RIC SUBSCRIPTION DELETE REQUEST message may include information indicating the common event trigger. Alternatively, when deleting multiple subscriptions that are associated with a common action when an event trigger is detected, the RIC SUBSCRIPTION DELETE REQUEST message may include information indicating the common action.

[0051] The E2 node 50 deletes the SUBSCRIPTION identified by the RIC Request ID and RAN Function ID specified in the RIC SUBSCRIPTION DELETE REQUEST message. Furthermore, the E2 node 50 may release resources used to manage the SUBSCRIPTION. The resources may be, for example, memory space in the E2 node 50, processor speed, etc.

[0052] After deleting the SUBSCRIPTION, the E2 node 50 transmits a RIC SUBSCRIPTION DELETE RESPONSE message to the Near-RT RIC 110 (S32). Upon receiving the RIC SUBSCRIPTION DELETE RESPONSE message, the Near-RT RIC 110 may release resources related to the deleted SUBSCRIPTION. The resources related to the SUBSCRIPTION may be resources used to manage the RIC Request ID and RAN Function ID associated with the SUBSCRIPTION.

[0053] Here, it is assumed that the E2 node 50 has deleted only some of the subscriptions that were targeted for deletion in the RIC SUBSCRIPTION DELETE REQUEST message. In this case, the E2 node 50 may transmit to the Near-RT RIC 110 a RIC SUBSCRIPTION DELETE RESPONSE message that includes the values ​​of the RIC Request ID and RAN Function ID associated with the deleted subscription.

[0054] The Near-RT RIC 110 recognizes pairs of RIC Request ID and RAN Function ID included in the RIC SUBSCRIPTION DELETE REQUEST message that are not included in the RIC SUBSCRIPTION DELETE RESPONSE message as undeleted pairs.

[0055] The Near-RT RIC 110 may resend a RIC SUBSCRIPTION DELETE REQUEST message including the RIC Request ID and RAN Function ID of the undeleted pair to the E2 node 50. This may allow the Near-RT RIC 110 to reattempt to delete the SUBSCRIPTION associated with the pair that was not deleted in the initial RIC SUBSCRIPTION DELETE REQUEST message.

[0056] Alternatively, the E2 node 50 may include the RIC Request ID and RAN Function ID associated with the SUBSCRIPTION that was not deleted in the RIC SUBSCRIPTION DELETE RESPONSE message.

[0057] Alternatively, the E2 node 50 may include, in the RIC SUBSCRIPTION DELETE RESPONSE message, information indicating the timing at which a RIC SUBSCRIPTION DELETE REQUEST message for a SUBSCRIPTION that has not been deleted can be transmitted. The information indicating the timing may be, for example, information indicating N milliseconds later, N seconds later (N is a positive real number), or the like.

[0058] As described above, the Near-RT RIC 110 transmits a RIC SUBSCRIPTION DELETE REQUEST message targeting multiple SUBSCRIPTIONS managed by the E2 node 50. This reduces the number of messages transmitted compared to transmitting a RIC SUBSCRIPTION DELETE REQUEST message specifying each of the multiple SUBSCRIPTIONS managed by the E2 node 50. Furthermore, by reducing the number of messages transmitted, the Near-RT RIC 110 can reduce the processing load associated with transmitting messages.

[0059] The operations described in the second embodiment may also be performed when the Non-RT RIC 100 deletes a SUBSCRIPTION or other information managed in the E2 node 50. In this case, the message names and the like are not limited to the RIC SUBSCRIPTION DELETE REQUEST message and the RIC SUBSCRIPTION DELETE RESPONSE message.

[0060] FIG. 8 is a block diagram showing an example configuration of a RIC 10, a Near-RT RIC 110, and an E2 node 50 (hereinafter referred to as RIC 10, etc.). Referring to FIG. 8, 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.

[0061] The processor 1202 reads and executes software (computer programs) from the memory 1203 to perform the processing of the RIC 10 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.

[0062] 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).

[0063] 8, the memory 1203 is used to store software modules. The processor 1202 reads these software modules from the memory 1203 and executes them to perform the processing of the RIC 10 and the like described in the above-described embodiment.

[0064] As explained using FIG. 8, each of the processors of the RIC 10 and the like in the above-described embodiments executes one or more programs including a group of instructions for causing a computer to perform the algorithms explained using the drawings.

[0065] 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.

[0066] 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.

[0067] 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.

[0068] Some or all of the above embodiments can be described as, but are not limited to, the following supplementary notes. (Supplementary Note 1) A RIC comprising a transmitter that transmits a request message requesting deletion of multiple pieces of management information to a wireless communication node having management information in which an event is associated with an operation triggered by the event. (Supplementary Note 2) The RIC according to Supplementary Note 1, wherein the request message includes multiple pieces of identification information that identify the multiple pieces of management information to be deleted. (Supplementary Note 3) The RIC according to Supplementary Note 2, wherein the request message includes first identification information that identifies first management information to be deleted, and list information that summarizes at least one piece of management information other than the first management information. (Supplementary Note 4) The RIC according to Supplementary Note 2 or 3, wherein the identification information includes a RIC Request ID and a RAN Function ID. (Supplementary Note 5) The RIC according to any one of Supplements 1 to 3, further comprising a receiver that receives a response message from the wireless communication node, the response message including a result of executing deletion of the management information. (Supplementary Note 6) The RIC according to Supplementary Note 5, wherein a result of executing the deletion of the management information includes at least one deleted piece of management information that has been successfully deleted from the plurality of pieces of management information. (Supplementary Note 7) The RIC according to Supplementary Note 6, wherein the transmitting unit transmits the request message to the wireless communication node, targeting undeleted management information that has not been notified as deleted management information from the plurality of pieces of management information indicated as pieces of management information to be deleted in the request message. (Supplementary Note 8) A communication system comprising: a RIC that transmits a request message requesting deletion of a plurality of pieces of management information, each piece of management information being associated with an event and an action that is triggered by the event; and a wireless communication node that deletes the plurality of pieces of management information upon receiving the request message. (Supplementary Note 9) A communication method comprising: transmitting a request message requesting deletion of a plurality of pieces of management information to a wireless communication node that manages management information, each piece of management information being associated with an event and an action that is triggered by the event; and receiving a response message to the request message.(Supplementary Note 10) A program that causes a computer to execute the following: sending a request message to a wireless communication node that manages management information in which events and actions that occur as triggers of the events are associated with each other, requesting deletion of multiple pieces of management information; and receiving a response message to the request message.

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

[0070] This application claims priority based on Japanese Patent Application No. 2024-028113, filed February 28, 2024, the disclosure of which is incorporated herein in its entirety by reference.

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

Claims

1. A RIC comprising a transmitting means for transmitting a request message to a wireless communication node having management information in which an event and an action that occurs as a trigger of the event are associated with each other, requesting deletion of a plurality of pieces of management information.

2. The RIC according to claim 1, wherein the request message includes a plurality of pieces of identification information that identify the plurality of pieces of management information to be deleted.

3. The RIC described in claim 2, wherein the request message includes first identification information that identifies the first management information to be deleted and list information that summarizes at least one of the management information other than the first management information.

4. The RIC according to claim 2 or 3, wherein the identification information includes a RIC Request ID and a RAN Function ID.

5. The RIC according to any one of claims 1 to 3, further comprising receiving means for receiving a response message including a result of executing the deletion of the management information from the wireless communication node.

6. The RIC according to claim 5, wherein the result of executing the deletion of the management information includes at least one deleted management information item that has been successfully deleted from among the plurality of management information items.

7. The RIC according to claim 6, wherein the transmitting means transmits the request message to the wireless communication node, specifying undeleted management information that has not been notified as deleted management information as the target for deletion from among the plurality of management information indicated as the target for deletion in the request message.

8. A communication system comprising: a RIC that transmits a request message requesting the deletion of multiple pieces of management information that correspond to an event and an action that occurs when the event is triggered; and a wireless communication node that deletes the multiple pieces of management information when the request message is received.

9. A communication method comprising: transmitting a request message to a wireless communication node that manages management information in which events are associated with actions that occur as triggers of the events, requesting the deletion of multiple pieces of management information; and receiving a response message to the request message.

10. A program that causes a computer to send a request message to a wireless communication node that manages management information that associates events with actions that occur as triggers of the events, requesting the deletion of multiple pieces of management information, and receive a response message to the request message.

Images