Search

EP-4740555-A1 - METHOD AND SYSTEM FOR MANAGING RADIO UNIT (RU) INSTANCE IDENTIFICATION IN A TELECOMMUNICATION NETWORK

EP4740555A1EP 4740555 A1EP4740555 A1EP 4740555A1EP-4740555-A1

Abstract

The present disclosure relates to a method [500] and a system [400] for managing Radio Unit (RU) instance identification in a telecommunication network The 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; 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; 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; and updating, by a storing unit [412], the mapped one or more RUs [702] in a configuration database.

Inventors

  • SHAH, BRIJESH
  • BHATNAGAR, AAYUSH
  • BHATNAGAR, PRADEEP KUMAR
  • PANDEY, Anup Kumar

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240703

Claims (15)

  1. 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. 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. 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. 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. 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. 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. 7. The method as claimed in claim 1, wherein the periodic polling is performed using a management plane (M-Plane) protocol.
  8. 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. 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. 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. 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. 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. 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. 14. The system [400] as claimed in claim 8, wherein the periodic polling is performed using a management plane (M-Plane) protocol.
  15. 15. 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 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 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 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.

Description

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 (0AM) 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, perfo