Apparatus for managing cells of a communication network in an ORAN environment and method thereof

Abstract

Disclosed is an apparatus of an Open Radio Access Network (ORAN) Radio Unit (O-RU) (402) and a method (600) for managing cells of a communication network in the ORAN environment. The O-RU (402) identifies each cell of a plurality of cells of the communication network supported by an apparatus of the O-RU (402) based on an identification information associated with each cell. Using the identification information, an Internet Protocol (IP) address is assigned to one or more fronthaul interfaces of each cell of the plurality of cells. One or more of the IP address and the identification information of each cell are published to a plurality of ORAN Distributed Units (O-DUs) (404) for identifying one or more O-DUs available for establishing an independent connection with a respective cell of the plurality of cells supported by the O-RU (402).

Description

APPARATUS FOR MANAGING CELLS OF A COMMUNICATION NETWORK IN AN ORAN ENVIRONMENT AND METHOD THEREOFTECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of communication networks and systems. More particularly, the present disclosure relates to an apparatus of a Radio Unit (RU) and a method for the O-RU for managing cells of a communication network in an Open Radio Access Network (ORAN) environment.BACKGROUND OF THE INVENTION

[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely due to its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.

[0003] A wireless communication network utilizes a large number of wireless and wired nodes hosting one or more telecom functions. Some of the nodes are deployed in data centers to provide centralized services, while other nodes are positioned across a geographical area to provide telecom coverage. All these nodes forming a part of the communication network work together in cohesion for providing seamless telecom services to User Equipment (UEs) in the communication network. The nodes operating in the communication network may be manufactured by different manufacturers. The nodes manufactured by the different vendors may perform the same functions or varied functions.

[0004] The nodes of a Radio Access Network (RAN) may also serve as monolithic units for network operators providing all-in-one solutions of a cellular protocol stack, however, the nodes with all-in-one solutions are provided by a limited number of vendors. To the network operators, the nodes or other RAN components are oftenblack boxes with limited reconfigurability for supporting diverse deployments and different traffic profiles. To overcome these limitations, Open RAN (ORAN) is being used in present day communication networks as the ORAN offers disaggregated, virtualized, and software-based components, connected through open and standardized interfaces, and interoperable across different vendors. Open and standardized interfaces also allow the network operators to onboard different equipment vendors, and open interfaces with software-defined protocol stacks further enables integration of intelligent, data-driven closed-loop control for the RAN. The 0-RAN specifications implement these principles on top of 3rd Generation Partnership Project (3GPP) LTE and New Radio (NR) RANs.

[0005] FIG. 1 illustrates a block diagram 100 depicting an architecture of the ORAN, in accordance with prior art. As illustrated in Fig. 1, the ORAN extends the 3GPP NR 7.2 split for base stations by disaggregating base station functionalities into an ORAN Central Unit (O-CU) 102, an ORAN Distributed Unit (0-DU) 104, and an ORAN Radio Unit (0-RU) 106. The 0-RU 106 is a hardware unit located near or integrated with an antenna of a node for transmitting or receiving radio signals. The 0-RU 106 is also configured to process the radio signal such as convert the received radio signals into digitalized radio signals and amplify the radio signals.

[0006] The 0-DU 104 and the O-CU 102 form logical units of the nodes. The O-DU 104 may be located at or near the 0-RU 106 and the O-CU 102 may be located near a Core Network (CN) 108. The 0-DU 104 and the O-CU 102 are configured to send the digitalized radio signal into the CN 108.

[0007] The O-CU 102 implements higher layers of a 3rd Generation Partnership Project (3GPP) stack, i.e., the Radio Resource Control (RRC) layer for managing life cycle of a connection; Service Data Adaptation Protocol (SDAP) layer for managing a Quality of Service (QoS) of the traffic flows, and a Packet Data Convergence Protocol (PDCP) layer for reordering, packet duplication, and encryption for air interface. Further, the 0-DU hosts Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) sublayers of the 3 GPP stack.

[0008] The O-RU 106, O-DU 104, and the O-CU 102 communicate with each other via different interfaces associated with the ORAN. The O-RU 106 and the O-DU 104 are connected by a fronthaul interface, the O-DU 104 and the O-CU 102 are connected by a mid-haul interface, and a backhaul interface connects the O-CU 102 with the CN 108. The fronthaul interface includes a Control / User / Synchronization (C / U / S) plane 110 and a Management (M) plane 112. The C plane refers to realtime control of data between the O-DU 104 and the O-RU 106, U plane refers to an interface for handling In phase and Quadrature (IQ) sample data transferred between the O-DU 104 and the O-RU 106, and the S plane handles data corresponding to traffic between the O-RU 106 or the O-DU 104 to a synchronization controller. The M plane 112 refers to an interface for handling non-real-time management operations between the O-DU 104 and the O-RU 106. For efficient and robust management of the ORAN, the M-Plane 112 plays a pivotal role in overseeing various functionalities within ORAN, including configuration, performance monitoring, fault handling, and software updates.

[0009] The O-RU 106 is managed exclusively by one or more of a Network Management System (NMS) 114 and the O-DU 104, using a Network Configuration Protocol (NETCONF) based M-Plane 112 interface and the YANG (Yet Another Next Generation) data modelling language. The O-DU 104 acts as the central authority for performing management operations for the O-RU 106. The O-DU 104 and the NMS 114 correspond to NETCONF clients while O-RUs 106 correspond to NETCONF servers.

[0010] FIG. 2 illustrates an exemplary architecture of a traditional O-RU in the ORAN environment, in accordance with prior art. Generally, as per the ORAN specification, for supporting a plurality of cells, an O-DU of a plurality of O-DUs 202-1 to 202 -N (collectively referred to as O-DU 202) is required to connect with an O-RU of a plurality of O-RUs 204-1 to 204-N (collectively referred to as O-DU 204). One O-DU 202 is supported with a single hardware of the traditional O-RU 204. Each O-DU 202 serves as a NETCONF client and each O-RU 204 serves as a NETCONF server, with an independent C / U / S / M plane interface between each ofthe O-DU 202 and each of the 0-RU 204. However, such a deployment of the O-RU 204 is inefficient and leads to wastage of hardware resources in the 0-RU 204. Furthermore, a one-on-one modelling of the O-DU 202 with the O-RU 204 increases operation costs for network operators especially with exponential growth of the ORAN across geographies. To this end, there is a need to optimize management of the ORAN.SUMMARY

[0011] The following embodiments present a simplified summary in order to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive overview, and it is not intended to identify key / critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0012] In an embodiment, disclosed herein is a method for managing cells of a communication network in an Open Radio Access Network (ORAN) environment, the method comprises identifying, by a processing module of an ORAN Radio Unit (O-RU), each cell of a plurality of cells of the communication network supported by an apparatus of the O-RU based on an identification information associated with each cell. Further, the method comprises assigning by the processing module using the identification information, an Internet Protocol (IP) address to one or more fronthaul interfaces of each cell of the plurality of cells. Furthermore, the method comprises publishing, by a transceiver module of the O-RU, one or more of the IP address and the identification information of each cell to a plurality of ORAN Distributed Units (O-DUs) for identifying one or more O-DUs available for establishing an independent connection with a respective cell of the plurality of cells supported by the ORU. Based on the availability of the one or more O-DUs among the plurality of O-DUs, the method comprises receiving, by the transceiver module, a configuration information associated with each O-DU of the one or more O-DUs for establishing the independent connection with the respective cell. Thereafter, themethod comprises establishing, by the processing module upon receiving the configuration information from the O-DU, the independent connection between the respective O-DU and the respective cell via the one or more fronthaul interfaces.

[0013] In one or more embodiments, the method comprises fetching, by the processing module, the configuration information of the respective O-DU updated by the respective cell in a datastore corresponding to a Yet Another Next Generation (YANG)-based data model. Further, the method comprises linking, by the processing module, the IP address of each fronthaul interface of the one or more fronthaul interfaces with the configuration information of the respective O-DU.

[0014] In one or more embodiments, the method comprises initiating, by the processing module upon establishment of the connection, a Network Configuration (NETCONF) protocol-based session between the respective O-DU and the respective cell at each fronthaul interface of the one or more fronthaul interfaces. Further, the method comprises performing, by the processing module, a plurality of operations associated with management of the respective cell via the NETCONF protocol -based session of the one or more fronthaul interfaces.

[0015] In one or more embodiments, the plurality of operations comprises securing, by the processing module, the NETCONF protocol-based session by authenticating via security protocols based on security information of the respective O-DU included in the configuration information. Further, the plurality of operations comprises exchanging, by the transceiver module, between the respective O-DU and the respective cell via the secured NETCONF protocol-based session, capability information corresponding to NETCONF capabilities of each of the respective O-DU and the respective cell.

[0016] In one or more embodiments, the plurality of operations further comprises receiving, by the transceiver module, via the secured NETCONF protocol-based session, operational parameters of the respective cell from the respective O-DU upon determining persistent flow of the data traffic during the NETCONF protocolbased session. Further, the plurality of operations comprises configuring, by theprocessing module, the respective cell by dynamically tuning the apparatus of the O-RU based on the received operational parameters.

[0017] In one or more embodiments, the plurality of operations further comprises one or more of monitoring, by the processing module, data traffic of the NETCONF protocol-based session at each of the one or more fronthaul interfaces between the respective O-DU and the respective cell for determining whether one or more data packets associated with the respective O-DU are received at the respective cell. Further, the plurality of operations further comprises one or more of sending, by the processing module to the respective O-DU, network statistics corresponding to the respective O-DU based on the determination that the one or more data packets associated with the respective O-DU are received at the respective cell via the NETCONF protocol-based session of each of the one or more fronthaul interfaces. Furthermore, the plurality of operations further comprises one or more of raising, by the processing module, at the respective O-DU, one or more alarms corresponding to the respective O-DU based on the determination that no data packets are received at the respective cell via the NETCONF protocol-based session of each of the one or more fronthaul interfaces.

[0018] In one or more embodiments, the configuration information includes at least one of a Media Access Control (MAC) address of the respective O-DU, security information of the respective O-DU, physical port number of the respective O-DU, a hardware address of an ethemet port of the respective O-DU, and a Virtual Local Area Network Identifier (VLAN-ID) of the respective O-DU.

[0019] In another embodiment, disclosed herein is an apparatus of an Open Radio Access Network (ORAN) Radio Unit (O-RU) for managing cells of a communication network in an ORAN environment. The apparatus comprises a processing module and a transceiver module. The processing module is configured to identify each cell of a plurality of cells of the communication network supported by the apparatus of the O-RU based on an identification information associated with each cell. Further, the processing module is configured to assign, using theidentification information, an Internet Protocol (IP) address to one or more fronthaul interfaces of each cell of the plurality of cells. The transceiver module configured to publish one or more of the IP address and the identification information of each cell to a plurality of ORAN Distributed Units (O-DUs) for identifying one or more O-DUs available for establishing an independent connection with a respective cell of the plurality of cells supported by the ORU. Based on the availability of the one or more O-DUs among the plurality of O-DUs, the transceiver module is configured to receive a configuration information associated with each 0-DU of the one or more O-DUs for establishing the independent connection with the respective cell. Thereafter, the processing module is configured to establish, upon receiving the configuration information from the O-DU, the independent connection between the respective O-DU and the respective cell via the one or more fronthaul interfaces.

[0020] In one or more embodiments, the processing module is further configured to fetch the configuration information of the respective O-DU updated by the respective cell in a datastore corresponding to a Yet Another Next Generation (YANG)-based data model. Further, the processing module is configured to link the IP address of each fronthaul interface of the one or more fronthaul interfaces with the configuration information of the respective O-DU.

[0021] In one or more embodiments, the processing module is further configured to initiate, upon establishment of the connection, a Network Configuration (NETCONF) protocol-based session between the respective O-DU and the respective cell at each fronthaul interface of the one or more fronthaul interfaces. Furthermore, the processing module is configured to perform a plurality of operations associated with management of the respective cell via the NETCONF protocol -based session of the one or more fronthaul interfaces.

[0022] In one or more embodiments, for performing the plurality of operations, the processing module is further configured to secure the NETCONF protocol-based session by authenticating via security protocols based on security information of the respective O-DU included in the configuration information. Furthermore, thetransceiver module is configured to exchange, between the respective O-DU and the respective cell via the secured NETCONF protocol-based session, capability information corresponding to NETCONF capabilities of each of the respective O-DU and the respective cell.

[0023] In one or more embodiments, for performing the plurality of operations, the transceiver module is further configured to receive, via the secured NETCONF protocol-based session, operational parameters of the respective cell from the respective O-DU upon determining persistent flow of the data traffic during the NETCONF protocol-based session. Furthermore, the processing module is configured to configure the respective cell by dynamically tuning the apparatus of the O-RU based on the received operational parameters.

[0024] In one or more embodiments, for performing the plurality of operations, the processing module is further configured to monitor data traffic of the NETCONF protocol-based session at each of the one or more fronthaul interfaces between the respective O-DU and the respective cell for determining whether one or more data packets associated with the respective O-DU are received at the respective cell. Furthermore, the processing module is configured to send, to the respective O-DU, network statistics corresponding to the respective O-DU based on the determination that the one or more data packets associated with the respective O-DU are received at the respective cell via the NETCONF protocol-based session of each of the one or more fronthaul interfaces. Thereafter, the processing module is configured to raise, at the respective O-DU, one or more alarms corresponding to the respective O-DU based on the determination that no data packets are received at the respective cell via the NETCONF protocol-based session of each of the one or more fronthaul interfaces.

[0025] In one or more embodiment, the configuration information includes at least one of a Media Access Control (MAC) address of the respective O-DU, security information of the respective O-DU, physical port number of the respective O-DU,a hardware address of an ethemet port of the respective 0-DU, and a Virtual Local Area Network Identifier (VLAN-ID) of the respective 0-DU.BRIEF DESCRIPTION OF DRAWINGS

[0026] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For the purpose of consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.

[0027] FIG. 1 illustrates a block diagram depicting an architecture of an Open Radio Access Network (ORAN), in accordance with prior art.

[0028] FIG. 2 illustrates an exemplary architecture of a traditional ORAN Radio Unit (O-RU) in the ORAN environment, in accordance with prior art.

[0029] FIG. 3 illustrates a block diagram depicting an exemplary environment of a communication network, in accordance with an embodiment of the present disclosure.

[0030] FIG. 4 illustrates an exemplary architecture of an apparatus of O-RU for managing cells of the communication network in an O-RAN environment, in accordance with an embodiment of the present disclosure.

[0031] FIG. 5 illustrates a flowchart depicting a method for management of communication between the plurality of cells supported at multi cell O-RU and plurality of ORAN Distributed Units (O-DUs), in accordance with an embodiment of the present disclosure.

[0032] FIG. 6 illustrates a flowchart depicting a method for managing cells of the communication network in the ORAN environment, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION OF THE INVENTION

[0033] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodiments disclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.

[0034] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.

[0035] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” or “some implementations” which may each refer to one or more or all of the same or different embodiments or implementations. The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “inan embodiment” or “in an implementation” refers to one embodiment or one implementation and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments ”. Further, the term, for example, “in one or more implementations” refers to “at least one implementation, or more than one implementation, or all implementations.

[0036] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so-described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,” “have,” “contains,” and other similar words are used in either the detailed description, such terms are intended to be inclusive in a manner similar to the term “comprising.”

[0037] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features.

[0038] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.

[0039] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As usedherein the description, the singular forms "a", "an", and "the" include plural forms unless the context of the invention indicates otherwise.

[0040] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure. Accordingly, unless otherwise defined, all terms, and especially any technical and / or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.

[0041] An object of the present disclosure is to provide an apparatus of an Open Radio Unit (0-RU) configured for managing cells of a communication network in an Open Radio Access Network (ORAN) environment. Another object of the present disclosure is to provide a method for management and monitoring session of each cell of a plurality of cells independently at the 0-RU. Yet another object of the present disclosure is to provide independent alarm count and fault monitoring for each cell of the plurality of cells independently by the 0-RU. Still another object of the present disclosure is to support multiple Open Distributed Units (0-DU) in an Open Radio Access Network (ORAN) environment simultaneously.

[0042] In the disclosure, various embodiments are described using terms used in communication standards (e.g., 3rd Generation Partnership Project (3GPP), x Radio Access Network (xRAN), and Open-Radio Access Network (0-RAN)), but these are merely examples for description. Various embodiments of the disclosure may also be modified and applied to other communication systems.

[0043] In order to facilitate an understanding of the disclosed invention, a number of terms are defined below.

[0044] A cell refers to a geographically defined area covered by a base station in a communication network. The base station within the cell provides a radio coverage that allow mobile devices within the cell to avail services of the communication network. The cells are arranged in a grid-like pattern, often hexagonal, to providecontinuous coverage across a region. For example, the cells may be in a range of a few meters to a few kilometers.

[0045] An O-RU refers to an entity responsible for Radio Frequency (RF) processing, including transmission and reception of signals over an air interface (Uu). The O-RU handles lower physical layer (Layer 1) functions such as digital-to-analog conversion, filtering, amplification, and antenna control. The O-RU may typically be deployed at a cell site or tower, close to the antennas.

[0046] An ORAN Distributed Unit (O-DU) performs refers to an entity responsible for performing higher physical layer (Layer 1) and Layer 2 functions, including medium access control, radio link control, medium access control, Radio Link Control, and some functionalities of functionalities of a physical layer. The O-DU also manages scheduling and resource allocation. The O-DU may typically be deployed at a centralized location or be deployed at edge data centers.

[0047] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. FIG. 3 through FIG. 6, discussed below, and the one or more embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0048] FIG. 3 illustrates a block diagram depicting an exemplary environment of a communication network 300, in accordance with an embodiment of the present disclosure. As illustrated in FIG. 3, the environment of the communication network 300 includes a Core Network (CN) 302 connected to a Radio Access Network (RAN) 304 via a data network 306 for serving one or more user devices 308-1, 308-2, 308-3, 308-4, through 308-(N-l), 308-N (collectively referred to as the “user devices 308”, “User Equipment (UE) 308”, and individually referred to as the “user device 308”, hereinafter). Typically, the term “UE 308” can refer to any component such as “mobile station,” “subscriber station,” “remote terminal,” “wirelessterminal,” “receive point,” or “end user device”. The UE 308 may correspond to, but is not limited to, mobile devices, tablets, or other portable devices utilized by users to access services provided by the CN 302 through radio connections provided by the RAN 304.

[0049] The RAN 304 includes a plurality of nodes 304-1 to 304-N. The plurality of nodes 304-1 to 304-N may be a network infrastructure that provides wireless access to one or more terminals or the user devices 308. The plurality of nodes 304-1 to 304-N provide coverage to a plurality of predetermined geographic areas based on distance over which a signal may be transmitted. The nodes may correspond to, but not limited to, a base station, and may also be referred to as a wireless “Access Point (AP),” “Long Term Evolution (LTE) evolved NodeB (eNodeB) (eNB),” “evolved NodeB (eNodeB)” “5th Generation (5G) node,” “next generation NodeB (gNB),” “wireless point,” “Transmission / Reception Point (TRP),” or other terms having equivalent technical meanings. The nodes 304 may provide wireless access in accordance with wireless communication protocols, e.g., 5G / NR 3GPP New Radio interface / access (NR), LTE, Long Term Evolution Advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.

[0050] The core network 302 may be configured as an application server and may be communicab ly operational or may be integrated with the user device 308 via a network coupled with a server. The core network 302 may host a plurality of network functions and may pertain to 5G service-based architecture and may be configured to interconnect distinct networks associated with the architecture. Therefore, the core network 302 may provide a path for the exchange of information between one or more of the networks, and corresponding subnetworks. The core network 302 is configured to facilitate a secured communication between the one or more user devices 308 associated with the plurality of nodes 304 in the RAN 304.

[0051] Further, the CN 302 connects the RAN 304 to the data network 306. The data network 306 may include wired connections, wireless connections such as a proprietary Internet Protocol (IP) network, Internet, or in accordance with otherwireless communication standards such as Worldwide Interoperability for Microwave Access (WiMAX), Wi-Fi 802.11a / b / g / n / ac, or a combination of wired and wireless connections.

[0052] In one embodiment, the RAN 304 includes one or more of the nodes providing functionalities corresponding to a 3G network, a 4G network, a 5G network, or a combination thereof. The RAN 304 is configured to manage radio resources and execute functionalities such as power control, bandwidth allocation and controlling flow of data between the nodes 304 and the UE 308. The RAN 304 may be deployed in various configurations, such as Global System for Mobile Communications (GSM) RAN (GRAN), GSM Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Mobile Telecommunications Service (UMTS) Terrestrial RAN (UTRAN), Evolved UMTS Terrestrial RAN (E-UTRAN), Centralized / Cloud RAN (CRAN), Virtualized RAN (VRAN), and Open RAN (ORAN). The ORAN environment, in particular, is being implemented within 5G network and beyond 5G networks, as it supports interoperation between vendors’ equipment and offers interoperability standard for network elements in the RAN 304.

[0053] Although FIG. 3 illustrates one example of the communication network 300, various changes may be made to FIG. 3. For example, the communication network 300 may include any number of nodes and user devices in any suitable arrangement, without deviating from the scope of the present disclosure. Further, various components in FIG. 3 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0054] FIG. 4 illustrates an exemplary architecture of an apparatus of O-RU for managing cells of the communication network in an O-RAN environment, in accordance with an embodiment of the present disclosure. As shown in FIG. 4, an ORAN utilizes open interfaces and disaggregates functionalities of radio entities into separate hardware and software. Functionalities of the nodes in the ORAN is separated into an O-RU 402, a plurality of ORAN Distributed Units (O-DUs) 404-1 to 404-N (alternatively referred to as an O-DU 404 and collectively referred to as O-DUs 404), and an ORAN Centralized Unit (O-CU) (not shown in FIG. 4). The O-RU 402 and the O-DU 404 are connected by a fronthaul interface, the O-DU 404 and the O-CU are connected by a mid-haul interface, and a backhaul interface connects the O-CU with the CN 302. The fronthaul interface includes a Control / User / Synchronization (C / U / S) plane and a Management (M) plane. The O-RU 402, the O-DU 404, and the O-CU are connected to each other via one or more networks of the data network 306. The O-DUs 404 may be deployed at a network cell site or concentrated in aggregated locations.

[0055] The O-RU 402 is configured to support either a single logical cell or a plurality of logical cells on a common apparatus of the O-RU 402. The logical cell may correspond to a cell of the communication network for providing radio coverage in a geographical region. The O-RU 402 is configured to support either a single cell or a plurality of cells over itself, based on a configuration of the O-RU 402. Thus, the O-RU 402 may also be referred to as multi cell O-RU 402 throughout the specification interchangeably. A single cell or the plurality of cells may be supported by a common apparatus of the multi cell O-RU 402. The single cell or the plurality of cells may be configured over the common apparatus of the multi cell O-RU 402, based on a configuration file input by a network operator into the multi cell O-RU 402.

[0056] The multi cell O-RU 402 may utilize a common Multiple Input Multiple Output (MIMO) apparatus including hardware and / or software to support the single cell or the plurality of cells simultaneously. The multi cell O-RU 402 may further include one or more Modulators-Demodulators (Modems) 406-1 to 406-n (collectively referred to as 406) and a physical interface for connection with the single cell or the plurality of the cells, based on the configuration. The one or more modems 406 converts digital data signals received from each of the plurality of cells into modulated analog signals suitable for transmission.

[0057] In one embodiment, a n-by-n modem of the one or more modems 406 of the multi cell O-RU 402 may be split into smaller configurations for connecting the plurality of cells. For an example, an 8x8 modem may be split in to two 4x4 modems and similarly, a 4x4 modem may be split in to two 2x2 modems, for supporting four cells simultaneously. The multi cell O-RU 402 may support operations for each individually split modem and a corresponding cell.

[0058] Each modem may be identified with a specific carrier names of plurality of carriers (n) at transmitters (tx) and receivers (rx) of each modem such as tx_array_carrierO, rx_array_carrierO, tx_array_carrierl, rx array carrierl . ‘n’ corresponds to any carrier number of a respective cell supported by each modem such as 0,1, 2 etc. The multi cell O-RU 402 may support modem operations such as carrier creation, activation of tx array carrier n, deactivation of tx array carrier n, activation of rx array carrier n, deactivation of rx array carrier n, and notification for each carrier. The modem 406 may include hardware and software components for implementing the above features, as well as the various other techniques described herein.

[0059] The multi cell O-RU 402 may further comprise one or more processors 408 in communication with the modem 406. The one or more processors 408 (alternatively referred to as processor 408) may be communicatively coupled with a memory 410. The processor 408 may include one or a plurality of processors, including a general-purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), an Application Processor (AP), a dedicated processor, a graphics-only processing unit such as a Graphics Processing Unit (GPU) or the like, a programmable logic device, or any combination thereof. The one or more processors 408 is configured to implement part or all of the features described herein by executing program instructions stored in the memory 410.

[0060] The memory 410 stores the set of instructions required by the processor 408 for controlling its overall operations. The memory 410 may include non-volatile storage elements. Examples of such non-volatile storage elements may includemagnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory 408 may, in some examples, be considered a non-transitory storage medium. The "non-transitory" storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted as the memory 410 is nonmovable. In some examples, the memory 410 may be configured to store larger amounts of information. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0061] The processor 408 is configured to execute instructions stored in the memory 410 and to perform various processes. The processor 408 may also include a plurality of processing engines i.e., information processing units for controlling overall operation of the O-RU 402. For example, the processor 408 is configured to execute programs and other processes stored in the memory 410. The processor 408 is further configured to move data into or out of the memory 410 as required by an execution process.

[0062] The processor 408 may include one or more processing unit(s) / module(s) 412. The one or more modules may include a transceiver module 412-1 and a processing module 412-2. Each of the module(s) 412 is communicatively coupled with each other. The module(s) 412 may comprise Field Programmable Gate Array (FPGA) and / or Application Specific Integrated Circuits (ASICs) for further lower physical layer processing of the signals. Each of the module(s) 412 is communicatively coupled with each other.

[0063] In an embodiment, the module(s) 412 may be implemented as a combination of hardware and software programming (for example, programmable instructions) to implement one or more functionalities of the O-RU 402. In non-limiting examples, described herein, such combinations of hardware and software programming may be implemented in several different ways, without deviatingfrom the scope of the present disclosure. The module(s) 412 may include suitable logic, circuitry, interfaces, and / or codes. For example, the programming for the module(s) 412 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the module(s) 412 may comprise a processing resource (for example, one or more processors), to execute such instructions. In an embodiment, the module(s) 412 may be combined to a single module or each module of the module(s) 412 may be further subdivided into different modules.

[0064] One or more O-DU of the plurality of the O-DU 404 may perform management operations for the multi cell O-RU 402 using a Network Configuration Protocol (NETCONF) based M Plane interface. Each of the plurality of the O-DUs 404 may serve as O-RU controller utilizing NETCONF protocol to communicate with and control a respective cell of the plurality of cells supported by the multi cell O-RU 402. The O-RU controller is a network function that is permitted to control the configuration of the multi cell O-RU. The O-RU controllers may include, but are not limited to, each of the plurality of the O-DU 404, a Network Management System (NMS), an ORAN Service Management and Orchestration function, or other network automation platforms.

[0065] Each of the plurality of O-DU 404 corresponds to NETCONF clients while each cell of the plurality of cells supported by the multi cell O-RU 402 corresponds to a NETCONF server. The NETCONF server is a policy control point in a managed device that terminates the NETCONF protocol and manages interactions with the O-RU’s 402 configuration management information or a datastore that can be maintained at the O-RU. Terms such as “the plurality of the O-DU 404” “the O-RU controller” and "the NETCONF clients” may be used interchangeably throughout the disclosure. Similarly, terms such as “the cell of the O-RU 402” among the plurality of cells of O-RU 402 and "the NETCONF server” may be used interchangeably throughout the disclosure.

[0066] The multi cell O-RU 402 is configured to provide M-plane support for independent management of either the plurality of O-DUs 404 or a single 0-DU 404, when a Control (C) plane and a User (U) plane are flexibly configured to support the single cell or the plurality of cells in a common apparatus of the multi cell O-RU 402.

[0067] Furthermore, the processor 408 utilizes a Yet Another Next Generation (YANG) data model adapted and augmented for cell management and cell traffic monitoring for the plurality of cells simultaneously and independently as part of the common multi cell O-RU 402. Each NETCONF client i.e. each of the plurality of O-DUs 404 may configure the multi cell O-RU 402 for performing one or more of software management functions and fault management functions of a respective cell of the plurality of cells.

[0068] The multi cell O-RU 402 is configured to allow independent monitoring of C / U / S / M plane traffic of each of the plurality of cells. Furthermore, network statistics of each cell of the plurality of cells on each of C / U plane is exchanged with each NETCONF client independently. Additionally, the multi cell O-RU 402 is further configured to manage alarms and counters independently for each of the plurality of cells i.e. an alarm raise time, a clearance time of an alarm, and also recovery action for the alarm on each cell of the plurality of cells is independent. The alarms may include alarms corresponding to faults related to hardware and software related to units of the multi cell O-RU 402 and external devices such as antenna line device. The alarms may include, but not limited to, C / U plane logical connectivity fault, port test failure, synchronization failure with external devices, configuration failed, temperature increase in the O-RU 402. Details of operations performed by the multi cell O-RU 402 for management of network communication between the plurality of cells supported by the multi cell O-RU 402 and the O-DUs 404 are described further below with reference to FIG. 5

[0069] The processor 408, using the processing module 412-2 identifies each cell of the plurality of cells of the communication network supported by the apparatusof the O-RU 402. Each cell may be identified based on an identification information associated with each cell. The identification information may include, but is not limited to, an instance identifier of each cell comprising a hardware serial number extended for each cell of the plurality of cells supported by the multi cell O-RU 402 and a MAC address of the cell.

[0070] Upon identification of the cells, the processor 408 establishes a connection with the plurality of cells of the 0-DU 404 via a physical or a virtual interface. Post establishment of the connection via the physical interface or the virtual interface, the processor 408, using the processing module 412-2 assigns an Internet Protocol (IP) address to one or more fronthaul interfaces of the plurality of cells. The IP address may be assigned for each of the C / U / S fronthaul plane interface. The one or more fronthaul interfaces may operate concurrently over the fronthaul using the Split 7.2x architecture of the ORAN environment. Each fronthaul interface may use a separate logical or physical connections, distinct IP addresses, and dedicated timing protocols. In one embodiment, the multi cell O-RU 402 assigns the IP addresses via Dynamic Host Configuration Protocol (DHCP), using the instance identifier of each cell of the plurality of cells supported by the multi cell O-RU 402. In an embodiment, the IP address may be assigned in one of IPv4 and IPv6 configurations, for example a IPv4 address such as 198.185.0.1. The IP addresses corresponding to each cell may be distinct, for the C / U / S fronthaul plane interface for each cell.

[0071] Further, the processor 408, using the transceiver module 412-1 publishes one or more of the assigned IP addresses and the identification information of each cell of the plurality of cells to the plurality of O-DUs 404. The one or more of the assigned IP addresses and the identification information is published by the multi cell O-RU 402 to the O-DUs 404 for identification of one or more O-DUs available for establishing an independent connection with a respective cell of the plurality of cells, on the same apparatus of the multi cell O-RU 404. The one or more of the assigned IP addresses and the identification information may be published bysending the one or more of the assigned IP addresses and the identification information to the O-DUs 404.

[0072] In one embodiment, upon receiving the published information, the O-DUs 404 send out messaging requests to the plurality of cells at a configured time interval and keep track of responses received for the messaging requests from the plurality of cells. The one or more O-DUs that receive the responses for the messaging requests at the configured time interval are assumed to be available. The one or more O-DUs are assumed to be not available when no responses for the messaging requests from the respective cell are received for during the configured time interval. Based on the availability of the one or more O-DUs among the plurality of O-DUs 404, the processor 408, using the transceiver module 412-1 receives a configuration information associated with each O-DU of the one or more O-DUs for establishing the independent connection with the respective cell. The configuration information includes at least one of a Media Access Control (MAC) address of the respective O-DU among the plurality of O-DUs 404, security information of the respective O-DU, physical port number of the respective O-DU, a hardware address of an ethemet port of the respective O-DU, and a Virtual Local Area Network Identifier (VLAN-ID) of the respective O-DU. The configuration information may be utilized by the respective cell to establish the independent connection with the respective O-DU.

[0073] Upon establishment of the connection, the processor 408, using the processing module 412-2, may initiate a call home session between each cell and the respective O-DU at each fronthaul interface of the one or more fronthaul interfaces. The call home session may be a Network Configuration (NETCONF) protocol -based session between the respective O-DU 404 and the respective cell. The call home session may be established by the O-RU 402 by initiating a connection back to the NMS or the ORU-Controllers 404 to report presence of the O-RU 402, share configuration data, and request further instructions from the O-DUs 404.

[0074] Upon receiving the configuration information associated from each available O-DU, the processor 408, using the processing module 412-2 establishes an independent connection between the respective O-DU and the respective cell via the one or more fronthaul interfaces. For establishment of the call home session on the one or more fronthaul interfaces on each cell of the plurality of cells and the respective the O-DU 404, the NETCONF server and the NETCONF client(s) may have an identical NETCONF call home port configured, to ensure the NETCONF client listens on the same port used by the NETCONF server. The identical home port may be configured by the respective cell using the configuration information of the respective O-DU 404.

[0075] The independent call home session between each cell and respective O-DU 404 via an independent M-plane interface is utilized for management of network communication between the plurality of cells and the plurality of O-DUs 404. Each cell of the plurality of cells is connected to the respective O-DU 404 via a separate M-plane interface. Furthermore, the processor 408, using the processing module 412-2 performs a plurality of operations associated with management of the respective cell via the NETCONF protocol-based session of the one or more fronthaul interfaces, such as over the M plane.

[0076] Post establishment of the call home session, each cell of the plurality of cell may update the configuration information, such as the MAC address of the respective O-DU 404 i.e. the controller of respective cell, in a datastore 414 corresponding to YANG-based data model. The datastore 414 may alternatively be referred to as YANG defined NETCONF configuration datastore. Datastores are system repositories that hold configuration and operational data for YANG-based data model. In one embodiment, a dynamic discovery of MAC address of the respective O-DU 404 for the C / U / S plane interface is performed by each respective cell of the plurality of cells. In another embodiment, the processing module 412-2 may query the datastore 414 and fetch the configuration information of the respective O-DU 404 from the datastore 414. Upon fetching the configuration information, the processing module 412-2 may link the IP address of each fronthaulinterface of the one or more fronthaul interfaces with the configuration information of the respective O-DU 404, for management of data traffic at the one or more fronthaul interfaces such as the C / U / S plane interface.

[0077] For example, for a cell X, the 0-RU 402 assigns an IP address for C-plane fronthaul interface as 192.168.10.1, an IP address for U-plane fronthaul interface as 192.168.10.2, an IP address for S-plane fronthaul interface as 192.168.10.3. The MAC address of the O-DU X connected with the cell X may be fetched from the datastore 414. For example, the MAC address fetched from the datastore 414 is 98-43-FA-28-3C-14. The IP addresses of the C / U / S fronthaul interface are mapped to the O-DU X configuration in the datastore 414. The processor 408, using the processing module 412-2 uses this mapping to route control, user, and sync traffic to the O-DU X from the cell X. The datastore 414 is updated by the respective cell when there is a change in the assigned IP address or the configuration information of the respective O-DU.

[0078] The YANG-based data model is configured to be utilized for managing NETCONF based operations in the M-plane interface between the plurality of cells and the O-DUs 404. In one embodiment, the datastore may correspond to Sysrepo i.e. a YANG-based configuration and operational state data store for Unix or Linux applications.

[0079] Further, the processing module 412-2 is configured to perform a plurality of operations associated with management of the respective cell via the NETCONF protocol -based session of the one or more fronthaul interfaces. The plurality of operations may include, but is not limited to, securing the NETCONF protocolbased session, monitoring the NETCONF protocol-based session, provisioning new management accounts corresponding to one or more cells among the plurality of cells, and performing capability discovery of the respective O-DU over the NETCONF protocol-based session.

[0080] For securing the NETCONF protocol-based session, the processing module 412-2 is configured to authenticate via security protocols based on securityinformation included in the configuration information of the respective O-DU. After the NETCONF protocol-based session is secured between each cell of the plurality of cells and the respective O-DU, the data traffic of the NETCONF protocol-based session is monitored by the processing module 412-2 at each of the one or more fronthaul interfaces between the respective O-DU and the respective cell for determining whether one or more data packets associated with the respective O-DU are received at the respective cell.

[0081] In one embodiment, the C / U plane connection is monitored by the processing module 412-2 for each cell using the data packets received on each interface corresponding to the respective O-DU 404 during a monitoring interval. The monitoring interval may be a pre-defined periodic time interval for monitoring the NETCONF protocol-based session.

[0082] Based on the determination that the one or more data packets associated with the respective O-DU are received at the respective cell during the monitoring interval, the processor 408 monitors each of the one or more fronthaul interfaces corresponding to the respective O-DU and collects O-RAN network statistics for each of the one or more fronthaul interfaces. The processing module 412-2 is configured to report or send the collected network statistics to the respective O-RU controller independently for each cell of the plurality of cells. Further, the multi cell O-RU 402 sends counters for each of the one or more fronthaul interfaces to the O-RU controller via separate notifications for each O-DU 404. In one embodiment, a rate of flow of data packets may be monitored during the monitoring interval and compared with a threshold number of data packets exchanged during the NETCONF protocol-based session during the monitoring interval. The flow of data packets is determined to be persistent when the rate of flow of data packets exceeds the threshold number of data packets.

[0083] In another embodiment, based on the determination that no data packets associated with the respective O-DU are received on any fronthaul interfaces, the processing module 412-2 is configured to raise, at the respective O-DU, one or morealarms corresponding to the respective 0-DU via the NETCONF protocol-based session of each of the one or more fronthaul interfaces.

[0084] The processor 408, using the processing module 412-2, further monitors alarm conditions for each of the plurality of O-DUs 404 independently and raises the alarm individually for the respective 0-DU connected with the respective cell. As the multi cell 0-RU 402 maintains a separate call home session for each cell, an alarm clearance is supported for each individual cell of the plurality of cells connected with the respective 0-DU 404.

[0085] In one embodiment, the processing module 412-2 monitors the alarm conditions and decides if an alarm condition is cell specific, or if an alarm condition is system specific i.e. an alarm corresponding to condition affecting all the cells. The processing module 412-2 determines if the alarm condition is cell specific, then the alarm is raised to an individual cell and if the processing module 412-2 determines that the alarm condition is system specific, then an alarm is raised to all the cells connected to the multi cell 0-RU 402. Similarly, when alarm condition mitigates, and alarm is cleared. At the time of alarm clearance, the processing module 412-2 determines if a resolved condition corresponds to an alarm that is cell specific or system specific. Accordingly, the processing module 412-2 clears the alarm on one or more cells of the plurality of cells.

[0086] Although FIG. 4 shows an exemplary architecture of the multi cell 0-RU 402, in other implementations, the multi cell 0-RU 402 may include fewer components, different components, differently arranged components, or additional components than depicted in FIG. 4. Additionally, or alternatively, one or more components of multi cell 0-RU 402 may perform functions described as being performed by one or more other components of the multi cell O-RU 402.

[0087] FIG. 5 illustrates a flowchart depicting a method 500 for management of communication between the plurality of cells supported at the multi cell O-RU 402 and the plurality of O-DUs 404, in accordance with an embodiment of the present disclosure. The method 500 comprises a series of operations indicated by steps 502through 514. Although method 500 shows example blocks of steps 502 to 514, in some embodiments, the method 500 may include additional steps, fewer steps or steps in different order than those depicted in FIG. 5. In other embodiments, the steps 502-514 may be combined or may be performed in parallel.

[0088] At step 502, the multi cell 0-RU 402, using the processing module 412-2 performs initialization of a transport layer for establishment of a connection at the M-plane interface between the 0-RU controller or a NETCONF client i.e. a cell of the plurality of the cells of 0-DU 404 and the respective NETCONF server 402. For establishing connection of the M-plane, the multi cell 0-RU 402, using the transceiver module 412-1, performs transport layer resolution for assigning the IP address(es) to the one or more fronthaul interfaces of each of the NETCONF client, based on the identification information associated with each cell. The IP address may correspond to, but is not limited to, one or more of a local IP address, remote IP address, gateway address, and subnet mask. Thereafter, one or more of the IP address, the identification information, and other transport layer interface related information is published by the plurality of NETCONF server to the plurality of NETCONF client.

[0089] At 504, the multi cell 0-RU 402, using the processing module 412-2 performs a synchronization of each of the 0-RU controller against a primary reference clock and synchronization of each cell with the respective 0-RU controller for ensuring precise timing and frequency accuracy across the ORAN. The synchronization operation may be performed to the primary reference clock of the ORAN via a Precision Time Protocol (PTP) to ensure that each cell connected with the respective 0-DU 404 transmits and receives signals in perfect alignment with each other and rest of the ORAN.

[0090] Post synchronization of each cell and the respective 0-DU 404, the processing module 412-2 is configured to receive for each cell, an identity of each 0-RU controller included in the configuration information corresponding to each 0-RU controller. The configuration information includes at least one of theMAC address of the respective 0-DU, the security information of the respective O-DU, the physical port number of the respective 0-DU, the hardware address of the ethemet port of the respective 0-DU, and the VLAN-ID of the respective 0-DU.

[0091] At step 506, the processing module 412-2 establishes an independent connection between the respective 0-DU and the respective cell via the one or more fronthaul interfaces. Each cell is configured to update the IP address of each fronthaul interface of the one or more fronthaul interfaces in the datastore 414. The processing module 412-2 is configured to fetch the IP address of each fronthaul interface of the one or more fronthaul interfaces from the datastore 414 and link the IP address of each fronthaul interface of the one or more fronthaul interfaces with the configuration information of the respective O-DU. The processing module 412-2 initiates a NETCONF protocol-based session using the fetched configuration information address received corresponding to each of the 0-RU controller 402. The independent NETCONF protocol-based session between each cell and the respective 0-DU 404 is established by initiating a NETCONF call home operation by each cell to each 0-RU controller 402. Through the call home operation, the processing module 412-2 takes control of configuration and monitoring tasks in the M-plane interface between the NETCONF client and the NETCONF server.

[0092] At step 508, the processing module 412-2 is configured to secure the NETCONF protocol-based session by authenticating via security protocols based on security information of the respective 0-DU included in the configuration information. For securing the connection between the NETCONF client and the NETCONF server by the respective cell, the respective cell, using the processing module 412-2 is configured to secure the established NETCONF protocol-based session using one or more of Secure Shell (SSH) / Transport Control Protocol (TCP) or Transport Layer Security (TLS) protocols. The NETCONF session is secured to ensure that configuration and monitoring data is exchanged securely the NETCONF client and the NETCONF server, thereby preventing unauthorized access.

[0093] At step 510, upon securing the NETCONF session, each O-RU controller and the respective cell of the multi cell O-RU 402 exchange information corresponding to NETCONF capabilities of each of the O-RU controller and the multi cell O-RU 402. The NETCONF capabilities of each of the O-RU controller and the respective cell may include writable-running capability, candidate configuration capability and associated Commit operation, discard change operation, lock, and un-lock operations, confirmed commit capability, cancel commit operation, rollback on error capability, validate capability, startup configuration capability, Uniform Resource Locator (URL) capability, XPATH capability, notifications, and interleave capability.

[0094] At step 512, the processing module 412-2 is configured to monitor each secured NETCONF session between the O-RU controller and the respective cell of the multi cell O-RU 402. The processing module 412-2 operates one or more of supervision timer and notification timer to ensure that the secured NETCONF session to each of NETCONF client is persistent. The supervision operation is performed to ensure that configuration changes, monitoring data, alarms and fault management data, and periodic updates about status of the multi cell O-RU 402 can be continuously exchanged between the O-RU controller and the respective cell of the multi cell O-RU 402.

[0095] At step 514, each of the cell is configured to receive operational parameters from the respective O-DU 404 through the secured NETCONF connection between the O-RU controller and the multi cell O-RU 402. The operational parameters may include, but are not limited to, carrier creation, activation of transmitting carrier, deactivation of transmitting carrier, activation of receiving array carrier, deactivation of receiving array carrier, and notification for each carrier of the respective cell.

[0096] The processing module 412-2 is configured to configure the respective cell by dynamically tuning the apparatus of the O-RU based on the received operational parameters. Each cell supported on the multi cell O-RU 402 is controlled throughthe respective O-DUs 404 through the operational parameters by carrier creation, carrier activation, and carrier de-activation for each of the cell. The operational parameters are utilized by the 0-RU for tuning modem operations of each respective cell. Accordingly, operation of each cell such as a coverage area of the cell and handover of the cell may be tuned for meeting different requirement of the communication network in providing the services to users. Further, in the datastore 414 utilized by the multi cell 0-RU 402, the YANG module is updated to add information of each cell of the plurality of the 0-DU 404 with the MAC address and VLAN Ids at the one or more fronthaul interface. Furthermore, network statistics for each cell of the plurality of cells are sent to each 0-RU controller(s) by the multi cell 0-RU 402 by configuring ORAN specified YANG models. Additionally, the multi cell 0-RU 402 supports fault management for each cell of the plurality of cells independently and simultaneously through a subscription to the YANG notifications.

[0097] FIG. 6 illustrates a flowchart depicting a method for managing cells of the communication network in the ORAN environment, in accordance with an embodiment of the present disclosure. The method 600 comprises a series of operations indicated by steps 602 through 610.

[0098] At step 602, the processor 408, using the processing module 412-2 is configured to identify each cell of the plurality of cells of the communication network supported by the apparatus of the 0-RU based on the identification information associated with each cell. The identification information corresponds to one or more of the instance identifier of each cell, the MAC address of the cell and the unique instance identifier of each cell of the plurality of cell.

[0099] At step 604, the processor 408, using the processing module 412-2 is configured to assign, using the identification information, the Internet Protocol (IP) address to the one or more fronthaul interfaces of each cell of the plurality of cells. The IP address corresponds to one or more of the local IP address, remote IP address, gateway address, and subnet mask.

[0100] At step 606, the processor 408, using the processing module 412-2 is configured to publish the one or more of the IP address and the identification information of each cell to the plurality of O-DUs 404 for identifying one or more O-DUs available for establishing an independent connection with a respective cell of the plurality of cells supported by the multi cell 0-RU 402.

[0101] At step 608, based on the availability of the one or more O-DUs among the plurality of O-DUs, the processor 408, using the transceiver module 412-1, is configured to receive the configuration information associated with each O-DU of the one or more O-DUs for establishing the independent connection with the respective cell. The configuration information includes at least one of the MAC address of the respective O-DU, the security information of the respective O-DU, the physical port number of the respective O-DU, the hardware address of the ethemet port of the respective O-DU, and the VLAN-ID of the respective O-DU.

[0102] At step 610, upon receiving the configuration information from the O-DU, the processor 408, using the processing module 412-2 is configured to establish an independent connection between the respective O-DU and the respective cell via the one or more fronthaul interfaces. Thus, the multi cell O-RU 402 may support a single cell or the plurality of cell simultaneously, based on requirement of the network operator.

[0103] Now, referring to the technical abilities and advantageous effect of the present disclosure, the embodiments disclosed herein provides an apparatus of the O-RU configured to support modelling of the plurality of cells in a single multi cell O-RU 402. Furthermore, the method disclosed herein is leads to full utilization of hardware resources available in the multi cell O-RU 402. The apparatus and the method offer a cost-effective solution in terms of installation and operational cost of supporting and managing the plurality of cells with a single hardware unit of the multi cell O-RU 402. The multi cell O-RU 402 can be deployed as a single high-capacity unit or as multiple reduced capacity units based on deployment types for supporting one or more of the plurality of cells of the O-DU 404 in an ORAN environment.

[0104] Embodiments of the present technology may be described herein with reference to flowchart illustrations of methods and systems according to embodiments of the technology, and / or procedures, algorithms, steps, operations, formulae, or other computational depictions, which may also be implemented as computer program products. In this regard, each block or step of the flowchart, and combinations of blocks (and / or steps) in the flowchart, as well as any procedure, algorithm, step, operation, formula, or computational depiction can be implemented by various means, such as hardware, firmware, and / or software including one or more computer program instructions embodied in computer-readable program code. As will be appreciated, any such computer program instructions may be executed by one or more computer processors, including without limitation a general -purpose computer or special purpose computer, or other programmable processing apparatus to perform a group of operations comprising the operations or blocks described in connection with the disclosed methods.

[0105] Further, these computer program instructions, such as embodied in computer-readable program code, may also be stored in one or more computer-readable memory or memory devices (for example, the memory 410) that can direct a computer processor or other programmable processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory or memory devices produce an article of manufacture including instruction means which implement the function specified in the block(s) of the flowchart(s).

[0106] It will further be appreciated that the term “computer program instructions” as used herein refer to one or more instructions that can be executed by the one or more processors (for example, the processor 408) to perform one or more functions as described herein. The instructions may also be stored remotely such as on a server, or all or a portion of the instructions can be stored locally and remotely.

[0107] Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present invention. The above-describedembodiments are therefore to be construed in all aspects as illustrative and not restrictive.

[0108] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Any combination of the above features and functionalities may be used in accordance with one or more embodiments.

[0109] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosed herein may reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.LIST OF REFERENCE NUMERALS

[0110] The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is:100 - Architecture of ORAN102 - ORAN Central Unit (O-CU)104 - ORAN Distributed Unit (O-DU)106 - ORAN Radio Unit (O-RU)108 - Core Network (CN)110 - Control / User / Synchronization (C / U / S) plane112- Management (M) plane114 - Network Management System200 - Architecture of a traditional O-RU in the ORAN environment 202- Plurality of O-DUs204 - Plurality of O-RUs300 - Exemplary environment of a communication network302 - Core Network (CN)304 - Radio Access Network (RAN)304-1 to 304-N - Plurality of nodes306 - Data network308 - User devices402- O-RU404-1 to 404-N - Plurality of ORAN Distributed Units (O-DUs)406-1 to 406-N - One or more Modulators-Demodulators (Modems) 408 - Processor410 - Memory412 - Processing unit(s) / module(s)412-1 - Transceiver module412-2 - Processing module414 - Datastore500 - Method for management of communication between the plurality of cells supported at the multi cell O-RU and the plurality of O-DUs502- 514 - Operation steps of method 500600 - Method for managing cells of the communication network in the ORAN environment602- 610 - Operation steps of method 600

Claims

WE CLAIM:

1. A method (600) for managing cells of a communication network in an Open Radio Access Network (ORAN) environment, the method (600) comprising: identifying, by a processing module (412-2) of an ORAN Radio Unit (O- RU) (402), each cell of a plurality of cells of the communication network supported by an apparatus of the O-RU (402) based on an identification information associated with each cell;assigning, by the processing module (412-2) using the identification information, an Internet Protocol (IP) address to one or more fronthaul interfaces of each cell of the plurality of cells;publishing, by a transceiver module (412-1) of the O-RU (402), one or more of the IP address and the identification information of each cell to a plurality of ORAN Distributed Units (O-DUs) (404) for identifying one or more O-DUs available for establishing an independent connection with a respective cell of the plurality of cells supported by the O-RU (402);receiving, by the transceiver module (412-1) based on the availability of the one or more O-DUs among the plurality of O-DUs (404), a configuration information associated with each O-DU of the one or more O-DUs for establishing the independent connection with the respective cell; and establishing, by the processing module (412-2) upon receiving the configuration information from the O-DU, the independent connection between the respective O-DU and the respective cell via the one or more fronthaul interfaces.

2. The method (600) as claimed in claim 1, the method (600) comprising:fetching, by the processing module (412-2), the configuration information of the respective O-DU updated by the respective cell in a datastore corresponding to a Yet Another Next Generation (YANG)-based data model; andlinking, by the processing module (412-2), the IP address of each fronthaul interface of the one or more fronthaul interfaces with the configuration information of the respective O-DU.

3. The method (600) as claimed in claim 1, the method (600) comprising:initiating, by the processing module (412-2) upon establishment of the connection, a Network Configuration (NETCONF) protocol -based session between the respective O-DU and the respective cell at each fronthaul interface of the one or more fronthaul interfaces; andperforming, by the processing module (412-2), a plurality of operations associated with management of the respective cell via the NETCONF protocolbased session of the one or more fronthaul interfaces.

4. The method (600) as claimed in claim 3, wherein the plurality of operations comprises:securing, by the processing module (412-2), the NETCONF protocolbased session by authenticating via security protocols based on security information of the respective O-DU included in the configuration information; andexchanging, by the transceiver module (412-1), between the respective O-DU and the respective cell via the secured NETCONF protocol-based session, capability information corresponding to NETCONF capabilities of each of the respective O-DU and the respective cell.

5. The method (600) as claimed in claim 4, wherein the plurality of operations further comprises:receiving, by the transceiver module (412-1), via the secured NETCONF protocol-based session, operational parameters of the respective cell from the respective O-DU upon determining persistent flow of the data traffic during the NETCONF protocol-based session; andconfiguring, by the processing module (412-2), the respective cell by dynamically tuning the apparatus of the O-RU (402) based on the received operational parameters.

6. The method (600) as claimed in claim 3, wherein the plurality of operations further comprises one or more of:monitoring, by the processing module (412-2), data traffic of the NETCONF protocol-based session at each of the one or more fronthaul interfaces between the respective O-DU and the respective cell for determining whether one or more data packets associated with the respective O-DU are received at the respective cell;sending, by the processing module (412-2) to the respective O-DU, network statistics corresponding to the respective O-DU based on the determination that the one or more data packets associated with the respective O-DU are received at the respective cell via the NETCONF protocol-based session of each of the one or more fronthaul interfaces; andraising, by the processing module (412-2), at the respective O-DU, one or more alarms corresponding to the respective O-DU based on the determination that no data packets are received at the respective cell via the NETCONF protocol-based session of each of the one or more fronthaul interfaces.

7. The method (600) as claimed in claim 1, wherein the configuration information includes at least one of a Media Access Control (MAC) address of the respective O-DU, security information of the respective O-DU, physical port number of the respective O-DU, a hardware address of an ethemet port of the respective O-DU, and a Virtual Local Area Network Identifier (VLAN-ID) of the respective O- DU.

8. An apparatus of an Open Radio Access Network (ORAN) Radio Unit (O-RU) (402) for managing cells of a communication network in an ORAN environment, the apparatus comprising:a processing module (412-2) configured to:identify each cell of a plurality of cells of the communication network supported by the apparatus of the 0-RU based on an identification information associated with each cell; andassign, using the identification information, an Internet Protocol (IP) address to one or more fronthaul interfaces of each cell of the plurality of cells; anda transceiver module (412-1) configured to:publish one or more of the IP address and the identification information of each cell to a plurality of ORAN Distributed Units (O-DUs) (404) for identifying one or more O-DUs available for establishing an independent connection with a respective cell of the plurality of cells supported by the 0-RU (402); andreceive, based on the availability of the one or more O-DUs among the plurality of O-DUs (404), a configuration information associated with each O- DU of the one or more O-DUs for establishing the independent connection with the respective cell, wherein the processing module (412-2) is configured to establish, upon receiving the configuration information from the O-DU, the independent connection between the respective O-DU and the respective cell via the one or more fronthaul interfaces.

9. The apparatus as claimed in claim 8, wherein the processing module (412-2) is further configured to:fetch the configuration information of the respective O-DU updated by the respective cell in a datastore corresponding to a Yet Another Next Generation (YANG)-based data model; andlink the IP address of each fronthaul interface of the one or more fronthaul interfaces with the configuration information of the respective O-DU.

10. The apparatus as claimed in claim 8, wherein the processing module (412-2) is further configured to:initiate, upon establishment of the connection, a Network Configuration (NETCONF) protocol -based session between the respective O-DU and the respective cell at each fronthaul interface of the one or more fronthaul interfaces; andperform a plurality of operations associated with management of the respective cell via the NETCONF protocol-based session of the one or more fronthaul interfaces.

11. The apparatus as claimed in claim 10, wherein for performing the plurality of operations, the processing module (412-2) is further configured to:secure the NETCONF protocol-based session by authenticating via security protocols based on security information of the respective 0-DU included in the configuration information, wherein the transceiver module (412- 1) is configured to exchange, between the respective O-DU and the respective cell via the secured NETCONF protocol-based session, capability information corresponding to NETCONF capabilities of each of the respective 0-DU and the respective cell.

12. The apparatus as claimed in claim 11, wherein for performing the plurality of operations, the transceiver module (412-1) is further configured to:receive, via the secured NETCONF protocol-based session, operational parameters of the respective cell from the respective O-DU upon determining persistent flow of the data traffic during the NETCONF protocol-based session, wherein the processing module (412-2) is configured to configure the respective cell by dynamically tuning the apparatus of the O-RU (402) based on the received operational parameters.

13. The apparatus as claimed in claim 10, wherein for performing the plurality of operations, the processing module (412-2) is further configured to:monitor data traffic of the NETCONF protocol-based session at each of the one or more fronthaul interfaces between the respective O-DU and the respective cell for determining whether one or more data packets associated with the respective O-DU are received at the respective cell;send, to the respective O-DU, network statistics corresponding to the respective O-DU based on the determination that the one or more data packetsassociated with the respective 0-DU are received at the respective cell via the NETCONF protocol-based session of each of the one or more fronthaul interfaces; andraise, at the respective O-DU, one or more alarms corresponding to the respective O-DU based on the determination that no data packets are received at the respective cell via the NETCONF protocol-based session of each of the one or more fronthaul interfaces.

14. The apparatus as claimed in claim 10, wherein the configuration information includes at least one of a Media Access Control (MAC) address of the respective O-DU, security information of the respective O-DU, physical port number of the respective O-DU, a hardware address of an ethemet port of the respective O-DU, and a Virtual Local Area Network Identifier (VLAN-ID) of the respective O- DU.

15. A computer program product for managing cells of a communication network in an Open Radio Access Network (ORAN) environment, the computer program product comprising computer-executable instructions that are stored on a non- transitory computer-readable medium and that, when executed by at least one processor performs operations comprising:identifying, by an ORAN Radio Unit (0-RU), each cell of a plurality of cells of the communication network supported by an apparatus of the 0-RU based on an identification information associated with each cell;assigning, using the identification information, an Internet Protocol (IP) address to one or more fronthaul interfaces of each cell of the plurality of cells;publishing one or more of the IP address and the identification information of each cell to a plurality of ORAN Distributed Units (O-DUs) for identifying one or more O-DUs available for establishing an independent connection with a respective cell of the plurality of cells supported by the ORU;receiving, based on the availability of the one or more O-DUs among the plurality of O-DUs (404), a configuration information associated with eachO-DU of the one or more O-DUs for establishing the independent connection with the respective cell; andestablishing, upon receiving the configuration information from the O-DU, the independent connection between the respective O-DU and the respective cell via the one or more fronthaul interfaces.

Images