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 INSTALLING ONE OR MORE NETWORK FUNCTIONS (NFs)”
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 INSTALLING ONE OR MORE NETWORK FUNCTIONS (NFs)
FIELD OF THE DISCLOSURE
[0001] Embodiments of the present disclosure generally relate to wireless
communication systems. Particularly, embodiments of the present disclosure relate to methods and systems for installing one or more network functions (NFs). More particularly, the present disclosure relates to methods and systems for installing docker service Global Configuration Template (GCT).
BACKGROUND
[0002] The following description of the 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 is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the 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. Third-generation (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] In the existing solutions, different steps are required to install a Docker
platform on certain nodes. The existing attempts are only efficient in installation on a few devices such as a host or two. However, manual installation becomes an inefficient and time-consuming process in case of a need to install it on a bulk amount such as more than 100 nodes. In that case, there is a need for an automatic solution to speed up the process. At present cloud native platform setup for each individual network function is done in a manual fashion which takes more time and gives scope for human errors.
[0005] Thus, there exists an imperative need in the art to overcome the above-
stated disadvantages. Further, there exists a need for a solution to automate docker platform installation on any number of network functions/ hosts in order to increase efficiency and effectiveness and install the network functions faster and in an efficient manner.
SUMMARY
[0006] 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.
[0007] An aspect of the present disclosure relates to a method for installing one
or more network functions (NFs). The method comprises determining, by a processing unit, for a server, a connectivity with a set of NFs based on an exchange.

The method further comprises selecting, by a selection unit, at least one NF from the set of NFs, wherein said at least one NF is to be installed by the server. The method further comprises generating, by a generation unit, at the server, an event related to an operation on said at least one NF, wherein the event is executable based on a receipt of a trigger signal, and wherein the operation comprises at least an installation of said at least one NF. The method further comprises executing, by an execution unit, the operation related to the generated event, in response to the receipt of the trigger signal.
[0008] In an exemplary aspect of the present disclosure, the method comprises
performing, by the processing unit, a sanity check of the event.
[0009] In another exemplary aspect of the present disclosure, the method
comprises transmitting, by a transceiver unit, a request for an acknowledgement indicative of an execution of the operation. Further, the method comprises determining, by the processing unit, a status of the execution of the operation. The method further comprises transmitting, by the transceiver unit, the determined status.
[0010] In another exemplary aspect of the present disclosure, the status is one
of a successful execution, and an unsuccessful execution, wherein the status of the successful execution is indicative of a positive execution of the operation, and wherein the status of the unsuccessful execution is indicative of a negative execution of the operation.
[0011] In another exemplary aspect of the present disclosure, the server is a
docker global configuration template (GCT).
[0012] In another exemplary aspect of the present disclosure, for executing the
event, the method further comprises installing, by the execution unit, via the server,

a service module connected to said at least one NF. Also, the method comprises triggering, by the processing unit via the server, the service module to execute the operation, based on the generated event.
[0013] In another exemplary aspect of the present disclosure, the service
module is a docker service adapter (DSA) module.
[0014] In another exemplary aspect of the present disclosure, the method
further comprises receiving, by the transceiver unit, via a user interface (UI), a user input for selecting the at least one NF from the set of NFs.
[0015] In another exemplary aspect of the present disclosure, the receipt of the
trigger signal is received remotely.
[0016] Another aspect of the present disclosure may relate to a system for
installing one or more network functions (NFs). The system comprises a processing unit, a selection unit, a generation unit, and an execution unit connected to each other. The processing unit is configured to determine, for a server, a connectivity with a set of NFs based on an exchange. The selection unit is configured to select at least one NF from the set of NFs, wherein said at least one NF is to be installed by the server. The generation unit is configured to generate, at the server, an event related to an operation on said at least one NF, wherein the event is executable based on a receipt of a trigger signal, and wherein the operation comprises at least an installation of said at least one NF. The execution unit is configured to execute the operation related to the generated event, in response to the receipt of the trigger signal.
[0017] Yet another aspect of the present disclosure may relate to a non-
transitory computer readable storage medium storing one or more instructions for installing one or more network functions (NFs), the one or more instructions include

executable code which, when executed by one or more units of a system, causes the one or more units to perform certain functions. The one or more instructions when executed causes a processing unit to determine a connectivity with a set of NFs based on an exchange. The one or more instructions when executed further causes a selection unit to select at least one NF from the set of NFs, wherein said at least one NF is to be installed by the server. The one or more instructions when executed further causes a generation unit to generate, at the server, an event related to an operation on said at least one NF. The event is executable based on a receipt of a trigger signal. The operation comprises at least an installation of said at least one NF. The one or more instructions when executed further causes an execution unit to execute the operation related to the generated event, in response to the receipt of the trigger signal.
OBJECTS OF THE DISCLOSURE
[0018] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0019] It is an object of the present disclosure to provide a system and a method
for installing one or more network functions (NFs).
[0020] It is an object of the present disclosure to provide a system and a method
for installing docker service Global Configuration Template (GCT).
[0021] It is yet another object of the present disclosure to provide a solution to
automate Docker platform installation on any number of hosts along with 5G environment specific docker Global Configuration Template (GCT).

[0022] Yet another object of the present disclosure is to minimize time to setup
cloud native platforms, and help to implement 5G network function specific docker GCT.
BRIEF DESCRIPTION OF THE DRAWINGS
[0023] 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.
[0024] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture.
[0025] FIG. 2 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.
[0026] FIG. 3 illustrates an exemplary block diagram of a system for installing
one or more network functions (NFs), in accordance with exemplary implementations of the present disclosure.

[0027] FIG. 4 illustrates an exemplary flow diagram of a method for installing
one or more network functions (NFs), in accordance with exemplary implementations of the present disclosure.
[0028] FIG. 5 illustrates an exemplary flow diagram depicting the
implementation of the present disclosure, in accordance with exemplary implementations of the present disclosure.
[0029] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
[0030] 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.
[0031] 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.

[0032] 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.
[0033] It should be noted that the terms "first", "second", "primary",
"secondary", "target" and the like, herein do not denote any order, ranking, quantity, or importance, but rather are used to distinguish one element from another.
[0034] 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.
[0035] 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.

[0036] 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.
[0037] 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 unit(s) which are required to implement the features of the present disclosure.
[0038] 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.
[0039] 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.
[0040] 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.
[0041] 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.
[0042] As discussed in the background section, the current known solutions
have several shortcomings. 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 of installing one or more network functions (NFs).

[0043] FIG. 1 illustrates an exemplary block diagram representation of an
environment for installing one or more network functions (NFs), in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the environment comprises a server [102], one or more network functions [104], and a user interface [106]. The one or more network functions [104] comprise network functions NF-1, NF2…NF-N ( [104-1], [104-2]…[104-N]). The network functions NF-1, NF2…NF-N ( [104-1], [104-2]…[104-N]) may herein individually or collectively be referred to as network functions (NFs) [104].
[0044] The server [102] may be a computing device which may be used for
docker installation and docker global configuration template (GCT). The server [102] may be an automation platform used for performing several functions associated with installation of the one or more NFs [104]. In an example, the server [102] may be used for automatically installing the one or more NFs [104] without requiring any manual input.
[0045] The one or more network functions [104] may refer to the operations
and processes that are performed within the telecommunication network in order to facilitate communication. The one or more NFs [104] may be performed by one or more network nodes or may also be performed by different network entities. The one or more NFs [104] may be connected with the server [102] via an interface.
[0046] The user interface [106] may refer to the device or a component used
for interaction with a user or a network entity. The user interface [106] may comprise an input mechanism such as keyboard/ mouse or touch. The user interface [106] may also comprise output mechanisms such as display devices. The user interface [106] may be connected with the server [102] either directly or indirectly.
[0047] FIG. 2 illustrates an exemplary block diagram of a computing device
[200] upon which the features of the present disclosure may be implemented in

accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for installing one or more network functions (NFs) utilising the system [300]. In another implementation, the computing device [200] itself implements the method for installing the one or more network functions (NFs) using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
[0048] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204]. Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
[0049] A storage device [210], such as a magnetic disk, optical disk, or solid-
state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], 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 [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the

bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. The 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.
[0050] The computing device [200] 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 [200] causes or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] 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.
[0051] The computing device [200] also may include a communication
interface [218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] 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 [218] 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 [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0052] The computing device [200] can send messages and receive data,
including program code, through the network(s), the network link [220] and the communication interface [218]. In the Internet example, a server [230] might transmit a requested code for an application program through the Internet [228], the ISP [226], the local network [222], a host [224] and the communication interface [218]. The received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution.
[0053] FIG. 3 illustrates an exemplary block diagram of a system [300] for
installing one or more network functions [104], in accordance with the exemplary implementations of the present disclosure. The system [300] may comprise at least one processing unit [302], at least one transceiver unit [304], at least one selection unit [306], at least one generation unit [308], and at least one execution unit [310]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system [300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in a user device/ user equipment to implement the features of the present disclosure. The system [300] may be a part of a user equipment (UE) or may be independent of but in communication with the UE. In another implementation, the system [300] may reside in a server or a network entity. In yet another implementation, the system [300] may reside partly in the server/ network entity and partly in the UE.

[0054] The system [300] is configured for installing the one or more network
functions [104], with the help of the interconnection between the components/units of the system [300].
[0055] The processing unit [302] determines a connectivity with a set of NFs
based on an exchange. The exchange may be an exchange of information or data between the set of NFs [104] and the server [102]. In an example, the exchange may be an exchange of a ping. The connectivity may refer to a connection status depicting a connection for a server [102] and the set of NFs [104]. The set of Network Functions (NFs) may refer to the one or more network functions which are connected with the server [102]. The network functions may refer to one or more components within the telecommunication networks such as the 5G Core (5GC) network (5GCN).
[0056] In an implementation of the preset disclosure, the server [102] may refer
to a docker global configuration template (GCT). The docker GCT may refer to a component used for defining and managing global configuration settings for docker containers.
[0057] Once the connectivity is determined, then the selection unit [306]
selects at least one NF [104] from the set of NFs [104], wherein said at least one NF [104] is to be installed by the server [102]. The at least one NF [104] from the set of NFs [104] may be the NF that is selected based on the requirement of its installation.
[0058] For selecting the at least one NF [104], the requirement of installation
of a docker and the docker GCT may be analysed. The docker may refer to a platform used for development and deployment and managing applications using containers. In another implementation of the present disclosure, the at least one NF

[104] is selected based on a user input. The transceiver unit [304] receives the user input, at the server [102], via a user interface (UI). The user input may refer to the inputs provided by the network operator or a network entity which specifies the NFs that are required to be installed. The user interface (UI) [106] may refer to a component or a device which takes input from the user and may also be used for displaying one or more visual representations.
[0059] On selection of the at least one NF [104] which is to be installed, the
generation unit [308] generates, at the server [102], an event related to an operation on said at least one NF [104]. The event may be executable based on a receipt of a trigger signal. In an implementation of the present disclosure, the trigger signal may be received remotely, via the server [102]. For example, to trigger the signal remotely, a timer may be implemented after which the trigger signal may be sent from the user interface [106]. In another example, the trigger signal may be manually sent from the user interface [106]. It may be noted that the user interface [106] and the server [102] may not be located at the same place and may be indirectly connected for sending the trigger signal. The operation may comprise at least an installation of said at least one NF [104], i.e., the operation may refer to installation of said at least one NF [104]. The event related to the operation of said at least one NF [104] may refer to a scenario or a case when said one or more NFs [104] are installed. The event may be a task which is generated for performance/ execution of the operation.
[0060] Thereafter, in response to the receipt of the trigger signal, the execution
unit [310] executes the operation based on the event via the server. The execution of the operation may refer to the installation of said at least one NF [104] from the set of NFs [104].
[0061] In an implementation, the installation of said at least one NF [104] may
include allocating, by the execution unit [310] one or more network resources

required for the installation of the at least one NF [104]. The network resources may include, without limitations, memory resources, processing resources, connectivity resources, etc. The memory resources may include one or more nodes that are adapted to store information/data, such as repository nodes, databases, storage instances, etc. The processing resources may include sub-units (e.g., the execution unit [310]) that is configured to execute instructions to instantiate and initialise the at least one NF [104]. The connectivity resources may include interfaces, and other microservices that are adapted to exchange data and/or instructions with the at least one NF [104].
[0062] In another implementation of the present disclosure, the transceiver unit
[304] transmits, via the server, a request for an acknowledgement indicative of the execution of the operation. For example, the request for acknowledgement may be transmitted from the user interface (UI) [106], to the server. The request for the acknowledgement may refer to a request for receiving an indication representing the status of the execution of the operation.
[0063] Then the processing unit [302] determines, via the server, a status of the
execution of the operation. In an implementation of the present disclosure, the status is one of a successful execution, and an unsuccessful execution. The status of the successful execution is indicative of a positive execution of the operation. The positive execution of the operation is the indication that the operation has been executed successfully without any errors. The status of the unsuccessful execution is indicative of a negative execution of the operation. The negative execution of the operation may refer to the indication that the operation has not been able to be executed properly and the operation has resulted in a failure due to some errors. Then the transceiver unit [304] transmits, via the server, the determined status. The determined status may be transferred in order to communicate the failure to the user interface.

[0064] In another implementation of the present disclosure, the processing unit
[302] may also be configured to perform, via the server, a sanity check of the event. The sanity check may refer to the type of software testing that is used to verify that a small change or a bug fix in the software is working as intended and has not caused any unexpected side effects or broken any existing functionality.
[0065] In another implementation of the present disclosure, to execute the
operation the execution unit [310] installs, via the server, a service module connected to said at least one NF [104]. In an implementation of the present disclosure, the service module may refer to a docker service adapter (DSA) module. The DSA module may be the component acting as an interface or a bridge between the docker and the telecommunication network. Further, to execute the operation, the execution unit [310] triggers, via the server, the service module to execute the operation.
[0066] FIG. 4 illustrates an exemplary flow diagram of a method [400] for
installing the one or more network functions (NFs), in accordance with exemplary implementations of the present disclosure. In an implementation, the method [400] is performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402].
[0067] At step [404], the method [400] comprises determining, by a processing
unit [302], for the server [102], a connectivity with a set of NFs [104] based on an exchange.
[0068] In an implementation of the preset disclosure, the server [102] may refer
to a docker global configuration template (GCT).

[0069] After, the connectivity is determined, then at step [406], the method
[400] comprises selecting, by a selection unit [306], at least one NF [104] from the set of NFs [104], wherein said at least one NF [104] is to be installed by the server.
[0070] In an implementation of the present disclosure, for selecting the at least
one NF [104], the method [400] further comprises receiving, by the transceiver unit [304], via a user interface (UI), a user input for selecting the at least one NF [104] from the set of NFs [104].
[0071] After, the at least one NF [104] is selected, then at step [408], the
method [400] involves generating, by the processing unit [302], at the server [102], an event related to an operation on said at least one NF [104], wherein the event is executable based on a receipt of a trigger signal, and wherein the operation comprises at least an installation of said at least one NF [104].
[0072] In an implementation of the present disclosure, for the receipt of the
trigger signal, the trigger signal may be received remotely.
[0073] In one implementation of the present disclosure, the method [400] also
comprises transmitting, by a transceiver unit [304] a request for an acknowledgement indicative of an execution of the operation. The method [400] may also comprise determining, by the processing unit [302], a status of the execution of the operation. The method [400] may also comprise transmitting, by the transceiver unit [304], the determined status.
[0074] In another implementation of the present disclosure, the status may be
one of a successful execution, and an unsuccessful execution. The status of the successful execution is indicative of a positive execution of the operation. The status of the unsuccessful execution is indicative of a negative execution of the operation.

[0075] Thereafter, in response to the receipt of the trigger signal, the method
[400] at step [410] comprises executing, by the processing unit [302], the operation related to the generated event.
[0076] In another implementation of the present disclosure, for the executing
of the event, the method further comprises installing, by the execution unit [310], via the server, a service module connected to said at least one NF [104]. The method [400] also comprises triggering, by the processing unit [302] via the server, the service module to execute the operation, based on the generated event.
[0077] In another implementation of the present disclosure, the service module
is a docker service adapter (DSA) module.
[0078] In an implementation of the present disclosure, the method [400] also
comprises performing, by the processing unit [302], a sanity check of the event.
[0079] Thereafter, at step [412], the method [400] is terminated.
[0080] FIG. 5 illustrates an exemplary flow diagram [500] depicting the
implementation of the present disclosure, in accordance with exemplary implementations of the present disclosure. As shown in the figure, on receipt of the user input at the server [102], at step 1, the NF is selected based on the requirement of the docker installation and docker GCT. Therea, the event generated related to the operation on the NFs [104]. The generated event may be a task for performance of the operation which may be the installation of the network functions (NFs) [104]. Thereafter, at step 2, the generated event is executed. The generated event may be related to docker installation and docker GCT. Meanwhile, step 3, involves the execution period of step 2, and waits for the completion of step 2. Step 3 may also involve obtaining an outcome of the execution of the operation based on the

execution of the event. The outcome may be positive execution or negative execution. Based on the outcome of the step 2, step 4 proceeds to restart the docker service which leads to another outcome. Then based on this another outcome, at step 5, the docker installation and the docker GCT may be completed.
[0081] The present disclosure further discloses a non-transitory computer
readable storage medium storing one or more instructions for installing the one or more network functions (NFs), the one or more instructions include executable code which, when executed by one or more units of a system [300], causes the one or more units to perform certain functions. The one or more instructions when executed causes a processing unit [302] to determine a connectivity with a set of NFs [104] based on an exchange. The one or more instructions when executed further causes a selection unit [306] to select at least one NF [104] from the set of NFs [104], wherein said at least one NF [104] is to be installed by the server. The one or more instructions when executed further causes a generation unit [302] to generate, at the server, an event related to an operation on said at least one NF [104]. The event is executable based on a receipt of a trigger signal. The operation comprises at least an installation of said at least one NF [104]. The one or more instructions when executed further causes an execution unit [302] to execute the operation related to the generated event, in response to the receipt of the trigger signal.
[0082] As is evident from the above, the present disclosure provides a
technically advanced solution for installing the one or more network functions (NFs). The present solution provides a solution to automate Docker platform installation on any number of hosts along with 5G environment specific docker GCT (Global Configuration Template). Further, due to inefficient procedure of manually installing the one or more NFs, the present solution provides a solution which is more efficient due to its automated procedure requiring very little manual intervention, which increases efficiency of installing the network functions. The present proves installation on any number of network functions/ hosts and provides

increased efficiency and effectiveness and installs the network functions faster and in an efficient manner.
[0083] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations 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.
[0084] 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.

We Claim:
1. A method for installing one or more network functions (NFs) [104], the
method comprising:
- determining, by a processing unit [302], for a server, a connectivity with a set of NFs [104] based on an exchange;
- selecting, by a selection unit [306], at least one NF [104] from the set of NFs [104], wherein said at least one NF [104] is to be installed by the server; and
- generating, by a generation unit [308], at the server, an event related to an operation on said at least one NF [104], wherein the event is executable based on a receipt of a trigger signal, and wherein the operation comprises at least an installation of said at least one NF [104];
wherein, in response to the receipt of the trigger signal, the method comprises:
- executing, by an execution unit [310], the operation related to the generated event.
2. The method as claimed in claim 1, wherein the method comprises performing, by the processing unit [302], a sanity check of the event.
3. The method as claimed in claim 1, wherein the method comprises:

- transmitting, by a transceiver unit [304], a request for an acknowledgement indicative of an execution of the operation;
- determining, by the processing unit [302], a status of the execution of the operation; and
- transmitting, by the transceiver unit [304], the determined status.

4. The method as claimed in claim 3, wherein the status is one of a successful execution, and an unsuccessful execution, wherein the status of the successful execution is indicative of a positive execution of the operation, and wherein the status of the unsuccessful execution is indicative of a negative execution of the operation.
5. The method as claimed in claim 1, wherein the server is a docker global configuration template (GCT).
6. The method as claimed in claim 1, wherein for the executing of the event, the method further comprises:

- installing, by the execution unit [310], via the server, a service module connected to said at least one NF [104]; and
- triggering, by the processing unit [302] via the server, the service module to execute the operation, based on the generated event.

7. The method as claimed in claim 6, wherein the service module is a docker service adapter (DSA) module.
8. The method as claimed in claim 1, wherein the method further comprises: receiving, by a transceiver unit [304], via a user interface (UI), a user input for selecting the at least one NF [104] from the set of NFs [104].
9. The method as claimed in claim 1, wherein for the receipt of the trigger signal is received remotely.
10. A system [300] for installing one or more network functions (NFs) [104], the system [300] comprising:

- a processing unit [302] configured to determine, for a server, a connectivity with a set of NFs [104] based on an exchange;
- a selection unit [306] connected at least to the processing unit [302], the selection unit [306] configured to select, at least one NF [104] from the set of NFs [104], wherein said at least one NF [104] is to be installed by the server;
- a generation unit [308] connected at least to the processing unit [302], the generation unit [308] configured to generate, at the server, an event related to an operation on said at least one NF [104], wherein the event is executable based on a receipt of a trigger signal, and wherein the operation comprises at least an installation of said at least one NF [104]; and
- an execution unit [310] connected at least to the processing unit [302], the execution unit [310] configured to execute the operation related to the generated event, in response to the receipt of the trigger signal.

11. The system [300] as claimed in claim 10, wherein the processing unit [302] is configured to perform, via the server, a sanity check of the event.
12. The system [300] as claimed in claim 10, wherein the system comprises a transceiver unit [304] connected at least to the processing unit [302], and wherein,

- the transceiver unit [304] is configured to transmit, via the server, a request for an acknowledgement indicative of an execution of the operation,
- the processing unit [302] is configured to determine, via the server, a status of the execution of the operation, and
- the transceiver unit [304] is configured to transmit, via the server, the determined status.

13. The system [300] as claimed in claim 12, wherein the status is one of a successful execution, and an unsuccessful execution, wherein the status of the successful execution is indicative of a positive execution of the operation, and wherein the status of the unsuccessful execution is indicative of a negative execution of the operation.
14. The system [300] as claimed in claim 10, wherein the server is a docker global configuration template (GCT).
15. The system [300] as claimed in claim 10, wherein, to execute, via the server, the operation, the execution unit [310] is configured to:

- install a service module connected to said at least one NF [104]; and
- trigger the service module to execute the operation.

16. The system [300] as claimed in claim 15, wherein the service module is a docker service adapter (DSA) module.
17. The system [300] as claimed in claim 10, wherein the at least one NF [104] is selected based on a user input, and wherein a transceiver unit [304] is configured to receive the user input, at the server, via a user interface (UI) [106].
18. The system [300] as claimed in claim 10, wherein a transceiver unit [304] is configured to receive the trigger signal remotely, via the server.