hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5.2 Interfaces | The M-Plane interface is defined between the O-RU Controller and the O-RU. The protocol stack of the M-Plane interface is shown in Figure 5.2-1 below. The transport network layer built on IP transport, SSH/TCP, and TLS, is used to carry the M-Plane message between the O-RU Controller and the O-RU. As an option, the O-RU may support the capability to support asynchronous notifications to be sent using HTTPS. This option enables system optimization when the O-RU Controller corresponds to the SMO which is operating with a non-persistent NETCONF session to the O-RU. 802.1X ARP ICMP DHCP NDP DHCPv6 MPlane (note 1) Notif (note 2) Notif (note 3) SFTP FTPES CMPv2 UDPECHO LBM ICMPv6 NETCONF HTTP SSH or TLS TLS SSH TLS HTTP UDP UDP TCP UDP IPv4 IPv6 IPv4 or IPv6 802.1Q tagged or (opt) untagged ETH frames Physical Layer NOTE 1: Management Plane Configuration Management. NOTE 2: Asynchronous Notification over NETCONF. NOTE 3: Asynchronous Notification over JSON/REST (Optional). Figure 5.2-1: M-plane protocol stack |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5.3 YANG module introduction | The data models representing the M-Plane are organized as a set of reusable YANG modules. It is also the intent to reuse the publicly available and generic YANG models as much as possible instead of developing customized O-RAN specific modules. Refer to the various clauses, clause D and the repository of YANG models for more details on each of these modules. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5.4 Security | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5.4.1 General | Clause 5.4 specifies the security requirements for the O-RU. The O-RU shall provide end to end security for all OAM procedures. All O-RUs shall support SSH based security described in clause 5.4.2 and TLS based security described in clause 5.4.3. Corresponding file transfer protocols are defined in clause 5.4.4, including SFTP-based transfer over SSH and FTPES-based transfer over TLS. As per requirements in [79] clause 5.3.4.1, all O-RUs should implement robust implementations of SSH and TLS transport protocols. NOTE: It is recommended that operators use NETCONF/TLS and FTPES in production networks. A summary of the mandatory and optional O-RU authentications features is shown in Table 5.4.1-1. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 27 Table 5.4.1-1: Mandatory and Optional Features for O-RU Authentication Protocol Certificate lifecycle management PKIX (Public Key Infrastructure with X.509 Certificates) Simple Public Key Password-based Authentication TLS 1.2 (Mandatory) TLS 1.3 (Optional) Mandatory to support CMPv2, optional to support vendor certificate lifecycle management Mandatory to support / Optional to use Not specified for use with TLS Not specified for use with NETCONF SSHv2 (Mandatory) Optional to support CMPv2, optional to support vendor certificate lifecycle management Optional to support/Optional to use Used for SSH Server authentication by SSH client (IETF RFC 4253 [7]). Mandatory to support / Optional to use. Used for SSH Client authentication by SSH server (IETF RFC 4252 [6]). Optional to support / Optional to use. Used for SSH Client authentication by SSH server. Mandatory to support / Optional to use |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5.4.2 Secure Shell (SSH) | The O-RU shall support NETCONF/SSHv2 as specified in IETF RFC 6242 [5]. If there are multiple NETCONF sessions established with a single O-RU, each session should be established over a separate SSH tunnel. SSHv2 may be used to perform SSH client authentication, SSH server host authentication, key exchange, encryption, and integrity protection. It also derives a unique session ID that may be used by higher-level protocols. The end point (SSH client) authentication should be done as specified in IETF RFC 4252 [6]. Clause 6.4.2 of the present document describes NETCONF authentication approach. The authentication mechanism and protocol for operators to use are as shown in Table 5.4.1-1. The SSHv2 transport level security (encryption algorithms, data integrity algorithms) shall be as specified in IETF RFC 4253 [7]. The O-RU shall support the mandatory symmetric algorithms for encrypting transferred data as specified in clause 4.1.2.2 of [56], with the following deviation: • support for aes256-gcm, aes128-gcm, aes256-ctr and aes192-ctr are optional for the O-RU to support. For data integrity, the O-RU shall support the mandatory message authentication codes (MACs) specified in clause 4.1.2.4 of [56], with the following deviation: • support for hmac-sha2-512-etm, hmac-sha2-512, hmac-sha2-256-etm and umac-128 are optional for the O-RU to support. Public key-based host authentication shall be used for authenticating the server by the clients, and username/password- based client authentication shall be done by the server as part of the SSH session establishment as specified in IETF RFC 4253 [7]. The O-RU shall support the host key algorithms and key exchange methods for securing the Secure Shell (SSH) transport, as specified in clause 10.1 of IETF RFC 5656 [63]. The O-RU shall support the mandatory key agreement algorithms, may support the optional key agreement algorithms and shall not support the prohibited key agreement algorithms, as specified in clause 4.1.2.1 of [56], with the following deviation: • support for ssh-ed25519 is optional for the O-RU to support. The O-RU shall support the mandatory key exchange methods and shall not support the prohibited key exchange methods as specified in clause 4.1.2.3 of [56], with the following deviation: • support for diffie-hellman-group-exchange-sha256 and curve25519-sha256 are optional for the O-RU to support. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 28 The O-RU should support the following host key algorithms as specified in IETF RFC 8332 [68]: • rsa-sha2-256 • rsa-sha2-512 In order to ensure backwards compatibility with equipment supporting earlier versions of the present document, a vendor may provide support for other, optional non-broken host key algorithms and key exchange methods. NOTE 1: A "non-broken" algorithm is an algorithm without publicly available/published vulnerabilities. As an additional option, both client and server may implement authentication based on X.509 certificates. With this option, RSA 2048 bit shall be supported for the Public Key algorithm, aes128-ctr shall be supported for the ciphering algorithm and hmac-sha2-256 shall be supported for integrity algorithm. NOTE 2: The vendor and operator need to be prepared to replace integrity and/or ciphering algorithms if the current algorithm in use is compromised or deprecated. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5.4.3 Transport Layer Security (TLS) | TLS requirements specified in O-RAN Security Protocols Specifications [56], clause 4.2 shall apply, with the following deviations: • TLS 1.3 as specified in IETF RFC 8446 [42] and clause 4.2.3 of O-RAN Security Protocols Specifications [56] may be supported. IETF RFC 7589 [41] provide the procedures for TLS interoperability with NETCONF implementations. TLS as specified in O-RAN Security Protocols Specification [56] performs mutual authentication, key exchange, encryption, and integrity protection to ensure trusted communication between the NETCONF server (O-RU) and the NETCONF client (O-DU or SMO). NETCONF implementations shall support X.509 certificate-based authentication using TLS as specified in IETF RFC 7589 [41]. When X.509 based authentication is used, NETCONF server identity is as specified in clause 4 of IETF RFC 9525 [84] and NETCONF client identity is specified in clause 7 of IETF RFC 7589 [41]. If there are multiple NETCONF sessions established with a single O-RU, each session should be established over a separate TLS connection. It is mandatory that TLS implementations follow the rules on allowed cipher suites specified in clause 4.2.2 of the O-RAN Security Protocols Specifications [56]. TLS implementations shall support the TLS Cipher Suites with SHA-256 and AES Galois Counter Mode as specified in clause 9.2 of IETF RFC 7540 [49] and clause 7 of ETSI TS 133 210 [46]: Implementations may include additional TLS cipher suites that provide mutual authentication and confidentiality as required by NETCONF in IETF RFC 6241 [3]. Only cipher suites with AEAD (e.g. GCM) and PFS (e.g. ECDHE, DHE) and recommended by IANA [45] may be optionally supported. The disallowed cipher suites in IETF RFC 7540 [49], Appendix A, shall not be used. The vendor and operator need to be prepared to replace integrity and/or ciphering algorithms if the current algorithm in use is compromised or deprecated. TLS 1.2 shall follow TLS profiling defined in clause 6.2.3 of ETSI TS 133 210 [46]. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5.4.4 File Transfer Protocol (SFTP, FTPeS) | An O-RU shall support SFTP based secure file transfer over SSH and FTPES based secure file transfer over TLS. Security file transfer requirements specified in O-RAN Security Protocol Specifications [56] clauses 6.2 and 6.3 shall apply. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5.4.5 Representational State Transfer | An O-RU may optionally support of JSON/REST transported over HTTPS. NOTE: JSON/REST is be used by O-RUs supporting the NON-PERSISTENT-MPLANE feature and the configured subscriptions capability described in clause 18. HTTPS requirements specified in O-RAN Security Protocol Specifications [56] clause 6.4 shall apply. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 29 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6 "Start-up" installation | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.1 General | This clause provides the overall start-up mechanism from the power-on of O-RU to available in service. Pre-condition: • Power-ON for O-RU/NETCONF Server or O-RU restart operation. O-RU enables its port(s). • O-RU controller/NETCONF Client(s) and/or event-collector is/are in operation. • Physical interface(s) is(are) connected to a compatible Ethernet port. Post-condition: • O-RU is running software from slot with active = TRUE. • O-RU has marked slot with currently used software as running = TRUE. • O-RU is ready for the radio transmission to the air on at least one carrier if packet transmission received from O-DU. • O-RU is ready for the packet transmission to the O-DU if radio reception received at the air on at least one carrier. • At least one O-RU Controller/NETCONF client with either "sudo" or "hybrid-odu" access privileges can control the carrier configuration of the O-RU/NETCONF server in O-RU. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 30 Figure 6.1-1: Overall of Start-Up Installation ETSI ETSI TS 104 023 V17.1.0 (2026-01) 31 At the power-on of O-RU or following an O-RU restart, the following procedures are performed, as illustrated in Figure 6.1-1: 1) (opt) Supplicant PAE is enabled on the port(s). 2) (opt) The O-RU initiates authentication and attempts to perform an EAP authentication dialogue with a peer Authenticator PAE. NOTE 1: This does not limit the ability of an Authenticator PAE to initiate the authentication, as defined in clause 8.1 of [70] 3) (alt) EAP failure results in O-RU providing unauthenticated connectivity. 4) (alt) EAP Success results in O-RU providing authenticated connectivity. 5) O-RU performs M-Plane transport layer resolution (DHCP, MAC, VLAN, IP, etc.) and recovers IP address(es) of O-RU controller(s) and/or pnfRegistration event-collector. 6) (opt) If DHCP response contains CA/RA address information and the O-RU has not already enrolled in the operator PKI, or the certificate issued during previous enrolment has expired, the O-RU attempts to enrol. 7) (opt) After installing the operator issued certificate, the O-RU re-initializes its start-up procedure (jump to step 1). 8) O-RU begins synchronization of the O-RU against a Primary Reference Clock. Step 8 may be in parallel with step 5 for some O-RU implementation. 9) (opt) O-RU performs NETCONF Call Home to discovered O-RU controller(s). 10) (opt) O-RU performs pnfRegistration to discovered event-collector. 11) O-RU controller performs SSH or TLS connection establishment. 12) O-RU and O-RU controller perform NETCONF capability discovery. 13) (opt) O-RU controller retrieves O-RU schemas using <get-schema> RPC [67]. 14) O-RU controller performs optional provisioning of new management accounts (typically only performed once during pre-staging). O-RU controller may perform provisioning of certificate-to-NETCONF username mapping information to the O-RU after account provisioning in case certificate-based client authentication is used. 15) O-RU and O-RU controller perform supervision of NETCONF connection. 16) O-RU controller performs retrieval of O-RU information. (opt) O-RU controller retrieves O-RU S-Plane information and if necessary, it updates the O-RU's S-Plane configuration. (This step may be started any time after step 15 but needs to be completed before step 28). 17) O-RU controller performs SW management. NOTE 2: If an O-RU is running with factory default software, the O-RU functionality is permitted to comprise a sub-set of a fully operating O-RU. In such scenarios, it is recommended that the O-RU controller triggers a software update to fully functioning O-RU software. 18) O-DU performs CU-Plane transport configuration. 19) (opt) O-DU performs LBM configuration (CU-Plane over ETH) or enables UDP Echo (CU-Plane over IP). 20) (opt) O-DU performs initial C/U-Plane transport connectivity checking between O-DU and O-RU. 21) O-RU controller retrieves the O-RU delay profile from the O-RU. 22) O-RU controller performs U-Plane configuration between O-DU and O-RU. C/U-Plane transport connectivity between O-DU and O-RU is configured as part of this step. 23) O-DU optionally performs C/U-Plane delay measurements between O-DU and O-RU if the O-RU supports it. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 32 24) O-RU controller performs Fault Management activation by creating a subscription to the YANG notifications defined in the o-ran-fm.yang model. Additionally, the O-RU controller uses the same YANG model to retrieve the list of O-RU's active alarms. See clause 11 for details. 25) O-RU controller activates performance measurement (if required at start-up timing). 26) O-RU controller retrieves O-RU state, including synchronization information, from O-RU. 27) O-RU controller configures the O-RU operational parameters. 28) Service available. Additional Start-up considerations: • The synchronization procedures started in step 8 needs to be completed before service is available. If the O-RU's power-on S-Plane settings are incompatible with the network's S-Plane design, then at step 16 the O-RU controller should reconfigure the O-RU's S-Plane settings. • Periodic CU-Plane connectivity check is not considered as the part of start-up. Once configured in start-up phase, CU-Plane connectivity check can later be performed periodically and at any time in run-time. • The details of the above start-up procedure are covered in clauses 6.3 to 6.7. Cross Reference to other clauses: • The details of 8, 16 and 26. Synchronization management is described in clause 13. • The method of 13 and 26 retrieval of O-RU information is described in clause 9. • The detail of 17. SW management is described in clause 8. • The detail of 20. C/U-Plane transport connectivity checking between O-DU and O-RU is described in clause 7. • The detail of 21. Retrieval of the O-RU delay profile and 23. C/U-Plane delay measurements are described in clause 7. • The detail of 22. U-plane configuration is described in clause 15, and C/U-Plane transportation configuration is described in clause 7. • The detail of 25. Performance management is described in clause 10. • The detail of 24. Fault management is described in clause 11. • The method of 27. Control to make service available is described in clause 15. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2 Management plane transport aspects | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.1 Transport establishment | This clause provides the M-plane transport establishment scenario between O-RU and O-RU controller(s), such as O-DU and/or SMO. The transport layer address of M-plane is only the target in this clause. Transport aspects of the C plane and U plane are covered in clause 7. Pre-condition: • Physical interface is connected to a compatible Ethernet port. • When operating in an environment using call-home, the NETCONF server and NETCONF Client(s) have an identical NETCONF call home port configured, to ensure the NETCONF client listens on the same port used by the NETCONF Server. Post-condition: • Transport Layer address(es) for M-plane are known to O-RU and O-RU controllers. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 33 • O-RU is aware of the physical port(s) for M-plane, e.g. if there are multiple ports in the O-RU. • O-RU is aware of the VLAN(s) to be used for M-Plane, e.g. if VLANs are used in the transport network. • Then O-RU is ready to establish TCP connection for NETCONF call home and/or for PNF registration. For the transport establishment, there are the following alternatives, as illustrated in Figure 6.2.1-1: a) Manual transport layer address configuration in O-RU. This configuration contains the addresses for O-RU and NETCONF client(s) and/or the event-collector. The method to manually configure the O-RU is out of scope in the present document. Assuming manual configuration is successful, the NETCONF server shall be able to recover this configured information and use the client-info container in the o-ran-mplane-int.yang model to expose this information to a NETCONF client. b) If IPv4 is supported, DHCP server provides O-RU's transport layer address information together with the identity of the NETCONF client and/or the identity of the event-collector. This identity encodes either the transport layer address or FQDN of the NETCONF client or event-collector. If an FQDN is signalled, the O-RU shall use the DNS server address provided by the DHCP server to recover the IP address corresponding to FQDN of the NETCONF client or event-collector. c) If IPv6 is supported, Stateless Address Auto-Configuration (SLAAC) is used to configure the O-RU's transport address with the DHCPv6 server providing the identity of the NETCONF client and/or event-collector. This identity encodes either the transport layer address or FQDN of the NETCONF client or event-collector. If an FQDN is signalled, the O-RU shall use the DNS server address provided by the DHCPv6 server to recover the IP address corresponding to FQDN of the NETCONF client or event-collector. d) A NETCONF Client with suitable privileges can use the ietf-interfaces YANG module augmented by ietf-ip and o-ran-interfaces YANG modules to configure the O-RU's IPv4 and/or IPv6 ip address and associated subnet/prefix, together with port-reference and optional vlan-id. In this case the origin parameter from ietf-ip.yang module shall be set to "static". Assuming configuration is successful, the NETCONF server shall be able to operate with the configured network layer parameters provided by the NETCONF Client. The NETCONF server shall use the client-info container in the o-ran-mplane-int.yang model to expose NETCONF client information to other NETCONF clients. NOTE: A NETCONF client can receive a hint as to whether an O-RU supports a particular IP version by using the get RPC to recover the list of interfaces supported by the O-RU and using the presence of the augmented ipv4 container or ipv6 container in the o-ran-interfaces module as an indication that a particular IP version is supported. The O-RU uses the o-ran-dhcp.yang model to be able to expose information signalled by the DHCP server. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 34 Figure 6.2.1-1: Transport Layer Establishment for M-plane Transport Layer interface related information for M-plane contains at least the physical port number, the hardware address of the Ethernet port, VLAN-ID, local IP address, remote IP address, Default Gateway address and Subnet mask. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 35 In the case of option b) and c), the following clauses are used: • O-RU identification in DHCP messages from O-RU (clause 6.2.2). • VLAN discovery aspect for M-plane (clause 6.2.3). • IP address assignment to O-RU (clause 6.2.4). • Discovery of address information of O-RU controller(s) and/or Event-Collector (clause 6.2.5 and/or clause 6.2.7). |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.2 O-RU identification in DHCP | The O-RU shall use the DHCP Vendor Class option(s) with the vendor-class-data string within the o-ran-dhcp YANG model or vendor identifying vendor class option with enterprise number and vendor-class-data to identify itself as an O-RU to DHCP servers. When the O-RU supports IPv4, it shall identify itself either 1) use option 60 Vendor Class Identifier, as specified in IETF RFC 2132 [8], OR 2) use option 124 Vendor Identifying Vendor Class Option, as specified in IETF RFC 3925 [9]. When the O-RU supports IPv6, it shall identify itself using the DHCPv6 Vendor Class Option 16. O-RU can identify itself with both O-RAN registered IANA Enterprise Number and 3GPP registered Enterprise Number when using option 124 to retrieve O-RU controller, event controller and CA/RA information in DHCPv4 server. If an O-RU intends to get only O-RAN domain information, O-RU can use opt 60 or opt 124 with only O-RAN enterprise number. NOTE: To support DHCP server implementations that are limited in their support for multiple instances of the Vendor-Specific Information Options, an operator and vendor can agree to use the O-RAN registered IANA Enterprise Number in DHCPv4/DHCPv6 messages to identify itself to signal the CA/RA server information. DHCPv4 Vendor Class Option: • Option: 60 • Vendor Class Identifier Option 60: string The format of the vendor class string shall be configured to one of the following three options: 1) "o-ran-ru2/<vendor>", e.g. "o-ran-ru2/vendorA" OR 2) "o-ran-ru2/<vendor>/<product-code>", e.g. "o-ran-ru2/vendorA/ORUAA100" OR 3) "o-ran-ru2/<vendor>/<product-code>/<serial-number>", e.g. "o-ran- ru2/vendorA/ORUAA100/FR1918010111". The Vendor Class Identifier should be selected to avoid the likelihood that different vendors select identical strings, e.g. using a vendor namespace registry or ensuring that the identifier includes the <product-code> information. DHCPv4 Vendor-Identifying Vendor Class Option: • Option: 124 • Enterprise number: O-RAN-alliance 53148 • Vendor-Class-Data: the format of the string shall follow the rules defined for the DHCPv4 Vendor Class Option DHCPv6 Vendor Class Option: • Option: 16 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 36 • Enterprise number: O-RAN-alliance 53148 • Vendor-Class-Data: the format of the string shall follow the rules defined for the DHCPv4 Vendor Class Option The DHCP Server may use the information when selecting an address pool from which to allocate an IP address to the O-RU or when selecting which management plane O-RU Controller information to configure in the O-RU. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.3 Management plane VLAN discovery aspects | The O-RU is connected to one or more Ethernet ports. The transport systems may be realized such that these Ethernet ports is/are configured either as an access port, where untagged Ethernet frames are used, or as a trunk port, where multiple VLANs are configured. During start up, the O-RU is typically unable to immediately determine whether its ports are attached to remote transport equipment configured for access or trunk mode operation. Once an O-RU completes its boot-up sequence and Ethernet connectivity is detected on at least one of its Ethernet interfaces, the O-RU starts management plane connection establishment. The O-RU shall determine whether it is connected to an access port or a trunk port. In particular, when connected to a trunk port, the O-RU shall additionally determine the VLAN identity/ies used to support the management plane communication(s). The VLAN(s) used to support management plane communications can be identified by the DHCP server replying to the DHCP DISCOVER message, as described in clause 6.2.5, clause 6.2.7 or clause 6.2.6.1. NOTE 1: An O-RU which supports IPv6 can infer that a VLAN is not used to support management plane communications if it receives an IPv6 Router Advertisement without either the "managed address configuration" or "other configuration" bits set. NOTE 2: Versions prior v12.0 of the present document did not define management plane VLAN discovery based on CA/RA server identity as specified in clause 6.2.6.1. When operating with O-RUs that support an earlier version of this documents, an operator wanting to operate a VLAN that restricts access to production O-RU controllers, e.g. offering sole access to a CA/RA server, can configure a dummy NETCONF client identity to be returned to the O-RU in the DHCP OFFER message. If the O-RU does not have previously configured management plane VLAN information, the O-RU shall attempt to discover DHCP servers on all its Ethernet ports using untagged Ethernet frames. When the O-RU has been previously configured with management plane VLAN information, the O-RU may use this information to optimize its discovery of the VLAN ID(s) used for management plane connectivity. Previously configured management plane VLAN information includes an O-RU that stores the last VLAN(s) used for management plane connectivity, and/or an O-RU which has been previously configured with a range of management plane VLANs by a NETCONF client using the contents of the searchable-mplane-access-vlans-info container that have been stored in reset-persistent memory. The O-RU may use this information to optimize its discovery of the VLAN ID(s) used for management plane connectivity. If the O-RU does not receive a DHCP OFFER from a DHCP server using untagged frames, or previously configured VLANs, the O-RU should attempt to contact a DHCP server using the full range of VLAN IDs (1~4094) on all its Ethernet ports. The individual VLAN search algorithm used by an O-RU should ensure timely activation of the M-Plane while accommodating scenarios whereby there may be an intermittent or temporary connectivity problem between the O-RU and the DHCP server causing no DHCP response to be received on the M-Plane VLAN. The O-RU should repeatedly search using untagged frames and previously configured VLANs whenever it searches across the full range of VLAN IDs. The O-RU controller is able to recommend the maximum interval between repeatedly scanning for M-Plane connectivity on the untagged and configured VLANs using the scan-interval schema node. For example, the default scan-interval is 60 seconds. If the O-RU takes 1 second to scan an individual VLAN, then after scanning every 60 out of the full range of VLAN IDs, the O-RU should repeat the scan for M-Plane connectivity on untagged and configured VLANs. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 37 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.4 O-RU management plane IP address assignment | Automatic IP address assignment for the O-RU management plane can be achieved using different techniques: 1) IPv4 configuration using DHCPv4, as described in IETF RFC 2131 [10] enables DHCP servers to configure IPv4 network address(es) on the O-RU. An O-RU implementing IPv4 shall support the behaviour specified in clause 6.1 of IETF RFC 4361 [33], using stable DHCPv4 node identifiers in their dhcp-client-identifier option. A network realized with multiple DHCP servers should ensure that their configurations are coordinated to ensure a common default gateway is provisioned in an O-RU which receives multiple DHCPv4 responses, e.g. when received over different interfaces. An O-RU may indicate that it supports configuration of routing information as specified in IETF RFC 3442 [62], enabling static routes to be used by the O-RU when determining how to route uplink packets, e.g. when the O-RU supports multiple interfaces. For O-RUs that support IPv6, both stateful and stateless address assignment procedures are supported: 2) IPv6 Stateless Address Auto-Configuration (SLAAC), IETF RFC 4862 [11] enables the O-RU to generate link-local and global addresses. A network realized with multiple IPv6-enabled routers that support dynamic address assignment should use the extensions to Router Advertisements as specified in IETF RFC 4191 [61] to configure the preference of the default route prefixes learnt by the O-RU using SLAAC. 3) IPv6 State-full address configuration uses DHCPv6, as specified in IETF RFC 8415 [58] and enables DHCP servers to configure IPv6 network address(es) on the O-RU. DHCPv6 is transported using UDP, using the link-local address on the O-RU and a link-scoped multicast address on the DHCP server. NOTE 1: The above does not restrict the realization of the DHCP server, which can be integrated with the O-DU, can be provided by the transport system, or can be accessed via a relay. O-RUs that support more than one network interface should use a different client-identifier on each interface using a combination of Identity Association Unique Identifier and DHCP Unique Identifier, as specified in clause 6.1 of IETF RFC 4361 [33] for DHCPv4 and clauses 11 and 12 of IETF RFC 8415 [58] for DHCPv6. NOTE 2: An O-RU Controller can learn the particular client identifier(s) used by an O-RU by using the o-ran-dhcp YANG model. The DHCP server should operate using static bindings, i.e. ensuring an O-RU identified by a particular client hardware address is re-allocated the same management plane IP address, e.g. after performing an O-RU reset procedure. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.5 O-RU controller discovery | This clause provides how to automatically discover the O-RU Controller address(es). O-RUs that have obtained their IPv6 addresses by stateless address auto-configuration, shall use stateless DHCPv6 as specified in IETF RFC 8415 [58], to obtain management plane configuration information. Other O-RUs operating using stateful IPv4 or IPv6 address allocations shall obtain management plane configuration information during IP address allocation. Other O-RUs which have had their IP address(es) manually configured, shall also have their O-RU Controller(s) manually configured. O-RAN defined vendor specific option shall be used to signal all NETCONF client information to the O-RU using option 43 or option 125 for DHCPv4 and option 17 for DHCPv6. The O-RU shall request this option. Multiple instances of NETCONF client information may be signalled, encoded as a sequence of type/length/value fields. The O-RU shall consider these DHCP options as concatenation-requiring-options, as specified in IETF RFC 3396 [78]. NOTE: Previous versions of the present document (prior to v15.0) did not require support of IETF RFC 3396 [78]. For previous versions, the support for IETF RFC 3396 [78] can be agreed between an operator and vendor. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 38 The definition of the types used within the DHCPv4 option 43, option 125/DHCPv6 Option 17 depends on the vendor-class option reported by the O-RU in its DHCP messages. When a legacy O-RU reports its vendor-class using the "o-ran-ru" prefix, the following types are defined: • Type: 0x01 - O-RU Controller IP Address • Type: 0x02 - O-RU Controller Fully Qualified Domain Name When the O-RU reports its vendor-class using the "o-ran-ru2" prefix, the following types are defined: • Type: 0x81 - O-RU Controller IP Address • Type: 0x82 - O-RU Controller Fully Qualified Domain Name • Type: 0x86 - O-RU Call home protocol In all cases, the Type is followed by the length, which is the hexadecimal encoding of length of value field in octets, and the Value. When Type corresponds to an O-RU Controller IP Address, the value encodes IPv4 address(es) in hexadecimal format. For example, a single server with IPv4 address 198.185.159.144 is encoded in an option 43 or option 125 TLV as: • Type 0x81 (or x01 for legacy) • Length: 0x04 • Value: C6 B9 9F 90 When Type corresponds to an O-RU Controller Fully Qualified Domain Name, this encodes the string representation of domain name, using ACSII encoding (i.e. following for encoding used for the domain name in the Host Name DHCP Option 12). For example, a server with FQDN "controller.operator.com" is encoded in an option 43 or option 125 TLV as: • Type 0x82 (or x02 for legacy) • Length: 0x17 • Value: 63 6F 6E 74 72 6F 6C 6C 65 72 2E 6F 70 65 72 61 74 6F 72 2E 63 6F 6D The format of the DHCPv6 option 17 follows the format of the DHCPv4 encoding, with the additional inclusion of an Enterprise Number prior to the TLV option data. The IANA allocated private enterprise number to be used with DHCPv6 option 17 is 53148. When Type corresponds to the call home protocol, the value encodes whether an O-RU shall call home using NETCONF/SSH or NETCONF/TLS using the IANA defined ports as specified in clause 6 of IETF RFC 8071 [15]. If no call home protocol type is provided, the O-RU shall use NETCONF/SSH. The format is encoded as follows: • Value 00 - O-RU shall attempt to call home using NETCONF/SSH • Value 01 - O-RU shall attempt to call home using NETCONF/TLS For example, a DHCP server wanting to trigger the call home procedure using NETCONF/TLS encodes the option 43 or option 125 TLV as: • Type: 0x86 • Length: 0x01 • Value: 01 NOTE: A previous version of the present document defined the use of OPTION_V4_SZTP_REDIRECT and OPTION_V6_SZTP_REDIRECT DHCP options to allow an O-RU to recover NETCONF Client information. In order to ensure backwards compatibility with equipment supporting earlier versions of the present document, an operator and vendor can agree to continue to use OPTION_V4_SZTP_REDIRECT and/or OPTION_V6_SZTP_REDIRECT DHCP options to recover NETCONF Client information. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 39 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.6 Certificate handling | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.6.0 Trust anchor provisioning | Before an O-RU can establish a mutual TLS connection with a signalling peer, e.g. with an O-RU Controller, an O-RU needs to be able to trace the peer's certificate path to a valid trust anchor. To validate against a trust anchor, the O-RU shall be able to be provisioned with one or more trust anchor certificates. The O-RU shall ensure that all trust anchor certificates are stored in reset persistent memory and protected from unauthorised external modification. The O-RU shall be able to be provisioned with new trust anchors. Provisioning of trust anchors is done using one of the options in clause 5.3.11 in [83] or through configuration in ietf-truststore. The O-RU shall be able to have an existing trust anchor replaced, e.g. because it has expired. The O-RU should support ietf-truststore YANG model to enable an O-RU Controller to manage (read, add, delete) the list of provisioned trust anchors and associated public keys. NOTE 1: If the O-RU is configured to perform certificate enrolment, the CMPv2 Initialization Response message allows the discovered CA/RA server to provision a trust anchor. NOTE 2: The CA/RA Server identity is configured by the DHCP server using techniques described in clause 6.2.6.1. The DHCP server is not considered by the O-RU as a trusted source of security bootstrapping data. When shipped, an O-RU only trusts information that is signed or encrypted using a certificate chain leading to a pre-loaded trust anchor. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.6.1 Certificate enrolment | An O-RU shall support certificate enrolment using CMPv2 as specified in IETF RFC 4210 [44]. ETSI TS 132 509 [52] specifies how the O-RU supporting certificate enrolment over IPv4 can be configured with the IP address or FQDN of one or more Certification Authority (CA/RA) servers using DHCP Option 43 as specified in clause 4.2.2 of ETSI TS 132 509 [52]. The DHCP Options specified in ETSI TS 132 509 [52] do not specify how to signal a CA/RA server identity using DHCPv6. Hence, O-RU certificate enrolment using CMPv2 over IPv6 shall support the signalling of vendor specific options using DHCPv6 option 17. The format of the DHCPv6 option 17 follows the format of the DHCPv4 encoding as specified in clause 4.2.2 of ETSI TS 132 509 [52], with the additional inclusion of an Enterprise Number prior to the TLV option data. The IANA allocated private enterprise number to be used with DHCPv6 option 17 shall be 53148 (as allocated by IANA to O-RAN Alliance). 3GPP has since published ETSI TS 128 316 [72] which now specifies how to signal a CA/RA server identity with DHCPv6 option 17 messages using the 3GPP registered IANA Enterprise Number (10415). The DHCP Options defined in [52] are a subset of those defined in [72]. An operator and vendor can agree to use the 3GPP registered IANA Enterprise Number in DHCPv6 messages that signal the CA/RA server information instead of the O-RAN registered IANA Enterprise Number. If an O-RU has a point-to-point connection between the O-RU and the O-DU, or if an O-RU has a bridged connection between the O-RU and the O-DU and the O-DU is operating as the default gateway to provide connectivity between the O-RU and a remote CA/RA server, when the O-RU is required to perform certificate enrolment using CMPv2, the O-DU shall provide means for the O-RU to access the operator CA/RA for the O-RU certificate enrolment at the IP address conveyed as described above. If the FQDN option is used instead, the O-DU shall provide means for the O-RU to access an operator DNS server in addition. Examples of providing such access include: • An IP forwarding function within the O-DU providing access to the operators PKI. • A Network Address Translation function within the O-DU providing access to the operators PKI. • A Registration Authority (RA) function accessible by the O-DU (in the same domain), which is part of the operator PKI. An O-RU shall report any discovered multi-vendor plug-and-play servers using the o-ran-dhcp YANG model. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 40 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.6.2 CMPv2 based certificate enrolment | This clause covers the use case where an O-RU is configured with the identity of a CMPv2 capable CA/RA server that the operator uses for certificate enrolment. The O-RU shall attempt to enrol in the operator-PKI and may be issued an operator-signed certificate. The Initialization Request (IR) message used to signal the initial certificate enrolment shall be signed using the private key of the manufacturer installed certificate. NOTE 1: The pre-conditions for certificate enrolment described in clause 5.5 of [i.7] includes the condition that the vendor's root certificate is pre-provisioned in the CA/RA server. Clause 9 of ETSI TS 133 310 [51] specifies the use of CMPv2 used by base stations to obtain an operator-signed certificate using a secured communication based on the vendor-signed certificate in the base station and a vendor root certificate pre-installed in the CA/RA server. While the approach has been defined for provisioning certificates for use in either IPSec or TLS, the same techniques defined for provisioning TLS certificates are specified to be re-used here to provision certificates for use in securing the SSHv2 based M-Plane connection as specified in IETF RFC 6187 [31]. Hence, the TLS client CA issues certificates to NETCONF clients, irrespective of whether NETCONF is secured using TLS or SSHv2. Similarly, the TLS server CA issues certificates to NETCONF servers, irrespective of whether NETCONF is secured using TLS or SSHv2. The handling of certificates, including certificate profiles, shall follow the rules defined in ETSI TS 133 310 [51] for TLS CA certificates. In addition: • when an O-RU generates a certificate signing request it shall populate the Subject Distinguished Name field with a string that includes the O-RU manufacturer's name, model and serial number. The exact Subject DN sub-field used is defined in the operator of the CA/RA server's certificate policy. NOTE 2: In future, an O-RAN defined certificate policy may be defined to normalize the sub-field definition across the O-RAN ecosystem. NOTE 3: There are various characters that may not be permissible in the Subject Distinguished Name Field, e.g. ":" (colon, hexadecimal character 0x34), "." (period, hexadecimal character 0x2E), "_" (underscore, hexadecimal character 0x5F), "#" (hash, hexadecimal 0x23), "£" (pound, hexadecimal 0xa3), "*" (asterisk, hexadecimal 0x2a) or """ (double quote, hexadecimal 0x22). Manufacturers that include such characters in their name, model and/or serial number should ensure such characters are removed before including in the Subject Distinguished Name Field. • when transferring messages to the CA/RA server, the O-RU shall use the "port number of the CA/RA server" and the "path to the CA/RA directory" as signalled using the DHCP options as specified in clause 4.2.2 of ETSI TS 132 509 [52]. If no DHCP based configuration is received by an O-RU, the O-RU shall use the default port 443 and default directory "/pkix/". • The CA/RA server shall include the trust anchor for the operator issued certificate and the appropriate certificate chains in the initialization response message. • The O-RU shall store the operator issued certificate and corresponding certificate chain in reset persistent memory. When configured to operate with TLS, an O-RU that has a valid certificate issued by an operator PKI shall use this certificate to establish a mutually authenticated TLS connection for secure signalling with its O-RU Controller(s). |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.6.3 Operation with vendor-signed certificates | All O-RUs should be provisioned with a unique device vendor-signed certificate and its entire certificate chain up to the root. If the DHCP response does not contain CA/RA address information to allow certificate enrolment for O-RUs, or if an O-RU fails to enrol in an operator-PKI, as specified in clause 6.2.6.2, or the certificate issued during previous enrolment has expired, an O-RU configured to operate with TLS may use its vendor-signed certificate for setting up mTLS connections to its O-RU Controller(s), for example using the procedures specified in clause 6.2.5 to call home using NETCONF/TLS. Operators are then recommended to agree with the vendor on the life cycle management of these vendor-signed certificates, but life cycle management of Vendor Certificates is out of scope for the present document. NOTE: To achieve mTLS connections, the O-RU needs to be provided with necessary trust anchors from the operator, either through configuration in ietf-truststore YANG model, or using one of the options in clause 5.3.11 in [83]. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 41 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.6.4 Certificate lifecycle management | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.6.4.1 Introduction | An O-RU indicates its support for O-RAN defined certificate lifecycle management by including the ietf-keystore in its YANG library. Clause 6.2.6.4 applies to those O-RUs that support O-RAN defined certificate lifecycle management. The O-RU shall support the life cycle management of certificates as specified in ETSI TS 133 310 [51] clause 7.2, including the renewal of certificates using CMPv2 before their expiry. The O-RU takes the role of a Network Element (NE) when following this clause. The O-RU shall support configurations for setting the policy for certificates re-issuance using the cert-lcm-policy leaf defined in o-ran-certificates.yang. The defined policies are: • REISSUE_ON_DEMAND When configured with a cert-lcm-policy set to REISSUE_ON_DEMAND, the O-RU shall not autonomously initiate certificate re-issuance or re-key procedure. Instead, the O-RU Controller shall be responsible for triggering the initiation of the CMPv2 Certificate Request/Response procedure, as specified in clause 6.2.6.4.3. NOTE: When the certificates are re-issued, trust anchors can also be updated through provisioning as specified in clause 6.2.6.0. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.6.4.2 Void | NOTE: This clause is kept void for specifying autonomous rekeying or certificate re-issuance procedure from O-RU. These are not defined in the present document. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.6.4.3 On-demand certificate re-issuance | An O-RU controller wanting to trigger the re-issuance of a certificate to the O-RU shall configure the cert-lcm-policy to REISSUE_ON_DEMAND. The O-RU controller can trigger the issuance of a certificate by using the action statement <generate-csr> defined in IETF RFC 9642 [86]. After having responded with a rpc-reply <ok/>, an O-RU receiving the <generate-csr> shall recover the SubjectPublicKeyInfo from the csr-info and trigger the generation of a new key pair. After a new key pair has been generated, the O-RU shall use the csr-info, as specified in IETF RFC 2986 [87], to create a certificate signing request which it shall use in a CMPv2 certificate request exchange with the CA/RA server. The procedure is shown in Figure 6.2.6.4.3-1. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 42 Figure 6.2.6.4.3-1: On-demand certificate re-issuance ETSI ETSI TS 104 023 V17.1.0 (2026-01) 43 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.6.4.4 Certificate Life Cycle Notifications | The O-RU shall support configurations for "advance certificate about to expire notification timer" for different severities. The O-RU shall notify all the O-RU controller(s) that have subscribed to receive fault ID 39 specified in clause A.1 as follows: • With severity as minor minor-alarm-advance-time prior to expiry [units days, default: 30]; • With severity as major major-alarm-advance-time prior to expiry [units days, default: 10]; and • With severity as critical critical-alarm-advance-time prior to expiry [units days, default: 2]. The O-RU shall notify the subscribing O-RU controller(s) of certificate expiry using fault ID 40 as specified in clause A.1. After the O-RU successfully completes the CMPv2 process for certificate issuance, it shall notify all the subscribing O-RU controller(s) by sending a certificate-lcm notification. If the triggered certificate issuance process fails, the O-RU shall notify all the subscribing O-RU controller(s) using faults specified in clause A.1. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.2.7 Event-Collector discovery | This clause describes how an O-RU automatically discovers the Event-Collector to which it shall send its pnfRegistration notification. The support by an O-RU of PNF Registration to a discovered Event-Collector is optional and hence this clause only applies to those O-RUs that support this optional capability. O-RUs that have obtained their IPv6 addresses by stateless address auto-configuration, shall use stateless DHCPv6, as specified in IETF RFC 8415 [58], to obtain Event-Collector information. Other O-RUs operating using stateful IPv4 or IPv6 address allocations shall obtain Event-Collector information during IP address allocation. Other O-RUs which have had their IP address(es) manually configured, shall also have their Event-Collector(s) and Event-Collector Notification Format manually configured. The O-RU supporting PNF Registration shall be able to recover Event-Collector information using O-RAN defined vendor specific option to signal Event-Collector information to the O-RU using option 43 or option 125 for DHCPv4 and option 17 for DHCPv6. To achieve that, the O-RU shall request the option 43 or option 125 for DHCPv4 and option 17 for DHCPv6 as defined in clause 6.2.5. If the network provides an Event-Collector for the O-RU to send its pnfRegistration notification to, a DHCPv4 server shall respond with option 43 or option 125 if so requested, and a DHCPv6 server shall respond with option 17 if so requested. The definition of the types used within the DHCPv4 option 43 or option 125/DHCPv6 Option 17 are as follows: • Type: 0x83 - Event-Collector IP Address • Type: 0x84 - Event-Collector Fully Qualified Domain Name • Type: 0x85 - Event-Collector Notification Format In this version of the present document, the operation of an O-RU when receiving multiple instances of the Event-Collector IP Address and/or Event-Collector FQDN information is not defined. In all cases, the Type is followed by the length, which is the hexadecimal encoding of length of value field in octets, and the Value. When Type corresponds to an Event-Collector IP Address, the value encodes IPv4 address(es) in hexadecimal format. For example, an Event-Collector with IPv4 address 198.185.159.144 is encoded in an option 43 or option 125 TLV as: • Type 0x83 • Length: 0x04 • Value: C6 B9 9F 90 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 44 When Type corresponds to an Event-Collector Fully Qualified Domain Name, this encodes the string representation of domain name, using ACSII encoding (i.e. following for encoding used for the domain name in the Host Name DHCP Option 12). For example, a server with FQDN "collector.operator.com" is encoded in an option 43 or option 125 TLV as: • Type 0x84 • Length: 0x17 • Value: 63 6F 6C 6C 65 63 74 6F 72 2E 6F 70 65 72 61 74 6F 72 2E 63 6F 6D In this version of the present document, the operation of an O-RU when receiving an Event-Collector FQDN that is subsequently resolved by the O-RU to more than one IP address (i.e. returning multiple Address records) is not defined. The format of the DHCPv6 option 17 follows the format of the DHCPv4 encoding, with the additional inclusion of an Enterprise Number prior to the TLV option data. The IANA allocated private enterprise number to be used with DHCPv6 option 17 is 53148. When Type corresponds to an Event-Collector Notification Format, the value encodes in what format the Event-Collector expects to receive asynchronous notifications. In the present document, only a single format is defined: Value 00 - Event-Collector expects the notification to be signalled using the format as specified in the ONAP VES event listener specification [i.2]. For example, an Event-Collector expecting the pnfRegistration notification to be signalled using the ONAP defined format is encoded in the option 43 or option 125 TLV as: • Type 0x85 • Length: 0x01 • Value: 00 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.3 NETCONF call home to O-RU controller(s) | The O-RU aims to have NETCONF sessions with all of the call home O-RU Controller(s), either discovered using the DHCP options defined in clause 6.2.5, provisioned by an existing NETCONF client, or statically configured. An O-RU controller may attempt to autonomously initiate a NETCONF session with the O-RU, e.g. triggered by the pnfRegistration procedure. In order to support NETCONF clients corresponding to call home O-RU Controllers that either do not attempt to initiate a NETCONF session with the O-RU, or are prevented from doing so, e.g. because of Network Address Translation limitations, the O-RU shall call home to all call home O-RU Controller identities with which it does not already have an active NETCONF session. When the O-RU discovers, or is provisioned with, a call home O-RU Controller identity represented as an FQDN, the O-RU shall use DNS to resolve the IP address(es) of the FQDN identity. If as result of the resolution of the O-RU Controller FQDN to IP address, an O-RU receives multiple A and/or AAAA records, the O-RU should cycle through the received IP addresses in the A and/or AAAA records until it is able to establish a NETCONF session with a particular O-RU Controller identity. The O-RU should report the O-RU controller IP address used in the established NETCONF session in the client-info container in the o-ran-mplane-int YANG model. As a consequence, the O-RU is expected to have a single M-Plane session established per each O-RU controller's FQDN, regardless how many A/AAAA records were returned by the DNS server for each O-RU Controller FQDN. An O-RU that supports more than one network interface shall be able to perform O-RU Controller discovery on each of its network interfaces. If an O-RU recovers identical O-RU controller identity information on multiple network interfaces, then it should select which one out of the multiple interfaces to use for its call home operation. NOTE 1: The operation of an O-RU that discovers different O-RU Controller identities on separate network interfaces is not currently defined in the present document. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 45 If the O-RU is unable to establish a NETCONF session with some of the call home O-RU Controller identities, the O-RU shall use the re-call-home-no-ssh-timer to repeatedly re-perform the call home procedure to all call home O-RU Controller identities with which the O-RU does not have an established NETCONF session, cycling through the A and/or AAAA records until it is able to establish a NETCONF session with a particular call home O-RU Controller identity. The same value of timer shall be used, irrespective of whether SSH or TLS is being used to transport the NETCONF session. NOTE 2: The O-RU can cache the returned A/AAAA records for a period of time according to the DNS time to live. The setting of the DNS time to live is an operator name server configuration parameter. As an example, if an operator knows in advance of a change in the IP address(es) used by its O-RU controller(s), the operator can configure the name server with a minimum time to live value to ensure O-RUs request the new IP address(es) in a timely fashion. Name server configuration is outside the scope of the present document. If the O-RU is unable to trigger the establishment of NETCONF session with at least one call home O-RU Controller after having repeated the call home procedure a total of max-call-home-attempts per O-RU Controller, then the O-RU should perform an autonomous reset. The O-RU shall call home as specified in clause 4 of IETF RFC 8071 [15] whereby the O-RU (NETCONF Server) initiates a TCP connection to the NETCONF client. When calling home to the NETCONF clients in the container client-info, O-RU shall use the port manually configured during installation, and when calling home to the NETCONF clients in the container configured-client-info, O-RU shall use the port configured by other NETCONF Client. If no port was signalled or manually configured in the container client-info, or not configured in the container configured-client-info, O-RU shall use the port configured in call-home-ssh-port to indicate that the O-RU uses SSHv2 to secure the NETCONF connection and use the port configured in call-home-tls-port to indicate that the O-RU uses TLS to secure the NETCONF connection. If call-home-ssh-port does not exist, the O-RU shall use the IANA-assigned port 4334 to indicate that the O-RU uses SSHv2 to secure the NETCONF connection, and if call-home- tls-port does not exist, the O-RU shall use the IANA-assigned port 4335 to indicate that the O-RU uses TLS to secure the NETCONF connection. As illustrated in Figure 6.3-1, when the NETCONF client accepts a TCP connection on the allocated port, it initiates an SSH session/TLS connection with the NETCONF Server. Using this SSH session/TLS connection, the NETCONF client initiates a NETCONF session. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 46 Figure 6.3-1: Outline of NETCONF call home procedure ETSI ETSI TS 104 023 V17.1.0 (2026-01) 47 The O-RU shall ensure that a persistent connection to all call-home O-RU controllers is maintained by actively testing the aliveness of the connection. The O-RU should support TLS heartbeat/SSH using the keep-alive mechanism as specified in clause 4.1 of IETF RFC 8071 [15] and may support TCP keep-alive. The establishment of NETCONF client privileges is covered in clause 6.5. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.4 NETCONF connection establishment | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.4.0 General | The authentication mechanism and protocol to use are described in Table 5.4.1-1. The identity of the NETCONF server (O-RU) shall be verified and authenticated by the NETCONF client according to local policy for authentication described in Table 5.4.1-1 before password-based authentication data or any configuration or state data is sent to or received from the NETCONF server. When using SSHv2, public key-based host authentication shall be used for authenticating the server (IETF RFC 4253 [7]) by the clients. In addition, server authentication based on X.509 certificates may also be provided as specified in IETF RFC 6187 [31]. When using TLS, X.509 certificate-based authentication shall be used for mutual authentication between the NETCONF client and NETCONF server. NOTE: SSHv2 based public key-based host authentication requires that the SSH server (O-RU) public keys are provisioned in the NETCONF client (e.g. O-DU and/or SMO). As an alternative, IETF RFC 4251 [79] mentions that "a possible strategy is to only accept a host key without checking the first time a host is connected, save the key in a local database, and compare against that key on all future connections to that host". This option simplifies the key management procedure as it does not require to pre-populate them in O-DU/SMO (SSH client) but obviously at the price of degraded security, therefore the support of this option is configurable and left to operator's choice. In case the O-RU is not configured to perform certificate enrolment, or enrolment failed the O-RU may use its unique device vendor-signed certificate. The first NETCONF session during start-up installation using the default NETCONF account will in this case be authenticated by the O-RU controller but not by the O-RU, unless the O-RU has been provisioned with trust anchors using one of the options in clause 5.3.11 in [83]. If an O-RU is not configured with a valid, non-manufacturer trust anchor, the O-RU may skip the verification of the client certificate exchanged during the mTLS handshake. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.4.1 NETCONF security | As specified in clause 5.4, this version of the O-RU Management Plane Specification uses TLS 1.2, TLS 1.3, or SSHv2 for mutual authentication between the NETCONF server (O-RU) and the NETCONF client (O-DU or SMO). If multiple NETCONF sessions are established to an O-RU, those sessions shall be established over separate SSH tunnels/TLS connections. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.4.2 NETCONF authentication | The authentication mechanism and protocol to use are described in clause 5.4. This version of the O-RU Management Plane Specification supports SSHv2 using password authentication method for SSHv2 as specified in clause 8 of IETF RFC 4252 [6] and client authentication based on X.509 certificates as specified in IETF RFC 6187 [31], and TLS 1.2, or TLS 1.3, using X.509 certificate-based authentication. The identity of the NETCONF server (O-RU) shall be verified and authenticated by the NETCONF client (O-DU or SMO) according to local policy for authentication described in Table 5.4.1-1 before authentication data or any configuration or state data is sent to or received from the server. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 48 The identity of the NETCONF client (O-DU or SMO) shall be verified and authenticated by the NETCONF server (O-RU) according to local policy for authentication described in Table 5.4.1-1 to ensure that the incoming NETCONF client request is legitimate before any configuration or state data is sent to or received from the NETCONF client. The server shall also perform proper authorization of the client before accepting any request. If authentication is based on X.509 certificates, for the purposes of user authentication, the mapping between certificates and user-name is provided by the subjectAltName field of the X.509 certificate, which means that the user name is coded in the subjectAltName. The username is determined from the subjectAltName using the rules as specified in IETF RFC 7589 [41]. For the purposes of NETCONF server authentication, IETF RFC 7589 [41] specifies server identity as specified in clause 4 of IETF RFC 9525 [84]. Upon initial system initialization, the O-RU is configured with a default account. The specific details of the default account are to be agreed between operator and vendor. An example of a default user account for account-type PASSWORD is one with username "oranuser". An example of a default user account for account-type CERTIFICATE is map type "san-rfc822-name" with an rfc822-name of "oranuser@o-ran.org". An example of a default user account for account-type SSHPUBLICKEY is "oranuser". The default account may be of account-type PASSWORD, in which case a default password needs to be defined and configured in the O-RU, for example "o-ran-password". The default account may be of account-type SSHPUBLICKEY, in which case the default public key and associated algorithm need to be configured in the O-RU. As the default account may be operator specific, this may require that the O-RU provides facilities to configure securely this default account and cert-to-name mapping list at installation time (i.e. before the O-RU is connected to the O-RU Controller). NOTE: The account-type SSHPUBLICKEY was first defined in v16.01 of the present document. The support for a default account type SSHPUBLICKEY can be agreed between operator and vendor, depending upon O-RU controller capabilities. If user authentication is based on X.509v3 certificate during O-RU plug and play, to support zero touch for the first NETCONF connection, the O-RU shall support the default mapping between certificate and default NETCONF account which maps any authenticated X.509 v3 certificate to this default O-RAN account. The trust anchor for O-RU shall be provisioned automatically with online CA server during O-RU Plug and Play, and it shall be same as the trust anchor of the O-RU Controller(s), thus avoiding the need for manual configuration of the peer trust anchor for O-RU. The default account is a member of the "sudo" privilege group (see clause 6.5 for details of groups/privileges) as it is intended to be used to create other accounts, as specified in clause 6.4.3. As the default account credential may be common across different deployments of a vendor's equipment, it is strongly recommended to only use the default account to create other operator specific user accounts on the O-RU. Clause 6.4.3.1 specifies the conditions whereby the creation of a NETCONF server account triggers the automatic disabling of the default account. The operator and vendor shall agree how the default account can be determined by a NETCONF client operating in a multi-vendor O-RU environment based on the SSH response message sent by the O-RU. It is recommended that the vendor and operator agree on a particular format of the "SSH-protoversion-softwareversion SP comments CR LF" identification string, as defined in IETF RFC 4253 [7] clause 4.2, used by the SSH Server in the O-RU to identify the O-RU vendor and consequently the default account to be used by the NETCONF client. Upon initial system initialization, the NETCONF client can authenticate itself to the O-RU using SSH Authentication either with the agreed default username and password or with simple public key. If authentication based on X.509 certificates according to [31] is supported by SSH and TLS client and server, the certificates need to be installed at initial system initialization, or can be obtained through certificate enrolment with operator's PKI (certificate enrolment as defined by 3GPP with CMPv2 protocol between the NE and the operator's CA). After having enrolled in an Operator PKI, when establishing a new TLS session using X.509 certificate-based authentication, the O-RU shall select a valid certificate issued by the operator PKI with the longest time to its expiration. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 49 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.4.3 User account provisioning | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.4.3.1 General | The NETCONF client with suitable privileges may provision user accounts on the O-RU, including the accounts (users) name, password, group (see clause 6.5 for details of groups/privileges) and whether a particular account is enabled or disabled. The provisioning of new accounts is typically performed once during pre-staging, as described in step 14 of Figure 6.1-1. • The name for the user is a string which should be between 3-32 characters. For account-type PASSWORD, the first character should be a lowercase letter. The remaining characters should be lowercase letters or numbers. For account-type CERTIFICATE or SSHPUBLICKEY, the characters should be lowercase letters, numbers, periods (ASCII code 0x2E) or @ sign (ASCII code 0x40). • The account-type is an enumeration, indicating authentication method such as password, certificate, or simple public key. • The password is a string between 8-128 characters. Allowed characters in the password field include lowercase and uppercase letters, numbers and the special characters: ! $ % ^ ( ) _ + ~ { } [ ]. The password leaf is present only for those user accounts associated with password-based authentication. • Whether an account is enabled. The YANG model ensures that at least one user account is always enabled on the O-RU. • When the O-RU supports the SHARED-ORU-MULTI-OPERATOR feature, the user account may be associated with zero or more Shared Resource Operator IDs (sro-id). Clause 19 describes the operation of the SHARED-ORU-MULTI-OPERATOR feature in more detail. When an sro-id is configured with a user account with "carrier" group/role privileges, the multi-operator shared O-RU feature is enabled. The new account information (user name, password, optional sro-id, account-type and whether the account is enabled) shall be stored in reset-persistent memory in O-RU. Each account name in o-ran-usermgmt YANG model is identical to the user-name used in ietf-netconf-acm YANG model. User account provisioning shall include using the ietf-netconf-acm module to define which groups are associated with a particular user-name (see clause 6.5 for details of groups/privileges). The definition of a privilege group or set of privilege groups referred to by name(s) is(are) intended to match deployment scenarios. For example, the group name "sudo" is intended to be used when configured as a NACM group for a user-name associated with the NECTONF client of a hierarchical O-DU. Conversely, the group name "hybrid-odu" is intended to be used when configured as a NACM group for a user-name associated with the NECTONF client of a hybrid O-DU. For client authentication based on certificate or Simple Public Key, no password needs to be provisioned. For certificate based authentication, at time of SSH or TLS connection, user's authorization is done based on the X.509 certificate's SubjectAltName field that codes the associated account's name. When a NETCONF client using the default account is used to successfully commit the configuration for another user account with account privileges "sudo", the NETCONF client should close existing NETCONF session as described in clause 6.8. Then, the O-RU disables the default account and default account stays disabled over the resets. The default account becomes enabled when the O-RU is reset to the factory default software by following the procedures defined in clause 8.8. Any other way to enable the default account is not precluded as O-RU vendor implementation matter. NOTE 1: Configuring a new user account with "sudo" privileges enables that account to have full permissions over the o-ran-usermgmt.yang model which then permits that account to create other user accounts on the O-RU's NETCONF server. The security principle defined in this clause shall follow those defined for the default account and default mapping, i.e. the O-RU Controller shall create a new mapping. NOTE 2: Depending on the EE/CA certificate of the O-RU Controller, the map type can still be specified but with specific fingerprint of the EE/CA certificate or based on SubjectAltName of EE/CA certificate as specified in clause 6.4.2. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 50 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.4.3.2 Certificates to NETCONF usernames mapping list provisioning | The O-RU controller with suitable privileges may provision list cert-to-name to define how certificates are mapped to NETCONF usernames at the O-RU using o-ran-certificates.yang. This list shall be stored in reset persistent memory. Each entry of the mapping list contains a certificate fingerprint, a map-type and optional username. • The certificate fingerprint is a digest of NETCONF client End-Entry (EE) certificate or a digest of a trusted Certificate Authority (CA) which is part of the CA certificate chain of the NETCONF client EE certificate in X.509 binary format. From security consideration, it is recommended to use EE certificate fingerprint instead of CA certificate fingerprint. • The map-type indicates how the NETCONF username associated with the certificate should be determined. O-RU shall support map-types A and B defined in section 7 of IETF RFC 7589 [41]. Support for other map-types is optional. Support for map-type F, "common-name", is deprecated. • The username name is a NETCONF account's name which is specified only when map-type is 'specified'. In case a X.509v3 certificate that is used for client authentication is updated e.g. due to it being close to expiry, the O-RU controller shall update the X.509v3 certificate and if necessary re-provision the cert-to-name entry to O-RU Configuration using o-ran-certificates.yang. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.5 NETCONF access control | This clause defines the access control for NETCONF clients. Its motivation is that when multiple NETCONF clients (users) are defined, the NETCONF access control mechanism enables the NETCONF server to limit some operations for one client but allow full access for another client. In particular, for hybrid access configuration as introduced in clause 5, this allows the privileges associated with the NETCONF client in the hybrid O-DU to be distinct and different from the privileges associated with the NETCONF client in the SMO. In order to support interoperable access control management, the NETCONF Server shall use the IETF NETCONF Access Control Model as specified in IETF RFC 8341 [64]. Currently seven access control groups corresponding to different NETCONF client roles are defined and can be mapped to the user-name for a NETCONF session: "sudo", "smo", "hybrid-odu", "carrier", "nms", "fm-pm", and "swm". Table 6.5-1 maps the group/role name to different privileges. Privileges are defined per namespace for read "R", write "W" and execute "X" where "X" indicates access privilege to use RPC operations or to subscribe to Notifications. The NACM module is used to store the association between the groups and user-names and enables a user-name to be associated with multiple different groups. The configuration of the NACM module shall be stored in reset-persistent memory in O-RU. During access control procedure, groups associated to the user are determined based on user-name that an O-RU controller provided or derived from O-RU controller's certificate. The user's access privileges are the combination (union) of the privileges associated with those groups. Refer to Table 6.5-1 for privilege details. O-RU shall support access control enforcement procedure defined in IETF RFC 8341 [64] clause 3.4. The NETCONF client in the hybrid O-DU should be associated with the "hybrid-odu" privilege group and the NETCONF client in the SMO should be associated with the "smo" privilege group. A NECTONF client can perform read operations on the o-ran-usermgmt and ietf-netconf-acm YANG models to determine the group privileges its NETCONF account has been granted. When operating with a NETCONF client with user name user-list entry containing a configured sro-id and with "carrier" privileges, e.g. a client operated by a Shared Resource Operator, a Multi-Operator O-RU shall have its read, write and execute privileges for certain models further refined based on the sro-id associated with the name of the NETCONF client as configured using the o-ran-usermgmt YANG model. Further details are described in clause 19. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 51 Table 6.5-1: Mapping of account groupings to O-RU module privileges Module Rules sudo nms fm-pm swm smo hybrid- odu carrier "urn:o-ran:supervision:x.y" RWX --- --- --- RW- (note 4) RWX R-X "urn:o-ran:hardware:x.y" RWX RW- --- --- RWX R-- R-- "urn:ietf:params:xml:ns:yang:ietf- hardware" RWX RWX R-X --- RWX R-X R-X "urn:o-ran:user-mgmt:x.y" RWX (note 1) --X (note 8) --X (note 8) --X (note 8) RWX (note 1) RWX (note 1) --X (notes 7 and 8) "urn:o-ran:fm: x.y " R-X R-X R-X --- R-X R-X R-X "urn:o-ran:fan: x.y " R-- R-- R-- --- R-- R-- R-- "urn:o-ran:sync: x.y " RWX RWX R-- --- RWX R-X R-X "urn:o-ran:delay: x.y " RW- R-- R-- --- R-- RW- R-- "urn:o-ran:module-cap: x.y " RW- R-- R-- --- R-- RW- R-- "urn:o-ran:udpecho: x.y " RW- R-- --- --- RW- R-- R-- "urn:o-ran:operations: x.y " RWX RW- R-- --- RWX RWX R-X (note 10) "urn:o-ran:uplane-conf: x.y " RWX RWX R-- --- R-- RWX RWX (note 6) "urn:o-ran:beamforming: x.y" R-X R-X R-- --- R-- R-X R-- "urn:o-ran:lbm: x.y " RW- RW- R-- --- RW- R-- R-- "urn:o-ran:software-management: x.y " R-X R-X R-- R-X R-X R-- R-- "urn:o-ran:file-management: x.y " R-X R-X R-X --- R-X --- --- " urn:o-ran:message5: x.y " RW- R-- R-- --- R-- RW- R— (note 6) "urn:o-ran:performance-management: x.y " RWX RWX RWX --- RWX R-X R-X (note 6) "urn:o-ran:transceiver: x.y " RW- RW- R-- --- RW- R-- R-- "urn:o-ran:externalio: x.y " RWX RWX --- --- RWX R-- R-- "urn:o-ran:ald-port: x.y " RWX RWX --- --- RWX (note 3) RWX --- "urn:o-ran:interfaces: x.y " RWX RWX R-- --- RWX R-- R-- "urn:ietf:params:xml:ns:yang:ietf-ip" RW- RW- R-- --- RW- R-- R-- "urn:ietf:params:xml:ns:yang:ietf- interfaces" RW- RW- R-- --- RW- R-- R-- "urn:o-ran:processing-elements: x.y " RW- RW- R-- --- RW- RW- R-- (note 6) " urn:o-ran:mplane-interfaces: x.y " RW- RW- (note 2) R-- --- RW- R-- R-- "urn:o-ran:dhcp: x.y " R-- R-- R-- --- R-- R-- R-- "urn:o-ran:ald: x.y" --X --- --- --- --X (note 3) --X --- "urn:o-ran:troubleshooting: x.y" R-X R-X R-X --- R-X --- --- " urn:o-ran:trace: x.y" R-X R-X R-X --- R-X --- --- "urn:o-ran:laa: x.y " RW- RW- --- --- R-- RW- R-- "urn:o-ran:laa-operations: x.y " R-X --- --- --- --- R-X --- "urn:o-ran:antcal: x.y " RWX R-- --- --- R-- RWX R-X "urn:ietf:params:xml:ns:yang:ietf- netconf-acm" RW- R-- R-- R-- RW- RW- R-- "urn:ietf:params:xml:ns:yang:ietf-yang- library" R-X R-X R-X R-X R-X R-X R-X "urn:ietf:params:xml:ns:yang:ietf- netconf-monitoring" R-X R-X R-X R-X R-X R-X R-X "urn:ietf:params:xml:ns:yang:ietf- netconf-notifications" R-X R-X R-X R-X R-X R-X R-X "urn:o-ran:shared-cell:x.y" RW- RW- --- --- R-- RW- R-- (note 6) "urn:o-ran:ethernet-fwd:x.y" RW- RW- --- --- RW- R-- R-- "urn:ietf:params:xml:ns:yang:ietf- subscribed-notifications" --- --- --- --- RWX --- --- "urn:o-ran:ves-sn:x.y" --- --- --- --- RW- --- --- "urn:ieee:std:802.1X:yang:ieee802- dot1x" RW- RW- R-- --- RW- R-- R-- ETSI ETSI TS 104 023 V17.1.0 (2026-01) 52 Module Rules sudo nms fm-pm swm smo hybrid- odu carrier "urn:ieee:std:802.1X:yang:ieee802- dot1x-eapol" RW- RW- R-- --- RW- R-- R-- "urn:ieee:std:802.1Q:yang:ieee802- dot1q-cfm" RW- RW- R-- --- RW- R-- R-- "urn:o-ran:o-ran-ieee802-dot1q-cfm" RW- RW- R-- --- RW- R-- R-- "urn:ietf:params:xml:ns:yang:ietf-system" RW- (note 5) RW- (note 5) R— (note 5) --- RW- (note 5) R-- (note 5) R— (note 6) "urn:ietf:params:xml:ns:yang:ietf- truststore" RW- R-- --- --- RW- R-- R-- "urn:ietf:params:xml:ns:yang:ietf- keystore" R-X (note 11) R-X (note 11) --- --- R-X (note 11) R-X (note 11) R-- (note 11) "urn:o-ran:certificates:x.y" RW- --- --- --- RW- RW- --- "urn:o-ran:frequency-band- measurement:x.y" R-X R-- --- --- R-X R-X --- NOTE 1: The rule list for "urn:o-ran:user-mgmt:1.0" shall additionally deny reading of the password leaf by any NETCONF client. NOTE 2: The rule list for "urn:o-ran:mplane-int:1.0" shall additionally deny the writing of the configured-client-info container for NETCONF sessions with "nms" group privileges. NOTE 3: While the rule list for models related to Antenna Line Devices (ALD) permit SMO configuration privileges, the operation of the current architecture, including requiring the use of regular NETCONF RPCs to tunnel heartbeat messages to the ALD, may limit the scalability of scenarios where the SMO is providing for the ALD Controller function described in clause 14.4. NOTE 4: The rule list for "urn:o-ran:supervision:x.y" shall additionally deny writing of the cu-plane-monitoring container for NETCONF sessions with "smo" group privileges. NOTE 5: The rule list for "urn:ietf:params:xml:ns:yang:ietf-system" shall additionally deny write access to the clock container and the authentication container and deny read access to the system-state container for all group privileges. NOTE 6: Clause 19 describes further details of how carrier privileges are refined based on sro-id for O-RUs that support the SHARED-ORU-MULTI-OPERATOR feature. NOTE 7: The carrier rule list prohibits read and write to o-ran-usermgmt YANG model, but allows access to the sro-id leaf instance defined in o-ran-usermgmt from different data structures by reference. NOTE 8: Execution access privilege applies to chg-password RPC only. NOTE 9: Void. NOTE 10: Execution access privilege applies to subscription for the notification emergency-wake-up-complete and notification deep-hibernate-activated only. Privilege to execute the deep-hibernate RPC shall be denied. NOTE 11: The present document only supports CMPv2 as the method to issue a certificate. An O-RU controller can use the ietf-keystore model to read the installed certificate(s) and/or trigger the generation of a certificate signing request. The O-RU shall encode the mappings defined in Table 6.5-1 in the rule list in ietf-netconf-acm.yang model. Only Multi-Operator O-RUs are required to support the "carrier" privilege group. The sudo access control group shall be supported by all O-RUs. This rule list shall be unmodifiable by any NETCONF client. O-RU shall use the same model for configuring the mapping between different user-names and groups. NOTE: The operation of an O-RU when using other vendor defined pre-configured groups is not defined in the present document. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.6 NETCONF capability discovery | The O-RU shall advertise its NETCONF capabilities in the NETCONF Hello message. The Hello message sent by the O-RU shall include the <session-id> element containing the session ID for the NETCONF session and shall provide an indication of support for standard features defined in NETCONF RFCs as well as support for specific namespaces. NETCONF capabilities are exchanged between the O-RU and the NETCONF client(s). Examples of capabilities are specified in clause 8 of IETF RFC 6241 [3] and include the following capability items: • Writable-running Capability • Candidate Configuration Capability and associated Commit operation • Discard change operation ETSI ETSI TS 104 023 V17.1.0 (2026-01) 53 • Lock and un-lock operations • Confirmed commit Capability • Cancel commit operation • Rollback on error capability • Validate Capability • Startup configuration capability • URL capability • XPATH capability • Notifications • Interleave capability O-RUs shall support the "XPATH capability". O-RUs shall support "Notifications": • O-RUs shall support subscribing to receive event notifications, as specified in clause 2 of IETF RFC 5277 [21]. • O-RUs may support dynamic subscriptions to receive event notifications, as specified in clause 2.4 or IETF RFC 8639 [37]. The use of <create-subscription> RPC in the present document can be understood as being equivalent to the <establish-subscription> RPC for those NETCONF servers and NETCONF clients that support dynamic subscriptions as specified in IETF RFC 8639 [37]. O-RUs shall support at least one of the following capabilities: • "writable-running capability" • "candidate configuration capability and associated Commit operation". In addition, an O-RU that supports "writable-running capability" should support the "rollback on error capability" and an O-RU that supports "candidate configuration capability and associated Commit operation" should support the "confirmed commit capability". The NETCONF client uses the get RPC together with sub-tree based <filter> and XPATH based <filter> to recover particular sub-trees from the O-RU. See clause 9 for more information on NETCONF based configuration management. In order to avoid interactions between the operation of supervision watchdog timer (see clause 6.7) and the confirmed commit timer (default value set to 600 seconds in IETF RFC 6241 [3]), when using the NETCONF confirmed commit capability, a NETCONF client with "sudo" privileges shall ensure the confirmed-timeout is less than the supervision-notification-interval timer (default value 60 seconds in o-ran-supervision.yang). |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.7 Monitoring NETCONF connectivity | This clause provides description of NETCONF connectivity monitoring for persistent NETCONF session. Additional procedures for O-RUs that support the optional NON-PERSISTENT-MPLANE feature to monitor the communication path between the O-RU and Event-Collector are defined in clause 18.6. When having a session with a NETCONF client that has subscribed to receive the supervision-notification, the O-RU operates watchdog timers (supervision timer and notification timer) to ensure that the session to the NETCONF client is persistent, as illustrated in Figure 6.7-1. The O-RU provides NETCONF Notifications to indicate to remote systems that its management system is operational. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 54 For the O-RU that supports feature SUPERVISION-WITH-SESSION-ID, these supervision-notification messages shall also indicate the NETCONF session-id associated with the subscription to the event notification. When subscribing to receive the supervision-notification, a NETCONF client may use its own NETCONF session-id in the subscription filter criteria to indicate to the O-RU which supervision-notification events the O-RU shall forward to the NETCONF client. The session-id is provided by the NETCONF server to the NETCONF client in the initial Hello exchange, see clause 6.6. An O-RU controller that has subscribed to the supervision-notification is expected to use the <supervision-watchdog- reset> RPC to indicate to O-RU the O-RU controller is operational. NOTE 1: This supervision is intended to be used with the NETCONF client associated with the operation of the peer to the O-RU's lower layer split and clause 6.5 describes which NETCONF clients have privileges to subscribe to the supervision-notification. A NETCONF server shall support the operation of individual supervision watchdog timers for each NETCONF client which has subscribed to supervision-notification. The privileged NETCONF client may enable the operation of the watchdog timers by creating supervision-notification subscription. After operation of watchdog timers is enabled - the timers are considered as running. The O-RU uses two timers, referred generically as watchdog timers, to support the bi-directional monitoring of NETCONF connectivity: • Notification timer: - Value: Equal to supervision-notification-interval (default value: 60s) - Operation: The O-RU sends supervision-notification to those NETCONF clients that have subscribed to receive such notifications. The O-RU sends supervision-notification, at the latest when the timer expires. The O-RU Controller confirms that NETCONF connectivity to the O-RU is operational by receiving the notification. • Supervision timer: - Value : Equal to supervision-notification-interval (default value: 60s) + guard-timer-overhead (default value: 10s) - Operation: The O-RU identifies supervision failure operation when the timer expires. To avoid supervision timer expiration, a NETCONF client who has subscribed to receive the supervision-notification should repeatedly reset this supervision timer. Such supervision timer reset is considered by O-RU as confirmation that NETCONF connectivity to the O-RU Controller is operational. The O-RU enables dedicated watchdog timers for specific NETCONF client when it receives a <create-subscription> RPC from a NETCONF client with required privileges. The notification timer shall be started when the O-RU receives a <create-subscription> RPC, but how the O-RU treats the supervision timer is up to O-RU's implementation based on the above definition. After the watchdog timers have been enabled, the O-RU shall send supervision-notification after the expiry of the notification timer. An O-RU Controller who has subscribed to the supervision-notification shall be prepared to receive the notification at any time when the watchdog timers are running. A NETCONF client that has triggered operation of watchdog supervision by using the <establish-subscription> RPC to subscribe to the supervision-notification may cancel the subscription by using the <delete-subscription> RPC, as specified in clause 9.1.7.3. An O-RU receiving a <delete-subscription> RPC from a NETCONF client for an existing supervision-notification shall cease operation of the watchdog supervision with that NETCONF client. NOTE 2: In case there are active carriers and watchdog supervision is active, it is not recommended to delete the subscription to the supervision-notification. The NETCONF client should send supervision-watchdog-reset RPC in order not to cause the Supervision timer to expire, and the O-RU should send next notification timestamp as next-update-at in reply. NOTE 3: next-update-at is just informative. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 55 In the supervision-watchdog-reset RPC, the NETCONF client may configure new values for the watchdog timers using RPC parameters "supervision-notification-interval" and "guard-timer-overhead. When the O-RU receives the supervision-watchdog-reset RPC, it shall reset its supervision timer and notification timer. When the watchdog timers are running, the O-RU shall be prepared to receive supervision-watchdog-reset RPC at any time - also within supervision timer period. The NETCONF client can set new value of watchdog timers without receiving supervision-notification from the O-RU. The new values are taken into use immediately with respect to supervision-watchdog-reset RPC content. The next notification should be expected not later than at the moment addressed in timestamp provided by RPC reply. If another NETCONF client has locked the running configuration, e.g. when operating in hybrid mode of operation, and if the O-RU Controller attempts to configure a new value of the watchdog timer(s) by sending the supervision-watchdog-reset RPC, then the RPC operation to reset the watchdog timer will succeed, but the related backend implementation to modify the watchdog timer(s) may fail. In such circumstances, the O-RU may use the error-message in the RPC output to indicate to the O-RU Controller that the configuration modification has failed. If the supervision timer expires, the O-RU shall enter "supervision failure" condition, as described in clause 14. If all NETCONF sessions to NETCONF clients with "sudo" privileges are closed, the O-RU shall immediately disable operation of the supervision timer. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 56 Figure 6.7-1: Monitoring NETCONF Connectivity NOTE 4: A NETCONF client can use the create-subscription for the single supervision-notification event stream, or alternatively subscribe to the default event-stream using additional filter criteria to identify the supervision notification. In order to subscribe to multiple notifications, the appropriate create-subscription message is required. Refer to clause 11.3 for the appropriate example of create-subscription of multiple notifications. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 57 Figure 6.7-1 illustrates the O-RU ceasing supervision operation triggered by two options: 1) The supervision timer expires. In such case the O-RU performs Supervision Failure handling as described in clause 14.1.1. 2) The NETCONF client terminates the subscription to the supervision-notification. The NETCONF client can either close the subscription session, terminate the NETCONF session or wait for the subscription stop time to be reached. In such case the O-RU performs Supervision Termination handling as described in clause 14.1.2. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.8 Closing a NETCONF session | A NETCONF client closes an existing NETCONF session by issuing the RPC close-session command. The O-RU shall respond and close the SSH session or TLS connection. If the NETCONF client is a Call home O-RU controller, the O-RU shall then re-commence call home procedures, as described in clause 6.3. In case the O-RU is operating in deep-hibernate mode and the hibernate-time timer is operational, as specified in clause 20.5, the O-RU shall suspend call home procedures. Under normal operations, it is expected that at least one NETCONF session with "sudo" or "hybrid-odu" privileges are long-lived and used to repeatedly reset the O-RU's supervision watchdog timer for the NETCONF session. NETCONF clients associated with other privilege groups are not required to operate using persistent NETCONF sessions. If a NETCONF client has been previously become known to an O-RU by being configured using NETCONF, and the NETCONF client is subsequently removed from the O-RU's configuration, e.g. by a second NETCONF client with "sudo" privileges, the NETCONF server shall force the termination of the NETCONF session to the removed client. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.9 PNF registration | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.9.1 Introduction | The support by an O-RU of PNF Registration to a discovered Event-Collector is optional and hence clause 6.9 only applies to those O-RUs that support this optional capability. An O-RU that support pnfRegistration shall also support the Monitoring the Communications Channel between O-RU and Event-Collector as defined in clause 18.6. In case the O-RU is operating in in deep-hibernate mode and the hibernate-time timer is operational, as specified in clause 20.5, the O-RU shall suspend PNF Registration procedures. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.9.2 PNF registration procedure | The pnfRegistration notification is a JSON encoded message sent from the O-RU to the discovered Event-Collector using REST/HTTPS. As a pre-condition to performing PNF Registration, the O-RU first receives the Event-Collector information encoded in a DHCP/DHCPv6 option as described in clause 6.2.7. The O-RU shall attempt to establish a HTTP connection to the discovered Event-Collector using TLS to authenticate the connection. It shall then signal the pnfRegistration notification over the HTTP/TLS connection. The sending of the pnfRegistration notification is repeated periodically until the SMO establishes a NETCONF session with the O-RU. These procedures are illustrated in Figure 6.9.2-1. An O-RU that is performing the PNF registration procedure whilst simultaneously performing the call home procedure described in clause 6.3, shall be able to determine that the SMO has established a NETCONF session with the O-RU. This is identified by the O-RU analysing the source IP address from which the NETCONF originates, based on the assumption that the NETCONF session from the SMO originates from an IP address that is distinct from the IP address(es) of the call home O-RU Controller(s) to which the O-RU is simultaneously performing the call home procedure. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 58 Figure 6.9.2-1: PNF Registration Procedure |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.9.3 Encoding of PNF registration notification | In the present document, the encoding of the pnfRegistration notification follows the ONAP definition [i.2]. The pnfRegistration notification shall include the IP address information necessary for a NETCONF client to establish IP connectivity to the NETCONF Server in the O-RU. The contents of the pnfRegistration notification are derived from the O-RU's configuration database using Table 6.9.3-1. An O-RU shall support the o-ran-hardware.yang model revision 5.0.0, or later, which defines the schema nodes corresponding to unitFamily and unitType values and the o-ran-operations.yang model revision 5.0.0, or later, which defines the schema nodes corresponding to the version of pnfRegistration fields. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 59 Table 6.9.3-1: Mapping from O-RU's Operational Data to PnfRegistration fields PnfRegistration Notification Field YANG Operational Data O-RU pnfRegistration requirements lastServiceDate /hw:hardware/hw:component/or-hw:last-service- date The O-RU may include the lastServiceDate field macAddress /if:interfaces/if:interface/o-ran-int:mac-address The O-RU may include the macAddress field manufactureDate /hw:hardware/hw:component/hw:mfg-date The O-RU may include the manufactureDate field modelNumber /hw:hardware/hw:component/hw:model-name The O-RU shall include the modelNumber field oamV4IpAddress /if:interfaces/if:interface/ip:ipv4/ip:address/ip:ip When the O-RU has IPv4 address assigned for management plane (as specified in clause 6.2.4), it shall include the oamV4IpAddress field (note) oamV6IpAddress /if:interfaces/if:interface/ip:ipv6/ip:address/ip:ip When the O-RU has IPv6 address assigned for management plane (as specified in clause 6.2.4), it shall include the oamV6IpAddress field (note) pnfRegistrationFields Version /o-ran-ops:operational-info/o-ran- ops:declarations/o-ran-ops:supported-pnf- registration-fields-version The O-RU shall include the pnfRegistrationFieldsVersion field serialNumber /hw:hardware/hw:component/hw:serial-num The O-RU shall include the serialNumber field softwareVersion /hw:hardware/hw:component/hw:software-rev The O-RU shall include the softwareVersion field vendorName /hw:hardware/hw:component/hw:mfg-name The O-RU shall include the vendorName field NOTE: The PNF registration operation of an O-RU that uses o-ran-mplane-int YANG model to report multiple m-plane-sub-interfaces list entries of the same IP address type is not defined in the present document. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 6.10 On-demand renewal of Call Home procedure | The O-RU that exposes presence of feature CALL-HOME-REACTIVATION-SUPPORTED can be triggered to re-activate timed out call-home procedure towards call home O-RU controllers. The RPC <restart-call-home> sent by any active O-RU controller having necessary permissions causes O-RU to re-start call home towards all not actively connected call home O-RU controllers as described in clause 6.3. Once restarted, the call home flows are continued until M-Plane session with lost call home O-RU controller(s) is successfully re-established or until counter max-call-home-attempts is exhausted. For every call home O-RU controller for which supervision is recovered in(as) result of RPC <restart-call-home>, the O-RU cancels alarm 35 "Lost O-DU ID based Supervision" when supervision is successfully recovered This RPC has no impact on O-RU operations with call home controllers that have M-Plane session established with O-RU. In case O-RU is performing call home procedure towards call home O-RU controller, the RPC triggers the O-RU to re-initialize its internal counter based on value of node max-call-home-attempts and continues call home procedure. 6.11 TLS sessions and certificate expiry After a certificate has been re-issued, an O-RU may continue to use M-Plane sessions (e.g. NETCONF, FTPeS) authenticated using a previously issued, un-expired certificate. New M-Plane sessions shall use the certificate with the longest time to expiration, as described in clause 6.4.2. After having received a notification that an O-RU has been re-issued a certificate by the Operator PKI, an O-RU controller should schedule the closing of existing NETCONF session by issuing the RPC close-session command following the procedure specified in clause 6.8. NOTE 1: The timing of the scheduled session closing can be arranged to minimize any service impacting effects. NOTE 2: The operation of the O-RU when the certificate used to authenticate an on-going M-Plane session expires is not defined. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 60 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7 O-RU to O-DU interface management | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.1 O-RU interfaces | An O-RU has a number of network interfaces, including Ethernet, VLAN and IP interfaces. This clause describes the management of these network interfaces. The O-RU's configuration for its interfaces is defined using the o-ran-interfaces.yang module. This module augments the standard ietf-interfaces.yang and ietf-ip.yang modules. The O-RU's interfaces are built on a layering principle where each interface has a unique name. All interfaces are referenced by their port-number and name. The base interface corresponds to the Ethernet interface. These leafs describe the maximum transmission unit (l2-mtu), the hardware-address as well as optional alias mac addressees that may be used to transport the CU plane. An O-RU can indicate the maximum Ethernet payload size per O-RU Ethernet interface it supports by using the maximum-ethernet-payload-size leaf. The O-RU shall reject any configuration where the Ethernet payload configured using l2-mtu for an Ethernet interface exceeds the value of maximum-ethernet-payload-size. NOTE 1: If an O-RU does not indicate a value of maximum-ethernet-payload-size in its operational state, the operator and O-RU vendor can agree on a maximum Ethernet frame size. NOTE 2: The definition of the read-only maximum-ethernet-payload-size is different from the l2-mtu definition. The description in the YANG model defines how to map between the two and Figure 7.1-0a illustrates an example subset of configuration and operational data. <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> <interface> <name>10Geth0</name> <type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:ethernetCsmacd</type> <enabled>true</enabled> <l2-mtu xmlns="urn:o-ran:interfaces:1.0"> 9014 </l2-mtu> <maximum-ethernet-payload-size xmlns="urn:o-ran:interfaces:1.0"> 9000 </maximum-ethernet-payload-size> <vlan-tagging xmlns="urn:o-ran:interfaces:1.0"> true </vlan-tagging> </interface> </interfaces> Figure 7.1-0a: Example subset of configuration and operational data related Ethernet payload size Additionally, for O-RUs that include the ieee802-dot1x and ietf-system models in their YANG library the /if:interfaces/if:interface/dot1x:pae/dot1x:port-capabilities/dot1x:supp schema node enables an O-RU Controller to configure operation of IEEE 802.1X Port based Access Control, as specified in [70]. Above the Ethernet interface are VLAN interfaces. Both Ethernet and VLAN interfaces can support IP interfaces. IP interfaces are defined using the standard ietf-ip.yang model. The O-RU controller can restrict the maximum size of IP packets using the /if:interfaces/if:interface/ip:ipv4/ip:mtu and/or the /if:interfaces/if:interface/ip:ipv6/ip:mtu leaves. Accordingly, each IP interface can have an IPv4 and/or IPv6 interface(s) defined. An O-RU may support the PER-INT- TCP-MSS feature that allows an O-RU controller to configure the TCP Maximum Segment Size (MSS). When the O-RU supports the PER-INT-TCP-MSS feature, the O-RU shall reject any configuration where the mss-adjust leaf for an interface exceeds the value of /ip:mtu configured on the same interface. When a value of the mss-adjust leaf is configured, an O-RU shall set its value of MSS option to the configured value, independently of any MSS value derived using discovered MTU procedures. Figure 7.1-0b illustrates a subset of configuration data that enables a UDP/IP based CUS-Plane to benefit from 9 000 bytes payload, compared with the TCP based M-plane that is restricted to a payload of 1 500 bytes. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 61 <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> <interface> <name>10Geth0</name> <type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:ethernetCsmacd</type> <enabled>true</enabled> <vlan-tagging xmlns="urn:o-ran:interfaces:1.0"> false </vlan-tagging> <ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"> <mtu>9000</mtu> <tcp xmlns="urn:o-ran:interfaces:1.0"> <mss-adjust>1460</mss-adjust> </tcp> </ipv4> <ipv6 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"> <mtu>9000</mtu> <tcp xmlns="urn:o-ran:interfaces:1.0"> <mss-adjust>1440</mss-adjust> </tcp> </ipv6> </interface> </interfaces> Figure 7.1-0b: Example subset of configuration data related to different IP payload size for CU-Plane and M-Plane The O-RU shall provide operational state associated with the layer 3 configuration of these interfaces, including prefix(es), using the ietf-ip YANG model, and domain name servers and default gateway addresses, using the o-ran- dhcp YANG model. An example of such operational state for the ietf-ip YANG model is shown in Figure 7.1-1. <ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"> <enabled>true</enabled> <address> <ip>10.10.0.17</ip> <netmask>255.255.255.0</netmask> <origin>dhcp</origin> </address> </ipv4> Figure 7.1-1: Example operational data related to an IP interface Finally, leafs associated with CoS and DSCP marking are defined, enabling independent configuration of CoS and DSCP markings for u-plane, c-plane and m-plane traffic. As a default, all user-plane flows are marked identically by the O-RU. Optionally, the interfaces can be configured to support enhanced user plane marking for up-link traffic whereby different CoS or DSCP values can be configured. This enables individual receive endpoints in the O-RU to be configured with different markings to then enable differentiated handling of up-link flows by the transport system. Because the o-ran-interfaces model defines augments to the ietf-interfaces model, the O-RU can leverage the definition of operational state in ietf-interfaces to optionally report packet and byte counts on a per interface basis. A single RPC is defined in the o-ran-interfaces module, to enable these counters to be reset. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.2 Transceiver | The o-ran-transceiver YANG module is used to define operational state for the pluggable transceiver module (like SFP, SFP+, SFP28, XFP and QSFP, QSFP+, QSFP28, QSFP56). Each transceiver is associated with a unique interface-name and port-number. Interfaces accessible through the transceiver are provided by the interface-name, interface-names and additional-multi-lane-reporting/interface-names leaves in the o-ran-transceiver YANG module. A digital diagnostic monitoring interface for optical transceivers is used to allow access to device operating parameters. As specified in SFF-8472 [16] and SFF-8636 [34], data is typically retrieved from the transceiver module in a file. This file may be obtained from O-RU by the NETCONF client. See clause 9 for more details. With QSFP form factor, the optical links may be multi-wavelengths (4xTx & 4xRx) and/or multi-fibres (Multifibre Parallel Optic (MPO)). The QSFP digital diagnostic interface as specified in SFF-8636 [34] describes the use of optical lanes and the O-RU interface management defines alarm 29: "transceiver fault" for all media lanes. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 62 The byte with offset i (i=0, …, 511) from the beginning of the file is the byte read from data address i of the transceiver memory at two-wire interface address 0xA0 if i<256, otherwise it is the byte read from data address i-256 of the transceiver memory at two-wire interface address 0xA2. The retrieved data is stored in the file without any conversion in binary format. The O-RU stores data from the transceiver module on transceiver module detection during start-up. The data from the transceiver module is saved in the file. A NETCONF client can upload it by using the File Upload procedure defined in clause 12. The O-RU does not synchronize contents of the file with transceiver memory in runtime, therefore bytes representing dynamic information are expected to be outdated. The O-RU does not remove the file on transceiver module removal. If a transceiver module is inserted during File Upload procedure, then the procedure may provide a file with previous content or fail (with failure reason as listed in File Upload procedure). If the O-RU is unable to retrieve the data from the transceiver module or it is not present, then the O-RU does not create the file or removes the file created earlier. NOTE: File Upload procedure requesting non-existing file will fail. The file name shall have the following syntax: • sfp_{portNumber}.sffcap where {portNumber} is the value of port-number leaf of the corresponding list of port-transceiver data. EXAMPLES: sfp_0.sffcap, sfp_1.sffcap. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.3 C/U-Plane VLAN configuration | Within the o-ran-interfaces YANG model, each named Ethernet interface includes a leaf to indicate whether VLAN tagging is supported. By default, VLAN tagging shall be enabled on all interfaces. This permits an O-RU to autonomously discover that it is connected to a trunk port, as described in clause 6.2.3. When an O-RU is connected to a trunk port, VLANs will also typically be assigned to the C/U plane connections. The VLAN(s) used to support C/U plane transport may be different from the VLAN(s) used to support management plane connectivity. The VLAN assigned to the U-Plane shall be the same as the VLAN assigned to the C-Plane for any given eAxC_ID. When different VLANs are used, the C/U plane VLANs shall be configured in the O-RU by the NETCONF client. In such circumstances, as defined in o-ran-interfaces, the NETCONF client shall configure separate named interfaces for each active VLAN. This configuration will define a C/U-Plane named VLAN interface as being the higher-layer-if reference for the underlying Ethernet interface and the underlying Ethernet interface is defined as being the lower-layer-if reference for the named VLAN interface. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.4 O-RU C/U-Plane IP address assignment | In this release, the support for C/U plane transport over UDP/IP is optional and hence this clause only applies to those O-RUs that support this optional capability. An O-RU that supports C/U plane transport over UDP/IP shall support IPv4 and/or IPv6 based transport. A NETCONF client can receive a hint as to whether an O-RU supports a particular IP version by using the get RPC to recover the list of interfaces supported by the O-RU and using the presence of the augmented ipv4 container or ipv6 container in the o-ran-interfaces YANG module as an indication that a particular IP version is supported. The IP interface(s) used to support UDP/IP based C/U plane transport may be different than the IP interface(s) used to support management plane connectivity. When different IP interface(s) is/are used, the C/U plane IP interfaces shall be configured in the O-RU by the NETCONF client by using the ietf-ip YANG model to configure the IPv4 container and/or IPv6 container. When defined by the NETCONF client, this interface shall be configured using either a named Ethernet interface (i.e. where the interface type is set to ianaift:ethernetCsmacd) and/or a named VLAN interface (i.e. where the interface type is set to ianaift:l2vlan), depending upon whether VLANs are used to support IP based C/U plane traffic. When a separate C/U plane IP interface is configured by the NETCONF client, additionally the NETCONF client may statically configure the IP address(es) on this/these interface(s). If the NETCONF client does not statically configure an IP address, the O-RU shall be responsible for performing IP address assignment procedures on the configured interfaces. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 63 When an O-RU has not been configured with a static IP address, the O-RU shall support the IP address assignment using the following techniques: When the O-RU supports IPv4: 1) IPv4 configuration using DHCPv4 as specified in IETF RFC 2131 [10]. and when the O-RU supports IPv6: 2) IPv6 Stateless Address Auto-Configuration (SLAAC) as specified in IETF RFC 4862 [11]. OR 3) IPv6 State-full address configuration uses DHCPv6 as specified in IETF RFC 8415 [58]. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.5 Definition of processing elements | The CU-plane application needs to be uniquely associated with specific transport flows. This association is achieved by defining an O-RU "processing element" which can then be associated with a particular C/U plane endpoint eAxC ID, as specified in [2] clause 5.4 or delay measurement operation, as specified in [2] clause 4.4.3.3. Unless specified otherwise, a common processing element is required to be configured for the control and user-plane application components associated with any individual eAxC_ID. The O-RU management plane supports different options for defining the transport endpoint identifiers used by a particular processing element (used depending on transport environment), supporting the following 3 options: • Processing element definition based on usage of different (alias) MAC addresses; • Processing element definition based on a combination of VLAN identity and MAC address; and • Processing element definition based on UDP-ports and IP addresses. NOTE: There is no well-defined source port currently allocated by IANA for the o-ran application and hence the NETCONF client can configure this port number in the O-RU. A processing element consists of both the local and remote transport endpoints and is used as a logical transport path. The processing element definition includes its element name which is then used by other systems to refer to a particular processing element instance. The o-ran-interfaces YANG model is used to define feature support for C/U plane transport based on alias MAC addresses and UDP/IP. The exchange of NETCONF capabilities is used to signal which optional capabilities are supported by the O-RU, as described in Annex C. The o-ran-processing-elements YANG model uses a processing-elements container to define a list of processing elements. Each processing element is identified by a unique element name. Each processing element references a particular interface-name used to support the data flows associated with a particular processing element. Depending upon the type of C/U plane transport session, additionally leafs are configured that specify MAC addresses, and/or VLANs and/or IP addresses and/or UDP ports used to identify a particular processing element. If the O-RU reports the capability of supporting feature MULTIPLE-TRANSPORT-SESSION-TYPE, which indicates the O-RU supports multiple transport-session-type, the NETCONF client may configure processing-elements with more than one transport-session-type to the O-RU, using the list additional-transport-session-type-elements with the key transport-session-type. When a processing element configured by the list additional-transport-session-type- elements is referenced by other modules, the transport-session-type shall also be configured as a key to the list additional-transport-session-type-elements. The O-RU may discard any received CU-plane messages, i.e. eCPRI/IEEE 1914 frames/packets, which are not transported using a configured processing element. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 64 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.6 O-DU verification of C/U-Plane transport connectivity | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.6.1 C/U-Plane transport connectivity verification | As described above, there will likely be multiple C/U-plane data flows being exchanged between the O-DU and the O-RU. In order to enable checks verifying C/U-Plane end-to-end transport connectivity between the O-DU and O-RU, the O-RU shall support C/U-Plane connectivity verification capabilities using a request/reply function, as illustrated in Figure 7.6.1-1. Using that connectivity verification procedure, bi-directional reachability/connectivity verification between transport endpoints can be performed by the O-DU: • During O-RU configuration, to validate the transport configuration. • At runtime to regularly perform bi-directional network connectivity verification. The periodicity for bi-directional connectivity verification is usually between 1 and 60 seconds. Two different network protocols are defined for performing the bi-directional transport connectivity verification procedure: • For C/U sessions over Ethernet: Loop-back Protocol (LBM/LBR) as specified in IEEE 802.1Q-2018 [69]. • When the O-RU is configured to support C/U sessions over IP: UDP echo, as specified in IETF RFC 862 [18]. Figure 7.6.1-1: C/U Plane Transport Connectivity Verification ETSI ETSI TS 104 023 V17.1.0 (2026-01) 65 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.6.2 Ethernet connectivity monitoring procedure | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.6.2.1 Transport connectivity verification monitoring Procedure | When the O-RU and O-DU are operating their C/U sessions transported over Ethernet, the transport connectivity verification checks operate at the Ethernet layer. The protocol for Ethernet connectivity verification shall use the Loop-back Protocol as defined by IEEE 802.1Q-2018 [69]. For the purpose of regular connectivity verification, all transport endpoints used for C/U-plane messaging in the fronthaul network shall be configured to be part of the same Maintenance Entity (ME). The O-RU Controller shall configure each O-RU, assigning them the role of a Maintenance association End Point (MEP) for LBM. The sending of Loop-back Messages (LBMs) is administratively initiated and stopped in the O-DU. Therefore, sending LBM requests needs to be requested by an administration entity, specifying an Ethernet interface of the O-RU responder. If administratively initiated, the O-DU shall send the LBM request. When sending the LBM request, support for setting the destination MAC address as the unicast MAC address of the specified O-RU Ethernet interface as per IEEE 802.1Q-2018 [69] is mandatory while the support for setting the destination MAC address as the group destination MAC address 01-80-C2-00-00-3x as specified in Recommendation ITU-T Y.1731 [25] clause 7.2.2, where the LSB 4 bits are derived from the md-level configuration in o-ran-lbm.yang, is optional. See also clause 10.1 of Recommendation ITU-T Y.1731 [25]. An O-RU that supports LBM configuration using the ieee802-dot1q-cfm YANG model shall include the ieee802-dot1q- cfm model in its YANG library. Such an O-RU can have a common LBM configuration datastore and operational data, exposed by both ieee802-dot1q-cfm and o-ran-lbm YANG models. For example, an O-RU can ensure the value of replies-transmitted in o-ran-lbm YANG model to be set as identical to that value of mep-lbr-out in the ieee802-dot1q-cfm YANG model. In case the coordination of LBM configuration happens external to the O-RU, when LBM configuration is inconsistent between two models, the LBM behaviour of the O-RU is not specified by the present document. O-RUs that supports ieee802-dot1q-cfm.yang shall support the Notification of Updates to its Configuration Datastore functionality, as specified in clause 9.4. Hence, any NETCONF clients connected to the O-RU may configure subscriptions to receive notifications of modifications to ieee802-dot1q-cfm.yang and/or o-ran-lbm.yang configuration changes. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.6.2.2 Validating the transport configuration | After setting up a U/C-plane session between an O-DU and an O-RU, the O-DU can test whether connectivity exists as per the configuration. To achieve that, at the time a transport endpoint becomes operational at an O-RU, it starts an LBM responder application which automatically responds to incoming LBM requests on that transport endpoint. Based on a configuration command the O-DU starts sending out a predefined number of LBM requests to its O-RU(s) at a predefined interval, storing the information received in LBM responses from the O-RU(s) in an internal database. O-RU(s) are identified by both Ethernet MAC address and the CU plane VLAN. The O-RU shall be able to respond to Loopback Messages received from different remote Maintenance Association Endpoints, when the destination MAC address is the O-RU's MAC address. The O-RU should respond to Loopback Messages received from different remote Maintenance Association Endpoints, when the destination MAC address is a group destination MAC address as defined in clause 10.1 of [25]. In case the O-RU is operating in in deep-hibernate mode and the hibernate-time timer is operational, as specified in clause 20.5, the O-RU may suspend Loopback Message processing. In case the configuration of the session is indeed correct, the O-DU should receive LBM responses from the O-RU(s) within a time frame dependent on the network latency and the O-RU's reaction time. If LBMs from the O-RU(s) are being received, the session is determined to be operational. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.6.2.3 Monitor network connectivity | After the procedure described in clause 7.6.2.2 has been executed successfully, a further procedure may be executed continuously to maintain the connectivity status. To achieve this the O-DU can continually send out LBM requests at the configured interval. It also keeps track of LBM responses received. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 66 Based on the LBM responses received the O-DU shall decide on the connectivity status. Connectivity shall be assumed to be available as long as LBM responses from the O-RU(s) are being received at the configured interval. Connectivity shall be assumed not available if no LBM response from the particular O-RU has been received for an interval that is as long as 3 x the configured LBM request interval or longer. Optionally, for those O-RUs that advertise support for the ieee802-dot1q-cfm.yang, the O-DU can enable O-RU sending of Connectivity Check Messages (CCM) by configuring ccm-enabled to "true" on the O-RU. The O-DU can monitor network connectivity by received CCM message from the O-RU. These CCM messages are sent to a multicast destination address which encodes the maintenance domain level as specified in Table 8-18 of IEEE 802.1Q-2018 [69]. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.6.2.4 Managing ethernet connectivity monitoring procedure | An O-DU may have one or more Ethernet interfaces that have to support the Ethernet connectivity monitoring procedure. This clause describes the management of this function. The module described here is based on (i.e. a subset of) the mef-cfm module defined by the Metro Ethernet Forum [i.3]. This is to allow for a later extension of the module to the full feature set of mef-cfm. The YANG module provided below supports the configuration and fault management of the Loop-back Protocol as defined by IEEE 802.1Q-2018 [69]. Derived from MEF CFM YANG, the subset of type definitions is defined as part of the o-ran-lbm.yang. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.6.3 IP connectivity monitoring procedure | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.6.3.1 Monitoring procedure | If the O-RU and O-DU are connected using IP (and UDP/IP is being used to transport the C/U plane), these transport connectivity verification checks operate at layer 3. Layer 3 connection verification is based on the O-RU supporting the UDP echo server functionality, as specified in IETF RFC 862 [18]. The NETCONF client should enable the UDP echo server in the O-RU, triggering the O-RU to listen for UDP datagrams on the well-known port 7. When a datagram is received by the O-RU, the data from it is sent back towards the sender, where its receipt can be used to confirm UDP/IP connectivity between the transport endpoints. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.6.3.2 Managing IP connectivity monitoring procedure | This clause describes the management of the UDP echo functionality. The NETCONF client uses the enable-udp-echo leaf in the udp-echo YANG model to control operation of the UDP echo server in the O-RU. The NETCONF client is able to control the DSCP marking used by the O-RU when it echoes back datagrams using the dscp-config leaf. Additionally, the NETCONF client can recover the number of UDP Echo messages sent by the O-RU by using echo-replies-transmitted operational state. An O-DU may have one or more IP interfaces that have to support the UDP/IP connectivity monitoring procedure. An O-RU with its UDP echo server enabled shall be able to respond to UDP datagrams originated from any valid source IP address. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.7 C/U-Plane delay management | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.7.1 Introduction | The Intra-PHY lower layer fronthaul split has the characteristic of a stringent bandwidth and tight latency requirement. The CUS-Plane specification [2] clause 4.4 describes how the propagation delay incurred due to distance between the O-DU and O-RU is an important parameter in defining the optimization of windowing and receive-side buffering operations. This clause describes the procedures that are used to manage the delay parameters for the fronthaul split. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 67 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.7.2 Delay parameters | The reference points for delay management are specified in the CUS-Plane Specification [2], clauses 4.4 and 4.7. Important delay parameters related to the operation of the O-RU are referred to as the O-RU delay profile. As the delay characteristics for an O-RU may vary based on air interface properties, a table of the parameters is provided based on a combination of Sub-Carrier Spacing (SCS) and channel bandwidth. Other parameters related to delays to external antennas may vary according to specific tx/rx-array-carriers. When considering the downlink data direction, these parameters include: • T2a_min: Corresponding to the minimum O-RU data processing delay between receiving the last data sample over the fronthaul interface and transmitting the first IQ sample at the antenna. • T2a_max: Corresponding to the earliest allowable time when a data packet is received before the corresponding firs IQ sample is transmitted at the antenna. • Using the above parameters, (T2a_max - T2a_min): The difference between these two parameters corresponds to the O-RU reception window range. • T2a_min_cp_dl: Corresponding to the minimum O-RU data processing delay between receiving downlink real time control plane message over the fronthaul interface and transmitting the corresponding first IQ sample at the antenna. • T2a_max_cp_dl: Corresponding to the earliest allowable time when a downlink real time control message is received before the corresponding first IQ sample is transmitted at the antenna. • Tcp_adv_dl: Corresponding to the time difference (advance) between the reception window for downlink real time Control messages and reception window for the corresponding IQ data messages. • Tda: Corresponding to the time difference between the output of DL signal at the antenna connector of O-RU and the transmission over the air. The delay parameters related to the operation of the O-RU for the uplink data direction include: • Ta3_min: Corresponding to the minimum O-RU data processing delay between receiving an IQ sample at the antenna and transmitting the first data sample over the fronthaul interface. • Ta3_max: Corresponding to the maximum O-RU data processing delay between receiving an IQ sample at the antenna and transmitting the last data sample over the fronthaul interface. • Using the above parameters, (Ta3_max - Ta3_min): The difference between these two parameters corresponds to the O-RU transmission window range. • T2a_min_cp_ul: The minimum O-RU data processing delay between receiving real time up-link control plane message over the fronthaul interface and receiving the first IQ sample at the antenna. • T2a_max_cp_ul: The earliest allowable time when a real time up-link control message is received before the corresponding first IQ sample is received at the antenna. • Tau: Corresponding to the time difference between the reception over the air and the input of UL signal at the antenna connector of O-RU. If the O-RU supports multiple beamforming methods, some beamforming methods can have different delay parameters from others. In this case, the O-RU uses non-default-ru-delay-profile to report the additional sets of delay profile values based on a combination of SCS and bandwidth, the O-RU may only report the parameters that differ from ru-delay-profile. The delay parameter not reported in the non-default-ru-delay-profile uses the default value defined in ru-delay-profile. The delay-profile-id shall be used to identify additional sets of delay profiles supported by the O-RU in addition to the default delay profile. One delay profile may be common for multiple beamforming methods or may be specific to a beamforming method. Multiple BF methods used simultaneously can have the same set of delay profiles identified by the delay-profile-id. When requested, all O-RUs shall signal the table of statically "pre-defined" values of the above parameters, for different supported combinations of SCS and channel bandwidth over the management plane interface. This will typically occur during the initial start-up phase. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 68 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.7.3 Reception window monitoring | The O-RU shall monitor operation of its reception window, monitoring the arrival of packets received over the fronthaul interface relative to the earliest and latest allowable times as defined by the values of T2a_max and T2a_min respectively. See clause B.3 for information on reception window counters. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.7.4 External antenna delay control | An O-RU may optionally support the external antenna delay control by indicating that it supports the EXT-ANT- DELAY-CONTROL feature in its o-ran-wg4-features YANG model. Such an O-RU uses the ext-ant-delay-capability schema node in o-ran-module-cap YANG model to indicate to the O-RU Controller the type of external delay configuration supported by the O-RU: • PER-O-RU: The O-RU only supports a single value of t-da-offset and a single value of t-au-offset across all tx-array-carriers and rx-array-carriers respectively. • PER-ARRAY: The O-RU supports separate values of t-da-offset and t-au-offset across individual tx-arrays and rx-arrays respectively. • PER-ARRAY-CARRIER: The O-RU supports separate values of t-da-offset and t-au-offset across separate tx- array-carriers and rx-array-carriers respectively. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.8 O-RU adaptive delay capability | O-RUs may optionally support the ability to optimize their buffers based on information signalled concerning the configuration of the O-DU, e.g. including the O-DU delay profile, together with transport delay information, which may have been derived by the O-DU by using a delay measurement procedure operated by the O-DU or by other techniques. This clause describes such optional O-RU buffer optimization functionality. An O-RU that supports the optional adaptive timing capability shall indicate such to the O-RU Controller client by exchanging NETCONF capabilities, as described in clause 9.2 and Annex C indicating that it supports the ADAPTIVE RU-PROFILE feature. An O-RU Controller may then provide the O-RU with the O-DU delay profile based on a combination of Sub-Carrier Spacing (SCS) and channel bandwidth, comprising the following parameters: • T1a_max_up: Corresponding to the earliest possible time which the O-DU can support transmitting an IQ data message prior to transmission of the corresponding IQ samples at the antenna. • TXmax: Corresponding to the maximum amount of time which the O-DU requires to transmit all downlink user plane IQ data message for a symbol. • Ta4_max: Corresponding to the latest possible time which the O-DU can support receiving the last uplink user plane IQ data message for a symbol. • RXmax: Corresponding to the maximum time difference the O-DU can support between receiving the first user plane IQ data message for a symbol and receiving the last user plane IQ data message for the same symbol. • T1a_max_cp_dl: Corresponding to the earliest possible time which the O-DU can support transmitting the downlink real time control message prior to transmission of the corresponding IQ samples at the antenna. In addition to the O-DU delay profile, the O-RU-Controller provides the O-RU with the transport network timing parameters: • T12_min: Corresponding to the minimum delay between any O-DU and O-RU processing elements. • T12_max: Corresponding to the maximum delay between O-DU and O-RU processing elements. • T34_min: Corresponding to the minimum delay between any O-RU and O-DU processing elements. • T34_max: Corresponding to the maximum delay between O-RU and O-DU processing elements. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 69 As per [2] clause 4.7, the O-RU Controller shall configure values of t12-max and t34-max as if there is no external delay, i.e. Tau = Tda = 0 (zero). The O-RU may use this information to adapt its delay profile, ensuring that the inequalities defined in clause B of [2] are still valid The O-RU controller should provide this information during the O-RU's start-up procedure. If an O-RU receives the adaptive delay configuration information when operating a carrier, the O-RU shall not adapt its O-RU delay profile until all carriers operating using the O-RU buffers have been disabled. Once an O-RU has adapted its O-RU profile, it shall include the newly adapted timing values when signalling its delay parameters to a NETCONF client. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.9 Measuring transport delay parameters | An O-RU may optionally indicate that it supports the eCPRI based measurement of transport delays between O-DU and O-RU. If O-RU supports measured transport delay, it shall implement the protocol as described in the CUS-Plane Specification [2] clause 4.4.3.3. An O-RU that supports the eCPRI based delay measurement capability, shall be able to support the operation of delay measurements whenever any processing element has been configured as described in clause 7.5. For each processing element configured, the O-RU shall be able to respond to any messages when received and keep a record of the number of responses, requests and follow-up messages transmitted by the O-RU. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.10 O-RU monitoring of C/U-Plane connectivity | The O-RU should monitor the C/U plane connection and should raise an alarm if the logical C/U-plane connection associated with a processing-element fails. The O-RU uses a timer to monitor the C/U plane connection on a per processing-element basis. This timer is enabled only when at least one array-carrier using the processing-element is in the active state and is reset whenever it receives any C/U plane data flows associated with the particular processing- element. Because of the variety of PHY and C/U plane configurations, the O-RU cannot independently determine the minimum frequency of messages across the fronthaul interface. When an O-RU is monitoring the C/U plane, as a default, the O-RU uses a timer value of 160 milliseconds for monitoring the C/U plane connection. An O-RU may indicate that its C/U-plane monitoring timer is configurable, by the presence of the cu-plane-monitoring container in the o-ran-supervision.yang model. A NETCONF client can use the configured-cu-monitoring-interval leaf to configure the O-RU's timer value, including being able to disable the operation of C/U Plane monitoring. If the O-RU supports this timer, then depending on how long the O-DU takes to initiate sending of C/U plane data flows, it is advisable for the NETCONF client to initially disable the operation of the timer before carrier activation. Such an approach avoids the O-RU sending spurious alarm notifications triggered by O-DU delays in initializing the sending of C/U plane data that exceed the default timer value. Once C/U plane data flows have commenced, the NETCONF client can re-configure the timer with the desired value and hence activate monitoring of the C/U plane connectivity by the O-RU. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.11 Bandwidth management | An O-RU can indicate the maximum bitrate able to be supported on those interfaces associated with a particular physical port using the optional nominal-bitrate leaf in the o-ran-transceiver YANG module. When the sustainable bitrate able to be supported by an O-RU is less than the combined bitrates of all its physical ports, an O-RU can use the optional interface-grouping container in the o-ran-interfaces YANG model to define the maximum sustainable rate able to be supported by an interface-group-id corresponding to a group of one or more physical interfaces. The same YANG model is used to augment the ietf-interfaces defined interface list with the interface-group-id to which the interface belongs. NOTE: The maximum sustainable bandwidth is calculated over one radio frame, meaning that the peak bandwidth can exceed the defined value over time periods shorter than one radio frame. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.12 IEEE 802.1X port based access control | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.12.1 Configuring port based access control | The O-RU shall support IEEE 802.1X port based access control supplicant functionality. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 70 NOTE 1: IEEE 802.1X port based authentication is useful in those deployment scenarios where the O-RU is connected to a physically secure point-to-point Ethernet LAN used to transport the fronthaul traffic. NOTE 2: A previous version of the present document did not mandate IEEE 802.1X port-based network access control supplicant functionality in the O-RU. Operators that enable IEEE 802.1X authenticator PAE functionality in the fronthaul need to accommodate legacy O-RUs that do not support supplicant PAE functionality. NOTE 3: The present document does not define operation of an authenticator PAE in the O-RU. When operating an O-RU in shared cell configuration (i.e. in FHM or cascade mode), operators wanting to benefit from the port based access control supplicant functionality in an O-RU will need to rely on the transport network equipment to implement the authenticator PAE functionality. Clause 17.4 of O-RAN Xhaul Packet Switched Architectures and Solutions [73], requires each port connection from the transport network equipment towards the O-RU supports IEEE 802.1X authenticator functionality. O-RUs indicate they support IEEE 802.1X port based access control by including the ieee802-dot1x and ietf-system models in their YANG library. An O-RU Controller can use the /sys:system/dot1x:pae-system/dot1x:system-access- control parameter to enable or disable operation of IEEE 802.1X port based access control. Once configured, an O-RU shall store the system-access-control parameter in reset persistent memory. This means that, unless the O-RU has performed a factory reset procedure as described in clause 8.8, the O-RU shall always use the last configured value of system-access-control during its next start-up procedure. NOTE 4: The leaf sys:system/dot1x:pae-system/dot1x:system-access-control in ieee802-dot1x YANG model does not have a default value and hence IEEE 802.1X operation will normally be disabled in factory software. An operator and vendor can agree that an O-RU uses a default value for this leaf in factory software. The configuration parameters and operational data related to IEEE 802.1X are defined in the pae container defined in the ieee802-dot1x YANG model defined augmentation of ietf-interfaces YANG model. An O-RU uses the port-capabilities container to indicate to an O-RU controller its PAE capabilities on a per-port basis. An O-RU indicates it supports a supplicant on a particular port by setting the supp leaf to true. When an O-RU indicates it supports a supplicant, an O-RU controller can use the supplicant container to configure authentication timers and re-try behaviour. The O-RU controller can use the sys:system/dot1x:pae-system/o-ran-cert:credential container to configure the trust anchor and the client certificate to be used by the supplicant PAE. The O-RU shall store this supplicant and credential configuration in reset persistent memory. When using a group destination address for transmitting or receiving EAP encapsulation over LAN (EAPOL) messages, an O-RU including the model ieee802-dot1x-eapol in its YANG library shall use the value configured for the PAE using the eapol-group-address leaf. In other cases, an O-RU shall use the IEEE Std 802.1X PAE Address, as specified in clause 11.1.1 of IEEE 802.1X [70]. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.12.2 EAP authentication | The operation of a successful EAP authentication is described O-RAN Security Requirements Specifications [83], clause 3.2.5.5.3. An O-RU that supports IEEE 802.1X and which has its supplicant functionality enabled shall support EAP-TLS authentication. An O-RU that has a valid operator-signed certificate shall use the certificate in the EAP-TLS authentication. An O-RU that does not have a valid operator-signed certificate shall use its manufacturer installed certificate in the EAP-TLS authentication. All O-RUs that have a supplicant enabled shall set their unauthAllowed variable to AuthFail, as specified in IEEE 802.1X [70], clause 12.5.1. Accordingly, the O-RU's PAE controlled port state machine shall enable unauthenticated connectivity on a port with supplicant enabled only after the EAP authentication procedure has failed. NOTE: The PAE authenticator can decide to permit unauthenticated connectivity from an O-RU based on operator determined policy, e.g. based on matching the source Ethernet MAC address used by the Supplicant PAE against a register of O-RU MAC addresses. Such policies and their enforcement are outside the scope of the present document. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 71 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.12.3 Certificate time validation | Operation of the EAP-TLS method requires the O-RU verify the certificate chain presented by the authenticator PAE, including confirming the certificate's validity periods. O-RUs using IEEE 802.1X port based access control shall be able to verify the certificate validity periods during the EAP-TLS exchange, e.g. by employing a persistent clock or using GNSS-based time synchronization. If the O-RU cannot verify the certificates validity, e.g. because a persistent clock has failed, the EAP authentication procedure will fail. According to clause 7.12.2, this will result in the O-RU providing un-authenticated connectivity. If the O-RU uses a persistent clock for certificate validity checking and detects a persistent clock failure, it shall, as soon as possible, set its clock to the current time recovered from available external sources, e.g. PTP or GNSS. NOTE: The scenario corresponding to a failed clock source and resulting O-RU operation using un-authenticated connectivity, is identical to the O-RU operation prior to the introduction of IEEE 802.1X port based access control in version 10 of the present document. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.13 Media Access Control (MAC) security | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.13.1 General | Clause 7.13 describes requirements for those O-RUs that support MACsec. The support by an O-RU of MACsec is optional and hence clause 7.13 only applies to those O-RUs that support this optional capability. MACsec can be used in scenarios where the O-RU is not connected to a physically secure point-to-point Ethernet LAN. When configured, MACsec is used to secure the communications between the authenticated and authorised MAC Security Entity (SecY) associated with the O-RU's PAE and the SecY in the authenticator PAE. The present document places no restrictions on which element hosts the SecY associated with the authenticator PAE function which is a peer of the O-RU's supplicant PAE function. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.13.2 MACsec and MACsec key agreement | An O-RU that supports MACsec shall implement MAC Security Entity requirements as specified in clause 5.3 of IEEE 802.1AE [85], MACsec Key Agreement (MKA) functionality for authentication and cryptographic key distribution as specified in clauses 5.10 and 5.11 of IEEE 802.1X [70] and the cipher suite GCM-AES-128, as specified in clause 14.4 of IEEE 802.1AE [85]. An O-RU shall indicate it supports MACsec and MKA on a particular interface name by setting the following schema nodes to true: • /if:interfaces/if:interface/dot1x:pae/dot1x:port-capabilities/dot1x:macsec; • /if:interfaces/if:interface/dot1x:pae/dot1x:port-capabilities/dot1x:mka; and • /if:interfaces/if:interface/dot1x:pae/dot1x:kay/dot1x:macsec/dot1x:capable. When an O-RU Controller configures the value of /if:interfaces/if:interface/dot1x:pae/dot1x:kay/dot1x:enable to True on an interface, the O-RU shall enable the PAE Supplicant Key Agreement entitY (KaY) on the interface. The MACsec format used between the PAE Supplicant SecY and the peer PAE Authenticator SecY shall depend on whether the interface corresponds to the base-interface of an O-RU port, or a VLAN interfaces layered above a base-interface, as specified in clause 7.13.3. When the O-RU indicates multiple individual interfaces are MACsec capable, the O-RU shall support configuration and operation of multiple instances of the PAE Supplicant SecY on the individual interfaces. An O-RU that has a PAE Supplicant SecY configured on a VLAN interface which has secured communication with an authenticator PAE SecY shall be able to simultaneously support the configuration of a PAE Supplicant with IEE 802.1X on the base-interface, as described in clause 7.12. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 72 NOTE: Clause 5.2.5.6 of the O-RAN Security Requirements Specifications [83] defines three different MACsec "encryption modes". "LAN mode MACsec" corresponds to configuring the KaY/SecY on an O-RU base interface and configuring an EAPOL group address corresponding to the Nearest non-TPMR Bridge group address, as defined in Table 11-1 of IEEE 802.1X [70]. "MACsec using EDE-CC" mode corresponds to configuring the KaY/SecY on an O-RU VLAN interface and configuring an EAPOL group address corresponding to the EDE-CC PEP Address, as defined in Table 11-1 of IEEE 802.1X [70]. The present document does not specify a solution for the third mode "WAN mode MACsec". |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.13.3 MACsec frame format | The O-RU shall use the MACsec Ethertype 88-E5 to distinguish secure frames from other insecure frames. When the PAE Supplicant with SecY is configured on an O-RU base-interface, the VLAN tag, including the priority field, shall be encapsulated within the secure data portion of the MACsec frame, as illustrated in Figure 7.13.3-1. Figure 7.13.3-1: Base interface MACsec Frame, VLAN TAG and Priority Field When the PAE Supplicant with SecY is configured on an O-RU VLAN interface, i.e. an interface name entry which includes a vlan-id leaf, the VLAN tag, including the priority field, shall be put in a cleartext VLAN header before the SecTag and shall also include the VLAN header in the secure data, as illustrated in Figure 7.13.3-2. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 73 Figure 7.13.3-2: VLAN interface MACsec Frame, VLAN TAG and Priority Field |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.13.4 Controlled and uncontrolled port | The O-RU shall permit simultaneous access to secure MAC layer Internal Sublayer Services (ISS) using the controlled port of the SecY and insecure MAC ISS using the uncontrolled port, as illustrated in Figure 7.13.4-1. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 74 Figure 7.13.4-1: Simultaneous access to controlled and un-controlled ports The O-RU shall permit operation of other protocols and entities that make use of the service provided by the SecY's uncontrolled port to communicate independently of the operation of the MKA state machine. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 7.13.5 MACsec bypass policy | An O-RU may indicate it supports MACsec bypass policies on its base-interface by including the MAC-BYPASS- POLICY in its yang library feature list. This clause applies to those O-RUs that include the feature in their YANG library. MACsec bypass policies on the base-interface are defined to allow matching Ethernet frames egressing the O-RU to bypass MACsec protection being applied at the base-interface, instead forwarding the matching frames using the uncontrolled port. Three different types of policies are defined: 1) matching on destination MAC address; 2) matching on ethernet type; and 3) matching on vlan-id. O-RUs supporting MACsec bypass policy shall use the macsec-bypass-capabilities container to indicate the type(s) of MACsec bypass policy supported as well as the number of policy elements that can be configured by the O-RU controller. For O-RUs that support the MACSEC-BYPASS-POLICY feature, an O-RU controller can use the o-ran-interfaces YANG model to configure a base-interface on which it has enabled a SecY with a macsec-bypass-policy container. This container allows an O-RU controller to configure the policies to apply to egress packets from the base-interface. When an O-RU controller enables a SecY on a base-interface and does not configure a corresponding macsec-bypass- policy, all traffic egressing the base-interface shall be protected by MACsec. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 75 NOTE 1: The MACSEC-BYPASS-POLICY feature applies when the SecY is operating at the base-interface. Configuring SecY to operate at the VLAN-ID level automatically establishes MACsec bypass polices based on vlan-id. NOTE 2: The MACSEC-BYPASS-POLICY feature allows an O-RU controller to configure bypass policies for the PTP Message Ethernet Type (88F7). In such a scenario, an O-RU configured with a physical port with time-transmitter-only = True that corresponds to a MACsec enabled base-interface, will use the un-controlled port for all PTP frames egressing the O-RU. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8 Software management | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.1 General | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.1.1 Introduction | The Software Management function provides a set of operations allowing the desired software package or build to be downloaded, files to be installed and slot containing installed software to be activated at O-RU. There are two types of software management processing. Some O-RUs expect a software package (in form of a zip file) to be downloaded to O-RU, while other O-RUs expect individual files in a build to be downloaded. The O-RUs that do not support download of an archived package and require downloading of individual files in a build can be distinguished by the existence of data node build-content-download. For such O-RU, the O-RU controller shall provide remote-file-path of file in the desired build as input for software-download RPC. Refer to clause 8.5 for details. If the build-content-download is not exposed by an O-RU, the O-RU controller shall provide remote-file-path of the software package zip file as input for software-download RPC. Successful software activation operation does not mean an O-RU is running the just activated software build. An O-RU reset RPC is required to trigger the O-RU to take the activated software build into operational use. The software management functions involve the O-RU controller subscribing to receive particular YANG notifications from the O-RU. All O-RUs support the NETCONF Create-Subscription method, enabling those notifications to be transported using NETCONF notifications. In addition, those O-RUs that support the optional NON-PERSISTENT- MPLANE feature, the O-RU Controller can create a configured subscription from the O-RU, enabling those notifications to be transported over HTTPS to an Event-Collector as described in clause 18. It is also Vendor's responsibility to handle SW Build / package / file integrity check. The O-RU controller shall be able to obtain information contained in the manifest.xml. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.1.2 Software slots | The O-RU provides a set of so called "software slots" or "slots". Each slot provides an independent storage location for a single software build. The number of slots offered by O-RU depends on the device's capabilities. At least two writable slots shall be available at the O-RU for failsafe update operation. If the read-only slot is supported by an O-RU, the software that is present in the read only slot is termed factory default software and can be used in factory reset procedure. Refer to clause 8.9 for detailed information. Presence of read only slot is optional. The software slots are resources provided by the O-RU and as such are not the subject of creation and deletion. The size of individual software slots is fixed and determined by the O-RU's vendor and sufficient to accommodate the full software build. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.1.3 Software management procedures | Software management procedures are described in clauses 8.4, 8.5 and 8.6. Procedures used in Software Management are covered by o-ran-software-management.yang module. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 76 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.2 Software build | A single software build is considered as set of internally consistent files compliant within such a build. Replacement of files within a build is prohibited, as this will cause software version incompatibility. Software build is a subject of versioning and maintenance and as such cannot be broken. Whether a file is included in a build is defined in manifest.xml. The manifest.xml enables mapping from radio product type to files. Revision and name of the build in each slot is provided as result by the inventory procedure to ensure visibility of radio software installation status. The use of compression and ciphering for the content of the software build is left to vendor implementation. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.3 Software package | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.3.1 Software package name | The name of a software package shall conform to the following format: • "<Vendor Code><Vendor Specific Field>[#NUMBER].EXT" Where: • Vendor Code is a mandatory part which either has two capital characters or 1-5 digits. The vendor code prefix in the software package file name is used to avoid conflict between file names of SW packages provided by different vendors; • Vendor Specific Field is any set of characters allowed in filename. The value shall not include character "_" (underscore) or "#" (hash). The value can be defined per vendor for the human readable information. Version information is necessary in the Vendor Specific Field which defines load version; • NUMBER is optional and used when the software package is split into multiple files, e.g. when a zipped file is split into multi-part zip file - number after "#" indicates the part number of a split file. Numbering starts from 1 and shall be continuous; • EXT is a mandatory part which defines the extension of filename. A vendor provides one or more software packages. Each software package shall be compressed by zip. <EXT > in the file name shall be ".zip". The O-RUs that do not expose build-content-download shall support ZIP functionality. For O-RUs that expose build-content-download, support of ZIP functionality is implementation dependent. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.3.2 File server storage of software package | The operator needs to manage and control which O-RU files will be stored and used in the file server. The software package can be stored on the file sever as one or more archived file(s) or as multiple files that are extracted from a software package zip file. The O-RU controller triggers the O-RU to download software file from a file server and should ensure that all the files necessary for the O-RU are transferred from the file server to the O-RU. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.3.3 Software package content and manifest.xml file | Each software package includes: • manifest.xml • software files NOTE: Those software files are intended to be installed on software slot. Those software files are intended to be used for one or several O-RU products. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 77 An example of archive structure for the software files is: ../o-ru-sw/version1.0/xxxx ../o-ru-sw/version1.0/yyyy ../o-ru-sw/version2.0/yyyy ../o-ru-sw/version1.5/zzzz The content of the manifest.xml file allows to maintain software update process correctly in terms of compatibility between O-RU hardware and software files to be downloaded. The content of the manifest.xml file enables the O-RU controller to trigger the installation of files of a software build designed for device based on different product code. The manifest.xml file is contained in a software package and shall not be ciphered. The format of the manifest.xml file is illustrated below using example data: <xml> <manifest version="1.0"> /// @version describes version of file format (not the content) <products> <product vendor="XX" code="0818820\.x11" name="RUXX.x11" build-Id="1"/> <product vendor="XX" code="0818820\.x12" name="RUXX.x12" build-Id="1"/> <product vendor="XX" code="0818818\…" name="RUYY" build-Id="2"/> /// @vendor is as reported by O-RU /// @code is a regular expression that is checked against productCode reported by O-RU /// @name is optional and used for human reading - SHALL NOT be used for other purposes! /// @buildId is value of build@id (see below) </products> <builds> <build id="1" bldName="xyz" bldVersion="1.0"> /// @id is index of available builds and corresponds to attribute build-Id in the tag "product". /// @bldName and @bldVersion are used in YANG (build-name, build-version) <file fileName="xxxx" fileVersion="1.0" path="full-file_name-with-path-relative-to- package -root-folder" checksum="FAA898"/> <file fileName="yyyy" fileVersion="2.0" path="full-file_name-with-path-relative-to- package -root-folder" checksum="AEE00C"/ > /// @fileName and @fileVersion are used in YANG (name, version) /// @fileVersion may be used as a handle to identify a specific path used when archiving different file versions /// @path is full path (with name and extension) of a physical file, relative to package root folder, used in YANG (local-path) /// @checksum is used to check file integrity on O-RU side </build> <build id="2" bldName="xyz" bldVersion="1.0"> <file fileName="xxxx" fileVersion="1.0" path="full-file_name-with-path-relative-to- package -root-folder" checksum="FAA898"/> <file fileName="yyyy" fileVersion="2.0" path="full-file_name-with-path-relative-to- package -root-folder" checksum="AEE00C"/ > <file fileName="zzzz" fileVersion="1.5" path="full-file_name-with-path-relative-to- package -root-folder" checksum="ABCDEF"/ > </build> </builds> </manifest> </xml> Keywords in manifest.xml example are in bold, the keywords shall be strictly followed. Correspondence between content of manifest.xml tags, their attributes and content of o-ran-software-management.yang is: • XML tag "product", attribute "vendor" corresponds to content leaf "vendor-code"; • XML tag "product", attribute "code" corresponds to content of leaf "product-code"; • XML tag "product", attribute "build-Id" corresponds to content of leaf "build-id"; • XML tag "build", attribute "id" corresponds to leaf "build-id"; • XML tag "build", attribute "bldName" corresponds to content of leaf "build-name"; • XML tag "build", attribute "bldVersion" corresponds to content of leaf "build-version"; • XML tag "file", attribute "fileName" corresponds to content of leaf "name" in list "files"; • XML tag "file", attribute "fileVersion" corresponds to content of leaf "version" in list "files". ETSI ETSI TS 104 023 V17.1.0 (2026-01) 78 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.4 Software inventory | Pre-condition: • M-Plane NETCONF session established. Post-condition: • NETCONF client successfully collected the software inventory information from NETCONF server. Figure 8.4-1: Inventory fetch call flow Figure 8.4-1 illustrates the operation where Software Inventory is fetched by a NETCONF Client using the NETCONF get RPC filtered over the software-slot container. The response contains information about each software slot and its contents. The following information is provided by software-inventory reply message: a) name - name of the software slot (the name is defined by the O-RU vendor) b) status - status of the software slot. Status of the software in the slot can be: - VALID - Slot contains a software build considered as proven valid. - INVALID - software build in the software slot cannot be used by O-RU. The software is considered by the O-RU as damaged (e.g. wrong CRC). Failed software install operation can cause a slot status to change to "Invalid". - NETCONF client shall not activate a software slot that is invalid. Activation of a software slot containing an invalid software build shall be rejected by O-RU. - EMPTY - software slot does not contain any software files. NETCONF client shall not activate an empty software slot. Activation of an empty software slot shall be rejected by O-RU. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 79 c) active - indicates if the software stored in particular slot is activated at the moment. - True - software slot is activated. Active::True can be assigned only for slots with status "Valid". At any time, only one slot in the O-RU shall be marked as active::True. The O-RU shall reject activation for software slots with status "Empty" and "Invalid". - False - software slot is not active. d) running - informs if software stored in particular slot is used at the moment. - True - software slot contains the software build used by the O-RU in its current run. - False - software slot contains a software build not used by O-RU at the moment. e) access - informs about access rights for the current slot. - READ_ONLY - The slot is intended only for factory software. Activation of such software slot means performing a factory reset operation and a return to factory defaults settings. - READ_WRITE - slot used for updating software. f) product-code - product code provided by the vendor, specific to the product. g) vendor-code - unique code of the vendor. h) build-id - Identity associated with the software build. This id is used to find the appropriate build-version for the product consist of the vendor-code and the product-code. i) build-name - Name of the software build. j) build-version - Version of the software build for the product consist of the vendor-code and the product-code. k) files - list of files in the software slot. - name - name of one particular file - version - version of the file - local-path - complete path of the file on local file system - integrity - result of the file integrity check OK - file integrity is correct NOK - file is corrupted If a slot contains a file with integrity::NOK, the O-RU shall mark the slot with status::INVALID. The content of a software-slot is fully under O-RU's management - including removal of the content occupying the slot (in case the slot is subject of software update procedure), control of file system consistency and so on. The slot content shall not be removed until there is a need for new software to be installed. The empty slot parameters shall be as follows: • name: up to vendor, not empty • status: "EMPTY" • active: parameter does not exist • running: parameter does not exist • access: READ_WRITE • product-code: up to vendor • vendor code: up to vendor • build-name: null (empty string) ETSI ETSI TS 104 023 V17.1.0 (2026-01) 80 • build-version: null (empty string) • files: empty list |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.5 Download | Pre-condition: • M-Plane NETCONF session established. • O-RU Controller has subscribed to receive download-event notifications. • O-RU controller has validated presence of data node build-content-download at O-RU. Post-condition: • O-RU has downloaded the file specified and has successfully stored the downloaded file in the O-RU's file system. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 81 Figure 8.5-1: Software download call flow Figure 8.5-1 illustrates the software download call flow. The following types of authentications shall be supported for software-download: a) password for RU authentication and list of public keys (see clause 5.4 in the present document) for sFTP server authentication. Following types of authentications may be supported for software-download: a) X.509 certificate for authentication of FTPES client (O-RU) and FTPES server. b) certificate for both O-RU and sFTP server authentication. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 82 The software-download RPC is used to trigger the downloading of software files to the O-RU. The download shall be performed using either sFTP or FTPES. Based on presence of data node build-content-download, O-RU controller provides either path to a file in a build or path to a software package file as input to software-download RPC. The RPC specifies the URI of the remote location of the software files using the remote-file-path leaf, where the URI scheme is used to signal whether to use sFTP or FTPES. An O-RU Controller shall only trigger software-download using FTPES if it is using NETCONF/TLS to configure the O-RU. The O-RU shall send an immediate rpc-reply message with one of following statuses: a) STARTED - software download operation has been started. b) FAILED - software download operation could not be proceeded, reason for failure in error-message. The O-RU downloads the file from file server. When the O-RU completes the software download or software download fails, the O-RU shall send the download-event notification with one of the following statuses: a) COMPLETED. b) AUTHENTICATION_ERROR - source available, wrong credentials. c) PROTOCOL_ERROR - sFTP or FTPES protocol error. d) FILE_NOT_FOUND - source not available. e) APPLICATION_ERROR - operation failed due to internal reason. f) TIMEOUT - source available, credentials OK, Operation timed out (e.g. source becomes unavailable during ongoing operation). g) INTEGRITY_ERROR - file is corrupted. An O-RU that supports integrity check at download shall expose YANG feature cINTEGRITY-CHECK-AT-SW- DOWNLOAD". O-DU can enable the feature by configuring type empty parameter integrity-check-at-download- enabled. O-RU may send download-event with status INTEGRITY_ERROR when integrity-check-at-download- enabled is presented. NOTE: O-RU can obtain information of expected checksum either from manifest.xml or from information embedded in the file. O-RU controller shall repeat the above procedure until all files which are required by the O-RU have been downloaded to the O-RU. To determine all files needed by O-RU, the O-RU Controller uses content of manifest.xml and relies on presence of data node build-content-download. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.6 Install | Pre-condition: • M-Plane NETCONF session established. • At least one software slot with status active::False and running::False exists in O-RU. • Software Download has been completed successfully and all files required by the O-RU are available in O-RU. • O-RU Controller has subscribed to receive install-event notifications. Post-condition: • O-RU software file(s) is/are installed in the specified target software-slot. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 83 Figure 8.6-1: Software install call flow Figure 8.6-1 illustrates the operation where the NETCONF software-install RPC is used to install the previously downloaded software (i.e. all necessary) to the specified target software-slot on O-RU. The list of file-names in install-input shall not be empty. This slot shall have status active::False and running::False. The O-RU shall send an immediate rpc-reply message with one of following statuses: a) STARTED - software install operation has been started. b) FAILED - software install operation could not be proceeded, reason for failure in error-message. When O-RU completes the software install or software install procedure fails, the O-RU shall send the install-event notification with one of the following statuses: a) COMPLETED - Install procedure is successfully completed. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 84 b) FILE_ERROR - operation on the file resulted in in error, disk failure, not enough disk space, incompatible file format c) INTEGRITY_ERROR - file is corrupted. d) APPLICATION_ERROR - operation failed due to internal reason. e) TIMEOUT - install operation timed out. When the software install commences, the O-RU shall set the slot status to INVALID. After the install procedure finishes, the O-RU shall change the slot status to its appropriate status. O-RU shall not change the status of the slot when the install procedure is ongoing or when it is interrupted (e.g. by spurious reset operation). |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.7 Bringing software into operation | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.7.1 Procedure | Two steps are required to bring O-RU software into operation. The first step uses RPC software-activate to activate software in a slot. The second step, which may be delayed as per operator's decision until a suitable time, uses a reset RPC to take the activated software into operation. The information about which slot is active shall be reset persistent. NOTE: In certain circumstances, for example when performing a vendor defined O-RU recovery mechanism, the O-RU can start up using other software than the software in active slot before reset (e.g. factory default software). |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.7.2 Software activation | Pre-condition: • M-Plane NETCONF session established. • Software slot to be activated has status VALID. • O-RU Controller has subscribed to receive activation-event notifications. Post-condition: • For activated slot the parameter active is set to TRUE. At the same time the parameter active for previously operational slot is set to FALSE by the O-RU. Parameter running is not changed for any of O-RU's software slots. This indicates that O-RU is still running software from previously active slot. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 85 Figure 8.7.2-1: Software activation call flow Figure 8.7.2-1 illustrates the operations where the NETCONF software-activate RPC is used to activate the software. The name of the software-slot is specified in the activate request. The O-RU shall send an immediate rpc-reply message with one of following statuses: a) STARTED - software activation operation has been started. b) FAILED - software activation operation could not be proceeded, reason for failure in error-message. When the activation is completed, the O-RU shall send the activation-event notification with the status of activation. The following status is returned in the activation-event notifications. a) COMPLETED - Activation procedure is successfully completed. O-RU can be restarted via NETCONF reset rpc for the new software to be activated. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 86 b) APPLICATION_ERROR - operation failed due to internal reason. Only one software slot can be active at any time. Thus, successful software-activate command sets active to true for the slot that was provided in the RPC and O-RU sets active to false for the previously active slot. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.7.3 Reset | A O-RU reset is required to take the activated software into operation. See clause 9.5 for details of how an O-RU controller can trigger reset operation. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.8 Software update scenario | An example scenario of a successful software update procedure can be as follows. The present document does not distinguish between a software upgrade and a downgrade. 1) NETCONF client performs a software inventory operation and identifies that an inactive and not-running slot for installing software is available so that it can download and install a software package. 2) NETCONF client validates whether the O-RU has data node build-content-download. 3) In case the O-RU does not expose build-content-download, NETCONF client, knowing target SW version, O-RU product type and manifest.xml content, determines the software package zip file(s) to be downloaded. 4) In case the O-RU exposes data node build-content-download, NETCONF client, knowing target SW version, O-RU product type and manifest.xml content, determines the desired build name, build version and software files in the build to be downloaded. 5) NETCONF client using the software-download RPC triggers the O-RU to download a file (if several files are required, steps 5-7 need to be performed repeatedly until all files needed by O-RU have been downloaded). 6) O-RU sends RPC response that download was started. 7) O-RU finishes downloading the file(s) and reports this by sending the download-event notification. 8) NETCONF client requests installation of the software using software-install RPC, and provides the slot name where the software needs to be installed along with a list of filenames to be installed. NOTE: List of files to be installed cannot be empty. 9) O-RU sends RPC response that installation was started. 10) O-RU sets installation slot status to INVALID. 11) O-RU installs the software and after successful installation (with checksum control) changes status of the slot to VALID. 12) O-RU notifies the notification subscriber that the installation is finished using install-event notification. 13) NETCONF client requests the O-RU to activate the slot that contains the newly installed software using the software-activate rpc. 14) O-RU sends RPC response that activation was started. 15) For requested slot, O-RU changes active to true and at the same time sets active to false for previously active slot. 16) O-RU notifies the notification subscriber about activation finished using the activation-event notification. 17) NETCONF client restarts the O-RU forcing it to use the newly installed and activated software. Refer to clause 9.5 O-RU reset for detailed information. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 87 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 8.9 Factory reset | An O-RU that support a read only slot can perform this procedure. O-RU can be reset to the factory default software by activating the software-slot containing the factory default software and initiating NETCONF reset RPC. O-RU may clear persistent memory data during factory reset as vendor implementation option. Factory default software may have limited functionality and O-RU that runs on factory default SW will typically require a software update before it can be fully functional (for example carry traffic). Factory default software shall support all functionality needed to perform a software update. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 9 Configuration management | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 9.1 Baseline configuration |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.