Sujeet Kumar’s Post

View profile for Sujeet Kumar, graphic

Senior Technical Specialist |5G | O-RAN | LTE | RAN | Telco Cloud | Open stack | SDN | NFV |AWS | Linux | shell scripting | Jenkins | PYTHON | KUBERNETES | DOCKER | AUTOMATION.

🎤 why Interoperability Testing Required 5G(ORAN): 🔸 While the move to open RAN offers numerous benefits for MNOs, making it work means adopting rigorous testing requirements. 🔸 A few years ago, it was sufficient to simply test an Evolved Node B (eNB) as a complete unit in accordance with 3GPP requirements. 🔹 But the introduction of the open RAN and distributed RANs change the equation, requiring testing each component of the RAN in isolation for conformance to the standards and testing combinations of components for interoperability. 🎤 FH tests focused on the M-Plane IOT: 🔸 Start-up (O-RU start-up from the power-on of O-RU to the availability of service). 💠 Fronthaul M-Plane Architectural options 🔸 Hierarchical model: The O-RU is entirely managed by one O-DU (sudo) using a NETCONF based M-Plane interface. 🎤 Procedure: M-Plane start up test 🎤 M-plane IOT Test: 🔸 Netconf Client 🔸 By default, Netconf server running at O-RU is listening on port #830. 🔸 Following is the command used at netopeer2-cli to connect to the O-RU   $ netopeer2-cli   > connect --host <o-ru-ip-address> --port 830 --login root                        Interactive SSH Authentication Type your password:                        Password: admin123 💠 RPC execution 🔸 Following is the command to execute RPCs from netopeer2-cli:   > user-rpc --file <file.xml> --timeout 120 👉 Transport layer initialization 👉 RU calls home to NETCONF client (TCP connection establishment) 💠 Pre - Requisites: O1_MPLANE_CONN_METHOD=CALLHOME        Set below mentioned fields in /o1_config.cfg file on the O-RU side   O1_MPLANE_CONN_METHOD=CALLHOME NETCONF_CONNECTION_PROTOCOL=SSH   Set the DU IP address in /o_ran_transport.cfg ODU_IPADDRESS=<DU_IP_ADDERESS>  🔸 Restart the O-RU to make the above configuration changes effective.  🔸 Start netopeer2-cli on Linux terminal on Netconf client side:   $ netopeer2-cli > listen netopeer2-cli Give listen to establish CALLHOME session in NETCONF client 👉 SSH/TLS Secure connection establishment 👉 Initial process of NETCONF Subscribe for each stream XML to subscribe to NETCONF stream.  <create-subscription xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">    <stream>NETCONF</stream> </create-subscription> 👉 Supervision of NETCONF connection 👉 Retrieval of O-RU information and Additional configuration O-DU sends <rpc><get><filter=”subtree”> to get each yang module listed in ietf-yang-library.yang in O-RU, for example ietf-hardware augmented by o-ran-hardware O-RU responds with <rpc-reply><data> for each yang module per <rpc><get> O-DU sends <rpc><edit-config> to each configurable yang module for additional configuration to O-RU whenever it is necessary O-RU responds with <rpc-reply><ok/> 👉 Software management

  • No alternative text description for this image

To view or add a comment, sign in

Explore topics