Abstract: The present disclosure relates to a method and a system for provisioning and registration of network node. The disclosure encompasses: transmitting, by a transmitting unit [102], configuration information corresponding to the network node to a Global - Self Organizing Network (G-SON) [204]; receiving, by a receiving unit [104], an identifier corresponding to the configuration information from the G-SON [204]; transmitting, by the transmitting unit [102], the identifier corresponding to the configuration information to a Global-Element Management System (G-EMS) [302]; receiving, by the receiving unit [104] via the G-EMS [302], connection information associated with a Public Land Mobile Network (PLMN) based on the identifier, the connection information corresponds to the PLMN; and registering, by a registering unit [106], the network node with the PLMN based on the connection information. [FIG. 4]
FORM 2
THE PATENTS ACT, 1970 (39 OF 1970)
& THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR PROVISIONING AND REGISTRATION OF
NETWORK NODE”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.
5 METHOD AND SYSTEM FOR PROVISIONING AND REGISTRATION
OF NETWORK NODE
FIELD OF THE DISCLOSURE
[0001] The present disclosure relates generally to the field of wireless
10 communication systems. More particularly, the present disclosure relates to method
and system for provisioning and registration of network node.
BACKGROUND
[0002] The following description of related art is intended to provide background
15 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 to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
20
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the
25 advent of the second-generation (2G) technology, digital communication and data
services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and
30 improved security. Currently, the fifth-generation (5G) technology is being
deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
2
5
[0004] Existing solutions in the field of network node provisioning and registration often rely heavily on manual intervention, which can be time-consuming, error-prone, and inefficient. Manual provisioning requires technical personnel to physically configure each network node, such as a gNodeB [206], with
10 the necessary parameters for it to connect to the Self-Organizing Network (SON)
and the Network Management System (NMS). This process can lead to inconsistencies and delays in network deployment, especially in large-scale rollouts. Furthermore, existing systems may lack the capability to dynamically update the cell database in real time as changes occur in the field. For example,
15 when attributes such as the Physical Cell Identifier (PCI) or Tracking Area Code
(TAC) change, manual intervention is typically required to update the cell database. This lack of automation can lead to outdated information being used by the SON and NMS, potentially affecting network performance and optimization. Another issue with prior art is the absence of a centralized system for managing the
20 registration of network nodes with the SON and NMS. Without a unified approach,
the process can be fragmented and inefficient, with different nodes requiring separate registration processes. This can increase the complexity of network management and reduce the overall effectiveness of network operations.
25 [0005] Thus, there exists an imperative need in the art to provide method and
system for provisioning and registration of network node, that aims to address the problems in the prior art.
30 OBJECTS OF THE INVENTION
[0006] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
3
5 [0007] It is an object of the present disclosure to provide a method and system for
provisioning and registration of network node.
[0008] It is another object of the present disclosure to provide a method and
system for provisioning and registration of network nodes that automates the
10 process, reducing the need for manual intervention and thereby improving
efficiency and accuracy.
[0009] It is another object of the present disclosure to provide a method and
system for provisioning and registration of network nodes that enables real-time
15 updating of the cell database as changes occur in the field, ensuring that the Self-
Organizing Network (SON) and Network Management System (NMS) always have access to the most current information.
[0010] It is another object of the present disclosure to provide a method and
20 system for provisioning and registration of network nodes that offers a centralized
approach to managing the registration of network nodes with the SON and NMS, streamlining the process and reducing complexity.
[0011] It is another object of the present disclosure to provide a method and
25 system for provisioning and registration of network nodes that utilizes an
Unstructured Data Storage Function (UDSF) platform for transmitting configuration information, thereby enhancing the flexibility and scalability of the system.
30 [0012] It is another object of the present disclosure to provide a method and
system for provisioning and registration of network nodes that includes verification of configuration information by the Global Self-Organizing Network (G-SON) to ensure data integrity and prevent anomalies.
4
5 [0013] It is yet another object of the present disclosure to provide a method and
system for provisioning and registration of network nodes that facilitates the registration of the network node with a Global Network Management System (NMS) to enable the retrieval of endpoints for the Zonal SON and Zonal NMS, thereby improving network management and optimization. 10
SUMMARY
[0014] This section is provided to introduce certain implementations of the
present disclosure in a simplified form that are further described below in the
detailed description. This summary is not intended to identify the key features or
15 the scope of the claimed subject matter.
[0015] An aspect of the present disclosure provides a method for provisioning and registration of network node. The method includes transmitting, by a transmitting unit, configuration information corresponding to the network node to a Global -
20 Self Organizing Network (G-SON). The method further includes receiving, by a
receiving unit, an identifier corresponding to the configuration information from the G-SON. The method further includes transmitting, by the transmitting unit, the identifier corresponding to the configuration information to a Global-Element Management System (G-EMS). The method further includes receiving, by the
25 receiving unit via the G-EMS, connection information associated with a Public
Land Mobile Network (PLMN) based on the identifier, the connection information corresponds to the PLMN. Thereafter, the method includes registering, by a registering unit, the network node with the PLMN based on the connection information.
30
[0016] In an aspect, the configuration information is transmitted utilizing an Unstructured Data Storage Function (UDSF) platform.
5
5 [0017] In an aspect, the identifier is received upon verification of the
configuration information by the G-SON, the verification comprising checking for anomalies.
[0018] In an aspect, the configuration information comprises at least one of a
10 serial number of the network node, a height of the network node, and geographic
coordinates of the network node.
[0019] In an aspect, the method further comprises registering the network node
with the PLMN comprises: transmitting, by the transmitting unit, the identifier to
15 the G-EMS; receiving, by the receiving unit from the G-EMS, a Uniform Resource
Locator (URL) corresponding to each of a Local EMS and Zonal SON based on the identifier; and transmitting, by the transmitting unit, the URL corresponding to the Local EMS to the network node for configuration with the Local EMS.
20 [0020] In an aspect, the method further comprises receiving, by the receiving unit,
a Cell Global Identify (CGI) from the local EMS based on the URL corresponding to the local EMS, the CGI is provided by the local EMS after establishing a connection between the network node and the local EMS, wherein the CGI identifies the network node amongst a plurality of network nodes.
25
[0021] In an aspect, the connection information associated with the PLMN comprises at least one of a Mobile Network Code (MNC) and a Mobile Country Code (MCC).
30 [0022] In an aspect, the method further comprises registering, by the registering
unit, the network node with a Global Network Management System (NMS) to enable retrieving endpoints for the Zonal SON and Zonal NMS.
6
5 [0023] Another aspect of the present disclosure comprises a system for
provisioning and registration of network node. The system includes a transmitting unit configured to transmit configuration information corresponding to the network node to a Global - Self Organizing Network (G-SON). The system further includes a receiving unit configured to receive an identifier corresponding to the
10 configuration information from the G-SON. The system further includes the
transmitting unit is configured to transmit the identifier corresponding to the configuration information to a Global-Element Management System (G-EMS). The system further includes the receiving unit further configured to receive, via the G¬EMS, connection information associated with a Public Land Mobile Network
15 (PLMN) based on the identifier, the connection information corresponds to the
PLMN. The system further includes a registering unit configured to register the network node with the PLMN based on the connection information.
[0024] Yet another aspect of the present disclosure relates to a non-transitory
20 computer-readable storage medium storing instructions for provisioning and
registration of a network node, the instructions include executable code which,
when executed by a one or more units of a system, causes: a transmitting unit to
transmit configuration information corresponding to the network node to a Global
- Self Organizing Network (G-SON); a receiving unit to receive an identifier
25 corresponding to the configuration information from the G-SON; the transmitting
unit is configured to transmit the identifier corresponding to the configuration
information to a Global-Element Management System (G-EMS); the receiving unit
to receive, via the G-EMS, connection information associated with a Public Land
Mobile Network (PLMN) based on the identifier, the connection information
30 corresponds to the PLMN; and a registering unit to register the network node with
the PLMN based on the connection information.
BRIEF DESCRIPTION OF DRAWINGS
7
5 [0025] The accompanying drawings, which are incorporated herein, and
constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the
10 principles of the present disclosure. Some drawings may indicate the components
using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
15
[0026] FIG. 1 illustrates an exemplary block diagram of a system for provisioning and registration of network node, in accordance with exemplary embodiments of the present disclosure.
20 [0027] FIG. 2 illustrates an exemplary flow diagram indicating the process
implemented by the system for provisioning and registration of network node, in accordance with exemplary embodiments of the present disclosure.
[0028] FIG. 3A illustrates an exemplary flow diagram indicating the process of
25 Node Register Flow in accordance with the exemplary embodiments of the present
disclosure.
[0029] FIG. 3B illustrates an exemplary flow diagram indicating the process of
Initial Param Flow for deployment of one or more network nodes in a Radio Access
30 Network (RAN), in accordance with the exemplary embodiments of the present
disclosure.
8
5 [0030] FIG. 4 illustrates an exemplary flow diagram indicating a method for
provisioning and registration of network node, in accordance with an embodiment of the present disclosure.
[0031] FIG. 5 illustrates an exemplary block diagram of a computing device upon
10 which an embodiment of the present disclosure may be implemented.
[0032] The foregoing shall be more apparent from the following more detailed description of the disclosure.
15 DESCRIPTION
[0033] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that
20 embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter can each be used independently of one another or with any combination of other features. 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
25 fully addressed by any 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.
30 [0034] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. 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
9
5 arrangement of elements without departing from the spirit and scope of the
disclosure as set forth.
[0035] It should be noted that the terms "mobile device", "user equipment", "user device”, “communication device”, “device” and similar terms are used
10 interchangeably for 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 particular type of device or equipment, and it should be understood that other equivalent terms
15 or variations thereof may be used interchangeably without departing from the scope
of the invention as defined herein.
[0036] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one
20 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 obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without
25 unnecessary detail in order to avoid obscuring the embodiments.
[0037] Also, it is noted that individual embodiments may be described as a
process which is depicted as a flowchart, a flow diagram, a data flow diagram, a
structure diagram, or a block diagram. Although a flowchart may describe the
30 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 steps not included in a figure.
10
5 [0038] The word “exemplary” and/or “demonstrative” is used herein to mean
serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or
10 designs, nor is it meant to preclude equivalent exemplary structures and techniques
known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding
15 any additional or other elements.
[0039] 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 is capable of receiving 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,
30 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.
[0040] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data
11
5 transfer are also expected to evolve and replace the older generations of
technologies. In the field of wireless data communications, the dynamic
advancement of various generations of cellular technology are also seen. The
development, in this respect, has been incremental in the order of second generation
(2G), third generation (3G), fourth generation (4G), and now fifth generation (5G),
10 and more such generations are expected to continue in the forthcoming time.
[0041] Radio Access Technology (RAT) refers to the technology used by mobile devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base
15 stations, which are responsible for providing the wireless connection. Further, each
RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS
20 (Universal Mobile Telecommunications System), LTE (Long-Term Evolution),
and 5G. The choice of RAT depends on a variety of factors, including the network infrastructure, the available spectrum, and the mobile devices/device’s capabilities. Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available network
25 resources.
[0042] Cell database (DB) is responsible for storing information of the one or
more network nodes which has attributes like SAP ID, GNB serial number, MCC,
MNC, TAC, PCI. G-SON is responsible for managing various zonal/local SON.
30 Global EMS is responsible for providing local/zonal EMS and zonal/local SON
endpoints. Local EMS is responsible for providing initial configuration data of one or more network nodes from cell database. Zonal SON is responsible for managing deployed the one or more network nodes to perform SON use cases like automatic neighbour relationship, physical cell identity collision/confusion resolution. PLMN
12
5 – It is public land mobile network which holds information of the MCC & the MNC.
Unstructured Data Storage Function (UDSF)is a platform for transmitting the configuration information.
[0043] As discussed in the background section, the existing solutions in the field
10 of network node provisioning and registration often rely mostly on manual
intervention, which can be time-consuming, error-prone, and inefficient. Manual provisioning requires technical personnel to physically configure each network node, such as a gNodeB [206], with the necessary parameters for it to connect to the Self-Organizing Network (SON) and the Network Management System (NMS).
15 This process can lead to inconsistencies and delays in network deployment,
especially in large-scale rollouts. Furthermore, existing systems may lack the capability to dynamically update the cell database in real time as changes occur in the field. For example, when attributes such as the Physical Cell Identifier (PCI) or Tracking Area Code (TAC) change, manual intervention is typically required to
20 update the cell database. This lack of automation can lead to outdated information
being used by the SON and NMS, potentially affecting network performance and optimization. Another issue with prior art is the absence of a centralized system for managing the registration of network nodes with the SON and NMS. Without a unified approach, the process can be fragmented and inefficient, with different
25 nodes requiring separate registration processes. This can increase the complexity of
network management and reduce the overall effectiveness of network operations.
[0044] The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by providing a method and system for
30 the automated provisioning and registration of network nodes, thereby significantly
reducing the reliance on manual intervention. By automating the process, the invention seeks to eliminate the time-consuming, error-prone steps involved in manually configuring each network node for connection to Self-Organizing Networks (SON) and Network Management Systems (NMS). This automation is
13
5 expected to lead to more consistent and efficient network deployments, particularly
beneficial in large-scale rollouts. Moreover, the invention introduces a real-time
updating mechanism for the cell database as changes occur in the field, such as
modifications to the Physical Cell Identifier (PCI) or Tracking Area Code (TAC).
This feature addresses the current lack of automation in updating the cell database,
10 ensuring that the SON and NMS always utilize the most current information,
thereby potentially enhancing network performance and optimization. Another
significant aspect of the present disclosure is the centralized management of
network node registration with the SON and NMS. This unified approach simplifies
the registration process, reducing fragmentation and inefficiency, and thereby
15 streamlining network management and improving the overall effectiveness of
network operations. By utilizing an Unstructured Data Storage Function (UDSF)
platform for transmitting configuration information, the invention also enhances the
flexibility and scalability of the network provisioning and registration process. The
method includes a verification step by the Global Self-Organizing Network (G-
20 SON) to ensure data integrity and prevent anomalies, further contributing to the
reliability and robustness of the network.
[0045] It would be appreciated by the person skilled in the art that the present disclosure offers a comprehensive solution to the problems identified in the prior
25 art by automating the provisioning and registration process, ensuring real-time
updates to the cell database, and centralizing the management of network node registration. These advancements represent a significant improvement over existing technologies, minimizing manual intervention, and paving the way for more efficient, reliable, and optimized network operations.
30
[0046] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
14
5 [0047] FIG. 1 illustrates an exemplary block diagram of a system [100] for
provisioning and registration of a network node, in accordance with exemplary embodiments of the present disclosure. The system [100] is for provisioning and registration of network node. As shown in FIG. 1, the system [100] includes at least one transmitting unit [102], at least one receiving unit [104] and at least one
10 registering unit [106], wherein all the components are assumed to be connected to
each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure. Also, in FIG. 1 only a few units are shown, however, the system [100] may comprise multiple such units or the system [100] may comprise any such numbers of said units, as required to implement the features
15 of the present disclosure.
[0048] The system [100] includes a transmitting unit [102] configured to transmit
configuration information corresponding to the network node (such as gNodeB
[206]) as shown in FIG. 2 to a Global - Self Organizing Network (G-SON) [204] as
20 shown is FIG. 2. The configuration information transmitted by the transmitting unit
[102] includes parameters such as the serial number, height, and geographic
coordinates of the network node (such as gNodeB [206]), as well as other relevant
data required for the network node (such as gNodeB [206]) to be properly integrated
into the network infrastructure. The configuration information facilitates the G-
25 SON [204] to correctly identify, authenticate, and configure the network node (such
as gNodeB [206]) for optimal operation within the Public Land Mobile Network
(PLMN). The transmitting unit [102] ensures that the configuration information is
accurately and efficiently conveyed to the G-SON [204], thereby enabling the
seamless integration of the network node (such as gNodeB [206]) into the network.
30
[0049] The system [100] includes a receiving unit [104] communicatively coupled to the transmitting unit [102]. The receiving unit [104] is configured to receive an identifier corresponding to the configuration information from the G-SON [204]. The identifier serves as a unique reference for the network node (such as gNodeB
15
5 [206]) within the network infrastructure, enabling the G-SON [204] to recognize
and manage the network node (such as gNodeB [206]) effectively. The identifier may be generated by the G-SON [204] after validating the configuration information transmitted by the network node (such as gNodeB [206]) via the transmitting unit [102]. The validation process involves checking for anomalies or
10 inconsistencies in the configuration data to ensure that the network node (such as
gNodeB [206]) meets the necessary criteria for integration into the network. Once the identifier is received by the receiving unit [104], it is used in subsequent communications to facilitate the registration of the network node (such as gNodeB [206]) with other network components, such as the Global-Element Management
15 System (G-EMS) [302] and the Public Land Mobile Network (PLMN).
[0050] The transmitting unit [102] is further configured to transmit the identifier corresponding to the configuration information to a Global-Element Management System (G-EMS) [302]. The transmission enables the G-EMS [302] to recognize
20 and authenticate the network node (such as gNodeB [206]). The G-EMS [302] is
responsible for overseeing the configuration and operation of network elements like the network node (such as gNodeB [206]). Upon receiving the identifier, the G¬EMS [302] uses it to retrieve and validate the network node's configuration information thereby ensuring that the network node (such as gNodeB [206]) is
25 configured correctly and is compatible with the network's standards and protocols.
Additionally, the G-EMS [302] may use the identifier to determine the appropriate connection information for the network node (such as gNodeB [206]), such as the Public Land Mobile Network (PLMN) it should connect to, as well as any specific parameters required for its operation within the network. The transmission of the
30 identifier from the transmitting unit [102] to the G-EMS [302] facilitates in
establishing a secure and efficient communication link between the network node (such as gNodeB [206]) and the network management systems for the seamless integration and ongoing management of the network node (such as gNodeB [206]) within the network infrastructure.
16
5
[0051] The receiving unit [104] is further configured to receive, via the Global-Element Management System (G-EMS) [302], connection information associated with a Public Land Mobile Network (PLMN) based on the identifier, wherein the connection information corresponds to the PLMN. The connection information
10 includes crucial network parameters such as the Mobile Network Code (MNC) and
Mobile Country Code (MCC) that are essential for the network node (such as gNodeB [206]) to establish communication within the PLMN. Upon receiving the identifier from the G-SON [204], the G-EMS [302] retrieves the relevant connection information for the network node (such as gNodeB [206]) and transmits
15 it to the receiving unit [104] such that the network node (such as gNodeB [206]) is
equipped with the necessary information to successfully integrate and operate within the PLMN.
[0052] The system [100] includes the registering unit [106] communicatively
20 coupled to the receiving unit [104]. The registering unit [106] is configured to
register the network node (such as gNodeB [206]) with the Public Land Mobile
Network (PLMN) based on the connection information. The registering involves
configuring the network node (such as gNodeB [206]) with the necessary
parameters to ensure its successful integration into the PLMN. The connection
25 information received by the receiving unit [104] from the Global-Element
Management System (G-EMS) [302] includes critical data such as Mobile Network Code (MNC) and Mobile Country Code (MCC), which are essential for the network node (such as gNodeB [206]) to communicate effectively within the PLMN.
30 [0053] Once the receiving unit [104] has received the connection information, it
is passed on to the registering unit [106], which then proceeds to configure the network node (such as gNodeB [206]) accordingly. This may involve setting up network interfaces, adjusting communication protocols, and ensuring compliance with network standards. The registration process ensures that the network node
17
5 (such as gNodeB [206]) is correctly configured and authenticated, thereby enabling
seamless communication and interaction with other network components and services within the PLMN.
[0054] Referring to FIG. 2, an exemplary flow diagram [200] indicating a process
10 of cell database Create, Read, Update, Delete (CRUD), in accordance with
exemplary embodiments of the present disclosure. The flow diagram [200]
comprises an Unstructured Data Storage Function (USDF) [202], the G-SON [204],
the network node (such as gNodeB [206]), and cell database [212]. Also, all of the
components/units of the flow diagram [200] are assumed to be connected to each
15 other unless otherwise indicated below. Also, in FIG. 2 only a few units are shown,
however, the flow diagram [200] may comprise multiple such units or the flow diagram [200] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
20 [0055] In operation, the UDSF [202] serves as a repository and management
interface for the cell database [212], handling the CRUD operations. It ensures that when a gNodeB [206] is deployed, the cell database [212] is updated with the current values in real time, facilitating the use cases for SON and NMS. When the gNodeB [206] shares the details, the UDSF [202] either updates the Cell Database
25 [212] if the data is new or validated, or rejecting the update if it is deemed a
duplicate or invalid. The data sent by the gNodeB [206] is processed further for validation process [208] before it is stored in the Cell Database [212]. However, if the validation process [208] determines that the data is invalid, then the cell database update request is rejected [210]. The validation process [208] ensures that
30 only correct and consistent data is used to update the cell database [212]. If changes
occur in the field, such as an update to parameters like the Physical Cell Identifier (PCI) or the Tracking Area Code (TAC), the G-SON [204] communicates these changes back to the UDSF [202], which then updates the Cell Database [212] accordingly. This configuration enables a robust, automated, and real-time update
18
5 mechanism for cell database management for the adaptive and efficient functioning
of modern telecommunication networks. It allows for a seamless and automatic registration of new gNodeBs and the update of network parameters, thereby reducing manual intervention and potential human error.
10 [0056] Referring to FIG. 3A, an exemplary flow diagram [300] indicating the
process of Node Register Flow in accordance with the exemplary embodiments of the present disclosure. The flow diagram [300] comprises the network node (such as gNodeB [206]), the cell database [212] and the G-EMS [302]. Also, all of the components/units of the flow diagram [300] are assumed to be connected to each
15 other unless otherwise indicated below. Also, in FIG. 3A only a few units are
shown, however, the flow diagram [300] may comprise multiple such units or the flow diagram [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
20 [0057] In operation, upon deployment, gNodeB [206] initiates the registration
process by transmitting its configuration information to the G-EMS [302]. The G-EMS [302] acting as an intermediary that verifies the gNodeB's [206] data, ensuring its accuracy and integrity before updating or referencing the Cell Database [212]. Once the gNodeB [206] is verified, the G-EMS [302] proceeds to facilitate the
25 registration by associating the gNodeB [206] with the necessary network
parameters stored within the Cell Database [212].
[0058] At [304], the connection information is retrieved based on the Public Land
Mobile Network (PLMN) to which the gNodeB [206] will connect. The G-EMS
30 [302] uses the information from the Cell Database [212] to provide the gNodeB
[206] with relevant endpoints, such as URLs for the Local EMS [306] and Zonal SON, based on the gNodeB’s [206] PLMN. This automated interaction streamlines the process, allowing for efficient and accurate registration of the network node
19
5 (such as gNodeB [206]) within the overall network system, and represents a
strategic departure from manual, error-prone methods that were traditionally used.
[0059] Referring to FIG. 3B, an exemplary flow diagram [350] indicating the process of Initial Param Flow for provisioning and registration of network node
10 (such as gNodeB [206]), in accordance with the exemplary embodiments of the
present disclosure. The flow diagram [350] comprises the network node (such as gNodeB [206]), the cell database [212] and the local-EMS [306]. Also, all of the components/units of the flow diagram [350] are assumed to be connected to each other unless otherwise indicated below. Also, in FIG. 3B only a few units are
15 shown, however, the flow diagram [350] may comprise multiple such units or the
flow diagram [350] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
[0060] In operation, the gNodeB [206] begins the process by sending a request for
20 initial parameters to the Local EMS [306]. At [308], the Local EMS [306] then
interacts with the Cell Database [212] to prepare the necessary configuration data
in the JSON format, which is required for the gNodeB’s [206] operation. The
configuration data includes essential information such as cell identity, network
settings, and other operational parameters critical for the gNodeB [206] to function
25 correctly within the network infrastructure. Once the configuration data is compiled
and formatted, the Local EMS [306] transmits this information back to the gNodeB
[206]. The gNodeB [206] then uses this data to configure itself, aligning its
operational parameters with those of the network to ensure optimal connectivity
and performance. The automated flow of configuration data from the Cell Database
30 [212] to the gNodeB [206], facilitated by the Local EMS [306], exemplifies the
invention's advantage in reducing manual intervention and streamlining the provisioning and registration process. It reflects a system designed for efficiency and reliability in updating and maintaining network nodes in a dynamic network environment.
20
5
[0061] Referring to FIG. 4, an exemplary method flow diagram [400] indicating
a method for provisioning and registration of network node (such as gNodeB [206]),
in accordance with an embodiment of the present disclosure is shown. In an
implementation, the method [400] is performed by the system [100]. As shown in
10 FIG. 4, the method [400] starts at step [402].
[0062] At step [404], the method [400] as disclosed by the present disclosure comprises transmitting, by the transmitting unit [102], configuration information corresponding to the network node (such as gNodeB [206]) to the G-SON [204].
15 The configuration information transmitted by the transmitting unit [102] includes
parameters such as the serial number, height, and geographic coordinates of the network node (such as gNodeB [206]), as well as other relevant data required for the network node (such as gNodeB [206]) to be properly integrated into the network infrastructure. The configuration information facilitates the G-SON [204] to
20 correctly identify, authenticate, and configure the network node (such as gNodeB
[206]) for optimal operation within the Public Land Mobile Network (PLMN). The transmitting unit [102] ensures that the configuration information is accurately and efficiently conveyed to the G-SON [204], thereby enabling the seamless integration of the network node (such as gNodeB [206]) into the network.
25
[0063] At step [406], the method [400] as disclosed by the present disclosure comprises receiving, by a receiving unit [104], an identifier corresponding to the configuration information from the G-SON [204]. receive an identifier corresponding to the configuration information from the G-SON [204]. The
30 identifier serves as a unique reference for the network node (such as gNodeB [206])
within the network infrastructure, enabling the G-SON [204] to recognize and manage the network node (such as gNodeB [206]) effectively. The identifier may be generated by the G-SON [204] after validating the configuration information transmitted by the network node (such as gNodeB [206]) via the transmitting unit
21
5 [102]. The validation process involves checking for anomalies or inconsistencies in
the configuration data to ensure that the network node (such as gNodeB [206])
meets the necessary criteria for integration into the network. Once the identifier is
received by the receiving unit [104], it is used in subsequent communications to
facilitate the registration of the network node (such as gNodeB [206]) with other
10 network components, such as the Global-Element Management System (G-EMS)
[302] and the Public Land Mobile Network (PLMN).
[0064] At step [408], the method [400] as disclosed by the present disclosure comprises transmitting, by the transmitting unit [102], the identifier corresponding
15 to the configuration information to the G-EMS [302]. The transmission enables the
G-EMS [302] to recognize and authenticate the network node (such as gNodeB [206]). The G-EMS [302] is responsible for overseeing the configuration and operation of network elements like the network node (such as gNodeB [206]). Upon receiving the identifier, the G-EMS [302] uses it to retrieve and validate the network
20 node's configuration information thereby ensuring that the network node (such as
gNodeB [206]) is configured correctly and is compatible with the network's standards and protocols. Additionally, the G-EMS [302] may use the identifier to determine the appropriate connection information for the network node (such as gNodeB [206]), such as the Public Land Mobile Network (PLMN) it should connect
25 to, as well as any specific parameters required for its operation within the network.
The transmission of the identifier from the transmitting unit [102] to the G-EMS [302] facilitates in establishing a secure and efficient communication link between the network node (such as gNodeB [206]) and the network management systems for the seamless integration and ongoing management of the network node (such as
30 gNodeB [206]) within the network infrastructure.
[0065] At step [410], the method [400] as disclosed by the present disclosure comprises receiving, by the receiving unit [104] via the G-EMS [302], connection
22
5 information associated with the PLMN based on the identifier, the connection
information corresponds to the PLMN.
[0066] Lastly, step [412], the method [400] as disclosed by the present disclosure comprises registering, by the registering unit [106], the network node (such as
10 gNodeB [206]) with the PLMN based on the connection information. The
connection information includes crucial network parameters such as the Mobile Network Code (MNC) and Mobile Country Code (MCC) that are essential for the network node (such as gNodeB [206]) to establish communication within the PLMN. Upon receiving the identifier from the G-SON [204], the G-EMS [302]
15 retrieves the relevant connection information for the network node (such as gNodeB
[206]) and transmits it to the receiving unit [104] such that the network node (such as gNodeB [206]) is equipped with the necessary information to successfully integrate and operate within the PLMN.
20 [0067] Once the receiving unit [104] has received the connection information, it
is passed on to the registering unit [106], which then proceeds to configure the network node (such as gNodeB [206]) accordingly. This may involve setting up network interfaces, adjusting communication protocols, and ensuring compliance with network standards. The registration process ensures that the network node
25 (such as gNodeB [206]) is correctly configured and authenticated, thereby enabling
seamless communication and interaction with other network components and services within the PLMN.
[0068] Thereafter, the method terminates at step [414]. 30
[0069] FIG. 5 illustrates an exemplary block diagram of a computing device [500] (also referred to herein as a computer system [500]) upon which an embodiment of the present disclosure may be implemented. In an implementation, the computing device implements the method for provisioning and registration of a network node
23
5 (such as gNodeB [206]) using the system [100]. In another implementation, the
computing device itself implements the method for provisioning and registration of a network (such as gNodeB [206]) by using one or more units configured within the computing device, wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
10
[0070] The computing device [500] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device [500] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may
15 operate independently or as part of a network and can perform a variety of tasks
such as data storage, retrieval, and analysis. Additionally, computing device [500] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications.
20
[0071] The computing device [500] may include a bus [502] or other communication mechanism for communicating information, and a processor [504] coupled with bus [502] for processing information. The processor [504] may be, for example, a general-purpose microprocessor. The computing device [500] may also
25 include a main memory [506], such as a random-access memory (RAM), or other
dynamic storage device, coupled to the bus [502] for storing information and instructions to be executed by the processor [504]. The main memory [506] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [504]. Such
30 instructions, when stored in non-transitory storage media accessible to the processor
[504], render the computing device [500] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [500] further includes a read only memory (ROM) [508] or other static
24
5 storage device coupled to the bus [502] for storing static information and
instructions for the processor [504].
[0072] A storage device [510], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [502] for storing information and
10 instructions. The computing device [500] may be coupled via the bus [502] to a
display [512], such as a cathode ray tube (CRT), for displaying information to a computer user. An input device [514], including alphanumeric and other keys, may be coupled to the bus [502] for communicating information and command selections to the processor [504]. Another type of user input device may be a cursor
15 controller [516], such as a mouse, a trackball, or cursor direction keys, for
communicating direction information and command selections to the processor [504], and for controlling cursor movement on the display [512]. This inputs device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
20
[0073] The computing device [500] may implement the techniques described herein using customized hard-wired logic, one or more Application-Specific Integrated Circuits (ASICs) or Field Programmable Gate Arrays (FPGAs), firmware and/or program logic which in combination with the computing device
25 [500] causes or programs the computing device [500] to be a special-purpose
machine. According to one embodiment, the techniques herein are performed by the computing device [500] in response to the processor [504] executing one or more sequences of one or more instructions contained in the main memory [506]. Such instructions may be read into the main memory [506] from another storage
30 medium, such as the storage device [510]. Execution of the sequences of
instructions contained in the main memory [506] causes the processor [504] to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
25
5 [0074] The computing device [500] also may include a communication interface
[518] coupled to the bus [502]. The communication interface [518] provides a two-way data communication coupling to a network link [520] that is connected to a local network [522]. For example, the communication interface [518] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
10 a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [518] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [518] sends and receives electrical,
15 electromagnetic or optical signals that carry digital data streams representing
various types of information.
[0075] The computing device [500] can send messages and receive data, including program code, through the network(s), the network link [520] and the
20 communication interface [518]. In the Internet example, a server [530] might
transmit a requested code for an application program through the Internet [528], the Internet Service Provider (ISP) [526], the Host [524], the local network [522] and the communication interface [518]. The received code may be executed by the processor [504] as it is received, and/or stored in the storage device [510], or other
25 non-volatile storage for later execution.
[0076] The present disclosure provides a non-transitory computer-readable
storage medium storing instructions for provisioning and registration of a network
node (such as gNodeB [206]), the instructions include executable code which, when
30 executed by a one or more units of a system, causes: a transmitting unit [102] to
transmit configuration information corresponding to the network node (such as gNodeB [206]) to a Global - Self Organizing Network (G-SON) [204]; a receiving unit [104] to receive an identifier corresponding to the configuration information from the G-SON [204]; the transmitting unit [102] is configured to transmit the
26
5 identifier corresponding to the configuration information to a Global-Element
Management System (G-EMS) [302]; the receiving unit [104] to receive, via the G¬
EMS [302], connection information associated with a Public Land Mobile Network
(PLMN) based on the identifier, the connection information corresponds to the
PLMN; and a registering unit [106] to register the network node (such as gNodeB
10 [206]) with the PLMN based on the connection information.
[0077] The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by providing a method and system for
the automated provisioning and registration of network nodes. This automation
15 reduces the reliance on manual intervention, thereby decreasing the likelihood of
errors, increasing efficiency, and speeding up the deployment process.
[0078] The present disclosure addresses the issue of real-time updates to the cell database by enabling the dynamic sharing and updating of cell details between the
20 network node (such as gNodeB [206]) and the Self-Organizing Network (SON)
through the Unstructured Data Storage Function (UDSF) [202] platform. This ensures that the SON and Network Management System (NMS) always have access to the most current information, thereby enhancing network performance and optimization. Furthermore, the present disclosure provides a centralized approach
25 to managing the registration of network nodes with the SON and NMS. By utilizing
a Global Self-Organizing Network (G-SON) [204] and a Global-Element Management System (G-EMS) [302], the system streamlines the registration process, reducing complexity and improving the overall effectiveness of network operations. The method and system outlined in the claims also include mechanisms
30 for verifying configuration information to prevent anomalies and ensure data
integrity. This adds an additional layer of reliability to the provisioning and registration process.
5 [0079] Further, in accordance with the present disclosure, it is to be acknowledged
that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The
10 functionality of specific units, as disclosed in the disclosure, should not be
construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
15
[0080] While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments
20 of the present disclosure will be apparent to those skilled in the art, whereby it is to
be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
5 We Claim:
1. A method [400] for provisioning and registration of a network node, the
method [400] comprising:
transmitting, by a transmitting unit [102], configuration information
corresponding to the network node to a Global - Self Organizing Network (G-
10 SON) [204];
receiving, by a receiving unit [104], an identifier corresponding to the configuration information from the G-SON [204];
transmitting, by the transmitting unit [102], the identifier
corresponding to the configuration information to a Global-Element
15 Management System (G-EMS) [302];
receiving, by the receiving unit [104] via the G-EMS [302],
connection information associated with a Public Land Mobile Network
(PLMN) based on the identifier, the connection information corresponds to
the PLMN; and
20 registering, by a registering unit [106], the network node with the
PLMN based on the connection information.
2. The method as claimed in claim 1, wherein the configuration information is
transmitted utilizing an Unstructured Data Storage Function (UDSF) [202]
25 platform.
3. The method as claimed in claim 1, wherein the identifier is received upon
verification of the configuration information by the G-SON [204], the
verification comprises checking for anomalies.
30
4. The method as claimed in claim 1, wherein the configuration information
comprises at least one of a serial number of the network node, a height of the
network node, and geographic coordinates of the network node.
5 5. The method as claimed in claim 1, wherein registering the network node with
the PLMN comprises:
transmitting, by the transmitting unit [102], the identifier to the G-EMS [302];
receiving, by the receiving unit [104] from the G-EMS [302], a
10 Uniform Resource Locator (URL) corresponding to each of a Local EMS
[306] and Zonal SON based on the identifier; and
transmitting, by the transmitting unit [102], the URL corresponding to the Local EMS [306] to the network node for configuration with the Local EMS [306]. 15
6. The method as claimed in claim 5, further comprising:
receiving, by the receiving unit [104], a Cell Global Identify (CGI)
from the local EMS [306] based on the URL corresponding to the local EMS
[306], the CGI is provided by the local EMS [306] after establishing a
20 connection between the network node and the local EMS [306], wherein the
CGI identifies the network node amongst a plurality of network nodes.
7. The method as claimed in claim 1, wherein the connection information
associated with the PLMN comprises at least one of a Mobile Network Code
25 (MNC) and a Mobile Country Code (MCC).
8. The method as claimed in claim 5, wherein the method comprises registering,
by the registering unit [106], the network node with a Global Network
Management System (NMS) to enable retrieving endpoints for the Zonal
30 SON and Zonal NMS.
9. A system [100] for provisioning and registration of a network node, the
system [100] comprising:
5 a transmitting unit [102] configured to transmit configuration
information corresponding to the network node to a Global - Self Organizing Network (G-SON) [204];
a receiving unit [104] configured to receive an identifier
corresponding to the configuration information from the G-SON [204];
10 the transmitting unit [102] is configured to transmit the identifier
corresponding to the configuration information to a Global-Element Management System (G-EMS) [302];
the receiving unit [104] further configured to receive, via the G-EMS
[302], connection information associated with a Public Land Mobile Network
15 (PLMN) based on the identifier, the connection information corresponds to
the PLMN; and
a registering unit [106] configured to register the network node with the PLMN based on the connection information.
20 10. The system as claimed in claim 9, wherein the configuration information is
transmitted utilizing an Unstructured Data Storage Function (UDSF) [202] platform.
11. The system as claimed in claim 9, wherein the identifier is received upon
25 verification of the configuration information by the G-SON [204], the
verification comprises checking for anomalies.
12. The system as claimed in claim 9, wherein the configuration information
comprises at least one of a serial number of the network node, a height of the
30 network node, and geographic coordinates of the network node.
13. The system as claimed in claim 9, comprises:
the transmitting unit [102] configured to transmit the identifier to the G-EMS [302];
5 the receiving unit [104] configured to receive, from the G-EMS [302],
a Uniform Resource Locator (URL) corresponding to each of a Local EMS [306] and Zonal SON based on the identifier; and
the transmitting unit [102] is configured to transmit the URL
corresponding to the Local EMS [306] to the network node for configuration
10 with the Local EMS [306].
14. The system as claimed in claim 13, comprises:
the receiving unit [104] is configured to receive a Cell Global Identify
(CGI) from the local EMS [306] based on the URL corresponding to the local
15 EMS [306], the CGI is provided by the local EMS [306] after establishing a
connection between the network node and the local EMS [306], wherein the
CGI identifies the network node amongst a plurality of network nodes.
15. The system as claimed in claim 9, wherein the connection information
20 associated with the PLMN comprises at least one of a Mobile Network Code
(MNC) and a Mobile Country Code (MCC).
16. The system as claimed in claim comprises the registering unit [106]
configured to register the network node with a Network Management System
(NMS) to enable retrieving endpoints for the Zonal SON and Zonal NMS.
| # | Name | Date |
|---|---|---|
| 1 | 202321046059-STATEMENT OF UNDERTAKING (FORM 3) [08-07-2023(online)].pdf | 2023-07-08 |
| 2 | 202321046059-PROVISIONAL SPECIFICATION [08-07-2023(online)].pdf | 2023-07-08 |
| 3 | 202321046059-FORM 1 [08-07-2023(online)].pdf | 2023-07-08 |
| 4 | 202321046059-FIGURE OF ABSTRACT [08-07-2023(online)].pdf | 2023-07-08 |
| 5 | 202321046059-DRAWINGS [08-07-2023(online)].pdf | 2023-07-08 |
| 6 | 202321046059-FORM-26 [12-09-2023(online)].pdf | 2023-09-12 |
| 7 | 202321046059-Proof of Right [06-10-2023(online)].pdf | 2023-10-06 |
| 8 | 202321046059-ORIGINAL UR 6(1A) FORM 1 & 26)-231023.pdf | 2023-11-06 |
| 9 | 202321046059-ENDORSEMENT BY INVENTORS [14-06-2024(online)].pdf | 2024-06-14 |
| 10 | 202321046059-DRAWING [14-06-2024(online)].pdf | 2024-06-14 |
| 11 | 202321046059-CORRESPONDENCE-OTHERS [14-06-2024(online)].pdf | 2024-06-14 |
| 12 | 202321046059-COMPLETE SPECIFICATION [14-06-2024(online)].pdf | 2024-06-14 |
| 13 | Abstract1.jpg | 2024-07-20 |
| 14 | 202321046059-FORM 3 [01-08-2024(online)].pdf | 2024-08-01 |
| 15 | 202321046059-Request Letter-Correspondence [13-08-2024(online)].pdf | 2024-08-13 |
| 16 | 202321046059-Power of Attorney [13-08-2024(online)].pdf | 2024-08-13 |
| 17 | 202321046059-Form 1 (Submitted on date of filing) [13-08-2024(online)].pdf | 2024-08-13 |
| 18 | 202321046059-Covering Letter [13-08-2024(online)].pdf | 2024-08-13 |
| 19 | 202321046059-CERTIFIED COPIES TRANSMISSION TO IB [13-08-2024(online)].pdf | 2024-08-13 |
| 20 | 202321046059-FORM 18 [24-03-2025(online)].pdf | 2025-03-24 |