FIELD OF DISCLOSURE
[0001] The present disclosure generally relates to the field of wireless
communication technologies. More particularly, the present disclosure relates to a
system and a method for identifying a serving cell and determining network
5 parameters in fifth generation (5G) and future generation mobile communication
networks using unique identifiers such as a New Radio (NR) Cell Identity (NCI).
DEFINITION
[0002] As used in the present disclosure, the following terms are generally
intended to have the meaning as set forth below, except to the extent that the context
10 in which they are used to indicate otherwise.
[0003] The term “client-side application,” as used hereinafter in the
specification, refers to a software (android/iOS) application running locally on a
User Equipment (UE), configured to retrieve a value of a unique identifier from the
UE.
15 [0004] The term “New Radio (NR) Cell Identity (NCI),” as used hereinafter in
the specification, refers to a unique 36-bit identifier assigned to a 5G NR cell, which
distinguishes it from other cells within a network. The NCI is part of an NR Cell
Global Identity (NR-CGI) and includes encoded information such as a nextgeneration NodeB identity (gNB ID) and a cell ID, enabling the identification of a
20 serving cell in the network. The NCI is used by network components and UE for
cell selection, handover, and performance diagnostics.
[0005] The term “platform-specific system-level application programming
interfaces (APIs),” as used hereinafter in the specification, refers to application
programming interfaces provided by an operating system that allows applications
25 to access low-level system services and hardware-related information. Examples of
the platform-specific system-level APIs include Android’s Telephony Manager
APIs and their equivalents on other platforms such as the iPhone Operating System
(iOS). The platform-specific system-level APIs enable retrieval of device-specific
3
and network-related parameters (e.g., cell identity, signal strength, network type)
without requiring modifications to a core network infrastructure.
[0006] The term “Physical Cell Identifier (PCI),” as used hereinafter in the
specification, refers to a unique identifier assigned to a cell within a wireless
5 communication network, used by UE to distinguish and synchronize with different
cells.
[0007] The term “operating frequency band,” as used hereinafter in the
specification, refers to a designated range of radio frequencies allocated for wireless
communication between UE and a base station within a cellular network. The
10 frequency band determines a spectrum on which the UE transmits and receives
signals and is critical for ensuring compatibility with network infrastructure and
optimizing coverage, capacity, and performance.
[0008] The term “Reference Signal Received Power (RSRP),” as used
hereinafter in the specification, refers to an average power received from specific
15 reference signals transmitted by a cell within a wireless communication network,
measured over resource elements carrying the signals. The RSRP is used as a key
metric to evaluate signal strength, particularly in 4G and 5G networks, and aids in
functions such as cell selection, handover decisions, and network optimization.
[0009] The term “Reference Signal Received Quality (RSRQ),” as used
20 hereinafter in the specification, refers to a quality metric that represents a ratio of
RSRP to a total received power within a given frequency bandwidth in a wireless
communication network. The RSRQ provides an indication of signal quality by
accounting for both the strength of the reference signal and the level of background
interference and noise.
25 [0010] The term “Signal-to-Interference-plus-Noise Ratio (SINR),” as used
hereinafter in the specification, refers to a key performance metric that quantifies
the quality of a wireless communication link by measuring a ratio of a power of the
desired signal to a sum of the power of interference from other signals and
background noise. It is typically expressed in decibels (dB) and serves as an
4
indicator of the reliability and efficiency of data transmission over a radio channel.
Higher SINR values generally correspond to better signal quality, enabling higher
data rates and improved network performance in communication technologies.
[0011] The term “Received Signal Strength Indicator (RSSI),” as used
5 hereinafter in the specification, refers to a measurement that indicates the total
power level of all received Radio Frequency (RF) signals, including a desired
signal, interference, and background noise, at a receiver antenna of UE. RSSI serves
as a coarse indicator of signal presence and strength within an operating frequency
band.
10 [0012] The term “NR Cell Global Identity (NCGI),” as used hereinafter in the
specification, refers to a globally unique identifier assigned to a 5G New Radio
(NR) cell within a Public Land Mobile Network (PLMN). The NCGI is used to
identify a cell uniquely and is composed of PLMN ID and NCI.
[0013] The term “Public Land Mobile Network (PLMN),” as used hereinafter
15 in the specification, refers to a telecommunications network established and
operated by a network service provider to offer wireless communication services to
the public. Each PLMN is uniquely identified by a combination of a Mobile Country
Code (MCC) and a Mobile Network Code (MNC).
[0014] The term “Mobile Country Code (MCC),” as used hereinafter in the
20 specification, refers to a three-digit numerical code used to uniquely identify a
country of origin of a mobile network within PLMN. The MCC is part of a PLMN
ID, combined with MNC, and is used in various mobile communication procedures,
including network selection, roaming, and subscriber authentication.
[0015] The term “Mobile Network Code (MNC),” as used hereinafter in the
25 specification, refers to a two- or three-digit numerical code that uniquely identifies
a specific mobile network operator within a given country. The MNC is used in
conjunction with the MCC to form a PLMN ID, which enables mobile devices to
connect to an appropriate network for services such as voice, data, and roaming.
5
[0016] The term “Serving Cell,” as used hereinafter in the specification, refers
to a specific radio cell within a wireless communication network that is actively
providing connectivity and communication services to UE. The serving cell handles
the transmission and reception of data, signaling, and control information with the
5 UE and is determined based on factors such as signal strength, quality, and network
configuration. It is identified by parameters such as PCI, cell identity (ID), and
associated gNB, and may change dynamically due to handovers or network
optimization processes.
[0017] The term “Cell identity (ID),” as used hereinafter in the specification,
10 refers to a unique identifier assigned to a specific cell within a mobile
communication network that is used to distinguish one cell from another within a
given geographical area or network configuration.
[0018] The term “Next Generation NodeB (gNB) Identity (ID),” as used
hereinafter in the specification, refers to a next-generation base station in a 5G New
15 Radio (NR) network that provides radio access to UE. The gNB handles radio
transmission and reception, resource scheduling, mobility management, and
coordination with 5G Core (5GC) network functions.
[0019] The term “System Information Block 1 (SIB1),” as used hereinafter in
the specification, refers to a standardized broadcast message transmitted by a base
20 station (e.g., gNB in 5G or evolved NodeB (eNB) in Long Term Evolution (LTE))
that contains essential system information required by UE to access and operate
within a wireless communication network.
[0020] The term “Broadcast Control Channel (BCCH),” as used hereinafter in
the specification, refers to a downlink logical channel used in wireless
25 communication systems to broadcast system information from a base station (e.g.,
gNB or eNB) to all UE within a cell.
[0021] The term “bit-level logic,” as used hereinafter in the specification,
refers to the use of binary operations to process and interpret a binary format of a
unique identifier (e.g., NCI). The binary operations are applied to specific bits or
6
groups of bits within the unique identifier to extract or derive meaningful
information such as network parameters (gNB ID and cell ID).
[0022] The term “first format,” as used hereinafter in the specification, refers
to an initial representation of a unique identifier associated with a serving cell. The
5 initial representation is in a human-readable or system-provided numerical form,
such as a decimal format.
[0023] The term “second format,” as used hereinafter in the specification,
refers to a processed or transformed representation of a unique identifier obtained
by converting the first format into a binary format.
10 [0024] The term “formatted number,” as used hereinafter in the specification,
refers to the value of a unique identifier after the unique identifier has been
converted from the first format to the second format. The formatted number is in
binary representation.
[0025] The term “bit length,” as used hereinafter in the specification, refers to
15 the size of a binary representation of a unique identifier (e.g., NCI), and the bit
length determines how many bits are used to encode and subsequently decode
network parameters such as gNB ID and cell ID.
[0026] The term “captured value of the unique identifier,” as used hereinafter
in the specification, refers to the retrieved or extracted value of a specific identifier
20 associated with a serving cell in a communication network. The captured value is
obtained by accessing system-level application programming interfaces (APIs) on
a UE and represents a parameter such as a New Radio Cell Identity (NCI), which
uniquely identifies a cell within a mobile network.
[0027] The term “predetermined bit length” as used hereinafter in the
25 specification, refers to a fixed, predefined number of bits that a value must conform
to for standardized processing in a system. The term “predetermined” indicates that
the value is established in advance either by standard specifications, system design,
or configuration parameters and remains constant during the execution of described
7
processes. In the context of the disclosure, the predetermined bit length is 36 bits
for NCI used in communication networks.
[0028] The term “predefined number of bits” refers to a fixed and
predetermined portion of a binary sequence that is designated in advance to
5 represent specific data segments. In the context of the present disclosure, the
predefined number of bits corresponds to a total of 36 bits, which are further divided
into bit segments such as 22 bits for representing gNB ID and 14 bits for
representing cell ID.
[0029] These definitions are in addition to those expressed in the art.
10 BACKGROUND OF DISCLOSURE
[0030] The following description of 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 be used only
15 to enhance the understanding of the reader with respect to the present disclosure,
and not as admissions of prior art.
[0031] Wireless communication technology has evolved significantly over the
past few decades. The first generation (1G) was based on analog technology and
supported only voice services. The second generation (2G) introduced digital
20 communication, enabling text messaging and basic data services. The third
generation (3G) brought high-speed internet access, mobile video calls, and
location-based services. The fourth generation (4G) further revolutionized
communication by providing significantly faster data speeds, broader network
coverage, and enhanced security protocols. Currently, the ongoing deployment of
25 fifth generation (5G) technology promises even higher data rates, ultra-low latency,
and the capability to connect a vast number of devices simultaneously. Furthermore,
the sixth generation (6G) technology anticipated as successor to the 5G is expected
to deliver dramatically increased data speeds and reduced latency, offering even
more reliable connectivity across a wide range of devices. While the 5G is still
8
being rolled out globally, research and development into the 6G are rapidly
advancing, with the goal of transforming how users connect to and interact with
digital ecosystems.
[0032] In mobile communication networks, accurately identifying and
5 monitoring serving cell parameters is critical for tasks such as network
optimization, performance monitoring, and site validation. New Radio Cell Identity
(NCI), which consists of a unique 36-bit value representing both a Next Generation
NodeB (gNodeB) Identity (ID) and a Cell ID, is essential for identifying a serving
cell to which a device is connected. The serving cell parameters are essential for
10 determining a physical location of the serving cell and are instrumental in ensuring
optimal signal strength, network performance, and coverage.
[0033] Field engineers and network technicians often require accurate serving
cell parameters to perform tasks such as troubleshooting network issues, validating
site configurations, and monitoring network health in real time. However, retrieving
15 and interpreting NCI values is not straightforward, as the NCI values provided by
Android Application Programming Interfaces (APIs) or other system interfaces
may not be in a desired format (e.g., 36-bit length), requiring additional steps for
conversion, extraction, and interpretation. Moreover, the engineers frequently face
complexity when the engineers need to manually extract information from disparate
20 sources or rely on vendor-specific tools, which can lead to compatibility issues and
increase time and effort.
[0034] Thus, there is a need for a unified, vendor-independent solution that
simplifies the process of accessing, interpreting, and utilizing serving cell
information to enable the engineers to quickly and accurately retrieve the serving
25 cell parameters in the field, thereby enhancing operational efficiency and
supporting real-time network diagnostics.
OBJECTIVES OF THE PRESENT DISCLOSURE
[0035] Some of the objectives of the present disclosure, which at least one
embodiment herein satisfies are as listed herein below.
9
[0036] An objective of the present disclosure is to provide a system and a
method for accurately identifying a serving cell in a communication network based
on a unique identifier, such as a New Radio Cell Identity (NCI), to derive vital
network parameters.
5 [0037] Another objective of the present disclosure is to provide a vendorindependent and standardized approach for converting and interpreting an NCI
value into its Next Generation NodeB (gNB) Identity (ID) and cell ID components,
regardless of vendor-specific implementations.
[0038] Yet another objective of the present disclosure is to enable real-time
10 visibility of critical network Key Performance Indicators (KPIs) such as gNB ID,
cell ID, frequency band, Physical Cell Identifier (PCI), Reference Signal Received
Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-toInterference-plus-Noise Ratio (SINR), Received Signal Strength Indicator (RSSI),
and so forth directly on a User Interface (UI) of a client-based application.
15 [0039] Another objective of the present disclosure is to ensure that accurate
serving cell information is displayed on a UI even as a device transitions between
different cells within a communication network.
[0040] Yet another objective of the present disclosure is to eliminate the need
for manual calculation or cross-referencing of data from multiple tools, thereby
20 accelerating a process of network validation, site commissioning, and optimization
for field engineers.
[0041] Another objective of the present disclosure is to develop a universal
algorithm at an application level for parsing an NCI value and calculating network
parameters in a consistent and accurate manner across different vendors.
25 [0042] Yet another objective of the present disclosure is to improve operational
efficiency and support real-time decision-making by providing field engineers and
network planners with accurate and actionable insights for 5G network deployment
and optimization.
10
[0043] Another objective of the present disclosure is to support business
operations by enabling real-time retrieval of network parameters associated with a
serving cell and KPIs based on an NCI. This facilitates quick validation of site
configurations, streamlines execution of work orders, and helps reduce
5 commissioning delays.
[0044] Yet another objective of the present disclosure is to offer a solution that
complies with industry standards while improving the precision and reliability of
5G network diagnostics and planning tools.
[0045] Another objective of the present disclosure is to provide a system and a
10 method that maintains a centralized database of NCI values for all serving cells in
a network, enabling field engineers to access information quickly and easily during
site validation or troubleshooting tasks.
[0046] Other objectives and advantages of the present disclosure will be more
apparent from the following description, which is not intended to limit the scope of
15 the present disclosure.
SUMMARY
[0047] In an exemplary embodiment, the present invention discloses a method
for identifying a serving cell from a unique identifier in a communication network.
The method includes capturing, by a data capturing unit, a value of the unique
20 identifier associated with the serving cell. The method further includes converting,
by a data conversion module, the captured value of the unique identifier from a first
format to a second format to generate a formatted number. The method further
includes comparing, by a comparison module, a bit length of the formatted number
with a predetermined bit length. The method further includes appending, by the
25 comparison module, one or more bits to the formatted number to obtain the
formatted number of the predetermined bit length when the bit length of the
formatted number is less than the predetermined bit length. The method further
includes determining, by a parameter determination module, at least one network
11
parameter for identifying the corresponding serving cell based on a predefined
number of bits of the formatted number having the predetermined bit length.
[0048] In some embodiments, the at least one network parameter includes a
Next Generation NodeB (gNB) Identity (ID), and a cell ID.
5 [0049] In some embodiments, the unique identifier includes a New Radio (NR)
Cell Identity (NCI).
[0050] In some embodiments, the first format includes a decimal format
considered as a raw input used in determining the at least one network parameter.
[0051] In some embodiments, the second format includes a binary format
10 obtained by converting the unique identifier from the first format to facilitate
implementation of bit-level logic for determining the at least one network
parameter.
[0052] In some embodiments, the method further includes converting, by the
data conversion module, the predefined number of bits of the formatted number
15 having the predetermined bit length from the second format to the first format to
determine the at least one network parameter.
[0053] In some embodiments, the method further includes displaying, by a
display module, the at least one determined network parameter and the value of the
unique identifier associated with the identified serving cell on a User Interface (UI)
20 of a User Equipment (UE).
[0054] In an exemplary embodiment, a system to identify a serving cell from a
unique identifier in a communication network is disclosed. The system includes a
data capturing unit configured to capture a value of the unique identifier associated
with the serving cell. The system further includes a processing unit
25 communicatively coupled to the data capturing unit. The processing unit includes a
data conversion module configured to convert the captured value of the unique
identifier from a first format to a second format to generate a formatted number.
The processing unit further includes a comparison module configured to compare a
12
bit length of the formatted number with a predetermined bit length. The comparison
module is further configured to append one or more bits to the formatted number to
obtain the formatted number of the predetermined bit length when the bit length of
the formatted number is less than the predetermined bit length. The processing unit
5 further includes a parameter determination module configured to determine the at
least one network parameter for identifying the corresponding serving cell based on
a predefined number of bits of the formatted number having the predetermined bit
length.
[0055] In some embodiments, the at least one network parameter includes a
10 Next Generation NodeB (gNodeB) Identity (ID), and a cell ID.
[0056] In some embodiments, the unique identifier includes a New Radio (NR)
Cell Identity (NCI).
[0057] In some embodiments, the first format includes a decimal format
considered as a raw input used in determining the at least one network parameter.
15 [0058] In some embodiments, the second format includes a binary format
obtained by converting the unique identifier from the first format to facilitate
implementation of bit-level logic for determining the at least one network
parameter.
[0059] In some embodiments, the data conversion module is further configured
20 to convert the predefined number of bits of the formatted number having the
predetermined bit length from the second format to the first format to determine the
at least one network parameter.
[0060] In some embodiments, the processing unit further includes a display
module configured to display the at least one determined network parameter and
25 the value of the unique identifier associated with the identified serving cell on a
User Interface (UI) of a User Equipment (UE).
[0061] In an exemplary embodiment, a user equipment (UE) communicatively
coupled with a communication network is disclosed. The coupling includes steps
13
of receiving, by the communication network, a connection request from the UE.
The coupling further includes sending, by the communication network, an
acknowledgment of the connection request to the UE. The coupling further includes
transmitting a plurality of signals in response to the connection request. The UE is
5 configured to generate at least one request for identifying a serving cell from a
unique identifier. The at least one request is managed in the communication
network by a method. The method includes capturing, by a data capturing unit, a
value of the unique identifier associated with the serving cell. The method further
includes converting, by a data conversion module, the captured value of the unique
10 identifier from a first format to a second format to generate a formatted number.
The method further includes comparing, by a comparison module, a bit length of
the formatted number with a predetermined bit length. The method further includes
appending, by the comparison module, one or more bits to the formatted number to
obtain the formatted number of the predetermined bit length when the bit length of
15 the formatted number is less than the predetermined bit length. The method further
includes determining, by a parameter determination module, at least one network
parameter for identifying the corresponding serving cell based on a predefined
number of bits of the formatted number having the predetermined bit length.
[0062] The foregoing general description of the illustrative embodiments and
20 the following detailed description thereof are merely exemplary aspects of the
teachings of this disclosure and are not restrictive.
BRIEF DESCRIPTION OF DRAWINGS
[0063] The accompanying drawings, which are incorporated herein, and
constitute a part of this disclosure, illustrate exemplary embodiments of the
25 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, emphasis instead being placed upon clearly illustrating the
principles of the present disclosure. Some drawings may indicate the components
using block diagrams and may not represent the internal circuitry of each
14
component. It will be appreciated by those skilled in the art that disclosure of such
drawings includes the disclosure of electrical components, electronic components
or circuitry commonly used to implement such components.
[0064] FIG. 1 illustrates an exemplary network architecture for implementing
5 a system to identify a serving cell from a unique identifier in a communication
network, in accordance with embodiments of the present disclosure.
[0065] FIG. 2 illustrates an exemplary block diagram of the system to identify
the serving cell from the unique identifier in the communication network, in
accordance with embodiments of the present disclosure.
10 [0066] FIG. 3 illustrates an exemplary structure of NR Cell Global Identity
(NCGI), in accordance with embodiments of the present disclosure.
[0067] FIG. 4 illustrates an exemplary User Interface (UI) for conducting
network speed tests and displaying real-time wireless network metrics on a User
Equipment (UE), in accordance with embodiments of the present disclosure.
15 [0068] FIG. 5 illustrates an exemplary flow diagram of a method for
identifying the serving cell from the unique identifier in the communication
network, in accordance with embodiments of the present disclosure.
[0069] FIG. 6 illustrates an exemplary computer system in which, or with
which, the system and the method of the present disclosure may be implemented.
20 [0070] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
LIST OF REFERENCE NUMERALS
100 – Network architecture
102 – System
25 104 – Communication Network
15
106-1, 106-2…106-N – User Equipment
108-1, 108-2…108-N – Users
200 – Data Capturing Unit
202 – Memory
5 204 – Interfacing Unit
206 – Processing Unit
208 – Database
210 – Data Conversion Module
212 – Comparison Module
10 214 – Parameter Determination Module
216 – Display Module
300 – Structure
302 – NR Cell Global Identity (NCGI)
304 – Mobile Country Code (MCC)
15 306 – Mobile Network Code (MNC)
308 – NR Cell Identity (NCI)
310a-310b – gNB Identity (ID)
312a-312b – Cell Identity (ID)
400 – User Interface (UI)
20 402 – Speed Test Button
404 – Frequency Band
16
406 – Physical Cell Identifier (PCI)
408 – NCI
410 – gNB ID
412 – cell ID
5 414 – Reference Signal Received Power (RSRP)
416 – Reference Signal Received Quality (RSRQ)
418 – Signal-to-Interference-plus-Noise Ratio (SINR)
420 – Received Signal Strength Indicator (RSSI)
422 – Feedback section
10 424 – History section
426 – Connection Status Indicator
500 – Method Flow
600 - Computer System
610 - External Storage Device
15 620 - Bus
630 - Main Memory
640 - Read-Only Memory
650 - Mass Storage Device
660 - Communication Ports
20 670 – Processor
17
DETAILED DESCRIPTION OF DISCLOSURE
[0071] In the following description, for the purposes of explanation, various
specific details are set forth to provide a thorough understanding of embodiments
of the present disclosure. It will be apparent, however, that embodiments of the
5 present disclosure may be practiced without these specific details. Several features
described hereafter can each be used independently of one another or with any
combination of other features. An individual feature may not address any of the
problems discussed above or might address only some of the problems discussed
above. Some of the problems discussed above might not be fully addressed by any
10 of the features described herein. Example embodiments of the present disclosure
are described below, as illustrated in various drawings in which like reference
numerals refer to the same parts throughout the different drawings.
[0072] The ensuing description provides exemplary embodiments only, and is
not intended to limit the scope, applicability, or configuration of the disclosure.
15 Rather, 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 disclosure as set forth.
20 [0073] 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
specific details. For example, circuits, systems, networks, processes, and other
components may be shown as components in block diagram form in order not to
25 obscure the embodiments in unnecessary detail. In other instances, well-known
circuits, processes, algorithms, structures, and techniques may be shown without
unnecessary detail to avoid obscuring the embodiments.
[0074] Also, it is noted that individual embodiments may be described as a
process that is depicted as a flowchart, a flow diagram, a data flow diagram, a
18
structure diagram, or a block diagram. Although a flowchart may describe the
operations as a sequential process, many of the operations can 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
5 steps not included in a figure. A process may correspond to a method, a function, a
procedure, a subroutine, a subprogram, etc. When a process corresponds to a
function, its termination can correspond to a return of the function to the calling
function or the main function.
[0075] The word “exemplary” and/or “demonstrative” is used herein to mean
10 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
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
15 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
description or the claims, such terms are intended to be inclusive like the term
“comprising” as an open transition word without precluding any additional or other
elements.
20 [0076] Reference throughout this specification to “one embodiment” or “an
embodiment” or “an instance” or “one instance” means that a particular feature,
structure, or characteristic described in connection with the embodiment is included
in at least one embodiment of the present disclosure. Thus, the appearances of the
phrases “in one embodiment” or “in an embodiment” in various places throughout
25 this specification are not necessarily all referring to the same embodiment.
Furthermore, the features, structures, or characteristics may be combined in any
suitable manner in one or more embodiments.
[0077] The terminology used herein is to describe embodiments only and is not
intended to be limiting the disclosure. As used herein, the singular forms “a” “an”,
19
and “the” are intended to include the plural forms as well, unless the context
indicates otherwise. It will be further understood that the terms “comprises” and/or
“comprising” when used in this specification, specify the presence of stated
features, integers, steps, operations, elements, and/or components, but do not
5 preclude the presence or addition of one or more other features, integers, steps,
operations, elements, components, and/or groups thereof. As used herein, the term
“and/or” includes any combinations of one or more of the associated listed items.
It should be noted that the terms “mobile device”, “user equipment”, “user device”,
“communication device”, “device” and similar terms are used interchangeably for
10 the purpose of describing the invention. These terms are not intended to limit the
scope of the invention or imply any specific functionality or limitations on the
described embodiments. The use of these terms is solely for convenience and clarity
of description. The invention is not limited to any device or equipment, and it should
be understood that other equivalent terms or variations thereof may be used
15 interchangeably without departing from the scope of the invention as defined
herein.
[0078] As used herein, an “electronic device” or “portable electronic device”
or “user device” or “communication device” or “user equipment” or “device” refers
to any electrical, electronic, electromechanical, and computing device. The user
20 device can receive and/or transmitting one or parameters, performing
function/s, communicating with other user devices, and transmitting data to the
other user devices. The user equipment may have a processor, a display, a memory,
a battery, and an input-means such as a hard keypad and/or a soft keypad. The user
equipment may be capable of operating on any radio access technology including
25 but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low
Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For
instance, the user equipment may include, but not limited to, a mobile phone,
smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a
general-purpose computer, desktop, personal digital assistant, tablet computer,
20
mainframe computer, or any other device as may be obvious to a person skilled in
the art for implementation of the features of the present disclosure.
[0079] Further, the user device may also comprise a “processor” or “processing
unit” includes processing unit, wherein processor refers to any logic circuitry for
5 processing instructions. The 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
DSP core, a controller, a microcontroller, Application Specific Integrated Circuits,
Field Programmable Gate Array circuits, any other type of integrated circuits, etc.
10 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 is a hardware processor.
[0080] Aspects of this disclosure are directed to a system and method for
identifying serving cell parameters in mobile communication networks using a
15 standardized, vendor-independent logic. Conventional methods for interpreting
New Radio (NR) Cell Identity (NCI) values often depend on vendor-specific
software tools, manual extraction, or proprietary formats, which complicate field
diagnostics and introduce inconsistencies in cell identification. Moreover, the
conventional methodslead to inefficiencies in site validation, increased dependency
20 on proprietary systems, and slower field operations, thereby impacting overall
network deployment and maintenance timelines.
[0081] The present disclosure provides an application-based solution for
devices that captures the NCI value using system APIs and converts the captured
NCI value into a standardized 36-bit binary format. The binary format of the NCI
25 value is then processed using a universal logic that accurately derives a gNB ID and
cell ID, independent of equipment vendors. The application-based solution also
includes a User Interface (UI) that displays critical KPIs such as signal strength and
connectivity status, allowing field engineers to quickly identify and validate serving
cells. Unlike the conventional methods that require manual calculations or vendor-
21
specific tools, the disclosed approach enables real-time, accurate extraction of
network parameters, improves operational efficiency, reduces the chance of error,
and supports faster commissioning, planning, and optimization of 5G network sites.
[0082] The various embodiments throughout the disclosure will be explained
5 in more detail with reference to FIG. 1- FIG. 6.
[0083] FIG. 1 illustrates an exemplary network architecture (100) for
implementing a system (102) to identify a serving cell from a unique identifier in a
communication network (104), in accordance with embodiments of the present
disclosure.
10 [0084] Referring to FIG. 1, the network architecture (100) may include one or
more computing devices or one or more user equipment (UE) (106-1, 106-2…106-
N) that may be associated with one or more users (108-1, 108-2…108-N) and the
system (102) in an environment. In an embodiment, the one or more UE (106-1,
106-2…106-N) may be communicated to the system (102) through the
15 communication network (104). A person of ordinary skill in the art will understand
that the one or more UE (106-1, 106-2…106-N) may be individually referred to as
the UE (106) and collectively referred to as the UE (106). A person of ordinary skill
in the art will appreciate that the terms “computing device(s)” and “UE” may be
used interchangeably throughout the disclosure. Although three UE (106) are
20 depicted in FIG. 1, however, any number of the UE (106) may be included without
departing from the scope of the ongoing description. Similarly, a person of ordinary
skill in the art will understand that the one or more users (108-1, 108-2…108-N)
may be individually referred to as the user (108) and collectively referred to as the
users (108).
25 [0085] In an embodiment, the UE (106) may include smart devices operating
in a smart environment, for example, an Internet of Things (IoT) system. In such
embodiment, the UE (106) may include but is not limited to, smartphones, smart
watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.),
networked appliances, networked peripheral devices, networked lighting systems,
22
communication devices, networked vehicle accessories, networked vehicular
devices, smart accessories, tablets, smart television (TV), computers, a smart
security system, a smart home system, other devices for monitoring or interacting
with or for the users (108) and/or entities, or any combination thereof. A person of
5 ordinary skill in the art will appreciate that the UE (106) may include, but not be
limited to, intelligent multi-sensing, network-connected devices that can integrate
seamlessly with each other and/or with a central server or a cloud-computing system
or any other device that is network-connected.
[0086] In an embodiment, the UE (106) may include but is not limited to, a
10 handheld wireless communication device (e.g., a mobile phone, a smartphone, a
phablet device, and so on), a wearable computer device (e.g., a head-mounted
display computer device, a head-mounted camera device, a wristwatch computer
device, and so on), a global positioning system (GPS) device, a laptop, a tablet
computer, or another type of portable computer, a media playing device, a portable
15 gaming system, and/or any other type of computer device with wireless
communication capabilities, and the like.
[0087] In an embodiment, the UE (106) may include but is not limited to, any
electrical, electronic, electro-mechanical, or equipment, or a combination of one or
more of the above devices, such as virtual reality (VR) devices, augmented reality
20 (AR) devices, a general-purpose computer, a desktop, a personal digital assistant, a
mainframe computer, or any other computing device. In another embodiment, the
UE (106) may include one or more in-built or externally coupled accessories
including, but not limited to, a visual aid device such as a camera, an audio aid, a
microphone, a keyboard, and input devices for receiving input from the user (108)
25 or the entity such as a touchpad, a touch-enabled screen, an electronic pen, and the
like. A person of ordinary skill in the art will appreciate that the UE (106) may not
be restricted to the mentioned devices and various other devices may be used.
[0088] Referring to FIG. 1, the UE (106) may communicate with the system
(102) through a set of executable instructions residing on any Operating System
23
(OS). In an embodiment, the set of executable instructions may include a client-side
application. In an embodiment, the client-side application may be a native software
application installed on the UE (106), downloaded from an application distribution
platform such as an Application Store for iOS (provided by Apple Inc.), a Play Store
5 for Android OS (provided by Google Inc.), or other similar platforms.
[0089] The client-side application may be configured to retrieve a value of the
unique identifier from the UE (106) upon launch of the client-side application,
without requiring user input. In another embodiment, the client-side application
may be configured to retrieve the value of the unique identifier from the UE (106)
10 upon receiving the user input (e.g., selecting a menu option, pressing a refresh
button, or navigating to a diagnostics or network info screen).
[0090] In a preferred embodiment, the unique identifier includes a New Radio
(NR) Cell Identity (NCI). In an embodiment, additional unique identifiers, such as
a combination of a Public Land Mobile Network (PLMN) and NCI, a Tracking Area
15 Code (TAC), and so forth, may be used for comprehensive cell identification or
mobility tracking purposes. The client-side application may utilize platformspecific system-level APIs (e.g., Android’s TelephonyManager APIs or iOS
equivalents) to extract the value of the unique identifier and other cellular network
attributes directly from a UE’s modem or telephony service layer. The other cellular
20 network attributes may include but are not limited to, a Physical Cell Identifier
(PCI), an operating frequency band, a Reference Signal Received Power (RSRP), a
Reference Signal Received Quality (RSRQ), a Signal-to-Interference-plus-Noise
Ratio (SINR), a Received Signal Strength Indicator (RSSI), and so forth.
[0091] In an exemplary embodiment, certain network identifiers (e.g., NCI,
25 NR Cell Global Identity (NCGI), Public Land Mobile Network (PLMN) ID, PCI,
operating frequency band may be extracted from broadcast system messages such
as a System Information Block 1 (SIB1), which is periodically transmitted by the
serving cell over a Broadcast Control Channel (BCCH). The SIB1 includes critical
cell-level information including, but not limited to, the PLMN ID, the NCGI, and
24
so forth. The NCGI includes the PLMN ID and the NCI, which uniquely identifies
the serving cell within the communication network (104). In contrast, other
parameters such as, signal quality metrics such as RSRP, RSRQ, SINR, and RSSI
are derived through real-time physical layer measurements performed by the UE’s
5 modem or radio interface layer. The signal quality metrics, though not directly
embedded in the SIB1, are made accessible to the client-side application via the
platform-specific system-level APIs, enabling the client-side application to retrieve
a comprehensive set of network and signal parameters.
[0092] Once the client-side application successfully captures the value of the
10 unique identifier and other cellular network attributes, the client-side application
encapsulates the captured values into a structured payload in a predefined format
(e.g., JavaScript Object Notation (JSON) format or protocol buffer). The client-side
application may transmit the structured payload to the system (102) through the
communication network (104).
15 [0093] In an embodiment, the system (102) may be integrated within the clientside application installed on the UE (106). In another embodiment, the system (102)
may reside on a remote server, which the client-side application accesses via a
communication interface. The communication interface may include, but is not
limited to, Representational State Transfer (REST) APIs, WebSocket, HTTP-based
20 protocols, and so forth.
[0094] In an embodiment, the UE (106) may communicate with the system
(102) through the communication network (104) to send or receive various types of
data. The types of data may include, but are not limited to, the value of the unique
identifier (e.g., NCI value) associated with the serving cell, and other cellular
25 network attributes. Hereinafter, the value of the unique identifier and other cellular
network attributes, may collectively be referred to as cell-level information. The
data may be utilized by the system (102) to identify network parameters associated
with the serving cell, validate site configurations, monitor network health, and
optimize communication performance. In an embodiment, the network parameters
25
associated with the serving cell may include a Next Generation NodeB (gNB)
Identity (ID), and a cell ID. In another embodiment, additional network parameters
such as but not limited to, the PLMN ID, the PCI, Cell Global Identity (CGI), and
so forth may also be utilized depending on an application context, such as mobility
5 tracking, handover decisions, or broader network analysis.
[0095] In an embodiment, the communication network (104) may include at
least one of a 5G network, a 6G network, or the like. The communication network
(104) may enable the UE (106) to communicate with other devices in the network
architecture (100) and/or with the system (102). The communication network (104)
10 may include a wireless card or some other transceiver connection to facilitate this
communication. In another embodiment, the communication network (104) may be
implemented as or include any of a variety of different communication technologies
such as a wide area network (WAN), a local area network (LAN), a wireless
network, a mobile network, a virtual private network (VPN), the Internet or the like.
15 [0096] In an embodiment, the communication network (104) may include, by
way of example but not limitation, at least a portion of one or more networks having
one or more nodes that transmit, receive, forward, generate, buffer, store, route,
switch, process, or a combination thereof, etc. one or more messages, packets,
signals, waves, voltage or current levels, some combination thereof, or so forth. The
20 communication network (104) may also include, by way of example but not
limitation, one or more of a radio access network (RAN), a wireless network, a
wired network, the internet, the intranet, a public network, a private network, a
packet-switched network, a circuit-switched network, an ad hoc network, an
infrastructure network, a public-switched telephone network (PSTN), a cable
25 network, a cellular network, a satellite network, a fiber optic network, or some
combination thereof. In an embodiment, the system (102) may be connected to
backend servers (not shown).
[0097] In an embodiment, the UE (106) is communicatively coupled with the
communication network (104). The communication network (104) may receive a
26
connection request from the UE (106). The communication network (104) may send
an acknowledgment of the connection request to the UE (106). The UE (106) may
transmit a plurality of signals in response to the connection request.
[0098] Although FIG. 1 shows exemplary components of the network
5 architecture (100), in other embodiments, the network architecture (100) may
include fewer components, different components, differently arranged components,
or additional functional components than depicted in FIG. 1. Additionally, or
alternatively, one or more components of the network architecture (100) may
perform functions described as being performed by one or more other components
10 of the network architecture (100).
[0099] FIG. 2 illustrates an exemplary block diagram of the system (102) to
identify the serving cell from the unique identifier in the communication network
(104), in accordance with embodiments of the present disclosure.
[00100] FIG. 2, with reference to FIG. 1, illustrates the system (102), which
15 includes a data capturing unit (200), a memory (202), an interfacing unit (204), a
processing unit (206), and a database (208). The processing unit (206) includes a
data conversion module (210), a comparison module (212), a parameter
determination module (214) and a display module (216).
[00101] The data capturing unit (200) is configured to receive the structured
20 payload from the UE (106) (e.g., client-side application of the UE (106)) through a
structured data exchange mechanism established over a secure communication
channel. The secure communication channel may include, but is not limited to, a
HyperText Transfer Protocol Secure (HTTPS), a Message Queuing Telemetry
Transport (MQTT), a WebSocket, a secure File Transfer Protocol (FTP), and so
25 forth.
[00102] In an exemplary embodiment, the structured data exchange mechanism
may enable the data capturing unit (200) to consistently obtain real-time cell-level
information. The data capturing unit (200) is configured to parse the structured
payload to extract and capture the value of the unique identifier and other cellular
27
network attributes. In an exemplary embodiment, the data capturing unit (200) may
employ a parsing module or logic to decode the structured payload by identifying
predefined field names, (e.g., “NCI”, “PCI”, “RSRP”, “RSRQ”, “SINR”, “RSSI”,
“band”) and maps corresponding values to internal data structures (e.g., objects,
5 dictionaries, or database fields) for subsequent processing or analysis.
[00103] In an embodiment, the captured value of the unique identifier may be
represented in a first format. The first format may include, for example, a
hexadecimal format, a structured string format, or other suitable formats. In a
preferred embodiment, the first format is a decimal format, which is considered as
10 a raw input used in determining the network parameters. The raw input refers to an
unaltered value before any transformation, such as conversion to a binary format of
the unique identifier retrieved from the client-side application of the UE (106). The
data capturing unit (200) is configured to transmit the captured value of the unique
identifier, in the first format, to the data conversion module (210) and to transmit
15 the other cellular network attributes to the display module (216).
[00104] The memory (202) may be a non-transitory computer-readable storage
medium configured to store instructions or routines. As used herein, the term
“instructions” may refer to a sequence of commands that are written in a
programming language and may be executed by the processing unit (206) to
20 perform tasks associated with the system (102). The memory (202) may include
any non-transitory storage device including, for example, but not limited to, a
volatile memory such as a Random-Access Memory (RAM), or a non-volatile
memory such as an Erasable Programmable Read Only Memory (EPROM), a flash
memory, and the like. Embodiments of the present invention are intended to include
25 or otherwise type of the memory (202), including known related art and/or later
developed technologies.
[00105] In an embodiment, the interfacing unit (204) may include a variety of
interfaces, for example, the interfaces for data input and output devices (I/O),
storage devices, and the like. The interfacing unit (204) may facilitate
28
communication through the system (102). The interfacing unit (204) may also
provide a communication pathway for various other units/modules of the system
(102).
[00106] In an embodiment, the database (208) may be a centralized database
5 configured to store information associated with various network sites and network
cells. In an example, the database (208) may maintain a set of network site IDs, a
set of cell IDs, a set of gNB IDs, a set of NCI values, and other telecommunication
network operator-specific information stored in a defined nomenclature. In one
aspect, the telecommunication network operator-specific nomenclature may
10 include information such as a geography name, a site name, and a cluster name
associated with specific evolved NodeBs (eNBs) or gNBs. The database (208) may
serve as a central repository for all relevant network data.
[00107] In some embodiments, the database (208) may receive and consolidate
data from multiple sources, including base stations (gNBs) and centralized network
15 elements. The gNBs, or base stations, are responsible for managing a Radio Access
Network (RAN) and controlling individual cells. Each gNB may be associated with
one or more cells and periodically update the database (208) with corresponding
values of the unique identifier. Additionally, the centralized network elements such
as Network Management Systems (NMS) may also contribute NCI data to the
20 database (208) as part of broader network configuration and management processes.
The stored values of the unique identifiers may be used to support network
functions such as cell selection, handover operations, and overall network
optimization.
[00108] The database (208) is designed to interact seamlessly with other
25 modules of the system (102), such as the data conversion module (210), the
comparison module (212), the parameter determination module (214) and the
display module (216), to support the functionality of the system (102) effectively.
The database (208) may store the data that may be generated as a result of
29
functionalities implemented by any of the modules of the processing unit (206). In
an embodiment, the database (208) may be separate from the system (102).
[00109] The modules are controlled by the processing unit (206), which
executes the instructions retrieved from the memory (202). The processing unit
5 (206) further interacts with the interfacing unit (204) to facilitate user interaction
and to provide options for managing and configuring the system (102). The
processing unit (206) may be implemented as one or more microprocessors,
microcomputers, microcontrollers, digital signal processors, central processing
units, logic circuitries, and/or any devices that process the data based on operational
10 instructions.
[00110] The data conversion module (210) is communicatively coupled to the
data capturing unit (200), to receive the captured value of the unique identifier from
the data capturing unit (200). The data conversion module (210) is configured to
convert the captured value of the unique identifier from the first format to a second
15 format to generate a formatted number. In a preferred embodiment, the second
format includes the binary format that facilitates the implementation of a bit-level
logic for determining the network parameters. The bit-level logic refers to the use
of binary operations to process and interpret the binary format of the unique
identifier (e.g., NCI). The binary operations are applied to specific bits or groups of
20 bits within the unique identifier to extract or derive meaningful information such as
the network parameters (gNB ID and cell ID). The binary operations may include,
but not limited to, bitwise masking (i.e., using a mask to isolate specific bits), bit
shifting (i.e., moving bits left or right to align or extract parts of the unique
identifier), a bit-padding operation (i.e., ensuring a fixed bit-length (e.g., 36-bit) by
25 adding leading zeros), a pattern matching (i.e., identifying predefined positions in
a binary sequence to extract embedded parameters), and so forth.
[00111] In an embodiment, the data conversion module (210) may be configured
to convert the captured value of the unique identifier from the first format to the
second format by using a standard numerical method, where the value of the unique
30
identifier of the decimal format is repeatedly divided by 2, and remainders are
recorded and reversed to obtain the binary format. For example, consider the value
of the unique identifier 1152921504606846975 (which is a valid 36-bit maximum
value) in the decimal format. By applying the standard numerical method, the data
5 conversion module (210) may divide the value of the unique identifier repeatedly
by 2, keeping the remainders, and finally reverse them to obtain the binary format
111111111111111111111111111111111111.
[00112] In another embodiment, the data conversion module (210) may be
configured to implement a bitwise conversion technique which involves using
10 bitwise operators such as right shifts (>>) and bitwise AND (&) to isolate individual
bits from a decimal value. For example, taking the same value of the unique
identifier 1152921504606846975 in the decimal format, the data conversion
module (210) performs successive right shifts while applying the bitwise AND
operation with 1 (i.e., value & 1) to extract each bit. This process produces a binary
15 format representation 111111111111111111111111111111111111.
[00113] In yet another embodiment, the data conversion module (210) may
utilize platform-specific utility functions that abstract a transformation from the
decimal format to the binary format. For instance, Java’s Long.toBinaryString(long
i) or Python’s bin(i) functions may be used to obtain the value of the unique
20 identifier in the binary format from the decimal format. For instance, in Python,
bin(1152921504606846975) returns
“0b111111111111111111111111111111111111”, where the “0b” prefix denotes
binary. The data conversion module (210) is configured to transmit the formatted
number, i.e., the value of the unique identifier in the second format, to the
25 comparison module (212).
[00114] The comparison module (212) is communicatively coupled to the data
conversion module (210), to receive the formatted number from the data conversion
module (210). The comparison module (212) is configured to compare a bit length
of the formatted number with a predetermined bit length stored in the database
31
(208). In an exemplary embodiment, the comparison module (212) may be
configured to calculate the bit length of the formatted number by determining a
number of binary digits in the second format (e.g., by evaluating a string length of
the binary representation or using bitwise operations to count significant bits). The
5 comparison module (212) then retrieves the predetermined bit length (e.g., 36 bits)
from the database (208) and performs a numerical comparison between the number
of binary digits and the predetermined bit length. The predetermined bit length is a
fixed, predefined number of bits that a value must conform to for standardized
processing in the system (102). In an exemplary embodiment, the predetermined bit
10 length is 36 bits. In an embodiment, if the bit length of the formatted number is less
than the predetermined bit length, the comparison module (212) may be configured
to implement the bit-level logic (as discussed above) to initiate the binary operation
such as the bit-padding operation that involves appending one or more bits to the
formatted number in order to match the predetermined bit length. In an
15 embodiment, the bits may be binary zeros, which are added to a most significant
side (i.e., beginning) of the formatted number to obtain the predetermined bit length.
In another embodiment, the bits may be added to a least significant side (i.e., end)
of the formatted number depending on a system’s requirement. For example, if the
formatted number is 1011001 and the predetermined bit length is 10, the
20 comparison module (212) calculates a difference in a bit length, which is 3 bits in
this case. Accordingly, the comparison module (212) may append three zeros to the
formatted number, resulting in 0001011001. The comparison module (212) may be
configured to transmit the formatted number of the predetermined bit length to the
data conversion module (210).
25 [00115] In another embodiment, if the bit length of the formatted number
exceeds the predetermined bit length, the comparison module (212) may be
configured to truncate extra bits from the most significant side or the least
significant side of the formatted number, depending on system’s configuration. In
yet another embodiment, if the bit length of the formatted number is equal to the
30 predetermined bit length, the comparison module (212) may be configured to
32
transmit the formatted number of the predetermined bit length to the data
conversion module (210).
[00116] The data conversion module (210) is communicatively coupled to the
comparison module (212), to receive the formatted number of the predetermined
5 bit length from the comparison module (212). The data conversion module (210) is
configured to extract a predefined number of bits from the formatted number of the
predetermined bit length. In an exemplary embodiment, the predefined number of
bits may be 22 bits and 14 bits. In another exemplary embodiment, the predefined
number of bits may be 32 bits and 4 bits.
10 [00117] In an exemplary embodiment, the data conversion module (210) may
be configured to extract the predefined number of bits by using bit-level operations
such as bit masking and bit shifting. For instance, to extract lower 14 bits from a
36-bit formatted number, the data conversion module (210) may apply a bitwise
AND operation with a mask like 0x3FFF (which corresponds to 14 binary 1s) to
15 isolate the lower 14 bits. To extract upper 22 bits from the 36-bit formatted number,
the data conversion module (210) may perform a right shift (>>) by 14 positions,
effectively discarding the lower 14 bits and retaining the upper 22 bits. The
extracted predefined number of bits may then be used individually to derive
corresponding network parameters.
20 [00118] In another exemplary embodiment, the extraction of the predefined
number of bits involves reading specific bit positions based on a predefined schema
or format layout that defines how different network identifiers are organized within
the formatted number. In an aspect, the schema is predefined according to
telecommunication standards, such as those defined by the 3rd Generation
25 Partnership Project (3GPP), where each segment of the binary format corresponds
to a particular identifier used in a network infrastructure. For instance, in the 36-bit
formatted number, the first 22 bits may be designated for the gNB ID, while the
remaining 14 bits may represent the cell ID. The data conversion module (210)
reads the formatted number as a sequence of bits and splits the formatted number
33
at specific positions based on the predefined format. This is done by selecting a bit
range from the binary representation (e.g., bit positions 0 to 21 (inclusive) for the
gNB ID, and positions 22 to 35 (inclusive) for the cell ID).
[00119] The data conversion module (210) may be configured to convert the
5 extracted predefined number of bits of the formatted number having the
predetermined bit length from the second format to the first format to determine the
network parameters. The conversion process involves interpreting the predefined
number of bits as predefined bit segments within a binary value and converting each
bit segment into its respective decimal value.
10 [00120] In an embodiment, once the formatted number is split into the
predefined bit segments (e.g., the first 22 bits for the gNB ID and the next 14 bits
for the cell ID), each bit segment may be individually processed. The data
conversion module (210) may interpret each predefined bit segment as the binary
number and apply a standard binary-to-decimal conversion technique. For example,
15 if the 22-bit segment representing the gNB ID is 0000000000000000000001, the
binary format corresponds to the decimal value 1. Similarly, if the 14-bit segment
representing the cell ID is 00000000001101, the binary format corresponds to the
decimal value 13. The converted values in the first format (i.e., decimal format)
may be used for identifying the network parameters.
20 [00121] In another embodiment, the data conversion module (210) may utilize
the platform-specific utility functions for the conversion. For example, in Python,
the function int(binary_string, 2) may be used, whereas in Java, a function
Integer.parseInt(binaryString, 2) may be used to obtain the decimal format. The
platform-specific utility functions interpret the binary format input and return its
25 equivalent in the decimal format, thereby enabling the system (102) to represent the
network parameters in a human-readable form. The data conversion module (210)
is configured to transmit the converted predefined number of bits of the formatted
number to the parameter determination module (214).
34
[00122] The parameter determination module (214) is communicatively
coupled to the data conversion module (210), to receive the converted predefined
number of bits of the formatted number from the data conversion module (210).
The parameter determination module (214) is configured to determine the network
5 parameters for identifying the corresponding serving cell based on the converted
predefined number of bits of the formatted number having the predetermined bit
length.
[00123] In an embodiment, the parameter determination module (214) may map
the converted decimal values of the predefined bit segments, such as the gNB ID
10 and cell ID, to corresponding network entities by referencing configuration data or
lookup tables stored in the database (208). Each decimal value serves as a unique
identifier for a specific network component within an operator’s infrastructure. In
an exemplary embodiment, the parameter determination module (214) may
associate the decimal value of the gNB ID with an entry in a gNB registry or
15 mapping table and, similarly, associate the decimal value of the cell ID with a
corresponding sector or cell under the gNB. For instance, if the gNB ID is
determined to be “12345” and the cell ID is “13”, the parameter determination
module (214) may identify the specific serving cell as the 13th sector of the gNB
having identity “12345”. This enables precise identification of the serving cell for
20 further analysis, monitoring, or control operations. The parameter determination
module (214) is configured to transmit the determined network parameters to the
display module (216).
[00124] The display module (216) is communicatively coupled to the data
capturing unit (200) and the parameter determination module (214), to receive the
25 network parameters, such as the gNB ID and the cell ID, from the parameter
determination module (214), and the corresponding value of the unique identifier
from the data capturing unit (200). The display module (216) is also configured to
receive the other cellular network attributes from the data capturing unit (200). The
display module (216) is configured to display the determined network parameters
30 and the associated unique identifier on a User Interface (UI) (400) (as shown in
35
FIG. 4) of the UE (106). The display module (216) is also configured to display
values of the cellular network attributes on the UI (400) of the UE (106). The
displayed information may assist network engineers, test users, or automated tools
in verifying the association between the unique identifier and the network
5 parameters of the currently serving cell. In an embodiment, the display is dynamic,
continuously updating in real time as the UE (106) moves across different cells,
thereby reflecting changes in the associated network parameters.
[00125] In an embodiment, the display may be rendered using a graphical or
tabular interface component on the UE (106). As the system (102) processes and
10 forwards updated data, the display module (216) refreshes relevant sections of the
UI (400) using standard rendering mechanisms (e.g., updating text fields, charts, or
status panels) to reflect the latest gNB ID, cell ID, NCI, and other network
identifiers.
[00126] In an embodiment, the values of the cellular network attributes
15 displayed on the UI (400) may be presented in a user-selectable format or in an
automatically determined format based on the system’s configuration. For example,
the frequency band may be displayed in GHz (e.g., 3.5 GHz) or as a band name
(e.g., n78, n99), depending on user preferences or application settings. The
flexibility allows the user (108) to choose a most meaningful representation for
20 network diagnostics and analysis.
[00127] In an embodiment, the display module (216) may also be configured to
generate structured reports based on the network parameters, cellular network
attributes, and the unique identifier (e.g., NCI) captured and displayed. The reports
may be exported or shared in various formats (e.g., comma separated value (CSV),
25 portable document format (PDF), JSON) for offline analysis, audit trails, or
integration with network analytics tools. In one aspect, the generated reports may
be accessible not only to the users (108) on the UE (106) but also to various
operational teams such as a radio optimization team which focuses on optimizing
the RAN by ensuring efficient spectrum usage, minimizing interference, and
36
improving coverage and capacity, a radio planning team, responsible for site
planning, antenna configuration, and frequency allocation to meet deployment
goals, a business team, which oversees strategic planning, budgeting, and
performance evaluation, and so forth.
5 [00128] FIG. 3 illustrates an exemplary structure (300) of NR Cell Global
Identity (NCGI) (302), in accordance with embodiments of the present disclosure.
[00129] FIG. 3, with reference to FIG. 1 and FIG. 2, illustrates the structure
(300) of the NCGI (302).
[00130] The NCGI (302) serves as a globally unique identifier for a 5G New
10 Radio (NR) cell and is composed of three components such as a Mobile Country
Code (MCC) (304), a Mobile Network Code (MNC) (306), and NCI (308). The
MCC (304) includes three digits that uniquely identify a country where a mobile
network operates. The MNC (306) includes two or three digits and is used to
identify a specific mobile network operator within the corresponding country.
15 [00131] The NCI (308) corresponds to the NCI (i.e., unique identifier) captured
by the data capturing unit (200) of FIG. 2. The NCI (308) is a 36-bit field that
uniquely identifies an individual cell within a PLMN. The NCI (308) is logically
partitioned into two sub-components: gNB ID (310a-310b) and cell ID (312a312b). In an embodiment, the gNB ID (310a-310b) and the cell ID (312a-312b)
20 correspond to the gNB ID and the cell ID determined by the parameter
determination module (214) of FIG. 2. The gNB ID (310a-310b) is used to identify
the base station (gNB), while the cell ID (312a-312b) is used to distinguish
individual cells or sectors served by the corresponding gNB.
[00132] FIG. 3 also illustrates that the 36 bits of the NCI (308) may be allocated
25 between the gNB ID (310a-310b) and the cell ID (312a-312b) in a flexible manner,
depending on the requirements of a particular network deployment. One allocation
scheme is illustrated in FIG. 3 that reserves 22 bits for the gNB ID (310a) and 14
bits for the cell ID (312a). This allows for the identification of a large number of
cells per gNB. Another scheme allocates 32 bits for the gNB ID (310b) and only 4
37
bits for the cell ID (312b), thereby enabling support for a very large number of
gNBs with fewer sectors per node.
[00133] FIG. 4 illustrates an exemplary UI (400) for conducting network speed
tests and displaying real-time wireless network metrics on the UE (106), in
5 accordance with embodiments of the present disclosure.
[00134] FIG. 4, with reference to FIG. 1 and FIG. 2, illustrates the UI (400) that
includes a “Speed test” button (402) that, when activated, initiates a network speed
test session on the UE (106), thereby making the UI (400) interactive and enabling
real-time measurement of data throughput. Such testing may be performed by field
10 engineers, network testers, or the users (108) to evaluate download and upload
speeds of a currently connected wireless network. Upon activation, a speed test
process involves establishing a data session over an active network connection and
measuring key performance indicators such as download speed, upload speed,
latency, jitter, and so forth. The results of the speed test help assess an actual user
15 experience and may assist in detecting performance degradation, congestion, or
network limitations at a specific location.
[00135] The UI (400) is designed to present comprehensive information
regarding a wireless network environment (e.g., 5G), enabling the users (108) to
access both signal quality metrics and cell identification data in real time. At the
20 top of the UI (400), the cell identification data is displayed, including an operating
frequency band (404) (e.g., Band n99), PCI (406) (e.g., ABC), and NCI (408)
represented as a unique identifier (e.g., PQR225). Additionally, network parameters
such as gNB ID (410) (e.g., “2XYZ1”), identifying the serving base station, and
associated cell ID (412) (e.g., “1”), indicating the specific sector within the gNB,
25 are also shown on the UI (400). In an embodiment, the NCI (408) corresponds to
the NCI captured by the data capturing unit (200) of FIG. 2, and the gNB ID (410)
and the cell ID (412) correspond to the gNB ID and cell ID determined by the
parameter determination module (214) of FIG. 2.
38
[00136] In addition to the cell identification data, the UI (400) displays radio
signal metrics such as RSRP (414), RSRQ (416), SINR (418), and RSSI (420),
along with corresponding values (e.g., -76 dBm for RSRP (414), -3 dB for RSRQ
(416), 15.0 dB for SINR (418), and -48 dBm for RSSI (420)). Below the radio signal
5 metrics, the UI (400) provides a feedback section (422) displaying a number of
user-submitted feedback entries (e.g., 0) and a history section (424) that includes
information on how many times the UE (106) has connected to different network
technologies such as Wireless Fidelity (WiFi), 3G, Long-Term Evolution (LTE),
and NR (e.g., WiFi: 0, 3G: 0, LTE: 0, NR: 1).
10 [00137] At the bottom of the UI (400), a connection status indicator (426) is
displayed, labeled as “Connected,” along with a visual icon (e.g., a signal bar or
checkmark) confirming that the UE (106) is currently connected to the wireless
network. The UI (400) is particularly useful for the field engineers, the network
testers, or the users (108) conducting diagnostic checks, as it consolidates data
15 related to the serving cell and signal performance into a single, accessible screen.
[00138] In some embodiments, the UI (400) may also be configured to display
Key Performance Indicators (KPIs) relevant to an evaluation of network
performance. The KPIs may be computed based on the radio signal metrics and the
network parameters. For example, the KPIs may include network coverage, which
20 reflects a geographical or population area served by the communication network
(104); throughput, which indicates a rate of data transmission measured in Mbps or
Gbps; latency, which measures a time taken for a data packet to travel from a source
to a destination and is especially critical for real-time applications such as video
conferencing, online gaming, and autonomous systems; and reliability, which
25 assesses a network’s ability to maintain stable and consistent connections without
drops or interruptions. The KPIs may be displayed directly on the UI (400) or may
be compiled and presented as part of performance summaries or diagnostic reports,
aiding the users (108) and technical teams in assessing the quality and robustness
of the communication network (104) in real-world conditions.
39
[00139] FIG. 5 illustrates an exemplary flow diagram of a method (500) for
identifying the serving cell from the unique identifier in the communication
network (104), in accordance with an embodiment of the present disclosure.
[00140] FIG. 5, with reference to FIG. 1 and FIG. 2, illustrates the method (500)
5 for identifying the serving cell from the unique identifier by using the data capturing
unit (200), and the processing unit (206) of the system (102).
[00141] At step (502), the method (500) includes capturing, by the data
capturing unit (200), the value of the unique identifier associated with the serving
cell. In a preferred embodiment, the unique identifier includes the NCI. This step
10 includes receiving the structured payload including the cell-level information (i.e.,
the value of the unique identifier, PCI, operating frequency band, and signal quality
metrics) from the UE (106). This step further includes parsing the structured
payload to extract and capture the value of the unique identifier associated with the
serving cell and the cellular network attributes.
15 [00142] At step (504), the method (500) includes converting, by the processing
unit (206), the captured value of the unique identifier from the first format to the
second format to generate the formatted number. In a preferred embodiment, the
first format includes the decimal format, which is considered the raw input used in
determining the network parameters. The network parameters may include the gNB
20 ID and cell ID. Further, the second format may include the binary format that
facilitates the implementation of the bit-level logic for determining the network
parameters. Step (504) includes converting the captured value of the unique
identifier from the first format to the second format using one of, but not limited to,
the standard numerical method, the bitwise conversion technique, and so forth.
25 [00143] At step (506), the method (500) includes comparing, by the processing
unit (206), the bit length of the formatted number with the predetermined bit length
stored in the database (208). In a preferred embodiment, the predetermined bit
length is 36 bits. This step includes determining the number of binary digits in the
second format (e.g., by evaluating a string length of the binary representation or
40
using bitwise operations to count significant bits), retrieving the predetermined bit
length (e.g., 36 bits) from the database (208) and performing the numerical
comparison between the number of binary digits and the predetermined bit length.
In an embodiment, if the bit length of the formatted number is less than the
5 predetermined bit length, then the method (500) proceeds to step (508). In another
embodiment, if the bit length of the formatted number is equal to the predetermined
bit length, then the method (500) proceeds to step (510).
[00144] At step (508), the method (500) includes appending, by the processing
unit (206), the one or more bits to the formatted number to obtain the formatted
10 number of the predetermined bit length. In an embodiment, the bits may be binary
zeros, which are added to the most significant side (i.e., beginning) of the formatted
number to obtain the predetermined bit length. Further, the method (500) proceeds
to step (512).
[00145] At step (510), the method (500) includes not adding any extra bits to
15 the formatted number and proceeds to step (512).
[00146] At step (512), the method (500) includes converting, by the processing
unit (206), the predefined number of bits of the formatted number having the
predetermined bit length from the second format to the first format to determine the
network parameters. In an exemplary embodiment, the predefined number of bits
20 may be 22 bits and 14 bits. In another exemplary embodiment, the predefined
number of bits may be 32 bits and 4 bits. Step (512) includes interpreting the
predefined number of bits as the predefined bit segments within the binary value
and converting each bit segment into its respective decimal value. In an
embodiment, once the formatted number is split into the predefined bit segments
25 (e.g., the first 22 bits for the gNB ID and the next 14 bits for the cell ID), each bit
segment may be individually processed by using one of, but not limited to, the
standard binary-to-decimal conversion technique, platform-specific utility
functions, and so forth.
41
[00147] At step (514), the method (500) includes determining, by the processing
unit (206), the network parameters for identifying the corresponding serving cell
based on the predefined number of bits of the formatted number having the
predetermined bit length. This step includes mapping the converted decimal values
5 of the predefined bit segments such as the gNB ID and cell ID to corresponding
network entities by referencing configuration data or lookup tables stored in the
database (208), thereby enabling the method (500) to accurately associate each bit
segment with the specific base station and its respective sector or cell within the
network infrastructure.
10 [00148] At step (516), the method (500) includes displaying, by the processing
unit (206), the determined network parameters (e.g., gNB ID and cell ID) and the
value of the unique identifier associated with the identified serving cell on the UI
(400) of the UE (106). This step further includes displaying the cellular network
attributes on the UI (400) to assist the users (108) in identifying the current serving
15 cell.
[00149] FIG. 6 illustrates an exemplary computer system (600) in which, or with
which, the system (102) and the method (500) of the present disclosure may be
implemented. As shown in FIG. 6, the computer system (600) may include an
external storage device (610), a bus (620), a main memory (630), a read-only
20 memory (640), a mass storage device (650), a communication port (660), and a
processor (670). A person skilled in the art will appreciate that the computer system
(600) may include more than one processor (670) and the communication port
(660). The processor (670) may include various modules associated with
embodiments of the present disclosure.
25 [00150] In an embodiment, the external storage device (610) may be any device
that is commonly known in the art, such as, but not limited to, a memory card, a
memory stick, a solid-state drive, a hard disk drive (HDD), and so forth.
[00151] In an embodiment, the bus (620) may be communicatively coupled with
the processor(s) (670) with the other memory, storage, and communication blocks.
42
The bus (620) may be, e.g., a peripheral component interconnect (PCI)/PCI
Extended (PCI-X) bus, a small computer system interface (SCSI), a universal serial
bus (USB) or the like, for connecting expansion cards, drives and other subsystems
as well as other buses, such a front side bus (FSB), which connects the processor
5 (670) to the computer system (600).
[00152] In an embodiment, the main memory (630) may be a random-access
memory (RAM), or any other dynamic storage device commonly known in the art.
The Read-only memory (640) may be any static storage device(s) e.g., but not
limited to, a Programmable Read Only Memory (PROM) chips for storing static
10 information e.g., start-up or Basic Input/Output System (BIOS) instructions for the
processor (670).
[00153] In an embodiment, the mass storage device (650) may be any current or
future mass storage solution, which may be used to store information and/or
instructions. Exemplary mass storage solutions include but are not limited to, a
15 parallel advanced technology attachment (PATA) or a serial advanced technology
attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g.,
having universal serial bus (USB) and/or Firewire interfaces), one or more optical
discs, redundant array of independent disks (RAID) storage, e.g., an array of disks
(e.g., SATA arrays).
20 [00154] Further, the communication port (660) may be any of an RS-232 port
for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit
or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other
existing or future ports. The communication port (660) may be chosen depending
on the communication network (104), such as a local area network (LAN), wide
25 area network (WAN), or any network to which the computer system (600) connects.
[00155] Optionally, operator and administrative interfaces, e.g., a display, a
keyboard, a joystick, and a cursor control device, may also be coupled to the bus
(620) to support a direct operator interaction with the computer system (600). Other
operator and administrative interfaces may be provided through network
43
connections connected through the communication port (660). Components
described above are meant only to exemplify various possibilities. In no way should
the aforementioned exemplary computer system (600) limit the scope of the present
disclosure.
5 [00156] In an exemplary embodiment, a user equipment (UE) (106)
communicatively coupled with a communication network (104) is disclosed. The
coupling includes steps of receiving, by the communication network (104), a
connection request from the UE (106). The coupling further includes sending, by
the communication network (104), an acknowledgment of the connection request
10 to the UE (106). The coupling further includes transmitting a plurality of signals in
response to the connection request. The UE (106) is configured to generate at least
one request for identifying a serving cell from a unique identifier. The at least one
request is managed in the communication network (104) by a method (500). The
method (500) includes capturing, by a data capturing unit (200), a value of the
15 unique identifier associated with the serving cell. The method (500) further includes
converting, by a data conversion module (210), the captured value of the unique
identifier from a first format to a second format to generate a formatted number.
The method (500) further includes comparing, by a comparison module (212), a bit
length of the formatted number with a predetermined bit length. The method (500)
20 further includes appending, by the comparison module (212), one or more bits to
the formatted number to obtain the formatted number of the predetermined bit
length when the bit length of the formatted number is less than the predetermined
bit length. The method (500) further includes determining, by a parameter
determination module (214), at least one network parameter for identifying the
25 corresponding serving cell based on a predefined number of bits of the formatted
number having the predetermined bit length.
[00157] The present disclosure provides technical advancement in the field of
wireless communication, specifically in an identification and interpretation of
serving cell parameters in a communication network. This advancement addresses
30 the limitations of existing solutions by introducing a standardized, vendor-
44
independent method for extracting and interpreting New Radio (NR) Cell Identity
(NCI) values. The disclosed solution involves capturing the NCI value from UE
(Android-based devices), converting the captured NCI values to a standardized 36-
bit binary format, and using a universal logic to accurately derive network
5 parameters such as gNB ID and cell ID, regardless of the vendor. The logic is
implemented at an application level, enabling deployment on commercially
available mobile operating systems (i.e., Android platforms) without modifying a
core network infrastructure. This provides significant improvements in operational
efficiency by reducing manual effort, minimizing calculation errors, and ensuring
10 quick and accurate retrieval of network Key Performance Indicators (KPIs) such as
RSRP, RSRQ, and SINR. By implementing this invention, field engineers and
network technicians may perform real-time diagnostics, site validation, and
optimization with greater accuracy and speed, thereby improving the overall
reliability and responsiveness of network operations.
15 [00158] While the foregoing describes various embodiments of the invention,
other and further embodiments of the invention may be devised without departing
from the basic scope thereof. The scope of the invention is determined by the claims
that follow. The invention is not limited to the described embodiments, versions or
examples, which are included to enable a person having ordinary skill in the art to
20 make and use the invention when combined with information and knowledge
available to the person having ordinary skill in the art.
TECHNICAL ADVANTAGES OF THE PRESENT DISCLOSURE
[00159] The present disclosure described herein above has several technical
advantages as follows:
25 [00160] The present disclosure provides a vendor-independent mechanism for
interpreting NCI values, enabling consistent and accurate retrieval of serving cell
information across different equipment providers.
45
[00161] The present disclosure provides a system and method that enables the
conversion of NCI values into a standardized 36-bit format, thereby facilitating
accurate extraction of gNB ID and Cell ID from captured data.
[00162] The present disclosure provides a system and method that eliminates
5 the need for manual computations by field engineers, thereby reducing the
possibility of human error and enhancing operational efficiency during network
validation and troubleshooting activities.
[00163] The present disclosure provides a system and method that allows for
real-time display of network KPIs, including gNB ID and Cell ID, on an application
10 UI, thereby supporting prompt decision-making in the field.
[00164] The present disclosure ensures continuous and accurate monitoring of
network parameters even during dynamic cell transitions, enhancing the reliability
of field diagnostics and mobility tracking.
[00165] The present disclosure supports business operations by enabling field
15 engineers to execute work orders and perform site commissioning tasks with
improved accuracy and reduced turnaround time.
[00166] The present disclosure provides a logic implemented at an application
level, allowing for deployment on Android-based devices, thereby making a system
scalable, cost-effective, and easily integrated into existing workflows without
20 requiring changes to core network infrastructure.
46
WE CLAIM:
1. A method (500) for identifying a serving cell from a unique identifier in a
communication network (104), the method (500) comprising steps of:
5 capturing, by a data capturing unit (200), a value of the unique
identifier associated with the serving cell;
converting, by a data conversion module (210), the captured value
of the unique identifier from a first format to a second format to generate a
formatted number;
10 comparing, by a comparison module (212), a bit length of the
formatted number with a predetermined bit length;
appending, by the comparison module (212), one or more bits to the
formatted number to obtain the formatted number of the predetermined bit
length when the bit length of the formatted number is less than the
15 predetermined bit length; and
determining, by a parameter determination module (214), at least
one network parameter for identifying the corresponding serving cell based
on a predefined number of bits of the formatted number having the
predetermined bit length.
20
2. The method (500) as claimed in claim 1, wherein the at least one network
parameter comprises a Next Generation NodeB (gNB) Identity (ID), and a
cell ID.
25 3. The method (500) as claimed in claim 1, wherein the unique identifier
comprises a New Radio (NR) Cell Identity (NCI).
4. The method (500) as claimed in claim 1, wherein the first format comprises
a decimal format considered as a raw input used in determining the at least
30 one network parameter.
47
5. The method (500) as claimed in claim 1, wherein the second format
comprises a binary format obtained by converting the unique identifier from
the first format to facilitate implementation of bit-level logic for
determining the at least one network parameter.
5
6. The method (500) as claimed in claim 1, further comprising converting, by
the data conversion module (210), the predefined number of bits of the
formatted number having the predetermined bit length from the second
format to the first format to determine the at least one network parameter.
10
7. The method (500) as claimed in claim 1, further comprising displaying, by
a display module (216), the at least one determined network parameter and
the value of the unique identifier associated with the identified serving cell
on a User Interface (UI) (400) of a User Equipment (UE) (106).
15
8. A system (102) to identify a serving cell from a unique identifier in a
communication network (104), the system (102) comprising:
a data capturing unit (200) configured to capture a value of the
unique identifier associated with the serving cell;
20 a processing unit (206) communicatively coupled to the data
capturing unit (200), the processing unit (206) comprising:
a data conversion module (210) configured to convert the
captured value of the unique identifier from a first format to a second
format to generate a formatted number;
25 a comparison module (212) configured to:
compare a bit length of the formatted number with a
predetermined bit length; and
append one or more bits to the formatted number to obtain
the formatted number of the predetermined bit length when the
30 bit length of the formatted number is less than the
predetermined bit length; and
48
a parameter determination module (214) configured to determine
the at least one network parameter for identifying the corresponding
serving cell based on a predefined number of bits of the formatted
number having the predetermined bit length.
5
9. The system (102) as claimed in claim 8, wherein the at least one network
parameter comprises a Next Generation NodeB (gNB) Identity (ID), and a
cell ID.
10 10. The system (102) as claimed in claim 8, wherein the unique identifier
comprises a New Radio (NR) Cell Identity (NCI).
11. The system (102) as claimed in claim 8, wherein the first format comprises
a decimal format considered as a raw input used in determining the at least
15 one network parameter.
12. The system (102) as claimed in claim 8, wherein the second format
comprises a binary format obtained by converting the unique identifier from
the first format to facilitate implementation of bit-level logic for
20 determining the at least one network parameter.
13. The system (102) as claimed in claim 8, wherein the data conversion module
(210) is further configured to convert the predefined number of bits of the
formatted number having the predetermined bit length from the second
25 format to the first format to determine the at least one network parameter.
14. The system (102) as claimed in claim 8, wherein the processing unit (206)
further comprises a display module (216) configured to display the at least
one determined network parameter and the value of the unique identifier
30 associated with the identified serving cell on a User Interface (UI) (400) of
a User Equipment (UE) (106).
49
15. A User Equipment (UE) (106) communicatively coupled with a
communication network (104), the coupling comprises steps of:
receiving, by the communication network (104), a connection
5 request from the UE;
sending, by the communication network (104), an acknowledgment
of the connection request to the UE; and
transmitting a plurality of signals in response to the connection
request, wherein the UE (106) is configured to generate at least one request
10 for identifying a serving cell from a unique identifier, wherein the at least
one request is managed in the communication network (104) by a method
(500) as claimed in claim 1.