FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR MANAGING RADIO UNIT
(RU) INSTANCE IDENTIFICATION IN A
TELECOMMUNICATION NETWORK”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR MANAGING RADIO UNIT (RU) INSTANCE IDENTIFICATION IN A TELECOMMUNICATION
NETWORK
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to wireless communication systems. More particularly, embodiments of the present disclosure relate to methods and systems for managing Radio Unit (RU) instance identification in a telecommunication network.
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect

multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] In 5G networks, a radio unit (RU) is a key component responsible for transmitting and receiving wireless signals over the air interface. The RU plays a crucial role in connecting user devices to the network infrastructure and facilitating high-speed data transfer, low-latency communication, and efficient resource allocation. It includes radio transceivers, antennas, and signal processing capabilities to operate within a specific frequency range. RUs are typically deployed at base stations or cell sites and are responsible for handling the wireless communication between the network and user devices, enabling reliable and robust connectivity in 5G networks.
[0005] In the current existing solutions, managing RU infrastructure becomes increasingly challenging. Further, during the startup process of the radio unit (RU), it does not possess Cell Number (cNUM) or cell identification ID information. The cNUM or the cell identification ID information is a unique identifier that is assigned to each cell tower by a cellular network. The cNUM or the cell identification ID information is utilized to distinguish one cell tower from another cell tower. Consequently, the detection of instance ID mismatches has been restricted to the site level only. The mismatches refer to discrepancies or inconsistencies in the configuration and identification of one or more radio units and their associated cells or sectors. However, currently there is a discrepancy in the assigned / matched sectors of the RU, and the same is not being addressed or dealt with.
[0006] Additionally in the current existing solution, the RU instance ID which is a serial number that serves as a means of identification and allows for tracking and management of individual RUs throughout their lifecycle is reported through a Management Plane (M-Plane) to the Next Generation NodeB (gNB) and then to the

Element Management System (EMS) through operation, administration, and maintenance (OAM) protocol.
[0007] The M-Plane refers to a Management Plane in a telecommunication network architecture which is one of the three functional planes in a network, alongside the Data Plane and Control Plane. The M-Plane is responsible for handling management functions, including network monitoring, configuration management, performance management, fault management, and security management. The M-Plane facilitates communication between a plurality of network elements and management systems for allowing one or more operators to monitor and control network operations efficiently. The M-Plane also plays a role in ensuring the smooth operation and optimization of telecommunication networks.
[0008] The gNB is the base station that connects user devices (UEs) to the core network and handles tasks such as radio resource management, mobility management, and connection establishment for 5G wireless communication. The EMS is a network management system used to manage individual network elements, such as routers, switches, and base stations, within a telecommunication network. The EMS provides functions for configuration, monitoring, performance analysis, fault detection, and software updates for one or more network elements. Additionally, the OAM protocol includes one or more rules, one or more instructions for managing one or more network elements that are present in the network.
[0009] In cases of RU ID mismatch with a configured ID, during deployment, an alarm or flag is generated for RU instance ID mismatch. However, this detection occurred at the site level rather than the sector level, resulting in deployment delays and additional costs.
[0010] Thus, there exists an imperative need in the art for a method and system for managing Radio Unit (RU) instance identification in a telecommunication network.

SUMMARY
[0011] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0012] An aspect of the present disclosure may relate to a method for managing Radio Unit (RU) instance identification in a telecommunication network. The method comprises receiving, by a transceiver unit, one or more instance identifiers (IDs) associated with one or more RUs. The method comprises mapping, by a mapping unit, the one or more RUs to one or more sectors based on the received one or more instance IDs. The method comprises periodically polling, by a processing unit, the one or more RUs for retrieving the mapped one or more instance IDs and sector information. The method comprises comparing, by a comparing unit, the retrieved one or more instance IDs with the mapped one or more RUs. The method comprises generating, by an alerting unit, an alert in case there is a mismatch between the retrieved one or more instance IDs with the mapped one or more RUs. The method comprises updating, by a storing unit, the mapped one or more RUs in a configuration database.
[0013] In an exemplary aspect of the present disclosure, the mapping is maintained by at least one of a network management system (NMS) or a Distributed Unit (DU).
[0014] In an exemplary aspect of the present disclosure, the generated alert comprises an information about affected one or more sectors and one or more RUs.
[0015] In an exemplary aspect of the present disclosure, the method further comprising transmitting, by the transceiver unit, the mapped one or more instance IDs and sector information to an Element Management System (EMS).

[0016] In an exemplary aspect of the present disclosure, the updating of the mapped one or more RUs in the configuration database comprises correcting a serial number of the one or more RUs at the EMS in an event of an incorrect installation.
[0017] In an exemplary aspect of the present disclosure, the method further comprises allocating, by an allocating unit, a unique IP address to the RU instance by a Dynamic Host Configuration Protocol (DHCP) server, wherein the RU instance receives the RU instance ID and the allocated unique IP address from the DHCP server.
[0018] In an exemplary aspect of the present disclosure, the periodic polling is performed using a management plane (M-Plane) protocol.
[0019] Another aspect of the present disclosure may relate to a system for managing Radio Unit (RU) instance identification in a telecommunication network. The system comprises a transceiver unit configured to receive one or more instance identifiers (IDs) associated with one or more RUs. The system comprises a mapping unit configured to map the one or more RUs to one or more sectors based on the received one or more instance IDs. The system comprises a processing unit configured to periodically poll the one or more RUs for retrieving the mapped one or more instance IDs and sector information. The system comprises a comparing unit configured to compare the retrieved one or more instance IDs with the mapped one or more RUs. The system comprises an alerting unit configured to generate an alert in case there is a mismatch between the retrieved one or more instance IDs with the mapped one or more RUs. The system comprises a storing unit configured to update the mapped one or more RUs in a configuration database.
[0020] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for managing Radio Unit

(RU) instance identification in a telecommunication network, the instructions
include executable code which, when executed by one or more units of a system,
causes: a transceiver unit of the system to receive one or more instance identifiers
(IDs) associated with one or more RUs; a mapping unit of the system to map the
5 one or more RUs to one or more sectors based on the received one or more instance
IDs; a processing unit of the system to periodically poll the one or more RUs for
retrieving the mapped one or more instance IDs and sector information; a
comparing unit of the system to compare the retrieved one or more instance IDs
with the mapped one or more RUs; an alerting unit of the system to generate an
10 alert in case there is a mismatch between the retrieved one or more instance IDs
with the mapped one or more RUs; and a storing unit of the system to update the mapped one or more RUs in a configuration database.
OBJECTS OF THE INVENTION
15
[0021] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0022] It is an object of the present disclosure to provide a system and a method for
20 managing Radio Unit (RU) instance identification in a telecommunication network.
[0023] It is another object of the present disclosure to provide a system and a method for an efficient process within an Open Radio Access Network (ORAN) system to accurately identify and rectify RU ID mismatches. 25
[0024] It is another object of the present disclosure to provide a solution that effectively manages the accurate identification (ID) of RUs within the ORAN system at the sector level.
7

[0025] It is another object of the present disclosure to provide a solution that detects and resolves RU ID mismatches for minimizing deployment delays and improving an operational efficiency.
5 [0026] It is another object of the present disclosure to provide a solution that
ensures a precise identification of RUs at a sector level for seamless integration and optimal resource allocation.
DESCRIPTION OF THE DRAWINGS
10
[0027] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale,
15 emphasis instead being placed upon clearly illustrating the principles of the present
disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such
20 drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
[0028] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture.
25
[0029] FIG. 2 illustrates a block diagram of an exemplary arrangement of a
Network Management System (NMS) and an Outdoor Unit (ODU) architecture.
[0030] FIG. 3 illustrates an exemplary block diagram of a computing device upon
30 which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure.
8

[0031] FIG. 4 illustrates an exemplary block diagram of a system for managing Radio Unit (RU) instance identification in a telecommunication network, in accordance with exemplary implementations of the present disclosure.
5 [0032] FIG. 5 illustrates flow diagram of a method depicting a process for
managing Radio Unit (RU) instance identification in a telecommunication network in accordance with exemplary implementations of the present disclosure.
[0033] FIG. 6. illustrates an exemplary flow diagram of a method depicting an
10 Internet Protocol (IP) binding process, in accordance with exemplary
implementations of the present disclosure.
[0034] FIG. 7 illustrates an exemplary block diagram of a network environment for
managing Radio Unit (RU) instance identification in a telecommunication network
15 in accordance with exemplary implementations of the present disclosure.
[0035] The foregoing shall be more apparent from the following more detailed description of the disclosure.
20 DETAILED DESCRIPTION
[0036] 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
25 embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
30
[0037] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather,
9

the ensuing description of the exemplary embodiments will provide those skilled in
the art with an enabling description for implementing an exemplary embodiment.
It should be understood that various changes may be made in the function and
arrangement of elements without departing from the spirit and scope of the
5 disclosure as set forth.
[0038] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of
ordinary skill in the art that the embodiments may be practiced without these
10 specific details. For example, circuits, systems, processes, and other components
may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0039] Also, it is noted that individual embodiments may be described as a process
15 which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
diagram, or a block diagram. Although a flowchart may describe the operations as
a sequential process, many of the operations may be performed in parallel or
concurrently. In addition, the order of the operations may be re-arranged. A process
is terminated when its operations are completed but could have additional steps not
20 included in a figure.
[0040] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any
25 aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed
30 description or the claims, such terms are intended to be inclusive—in a manner
10

similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0041] As used herein, a “processing unit” or “processor” or “operating processor”
5 includes one or more processors, wherein processor refers to any logic circuitry for
processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific
10 Integrated Circuits, Field Programmable Gate Array circuits, any other type of
integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
15
[0042] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device
20 or equipment, capable of implementing the features of the present disclosure. The
user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may
25 contain at least one input means configured to receive an input from unit(s) of a
telecommunication network.
[0043] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a
30 form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”),
11

magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions. 5
[0044] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with
10 each other, which also includes the methods, functions, or procedures that may be
called.
[0045] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a
15 general-purpose processor, a special purpose processor, a conventional processor,
a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
20
[0046] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
25
[0047] As used herein the term “Open Radio Access Network (ORAN)” refers to a network architecture initiative that promotes openness, interoperability, and innovation in radio access networks (RANs). The ORAN enables better flexibility and efficiency in the deployment and operation of RAN infrastructure by
30 standardizing interfaces, embracing virtualization and software-defined networking
12

(SDN) principles, and encouraging disaggregation of hardware and software components.
[0048] As used herein the "RU instance" refers to a specific occurrence or
5 instantiation of a Radio Unit (RU) within the network. Each RU instance represents
an individual unit or device deployed within the telecommunication network
infrastructure. The term "RU instance" is used to distinguish between multiple RUs
that may be deployed throughout the network. Each RU instance is assigned a
unique identifier, known as the RU instance ID, to differentiate it from other
10 instances within the network.
[0049] As discussed in the background section, in current times, there exists a significant challenge in managing an infrastructure of a Radio Unit (RU) as during a startup phase of an RU, there is a lack in an essential Cell Number (cNUM) or
15 cell identification ID information which limits the detection of instance ID
mismatches to the site level, wherein the instance ID mismatches refers to a situation where there is a disparity or inconsistency between the expected or configured instance identification information of the radio unit and its actual instance. Hence, the current known solutions have several shortcomings. The
20 present disclosure aims to overcome the above-mentioned and other existing
problems in this field of technology by providing method and system for managing Radio Unit (RU) instance identification in a telecommunication network which effectively manages the accurate identification (ID) of the RUs within an Open Radio Access Network (ORAN) system at a sector level. Further, the method and
25 system of the present disclosure detects one or more incorrect installations at a site
and generates an alarm. Further in response to the alarm information rectification is done regarding the RUs, which results in seamless deployment, enhanced operations, cost optimization and improved scalability and future-proofing.
30 [0050] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture, in accordance with exemplary
13

implementation of the present disclosure. As shown in FIG. 1, the 5GC network
architecture [100] includes a user equipment (UE) [102], a radio access network
(RAN) [104], an access and mobility management function (AMF) [106], a Session
Management Function (SMF) [108], a Service Communication Proxy (SCP) [110],
5 an Authentication Server Function (AUSF) [112], a Network Slice Specific
Authentication and Authorization Function (NSSAAF) [114], a Network Slice
Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a
Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122],
a Unified Data Management (UDM) [124], an application function (AF) [126], a
10 User Plane Function (UPF) [128], a data network (DN) [130], wherein all the
components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
[0051] Radio Access Network (RAN) [104] is the part of a mobile
15 telecommunications system that utilises one or more radio units (RUs) [702a, 702b,
702c] (collectively numbered as [702]), and connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
20
[0052] Access and Mobility Management Function (AMF) [106] is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
25
[0053] Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
30
14

[0054] Service Communication Proxy (SCP) [110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces. 5
[0055] Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
10 [0056] Network Slice Specific Authentication and Authorization Function
(NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
15 [0057] Network Slice Selection Function (NSSF) [116] is a network function
responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
[0058] Network Exposure Function (NEF) [118] is a network function that exposes
20 capabilities and services of the 5G network to external applications, enabling
integration with third-party services and applications.
[0059] Network Repository Function (NRF) [120] is a network function that acts
as a central repository for information about available network functions and
25 services. It facilitates the discovery and dynamic registration of network functions.
[0060] Policy Control Function (PCF) [122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies. 30
15

[0061] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
5 [0062] Application Function (AF) [126] is a network function that represents
external applications interfacing with the 5G core network to access network capabilities and services.
[0063] User Plane Function (UPF) [128] is a network function responsible for
10 handling user data traffic, including packet routing, forwarding, and QoS
enforcement.
[0064] Data Network (DN) [130] refers to a network that provides data services to
user equipment (UE) in a telecommunications system. The data services may
15 include but are not limited to Internet services, private data network related services.
[0065] FIG. 2 illustrates a block diagram of an exemplary arrangement of a
Network Management System (NMS) and an Outdoor Unit (ODU) architecture.
The NMS and ODU architecture [200] comprises an NMS [202] that refers to a
20 central system for monitoring, managing and maintaining one or more network
resources and performance. The NMS [202] interfaces with an ODU [204] to gather a performance data, configure one or more settings and mange one or more faults.
[0066] Further, the ODU [204] include two planes i.e. Control, User and
25 Synchronization Plane Specification (CUS) plane [206] and a Management plane
(M-Plane) [208]. The CUS plane [206] is a multifunctional plane and transfer one
or more control signals and user data respectively. The M-Plane [208] refers to a
Management Plane in a telecommunication network architecture which is one of
the three functional planes in a network, alongside a data plane and a control plane.
30 The M-Plane [208] is responsible for handling management functions, including
network monitoring, configuration management, performance management, fault
16

management, and security management. The M-Plane [208] facilitates
communication between a plurality of network elements and management systems
for allowing one or more operators to monitor and control network operations
efficiently. The M-Plane [208] also plays a role in ensuring the smooth operation
5 and optimization of telecommunication networks.
[0067] The ODU [204] is further connected to a fronthaul (FH) network [210]. The FH network [210] is responsible for transmitting a data between the ODU [204] and other network elements. 10
[0068] Further, the FH network [210] is connected to a Secure File Transfer Protocol (SFTP) client file manager [212] and a Network Configuration Protocol (NETCONF) server configuration manager [214].
15 [0069] The SFTP client file manager [212] is used for securing one or more file
transfers (i.e. data transfer) within the network. The NETCONF server configuration manager [214] is responsible for managing one or more network device configuration.
20 [0070] Further, the SFTP client file manager [212] and the NETCONF server
configuration manager [214] is connected to a message broker [216]. The message broker [216] acts as a middleware component which facilitates a message transmission between different modules within the ODU [204].
25 [0071] The message broker [216] may be based on 0MQ, which facilitates the
communication between the different modules. More particularly, 0MQ is a lightweight messaging library which provides high-performance asynchronous messaging across one or more transport protocols. The message broker [216] based on 0MQ support one or more transport protocols such as Transmission Control
30 Protocol (TCP) and User Datagram Protocol (UDP). Additionally, the message
broker [216] based on 0MQ support one or more asynchronous message patterns,
17

in which the message broker [216] allows one or more messages to be sent and received without requiring a direct synchronous connection between a sender and a receiver.
5 [0072] The message broker [216] is further connected with a plurality of functional
blocks. The plurality of functional blocks includes but is not limited to a logging unit [218], a performance manager [220], a supervision unit [222], a Software (SW) manager [224], a user manager [226], and a fault manager [228].
10 [0073] The logging unit [218] may keep a record of one or more events and one or
more activities for troubleshooting and auditing purposed. Further, the performance manager [220] may monitor and manage a performance of the network, via processing the record of the one or more events and the one or more activities. Further, the supervision unit [222] may optionally monitor the network for
15 addressing one or more issue. The SW manager [224] is responsible for managing
one or more software components associated with one or more network devices. The SW manager [224] also handle one or more update related operations and maintenance related operations. Furthermore, the user manager [226] that is optional functional block that may be responsible to manage one or more user
20 access and one or more permissions within the network. Further, the fault manager
[228] is responsible to detect, log and manage one or more faults within the network for ensuring reliability.
[0074] FIG. 3 illustrates an exemplary block diagram of a computing device [300]
25 upon which the features of the present disclosure may be implemented in
accordance with exemplary implementation of the present disclosure. In an
implementation, the computing device [300] may also implement a method for
message routing management. In another implementation, the computing device
[300] itself implements the method for message routing management using one or
30 more units configured within the computing device [300], wherein said one or more
units are capable of implementing the features as disclosed in the present disclosure.
18

[0075] The computing device [300] may include a bus [302] or other
communication mechanism for communicating information, and a hardware
processor [304] coupled with bus [302] for processing information. The hardware
5 processor [304] may be, for example, a general-purpose microprocessor. The
computing device [300] may also include a main memory [306], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [302] for storing information and instructions to be executed by the processor [304]. The main memory [306] also may be used for storing temporary variables or other
10 intermediate information during execution of the instructions to be executed by the
processor [304]. Such instructions, when stored in non-transitory storage media accessible to the processor [304], render the computing device [300] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [300] further includes a read only memory
15 (ROM) [308] or other static storage device coupled to the bus [302] for storing static
information and instructions for the processor [304].
[0076] A storage device [310], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [302] for storing information and
20 instructions. The computing device [300] may be coupled via the bus [302] to a
display [312], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [314], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the
25 bus [302] for communicating information and command selections to the processor
[304]. Another type of user input device may be a cursor controller [316], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [304], and for controlling cursor movement on the display [312]. This input device typically has two degrees
30 of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
the device to specify positions in a plane.
19

[0077] The computing device [300] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
and/or program logic which in combination with the computing device [300] causes
5 or programs the computing device [300] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the computing device [300] in response to the processor [304] executing one or more sequences of one or more instructions contained in the main memory [306]. Such instructions may be read into the main memory [306] from another storage medium,
10 such as the storage device [310]. Execution of the sequences of instructions
contained in the main memory [306] causes the processor [304] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
15
[0078] The computing device [300] also may include a communication interface [318] coupled to the bus [302]. The communication interface [318] provides a two-way data communication coupling to a network link [320] that is connected to a local network [322] and the local network [322] is further connected to the host
20 [324]. For example, the communication interface [318] may be an integrated
services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [318] may be a local area network (LAN) card to provide a data communication connection to a compatible
25 LAN. Wireless links may also be implemented. In any such implementation, the
communication interface [318] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
30 [0079] The computing device [300] can send messages and receive data, including
program code, through the network(s), the network link [320] and the
20

communication interface [318]. In the Internet example, a server [330] might
transmit a requested code for an application program through the Internet [328], the
ISP [326], the local network [322] and the communication interface [318]. The
received code may be executed by the processor [304] as it is received, and/or stored
5 in the storage device [310], or other non-volatile storage for later execution.
[0080] Referring to FIG. 4, an exemplary block diagram of a system [400] for managing Radio Unit (RU) instance identification in a telecommunication network is shown, in accordance with the exemplary implementations of the present
10 disclosure. The system [400] comprises at least one transceiver unit [402], at least
one mapping unit [404], at least one processing unit [406], at least one comparing unit [408], at least one alerting unit [410], at least one storing unit [412] and at least one allocating unit [414]. Also, all of the components/ units of the system [400] are assumed to be connected to each other unless otherwise indicated below. As shown
15 in the figures all units shown within the system should also be assumed to be
connected to each other. Also, in FIG. 4 only a few units are shown, however, the system [400] may comprise multiple such units or the system [400] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
20
[0081] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various
25 configurations and combinations thereof are within the scope of the disclosure. The
functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope
30 of the present disclosure.
21

[0082] The system [400] is configured to manage Radio Unit (RU) instance identification in a telecommunication network with the help of the interconnection between the components/units of the system [400].
5 [0083] In order to manage the RU instance identification in a telecommunication
network, the transceiver unit [402] is configured to receive one or more instance identifiers (IDs) that are associated with one or more RUs [702]. As used herein a “radio unit (RU)” refers to a component or device within a telecommunication network responsible for transmitting and/or receiving radio signals. The radio unit
10 plays a role in facilitating communication between network devices and end-user
devices for ensuring an efficient and reliable operation of the network. The present disclosure encompasses that the one or more instance identifiers (IDs) refers to unique identification number(s) or code(s) which are associated with individual RUs. For instance, the one or more instance identifiers (IDs)
15 corresponding to an RU may distinguish said RU from other RU in a same network.
Additionally, each ID from the one or more instance identifiers (IDs) may have a unique value. The unique value may include numeric value, alpha numeric value, alphabetic value such as 00942391.
20 [0084] Further, the mapping unit [404] is at least connected to the transceiver unit
[402] and the mapping unit [404] is configured to map the one or more RUs [702] to one or more sectors (such as sector 1, sector 2 and sector 3 for a RU [702a] as depicted in FIG. 1) based on the received one or more instance IDs.
25 [0085] Also, as used herein the one or more sectors refers to a division of a cellular
coverage area into a plurality of directional zones such as sector 1, sector 2 and sector 3 associated with the RU [702a] (as depicted in FIG. 1). The sector represents a specific angular range of coverage within a cell. Further, it is to be noted that the depiction of sectors (i.e., sector 1, sector 2 and sector 3 associated with the RU
30 [702a]) in FIG. 1 is exemplary in nature and should not be interpreted in a manner
to limit the scope of the disclosure.
22

[0086] More specifically, the mapping of the one or more RUs [702] to the one or
more sectors refers to association of the one or more RUs with specific one or more
sectors within the telecommunication network (or may be used herein as “network”
5 / “communication network”) based on the one or more instance IDs. Moreover, in
an implementation this mapping may be done by the mapping unit [404] via
utilizing one or more protocols which may be obvious to the person skilled in the
art for implementing the features of the present disclosure. Additionally, the
mapping ensures that each RU is correctly identified and assigned to the appropriate
10 sector for facilitating an efficient network operation and management.
[0087] The present disclosure encompasses that the mapping is maintained by at
least one of a network management system (NMS) [202] and a Distributed Unit
(DU) [704]. Therefore, in an instance the mapping unit [404] is configured at, at
15 least one of the network management system (NMS) [202] and the Distributed Unit
(DU) [704] for maintenance of the mapping. In other words, the mapping is updated or kept consistent by help of the NMS [202] and the DU [704].
[0088] The NMS [202] is a platform that enables monitoring, controlling and
20 managing of one or more components within the network. The NMS [202] is a tool
or a device that provides access of one or more tools and one or more interfaces to
a network administrator for handling one or more operations, performance and
configurations of plurality of network devices and services. Also, the NMS [202]
provides functionalities that include but not limited to device discovery, fault
25 detection, performance monitoring, configuration management, and security
management. The NMS [202] may perform one or more tasks for maintaining the
mapping of the one or more RUs [702]. The one or more tasks include but are not
limited to configuration management, monitoring and updating. For instance, the
NMS [202] may continuously monitors a status of each RU [702] and accordingly
30 updates the corresponding mapping.
23

[0089] The present disclosure encompasses that the DU [704] is a network element
which is responsible for processing and forwarding a data within a radio access
network (RAN). The DU [704] is generally located closer to the network edge and
near the cell sites or base stations and handles one or more tasks such as radio signal
5 processing, protocol termination and traffic aggregation. The DU [704] may
perform one or more tasks for maintaining the mapping of the one or more RUs
[702]. The one or more tasks include but are not limited to local configuration
management, status synchronization. For instance, the DU [704] may manage the
mapping of each RU [702] within the network and ensures that the corresponding
10 mapping is synchronized with the mapping stored or saved in the NMS [202].
[0090] Further, the processing unit [406] is connected to at least with the mapping
unit [404] and the processing unit [406] is configured to periodically poll the one
or more RUs [702] for retrieving the mapped one or more instance IDs and a sector
15 information.
[0091] For instance, the processing unit [406] is configured to periodically poll the
RUs within the network, which means that the processing unit [406] requests to the
RUs at pre-defined intervals to obtain information such as instance IDs and sector
20 information.
[0092] The present disclosure encompasses that the periodic polling is performed using a management plane (M-Plane) protocol.
25 [0093] The M-Plane protocol is a communication protocol that enable exchange of
management related information and commands for management purpose among radio units (RUs). Further, the M-Plane protocol ensures an efficient and standardized communication for retrieval of accurate instance IDs and a sector information.
30
24

[0094] The present disclosure encompasses that once the mapped one or more instance IDs and the sector information are retrieved the transceiver unit [402] is further configured to transmit the mapped one or more instance IDs and the sector information to an Element Management System (EMS). 5
[0095] The present disclosure encompasses that the EMS is utilized to manage and
monitor one or more network elements or devices. The EMS provides a centralized
control and oversight of the one or more network elements such as switches, routers,
base stations and RUs. For instance, the transmission of the mapped instance IDs
10 and sector information to the EMS allows the EMS to receive a real-time data about
the RUs and their associated sectors which enable the network administrator to monitor and manage the network more effectively.
[0096] Further, the comparing unit [408] is connected at least with the processing
15 unit [406], the comparing unit [408] is configured to compare the retrieved one or
more instance IDs with the mapped one or more RUs [702]. The comparison between the retrieved instance IDs and the mapped Radio Units (RUs) is achieved through a process that involves the comparing unit examining each retrieved instance ID and comparing the retrieved instance ID to the mapped RUs within the
20 telecommunication network. If an exact match is found between a retrieved instance
ID and a mapped RU, the comparison is deemed successful. Conversely, if no exact match is found, it is considered a mismatch. The comparison enables the comparing unit to identify any discrepancies between the expected and actual instances of RUs in the network.
25
[0097] The present disclosure encompasses that the comparison between the retrieved one or more instance IDs with the mapped one or more RUs [702] results in a successful match or a mismatch. In addition to this, when the retrieved one or more instance IDs exactly matches with the mapped one or more RUs [702] then it
30 is considered as a successful match or else it is considered as a mismatch.
25

[0098] Further, the alerting unit [410] is connected at least with the comparing unit
[408] and the alerting unit [410] is configured to generate an alert in case there is a
mismatch between the retrieved one or more instance IDs with the mapped one or
more RUs [702]. Further, in case of detection of mismatch condition, the alerting
5 unit is triggered for generating the alert. Also, the alert may be generated via one or
more protocols that may be obvious to the person skilled in the art. The present
disclosure encompasses that the generated alert comprises information about
affected one or more sectors and one or more RUs [702]. The information may
include one or more details such as one or more identification number, one or more
10 coordinates related the affected one or more sectors and one or more RUs [702].
Further the affected one or more sector and one or more RUs [702] refers to one or more sectors and Radio Units (RUs) that are impacted by the detected mismatch between the retrieved instance IDs and the mapped RUs.
15 [0099] For instance, the alerting unit may generate the alert which include the
information about identification numbers of two affected RUs [702] i.e. R1 and R2 (the identification number of R1: 00993377, R2: 88220022) along with coordinates of each RU, (such as coordinate of R1: 50°52'47" North, coordinate of R2: 4°42'01" East).
20
[0100] The storing unit [412] is connected at least with the alerting unit [410], the storing unit [412] configured to update the mapped one or more RUs [702] in a configuration database. The configuration database is an organized collection of serial numbers of the one or more RUs [540], also the configuration database is
25 present within the storage unit [412].
[0101] The present disclosure encompasses that the updating of the mapped one or
more RUs [702] in the configuration database comprises correcting a serial number
of the one or more RUs [702] at the EMS in an event of an incorrect installation.
30 For instance, in the event of an incorrect installation, the alerting unit [410] generate
26

the alert or flag for the mismatch and in response to the alert, the storage unit updates the correct serial number of the RUs [702] at the EMS.
[0102] The present disclosure encompasses that the correction of a serial number
5 for one or more Radio Units (RUs) at the Element Management System (EMS) in
an event of an incorrect installation involves accessing the configuration database
through the EMS interface. Upon detection of the discrepancy, an entry for the
affected RUs is located and the serial numbers is updated to reflect the correct
values. The correction ensures that the configuration database accurately represents
10 the serial numbers of the installed RUs.
[0103] Further, the correction of the serial number of the one or more RUs [702]
ensures the accuracy and integrity of a network configuration data. The correction
also mitigates the risk of one or more operational errors and inconsistencies caused
15 by incorrect serial numbers, thereby enhancing the reliability and efficiency of the
network management processes.
[0104] The present disclosure encompasses that the incorrect installation refers to one or more situations where one or more RUs [702] are not properly installed or
20 configured. For instance, the one or more RUs [702] may be installed incorrectly,
and the serial number does not match with a recorded information in a configuration database. The incorrect installation refers to situations where the one or more Radio Units (RUs) [702] are not properly installed or configured according to the expected or recorded information. This may occur due to various reasons such as human error
25 during installation, or miscommunication between installation teams and database
administrators.
[0105] For example, if the RU [702] is defined to be installed in sector A or tower
A, and due to any error, such as human error during installation, the RU [702] is
30 installed in sector B or tower B. This incorrect installation of the RU [702] lead to
27

a mismatch between the recorded information in the configuration database and the actual serial number of the installed RU [702].
[0106] In another instance, during the installation process, if an RU [702] is
5 assigned a specific serial number but is installed with a different serial number due
to any error, it may lead to a mismatch between the recorded information in the
configuration database and the actual serial number of the installed RU [702].
Similarly, if an RU [702] is installed in the wrong location or connected improperly,
the RU [702] may not be recognized or identified correctly, leading to discrepancies
10 between the expected and actual configuration data.
[0107] The present disclosure encompasses that the system [400] further comprises
an allocating unit [414] that is configured to allocate a unique IP address to the RU
instance by a Dynamic Host Configuration Protocol (DHCP) server, wherein the
15 RU instance receives the RU instance ID and the allocated unique IP address from
the DHCP server.
[0108] The present disclosure encompasses that the DHCP server is a network
service that assigns IP addresses and other network configuration parameters to
20 devices on the network.
[0109] The present disclosure encompasses that the allocating unit [414] may
operate according to one or more criteria to allocate the unique IP address from the
DHCP server. The allocation of unique IP addresses by the DHCP server through
25 the allocating unit ensures efficient resource management, simplifies network
administration, and enhances scalability, also reduces manual configuration tasks, prevents IP conflicts, and enables seamless integration of new Radio Units into the network, promoting overall network efficiency and flexibility.
30 [0110] Referring to FIG. 5, a flow diagram of a method [500] depicting a process
for managing Radio Unit (RU) instance identification in a telecommunication
28

network, in accordance with exemplary implementations of the present disclosure
is shown. In an implementation the method [500] is performed by the system [400].
Further, in an implementation, the system [400] may be present in the
telecommunication network to implement the features of the present disclosure.
5 Also, as shown in FIG. 5, the method [500] starts at step [502].
[0111] At step [504], the method [500] comprises receiving, by a transceiver unit
[402], one or more instance identifiers (IDs) associated with one or more RUs [702].
The present disclosure encompasses that the one or more instance identifiers (IDs)
10 refers to unique identification numbers or codes which are associated with
individual RUs. For instance, the one or more instance identifiers (IDs) corresponding to an RU, may distinguish said RU from other RU in a same network.
[0112] As used herein a “radio unit (RU)” refers to a component or device within
15 a telecommunication network responsible for transmitting and/or receiving radio
signals. The radio unit plays a role in facilitating communication between network devices and end-user devices for ensuring an efficient and reliable operation of the network.
20 [0113] At step [506], the method [500] comprises mapping, by a mapping unit
[404], the one or more RUs [702] to one or more sectors (such as sector 1, sector 2 and sector 3 for a RU [702a] as depicted in FIG. 1) based on the received one or more instance IDs.
25 [0114] Also, as used herein the one or more sectors refers to a division of a cellular
coverage area into a plurality of directional zones such as sector 1, sector 2 and sector 3 associated with the RU [702a] (as depicted in FIG. 1). The sector represents a specific angular range of coverage within a cell. Further, it is to be noted that the depiction of sectors (i.e., sector 1, sector 2 and sector 3 associated with the RU
30 [702a]) in FIG. 1 is exemplary in nature and should not be interpreted in a manner
to limit the scope of the disclosure.
29

[0115] More specifically, the mapping of the one or more RUs [702] to the one or
more sectors refers to association of the one or more RUs with specific one or more
sectors within the telecommunication network (or may be used herein as “network”
5 / “communication network”) based on the one or more instance IDs. Moreover, in
an implementation this mapping may be done by the mapping unit [404] via
utilizing one or more protocols which may be obvious to the person skilled in the
art for implementing the features of the present disclosure. Additionally, the
mapping ensures that each RU is correctly identified and assigned to the appropriate
10 sector for facilitating an efficient network operation and management.
[0116] The present disclosure encompasses that the mapping is maintained by at
least one of a network management system (NMS) [202] and a Distributed Unit
(DU) [704]. Therefore, in an instance the mapping unit [404] is configured at, at
15 least one of the network management system (NMS) [202] and the Distributed Unit
(DU) [704] for maintenance of the mapping.
[0117] The NMS [202] is a platform that enables monitoring, controlling and managing of one or more components within the network. The NMS [202] provides
20 access of one or more tools and one or more interfaces to a network administrator
for handling one or more operations, performance and configurations of plurality of network devices and services. Also, the NMS [202] provides functionalities that include but not limited to device discovery, fault detection, performance monitoring, configuration management, and security management. The NMS [202]
25 may perform one or more tasks for maintaining the mapping of the one or more
RUs [702]. The one or more tasks include but are not limited to configuration management, monitoring and updating. For instance, the NMS [202] may continuously monitors a status of each RU [702] and accordingly updates the corresponding mapping.
30
30

[0118] The present disclosure encompasses that the DU [704] is a network element
which is responsible for processing and forwarding a data within a radio access
network (RAN). The DU [704] is generally located closer to the network edge and
near the cell sites or base stations and handles one or more tasks such as radio signal
5 processing, protocol termination and traffic aggregation. The DU [704] may
perform one or more tasks for maintaining the mapping of the one or more RUs
[702]. The one or more tasks include but are not limited to local configuration
management, status synchronization. For instance, the DU [704] may manage the
mapping of each RU [702] within the network and ensures that the corresponding
10 mapping is synchronized with the mapping stored or saved in the NMS [202].
[0119] At step [508], the method [500] comprises periodically polling, by a processing unit [406], the one or more RUs [702] for retrieving the mapped one or more instance IDs and sector information. The present disclosure encompasses that
15 the periodic polling is performed using a management plane (M-Plane) protocol.
The M-Plane protocol is a communication protocol that enable exchange of management related information and commands for management purpose among radio units (RUs). Further, the M-Plane protocol ensures an efficient and standardized communication for retrieval of accurate instance IDs and a sector
20 information.
[0120] The present disclosure encompasses that once the mapped one or more
instance IDs and the sector information are retrieved the transceiver unit [402] is
further configured to transmit the mapped one or more instance IDs and the sector
25 information to an Element Management System (EMS).
[0121] The present disclosure encompasses that the EMS is utilized to manage and
monitor one or more network elements or devices. The EMS provides a centralized
control and oversight of the one or more network elements such as switches, routers,
30 base stations and RUs. For instance, the transmission of the mapped instance IDs
and sector information to the EMS allows the EMS to receive a real-time data about
31

the RUs and their associated sectors which enable the network administrator to monitor and manage the network more effectively.
[0122] For instance, periodically polling the RUs within the network, means that
5 the processing unit [406] requests to the RUs at a pre-defined intervals to obtain
information such as instance IDs and sector information.
[0123] At step [510], the method [500] comprises comparing, by a comparing unit [408], the retrieved one or more instance IDs with the mapped one or more RUs
10 [702]. The present disclosure encompasses that the comparison between the
retrieved one or more instance IDs with the mapped one or more RUs [702] results in a successful match or a mismatch. In addition to this, when the retrieved one or more instance IDs exactly matches with the mapped one or more RUs [702] then it is considered as a successful match or else it is considered as a mismatch.
15
[0124] The comparison between the retrieved instance IDs and the mapped Radio Units (RUs) is achieved through a process that involves the comparing unit examining each retrieved instance ID and comparing the retrieved instance ID to the mapped RUs within the telecommunication network. If an exact match is found
20 between a retrieved instance ID and a mapped RU, the comparison is deemed
successful. Conversely, if no exact match is found, it is considered a mismatch. The comparison enables the comparing unit to identify any discrepancies between the expected and actual instances of RUs in the network.
25 [0125] At step [512], the method [500] comprises generating, by an alerting unit
[410], an alert in case there is a mismatch between the retrieved one or more instance IDs with the mapped one or more RUs [702]. Further, in case of detection of mismatch condition, the alerting unit is triggered for generating the alert. Also, the alert may be generated via one or more protocols that may be obvious to the
30 person skilled in the art. The present disclosure encompasses that the generated alert
comprises an information about affected one or more sectors and one or more RUs
32

[702]. Further the affected one or more sector and one or more RUs [702] refers to one or more sectors and Radio Units (RUs) that are impacted by the detected mismatch between the retrieved instance IDs and the mapped RUs.
5 [0126] At step [514], the method [500] comprises updating, by a storing unit [412],
the mapped one or more RUs [702] in a configuration database. The present disclosure encompasses that the updating of the mapped one or more RUs [702] in the configuration database comprises correcting a serial number of the one or more RUs [702] at the EMS in an event of an incorrect installation. The present disclosure
10 encompasses that the updating of the mapped one or more RUs [702] in the
configuration database comprises correcting the serial number of the one or more RUs [702] at the EMS in the event of an incorrect installation. For instance, in the event of an incorrect installation, the alerting unit [410] generate the alert or flag for the mismatch and in response to the alert, the storage unit updates the correct
15 serial number of the RUs [702] at the EMS.
[0127] The present disclosure encompasses that the correction of the serial number
for one or more Radio Units (RUs) at the Element Management System (EMS) in
the event of an incorrect installation involves accessing the configuration database
20 through the EMS interface. Upon detection of the discrepancy, an entry for the
affected RUs is located and the serial numbers is updated to reflect the correct values. The correction ensures that the configuration database accurately represents the serial numbers of the installed RUs.
25 [0128] Further, the correction of the serial number of the one or more RUs [702]
ensures the accuracy and integrity of a network configuration data. The correction also mitigates the risk of one or more operational errors and inconsistencies caused by incorrect serial numbers, thereby enhancing the reliability and efficiency of the network management processes.
30
33

[0129] The present disclosure encompasses that the incorrect installation refers to
one or more situations where one or more RUs [702] are not properly installed or
configured. For instance, the one or more RUs [702] may be installed incorrectly,
and the serial number does not match with a recorded information in a configuration
5 database. The incorrect installation refers to situations where the one or more Radio
Units (RUs) [702] are not properly installed or configured according to the expected or recorded information. This may occur due to various reasons such as human error during installation, hardware malfunction, or miscommunication between installation teams and database administrators.
10
[0130] For instance, during the installation process, if an RU [702] is assigned a specific serial number but is installed with a different serial number due to any error, it may lead to a mismatch between the recorded information in the configuration database and the actual serial number of the installed RU [702]. Similarly, if an RU
15 [702] is installed in the wrong location or connected improperly, the RU [702] may
not be recognized or identified correctly, leading to discrepancies between the expected and actual configuration data.
[0131] The present disclosure encompasses that the method further comprises
20 allocating, by an allocating unit [414], a unique IP address to the RU instance by a
Dynamic Host Configuration Protocol (DHCP) server, wherein the RU instance receives the RU instance ID and the allocated unique IP address from the DHCP server.
25 [0132] The present disclosure encompasses that the DHCP server is a network
service that automatically assigns IP addresses and other network configuration parameters to devices on the network.
[0133] The present disclosure encompasses that allocation of the unique IP address
30 may be done according to one or more criteria. The allocation of unique IP
addresses by the DHCP server through the allocating unit ensures efficient resource
34

management, simplifies network administration, and enhances scalability, also reduces manual configuration tasks, prevents IP conflicts, and enables seamless integration of new Radio Units into the network, promoting overall network efficiency and flexibility. 5
[0134] Further the method terminates at step [516].
[0135] Referring to FIG. 6, an exemplary flow diagram of a method [600] depicting an Internet Protocol (IP) binding process, in accordance with exemplary
10 implementations of the present disclosure is depicted. The IP binding refers to a
process of linking a specific IP address to a particular device (i.e. a radio unit) or an interface. The IP binding may be static (i.e. permanently assigned) or dynamic (i.e. temporarily assigned). The IP binding process ensure that the device retains the assigned IP address for a pre-defined duration of connection.
15
[0136] At step S1, initiating the IP binding process, via a call back function.
[0137] At step S2, disabling a supervision timer for preventing an interference
during the IP binding process. The supervision timer is set to ensure that one or
20 more processes (such as IP binding process) are completed within a pre-defined
timeframe. The disabling of the supervision timer prevents unnecessary retries or errors that may occur during the IP binding process.
[0138] At step S3, determining whether a static IP is already configured for the
25 particular device or not. In case the static IP is not configured, then the process
proceeds to step S4 or else to step S9.
[0139] At step S4, discovering a Dynamic Host Configuration Protocol (DHCP)
server with no tag (tag such as Virtual Local Area Network (VLAN) tags). Further
30 the VLANs keep a network traffic from different networks separated when
traversing shared links and devices within a topology. The present disclosure
35

encompasses that the DHCP server is a network service that assigns IP addresses and other network configuration parameters to devices on the network.
[0140] At step S5, if the DHCP server is discovered with no tag, then process
5 proceeds to step S8, else the process proceeds to step S6.
[0141] At step S6, discovering DHCP server with each VLAN tag in a series, and at step S7, if no DHCP server with VLAN tag in series is discovered, then Step S4 is repeated or else the method proceeds to step S8.
10
[0142] At step S8, replacing the static IP and re-running a data transmission. Also, in step S9, setting the static IP and running the data transmission. The re-running of the data transmission ensures a continuous data transmission without any interruption, upon the replacement of the static IP. The re-running of the data
15 transmission helps to prevent one or more potential errors that may arise due to the
change in the static IP. Hence, the step of re-running the data transmission maintains stability and reliability in the network.
[0143] At step S10, storing the static IP in an internal configuration for future
20 reference, upon completion of step S8 and step S9.
[0144] At step S11, changing a Network Configuration Protocol (NETCONF) server configuration according to step S10.
25 [0145] At step S12, checking if the NETCONF server is running, in an event, if the
NETCONF server is running, the process proceeds to step S13 or else to step S14.
[0146] At step S13, reconfiguring the NETCONF server and at step S15, finishing the IP binding process. 30
36

[0147] At step S14, running the NETCONF server in case the NETCONF server is not running.
[0148] Further, the NETCONF server is a server which is configured to provide a
5 secured mechanism for installing, manipulating, deleting a data related to the
configuration. Moreover, at step S14, the NETCONF server manages the
configuration and ensures that the changes made in the static IP or any other
configuration, during the IP binding process, are synchronized across one or more
network devices such as radio unit. In other words, step S14 helps to maintain a
10 consistency in the all the configurations across the one or more network devices.
[0149] At step S15, terminating or finishing the IP binding process.
15 [0150] Referring to FIG. 7, an exemplary block diagram of the network
environment for managing Radio Unit (RU) instance identification in a telecommunication network, in accordance with exemplary implementations of the present disclosure is shown. The network environment [700] comprises a Network Management System (NMS) [202], a RU [702], a Distributed unit (DU) [6704], and
20 a storage unit [412]. Also, all of the components/ units of the network environment
[600] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 7 only a few units are shown, however, the network environment [700] may comprise multiple such units or the network
25 environment [700] may comprise any such numbers of said units, as required to
implement the features of the present disclosure.
[0151] The DU [704] sends a Dynamic Host Configuration Protocol (DHCP)
request to the one or more RUs [702] to obtain an IP address and one or more
30 network parameters. The one or more RUs [702] responds with DHCP offer that
includes an assigned IP address and the one or more network parameters. The DU
37

[704] sends the DHCP request to acknowledge the offer and confirm IP address assignment. Further, the one or more RUs [702] sends DHCP acknowledgement to confirm the IP address assignment to DU [704].
5 [0152] Thereafter, the DU initiates a Call Home procedure to establish a
hierarchical connection with the one or more RUs [702]. The one or more RUs [702] receives the Call Home request and acknowledges the request. Further a secure hierarchical communication channel is established between the DU [704] and the one or more RUs [702] for further interactions.
10
[0153] The DU [704] periodically polls the one or more RUs [702] for their instance IDs and the sector information using the M-Plane protocol. Further, the one or more RU responds with its instance ID and the associated sector information over the M-Plane interface. Further, the DU compares the reported instance IDs
15 with the expected RU-to-sector mapping. Thereafter, a mismatch is identified when
the reported instance ID and sector information do not align with the expected mapping.
[0154] Thereafter the DU [704] generates an alarm or notification indicating the
20 sector-instance ID mismatch. The alarm includes information about the affected
sector(s) and the one or more RUs [702] involved. The alarm is communicated to the NMS (Network Management System) [202] responsible for managing and monitoring the network.
25 [0155] The NMS using the storage unit [412] reports and updates the RU-to-sector
mapping in the configuration database using an operation, administration, and maintenance (OAM) protocol or a configuration management protocol. The updated configuration is synchronized with the one or more RUs [702] to align the reported instance IDs with the correct sectors. Once the mapping is corrected, the
30 sector-instance ID mismatch is resolved, and the network operates with the updated
configuration.
38

[0156] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for managing Radio Unit (RU) instance
identification in a telecommunication network, the instructions include executable
5 code which, when executed by a one or more units of a system [400], causes: a
transceiver unit [402] of the system [400] to receive one or more instance identifiers (IDs) associated with one or more RUs [702]; a mapping unit [404] of the system [400] to map the one or more RUs [702] to one or more sectors based on the received one or more instance IDs; a processing unit [406] of the system [400] to
10 periodically poll the one or more RUs [702] for retrieving the mapped one or more
instance IDs and sector information; a comparing unit [408] of the system [400] to compare the retrieved one or more instance IDs with the mapped one or more RUs [702]; an alerting unit [410] of the system [400] to generate an alert in case there is a mismatch between the retrieved one or more instance IDs with the mapped one or
15 more RUs [702]; and a storing unit [412] of the system [400] to update the mapped
one or more RUs [702] in a configuration database.
[0157] As is evident from the above, the present disclosure provides a technically advanced solution for managing Radio Unit (RU) instance identification in a
20 telecommunication network. The present solution provides a system and method
for managing Radio Unit (RU) instance identification in a telecommunication network that effectively manages the accurate identification of RUs at the sector level. In the event of any incorrect installations detected at a site, the present solution generates an alarm and rectifies the information regarding the RU. The
25 present solution streamlines the deployment process, ensuring that RUs are
accurately identified and integrated into the network with minimal disruption. Also, by accurately identifying RUs at the sector level, the present solution improves operational efficiency, which also allows for better resource allocation, monitoring, and troubleshooting. Further, the present solution adapts to evolving network
30 requirements and technologies, ensuring scalability and future-proofing for long-
term network growth and advancements.
39

[0158] While considerable emphasis has been placed herein on the
disclosed implementations, it will be appreciated that many implementations can
be made and that many changes can be made to the implementations without
5 departing from the principles of the present disclosure. These and other changes in
the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
40

We Claim:
1. A method for managing Radio Unit (RU) instance identification in a
telecommunication network, said method comprising:
receiving, by a transceiver unit [402], one or more instance identifiers (IDs) associated with one or more RUs [702];
mapping, by a mapping unit [404], the one or more RUs [702] to one or more sectors based on the received one or more instance IDs;
periodically polling, by a processing unit [406], the one or more RUs [702] for retrieving the mapped one or more instance IDs and a sector information;
comparing, by a comparing unit [408], the retrieved one or more instance IDs with the mapped one or more RUs [702];
generating, by an alerting unit [410], an alert in case there is a mismatch between the retrieved one or more instance IDs with the mapped one or more RUs [702]; and
updating, by a storing unit [412], the mapped one or more RUs [702] in a configuration database.
2. The method as claimed in claim 1, wherein the mapping is maintained by at least one of a network management system (NMS) [202] and a Distributed Unit (DU) [704].
3. The method as claimed in claim 1, wherein the generated alert comprises an information about affected one or more sectors and one or more RUs [702].
4. The method as claimed in claim 1, further comprising transmitting, by the transceiver unit [402], the mapped one or more instance IDs and sector information to an Element Management System (EMS).
5. The method as claimed in claim 4, wherein the updating of the mapped one or more RUs [702] in the configuration database comprises correcting a serial number of the one or more RUs [702] at the EMS in an event of an incorrect installation.

6. The method as claimed in claim 1, further comprising allocating, by an allocating unit [414], a unique IP address to the RU instance by a Dynamic Host Configuration Protocol (DHCP) server, wherein the RU instance receives the RU instance ID and the allocated unique IP address from the DHCP server.
7. The method as claimed in claim 1, wherein the periodic polling is performed using a management plane (M-Plane) protocol.
8. A system [400] for managing Radio Unit (RU) instance identification in a telecommunication network, the system [400] comprises:
a transceiver unit [402] configured to receive one or more instance identifiers (IDs) associated with one or more RUs [702];
a mapping unit [404] connected at least with the transceiver unit [402], the mapping unit [404] configured to map the one or more RUs [702] to one or more sectors based on the received one or more instance IDs;
a processing unit [406] connected at least with the mapping unit [404], the processing unit [406] configured to periodically poll the one or more RUs [702] for retrieving the mapped one or more instance IDs and sector information;
a comparing unit [408] connected at least with the processing unit [406], the comparing unit [408] configured to compare the retrieved one or more instance IDs with the mapped one or more RUs [702];
an alerting unit [410] connected at least with the comparing unit [408], the alerting unit [410] configured to generate an alert in case there is a mismatch between the retrieved one or more instance IDs with the mapped one or more RUs [702]; and
a storing unit [412] connected at least with the alerting unit [410], the storing unit [412] configured to update the mapped one or more RUs [702] in a configuration database.

9. The system [400] as claimed in claim 8, wherein the mapping is maintained by at least one of a network management system (NMS) [202] and a Distributed Unit (DU) [704].
10. The system [400] as claimed in claim 8, wherein the generated alert comprises information about affected one or more sectors and one or more RUs [702].
11. The system [400] as claimed in claim 8, the transceiver unit [402] is further configured to transmit the mapped one or more instance IDs and sector information to an Element Management System (EMS).
12. The system [400] as claimed in claim 11, wherein the updating of the mapped one or more RUs [702] in the configuration database comprises correcting a serial number of the one or more RUs [702] at the EMS in an event of an incorrect installation.
13. The system [400] as claimed in claim 8, further comprises an allocating unit [414] configured to allocate a unique IP address to the RU instance by a Dynamic Host Configuration Protocol (DHCP) server, wherein the RU instance receives the RU instance ID and the allocated unique IP address from the DHCP server.
14. The system [400] as claimed in claim 8, wherein the periodic polling is performed using a management plane (M-Plane) protocol.