Management of interoperability test profiles in O-RAN M-Plane

Abstract

A radio access network control device 1 comprises at least one processor configured to: set the version of Internet Protocol, which is requested for O-RUs, to IPv6 by an IP version setting unit 11; detect that the version of Internet Protocol supported by the O-RUs includes IPv6 by an IP version detection unit 12 capable of communicating with the O-RUs; and manage a test profile of an IOT device in an O-RAN M-Plane capable of handling IPv6 and / or TLS by a test profile management unit 13 (FIG. 3).

Description

[Technical field]

[0001] The present disclosure relates to management of interoperability test profiles in the M-Plane of O-RAN. [Background technology]

[0002] With the aim of opening up radio access networks (RANs) in mobile communication systems, studies on "Open RAN," "O-RAN," "vRAN," and the like are underway. In this specification, "O-RAN" is used as a term that collectively represents such various "open radio access networks." Therefore, "O-RAN" in this specification should not be interpreted as being limited to the standards and specifications of the same name formulated by the O-RAN Alliance.

[0003] The radio unit (RU) in O-RAN is called O-RU, and provides communication cells to the communication device (UE: User Equipment). The O-RU is controlled by a RAN node consisting of an O-CU, which is a central unit (CU), and / or an O-DU, which is a distributed unit (DU). The RAN node is further controlled by a higher-level controller, such as a Near-RT RIC (Near-Real Time RAN Intelligent Controller) and / or a Non-RT RIC (Non-Real Time RAN Intelligent Controller). O-RAN also provides a virtualization platform called O-Cloud that virtually manages a collection of multiple RAN nodes. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-83058 Summary of the Invention [Problem to be solved by the invention]

[0005] In conventional O-RAN, all O-RUs were required to support the Internet Protocol version IPv4. However, depending on the telecommunications carrier (hereinafter also referred to as operator or carrier) that operates O-RAN, IPv4 may not be used, so there was a risk that the IPv4 functions implemented in the O-RU would go to waste. In addition, the test profile for interoperability test (IoT: Interoperability Test) devices in the conventional O-RAN M-Plane only supported IPv4 and did not support TLS (Transport Layer Security) etc.

[0006] The present disclosure has been made in consideration of these circumstances, and aims to provide a radio access network control device and the like that can relax the constraints related to interoperability test profiles in the M-Plane of O-RAN. [Means for solving the problem]

[0007] In order to solve the above problems, a radio access network control device of a certain embodiment of the present disclosure includes at least one processor that executes, by a test profile management unit, management of test profiles for M-Plane interoperability tests in devices compliant with O-RAN that are IPv6-compatible.

[0008] In this aspect, since the test profile for M-Plane interoperability testing in O-RAN compliant devices is compatible with IPv6, the conventional constraints on the test profile can be relaxed.

[0009] Another aspect of the present disclosure is also a radio access network control device, comprising at least one processor that executes, by a test profile management unit, managing a test profile for an M-Plane interoperability test in a TLS-enabled O-RAN-compliant device.

[0010] In this aspect, since the test profile for M-Plane interoperability testing in O-RAN compliant devices is compatible with TLS, the conventional constraints on the test profile can be relaxed.

[0011] Yet another aspect of the present disclosure is a radio access network control method, comprising managing a test profile for M-Plane interoperability testing in an IPv6-enabled O-RAN compliant device.

[0012] Yet another aspect of the present disclosure is also a radio access network control method, comprising: managing a test profile for an M-Plane interoperability test in a TLS-enabled O-RAN compliant device.

[0013] Yet another aspect of the present disclosure is a storage medium that stores a radio access network control program that causes a computer to manage a test profile for an M-Plane interoperability test in an IPv6-enabled O-RAN compliant device.

[0014] Yet another aspect of the present disclosure is also a storage medium. The storage medium stores a radio access network control program that causes a computer to manage a test profile of an M-Plane interoperability test in a TLS-enabled O-RAN-compliant device.

[0015] Any combination of the above components, or any conversion of these components into a method, device, system, recording medium, computer program, or the like, is also encompassed by the present disclosure. Effect of the Invention

[0016] According to the present disclosure, it is possible to relax the constraints on the test profile of the interoperability test in the M-Plane of O-RAN. [Brief description of the drawings]

[0017] [Figure 1] 1 shows a schematic overview of a radio access network control device. [Diagram 2] Schematic diagram of various functions realized by SMO and / or Non-RT RIC and O-Cloud. [Diagram 3] FIG. 2 is a functional block diagram illustrating a radio access network control device. [Figure 4] This section provides a specific example of an interoperability test profile for the M-Plane of O-RAN that supports IPv6 and TLS. [Diagram 5] This section provides a specific example of an interoperability test profile for the M-Plane of O-RAN that supports IPv6 and TLS. [Figure 6] This section provides a specific example of an interoperability test profile for the M-Plane of O-RAN that supports IPv6 and TLS. [Figure 7] This section provides a specific example of an interoperability test profile for the M-Plane of O-RAN that supports IPv6 and TLS. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] In the following, this embodiment will be described in accordance with "O-RAN," which is a standard and specification formulated by the O-RAN Alliance. Therefore, in this embodiment, well-known terms defined in "O-RAN" are used for convenience, but the technology disclosed herein can also be applied to other existing radio access networks such as "Open RAN" and "vRAN," and similar radio access networks that may be developed in the future.

[0019] FIG. 1 is a schematic diagram showing an outline of a radio access network control device according to the present embodiment. This radio access network control device is a RAN control device that controls a radio access network conforming to O-RAN. SMO (Service Management and Orchestration) controls the entire RAN control device or the entire O-RAN to coordinate the operations of each unit. SMO includes Non-RT RIC (Non-Real Time RAN Intelligent Controller) that functions as an overall control processor that is responsible for overall control. Non-RT RIC, which has a relatively long control period (for example, 1 second or more), issues guidelines, policies, guidance, etc. regarding the operation of each RAN node (O-CU and / or O-DU, which will be described later). Specifically, Non-RT RIC executes application software called rApp to issue operation guidelines for each RAN node to Near-RT RIC (Near-Real Time RAN Intelligent Controller) through the A1 interface. The Near-RT RIC, which has a relatively short control period (e.g., less than one second), runs application software called xApp to control each RAN node (O-CU / O-DU) itself and general-purpose hardware in the radio unit (O-RU) connected to each RAN node through the E2 interface.

[0020] The illustrated RAN node includes an O-CU, which is a central unit (CU) conforming to O-RAN, and / or an O-DU, which is a distributed unit (DU) conforming to O-RAN. Both the O-CU and the O-DU are responsible for baseband processing in O-RAN, but the O-CU is provided on the core network side (not shown), and the O-DU is provided on the O-RU side, which is a radio unit (RU) conforming to O-RAN. The O-CU may be divided into an O-CU-CP constituting a control plane (CP) and an O-CU-UP constituting a user plane (UP). The O-CU and the O-DU may be integrally configured as one baseband processing unit. In addition, an O-eNB may be provided as a RAN node as a base station conforming to O-RAN and the fourth generation mobile communication system (4G). One or more O-RUs are connected to each RAN node (O-CU / O-DU), and are controlled by a Near-RT RIC via the RAN node. A communication device (UE: User Equipment) in a communication cell provided by each O-RU can be connected to each O-RU and can perform mobile communication with a core network (not shown) via each RAN node (O-CU / O-DU).

[0021] Each RAN node (O-CU / O-DU) and Near-RT RIC provide operation data of each RAN node, each O-RU, and each UE to the SMO for so-called FCAPS (Fault, Configuration, Accounting, Performance, Security) through the O1 interface. Based on the operation data acquired through the O1 interface, the SMO updates the operation guidelines of each RAN node issued by the Non-RT RIC to the Near-RT RIC through the A1 interface as necessary. Note that the O-RU may be connected to the SMO for FCAPS through the O1 interface or other interfaces (such as Open Fronthaul M-Plane).

[0022] The O-Cloud, which serves as a virtualization platform that virtually manages a set of multiple RAN nodes (O-CU / O-DU), is connected to the SMO via the O2 interface. Based on the operating status of multiple RAN nodes (O-CU / O-DU) obtained from the O-Cloud via the O2 interface, the SMO generates resource allocation guidelines for resource allocation of the multiple RAN nodes and load management guidelines for workload management, and issues them to the O-Cloud via the O2 interface.

[0023] Figure 2 shows a schematic diagram of various functions realized by SMO and / or Non-RT RIC and O-Cloud. SMO mainly realizes three functions: FOCOM (Federated O-Cloud Orchestration and Management), NFO (Network Function Orchestrator), and OAM Function. O-Cloud mainly realizes two functions: IMS (Infrastructure Management Services) and DMS (Deployment Management Services).

[0024] FOCOM manages resources in the O-Cloud while receiving services from the IMS of the O-Cloud through the O2 interface (O2ims). NFO realizes the cooperative operation of a set of network functions (NFs) by multiple NF deployments in the O-Cloud while receiving services from the DMS of the O-Cloud through the O2 interface (O2dms). NFO may use an OAM function to access deployed NFs through the O1 interface. The OAM function is responsible for FCAPS management of O-RAN managed entities such as RAN nodes. The OAM function in this embodiment can be a function block that is provided with a callback to receive data on failures and operating statuses of multiple RAN nodes virtually managed by the O-Cloud by monitoring the procedures or procedures of O2ims and / or O2dms. IMS is responsible for managing resources (hardware) of the O-Cloud and software used to manage them, and provides services mainly to FOCOM of the SMO. The DMS is responsible for managing multiple NF Deployments in the O-Cloud, specifically starting, monitoring, and terminating them, and provides services mainly to the SMO's NFO.

[0025] FIG. 3 is a functional block diagram showing a radio access network control device 1 according to the present embodiment. The radio access network control device 1 includes an IP version setting unit 11, an IP version detection unit 12, and a test profile management unit 13. These functional blocks are realized by the cooperation of hardware resources such as a processor such as a central processing unit of a computer, a memory, an input device, an output device, and peripheral devices connected to the computer, and software executed using them. Regardless of the type of computer or the installation location, each of the above functional blocks may be realized by the hardware resources of a single computer, or may be realized by combining hardware resources distributed among multiple computers. In particular, in this embodiment, some or all of the functional blocks of the radio access network control device 1 may be realized in a distributed or centralized manner by a computer or processor provided in any part of the O-RAN, such as a RAN node constituted by an SMO, a Non-RT RIC, a Near-RT RIC, an O-CU and / or an O-DU, an O-Cloud, or the like, or may be realized in a distributed or centralized manner by a computer or processor provided outside the O-RAN that can communicate with the O-RAN. Note that IP version setting unit 11 and IP version detection unit 12, which mainly control the O-RU, are provided outside the O-RU, but some or all of the functions of test profile management unit 13 may be provided in the O-RU. Also, at least one of IP version setting unit 11 and IP version detection unit 12 may be provided.

[0026] The IP version setting unit 11 and / or the IP version detection unit 12 in the radio access network control device 1 that controls the O-RAN including the O-RU as a radio unit can communicate at least unidirectionally with one or more O-RUs that are the main control targets via at least one interface. For example, as also shown in FIG. 1, the O-RU can communicate bidirectionally or unidirectionally with RAN nodes (O-CU and / or O-DU), Near-RT RIC, SMO (including Non-RT RIC), etc. that may constitute the radio access network control device 1 via the O1 interface, the M-Plane of the open fronthaul, etc. Also, the O-RU can communicate bidirectionally or unidirectionally with RAN nodes (O-CU and / or O-DU), etc. that may constitute the radio access network control device 1 via the CUS-Plane of the open fronthaul, etc.

[0027] The IP version setting unit 11 capable of communicating with the O-RU can set the version of the Internet Protocol required for each O-RU to IPv6. Also, the IP version setting unit 11 can set the version of the Internet Protocol required for each O-RU to IPv4. Furthermore, the IP version setting unit 11 can set the version of the Internet Protocol required for each O-RU to both IPv4 and IPv6. That is, the IP version setting unit 11 can set the version of the Internet Protocol required for each O-RU to at least three types, namely, "IPv4", "IPv6", and "both IPv4 and IPv6". Here, the expressions "IPv4", "IPv6", and "both IPv4 and IPv6" focus only on IPv4 and IPv6. Therefore, these may include versions of the Internet Protocol other than IPv4 and IPv6.

[0028] The IP version detection unit 12 capable of communicating with the O-RU can detect that the version of the Internet Protocol supported by each O-RU includes IPv6. The IP version detection unit 12 can also detect that the version of the Internet Protocol supported by each O-RU includes IPv4. Furthermore, the IP version detection unit 12 can detect that the version of the Internet Protocol supported by each O-RU includes both IPv4 and IPv6. That is, the IP version detection unit 12 can detect which of at least three types of Internet Protocol versions supported by each O-RU corresponds to, namely, "IPv4", "IPv6", and "both IPv4 and IPv6". Here, the expressions "IPv4", "IPv6", and "both IPv4 and IPv6" focus only on IPv4 and IPv6. Therefore, these may include versions of Internet Protocols other than IPv4 and IPv6.

[0029] For example, the IP version detection unit 12 can directly or indirectly obtain information suggesting the version of the Internet Protocol supported by each O-RU from each O-RU using NETCONF (Network Configuration Protocol) or a network configuration protocol implemented via the O1 interface, etc. In NETCONF implemented via the O1 interface, the SMO functions as a NETCONF client, and the O-RU (and / or Near-RT RIC, O-CU, O-DU) functions as a NETCONF server. The SMO, etc. as a NETCONF client may generate a list of interfaces supported by each O-RU as a NETCONF server through RPCs (Remote Procedure Calls) constituting NETCONF, or may infer that the corresponding version of the Internet Protocol is supported based on the presence of an IPv4 container or an IPv6 container in the O-RAN interface module.

[0030] In conventional O-RAN, all O-RUs were required to support the Internet protocol version of IPv4. However, depending on the telecommunications carrier operating the O-RAN, IPv4 may not be used, so there was a risk that the IPv4 function implemented in the O-RU would be wasted. According to this embodiment, the Internet protocol version of the O-RU can be set to IPv6, so that the conventional constraints on the Internet protocol version of the O-RU can be relaxed. In addition, according to this embodiment, it is possible to detect that the Internet protocol version supported by the O-RU includes IPv6, so that the conventional constraints on the Internet protocol version of the O-RU can be relaxed.

[0031] The test profile management unit 13 manages test profiles such as an interoperability test (IoT: Interoperability Test) related to the interoperability of the M-Plane in a device compliant with O-RAN capable of supporting IPv6 and / or TLS. ■ As shown in FIG. 3, an IoT device is a communication device (UE) that is connected to a radio unit O-RU and can communicate with an O-RAN and / or a core network (not shown). In FIG. 3, an IoT device is distinguished from a mobile device such as a smartphone or a mobile phone for convenience, but in O-RAN, some or all mobile devices can be treated as a communication device (UE) similar to an IoT device with respect to IOT. The test profile management unit 13 is connected to each O-RU via the M-Plane of an open fronthaul, and operates an interoperability test profile related to the communication device (UE) connected to each O-RU. Here, the terms "management" and "operation" of the interoperability test profile handled by the test profile management unit 13 should be interpreted broadly.

[0032] For example, the test profile management unit 13 applies the test profile of the interoperability test to each O-RU and / or each communication device (UE), makes them comply with the test profile of the interoperability test, makes them follow the test profile of the interoperability test, imposes constraints and / or rules based on the test profile of the interoperability test, and the like, all of which correspond to the "management" or "operation" of the interoperability test profile handled by the test profile management unit 13. Also, the test profile management unit 13 applies the test profile of the interoperability test to itself and / or the radio access network control device 1, makes them comply with the test profile of the interoperability test, makes them follow the test profile of the interoperability test, imposes constraints and / or rules based on the test profile of the interoperability test, and allows only the connection and / or communication of O-RUs and / or communication devices (UEs) that conform to the test profile of the interoperability test, and the like, all of which correspond to the "management" or "operation" of the interoperability test profile handled by the test profile management unit 13.

[0033] 4 to 7 show specific examples of interoperability test profiles in the M-Plane of O-RAN that are compatible with IPv6 and TLS and that are managed and / or operated by the test profile management unit 13.

[0034] Figure 4 shows a specific example of an interoperability test profile in the "High Level Description" category. The "Architectural models" section is related to the "2.1.2 M-Plane architecture model" section of the O-RAN M-Plane specifications and includes a description of the "Hierarchical model". The "IP version" section is related to the "2.1.3 Transport Network" section of the O-RAN M-Plane specifications and includes a description of "IPv6". The "Hash algorithm for data integrity" section is related to the "2.4 Security" section of the O-RAN M-Plane specifications and includes a description of "Entry 1) SSHv2 -HMAC-SHA2-256" and "Entry 2) TLS1.2 - SHA256". The "Cyphering algorithm" section relates to the "2.4 Security" section of the O-RAN M-Plane specification, and includes the descriptions of "Entry 1) SSHv2 - AES128-CTR" and "Entry 2) TLS1.2 -AES128-GCM."

[0035] Among the above, the description of "IPv6" in the "IP Version" section makes the interoperability test profile compatible with IPv6. Also, the description of "Entry 2) TLS1.2 - SHA256" in the "Hash algorithm for data integrity" section and the description of "Entry 2) TLS1.2 -AES128-GCM" in the "Cyphering algorithm" section make the test profile compatible with TLS. These "Hash algorithm for data integrity" and "Cyphering algorithm" sections include the descriptions of TLS "Entry 2) TLS1.2 - SHA256" and "Entry 2) TLS1.2 -AES128-GCM", as well as the descriptions of SSH "Entry 1) SSHv2 -HMAC-SHA2-256" and "Entry 1) SSHv2 - AES128-CTR", respectively. "Entry 1" and "Entry 2" in these sections may be selected as appropriate.

[0036] Figure 5 shows a specific example of an interoperability test profile in the category of "Start up installation". The item "O-RU identification by DHCP option" is related to the section "3.1.1 O-RU identification in DHCP" in the O-RAN M-Plane specifications and includes the description of "DHCPv6 (Option: 16)". The item "VLAN Discovery" is related to the section "3.1.2 Management Plane VLAN Discovery Aspects" in the O-RAN M-Plane specifications and includes the description of "support VLAN SCAN". The item "IP address assignment" is related to the section "3.1.3 O-RU Management Plane IP Address Assignment" in the O-RAN M-Plane specifications and includes the descriptions of "Entry 1) IPv6 State-full address configuration" and "Entry 2) Stateless Address Auto-Configuration (SLAAC)". The "O-RU controller discovery" section relates to the "3.1.4 O-RU Controller Discovery" section of the O-RAN M-Plane specifications and includes the description of "DHCPv6 (Option: 17)". The "DHCP format of O-RU controller discovery" section relates to the "3.1.4 O-RU Controller Discovery" section of the O-RAN M-Plane specifications and includes the description of "O-RU Controller IP Address". The "NETCONF Call Home" section relates to the "3.2 NETCONF Call Home to O-RU Controller(s)" section of the O-RAN M-Plane specifications and includes the descriptions of "Entry 1) SSH - call home port:4334" and "Entry 2) TLS - call home port 4335".The term "SSH Connection Establishment" relates to the section "3.3 SSH Connection Establishment" in the O-RAN M-Plane specifications and includes the description "password-based authentication". The term "TCP port for SSH establishment (for test purpose)" relates to the section "3.3.1 NETCONF Security" in the O-RAN M-Plane specifications and includes the description "Default (port 830)". The term "NETCONF Authentication" relates to the section "3.3.2 NETCONF Authentication" in the O-RAN M-Plane specifications and includes the description "Entry 1) SSH password-based authentication" and "Entry 2) TLS - X.509 Certificate". The term "User Account Provisioning" relates to the section "3.3.3 User Account Provisioning" in the O-RAN M-Plane specifications and includes the description "default sudo".

[0037] Among the above, the description of "DHCPv6 (Option: 16)" in the "O-RU identification by DHCP option" section, the description of "Entry 1) IPv6 State-full address configuration" in the "IP address assignment" section, the description of "Entry 2) Stateless Address Auto-Configuration (SLAAC)" in the "IP address assignment" section, and the description of "DHCPv6 (Option: 17)" in the "O-RU controller discovery" section enable the interoperability test profile to support IPv6. "Entry 1" and "Entry 2" in the "IP address assignment" section may be selected as appropriate. In addition, the description of "Entry 2) TLS - call home port 4335" in the "NETCONF Call Home" section and the description of "Entry 2) TLS - X.509 Certificate" in the "NETCONF Authentication" section enable the interoperability test profile to support TLS. These "NETCONF Call Home" and "NETCONF Authentication" sections include the TLS descriptions "Entry 2) TLS - call home port 4335" and "Entry 2) TLS - X.509 Certificate," as well as the SSH descriptions "Entry 1) SSH - call home port:4334" and "Entry 1) SSH password-based authentication." "Entry 1" and "Entry 2" in these sections may be optional.

[0038] Figure 6 shows a specific example of the interoperability test profile in the category of "Start up installation", which continues from Figure 5. The "sudo" section relates to the "3.4 NETCONF Access Control" section of the O-RAN M-Plane specifications and includes the description "used". The "nms" section relates to the "3.4 NETCONF Access Control" section of the O-RAN M-Plane specifications and includes the description "not used". The "fm-pm" section relates to the "3.4 NETCONF Access Control" section of the O-RAN M-Plane specifications and includes the description "not used". The "swm" section relates to the "3.4 NETCONF Access Control" section of the O-RAN M-Plane specifications and includes the description "not used". The "NETCONF capability" section is related to the "3.5 NETCONF capability discovery" section of the O-RAN M-Plane specification, and includes the descriptions of "yang-library, Writable-running Capability, rollback on error, XPATH capability, Notifications, Interleave capability". The "Watchdog timer" section is related to the "3.6 Monitoring NETCONF connectivity" section of the O-RAN M-Plane specification, and includes the description of "used".

[0039] Figure 7 shows specific examples of interoperability test profiles for other categories. The category "O-RU to O-DU Interface Management" includes the items "VLAN tagging for C / U / M-Plane", "C / U Plane IP Address Assignment", "Definition of processing elements", "C / U Plane Transport Connectivity", and "O-RU Monitoring of C / U Plane Connectivity". The item "VLAN tagging for C / U / M-Plane" is related to the sections "3.1.2 Management Plane VLAN Discovery Aspects" and "4.3 C / U Plane VLAN Configuration" in the O-RAN M-Plane specifications, and includes the description "used for C / U / M-Plane". The item "C / U Plane IP Address Assignment" is related to the section "4.4 O-RU C / U Plane IP Address Assignment" in the O-RAN M-Plane specifications, and includes the description "not used". The term "Definition of processing elements" relates to Section "4.5 Definition of processing elements" in the O-RAN M-Plane specifications, and includes the description of "a combination of VLAN identity and MAC address." The term "C / U Plane Transport Connectivity" relates to Section "4.6 Verifying C / U Plane Transport Connectivity" in the O-RAN M-Plane specifications, and includes the description of "Loop-back Protocol (LB / LBM)."The item "O-RU Monitoring of C / U Plane Connectivity" relates to the section "4.10 O-RU Monitoring of C / U Plane Connectivity" in the O-RAN M-Plane specification and includes the statement "not used."

[0040] The "Baseline configuration" item in the "Configuration Management" category is related to the "6.1 Baseline configuration" section in the O-RAN M-Plane specifications and includes the description of "2 phases". The "subscribe notification" item in the "Fault Management" category is related to the "8.2 Manage Alarms Request" section in the O-RAN M-Plane specifications and includes the description of "default stream". The "Sync Capability Object" item in the "Synchronization Aspects" category is related to the "10.2 Sync Capability Object" section in the O-RAN M-Plane specifications and includes the descriptions of "Entry 1: CLASS_B" and "Entry 2: ENHANCED". "Entry 1" and "Entry 2" may be selected as appropriate. The "Activation, deactivation and sleep" item in the "Details of O-RU Operations" category relates to the "12.3.2 Activation, deactivation and sleep" section in the O-RAN M-Plane specifications and includes the description "used."

[0041] Conventional interoperability test profiles in the M-Plane of O-RAN support only IPv4 and do not support IPv6 or TLS. According to the present embodiment, the interoperability test profile in the M-Plane of O-RAN supports IPv6 and TLS, so that conventional restrictions on the interoperability test profile can be relaxed.

[0042] The present disclosure has been described above based on the embodiments. Various modifications are possible to the combinations of the components and processes in the exemplary embodiments, and it will be obvious to those skilled in the art that such modifications are included within the scope of the present disclosure.

[0043] The configuration, action, and function of each device and method described in the embodiments can be realized by hardware resources or software resources, or by the cooperation of hardware resources and software resources. For example, a processor, ROM, RAM, and various integrated circuits can be used as hardware resources. For example, programs such as an operating system and applications can be used as software resources.

[0044] The present disclosure may be expressed as follows:

[0045] Item 1: A test profile management unit manages test profiles for interoperability tests of M-Plane of O-RAN that is compatible with IPv6; A radio access network controller comprising at least one processor executing: Item 2: Item 1. The radio access network control device according to item 1, wherein the test profile includes a description of IPv6 in the "IP Version" section. Item 3: 3. The radio access network control device according to item 1 or 2, wherein the test profile includes a description of DHCPv6 in the section "O-RU identification by DHCP option". Item 4: The radio access network control device according to any one of items 1 to 3, wherein the test profile includes a description of a state-full address configuration in an "IP address assignment" section. Item 5: The radio access network control device according to any one of items 1 to 4, wherein the test profile includes a description of Stateless address auto-configuration in an "IP address assignment" section. Item 6: The radio access network control device according to any one of items 1 to 5, wherein the test profile includes a description of DHCPv6 in the "O-RU controller discovery" section. Item 7: A test profile management unit manages test profiles for TLS-compatible O-RAN M-Plane interoperability tests; A radio access network controller comprising at least one processor executing: Item 8: Item 8. The radio access network control device according to item 7, wherein the test profile includes a description of TLS in the section "Hash algorithm for data integrity". Item 9: 9. The radio access network control device according to item 7 or 8, wherein the test profile includes a description of TLS in the section "Cyphering algorithm". Item 10: The radio access network control device according to any one of items 7 to 9, wherein the test profile includes a description of TLS in the "NETCONF Call Home" section. Item 11: The radio access network control device according to any one of items 7 to 10, wherein the test profile includes a description of TLS in the "NETCONF Authentication" section. Item 12: 12. The radio access network control device according to any one of items 8 to 11, wherein the test profile includes a description of SSH in each of the items in addition to the description of TLS in each of the items. Item 13: Manage test profiles for M-Plane interoperability testing of IPv6-enabled O-RAN compliant devices; A radio access network control method comprising: Item 14: Manage test profiles for M-Plane interoperability testing on TLS-enabled O-RAN compliant devices; A radio access network control method comprising: Item 15: Manage test profiles for M-Plane interoperability testing of IPv6-enabled O-RAN compliant devices; A storage medium storing a radio access network control program for causing a computer to execute the above. Item 16: Manage test profiles for M-Plane interoperability testing on TLS-enabled O-RAN compliant devices; A storage medium storing a radio access network control program for causing a computer to execute the above.

[0046] This application claims priority from International Patent Application PCT / JP2022 / 001559, filed on January 18, 2022, the entire contents of which are incorporated by reference. [Industrial Applicability]

[0047] The present disclosure relates to management of interoperability test profiles in the M-Plane of O-RAN. [Explanation of symbols]

[0048] 1 Radio access network control device, 11 IP version setting unit, 12 IP version detection unit, 13 Test profile management unit.

Claims

1. A test profile management unit manages a test profile for an M-Plane interoperability test in an IPv6-enabled O-RAN-compliant device; A radio access network controller comprising at least one processor executing:

2. The radio access network controller according to claim 1 , wherein the test profile includes a description of IPv6 in an "IP Version" section.

3. The radio access network controller according to claim 1 , wherein the test profile includes a description of DHCPv6 in an "O-RU identification by DHCP option" section.

4. The radio access network controller according to claim 1 , wherein the test profile includes a description of a state-full address configuration in an "IP address assignment" section.

5. The radio access network controller according to claim 1 , wherein the test profile includes a description of Stateless address auto-configuration in an "IP address assignment" section.

6. The radio access network controller according to claim 1 , wherein the test profile includes a description of DHCPv6 in an "O-RU controller discovery" section.

7. A test profile management unit manages a test profile for an M-Plane interoperability test in a TLS-enabled O-RAN compliant device; A radio access network controller comprising at least one processor executing:

8. The radio access network controller according to claim 7 , wherein the test profile includes a description of TLS in a section titled “Hash algorithm for data integrity”.

9. The radio access network controller according to claim 7 , wherein the test profile includes a description of TLS in a section titled “Cyphering algorithm”.

10. The radio access network controller according to claim 7 , wherein the test profile includes a description of TLS in a “NETCONF Call Home” section.

11. The radio access network controller according to claim 7 , wherein the test profile includes a description of TLS in a section "NETCONF Authentication".

12. The radio access network controller according to claim 7 , wherein the test profile includes a description of TLS and a description of SSH in at least one section.

13. Managing test profiles for M-Plane interoperability testing on IPv6 enabled O-RAN compliant devices; A radio access network control method comprising:

14. Managing test profiles for M-Plane interoperability testing on TLS-enabled O-RAN compliant devices; A radio access network control method comprising:

15. Managing test profiles for M-Plane interoperability testing on IPv6 enabled O-RAN compliant devices; A storage medium storing a radio access network control program for causing a computer to execute the above.

16. Managing test profiles for M-Plane interoperability testing on TLS-enabled O-RAN compliant devices; A storage medium storing a radio access network control program for causing a computer to execute the above.

Images