System and method for managing an upgradation of a node of a network

Abstract

The present invention provides a method (500) for managing an upgradation of a node of a network (106). Initially, at least one workorder associated with the upgradation of the node is received. Further, at least one node corresponding to a node type of the network is identified from the at least one received workorder. The at least one identified node is validated based on predetermined criteria. Finally, at least one request is transmitted to a node management unit upon validation of the at least one identified node. The at least one request includes one or more execution instructions for managing the upgradation of the at least one validated node of the network (106).

Description

SYSTEM AND METHOD FOR MANAGING AN DEGRADATION OF A NODE OF A NETWORKRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The present disclosure relates generally to the field of wireless communication network. More particularly, the present disclosure relates to a system and method for managing an upgradation of a node of a network.DEFINITION

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] ‘Workorder” refers to a structured digital request or instruction set created by a network operator or system to perform a software package upgrade on a specific network node or group of nodes. The workorder serves as a task management entity that contains all the necessary details required for executing the upgrade efficiently.

[0005] ‘Radio Access Network (RAN)” refer to a part of a telecommunication network that connects user devices such as smartphones, tablets, and Internet of Things(loT) devices to the core network via wireless communication. The RAN is responsible for managing radio signals, facilitating mobile connectivity, and ensuring seamless communication between users and network services.

[0006] Software package” refer to a collection of software files, programs, or updates that are bundled together for installation, upgrade, or deployment on a network node or system. The software package may include firmware update, network function software, bug fixes etc.

[0007] ‘Macro node” refer to a large-scale base station in a mobile network that provides wide-area coverage and supports a high number of simultaneous connections. The macro nodes are typically part of the Radio Access Network (RAN) and are used in macrocell deployments, covering several kilometers in urban, suburban, and rural areas.

[0008] ‘Indoor Small Cell (ISC) node” refers to a low-power cellular base station designed to enhance mobile network coverage and capacity in indoor environments such as offices, shopping malls, airports, stadiums, and residential buildings. The ISC nodes are part of the RAN and are used in 5G, Long Term Evolution (LTE), and other wireless networks to improve connectivity in areas where macro cell signals are weak or congested.

[0009] ‘Non-Service Affecting (NSA) activity” refers to an operation or upgrade that does not impact the service being provided to users. The NSA upgrade may be performed without causing downtime or service interruptions for end users.

[0010] Service Affecting (SA) activity” refers to an operation or process that impacts the functionality of the network or services, potentially causing disruptions or downtime for users. The SA activity may include certain software package upgrades or maintenance tasks that may temporarily interrupt service.BACKGROUND

[0011] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0012] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, fifth generation (5G) technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devices simultaneously. Further, Sixth Generation (6G) successor to 5G is expected to provide significantly high data speed with reduced latency, which may offer improved connectivity for a vast number of devices concurrently. The 6G technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way of connecting and interacting with technology.

[0013] As the wireless technologies are advancing, there is a need to cope up with the 5G requirements and delivering a high level of service to the customers. In a high scale radio access network (RAN) includes multiple antennas, multiple radio units, and multiple RAN nodes. The multiple RAN node includes various baseband units, andsoftware interfaces required to provide telecommunication services to the customers / users of the RAN. Further, the RAN node software includes multiple network functions for handling data transmission, quality of service, signal handover, and management and orchestration. The RAN node software needs to be upgraded regularly to fix problems related to failures and to introduce new functionality in the telecommunication network. The high-scale RAN includes a multiple-element management system (EMS) installed to perform day-to-day RAN node updating and tracking operations. However, different RAN nodes in an EMS require different / separate user interfaces (UIs) for updating and tracking. As a result, with existing solutions, it is difficult to perform the upgradation and tracking of different types of RAN node software at the same time with the same element management system (EMS).

[0014] Thus, there is a need for an improved system and a method that overcomes the limitations of the prior arts and efficiently performs the updating and tracking of the different types of RAN nodes present in the network.SUMMARY OF THE DISCLOSURE

[0015] In an exemplary embodiment, a method for managing an upgradation of a node of a network is described. The method includes receiving at least one workorder associated with the upgradation of the node of the network. The method further includes identifying at least one node corresponding to a node type of the network from the at least one received workorder. The method further includes validating the at least one identified node based on predetermined criteria. Further, the method includes transmitting at least one request to a node management unit upon validation of the at least one identified node. The at least one request includes one or more execution instructions for managing the upgradation of the at least one validated node of the network.

[0016] In an embodiment, the at least one node of the network comprises a Radio Access Network (RAN) node.

[0017] In another embodiment, the at least one workorder includes at least one of the node type of the network, one or more details associated with the at least one node, at least one execution type associated with the upgradation of the node n and workorder execution scheduling information.

[0018] In another embodiment, the at least one execution type comprises at least one of a pre-check execution, an alarm check execution, a software download execution, a software package upgrade execution and a post-check execution.

[0019] In another embodiment, the one or more execution instructions are based on the at least one received workorder.

[0020] In another embodiment, the node type of the network includes at least one of a macro node type and an indoor small cell (ISC) node type.

[0021] In another embodiment, the method further includes generating a report of at least one invalid node of the network.

[0022] In another embodiment, the method further includes receiving a response indicating at least one execution status of the at least one validated node from the node management unit.

[0023] In another exemplary embodiment, a system for managing an upgradation of a node of a network is described. The system includes a receiving unit configured to receive at least one workorder associated with the upgradation of the node of the network and a processing unit communicatively coupled to the receiving unit. The processing unit is configured to receive the at least one workorder from the receiving unit. Further, the processing unit includes a node identification module configured toidentify at least one node corresponding to a node type of the network from the at least one received workorder. The processing unit further includes a validation module configured to validate the at least one identified node based on predetermined criteria. Further, the processing unit further includes a request transmission module configured to transmit at least one request to a node management unit upon validation of the at least one identified node. The at least one request includes one or more execution instructions for managing the upgradation of the at least one validated node of the network.

[0024] In another embodiment, a UE is described. The UE is communicatively coupled to a network, the coupling comprises steps of receiving, by the network, a connection request from the UE. The coupling comprises sending, by the network, an acknowledgment of the connection request to the UE. Further, the coupling comprises transmitting a plurality of signals in response to the connection request. The upgradation of a node of the network is managed by a method including steps of receiving at least one workorder associated with the upgradation of the node of the network. Further, the method includes identifying at least one node corresponding to a node type of the network from the at least one received workorder. Further, the method includes validating the at least one identified node based on predetermined criteria. The method further includes transmitting at least one request to a node management unit upon validation of the at least one identified node. The at least one request includes one or more execution instructions for managing the upgradation of the at least one validated node of the network.

[0025] In an embodiment, a computer program product including a non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing an upgradation of a node of a network is described. The method includes steps of receiving at least one workorder associated with the upgradation of the node of the network.Further, the method includes identifying at least one node corresponding to a node type of the network from the at least one received workorder. The method further includes validating the at least one identified node based on predetermined criteria. Further, the method includes transmitting at least one request to a node management unit upon validation of the at least one identified node. The at least one request includes one or more execution instructions for managing the upgradation of the at least one validated node of the network.

[0026] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.OBJECTIVES OF THE PRESENT DISCLOSURE

[0027] Some of the objective of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0028] An objective of the present disclosure is to provide a system and method for upgrading the software of Radio Access Network (RAN) node(s) by using a single user interface (UI).

[0029] Another objective of the present disclosure is to provide a system and a method that allows a user to select a type of node whose software needs to be upgraded through a single UI.

[0030] Another objective of the present disclosure is to provide a system and a method that allows a user to use a single UI to submit a request for creating a workorder of the node.

[0031] Another objective of the present disclosure is to provide a system and a method that allows a user to track the execution status and workorder status of different types of nodes through a single UI.

[0032] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0033] 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.

[0034] FIG. 1 illustrates an exemplary network architecture of a system for managing an upgradation of a node of a network, in accordance with embodiments of the present disclosure.

[0035] FIG. 2 illustrates an example block diagram of the system for managing the upgradation of the node of the network, in accordance with an embodiment of the present disclosure.

[0036] FIG. 3 illustrates an exemplary system architecture of the system for managing the upgradation of the node of the network, in accordance with an embodiment of the present disclosure.

[0037] FIG. 4 illustrates an example flowchart of a method for managing the upgradation of the node of the network, in accordance with an embodiment of the present disclosure.

[0038] FIG. 5 illustrates another example flowchart of the method for managing the upgradation of the node of the network, in accordance with an embodiment of the present disclosure.

[0039] FIG. 6 illustrates an exemplary computer system in which or with which embodiments of the present disclosure may be implemented.

[0040] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - User(s)104 -User Equipments (UEs)106 - Network108 - System200 - Block diagram202 - Processor(s)204 - Memory206 -Interface(s)208 - Processing unit210 - Database212 - Receiving unit214 - Node identification module216 - Validation module 218 - Request transmission module220 - Node management unit222 - Report generation module224 - Output module300 - System Architecture 302 - A plurality of user equipments (UEs)304 - Shared Load Balancer (LB)306 - Network Management Platform308 - A plurality of web servers310 - A plurality of application programming interface (API) gateway servers 312 - W orkorder Engine314 - A plurality of Micro services316 - Database318 - Dashboard320 - Service(s) schedulers322 - Service(s) execution engine324 - Service(s) monitoring and status update engine326 - Elastic load balancer (ELB)328 - Element management system (EMS)400 - Flowchart500 - Flowchart600 - A computer system610 - External storage device620 - Bus630 - Main memory640 - Read only memory650 - Mass storage device660 - Communication port(s)670 - ProcessorDETAILED DESCRIPTION

[0041] In the following description, for the purposes of explanation, various specific details are set forth to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the 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 discussedabove or might address only some of the problems discussed above. Some of the problems discussed above might not be 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.

[0042] 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 arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0043] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0044] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine,a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0045] 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 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 like the term “comprising” as an open transition word without precluding any additional or other elements.

[0046] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0047] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements,components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for 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 or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein. It should be noted that the terms “graphical user interface” and “user interface” are used interchangeably for the purpose of describing the invention. Also, the terms “software” and “firmware” are used interchangeably for the purpose of describing the invention.

[0048] 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 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 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, 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.

[0049] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0050] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data 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), and more such generations are expected to continue in the forthcoming time.

[0051] 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 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 (Universal Mobile Telecommunications System), LIE (Long-Term Evolution), and 5G. The choice ofRAT depends on a variety of factors, including the network infrastructure, the available spectrum, and the mobile device' s / 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 resources.

[0052] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0053] With the rapid expansion of Fifth Generation (5G) networks, maintaining and upgrading software across network nodes has become a critical aspect of network management. Telecom operators frequently perform software upgrades on network infrastructure such as macro base stations, small cells, and other Radio Access Network (RAN) elements to ensure optimal performance, security, and feature enhancements. However, executing large-scale software package upgrades requires a structured, automated, and efficient process to minimize service disruptions and operational complexities.

[0054] Conventionally, software upgrades in telecom networks are complex and fragmented, requiring manual interventions and multiple tracking interfaces for different node types. Network operators face challenges in identifying eligible nodes, ensuring software compatibility, and managing upgrades without affecting live network performance. Additionally, failures during upgrades due to insufficient resources, network congestion, or alarm conditions result in service disruptions and extensive troubleshooting efforts. The conventional solutions lack a centralized,Y1 automated, and intelligent system that can handle workorder-based upgrades, node validation, execution tracking, and error reporting efficiently.

[0055] Currently, the element management system (EMS) manages, and monitors RAN nodes or cells within a telecommunications network. For example, the RAN nodes may include nodes like a macro node or indoor small cell (ISC). The macro node may be a base station, eNodeB, gNodeB (in 5G networks), or any other component responsible for providing wireless coverage over a wider / broad area. Similarly, the ISC may be a small cellular base station (e.g., femtocells, picocells, etc.) designed for indoors to enhance wireless coverage and capacity in areas with high user density or poor indoor signals. In the current EMS, if the user wants to perform RAN node software package upgrade for the ISC and macro node, he / she need to use different / separate User Interfaces (UIs) and tracking system(s).

[0056] Conventional methods for software package upgrades in telecom networks involve manual workorder management, separate upgrade interfaces for different node types, and isolated tracking systems. Some conventional solutions may use basic automation scripts, but lack real-time validation, error handling, and rollback mechanisms. In many cases, operators must manually check node compatibility, resource availability, and execution status, leading to delays, inefficiencies, and operational overhead. Additionally, conventional systems often fail to provide comprehensive error reports, making it difficult for network engineers to troubleshoot upgrade failures effectively.

[0057] Thus, there is a need for an improved system and a method that overcomes the limitations of the prior arts and efficiently provides a single UI solution for upgrading and tracking the execution status of different types of RAN nodes.

[0058] The present disclosure discloses a workorder-based software upgrade system introducing a centralized and automated approach to manage upgrades acrossvarious network nodes. The present disclosure includes modules for workorder creation, node identification, validation, execution management, and error reporting. Upon receiving a workorder, the present disclosure identifies the relevant nodes, validates them based on predetermined criteria, and initiates the upgrade process through the node management unit. Real-time execution tracking ensures seamless monitoring, while a reporting module logs errors and provides corrective recommendations. By automating the entire software upgrade lifecycle, the present disclosure significantly reduces manual effort, enhances network reliability, and minimizes downtime, making it an essential tool for modern 5G network operations.

[0059] In one aspect, the present disclosure provides an improved system and a method for upgrading the software of multiple RAN nodes using a single UI.

[0060] In an aspect, the present disclosure provides an improved system and a method that uses the single UI for upgrading the software of the multiple RAN nodes that makes the user’s work easy and fast.

[0061] In an aspect, the present disclosure provides an improved system and a method for upgrading the software of multiple RAN nodes that reduces the time for upgrading the software with minimal or no human intervention.

[0062] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0063] FIG. 1 illustrates an exemplary network architecture (100) of a system for managing the upgradation of the node of the network (106), in accordance with embodiments of the present disclosure. As illustrated in FIG. 1, the network architecture (100) may include one or more User Equipments (UEs) (104-1, 104- 2... 104-N) associated with one or more users (102-1, 102-2... 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102-N) may be collectively referred to as the users (102).Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2... 104-N) may be collectively referred to as the UE (104) or the UEs (104). Although only three UE (104) are depicted in FIG. 1, however, any number of the UE (104) may be included without departing from the scope of the ongoing description.

[0064] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, loT system. In such an embodiment, the UE (104) may include, but are not limited to, smartphones, smart watches, smart sensors (e.g., a mechanical, a thermal, an electrical, a magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, a smart television (TV), computers, a smart security system, a smart home system, other devices for monitoring or interacting with or for the users 102 and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but not limited to, intelligent, multi-sensing, network-connected devices, that may integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0065] Additionally, in some embodiments, the UE (104) may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE 104 may include, but are not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality(VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or an entity such as a touchpad, a touch-enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0066] In FIG. 1, the UE (104) may communicate with the system (108) through the network (106) for sending or receiving various types of data. In an embodiment, the network (106) may include at least one of a 5th Generation (5G) network, a 6th Generation (6G) network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network 106 may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0067] In an embodiment, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The 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, the PSTN, a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0068] In an embodiment, the UE (104) is communicatively coupled with the network (106). The network (106) may receive a connection request from the UE (104). The network (106) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request.

[0069] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).

[0070] FIG. 2 illustrates an example block diagram (200) of the system (108) for managing the upgradation of the node of the network (106), in accordance with an embodiment of the present disclosure.

[0071] In an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be 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 create or share datapackets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

[0072] In an embodiment, the system (108) may include an interface(s) (206). The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices (I / O), storage devices, and the like. The interface(s) (206) may facilitate communication through the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, a processing unit (208) and a database (210).

[0073] In an embodiment, the system (108) may include a processing unit (208) that may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing unit (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing unit (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing unit (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine- readable storage medium may store instructions that, when executed by the processing resource, implement the processing unit (208). In such examples, the system (108) may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing unit (208) may be implemented by electronic circuitry.

[0074] In an embodiment, the block diagram (200) may include a receiving unit (212) configured to receive at least one workorder associated with the upgradation of the node of the network (106). The at least one workorder includes at least one of the node types of the network, one or more details associated with the at least one node, at least one execution type associated with the upgradation of node of the network and workorder execution scheduling information. In an embodiment, the at least one workorder may be created by a user on a User Interface (UI). The workorder may be a structured digital request or instruction set created by a network operator or the user (102) to perform an upgrade on a specific network node or group of nodes. The workorder serves as a task management entity that contains all the necessary details required for executing the upgrade efficiently. The UI may be a centralized software interface that allows users to initiate, manage, and track upgrades for different types of network nodes, including Indoor Small Cells (ISC) and Macro Nodes. This UI simplifies the workorder creation process by enabling users to select node types, schedule upgrades, and monitor execution status from a single platform instead of using multiple tracking systems. In an embodiment, the at least one workorder may be created automatically based on the upgradation requirements of the node by a triggering module. The triggering module may communicate with the system (108) and the processing unit (208) to automatically initiate the software package upgrade of the node. The triggering module may be implemented at a local server or at a remote server. The triggering module may communicate with the system (108) via communication channel such as HyperText Transfer Protocol (HTTP). The triggering module may transmit a command to initiate the upgradation of the network. The command may be conditioned to trigger automatically or sent manually by the user (102). The command may include information for all possible interactions inbuilt and may be parsed to perform the interaction with the the system (108) and the processing unit (208). The command may include the at least one workorder created by the triggering module.

[0075] In some embodiments, the node type may be a specific type of network infrastructure that requires the software upgrade such as Macro nodes, Indoor Small Cells (ISC), gNB, etc. Further, the one or more details associated with the Node may include details about the node to ensure that the correct network elements are targeted for the upgrade such as node identifier, current software version, hardware specifications, location and status of network. The at least one execution type associated with the upgradation of the node may define the specific steps and procedures involved in performing the software upgrade. Further, the workorder execution scheduling information allows the user to define when the upgrade should take place, ensuring minimal service disruption. The execution scheduling information may include immediate execution, scheduled execution, Non-service Affecting (NSA) activity, Service Affecting (SA) activity.

[0076] Further, the at least one execution type associated with the upgradation of the node includes at least one of a pre- check execution, an alarm check execution, a software download execution, an upgrade execution and a post-check execution. The pre-check execution may be a validation process before initiating the upgrade to confirm that the node is ready. Further, the alarm check execution may scan the node for active alarms or issues that could impact the upgrade. The software download execution ensures that the correct software package is downloaded and available for installation. Further, the software package upgrade execution is the actual installation of the new software on the node. The post-check execution may be a final verification step to confirm the upgrade was successful and that the node is operating correctly. The at least one workorder facilitate software package upgrades for different types of network nodes, ensuring efficient execution and tracking of upgrade processes across the network. The workorder may also include technical specifications of the selected node(s), such as node identifiers, software version compatibility, current network status.

[0077] In an embodiment, the block diagram (200) may include a processing unit (208) communicatively coupled to the receiving unit (212). The processing unit (208) is configured to receive the at least one workorder from the receiving unit (212). The processing unit (208) further include a node identifier module configured to identify at least one node corresponding to a node type of the network from the at least one received workorder. Once a workorder is created by a user via the UI and received by the receiving unit (212), the processing unit (208) processes the request to ensure accurate execution based on the specified node type. The node identifier module may scan the at least one workorder and determines the specific node that match the node type defined in the request. The node typed defined in the request may include a Macro node, ISC node, gNB, etc. The node identifier module may extract parameters such as node type, node identifier, network location and associated parameters to identify the at least one node.

[0078] The processing unit (208) may further include a validation module configured to validate the at least one identified node based on predetermined criteria. The predetermined criteria may include a software compatibility check, hardware compatibility check, network connectivity validation, etc. After the node identifier module selects the at least one node for the software upgrade, the validation module checks whether the identified node is eligible for software upgrading. The verification of the at least one identified node is based on predefined criteria that ensure the at least one node is in a stable and operational state before the upgrade is initiated. The validation module may assess the node based on multiple criteria such as current software version, network connectivity, alarm status, resource availability, and node type compatibility. In some embodiment, the validation module may perform an automated pre-check execution to simulate or test the upgrade process without applying changes. If any issues are detected, the validation module generates a validation report, highlighting the reasons why a node fails validation.

[0079] Further, the processing unit (208) may include a request transmission module configured to transmit at least one request to a node management unit upon validation of the at least one identified node. The at least one request includes one or more execution instructions for managing the upgradation of the at least one validated node of the network. The one or more execution instructions are based on the at least one received workorder. Once the validation module confirms that the at least one identified node meets all upgrade criteria such as software compatibility, network availability, and resource sufficiency, the request transmission module generates and sends an upgrade request to the node management unit. The request transmission module may prepare a structured request containing execution instructions tailored for the specific node and its upgrade requirements. Further, the execution instruction may include pre-check execution commands, alarm check instructions, software download instructions, software installation and upgrade commands, and post-check execution. Further, the node management unit may be a centralized control system responsible for handling software upgrades across multiple network nodes. Upon receiving the request from the request transmission module, the node management unit executes the instructions, accordingly, ensuring a seamless upgrade process.

[0080] In an embodiment, the processing unit (208) further includes a report generation module configured to generate a report of at least one invalid node of the network. Before executing a software package upgrade, the validation module checks whether the selected node meets predetermined criteria. If a node fails validation, the at least one node is categorized as an invalid node, meaning the node may not proceed with the upgrade at that time. Further, the report generation module creates a detailed error report for each invalid node, specifying node identifier, reason of failure, timestamp, suggested resolution, etc. The generated reports are stored in the database (210) and may be accessed by network administrators or the node management unit for further analysis. The reports may be integrated into network monitoring dashboards for real-time visibility into upgrade failures.

[0081] In an embodiment, the processing unit (208) further include an output module configured to receive a response indicating at least one execution status of the at least one validated node from the node management unit. Once the request transmission module sends the upgrade request and execution instructions to the node management unit, the output module is responsible for capturing real-time status updates about the upgrade process. The node management unit may execute the software upgrade on the validated node and continuously reports back the progress to the output module. The output module may receive different types of execution status responses such as in progress, Successful execution, Failure / Error detected, pending execution, and Rollback initiated. Further, the output module logs the received execution status updates in the database (210) or monitoring system, ensuring that network administrators can track progress in real-time. The execution status may be mapped to the original workorder, ensuring transparency and traceability in the upgrade process. Further, the execution status updates received by the output module may be displayed in the UI, allowing network operators to monitor the real-time status of software upgrades across multiple nodes.

[0082] In an embodiment, the database (210) includes data (e.g., timestamp, network location, node identifier, cell ID, network data, session data, predefined criteria, user preferences, and the like associated with the node) that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the processing unit (208).

[0083] FIG. 3 illustrates an example system architecture (300) of the system (108) for managing the upgradation of the node of the network (106), in accordance with an embodiment of the present disclosure.

[0084] In an aspect, the present disclosure may allow one or more user equipments (302) to display the single UI for selecting a node type (e.g., Macro node, ISC node, etc.). A user may interact with the single UI to create work orders specifying the nodetype, execution type (pre-check, software upgrade, post-check, etc.), and scheduling details. In an aspect, once the user selects a specific node, a request is sent to a network management platform (306) via a shared load balancer (LB) (304). The Shared Load Balancer (304) distributes incoming workorders efficiently to prevent system overload. The network management platform (306) includes a plurality of components, e.g., web servers (308), application programming interface (API) gateway servers (310), a workorder engine (312), micro services (314), a database (316) which may include an elastic search (ES) engine, a dashboard (318), service(s) schedulers (320), service(s) execution engine (322), service(s) monitoring and status update engine (324), and an elastic load balancer (ELB) (326). In an aspect, the web servers (308) and API gateway servers (310) may be configured by using a firewall. The Web Servers (308) and API Gateway Servers (310) enable secure communication between the UI and backend processing components. Further, the work order engine (312) may process the received workorder. The Microservices Layer (314) manages different aspects of the upgrade. Further, the database (316) stores all work orders and system logs. The schedulers (320) determine when and how the upgrades may be executed. The execution engine (222) performs the actual upgrade tasks. Further, the Monitoring and Status Update Engine (324) continuously tracks progress and updates the system 9300). The system architecture (300) may include one or more element management systems (EMS) (328) such as EMS1, EMS2, EMS3, etc. One or more ELBs (326) may send at least one request to gather information from one or more EMS (328). In an aspect, the one or more EMS (328) may send at least one response back to the ELB (326).

[0085] In an aspect, the network management platform (306) and / or the element management system (EMS) (328) may perform a backend logic. For example, once the user selects the node type in the UI, a particular backend logic may be assigned automatically for the selected node, and execution method of procedure (MOP) may be executed for an upgradation of workorder. In an aspect, the MOP is a step-by-step sequence for completing a certain task / operation (e.g., software upgradetask / operation). The most high-level purpose of a MOP is to control every step of an operation to ensure a desired outcome, minimize the guesswork, and avoid human errors.

[0086] In an aspect, the MOP may be stored in the database (316). In an aspect, based on the node selected by the user, micro services (314) may access the MOP for execution. In an aspect, a pre-check activity may get performed before the software upgradation of the selected node. The service(s) monitoring and status update engine (324) is configured to monitor the services including software upgradation of a selected node, executed by the service(s) execution engine (322) and gather key performance indicators from the services. In addition, based on the gathered key performance indicators, the service(s) monitoring and status update engine (324) provides status of the services and software upgrade.

[0087] In an embodiment, the EMS (328) manages the actual network nodes. The EMS (328) may send instructions for software upgrades. Further, the EMS (328) acknowledges and processes the request associated with processing the workorder. Further, the software upgrade may be executed on the identified nodes based on the request. Finally, the system architecture (300) may retrieve the latest status of nodes post-upgrade.

[0088] In an aspect, all the updates or statuses related to software upgrade may be displayed on the UI. For example, the UI may display a summary related to updates made during software upgradation for history purposes.

[0089] In an aspect, the updates or statuses related to software upgradation of the node(s) may also be displayed in a real-time on the dashboard (318).

[0090] In an aspect, all the status updates related to software upgrade success events or fail events may be displayed on the dashboard (318). In an aspect, the dashboard (318) may also show the currently running workorder details.

[0091] In an aspect, the ELB (326) may send at least one software upgradation request to the one or more EMS (328). In an aspect, the one or more EMS (328) may send a get node status to the ELB (326).

[0092] In an aspect, the workorder engine (312) may coordinate with the EMS (328), by using the micro services (314), to create the workorder for the node type selected by the user. In an aspect, the service(s) schedulers (320) and / or service(s) execution engine (322) may allow the user to schedule the software upgrade activity / operations as desired. In an aspect, the schedule for the software upgrade activity / operations may be customized as per the user’s requirements.

[0093] In an aspect, the service(s) schedulers (320) may trigger / invoke the service(s) execution engine (322) to start the software upgrade activity at the scheduled date and / or time. The service(s) schedulers (320) may be initiated automatically or by the UE (302) based on the execution instructions.

[0094] FIG. 4 illustrates an example flowchart (400) of a method for managing the upgradation of the node of the network (106), in accordance with an embodiment of the present disclosure. FIG. 4 with reference to the FIGs. 1, 2 and 3, illustrates the method (400) for managing the upgradation of the node by using the processing unit (208) of the system (108).

[0095] In an aspect, the present disclosure enables the UI to display an option to the user for selecting a node type (e.g., macro node, ISC node, etc.).

[0096] In an aspect, at step (402), once the user selects a specific node type, the present disclosure creates a workorder to upgrade the software package for the selected node type. In an aspect, the workorder may include all the details required to upgrade the software package for the node. For example, the workorder may include software name, version number of current software and version to be updated to, date and / ortime the workorder was created, detailed description of what the update entails including any specific features to be addressed, schedule plan, etc.

[0097] In one aspect, during software package workorder creation, a node list may be verified based on the user-selected node type, and the associated validation and execution steps may be assigned to the user for the selected node type.

[0098] In an aspect, for example, once the workorder is created at step (402), the present disclosure submits the created workorder at step (404) for further validation at step (406).

[0099] In an aspect, for example, if the user wants to create a software package upgrade workorder for a macro node, he / she needs to select the macro node type in the workorder creation form available on the UI.

[0100] In another aspect, for example, if the user wants to create a software package upgrade workorder for an ISC, he / she needs to select the ISC node type in the workorder creation form available on the UI.

[0101] In an aspect, at step (406), the present disclosure may perform a pre-check activity for the received workorder with respect to the configuration(s) of the selected node type. The pre-check execution activity at step (406) may result in either fail (408) or success (410).

[0102] In an aspect, if the pre-check execution activity succeeds, the present disclosure may perform an alarm-check execution at step (412) to see if there are any errors, which may further result in either fail (414) or success (416).

[0103] In an aspect, at step (416), if the alarm-check execution activity succeeds, the present disclosure may perform downloading the software / firmware package forthe selected node at step (418). In an aspect, the downloading of software / firmware package may result in either fail (420) or success (422).

[0104] In an aspect, at step (422), if software / firmware package download activity succeeds, the present disclosure may start performing the software upgradation of the selected node at step (424).

[0105] In an aspect, at step (424), the software upgrade activity may result in either fail (426) or success (428).

[0106] In an aspect, at step (428), if software upgrade activity succeeds, the present disclosure may perform additional post-check execution activity at step (430). In an aspect, for example, the present disclosure may send a request to the upgraded software of the node to execute a set of predefined commands and compare the response(s) with the predetermined criteria. Based on the comparison, at step (430), the post-check execution activity may result in either failure (432) or success (434).

[0107] In an aspect, after fail results at steps (408), (414), (420), (426), and (432) no further activity check may get performed by the present disclosure.

[0108] In an aspect, activity steps (406), (412), and (418) may be described as nonservice affecting (NS A) steps as these steps do not materially affect the performance or quality of a service. In an aspect, activity steps (424) and (430) may be described as service-affecting activity steps as these steps may affect the performance or quality of the service.

[0109] In an aspect, activity steps (406), (412), and (418) may be scheduled as per the user-defined schedule. For example, the user can select a specific time and / or a day through the single UI for performing the activity steps (406), (412), and (418).

[0110] FIG. 5 illustrates a flowchart of a method (500) for managing the upgradation of the node of the network (106), in accordance with an embodiment of the present disclosure. FIG. 5 with reference to the FIGs. 1, 2, 3 and 4, illustrates the method (500) for managing the upgradation of the node by using the node identification module (214), the validation module (216), the request transmission module (218), the node management unit (220), the report generation module (222), and the output module (224) of the processing unit (208) of the system (108). .

[0111] The method (500), at step (502) may include receiving at least one workorder associated with the upgradation of the node of the network. The at least one workorder includes at least one of the node types of the network, one or more details associated with the at least one node, at least one execution type associated with the upgradation of the node and workorder execution scheduling information. The at least one execution type includes at least one of a pre-check execution, an alarm check execution, a software download execution, a software package upgrade execution and a post-check execution. The at least one workorder serves as an instruction set for executing an upgradation of a specific network node type. The workorder specifies the type of network node that requires the software upgrade such as / Macro node, ISC node, gNB. The workorder scheduling allow users to specify when the upgrade should take place. The networking scheduling may be configured on Non-Service Affecting (NSA) Mode ensuring that upgrades do not disrupt active network services and Service Affecting (SA) Mode allowing upgrades that may temporarily impact services but are necessary for major updates.

[0112] The method (500), at step (504) may include identifying at least one node corresponding to a node type of the network from the at least one received workorder. The at least one node of the network comprises a Radio Access Network (RAN) node. The method (500) may include scanning the network database or management system to locate actual nodes that match the specified node type. The nodes are identified basedon the node identifier, location and coverage area, current software version, operational status, etc. Further, the method (500) may check whether the identified node(s) are available and eligible for software upgrade.

[0113] The method (500), at step (506) may include validating the at least one identified node based on predetermined criteria. The validation ensures that the node is in a stable condition and meets all predetermined criteria required for a successful upgrade.

[0114] The method (500), at step (508) may include transmitting at least one request to a node management unit upon validation of the at least one identified node. The at least one request may include one or more execution instructions for managing the upgradation of the at least one validated node of the network. The one or more execution instructions are based on the at least one received workorder. The one or more execution instructions specify the upgrade process, including pre-check execution, software download, installation, and post-upgrade verification. The method (500) includes processing the instructions, coordinating the actual upgrade on the validated node. By automating the transmission of upgrade commands, this method (500) ensures seamless execution, minimizes manual intervention, and reduces the risk of errors, thereby enhancing the efficiency and reliability of software upgrades in the network.

[0115] The method (500) may include generating a report of at least one invalid node of the network. The generated report may provide detailed insights into why a node may be deemed ineligible for the upgrade, including reasons such as software incompatibility, insufficient resources, active alarms, or network connectivity issues. The method (500) may also include logging the node’s identifier, failure timestamp, and suggested corrective actions, ensuring that network administrators may troubleshoot and resolve the issues efficiently. The report may be stored in a centralized database or presented via a User Interface (UI) for monitoring and future reference.

[0116] Further, the method (500) may include receiving a response indicating at least one execution status of the at least one validated node from the node management unit. The response may provide real-time updates on whether the upgrade is in progress, successfully completed, failed, or requires rollback. If the upgrade is successful, the method (500) logs the completion status, if it fails, the response includes error details and possible corrective actions. The execution status is stored for reporting, monitoring, and troubleshooting purposes, ensuring that network administrators have full visibility into the upgrade process. By tracking execution status, the method (500) enables efficient network management, quick issue resolution, and optimized software deployment across multiple nodes.

[0117] In an exemplary, in a large-scale 5G telecom network, operators frequently perform software upgrades on thousands of base stations (gNBs and eNBs) to enhance performance, security, and compatibility with new features. Consider a scenario where a mobile network operator (MNO) plans to upgrade the software of macro and small cell base stations across a metropolitan area. The operator initiates a workorder through a centralized user interface, specifying the node types, execution schedule, and upgrade steps. The system then identifies the relevant base stations, validates their compatibility, and checks for any active alarms or resource limitations.

[0118] Once the nodes pass validation, upgrade requests are sent to the node management unit, which executes the software installation. The system monitors progress in real-time, receiving execution status updates such as successful completion, in-progress, or failure notifications. If certain nodes fail validation due to low memory or active faults, an error report is generated, allowing engineers to troubleshoot and reattempt the upgrade later. This automated process ensures that network stability is maintained, reducing manual intervention, minimizing service disruptions, and enhancing overall connectivity for mobile users. Through this system, telecomoperators can efficiently manage large-scale software upgrades, ensuring a seamless user experience.

[0119] In another embodiment, a UE is described. The UE is communicatively coupled to a network, the coupling comprises steps of receiving, by the network, a connection request from the UE. The coupling comprises sending, by the network, an acknowledgment of the connection request to the UE. Further, the coupling comprises transmitting a plurality of signals in response to the connection request. The upgradation of network node is managed by a method including steps of receiving at least one workorder associated with the upgradation of the node. Further, the method includes identifying at least one node corresponding to a node type of the network from the at least one received workorder. Further, the method includes validating the at least one identified node based on predetermined criteria. The method further includes transmitting at least one request to a node management unit upon validation of the at least one identified node. The at least one request includes one or more execution instructions for managing the upgradation of the at least one validated node of the network.

[0120] In an embodiment, a computer program product including a non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing the upgradation of the network node is described. The method includes steps of receiving at least one workorder associated with the upgradation of the node. Further, the method includes identifying at least one node corresponding to a node type of the network from the at least one received workorder. The method further includes validating the at least one identified node based on predetermined criteria. Further, the method includes transmitting at least one request to a node management unit upon validation of the at least one identified node. The at least one request includes one or more executioninstructions for managing the upgradation of the at least one validated node of the network.

[0121] The present disclosure provides several technical advantages in managing upgrades for different types of Radio Access Network (RAN) nodes, including Indoor Small Cell (ISC) and Macro nodes. The present disclosure introduces a unified user interface (UI) that enables users to raise a software package upgrade workorder for different node types through a single UI. The UI not only simplifies the initiation process but also ensures that users can track execution and work order status seamlessly across multiple node types. One of the key advantages of the present disclosure is the automated assignment of validation and execution steps based on the selected node type. When a user selects a Macro or ISC node for an upgrade, the present disclosure dynamically assigns the relevant nodes and execution procedures, reducing manual errors and ensuring consistency. Furthermore, the present disclosure integrates with a centralized Element Management System (EMS), which streamlines communication between different network elements, thereby improving operational efficiency. The ability to handle both Service Affecting (SA) and Non-Service Affecting (NSA) upgrades ensures network reliability and minimizes downtime. Overall, the invention enhances scalability, reduces manual effort, and significantly improves the speed and accuracy of upgrades of the node.

[0122] FIG. 6 illustrates an exemplary computer system (600) in which or with which embodiments of the present disclosure may be implemented. The computer system (600) may include an external storage device (610), a bus (620), a main memory (630), a read-only memory (640), a mass storage device (650), a communication port(s) (660), and a processor (670). A person skilled in the art will appreciate that the computer system (600) may include more than one processor and communication ports. The processor (670) may include various modules associated with embodiments of the present disclosure. The communication port(s) (660) may be any of an RS -232 port foruse with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (660) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (600) connects.

[0123] In some embodiments, the main memory (630) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (640) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input / output system (BIOS) instructions for the processor (670). The mass storage device (650) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Lirewire interfaces).

[0124] In some embodiments, the bus (620) may communicatively couple the processor(s) (670) with the other memory, storage, and communication blocks. The bus (620) may be, e.g., a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB, or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (670) to the computer system (600).

[0125] In another embodiment, operator, and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus (620) to support direct operator interaction with the computer system (600). Other operator and administrative interfaces can be provided through network connections connectedthrough the communication port(s) (660). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (600) limit the scope of the present disclosure.

[0126] Thus, the present disclosure raise software package upgrade workorder through single user interface and track execution status and workorder status for different node type. In an aspect, during software package workorder creation user may select node type and based on that associated node type validation and execution steps may be assigned to that workorder. The present disclosure may create workorder automatically in case the node needs to be upgraded with the software package. Further, in an example, if user wants to create software package upgrade workorder for MACRO node, then the present disclosure may select MACRO node type form workorder creation UI and based on that MACRO Nodes may be available for software package upgrade. In another example, if the user wants to create a software package upgrade workorder for Indoor small cell (ISC) node, then the present disclosure may select ISC node type form workorder creation UI and based on that ISC Nodes may be available for software package upgrade. Based on node type selection backed logic may automatically be assigned to the user and based on user selection that nodes and execution MOP may be executed for software package upgrade workorder. The backed logic may be a set of predefined instructions associated with each node type, that may be executed to upgrade the corresponding node.

[0127] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

[0128] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0129] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.TECHNICAL ADVANCEMENTS

[0130] As is evident from the above, the present disclosure provides a technically advanced solution by providing an improved system and method for upgrading software of node(s) by using a single User Interface (UI).

[0131] The present disclosure provides a system and a method that allows the user to upgrade the software package of different types of nodes through the single UI.

[0132] The present disclosure allows the user to track the execution status and workorder status of different types of nodes through the single UI.

[0133] The present disclosure provides the single UI that makes the user’s work easy and fast, reduces time for upgrading the software of a node with minimal or no human intervention.

[0134] The present disclosure enables users to initiate upgrades for different types of network nodes through a single user interface, eliminating the need for multiple systems.

[0135] By consolidating the upgrade process into a single platform, the present disclosure streamlines software upgrades, saving time and operational costs.

[0136] The present disclosure establishes a uniform approach to software upgrades across different node types, leading to improved consistency and compliance.

Claims

Claims1. A system (108) for managing an upgradation of a node of a network (106), wherein the system (108) comprising: a receiving unit (212) configured to receive at least one workorder associated with the upgradation of the node of the network; and a processing unit (208) communicatively coupled to the receiving unit (212), wherein the processing unit (208) is configured to receive the at least one workorder from the receiving unit, wherein the processing unit (208) comprises: a node identification module (214) configured to identify at least one node corresponding to a node type of the network (106) from the at least one received workorder; a validation module (216) configured to validate the at least one identified node based on predetermined criteria; and a request transmission module (218) configured to transmit at least one request to a node management unit (220) upon validation of the at least one identified node, wherein the at least one request comprises one or more execution instructions for managing the upgradation of the at least one validated node of the network (106).

2. The system (108) as claimed in claim 1, wherein the at least one node of the network (106) comprises a Radio Access Network (RAN) node.

3. The system (108) as claimed in claim 1, wherein the at least one workorder comprises at least one of the node types of the network (106), one or more details associated with the at least one node, at least one execution type associated with the upgradation of the node and workorder execution scheduling information.

4. The system (108) as claimed in claim 3, wherein the at least one execution type associated with the upgradation of the node comprises at least one of a pre-check execution, an alarm check execution, a software download execution, a software package upgrade execution and a post-check execution.

5. The system (108) as claimed in claim 1, wherein the one or more execution instructions are based on the at least one received workorder.

6. The system (108) as claimed in claim 1, wherein the node type of the network (106) comprises at least one of a macro node type and an indoor small cell (ISC) node type.

7. The system (108) as claimed in claim 1, wherein the processing unit (208) further comprises a report generation module (222) configured to generate a report of at least one invalid node of the network (106).

8. The system (108) as claimed in claim 1, wherein the processing unit (208) further comprises an output module (224) configured to receive a response indicating at least one execution status of the at least one validated node from the node management unit (220).

9. A method (500) for managing an upgradation of a node of a network (106), the method (500) comprising steps of: receiving, by a receiving unit (212), at least one workorder associated with the upgradation of the node; identifying, by a processing unit (208), at least one node corresponding to a node type of the network (106) from the at least one received workorder; validating, by the processing unit (208), the at least one identified node based on predetermined criteria; andtransmitting, by the processing unit (208), at least one request to a node management unit (220) upon validation of the at least one identified node, wherein the at least one request comprises one or more execution instructions for managing the upgradation of the at least one validated node of the network (106).

10. The method (500) as claimed in claim 9, wherein the at least one node of the network (106) comprises a Radio Access Network (RAN) node.

11. The method (500) as claimed in claim 9, wherein the at least one workorder comprises at least one of the node types of the network (106), one or more details associated with the at least one node, at least one execution type associated with the upgradation of the node and workorder execution scheduling information.

12. The method (500) as claimed in claim 11, wherein the at least one execution type comprises at least one of a pre-check execution, an alarm check execution, a software download execution, a software package upgrade execution and a post-check execution.

13. The method (500) as claimed in claim 9, wherein the one or more execution instructions are based on the at least one received workorder.

14. The method (500) as claimed in claim 9, wherein the node type of the network (106) comprises at least one of a macro node type and an indoor small cell (ISC) node type.

15. The method (500) as claimed in claim 9, further comprising generating, by the processing unit (208), a report of at least one invalid node of the network (106).

16. The method (500) as claimed in claim 9, further comprising receiving, by the processing unit (208), a response indicating at least one execution status of the at least one validated node from the node management unit (220).

17. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of: receiving, by the network (106), a connection request from the UE (104); sending, by the network (106), an acknowledgment of the connection request to the UE (104); and transmitting a plurality of signals in response to the connection request, wherein an upgradation of a node of the network (106) is managed by a method (500) as claimed in claim 9.

18. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (500) for managing an upgradation of a node of a network (106), the method (500) comprising steps of: receiving, by a receiving unit (212), at least one workorder associated with the upgradation of the node; identifying, by a processing unit (208), at least one node corresponding to a node type of the network (106) from the at least one received workorder; validating, by the processing unit (208), the at least one identified node based on predetermined criteria; and transmitting, by the processing unit (208), at least one request to a node management unit (220) upon validation of the at least one identified node, wherein the at least one request comprises one or more execution instructions for managing the upgradation of the at least one validated node of the network (106).

Images