DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
SYSTEM AND METHOD MANAGING ONE OR MORE BASE STATIONS (GNBs) IN A TELECOMMUNICATIONS NETWORK

2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention relates to the field of wireless communication systems, more particularly relates to a method and system for managing one or more base stations (GNBs) in a telecommunication network.
BACKGROUND OF THE INVENTION
[0002] In traditional network systems, upgrading one or more base stations, such as GNBs (GNodeBs), required code-level modifications, rigorous testing, and subsequent deployment processes. The GNBs, or GNodeBs, are essential components of wireless networks responsible for transmitting and receiving signals between a user device and a core network. GNBs play a crucial role in various network functions, including signal transmission, reception, processing, and routing. Upgrading GNBs is necessary to incorporate new features, support advanced standards, and improve network performance.
[0003] Each new release of GNBs demanded manual intervention and significant development efforts, leading to delays and disruptions in network operations. Moreover, the upgrade process often involves downtime, further impeding the timely deployment of new features and standards.
[0004] As wireless technologies continue to advance rapidly, frequent releases of new base station versions have become commonplace. These upgrades aim to incorporate improved functionalities, support new standards, and enhance overall network performance. However, efficiently managing these upgrades while ensuring uninterrupted network operations poses a considerable challenge.
[0005] In the prior art, traditional network systems required significant manual efforts and downtime to upgrade base stations. Code-level modifications, extensive testing, and deployment procedures were time-consuming and disruptive to network operations. These challenges hindered the timely deployment of new features and standards, posing obstacles to efficient network management.
[0006] Various attempts have been made to address these challenges, such as automated upgrade processes and real-time data handling. However, these approaches often lacked the flexibility, adaptability, and seamless integration required for efficient base station upgrades. Therefore, there is a need for a system and a method that eliminates manual intervention, code-level modifications, and downtime remains unmet.
SUMMARY OF THE INVENTION
[0007] One or more embodiments of the present disclosure provides a method and system for managing one or more base stations in a telecommunication network.
[0008] In one aspect of the present invention, a method for managing one or more base stations in the telecommunication network is disclosed. The method includes the step of receiving, by one or more processor(s), a plurality of provisioning requests from a User Equipment (UE) for at least one of, multiple new GNodeB (GNB) versions and data from one or more GNBs, wherein each of the plurality of provisioning requests includes one or more policies specific to a respective new GNB version. The method further includes the step of provisioning, by the one or more processor(s), based on the received provisioning requests, the one or more policies. The method further includes the step of decoding, by the one or more processor(s), the data received from the one or more GNBs related to the respective new GNB version according to the provisioned one or more policies. The method further includes the step of enriching, by the one or more processor(s), the decoded data using the provisioned one or more policies and a rule metadata. The method further includes the step of storing, by the one or more processor(s), the enriched data in a database.
[0009] In another embodiment, the method further comprises enabling a User Interface (UI), by the one or more processor(s), to enable a user to configure at least one of: a new GNB version and definitions of the one or more policies and the rule metadata for each new GNB version.
[0010] In yet another embodiment, the method further comprises handling the decoding of data pertaining to the new GNB version, by the one or more processor(s), received from the one or more GNBs based on the configured one or more policies.
[0011] In yet another embodiment, the method further comprises facilitating, by the one or more processor(s), bidirectional communication between a conductor and a normalizer for provisioning the one or more policies to decode the data received from the one or more GNBs, wherein at least one of: the conductor is further configured to handle the decoding of data received from the one or more GNBs based on the configured one or more policies, and the normalizer is configured to perform data enrichment by applying the defined one or more policies and the rule metadata.
[0012] In yet another embodiment, further comprising the step of enabling, by the one or more processor(s), creation of the one or more policies and rule-metadata for different versions in real-time.
[0013] In yet another embodiment, each GNB version has its own application slice for independent processing of data.
[0014] In another aspect of the present invention, a system for managing one or more base stations (GNBs) in a telecommunications network is disclosed. The system includes a User Interface (UI) configured to receive a plurality of provisioning requests from a User Equipment (UE) for at least one of, multiple new GNodeB (GNB) versions and data from one or more GNBs, wherein each of the plurality of provisioning requests includes one or more policies specific to a respective new GNB version. The system includes a conductor configured to provision, based on the received provisioning requests, the one or more policies. The system further includes a decoder configured to decode the data received from the one or more GNBs related to the respective new GNB version according to the provisioned one or more policies. The system further includes a normalizer configured to enrich the decoded data using the provisioned one or more policies and a rules metadata. The system further includes a database configured to store the enriched data.
[0015] In yet another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by a processor. The processor is configured to receive, a plurality of provisioning requests from a User Equipment (UE) for at least one of, multiple new GNodeB (GNB) versions and data from one or more GNBs, wherein each of the plurality of provisioning requests includes one or more policies specific to a respective new GNB version. The processor is further configured to provision, based on the received provisioning requests, the one or more policies. The processor is further configured to decode, the data received from the one or more GNBs related to the respective new GNB version according to the provisioned one or more policies. The processor is further configured to enrich the decoded data using the provisioned one or more policies and a rule metadata. The processor is further configured to store the enriched data in a database.
[0016] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0017] 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 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.
[0018] FIG. 1 is an exemplary block diagram of an environment for managing one or more base stations (GNBs) in a telecommunication network, according to one or more embodiments of the present invention;
[0019] FIG. 2 is an exemplary block diagram of a system for managing one or more base stations (GNBs) in the telecommunication network, according to one or more embodiments of the present invention;
[0020] FIG. 3 is an exemplary architecture of the system of FIG. 2, according to one or more embodiments of the present invention;
[0021] FIG. 4 is an exemplary signal flow diagram illustrating the flow for managing one or more base stations (GNBs) in the telecommunication network, according to one or more embodiments of the present disclosure; and
[0022] FIG. 5 is a flow diagram of a method for managing one or more base stations (GNBs) in the telecommunication network, according to one or more embodiments of the present invention.
[0023] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0024] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0025] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0026] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0027] The present invention introduces a multi-version policy framework for seamless handling of upgrades in one or more base stations (GNBs), specifically addressing the challenges associated with code-level modifications, testing, and deployment downtime. The invention eliminates a need for manual intervention and enables automatic adaptation to version-level changes. By adopting a Transparent Communication Engine (TCE), the invention ensures smooth decoding and ingestion of data from multiple versions in real-time without downtime. TCE is the solution where it adopts version level changes automatically and handles the decoding of new version smoothly in runtime without any manual intervention and downtime. The inventive step lies in the application-level implementation of the policy framework, enabling parallel support for multiple versions. The solution includes creation of policies and a rule metadata in runtime, facilitating efficient data processing. The invention streamlines an upgrade process, eliminates development efforts, testing phases, and downtime, thereby enhancing operational efficiency in the telecommunication network.
[0028] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing the one or more base stations (GNBs) in a telecommunication network, according to one or more embodiments of the present invention. The environment 100 includes a User Equipment (UE) 102, a server 104, a telecommunication network 106, a system 108, and one or more base stations (GNBs) 110.
[0029] For the purpose of description and explanation, the description will be explained with respect to one or more user equipment’s (UEs) 102, or to be more specific will be explained with respect to a first UE 102a, a second UE 102b, and a third UE 102c, and should nowhere be construed as limiting the scope of the present disclosure. Each of the at least one UE 102 namely the first UE 102a, the second UE 102b, and the third UE 102c is configured to connect to the server 104 via the telecommunication network 106.
[0030] In an embodiment, each of the first UE 102a, the second UE 102b, and the third UE 102c is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as Virtual Reality (VR) devices, Augmented Reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0031] The telecommunication network 106 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an 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 network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The telecommunication network 106 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0032] The telecommunication network 106 may also 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 telecommunication network 106 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an 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 network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0033] The environment 100 includes the server 104 accessible via the telecommunication network 106. The server 104 may include by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, a processor executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0034] The environment 100 includes the one or more base stations (GNBs) 110 which is communicably coupled to the server 104 via the telecommunication network 106. The one or more base stations (GNBs) 110 acts as a central connection point for a wireless device to communicate. The one or more base stations (GNBs) 110 further connects a device to other networks or devices, usually through a dedicated high bandwidth wire or a fiber optic connection. The one or more base stations (GNBs) 110 acts as a gateway between a wired network and the wireless network.
[0035] In an embodiment, as wireless technologies continue to advance rapidly, frequent releases of new one or more base stations (GNBs) 110 versions have become commonplace. These upgrades in the one or more base stations (GNBs) 110 aims to incorporate improved functionalities, support new standards, and enhance overall network performance. Whenever the one or more base stations (GNBs) 110 are upgraded, then the upgraded one or more base stations (GNBs) 110 are inferred as the new version of the respective one or more base stations (GNBs) 110. In particular, the upgraded one or more base stations (GNBs) 110 are referred as a respective new GNB version. For example, the upgraded one or more base stations (GNBs) 110 pertains to the respective GNB version 20.
[0036] The environment 100 further includes the system 108 communicably coupled to the server 104, the one or more base stations (GNBs) 110, and the UE 102, via the telecommunication network 106. The system 108 is adapted to be embedded within the server 104 or is embedded as the individual entity.
[0037] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0038] FIG. 2 is an exemplary block diagram of the system 108 for managing one or more base stations (GNBs) 110 in the telecommunication network 106, according to one or more embodiments of the present invention.
[0039] As per the illustrated and preferred embodiment, the system 108 for managing one or more base stations (GNBs) 110 in the telecommunication network 106, the system 108 includes one or more processors 202, a memory 204, and a database 206. The one or more processors 202 includes a User Interface (UI) 208, a conductor 210, a decoder 212, a normalizer 214, and a message broker 216. The one or more processors 202, hereinafter referred to as the processor 202, may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions. However, it is to be noted that the system 108 may include multiple processors as per the requirement and without deviating from the scope of the present disclosure. Among other capabilities, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204.
[0040] As per the illustrated embodiment, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204 as the memory 204 is communicably connected to the processor 202. The memory 204 is configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to manage one or more base stations (GNBs) 110 in the telecommunication network 106. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0041] In one embodiment, the processor 202 is a Transparent Communication Engine (TCE) which receives data from the one or more base stations (GNBs) 110. The TCE includes a policy framework which enables simultaneous provision and deciphering of the data with multiple new GNB versions. In particular, the policy framework provides an overarching structure that guides how one or more policies and procedures will be developed, approved, communicated and reviewed. An effective policy framework clearly documents the processes to be followed at each stage of a policy life cycle.
[0042] As per the illustrated embodiment, the database 206 is configured to store data pertaining to the one or more base stations (GNBs) 110. The database 206 is configured to store the enriched data. The database 206 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 206 types are non-limiting and may not be mutually exclusive e.g., the database can be both commercial and cloud-based, or both relational and open-source, etc.
[0043] In an embodiment, the User Interface (UI) 208 of the processor 202 is configured to receive a plurality of provisioning requests from the UE 102 for at least one of, multiple new GNodeB (GNB) versions and data from the one or more GNBs. In particular, each of the plurality of provisioning requests are transmitted by the UE 102 which includes one or more policies specific to its respective new GNB version. The plurality of provisioning requests specifies provisioning/adding of the one or more policies defined by the user for the new GNB version. In another embodiment, the one or more policies are deployed or added in the system 108.The User Interface (UI) 208 is configured to enable a user to configure at least one of, a new GNB version and definition of the one or more policies and a rule metadata for each new GNB version. Utilizing the User Interface (UI) 208 the user configures the one or more policies and the rule metadata in real time for each new GNB version. The one or more policies are the policies defined by the user for each new GNB version which allows to define at least one of, a process for managing the one or more GNBs 110. In particular, a policy is a piece of configuration that controls a specific aspect of processing during the handling of decoding the data received from the one or more GNBs 110 related to the respective new GNB version at run time. The rule meta data are one or more rules predefined by the user which are utilized in at least one of, provisioning, decoding and enriching data received from the one or more GNBs 110 without any disruptions in network operations.
[0044] For example, whenever the new GNB version is installed in the telecommunication network 106, the one or more policies and the rule metadata are provisioned/created by the user in order to make the the new GNB version compatible with the system 108. In particular, the compatibility refers to the data transmitted by the respective new GNB version should be accepted by the system 108 based on the one or more policies and the rule metadata are provisioned/created by the user.
[0045] In one embodiment, the data received from the one or more GNBs related to the respective new GNB version includes, at least one of, but not limited to, Non-Standalone Radio Signaling Link (NRSL) data. In an alternate embodiment, the data received from the one or more GNBs related to the respective new GNB version includes, at least one of, but not limited to, a file pertaining to updates in the one or more GNBs, and a payload. In computing and telecommunications, the payload is the part of transmitted data that is the actual intended message. In particular, the payload refers to the actual information that is transmitted over the telecommunication network 106. It only includes the data and excludes any headers or trailers added in the data unit by different network architecture layers.
[0046] In an embodiment, the conductor 210 of the processor 202 is configured to provision, the one or more policies based on the received provisioning requests. The conductor 210 is further configured to handle the decoding of the data received from one or more GNBs related to the respective new GNB version based on the configured one or more policies. In an alternate embodiment, the conductor 210 is further configured to process the data. The processing of the data includes at least one of, but not limited to, data ingestion. The data ingestion is the process of obtaining and importing data for immediate use or storage in the database 206.
[0047] In an embodiment, the decoder 212 of the processor 202 is configured to decode the data received from the one or more GNBs related to the respective new GNB version according to the provisioned one or more policies. The decoder 212 performs a decoding process which ensures compatibility with the specified GNB version. The decoding process are essential for extracting meaningful/required information from the encoded data and making it suitable for analysis or presentation.
[0048] In an alternate embodiment, it is to be noted that the conductor 210 and the decoder 212 are the same entity which are configured to decode the data from the one or more GNBs 110 related to the respective new GNB versions according to the provisioned one or more policies without deviating from the scope of the present disclosure. The conductor 210 is a component which performs the decoding process which ensures compatibility with the respective new GNB version. In one embodiment, the data is decoded in order to make compatible with the system 108. The decoding process is essential for extracting meaningful/required information from the encoded data and making it suitable for analysis or presentation.
[0049] In an embodiment, the normalizer 214 of the processor 202 is configured to enrich the decoded data using the provisioned one or more policies and the rule metadata. In particular, the normalizer 214 of the processor 202 preprocess the data which includes at least one of, but not limited to, data normalization. The data normalization is the process of at least one of, but not limited to, reorganizing the data, removing the redundant data, and removing null values from the data. The main goal of the normalizer 214 is to achieve a standardized data format across the entire system 108. In particular, the normalizer 214 is configured to perform data enrichment by applying the defined one or more policies and the rule metadata. The data enrichment is the process of incorporating new updates and the decoded data into the database 206 to improve accuracy and add missing information. The normalizer 214 ensures that the processed data such as enriched data is stored appropriately in the database 206 for subsequent retrieval and analysis. In an alternate embodiment, the rule metadata pertains to the one or more policies configured by the user specifically for the normalizer 214. The enriched data pertaining to the new GNB versions which is stored in the database 206 ensures the adaptability and compatibility of the new GNB versions of one or more GNBs 110 with the system 108. Advantageously, the one or more GNBs with are managed by the system 108 by adapting the new GNB versions within the system 108 without interrupting the telecommunication network 106 operations
[0050] In an alternate embodiment, the normalizer 214 is configured to receive the plurality of provisioning requests from the UE 102 for at least one of, multiple new GNB versions and data from one or more GNBs version. In particular, each of the plurality of provisioning requests includes one or more policies specific to the respective new GNB version.
[0051] In an embodiment, the message broker 216 of the processor 202 is configured to receive the decoded data from the at least one of, the conductor 210 and the decoder 212 and forwards the decoded data to the normalizer 214 for further processing. The message broker 216 acts as a translator which enables multiple applications, systems and services to communicate with each other and exchange information. The message broker 216 acts as an intermediary which bidirectionally connects at least one of, the conductor 210 and the decoder 212 with the normalizer 214. Additionally, the message broker 216 relays instructions and feedback from the normalizer 214 back to the conductor 210.
[0052] The User Interface (UI) 208, the conductor 210, the decoder 212, the normalizer 214, and the message broker 216 in an exemplary embodiment, are implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 202. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 204 may store instructions that, when executed by the processing resource, implement the processor 202. In such examples, the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[0053] FIG. 3 illustrates an exemplary architecture for the system 108, according to one or more embodiments of the present invention. More specifically, FIG. 3 illustrates the system 108 for managing one or more base stations (GNBs) 110 in the telecommunication network 106.
[0054] FIG. 3 shows communication between the system 108, and the one or more base stations (GNBs) 110. For the purpose of description of the exemplary embodiment as illustrated in FIG. 3, the one or more base stations (GNBs) 110 uses network protocol connection to communicate with the system 108. In an embodiment, the network protocol connection is the establishment and management of communication between the one or more base stations (GNBs) 110 and system 108 over the telecommunications network 106 (as shown in FIG. 1) using a specific protocol or set of protocols. The network protocol connection includes, but not limited to, Session Initiation Protocol (SIP), System Information Block (SIB) protocol, Transmission Control Protocol (TCP), User Datagram Protocol (UDP), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Simple Network Management Protocol (SNMP), Internet Control Message Protocol (ICMP), Hypertext Transfer Protocol Secure (HTTPS) and Terminal Network (TELNET).
[0055] In an embodiment, the User Interface (UI) 208 of the processor 202 includes a variety of interfaces, for example, a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The User Interface (UI) 208 allows the user to configure at least one of, the new GNB version and definitions of the one or more policies and the rule metadata for each new GNB version.
[0056] For example, the system 108 has the policy framework where the user defines the one or more policies of the new GNB version. These one or more policies are provisioned from the User Interface (UI) 208. These one or more policies are provisioned at the conductor 210 and the normalizer 214. Upon provisioning of the one or more policies, the conductor 210 and normalizer 214 creates its own slice to support decoding and the ingestion of these newly added GNB versions.
[0057] In one embodiment, the conductor 210 receives the plurality of provisioning requests for provisioning a new version of at least one of, multiple new GNodeB (GNB) and data from one or more GNBs from the User Interface (UI) 208. In one embodiment, the UI 208 is integrated with the UE 102. For example, let us assume in one or more telecom circles such as Mumbai circle and an Ahmedabad circle different GNBs are installed. The GNB of the Mumbai circle is working on GNB version 2.1 and the GNB of the Ahmedabad circle is working on GNB version 2.3. In particular, the version of the one or more GNBs are changed according to the updates made in the one or more GNBs. Along with the plurality of provisioning requests the conductor 210 receives the one or more policies and the rule metadata configured by the user. Based on the configured one or more policies and the rule metadata the conductor 210 decodes the data received from the User Interface (UI) 208 and pushes the decoded data to the message broker 216. The message broker 216 is software that enables applications, systems and services to communicate with each other and exchange information. The message broker communicates by translating messages between formal messaging protocols. For example, a message broker may be used to manage a workload queue or message queue for multiple receivers, providing reliable storage, guaranteed message delivery and perhaps transaction management. Further, the message broker 216 transmits the decoded data to the normalizer 214 which enriches the decoded data and thereafter the normalizer 214 stores the enriched data in the database 206.
[0058] In an alternate embodiment, the normalizer 214 also receives the plurality of provisioning requests for provisioning the new version of at least one of, multiple new GNodeB (GNB) and data from one or more GNB version from the User Interface (UI) 208. Thereafter, the normalizer 214 enriches the data and stores the enriched data in the database 206.
[0059] FIG. 4 is a signal flow diagram illustrating the flow for managing one or more base stations (GNBs) 110 in the telecommunication network 106, according to one or more embodiments of the present disclosure.
[0060] At step 402, the data pertaining to the one or more GNBs 110 related to the respective new GNB version is transmitted by at least one of, the one or more base stations (GNB) 110 to the system 108.
[0061] At step 404, the User Interface (UI) 208 of the system 108 receives the data from the one or more base stations (GNB) 110. Further, utilizing the User Interface (UI) 208 the user configures the one or more policies specific to the respective new GNB version and transmits the plurality of provisioning requests to the conductor 210, the plurality of provisioning requests includes at least one of, but not limited to, the received data from the one or more base stations (GNB) 110 and the configured one or more policies.
[0062] At step 406, the conductor 210 and the decoder 212 transmits the decoded data to the normalizer 214 subsequent to decoding the data received from the one or more GNBs 110 related to the respective new GNB versions based on the configured one or more policies.
[0063] At step 408, the normalizer 214 transmits the data to the database 206 in order to store the enriched data subsequent to enriching the decoded data received from the conductor 210 and the decoder 212 based on the configured one or more policies and the rule metadata.
[0064] At step 410, the database 206 transmits a response to the user via the User Interface (UI) 208 in order to notify the user regarding the storage of the enriched data.
[0065] FIG. 5 is a flow diagram of a method 500 for managing one or more base stations (GNBs) 110 in the telecommunication network 106, according to one or more embodiments of the present invention. For the purpose of description, the method 500 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0066] At step 502, the method 500 includes the step of receiving, the plurality of provisioning requests from the UE for at least one of, multiple new GNodeB (GNB) versions and data from one or more GNBs, wherein each of the plurality of provisioning requests includes one or more policies specific to a respective new GNB version. In one embodiment, the User Interface (UI) 208 of the processor 202 is configured to transmit the plurality of provisioning requests from the user to the system 108. The plurality of provisioning requests includes one or more policies configured by the user in real time for each of the respective new GNB versions. For example, let us assume a particular GNB among the one or more base stations (GNBs) 110 is upgraded and inferred as the new GNB version 20. Here, the plurality of provisioning requests specifies the provisioning of the new GNB version 20 and its corresponding one or more policies. The one or more policies define one or more features that are upgraded in the respective new GNB version 20. The plurality of provisioning requests further includes the data in the form of at least one of, but not limited to, the Non-Standalone (NSA) Radio Signaling Link NRSL data pertaining to the respective new GNB version 20.
[0067] At step 504, the method 500 includes the step of provisioning, based on the received provisioning requests, the one or more policies. In particular, the conductor 210 of the processor is configured to provision the one or more policies for decoding the data received from the one or more GNBs related to the respective new GNB versions based on the received provisioning requests. The one or more policies are provisioned to support the respective new GNB versions. For example, based on the received provisioning requests, the one or more policies for the respective new GNB version 20 are provisioned to the conductor 210. In one embodiment, these one or more policies define the rules and instructions for decoding the data received from the respective new GNB version 20.
[0068] At step 506, the method 500 includes the step of decoding, the data received from the one or more GNBs related to the respective GNBs according to the provisioned one or more policies. In one embodiment, the decoder 212 of the processor 202 is configured to decode the data received from the one or more GNBs related to the respective new GNB versions according to the provisioned one or more policies. For example, the NRSL data received from the respective GNB version 20 is decoded by the decoder 212 based on the one or more policies. The decoding process ensures compatibility with the respective GNB version 20 such that the NRSL data is compatible with the system 108. In another example, let us assume the data received from the one or more GNBs 110 includes at least one of, but not limited to, a file, or a payload in a particular format. Further, the user defines one or more policies in order to decode the file, or the payload. Based on the defined one or more policies, the decoder 212 decodes the file, or the payload in the format which is compatible with the system 108.
[0069] In an alternate embodiment, the conductor 210 of the processor 202 includes the decoder 212 which is configured to decode the data received from the one or more GNBs related to the respective new GNB versions according to the provisioned one or more policies. Upon successfully decoding the data, the conductor 210 pushes the decoded data to the message broker 216 for efficient distribution of the decoded data.
[0070] At step 510, the method 500 includes the step of enriching the decoded data using the provisioned one or more policies and the rule metadata. In one embodiment, the normalizer 214 of the processor 202 is configured to enrich the decoded data using the provisioned one or more policies and the rule metadata. For example, the normalizer 214 is configured to remove the null data and redundant data or repetitive data from the decoded data.
[0071] In one embodiment, the conductor 210 and normalizer 214 create own slice to support decoding, ingestion and enrichment of these newly added respective GNB version 20. For example, each of the multiple new GNB versions are supported by its own application slice for independent data processing. In particular, the data processing such as data decoding and data enrichment performed independently by the at least one of, the conductor 210 and the normalizer 214 in different slices of a single application The conductor 210 and normalizer 214 create own slice by network slicing which is a telecommunications configuration that allows multiple networks to be created on top of a common physical infrastructure. Each “slice” or portion of the network are allocated based on the specific needs of the application, use case, or user.
[0072] At step 512, the method 500 includes the step of storing, the enriched data in a database. In one embodiment, the database 206 is configured to store the enriched data. For example, the enriched data pertaining to the respective GNB version 20 is stored in the database 206 which ensures that the enriched data is available for at least one of, but not limited to, retrieval and analysis. The database 206 serves as the repository for the enriched data, enabling efficient organization and utilization.
[0073] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 202. The processor 202 is configured to receive a plurality of provisioning requests from a User Equipment (UE) for at least one of, multiple new GNodeB (GNB) versions and data from the one or more GNBs, wherein each of the plurality of provisioning requests includes one or more policies specific to a respective GNB new version. The processor 202 is further configured to provision based on the received provisioning requests, the one or more policies. The processor 202 is further configured to decode, the data received from the one or more GNBs related to the respective new GNB version according to the provisioned one or more policies. The processor 202 is further configured to enrich, the decoded data using the provisioned one or more policies and a rule metadata. The processor 202 is further configured to store the enriched data in a database 206.
[0074] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-5) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0075] The present disclosure provides technical advancement such as eliminating the need of development efforts for every GNB version upgrade. Traditional systems required code-level changes, testing, and deployment, leading to delays and disruptions. With the present technique, such development efforts are no longer required, streamlining the upgrade process. Further, the invention reduces or eliminates the need for extensive testing associated with GNB version upgrades. By automatically adapting to new versions and handling decoding in real-time, the system ensures smooth data processing without the traditional testing delays. Furthermore, in traditional systems, upgrading GNBs often required downtime during the transition phase. The system eliminates this downtime, enabling uninterrupted network operations. The smooth decoding and ingestion of data in real-time ensure a seamless transition without disrupting the telecommunication network. The invention allows for parallel support of multiple GNB versions. Each version has its own application slice within the conductor and normalizer components, enabling independent processing of data across different versions. This parallel support facilitates efficient handling of data from various GNB versions simultaneously. The system enables real-time adaptation to new GNB versions. When a new version is provisioned, the policies corresponding to that version are configured from the UI. The conductor and normalizer components automatically create their own slices to support the decoding and ingestion of the newly added versions, ensuring immediate compatibility and smooth data processing.
[0076] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS

[0077] Environment - 100;
[0078] User Equipment (UE) - 102;
[0079] Server - 104;
[0080] Network- 106;
[0081] System -108;
[0082] On or more base stations (GNBs) – 110;
[0083] Processor - 202;
[0084] Memory - 204;
[0085] Database – 206;
[0086] User Interface (UI) – 208;
[0087] Conductor – 210
[0088] Decoder – 212;
[0089] Normalizer– 214;
[0090] Message broker – 216.

,CLAIMS:CLAIMS
We Claim:
1. A method (500) for managing one or more base stations (GNBs) (110) in a telecommunications network (106), the method (500) comprising the steps of:
receiving, by one or more processor(s) (202), a plurality of provisioning requests from a User Equipment (UE) for at least one of, multiple new GNodeB (GNB) versions and data from one or more GNBs, wherein each of the plurality of provisioning requests includes one or more policies specific to a respective new GNB version;
provisioning, by the one or more processor(s) (202), based on the received provisioning requests, the one or more policies;
decoding, by the one or more processor(s) (202), the data received from the one or more GNBs related to the respective new GNB version according to the provisioned one or more policies;
enriching, by the one or more processor(s) (202), the decoded data using the provisioned one or more policies and a rule metadata; and
storing, by the one or more processor(s) (202), the enriched data in a database (206).

2. The method (500) of claim 1, the method (500) further comprising enabling a User Interface (UI) (208), by the one or more processor(s) (202), to enable a user to configure at least one of: the new GNB version and definitions of the one or more policies and the rule metadata for each new GNB version.

3. The method (500) of claim 1, the method (500) further comprises handling the decoding of data pertaining to the new GNB version, by the one or more processor(s) (202), received from the one or more GNBs based on the configured one or more policies.

4. The method (500) of claim 1, the method further comprises facilitating, by the one or more processor(s) (202), bidirectional communication between a conductor (210) and a normalizer (214) for provisioning the one or more policies to decode the data received from the one or more GNBs, wherein at least one of: the conductor (210) is further configured to handle the decoding ] of data received from the one or more GNBs based on the configured one or more policies, and the normalizer (214) is configured to perform data enrichment by applying the defined one or more policies and the rule metadata .

5. The method (500) of claim 1, further comprising the step of enabling, by the one or more processor(s) (202), creation of the one or more policies and rule-metadata for different versions in real-time.

6. The method of (500) claim 1, wherein each GNB version has its own application slice for independent processing of data.

7. A system (108) for managing one or more base stations (GNBs) (110) in a telecommunications network (106), the system (108) comprising:
User Interface (UI) (208) configured to receive a plurality of provisioning requests from a User equipment (UE) for at least one of, multiple new GNodeB (GNB) versions and data from respective one or more GNBs, wherein each of the plurality of provisioning requests includes one or more policies specific to a respective new GNB version;
a conductor (210) configured to provision, based on the received provisioning requests, the one or more policies;
a decoder (212) configured to decode the data received from the one or more GNBs related to the respective new GNB version according to the provisioned one or more policies;
a normalizer (214) configured to enrich the decoded data using the provisioned one or more policies and a rules metadata; and
a database (206) configured to for store the enriched data.

8. The system (108) of claim 7, wherein the User Interface (UI) (208) is configured to enable a user to configure at least one of: the new GNB version and definition of the one or more policies and the rule metadata for each new GNB version.

9. The system (108) of claim 7, wherein the conductor (210) is further configured to handle the decoding of data pertaining to the new GNB version received from the one or more GNBs based on the configured one or more policies.

10. The system (108) of claim 7, the system (108) further comprises a message broker (216) configured to facilitate bidirectional communication between the conductor (210) and the normalizer (214) for provisioning the one or more policies to decode the data received from the one or more GNBs, wherein at least one of: the conductor (210) is further configured to handle the decoding of data received from the one or more GNBs version based on the configured one or more policies, and the normalizer (214) is configured to perform data enrichment by applying the defined one or more policies and the rule metadata

11. The system (108) of claim 7, the system (108) is further configured to enable the real-time creation of the one or more policies and the rule-metadata for different versions.

12. The system (108) of claim 7, wherein each of the multiple GNB versions is supported by its own application slice for independent data processing.