First RIC, second RIC, management node, communication method, and program

Abstract

The objective of the present invention is to provide a first RAN Intelligent Controller (RIC) capable of sharing information specific to UE between Near-Real Time (RT) RICs before and after handover of the UE. A first RIC according to the present disclosure comprises: a receiving unit that receives communication terminal information specific to a communication terminal from a radio communication node; and a transmitting unit that, when handover of the communication terminal is performed, transmits identification information of the communication terminal and the communication terminal information or related information relating to the communication terminal information to a management node that manages the first RIC and a second RIC.

Description

First RIC, second RIC, management node, communication method and program

[0001] The present disclosure relates to a first RIC, a second RIC, a management node, 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 function of a Near-Real Time RAN Intelligent Controller (Near RT RIC) as a node for realizing RAN intelligence that realizes autonomous RAN operation. Non-Patent Document 1 describes that the Near RT RIC acquires information specific to a UE (User Equipment) corresponding to a communication terminal from an E2 node including an O-CU and an O-DU by using a REPORT service.

[0004] ORAN.WG3.E2SM-RC-R003-v04.00

[0005] The UE communicates using, for example, the O-RU and 5G, a wireless communication standard defined by 3GPP (3rd Generation Partnership Project) (registered trademark). Furthermore, when the UE moves from a current cell to a different cell, it continues communication by performing a handover. When the UE performs a handover, the Near-RT RIC (hereinafter referred to as the "first Near-RT RIC") that manages the E2 node that forms the cell before the UE moves may be different from the Near-RT RIC (hereinafter referred to as the "second Near-RT RIC") that manages the E2 node that forms the cell after the UE moves. In this case, there is a problem in that the second Near-RT RIC cannot recognize the UE-specific information held by the first Near-RT RIC.

[0006] The object of the present disclosure is to provide a first RIC, a second RIC, a management node, a communication method, and a program that can share information specific to a UE between Near-RT RICs before and after a UE handover.

[0007] The first RIC of the present disclosure comprises a receiving unit that receives communication terminal information specific to the communication terminal from a wireless communication node, and a transmitting unit that, when a handover of the communication terminal is performed, transmits identification information of the communication terminal and the communication terminal information or related information related to the communication terminal information to a management node that manages the first RIC and the second RIC.

[0008] The second RIC of the present disclosure comprises a transmitting unit that transmits identification information of the communication terminal to a management node that manages the first RIC and the second RIC when a handover of the communication terminal is performed, a receiving unit that receives from the management node communication terminal information specific to the communication terminal or related information related to the communication terminal information that the first RIC has received from a wireless communication node, and a management unit that manages the communication terminal information or the related information.

[0009] The management node of the present disclosure includes a receiving unit that receives communication terminal information specific to a communication terminal or related information related to the communication terminal information and first identification information of the communication terminal from a first RIC, and receives second identification information of the communication terminal from a second RIC, a determining unit that determines whether the first identification information and the second identification information are information that identifies the communication terminal, and a transmitting unit that transmits the communication terminal information or the related information to the second RIC when it is determined that the first identification information and the second identification information are information that identifies the communication terminal.

[0010] The communication method disclosed herein receives communication terminal information specific to a communication terminal from a wireless communication node, and when a handover of the communication terminal is performed, transmits identification information of the communication terminal and the communication terminal information or related information related to the communication terminal information to a management node that manages a first RIC and a second RIC.

[0011] The program disclosed herein causes a computer to receive communication terminal information specific to a communication terminal from a wireless communication node, and when a handover of the communication terminal is performed, to transmit identification information of the communication terminal and the communication terminal information or related information related to the communication terminal information to a management node that manages a first RIC and a second RIC.

[0012] The present disclosure provides a first RIC, a second RIC, a management node, a communication method, and a program that can share information specific to a UE between Near-RT RICs before and after a UE handover.

[0013] FIG. 1 shows an example configuration of a RIC according to the present disclosure. FIG. 2 shows an example configuration of a RIC according to the present disclosure. FIG. 3 shows an example configuration of a management node according to the present disclosure. FIG. 4 shows a diagram illustrating a flow of communication processing executed in a RIC according to the present disclosure. FIG. 5 shows a diagram illustrating a flow of communication processing executed in a RIC according to the present disclosure. FIG. 6 shows a diagram illustrating a flow of communication processing executed in a management node according to the present disclosure. FIG. 7 shows an example configuration of a communication system. FIG. 8 shows an example configuration of a Non-RT RIC and a Near-RT RIC. FIG. 9 shows a diagram illustrating a processing flow related to a RIC subscription procedure. FIG. 10 shows a diagram illustrating a processing flow related to a RIC subscription procedure. FIG. 11 shows a specific example of a UE ID. FIG. 12 shows a specific example of a UE ID. FIG. 13 shows a specific example of a UE ID. FIG. 14 shows a diagram illustrating a processing flow related to a RIC subscription procedure executed in a Near-RT RIC that manages a UE after handover. FIG. 15 shows a UE ID determination process in a Non-RT RIC. FIG. 16 is a block diagram showing an example of the configuration of a RIC, a wireless communication node, a Near-RT RIC, and a Non-RT RIC.

[0014] (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.

[0015] The RIC 10 has a receiving unit 11 and a transmitting unit 12. The receiving unit 11 and the transmitting unit 12 may be software or a module in which processing is performed by a processor executing a program stored in a memory. Alternatively, the receiving unit 11 and the transmitting unit 12 may be hardware such as a circuit or a chip. The receiving unit 11 may be used as a receiving means for receiving information. The transmitting unit 12 may be used as a transmitting means for transmitting information. The receiving unit 11 and the transmitting unit 12 may be referred to as a communication unit.

[0016] The receiving unit 11 receives communication terminal information unique to the communication terminal from the wireless communication node 30. The communication terminal and the wireless communication node 30 may be computer devices that operate when a processor executes a program stored in a memory.

[0017] The communication terminal may be a smartphone terminal, a tablet terminal, an IoT (Internet of Things) terminal, etc. The communication terminal may be a UE, which is used as a general term for communication terminals in 3GPP.

[0018] The wireless communication node 30 may be an E2 node. Alternatively, the wireless communication node 30 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.

[0019] The communication terminal information specific to the communication terminal may be information collected by the wireless communication node 30 from the communication terminal, or may be information generated by the wireless communication node 30. The information collected by the wireless communication node 30 from the communication terminal may be information indicating the state of the communication terminal or setting information for the operation of the communication terminal. The information generated by the wireless communication node 30 may be, for example, information related to the results of observing or monitoring communication performed by the communication terminal, information obtained by measuring the communication terminal or the environment surrounding the communication terminal, etc.

[0020] The receiving unit 11 may receive the communication terminal information transmitted from the wireless communication node 30 in response to a request from the RIC 10 to transmit the communication terminal information to the wireless communication node 30. Alternatively, the receiving unit 11 may receive the communication terminal information transmitted autonomously from the wireless communication node 30.

[0021] When a handover of a communication terminal is performed, the transmitter 12 transmits the identification information of the communication terminal and the communication terminal information or related information related to the communication terminal information to the management node that manages the RIC 10 and the RIC 20.

[0022] For example, when the radio wave reception strength in the cell in which the communication terminal is located decreases, the communication terminal continues communication by handing over to another cell. Here, the handover may involve a change of the E2 node that manages the O-RU, or a change of the RIC 10 that communicates with the E2 node. The change of the E2 node may be a change of the O-DU or a change of the O-CU. The RIC 10 that communicates with the E2 node may be rephrased as the RIC 10 that manages the E2 node.

[0023] The identification information of the communication terminal may be information that uniquely identifies the communication terminal. The identification information of the communication terminal may be, for example, information that is set at the time of manufacturing the communication terminal as information for identifying the communication terminal. Alternatively, the identification information of the communication terminal may be, for example, information that is assigned by the wireless communication node 30 or a core network node that manages the RAN when the communication terminal performs communication.

[0024] The related information related to the communication terminal information may be, for example, instruction information used by the RIC 10 to instruct the wireless communication node 30 to transmit the communication terminal information. The instruction information may be a parameter for identifying the communication terminal information. The instruction information may be included in or set in a message that is transmitted from the RIC 10 to the wireless communication node 30 and requests the transmission of the communication terminal information.

[0025] The management node 40 communicates with the RIC 10 and the RIC 20. In other words, the management node 40 transmits or receives information or data between the RIC 10 and the RIC 20. The management node 40 managing the RIC 10 and the RIC 20 may mean that the management node 40 is in a state where communication between the RIC 10 and the RIC 20 is possible. The management node 40 may manage information received from the RIC 10 or the RIC 20. Managing information may be rephrased as holding, memorizing, recording, or storing information.

[0026] 2 shows an example configuration of a RIC 20 according to the present disclosure. The RIC 20 has a transmitting unit 21, a receiving unit 22, and a management unit 23. The transmitting unit 21, the receiving unit 22, and the management unit 23 may be software or modules that perform processing when a processor executes a program stored in a memory. The transmitting unit 21, the receiving unit 22, and the management unit 23 may be hardware such as a circuit or a chip. The transmitting unit 21 may be used as a transmitting unit that transmits information. The receiving unit 22 may be used as a receiving unit that receives information. The management unit 23 may be used as a management unit that manages information. The transmitting unit 21 and the receiving unit 22 may be referred to as a communication unit.

[0027] When a handover of a communication terminal is performed, the transmitter 21 transmits identification information of the communication terminal to the management node 40. After the transmitter 21 transmits the identification information of the communication terminal to the management node 40, the receiver 22 receives the communication terminal information or related information from the management node 40. Furthermore, the manager 23 manages the communication terminal information or related information received by the receiver 22. The manager 23 managing the communication terminal information or related information may mean that the manager 23 updates, adds, or deletes the communication terminal information or related information.

[0028] FIG. 3 shows an example configuration of a management node 40 according to the present disclosure. The management node 40 may be a computer device that operates by executing a program. The management node 40 includes a receiving unit 41, a determining unit 42, and a transmitting unit 43. The receiving unit 41, the determining unit 42, and the transmitting unit 43 may be software or modules that execute processing when a processor executes a program stored in a memory. Alternatively, the receiving unit 41, the determining unit 42, and the transmitting unit 43 may be hardware such as a circuit or a chip. The receiving unit 41 may be used as a receiving unit that receives information. The determining unit 42 may be used as a determining unit that executes a determining process. The transmitting unit 43 may be used as a means for transmitting information.

[0029] The receiving unit 41 receives communication terminal information unique to the communication terminal or associated information related to the communication terminal information, and first identification information of the communication terminal from the RIC 10. The receiving unit 41 may receive the communication terminal information unique to the communication terminal or associated information and the first identification information of the communication terminal at different times. Alternatively, the receiving unit 41 may receive the communication terminal information unique to the communication terminal or associated information and the first identification information of the communication terminal at substantially the same time.

[0030] The first identification information is identification information used by the RIC 10 to identify the communications terminal. In other words, the first identification information may be identification information recognized by the RIC 10 to identify the communications terminal. The RIC 10 may identify the communications terminal using the first identification information among multiple pieces of identification information for identifying the communications terminal.

[0031] The second identification information is identification information used by the RIC 20 to identify the communication terminal. In other words, the second identification information may be identification information recognized by the RIC 20 to identify the communication terminal. The RIC 20 may identify the communication terminal by using the second identification information from among multiple pieces of identification information for identifying the communication terminal.

[0032] The determination unit 42 determines whether the first identification information and the second identification information are information that identifies the same communication terminal. For example, if the first identification information and the second identification information are the same, the determination unit 42 may determine that the first identification information and the second identification information are information that identifies the same communication terminal. Alternatively, even if the first identification information and the second identification information are different, the determination unit 42 may determine that the first identification information and the second identification information are information that identifies the same communication terminal if the first identification information and the second identification information are associated with the same communication terminal. For example, the determination unit 42 may determine that the first identification information and the second identification information are associated with the same communication terminal if the first identification information and the second identification information are associated with common identification information.

[0033] If it is determined that the first identification information and the second identification information identify the same communication terminal, the transmitting unit 43 transmits the communication terminal information or related information to the RIC 20 .

[0034] Next, the flow of communication processing executed in the RIC 10 will be described. Fig. 4 is a diagram showing the flow of communication processing executed in the RIC 10 according to the present disclosure. First, the receiver 11 receives communication terminal information unique to the communication terminal from the wireless communication node (S11). Next, when a handover of the communication terminal is performed, the transmitter 12 transmits identification information of the communication terminal and communication terminal information or related information related to the communication terminal information to the management node 40 (S12).

[0035] Next, the flow of communication processing executed in the RIC 20 will be described. Fig. 5 is a diagram showing the flow of communication processing executed in the RIC 20 according to the present disclosure. First, when a handover of a communication terminal is performed, the transmitter 21 transmits identification information of the communication terminal to the management node 40 (S21). Next, the receiver 22 receives communication terminal information or related information from the management node 40 (S22). Next, the manager 23 manages the communication terminal information or related information received by the receiver 22 (S23).

[0036] Next, the flow of communication processing executed in the management node 40 will be described. FIG. 6 is a diagram showing the flow of communication processing executed in the management node 40 according to the present disclosure. First, the receiving unit 41 receives communication terminal information specific to a communication terminal or related information related to the communication terminal information from the RIC 10 (S31). Next, the receiving unit 41 receives first identification information of the communication terminal from the RIC 10 (S32). Next, the receiving unit 41 receives second identification information of the communication terminal from the RIC 20 (S33). Next, the determining unit 42 determines whether the first identification information and the second identification information identify the same communication terminal (S34). Next, if it is determined that the first identification information and the second identification information identify the same communication terminal, the transmitting unit 43 transmits the communication terminal information or related information to the RIC 20 (S35).

[0037] As described above, when a handover of a communication terminal is performed, the RIC 20 receives communication terminal information held by the RIC 10 or related information related to the communication terminal information via the management node 40. When the RIC 20 receives the related information, it can receive communication terminal identification information using the related information from the wireless communication node that manages the communication terminal after the handover. Alternatively, by receiving the communication terminal information from the management node 40, the RIC 20 can manage the communication terminal information held by the RIC 10 after the handover.

[0038] As a result, even after the communication terminal has been handed over, the RIC 20 can perform analysis processing related to the communication terminal, optimization processing of communication related to the communication terminal, etc., using communication terminal information similar to the communication terminal information held by the RIC 10. Optimization of communication makes it possible to save power consumption in communication, for example.

[0039] (Embodiment 2) Next, embodiment 2 will be described. Fig. 7 is a diagram showing an example of the configuration of a communication system. The communication system of Fig. 7 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.

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

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

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

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

[0044] The O-DU 70 may be a logical node that hosts Radio Link Control (RLC) and Medium 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.

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

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

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

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

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

[0050] 1 corresponds to the Near-RT RIC 110, and the management node 40 corresponds to the Non-RT RIC 100. However, the management node 40 may be realized in a device different from the Non-RT RIC 100.

[0051] FIG. 8 shows an example configuration of a Non-RT RIC and a Near-RT RIC. As shown in FIG. 8, the Non-RT RIC 100 is connected to a Near-RT RIC 110_1 and a Near-RT RIC 110_2. The Non-RT RIC 100 being connected to the Near-RT RIC 110_1 and the Near-RT RIC 110_2 may mean that the Non-RT RIC 100 is in a state where it can communicate with the Near-RT RIC 110_1 and the Near-RT RIC 110_2. The Near-RT RIC 110_1 is also connected to an E2 node 50_1 including an O-CU 60_1 and an O-DU 70_1. The O-DU 70_1 is further connected to an O-RU 80_1. The Near-RT RIC 110_2 is connected to an E2 node 50_2 including an O-CU 60_2 and an O-DU 70_2. Furthermore, the O-DU 70_2 is connected to the O-RU 80_2.

[0052] Also, although only one O-CU, one O-DU, and one O-RU are shown in Figure 8, multiple O-CUs, O-DUs, and O-RUs may exist. For example, an O-DU may be connected to multiple O-RUs. Furthermore, an O-CU may be connected to multiple O-DUs. Furthermore, a Near-RT RIC may be connected to multiple O-CUs.

[0053] Next, a RIC subscription procedure for acquiring communication terminal information will be described. FIG. 9 is a diagram showing the processing flow of the RIC subscription procedure. The RIC subscription may be used by the Near-RT RIC 110 to request the E2 node 50 to transmit information regarding a serving cell or a cell adjacent to the serving cell. Alternatively, the RIC subscription may be used by the Near-RT RIC 110 to request the E2 node 50 to transmit state variables, etc., when there is a change in PDCP, RLC, and MAC state variables or an RRC state related to the UE. The PDCP, RLC, and MAC state variables or an RRC state related to the UE may be referred to as UE information. Alternatively, the RIC subscription procedure may be used by the Near-RT RIC 110 to request the E2 node 50 to transmit changed configuration information when there is a change in configuration information related to the E2 node 50 or a cell. Alternatively, the RIC subscription procedure may be used by the Near-RT RIC 110 to request the E2 node 50 to transmit changed UE identification information (UE ID) when the UE identification information is changed. Also, the Near-RT RIC 110 may execute the RIC Subscription procedure with the O-CU 60 or the O-DU 70.

[0054] First, the Near-RT RIC 110_1 transmits a RIC SUBSCRIPTION REQUEST message to the E2 node 50_1 (S41). The RIC SUBSCRIPTION REQUEST message includes a RIC EVENT TRIGGER DEFINITION IE and a RIC ACTION DEFINITION IE as information elements. The RIC SUBSCRIPTION REQUEST message may also include a RIC Request ID IE for identifying the RIC subscription procedure.

[0055] The RIC EVENT TRIGGER DEFINITION IE may be used by the Near-RT RIC 110_1 to detect a change in UE information related to the UE 120. For example, L2 MAC State Variables, which are L2 information, may be set as the detection condition. The L2 MAC State Variables may indicate, for example, Buffer Occupancy, which indicates the amount of data used that is stored in the UE buffer. In addition, values ​​such as an RRC state, a PDCP state variable, and an RLC state variable may be used as the detection condition.

[0056] The RIC ACTION DEFINITION IE may be used to instruct the E2 node 50 to notify or report information about the UE 120 to the Near-RT RIC 110_1 when the detection condition indicated in the RIC EVENT TRIGGER DEFINITION IE is satisfied. For example, identification information (UE ID) of the UE to be detected may be set in the RIC ACTION DEFINITION IE. Satisfying the detection condition may mean that the communication state of the UE to be detected reaches a value set as the detection condition.

[0057] When the detection condition is satisfied, an operation defined as REPORT, INSERT, CONTROL, POLICY, or QUERY may be executed. These operations may be referred to as RIC Services. 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_1. 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_1 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 that satisfies 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.

[0058] Next, the E2 node 50_1 transmits a RIC SUBSCRIPTION RESPONSE message to the Near-RT RIC 110_1 (S42).

[0059] Next, when the E2 node 50_1 determines that the detection condition set in the RIC EVENT TRIGGER DEFINITION IE is satisfied, it transmits a RIC INDICATION message to the Near-RT RIC 110_1 (S43). The RIC INDICATION message includes the RIC Request ID IE included in the RIC SUBSCRIPTION REQUEST message. Furthermore, the RIC INDICATION message may be set with changed values ​​of the L2 MAC State Variables, PDCP state variable, RLC state variable, RRC state, etc. set in the RIC EVENT TRIGGER DEFINITION IE.

[0060] Next, the RIC subscription procedure for detecting a change in UE ID will be described. Fig. 10 is a diagram showing the processing flow related to the RIC subscription procedure.

[0061] First, the Near-RT RIC 110_1 transmits a RIC SUBSCRIPTION REQUEST message to the E2 node 50_1 (S51). The RIC SUBSCRIPTION REQUEST message includes a RIC EVENT TRIGGER DEFINITION IE and a RIC ACTION DEFINITION IE as information elements. The RIC SUBSCRIPTION REQUEST message may also include a RIC Request ID IE for identifying the RIC SUBSCRIPTION procedure. The E2 node 50_1 may be an E2 node that manages the O-RU 80_1 to which the UE 120 is connected.

[0062] The RIC EVENT TRIGGER DEFINITION IE may be used by the Near-RT RIC 110_1 to detect a change in the identification information (UE identifier: UE ID) of the UE 120 managed by the E2 node 50_1. The change in the UE ID may be a change in a new UE ID being assigned to the UE 120 when the UE 120 is connected to the O-RU 80_1. Alternatively, the change in the UE ID may be a change in the setting or allocation content of the already assigned UE ID. Alternatively, the change in the UE ID may be a change in the UE ID identifying the UE 120 when the connection between the UE 120 and the O-RU 80_1 is terminated.

[0063] The RIC ACTION DEFINITION IE may be used to instruct the E2 node 50_1 to notify or report information about the UE 120 to the Near-RT RIC 110_1 when the detection condition indicated in the RIC EVENT TRIGGER DEFINITION IE is satisfied. For example, identification information (UE ID) of the UE 120 to be detected may be set in the RIC ACTION DEFINITION IE. Satisfying the detection condition may mean that the UE ID of the UE to be detected has changed.

[0064] Here, a specific example of the UE ID will be described. Figures 11 to 13 show a specific example of the UE ID. Figures 11 to 13 show a specific example of the UE ID disclosed in O-RAN.WG3.E2SM-R003-v04.00.

[0065] 10, in step S51, the RIC EVENT TRIGGER DEFINITION IE is used to detect that the UE ID identifying the UE 120 has been deleted. That is, when the UE ID identifying the UE 120 has been deleted, the Near-RT RIC 110_1 sets, in the RIC EVENT TRIGGER DEFINITION IE, a parameter or the like that instructs the E2 node 50_1 to notify that the UE ID identifying the UE 120 has been deleted.

[0066] Next, the UE 120 performs a handover from the cell formed by the O-RU 80_1 managed by the E2 node 50_1 to the cell formed by the O-RU 80_2 managed by the E2 node 50_2 (S52). The handover is performed according to an existing procedure defined in a mobile network. The existing procedure may be, for example, a procedure specified in 3GPP. Step S52 shows that handover processing is performed in the E2 node 50_1 and the E2 node 50_2 when the UE 120 performs a handover from the cell formed by the O-RU 80_1 to the cell formed by the O-RU 80_2.

[0067] As the UE 120 moves to the O-RU 80_2 managed by the E2 node 50_2, the E2 node 50_1 stops managing the UE ID of the UE 120. That is, as the UE 120 moves to the O-RU 80_2 managed by the E2 node 50_2, the E2 node 50_1 deletes the UE ID of the UE 120. Deleting the UE ID of the UE 120 may mean deleting the UE ID of the UE 120 from a storage area such as a memory in the E2 node 50_1.

[0068] Next, when the E2 node 50_1 deletes the UE ID of the UE 120, it transmits a RIC INDICATION message to the Near-RT RIC 110_1 in accordance with the RIC EVENT TRIGGER DEFINITION IE and the RIC ACTION DEFINITION IE (S53). The RIC INDICATION message may include a parameter indicating that the UE ID of the UE 120 has been deleted. The RIC INDICATION message may also include the deleted UE ID. For example, the RIC INDICATION message may include the UE ID of the UE 120 shown in FIGS. 11 to 13.

[0069] Next, the Near-RT RIC 110_1 transmits a UE ID notification message to the Non-RT RIC 100, which is the management node (S54). The UE ID notification message may include UE information about the UE 120, such as L2 MAC State Variables, PDCP state variables, RLC state variables, and RRC state, received by the Near-RT RIC 110_1 in step S43 of FIG. 9. Furthermore, the UE ID notification message includes the UE ID of the UE 120.

[0070] Here, the UE ID included in the UE ID notification is a UE ID that does not change before and after handover of the UE 120. For example, among the UE IDs shown in Figures 11 to 13, the Cell RNTI (Cell Radio Network Temporary Identifier) ​​is a UE ID that is unique to a cell. Therefore, the Cell RNTI is a UE ID that changes before and after handover of the UE 120. On the other hand, for example, the AMF (Access and Mobility Management Function) UE NGAP ID is a UE ID that is unique to the AMF, which is a core network node. Therefore, even if the UE 120 performs a handover that involves a change in the Near-RT RIC, the AMF UE NGAP ID does not change before and after handover of the UE 120. Therefore, the UE ID included in the UE ID notification may be, for example, the AMF UE NGAP ID. The UE ID included in the UE ID notification is not limited to the AMF UE NGAP ID, and may be another ID that does not change before and after handover of the UE 120.

[0071] 11 to 13 relating to the UE 120. In this case, the Non-RT RIC 100 may extract the AMF UE NGAP ID or the like that is not changed before and after the handover.

[0072] Next, a description will be given of a RIC subscription procedure for detecting a change in UE ID. Fig. 14 is a diagram showing a processing flow related to the RIC subscription procedure executed in the Near-RT RIC 110_2 that manages the UE after handover.

[0073] First, the Near-RT RIC 110_2 transmits a RIC SUBSCRIPTION REQUEST message to the E2 node 50_2 (S61). The RIC SUBSCRIPTION REQUEST message includes a RIC EVENT TRIGGER DEFINITION IE and a RIC ACTION DEFINITION IE as information elements. The RIC SUBSCRIPTION REQUEST message may also include a RIC Request ID IE for identifying the RIC SUBSCRIPTION procedure. The E2 node 50_2 is an E2 node managed by the Near-RT RIC 110_2.

[0074] The RIC EVENT TRIGGER DEFINITION IE may be used by the Near-RT RIC 110_1 to detect a change in the identification information (UE identifier: UE ID) of the UE 120 managed by the E2 node 50_1. In step S61, the RIC EVENT TRIGGER DEFINITION IE may be used to detect that a new UE has been connected to the O-RU 80_2 managed by the E2 node 50_2. Alternatively, the RIC EVENT TRIGGER DEFINITION IE may be used to detect that a new UE has been connected to the O-RU 80_2 by handover. In either case, a new UE ID is assigned to the UE.

[0075] The RIC ACTION DEFINITION IE may be used to instruct the E2 node 50_2 to notify or report information about a new UE to the Near-RT RIC 110_1 when the detection condition indicated in the RIC EVENT TRIGGER DEFINITION IE is met.

[0076] Next, the UE 120 performs a handover from the cell formed by the O-RU 80_1 managed by the E2 node 50_1 to the cell formed by the O-RU 80_2 managed by the E2 node 50_2 (S62). The handover in step S62 is similar to the handover in step S52 in FIG. 10.

[0077] Next, when the UE 120 newly connects to the O-RU 80_2, the E2 node 50_2 transmits a RIC INDICATION message to the Near-RT RIC 110_2 in accordance with the RIC EVENT TRIGGER DEFINITION IE and the RIC ACTION DEFINITION IE (S63). The case where the UE 120 newly connects to the O-RU 80_2 may be rephrased as the case where a new UE ID is assigned to the UE 120.

[0078] Since the UE 120 is performing handover, the serving cell is changed. Therefore, the new UE ID assigned to the UE 120 may be, for example, the Cell RNTI shown in Figures 11 to 13. On the other hand, if the handover performed by the UE 120 does not involve a change in AMF, the AMF UE NGAP ID as the UE ID of the UE 120 is not changed before and after the handover.

[0079] The RIC INDICATION message may include the UE ID of the UE 120, as shown in FIGS.

[0080] Next, the Near-RT RIC 110_2 transmits a UE ID notification message to the Non-RT RIC 100, which is the management node (S64). The UE ID notification message includes the UE ID of the UE 120. The UE ID included in the UE ID notification is a UE ID that does not change before and after handover of the UE 120. For example, the UE ID included in the UE ID notification is the AMF UE NGAP ID of the UE 120. The UE ID included in the UE ID notification is not limited to the AMF UE NGAP ID, and may be another ID that does not change before and after handover of the UE 120.

[0081] 11 to 13 relating to the UE 120. In this case, the Non-RT RIC 100 may extract the AMF UE NGAP ID or the like that is not changed before and after the handover.

[0082] Next, a description will be given of a procedure for transmitting UE information acquired in the RIC subscription procedure via the Non-RT RIC 100. FIG.

[0083] 15, it is assumed that step S54 in Fig. 10 and step S64 in Fig. 14 have been performed. That is, it is assumed that the Non-RT RIC 100 has received UE ID notifications from the Near-RT RIC 110_1 and the Near-RT RIC 110_2.

[0084] Next, the Non-RT RIC 100 determines whether the UE ID included in the UE ID notification received from the Near-RT RIC 110_1 matches the UE ID included in the UE ID notification received from the Near-RT RIC 110_2 (S71). For example, the Non-RT RIC 100 determines whether the AMF UE NGAP IDs included in each UE ID notification match. Here, a match in the AMF UE NGAP ID indicates that the UE 120 whose UE ID has been deleted in the E2 node 50_1 matches the UE 120 newly added in the E2 node 50_2.

[0085] If the Non-RT RIC 100 determines that the UE IDs match, it may send a UE ID notification response message to the Near-RT RIC 110_1 that includes information indicating that the UE 120 is located under the control of the E2 node 50_2 (S72).

[0086] Furthermore, in step S54, the Non-RT RIC 100 transmits a UE ID notification response including the UE information received from the Near-RT RIC 110_1 to the Near-RT RIC 110_2 (S73).

[0087] Here, if the Non-RT RIC 100 determines that the UE IDs match, the transmission of the UE ID notification message to the Near-RT RIC 110_1 in step S72 may be omitted.

[0088] Furthermore, if the Non-RT RIC 100 determines that the UE IDs do not match, the transmission of the UE ID notification message in steps S72 and S73 may be omitted.

[0089] As described above, the Near-RT RIC 110_2, which manages the UE 120 after handover, can obtain the UE information of the UE 120 that the Near-RT RIC 110_1 obtained in the RIC subscription procedure via the Non-RT RIC 100.

[0090] This allows the Near-RT RIC 110_2 to perform analysis processing, optimization processing, etc. using the UE information of the UE 120 immediately after handover of the UE 120.

[0091] (Embodiment 3) Next, a description will be given of the flow of communication processing according to embodiment 3. Specifically, it has been described that in step S53 of Fig. 10, the Near-RT RIC 110_1 transmits a UE ID notification message including UE information to the Non-RT RIC 100. Furthermore, it has been described that in step S73 of Fig. 15, the Non-RT RIC 100 transmits a UE ID notification response message including UE information to the Near-RT RIC 110_2.

[0092] Here, in the third embodiment, in the communication processing of Fig. 10, the Near-RT RIC 110_1 may include, in the UE ID notification message (S54), the parameters set in the IEs included in the RIC SUBSCRIPTION REQUEST message in step S51. The IEs included in the RIC SUBSCRIPTION REQUEST message may be, for example, a RIC EVENT TRIGGER DEFINITION IE and a RIC ACTION DEFINITION IE.

[0093] Furthermore, in step S73 of FIG. 15, the Non-RT RIC 100 may transmit a UE ID notification response message including the parameters included in the UE ID notification message of step S54 to the Near-RT RIC 110_2.

[0094] By performing such processing, the Near-RT RIC 110_2 can execute the RIC Subscription procedure using the same detection conditions as when the Near-RT RIC 110_1 acquired UE information regarding the UE 120. Therefore, by executing the RIC Subscription procedure after a handover of the UE 120 is executed, the Near-RT RIC 110_2 can acquire UE information similar to the UE information of the UE 120 acquired by the Near-RT RIC 110_1. Therefore, the Near-RT RIC 110_2 can execute analysis processing, optimization processing, etc. similar to those of the Near-RT RIC 110_1 after a handover of the UE 120.

[0095] FIG. 16 is a block diagram showing an example configuration of the RIC 10, the RIC 20, the wireless communication node 30, the Near-RT RIC 110, and the Non-RT RIC 100 (hereinafter referred to as RIC 10, etc.). Referring to FIG. 16, 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) that complies with the IEEE 802.3 series. Here, IEEE stands for Institute of Electrical and Electronics Engineers.

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

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

[0098] 16, 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 embodiments.

[0099] As explained using FIG. 16, 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.

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

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

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

[0103] Some or all of the above embodiments can be described as in the following supplementary notes, but are not limited to them. (Supplementary Note 1) A first RIC comprising: a receiving unit that receives communication terminal information unique to a communication terminal from a wireless communication node; and a transmitting unit that, when a handover of the communication terminal is performed, transmits identification information of the communication terminal and the communication terminal information or related information related to the communication terminal information to a management node that manages the first RIC and a second RIC. (Supplementary Note 2) The first RIC according to Supplementary Note 1, wherein the identification information is information used in common before and after the handover. (Supplementary Note 3) The first RIC according to Supplementary Note 2, wherein the identification information is information assigned by a core network node. (Supplementary Note 4) The first RIC according to any one of Supplements 1 to 3, wherein the related information is instruction information used to instruct the wireless communication node to transmit the communication terminal information. (Supplementary Note 5) The first RIC according to Supplementary Note 4, wherein the transmission unit transmits a RIC SUBSCRIPTION REQUEST including the instruction information to the wireless communication node in order to acquire the communication terminal information from the wireless communication node. (Supplementary Note 6) The first RIC according to Supplementary Note 5, wherein the instruction information is parameters set in a RIC EVENT TRIGGER DEFINITION IE and a RIC ACTION DEFENITION IE included in the RIC SUBSCRIPTION REQUEST. (Supplementary Note 7) The first RIC according to any one of Supplements 1 to 6, wherein the communication terminal information is information collected by the wireless communication node from the communication terminal or information generated by the wireless communication node. (Supplementary Note 8) A second RIC comprising: a transmitting unit that transmits identification information of the communication terminal to a management node that manages the first RIC and the second RIC when a handover of the communication terminal is performed; a receiving unit that receives from the management node communication terminal information specific to the communication terminal or related information related to the communication terminal information that the first RIC has received from a wireless communication node; and a management unit that manages the communication terminal information or the related information.(Supplementary Note 9) The second RIC according to Supplementary Note 8, wherein the identification information is information used in common before and after the handover. (Supplementary Note 10) The second RIC according to Supplementary Note 9, wherein the identification information is information assigned by a core network node. (Supplementary Note 11) The second RIC according to any one of Supplements 8 to 10, wherein the related information is instruction information used in the first RIC to instruct the wireless communication node to transmit the communication terminal information. (Supplementary Note 12) The second RIC according to Supplementary Note 11, wherein the instruction information is parameters set in a RIC EVENT TRIGGER DEFINITION IE and a RIC ACTION DEFENITION IE included in a RIC SUBSCRIPTION REQUEST. (Supplementary Note 13) A management node comprising: a receiving unit that receives, from a first RIC, communication terminal information unique to a communication terminal or associated information related to the communication terminal information, and first identification information of the communication terminal, and receives, from a second RIC, second identification information of the communication terminal, a determining unit that determines whether the first identification information and the second identification information are information that identify the communication terminal, and a transmitting unit that transmits the communication terminal information or the associated information to the second RIC when it is determined that the first identification information and the second identification information are information that identify the communication terminal. (Supplementary Note 14) A communication method that receives communication terminal information unique to a communication terminal from a wireless communication node, and when a handover of the communication terminal is performed, transmits the identification information of the communication terminal and the communication terminal information or associated information related to the communication terminal information to a management node that manages the first RIC and the second RIC. (Supplementary Note 15) A communication method, when a handover of a communication terminal is performed, transmitting identification information of the communication terminal to a management node that manages a first RIC and a second RIC, receiving from the management node communication terminal information specific to the communication terminal or related information related to the communication terminal information that the first RIC received from a wireless communication node, and managing the communication terminal information or the related information.(Supplementary Note 16) A communication method comprising: receiving, from a first RIC, communication terminal information unique to a communication terminal or associated information related to the communication terminal information, and first identification information of the communication terminal; receiving, from a second RIC, second identification information of the communication terminal; determining whether the first identification information and the second identification information are information identifying the communication terminal; and transmitting the communication terminal information or the associated information to the second RIC if it is determined that the first identification information and the second identification information are information identifying the communication terminal. (Supplementary Note 17) A program causing a computer to execute the following: receiving communication terminal information unique to a communication terminal from a wireless communication node; and, when handover of the communication terminal is performed, transmitting the identification information of the communication terminal and the communication terminal information or associated information related to the communication terminal information to a management node that manages the first RIC and the second RIC. (Supplementary Note 18) A program that causes a computer to execute the following when a handover of a communications terminal is performed: transmitting identification information of the communications terminal to a management node that manages a first RIC and a second RIC; receiving from the management node communications terminal information unique to the communications terminal or associated information related to the communications terminal information that the first RIC received from a wireless communication node; and managing the communications terminal information or the associated information. (Supplementary Note 19) A program that causes a computer to execute the following: receiving from a first RIC communications terminal information unique to the communications terminal or associated information related to the communications terminal information, and first identification information of the communications terminal; receiving from a second RIC second identification information of the communications terminal; determining whether the first identification information and the second identification information are information that identifies the communications terminal; and transmitting the communications terminal information or the associated information to the second RIC when it is determined that the first identification information and the second identification information are information that identifies the communications terminal.

[0104] 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 14 and 17 in the same dependency relationship as Supplementary Notes 2 to 7. Some or all of the elements (e.g., configurations and functions) described in Supplementary Notes 9 to 12 that are dependent on Supplementary Notes 8 may also be dependent on Supplementary Notes 15 and 18 in the same dependency relationship as Supplementary Notes 9 to 12. 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.

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

[0106] 10 RIC 11 Receiving unit 12 Transmitting unit 20 RIC 21 Transmitting unit 22 Receiving unit 23 Management unit 30 Wireless communication node 40 Management node 41 Receiving unit 42 Determination unit 43 Transmitting unit 50 E2 node 50_1 E2 node 50_2 E2 node 60 O-CU 60_1 O-CU 60_2 O-CU 70 O-DU 70_1 O-DU 70_2 O-DU 80 O-RU 80_1 O-RU 80_2 O-RU 90 SMO 100 Non-RT RIC 101 Receiving unit 102 Determination unit 103 Transmitting unit 110 Near-RT RIC 110_1 Near-RT RIC 110_2 Near-RT RIC 120 UE

Claims

1. A first RIC comprising: a receiving means for receiving communication terminal information specific to the communication terminal from a wireless communication node; and a transmitting means for transmitting, when a handover of the communication terminal is performed, identification information of the communication terminal and the communication terminal information or related information related to the communication terminal information to a management node that manages the first RIC and a second RIC.

2. The first RIC according to claim 1, wherein the identification information is information that is used in common before and after the handover.

3. The first RIC according to claim 2, wherein the identification information is information assigned by a core network node.

4. The first RIC according to any one of claims 1 to 3, wherein the related information is instruction information used to instruct the wireless communication node to transmit the communication terminal information.

5. The first RIC according to claim 4, wherein the transmitting means transmits a RIC SUBSCRIPTION REQUEST including the instruction information to the wireless communication node in order to acquire the communication terminal information from the wireless communication node.

6. The first RIC according to claim 5, wherein the instruction information is a parameter set in a RIC EVENT TRIGGER DEFINITION IE and a RIC ACTION DEFENITION IE included in the RIC SUBSCRIPTION REQUEST.

7. A first RIC according to any one of claims 1 to 3, wherein the communication terminal information is information collected by the wireless communication node from the communication terminal or information generated by the wireless communication node.

8. A second RIC comprising: a transmitting means for transmitting identification information of the communication terminal to a management node that manages the first RIC and the second RIC when a handover of the communication terminal is performed; a receiving means for receiving from the management node communication terminal information specific to the communication terminal or related information related to the communication terminal information that the first RIC has received from a wireless communication node; and a management means for managing the communication terminal information or the related information.

9. The second RIC according to claim 8, wherein the identification information is information that is used in common before and after the handover.

10. The second RIC according to claim 9, wherein the identification information is information assigned by a core network node.

11. A second RIC according to any one of claims 8 to 10, wherein the related information is instruction information used in the first RIC to instruct the wireless communication node to transmit the communication terminal information.

12. The second RIC according to claim 11, wherein the instruction information is a parameter set in a RIC EVENT TRIGGER DEFINITION IE and a RIC ACTION DEFENITION IE included in a RIC SUBSCRIPTION REQUEST.

13. A management node comprising: a receiving means for receiving, from a first RIC, communication terminal information specific to a communication terminal or related information related to the communication terminal information, and first identification information of the communication terminal, and receiving, from a second RIC, second identification information of the communication terminal; a determining means for determining whether the first identification information and the second identification information are information that identifies the communication terminal; and a transmitting means for transmitting the communication terminal information or the related information to the second RIC when it is determined that the first identification information and the second identification information are information that identifies the communication terminal.

14. A communication method comprising receiving communication terminal information specific to a communication terminal from a wireless communication node, and when a handover of the communication terminal is performed, transmitting identification information of the communication terminal and the communication terminal information or related information related to the communication terminal information to a management node that manages a first RIC and a second RIC.

15. A communication method in which, when a handover of a communication terminal is performed, identification information of the communication terminal is sent to a management node that manages a first RIC and a second RIC, communication terminal information specific to the communication terminal or related information related to the communication terminal information received by the first RIC from a wireless communication node is received from the management node, and the communication terminal information or the related information is managed.

16. A communication method comprising: receiving, from a first RIC, communication terminal information specific to a communication terminal or related information related to the communication terminal information, and first identification information of the communication terminal; receiving, from a second RIC, second identification information of the communication terminal; determining whether the first identification information and the second identification information are information identifying the communication terminal; and, if it is determined that the first identification information and the second identification information are information identifying the communication terminal, transmitting the communication terminal information or the related information to the second RIC.

17. A program that causes a computer to receive communication terminal information specific to a communication terminal from a wireless communication node, and when a handover of the communication terminal is performed, transmit the identification information of the communication terminal and the communication terminal information or related information related to the communication terminal information to a management node that manages a first RIC and a second RIC.

18. A program that causes a computer to execute the following steps when a handover of a communication terminal is performed: sending identification information of the communication terminal to a management node that manages a first RIC and a second RIC; receiving from the management node communication terminal information specific to the communication terminal or related information related to the communication terminal information that the first RIC received from a wireless communication node; and managing the communication terminal information or the related information.

19. A program that causes a computer to receive, from a first RIC, communication terminal information specific to a communication terminal or related information related to the communication terminal information, and first identification information of the communication terminal; receive, from a second RIC, second identification information of the communication terminal; determine whether the first identification information and the second identification information are information that identifies the communication terminal; and, if it is determined that the first identification information and the second identification information are information that identifies the communication terminal, send the communication terminal information or the related information to the second RIC.

Images