FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR UPGRADING A DOCKER PLATFORM ON ONE OR MORE TARGET NETWORK
NODES”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR UPGRADING A DOCKER PLATFORM ON ONE OR MORE TARGET NETWORK NODES
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to the field of
wireless communication systems. More particularly, embodiments of the present disclosure relate to methods and systems for upgrading a docker platform on one or more target network nodes.
BACKGROUND
[0002] 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.
[0003] Wireless communication technology has rapidly evolved over the past
few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect

multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] The node functions available in the present wireless communication
systems may be available as containers. A docker platform is a software platform that allows to build, test, and deploy applications that may be related to the nodes installed in these wireless communication systems. Docker packages software into standardized, i.e., “containers”. These containers may have the elements that are needed by the software applications to run, including libraries, system tools, code, and runtime. Thus, it is possible to quickly deploy and scale applications into any environment using a docker platform. This is also a highly reliable, low-cost way to build, ship, and run distributed applications at any scale. Also, the docker platform for running the applications needs to be updated and upgraded whenever needed.
[0005] The existing solutions provide for manually upgrading the docker
platform or the cloud native platform. However, automated upgradation of docker platform or the cloud native platform may facilitate in minimizing time required to upgrade the platform and also reducing errors that may be introduced in the system while upgrading the docker platform or the cloud native platform.
[0006] Further, over the period of time various solutions have been developed
to improve the performance of communication devices and to upgrade the cloud native platform or the docker platform. However, there are certain challenges with existing solutions, as none of the existing solutions provide for automated upgradation of the docker platform and are thus more time-consuming and prone to errors.

[0007] Thus, there exists an imperative need in the art to provide a method and
a system for upgrading a docker platform on one or more target network nodes, which the present disclosure aims to address.
SUMMARY
[0008] This section is provided to introduce certain aspects of the present
disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0009] An aspect of the present disclosure may relate to a method for
upgrading a docker platform on one or more target network nodes. The method includes receiving, by a transceiver unit via a user interface, a user input related to a selection of the one or more target network nodes from a set of network nodes, for performing the upgradation of the docker platform. Next, the method includes triggering, by an automation unit, an automation task for performing the upgradation of the docker platform on the selected one or more target network nodes. Next, the method includes restarting, by a restarting unit, the docker platform on the selected one or more target network nodes to complete the upgradation of the docket platform on the selected one or more target nodes.
[0010] In an exemplary aspect of the present disclosure, the method further
comprises performing, by a verification unit, a verification process on each of the selected one or more target network nodes.
[0011] In an exemplary aspect of the present disclosure, the verification
process comprises performing, by the verification unit, a check on the selected one or more target network nodes, the check related to functioning of the selected one or more target network nodes; and generating, by the verification unit, a result of

the check performed on the selected one or more target network nodes, wherein the result is one of a successful upgradation result and an unsuccessful upgradation result, and wherein the successful upgradation result is generated for a set of first network nodes functioning correctly post the restarting of the docker platform, and the unsuccessful upgradation result is generated for a set of second network nodes functioning incorrectly post the restarting of the docker platform.
[0012] In an exemplary aspect of the present disclosure, wherein prior to the
receiving, by the transceiver unit via the user interface, the user input related to the selection of the one or more target network nodes, the method comprises checking, by a connection unit, a connectivity with the one or more target network nodes.
[0013] In an exemplary aspect of the present disclosure, the method further
comprises the triggering, by the automation unit, the automation task, is performed remotely on the selected one or more target network nodes based on a set of instructions stored in storage unit for the corresponding selected one or more target network nodes.
[0014] Another aspect of the present disclosure may relate to a system for
upgrading a docker platform on one or more target network nodes. The system comprises a transceiver unit configured to receive, via a user interface, a user input related to a selection of one or more target network nodes from a set of network nodes, for performing the upgradation of the docker platform. The system further comprises an automation unit connected to at least the transceiver unit, the automation unit is configured to trigger an automation task for performing the upgradation of docker platform on the selected one or more target network nodes. The system further comprises a restarting unit connected to at least the automation unit, the restarting unit is configured to restart the docker platform on the selected one or more target network nodes to complete the upgradation of the docker platform on the selected one or more target nodes.

[0015] Yet another aspect of the present disclosure may relate to a user
equipment (UE). The UE comprises a system, the system comprising a transceiver unit configured to send, via a user interface, a user input related to a selection of one or more target network nodes from a set of network nodes, for performing the upgradation of the docker platform; an automation unit connected to at least the transceiver unit, the automation unit is configured to trigger an automation task for performing the upgradation of docker platform on the selected one or more target network nodes; a restarting unit connected to at least the automation unit, the restarting unit is configured to restart the docker platform on the selected one or more target network nodes to complete the upgradation of the docker platform on the selected one or more target nodes.
[0016] Yet another aspect of the present disclosure may relate to a non-
transitory computer readable storage medium storing instructions for upgrading a docker platform on one or more target network nodes, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit of the system to receive, via a user interface, a user input related to a selection of one or more target network nodes from a set of network nodes, for performing the upgradation of the docker platform; an automation unit connected to at least the transceiver unit, the automation unit of the system to trigger an automation task for performing the upgradation of docker platform on the selected one or more target network nodes; a restarting unit connected to at least the automation unit, the restarting unit of the system to restart the docker platform on the selected one or more target network nodes to complete the upgradation of the docker platform on the selected one or more target nodes.
OBJECTS OF THE INVENTION

[0017] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0018] It is an object of the present disclosure to provide a system and a method
for automated upgradation of the docker platform that consumes less time for upgrading a docker platform.
[0019] It is another object of the present disclosure to provide a solution that is
less prone to errors.
DESCRIPTION OF THE DRAWINGS
[0020] 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. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0021] FIG. 1 illustrates an exemplary block diagram of a computing device
upon which the features of the present disclosure may be implemented, in accordance with exemplary implementations of the present disclosure.

[0022] FIG. 2 illustrates an exemplary block diagram of a system for upgrading
a docker platform on one or more target network nodes, in accordance with exemplary implementations of the present disclosure.
[0023] FIG. 3 illustrates a flow diagram of a method for upgrading a docker
platform on one or more target network nodes, in accordance with exemplary implementations of the present disclosure.
[0024] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
[0025] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
[0026] 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.

[0027] 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, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0028] Also, it is noted that individual embodiments may be described as a
process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may 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.
[0029] 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—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0030] As used herein, a “processing unit” or “processor” or “operating
processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A 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 (Digital Signal Processing) 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 or processing unit is a hardware processor.
[0031] As used herein, “a user equipment”, “a user device”, “a smart-user-
device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0032] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.

[0033] As used herein “interface” or “user interface” refers to a shared
boundary across which two or more separate components of a system exchange information or data. The interface may also refer to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
[0034] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0035] As used herein the transceiver unit includes at least one receiver and at
least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
[0036] As used herein, Access and Mobility Management Function (AMF) is
a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
[0037] As used herein, Session Management Function (SMF) is a 5G core
network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane

Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
[0038] As used herein, a docker platform is a cloud native platform for
providing containers or software packages in virtual or cloud environments, and for building or running applications in microservices architectures.
[0039] As discussed in the background section, the current known solutions for
automated upgradation of docker platform have several shortcomings such as those related to more time consumption and errors introduced in the process of upgradation of docker platform. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a method and a system for upgrading a docker platform on one or more target network nodes.
[0040] Hereinafter, exemplary embodiments of the present disclosure will be
described with reference to the accompanying drawings.
[0041] FIG. 1 illustrates an exemplary block diagram of a computing device
[100] (also referred to herein as a computer system [100]) upon which the features of the present disclosure may be implemented, in accordance with exemplary implementations of the present disclosure. In an implementation, the computing device [100] may also implement a method for upgrading a docker platform on one or more target network nodes utilising the system. In another implementation, the computing device [100] itself implements the method for upgrading a docker platform on one or more target network nodes using one or more units configured within the computing device [100], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0042] The computing device [100] may include a bus [102] or other
communication mechanism for communicating information, and a hardware processor [104] coupled with bus [102] for processing information. The hardware processor [104] may be, for example, a general purpose microprocessor. The computing device [100] may also include a main memory [106], such as a random access memory (RAM), or other dynamic storage device, coupled to the bus [102] for storing information and instructions to be executed by the processor [104]. The main memory [106] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [104]. Such instructions, when stored in non-transitory storage media accessible to the processor [104], render the computing device [100] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [100] further includes a read only memory (ROM) [108] or other static storage device coupled to the bus [102] for storing static information and instructions for the processor [104].
[0043] A storage device [110], such as a magnetic disk, optical disk, or solid-
state drive is provided and coupled to the bus [102] for storing information and instructions. The computing device [100] may be coupled via the bus [102] to a display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [114], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [102] for communicating information and command selections to the processor [104]. Another type of user input device may be a cursor controller [116], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [104], and for controlling cursor movement on the display [112]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.

[0044] The computing device [100] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [100] causes or programs the computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [100] in response to the processor [104] executing one or more sequences of one or more instructions contained in the main memory [106]. Such instructions may be read into the main memory [106] from another storage medium, such as the storage device [110]. Execution of the sequences of instructions contained in the main memory [106] causes the processor [104] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[0045] The computing device [100] also may include a communication
interface [118] coupled to the bus [102]. The communication interface [118] provides a two-way data communication coupling to a network link [120] that is connected to a local network [122]. For example, the communication interface [118] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [118] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [118] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0046] The computing device [100] can send messages and receive data,
including program code, through the network(s), the network link [120] and the communication interface [118]. In the Internet example, a server [130] might transmit a requested code for an application program through the Internet [128], the

ISP [126], the local network [122], host [124] and the communication interface [118]. The received code may be executed by the processor [104] as it is received, and/or stored in the storage device [110], or other non-volatile storage for later execution.
[0047] The computing device [100] encompasses a wide range of electronic
devices capable of processing data and performing computations. Examples of the computing device [100] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The computing device [100] may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, the computing device [100] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications.
[0048] Referring to FIG. 2, an exemplary block diagram of a system [200] for
upgrading a docker platform on one or more target network nodes is shown, in accordance with the exemplary embodiments of the present invention. The system [200] comprises at least one transceiver unit [202], at least one user interface [204], at least one automation unit [206], at least one restarting unit [208], at least one verification unit [210], at least one connection unit [212], and at least one storage unit [214]. Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. Also, in FIG. 2 only a few units are shown; however, the system [200] may comprise multiple such units or the system [200] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [200] may be present in a user equipment (UE) (such as, a user device) to implement the features of the present invention. The system [200] may be a part of the UE, or may be independent of, but in communication with the UE. In another implementation, the system [200] may reside in a server or a network entity. In yet

another implementation, the system [200] may reside partly in the server/ network entity and partly in the UE.
[0049] The system [200] is configured for upgrading a docker platform on one
or more target network nodes, with the help of the interconnection between the components/units of the system [200].
[0050] In order to automatically upgrade the docker platform, the system [200]
comprises a transceiver unit [202]. The transceiver unit [202] is configured to receive, via a user interface [204], a user input related to a selection of one or more target network nodes from a set of network nodes, for performing the upgradation of the docker platform. In an exemplary implementation, a user such as, network admin, service provider or any authorised person may provide the input related to a selection of one or more target network nodes for performing the upgradation of the docker platform. The user may provide the input using a user device such as a mobile device, a computer device and a human machine interface (HMI) device, etc. The user input may be in any form of text, touch and voice format. The one or more target network nodes may be such as, but not limited to, in a wireless network and cellular network (e.g., Access and Mobility Management Function (AMF) in 5G network), on which upgradation may be desired by the user. As used herein, the upgradation of docker platform may be associated with such as, but not limited to, adding or installing new features of operating system (OS), OS version, software packages, supported formats, and plug-ins.
[0051] The system [200] further comprises a connection unit [212]. The
connection unit [212] is configured to check a connectivity with the one or more target network nodes. In an implementation, prior to the transceiver unit [202] receiving, via the user interface [204], the user input related to the selection of the one or more target network nodes, the connection unit [212] is configured to check that the selected target network nodes are connected in the network with a storage

unit [214] or a docker upgrade server. In an implementation, the connection unit [212] is configured to check that the target network nodes are active or in-service in the network and connected to the storage unit [214] or a docker upgrade server.
[0052] In an implementation, the network may be, such as but not limited to,
4G, 5G or 6G network. The target network nodes and set of the nodes may be such as, but not limited to, Access and Mobility Management Function (AMF), Session management Function (SMF) in 5G network.
[0053] The system [200] further comprises an automation unit [206], which is
connected to the transceiver unit [202]. The automation unit [206] is configured to trigger an automation task for performing the upgradation of docker platform on the selected one or more target network nodes. The automation unit [206] is configured to receive the user input related to the selection of one or more target network nodes for performing the upgradation of the docker platform from the transceiver unit [202]. Thereafter, the automation unit [206] is configured to trigger the automation task for performing the upgradation of the docker platform on the selected one or more target network nodes. In an implementation, the automation unit [206] is configured to trigger the automation task remotely on the selected one or more target network nodes based on a set of instructions stored in storage unit [214] or docker upgrade server for the corresponding selected one or more target network nodes.
[0054] The storage unit [214] or docker upgrade server is configured to store
the instructions for performing automated upgradation of the docker platform. In an implementation, these instructions may be fetched by the automation unit [206] while triggering the automation task for upgrading the docker platform on the selected one or more target network nodes.

[0055] The system [200] further comprises a restarting unit [208], which is
connected to the automation unit [206]. The restarting unit [208] is configured to restart the docker platform on the selected one or more target network nodes to complete the upgradation of the docker platform on the selected one or more target nodes. After performing the upgradation of the docker platform on the selected target nodes, the automation unit [206] is configured to communicate with the restarting unit [208]. The restarting unit [208] is configured to restart the selected one or more target network nodes to complete the upgradation of the docker platform. In an exemplary implementation, the upgradation may be associated with fixing one or more bugs and various patches.
[0056] The system [200] further comprises a verification unit [210]. The
verification unit [210] may be connected to the restarting unit [208]. The verification unit [210] is configured to perform a verification process on each of the selected one or more target network nodes. The verification unit [210] is configured to perform the verification process comprises a check on the selected one or more target network nodes, such as AMF nodes and SMF nodes in 5G network, the check is related to functioning of the selected one or more target network nodes and generate a result of the check performed on the selected one or more target network nodes. The result may comprise one of a successful upgradation result and an unsuccessful upgradation result. The successful upgradation result is generated for a set of first network nodes functioning correctly post restart of the docker platform, and the unsuccessful upgradation result is generated for a set of second network nodes functioning incorrectly post restart of the docker platform.
[0057] In an exemplary implementation, the verification unit [210] is
configured to check the functioning of the selected one or more target network nodes for identifying any error or any deviation from the upgrade or working correctly.

[0058] In an exemplary implementation, the system [200] is configured to store
the set of first network nodes with a successful upgradation status and the set of second network nodes with an unsuccessful upgradation status. The system [200] may share status of the upgradation of the target network nodes with the user.
[0059] In an exemplary implementation, the system [200] is configured to
retrigger, by the automation unit [206], the automation task for performing the upgradation of docker platform on the set of second network nodes as per pre-configured numbers and after pre-configured time durations.
[0060] Further, in accordance with the present disclosure, it is to be
acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0061] Referring to FIG. 3, an exemplary flow diagram of a method [300] for
upgrading a docker platform on one or more target network nodes, in accordance with exemplary embodiments of the present invention is shown. In an implementation the method [300] is performed by the system [200]. As shown in FIG. 3, the method [300] starts at step [302].
[0062] At step [304], the method [300] comprises receiving, by a transceiver
unit [202] via a user interface [204], a user input related to a selection of the one or more target network nodes from a set of network nodes, for performing the

upgradation of the docker platform. In an exemplary implementation, a user such as, network admin, service provider or any authorised person may provide the input related to a selection of one or more target network nodes for performing the upgradation of the docker platform. The user may provide the input using user devices such as a mobile device, a computer device and a human machine interface (HMI) device. The user input may be in any form of text, touch and voice format. The one or more target network nodes may be such as, but not limited to, in a wireless network and cellular network (e.g., Access and Mobility Management Function (AMF) in 5G network), on which upgradation may be desired by the user. As used herein, the upgradation of docker platform may be associated with such as, but not limited to, adding or installing new features of operating system (OS), OS version, software packages, supported formats, and plug-ins.
[0063] The method [300] is further implemented by a connection unit [212] to
check a connectivity with the one or more target network nodes. In an implementation, prior to the transceiver unit [202] receiving, via the user interface [204], the user input related to the selection of the one or more target network nodes, the connection unit [212] may check the selected target network nodes are connected in the network with a storage unit [214] or a docker upgrade server. In an implementation, the connection unit [212] may check the target network nodes are active or in-service in the network and connected to the storage unit [214] or a docker upgrade server.
[0064] In an implementation, the network may be, such as but not limited to,
4G, 5G or 6G network. The target network nodes and set of the nodes may be such as, but not limited to, Access and Mobility Management Function (AMF), Session management Function (SMF) in 5G network.
[0065] Next, at step [306], the method [300] comprises triggering, by an
automation unit [206], an automation task for performing the upgradation of docker

platform on the selected one or more target network nodes. The automation unit [206] may receive the user input related to the selection of one or more target network nodes for performing the upgradation of the docker platform from the transceiver unit [202]. Thereafter, the automation unit [206] may trigger the automation task for performing the upgradation of the docker platform on the selected one or more target network nodes. In an implementation, the automation unit [206] may trigger the automation task remotely on the selected one or more target network nodes based on a set of instructions stored in storage unit [214] or docker upgrade server for the corresponding selected one or more target network nodes.
[0066] The storage unit [214] or docker upgrade server may store the
instructions for performing automated upgradation of the docker platform. In an implementation, these instructions may be fetched by the automation unit [206] while triggering the automation task for upgrading the docker platform on the selected one or more target network nodes.
[0067] Next, at step [308], the method [300] comprises restarting, by a
restarting unit [208], the docker platform on the selected one or more target network nodes to complete the upgradation of the docket platform on the selected one or more target nodes. After performing the upgradation of the docker platform on the selected target nodes, the automation unit [206] may communicate with the restarting unit [208]. The restarting unit [208] may restart the selected one or more target network nodes to complete the upgradation of the docker platform. In an exemplary implementation, the upgradation may be associated with fixing one or more bugs and various patches.
[0068] The method [300] may further be implemented by a verification unit
[210] that may be connected to the restarting unit [208]. The verification unit [210] may perform a verification process on each of the selected one or more target

network nodes. The verification unit [210] may perform the verification process comprises a check on the selected one or more target network nodes, such as AMF nodes and SMF nodes in the 5G network, the check is related to functioning of the selected one or more target network nodes and generate a result of the check performed on the selected one or more target network nodes. Further, the result may comprise one of a successful upgradation result and an unsuccessful upgradation result. The successful upgradation result is generated for a set of first network nodes functioning correctly post restart of the docker platform, and the unsuccessful upgradation result is generated for a set of second network nodes functioning incorrectly post restart of the docker platform.
[0069] In an exemplary implementation, the verification unit [210] may check
the functioning of the selected one or more target network nodes for identifying any error or any from the upgrade or working correctly.
[0070] In an exemplary implementation, the system [200] may store the set of
first network nodes with a successful upgradation status and the set of second network nodes with an unsuccessful upgradation status. The system [200] may share status of the upgradation of the target network nodes with the user.
[0071] In an exemplary implementation, the system [200] may retrigger, by the
automation unit [206], the automation task for performing the upgradation of docker platform on the set of second network nodes as per pre-configured numbers an after pre-configured time durations.
[0072] Thereafter, the method [300] terminates at step [310].
[0073] The present disclosure further discloses a user equipment (UE). The UE
comprises a system [200], the system [200] comprising a transceiver unit [202] configured to send, via a user interface [204], a user input related to a selection of

one or more target network nodes from a set of network nodes, for performing the upgradation of the docker platform; an automation unit [206] connected to at least the transceiver unit [202], the automation unit [206] is configured to trigger an automation task for performing the upgradation of docker platform on the selected one or more target network nodes; a restarting unit [208] connected to at least the automation unit [206], the restarting unit [208] is configured to restart the docker platform on the selected one or more target network nodes to complete the upgradation of the docker platform on the selected one or more target nodes.
[0074] The present disclosure further discloses a non-transitory computer
readable storage medium storing instructions for upgrading a docker platform on one or more target network nodes, the instructions include executable code which, when executed by one or more units of a system [200], causes: a transceiver unit [202] of the system to receive, via a user interface [204], a user input related to a selection of one or more target network nodes from a set of network nodes, for performing the upgradation of the docker platform; an automation unit [206] connected to at least the transceiver unit [202], the automation unit [206] of the system to trigger an automation task for performing the upgradation of docker platform on the selected one or more target network nodes; a restarting unit [208] connected to at least the automation unit [206], the restarting unit [208] of the system to restart the docker platform on the selected one or more target network nodes to complete the upgradation of the docker platform on the selected one or more target nodes.
[0075] As is evident from the above, the present disclosure provides a
technically advanced solution for automated upgradation of the docker platform. Implementing the features of the present solution for upgradation of docker platform enables one to consume less time for upgrading the docker platform. Further, the present solution for upgradation of the docker platform is less prone to errors.

[0076] While considerable emphasis has been placed herein on the
disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We Claim:
1. A method [300] for upgrading a docker platform on one or more target
network nodes, the method [300] comprising:
- receiving, by a transceiver unit [202] via a user interface [204], a user input related to a selection of the one or more target network nodes from a set of network nodes, for performing the upgradation of the docker platform;
- triggering, by an automation unit [206], an automation task for performing the upgradation of docker platform on the selected one or more target network nodes; and
- restarting, by a restarting unit [208], the docker platform on the selected one or more target network nodes to complete the upgradation of the docket platform on the selected one or more target nodes.
2. The method [300] as claimed in claim 1, the method [300] further
comprising:
- performing, by a verification unit [210], a verification process on each
of the selected one or more target network nodes.
3. The method [300] as claimed in claim 2, wherein the verification process
comprises:
- performing, by the verification unit [210], a check on the selected one or more target network nodes, the check related to functioning of the selected one or more target network nodes; and
- generating, by the verification unit [210], a result of the check performed on the selected one or more target network nodes,
wherein the result is one of a successful upgradation result and an unsuccessful upgradation result, and
wherein the successful upgradation result is generated for a set of first network nodes functioning correctly post the restarting of the

docker platform, and the unsuccessful upgradation result is generated for a set of second network nodes functioning incorrectly post the restarting of the docker platform.
4. The method [300] as claimed in claim 1, wherein prior to the receiving, by
the transceiver unit [202] via the user interface [204], the user input related
to the selection of the one or more target network nodes, the method
comprises:
- checking, by a connection unit [212], a connectivity with the one or
more target network nodes.
5. The method [300] as claimed in claim 1, wherein the triggering, by the automation unit [206], the automation task, is performed remotely on the selected one or more target network nodes based on a set of instructions stored in storage unit [214] for the corresponding selected one or more target network nodes.
6. A system [200] for upgrading a docker platform on one or more target network nodes, the system [200] comprising:

- a transceiver unit [202] configured to receive, via a user interface [204], a user input related to a selection of one or more target network nodes from a set of network nodes, for performing the upgradation of the docker platform;
- an automation unit [206] connected to at least the transceiver unit [202], the automation unit [206] is configured to trigger an automation task for performing the upgradation of docker platform on the selected one or more target network nodes; and
- a restarting unit [208] connected to at least the automation unit [206], the restarting unit [208] is configured to restart the docker platform on the selected one or more target network nodes to complete the

upgradation of the docker platform on the selected one or more target nodes.
7. The system [200] as claimed in claim 6, the system [200] further
comprising:
- a verification unit [210] configured to perform a verification process on
each of the selected one or more target network nodes.
8. The system [200] as claimed in claim 7, wherein to perform the verification
process, the verification unit [210] is configured to:
- perform a check on the selected one or more target network nodes, the check is related to functioning of the selected one or more target network nodes; and
- generate a result of the check performed on the selected one or more target network nodes,
wherein the result is one of a successful upgradation result and an unsuccessful upgradation result, and
wherein the successful upgradation result is generated for a set of first network nodes functioning correctly post restart of the docker platform, and the unsuccessful upgradation result is generated for a set of second network nodes functioning incorrectly post restart of the docker platform.
9. The system [200] as claimed in claim 6, the system [200] further comprising
a connection unit [212], wherein prior to the transceiver unit [202] receives,
via the user interface [204], the user input related to the selection of the one
or more target network nodes, the connection unit [212] is configured to:
- check a connectivity with the one or more target network nodes.

10. The system [200] as claimed in claim 6, wherein the automation unit [206] is configured to trigger the automation task remotely on the selected one or more target network nodes based on a set of instructions stored in storage unit [214] for the corresponding selected one or more target network nodes.
11. A user equipment (UE) comprising: a system, the system comprising:

- a transceiver unit [202] configured to send, via a user interface [204], a user input related to a selection of one or more target network nodes from a set of network nodes, for performing the upgradation of the docker platform;
- an automation unit [206] connected to at least the transceiver unit [202], the automation unit [206] is configured to trigger an automation task for performing the upgradation of docker platform on the selected one or more target network nodes; and
- a restarting unit [208] connected to at least the automation unit [206], the restarting unit [208] is configured to restart the docker platform on the selected one or more target network nodes to complete the upgradation of the docker platform on the selected one or more target nodes.