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 INSTALLATION AND COMMISSIONING OF NETWORK NODE IN NETWORK”
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 INSTALLATION AND COMMISSIONING OF NETWORK NODE IN NETWORK
FIELD OF THE DISCLOSURE
[0001] Embodiments of the present disclosure generally relate to the field of network infrastructure management. More particularly, embodiments of the present disclosure relate to installation and commissioning of a network node in a network.
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 antilog 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. The 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] A Network Function (NF) (herein, may also be referred to as a network node) such as Access and Mobility Management Function (AMF) system installation and commissioning (I&C) requires a set of metadata as input. The nature of metadata is complex due to interdependency of internal fields. This data needs to be prepared by simplified method and must be easy for review before taking for usage. If there is issue in data selected which is not fulfilling criteria of interdependency of internal fields, it can cause delay in installation and commissioning. The metadata may be generated based on an Office Dependent Data (ODD). The ODD refers to the information and configurations that are specific to the management, operation, and maintenance of network node(s)/ network functions and infrastructure of the network. This may include data related to network node configuration, parameters, connections of the node with other entities, etc. and used while installation of a network node. For example, the connections with ports, switches, etc., the PLMN (public land mobile network) connections, etc. If the ODD is not valid, this may cause incorrect commissioning of system which may lead to undesired behavior of NF and also in some cases total count of I&C might increase which may need additional time and effort to correct. Main challenge of preparing proper ODD data and getting reviewed before attempting for I&C, is crucial if there are large number of I&C to be done in specified time across multiple sites. Further, if there is an issue in ODD data, I&C might fail, and the user needs to correct the data and re-attempt it. This is repetitive unless I&C is successful.
[0005] Hence, in view of these and other existing limitations, there arises an imperative need to install and commission the network node/ network systems having desired configuration based on data in the network to overcome the

limitations by providing a method and system for installation and commissioning of the network node in the network, which the present disclosure aims to address.
OBJECTS OF THE DISCLOSURE
[0006] This section is provided to introduce certain objects and aspects of the present invention in a simplified form that are further described below in the description. In order to overcome at least a few problems associated with the known solutions as provided in the previous section, an object of the present invention is to substantially reduce the limitations and drawbacks of the prior arts as described hereinabove.
[0007] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0008] It is an object of the present disclosure to provide a system and a method for installation and commissioning of a network node with desired configuration based on an automatically generated office dependent data (ODD).
[0009] It is another object of the present disclosure to provide a solution that automatically generates ODD.
[0010] It is yet another object of the present disclosure to provide a solution to reduce failed attempts at installation and commissioning of the network node because of incorrect ODD.
SUMMARY OF THE DISCLOSURE
[0011] 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.
[0012] An aspect of the present disclosure may relate to a method for installation and commissioning of a network node in a network. The method comprises receiving, by a transceiver unit at an installation and commissioning system (IAC system), a request for the installation and commissioning of the network node. The method further comprises automatically generating, by a processing unit at the IAC system, a set of Office Dependent Data (ODD) based on the request. The method further comprises performing, by an execution unit at the IAC system, a review action associated with the set of ODD based on predefined ODD review rules. The method further comprises detecting, by a detection unit at the IAC system, a status associated with the set of ODD based on the review action. The status can be one of a positive ODD status and a negative ODD status. The method further comprises generating, by the processing unit at the IAC system, a plurality of metadata based on the set of ODD and the positive ODD status. The method further comprises determining, by a determination unit at the IAC system, a target configuration associated with the request based on the metadata. The method further comprises triggering, by the execution unit, the installing and commissioning of the network node based on the target configuration.
[0013] In an exemplary aspect of the present disclosure, the ODD is generated in a predefined format at the network node.
[0014] In an exemplary aspect of the present disclosure, the ODD is generated in the predefined format at the network node via one or more macros.
[0015] In an exemplary aspect of the present disclosure, the positive ODD status is detected at the detection unit in an event a successful response associated with the review action is received at the detection unit.

[0016] In an exemplary aspect of the present disclosure, the method further
comprises performing, by the execution unit, a data update action associated with
the set of ODD based on the negative ODD status, wherein the negative ODD status
5 is detected at the detection unit in an event an unsuccessful response associated with
the review action is received at the detection unit.
[0017] In an exemplary aspect of the present disclosure, the target configuration is
determined further based on a set of configuration parameters and the set of ODD,
10 wherein the set of configuration parameters is received with the request.
[0018] Another aspect of the present disclosure may relate to a system for an installation and commissioning of a network node in a network. The system comprises an installation and commissioning system (IAC system). The IAC
15 system further comprises a transceiver unit configured to receive, a request for the
installation and the commissioning of the network node. The system further comprises a processing unit configured to automatically generate a set of Office Dependent Data (ODD) based on the request. The system further comprises an execution unit configured to perform a review action associated with the set of ODD
20 based on predefined ODD review rules. The system further comprises a detection
unit configured to detect a status associated with the set of ODD based on the review action. The status is one of a positive ODD status and a negative ODD status. The processing unit is further configured to generate a plurality of metadata based on the set of ODD and the positive ODD status. The system further comprises a
25 determination unit configured to determine a target configuration associated with
the request based on the metadata. The execution unit is further configured to trigger the installing and commissioning of the network node based on the target configuration.
6

[0019] Another aspect of the present disclosure may relate to a non-transitory
computer-readable storage medium storing instruction for an installation and
commissioning of a network node in a network, the storage medium comprising
executable code which, when executed by one or more units of a system, causes a
5 transceiver unit configured to receive, a request for the installation and the
commissioning of the network node. Further, the executable code, when executed causes a processing unit configured to automatically generate a set of Office Dependent Data (ODD) based on the request. Further, the executable code, when executed causes an execution unit configured to perform a review action associated
10 with the set of ODD based on predefined ODD review rules. Further, the executable
code, when executed causes a detection unit configured to detect a status associated with the set of ODD based on the review action. The status is one of a positive ODD status and a negative ODD status. Further, the executable code, when executed causes the processing unit to generate a plurality of metadata based on the set of
15 ODD and the positive ODD status. Further, the executable code, when executed
causes a determination unit configured to determine a target configuration associated with the request based on the metadata. Further, the executable code, when executed causes the execution unit to trigger the installing and commissioning of the network node based on the target configuration.
20
DESCRIPTION OF DRAWINGS
[0020] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
25 and systems in which like reference numerals refer to the same parts throughout the
different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated
30 by those skilled in the art that disclosure of such drawings includes disclosure of
7

electrical components, electronic components or circuitry commonly used to implement such components.
[0021] FIG. 1 illustrates an exemplary block diagram representation of a 5th
5 generation core (5GC) network architecture [100].
[0022] 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. 10
[0023] FIG. 3 illustrates an exemplary block diagram of a system [300] for installation and commissioning of a network node [320] in a network, in accordance with exemplary implementations of the present disclosure.
15 [0024] FIG. 4 illustrates an exemplary method [400] flow diagram for installation
and commissioning of a network node [320] in a network, in accordance with the exemplary embodiments of the present disclosure.
[0025] The foregoing shall be more apparent from the following more detailed
20 description of the disclosure.
DETAILED DESCRIPTION
[0026] In the following description, for the purposes of explanation, various
25 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 can each be used independently of one
another or with any combination of other features. An individual feature may not
30 address any of the problems discussed above or might address only some of the
8

problems discussed above. Some of the problems discussed above might not be
fully addressed by any of the features described herein. Example embodiments of
the present disclosure are described below, as illustrated in various drawings in
which like reference numerals refer to the same parts throughout the different
5 drawings.
[0027] 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
10 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.
15 [0028] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to
20 obscure the embodiments in unnecessary detail. In other instances, well-known
circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0029] Also, it is noted that individual embodiments may be described as a process
25 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 can be performed in parallel or
concurrently. In addition, the order of the operations may be re-arranged. A process
is terminated when its operations are completed but could have additional steps not
30 included in a FIG.
9

[0030] 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
5 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
10 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.
[0031] Further, the user device and/or a system as described herein to implement
15 technical features as disclosed in the present disclosure may also comprise
a “processor” or “processing unit”, wherein processor refers to any logic circuitry
for processing instructions. The processor may be a general-purpose processor, a
special purpose processor, a conventional processor, a digital signal processor, a
plurality of microprocessors, one or more microprocessors in association with a
20 Digital Signal Processor (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
25 processor is a hardware processor.
[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
30 medium includes read-only memory (“ROM”), random access memory (“RAM”),
magnetic disk storage media, optical storage media, flash memory devices or other
10

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.
5 [0033] 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,
10 Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
[0034] As used herein the transceiver unit includes at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals,
15 information or a combination thereof between units/components within the system
and/or connected with the system.
[0035] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above-
20 mentioned and other existing problems in this field of technology by providing a
method and a system of installation and commissioning of a network node in a
network.
[0036] Hereinafter, exemplary embodiments of the present disclosure will be
25 described in detail with reference to the accompanying drawings so that those
skilled in the art can easily carry out the present disclosure.
[0037] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture, in accordance with exemplary
30 implementation of the present disclosure. As shown in FIG. 1, the 5GC network
architecture [100] includes a user equipment (UE) [102], a radio access network
11

(RAN) [104], an access and mobility management function (AMF) [106], a Session
Management Function (SMF) [108], a Service Communication Proxy (SCP) [110],
an Authentication Server Function (AUSF) [112], a Network Slice Specific
Authentication and Authorization Function (NSSAAF) [114], a Network Slice
5 Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a
Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122],
a Unified Data Management (UDM) [124], an application function (AF) [126], a
User Plane Function (UPF) [128], a data network (DN) [130], wherein all the
components are assumed to be connected to each other in a manner as obvious to
10 the person skilled in the art for implementing features of the present disclosure.
[0038] The Radio Access Network (RAN) [104] is the part of a mobile
telecommunications system that connects the user equipment (UE) [102] to the core
network (CN) and provides access to different types of networks (e.g., 5G network).
15 It consists of radio base stations and the radio access technologies that enable
wireless communication.
[0039] The Access and Mobility Management Function (AMF) [106] is the 5G core
network function responsible for managing access and mobility aspects, such as UE
20 registration, connection, and reachability. It also handles mobility management
procedures like handovers and paging.
[0040] The Session Management Function (SMF) [108] is the 5G core network
function responsible for managing session-related aspects, such as establishing,
25 modifying, and releasing sessions. It coordinates with the User Plane Function
(UPF) [128] for data forwarding and handles IP address allocation and Quality of Service (QoS) enforcement. Further, the SMF [108] facilitates enforcement of session management related policy decisions from the PCF [122].
12

[0041] The Service Communication Proxy (SCP) [110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces. 5
[0042] The Authentication Server Function (AUSF) [112] is the network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
10 [0043] The Network Slice Specific Authentication and Authorization Function
(NSSAAF) [114] is the network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
15 [0044] The Network Slice Selection Function (NSSF) [116] is the network function
responsible for selecting the appropriate network slice for the UE based on factors such as subscription, requested services, and network policies.
[0045] The Network Exposure Function (NEF) [118] is the network function that
20 exposes capabilities and services of the 5G network to external applications,
enabling integration with third-party services and applications.
[0046] The Network Repository Function (NRF) [120] is the network function that
acts as a central repository for information about available network functions and
25 services. It facilitates the discovery and dynamic registration of network functions.
[0047] The Policy Control Function (PCF) [122] enables efficient policy control
and management, facilitating network behaviour control, network slicing, user
equipment (UE) activities, and communication with other 5G core
30 network functions. PCF is responsible for policy control decisions, such as QoS,
13

charging, and access control, based on subscriber information and network policies. The PCF is responsible for policy control decisions and flow-based charging control functionalities.
5 [0048] The Unified Data Management (UDM) [124] is the network function that
centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0049] The Application Function (AF) [126] is the network function that represents
10 external applications interfacing with the 5G core network to access network
capabilities and services. In an exemplary implementation, the application function
(AF) [126] as shown in FIG. 1, resembles an application server that can interact
with the other control-plane NFs. AF(s) [126] can exist for different application
services and can be owned by the network operator or by trusted third parties. For
15 instance, the AF [126] of an over-the-top application provider can influence routing,
steering its traffic towards its external edge servers. For services considered to be
trusted by the operator, the AF [126] can access Network Function(s) (NF) directly
whereas untrusted or third-party AF(s) [126] would access the Network Functions
through the NEF [118].
20
[0050] The User Plane Function (UPF) [128] is the network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
25 [0051] The Data Network (DN) [130] refers to a network that provides data
services to user equipment (UE) [102] in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
14

[0052] The present disclosure can be implemented on a computing device [200] as
shown in FIG. 2. The computing device [200] implements the present disclosure in
accordance with the 5G communication network architecture (as shown in FIG. 1).
FIG. 2 illustrates an exemplary block diagram of the computing device [200] upon
5 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 [400] for an installation and
commissioning of a network node [320] in a network utilising the system [300]. In
another implementation, the computing device [200] itself implements the method
10 [400] for the installation and the commissioning of the network node [320] in the
network 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.
15 [0053] 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-
20 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
25 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].
30
15

[0054] 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),
5 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
10 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.
15
[0055] 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.
20 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
25 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.
16

[0056] 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
5 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
10 implementation, the communication interface [218] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing various types of information.
[0057] The computing device [200] can send messages and receive data, including
15 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], the host [224] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received,
20 and/or stored in the storage device [210], or other non-volatile storage for later
execution.
[0058] The present disclosure is implemented by the system [300] (as shown in FIG. 3). The system [300] may be implemented using the computing device [200]
25 (as shown in FIG. 2). In an implementation, the computing device [200] may be
connected to the system [300] to perform the present disclosure. Referring to FIG. 3, an exemplary block diagram of the system [300] for installation and commissioning of a network node [320] in a network, is shown, in accordance with the exemplary implementations of the present disclosure. In general, a network
30 node may be construed as a connection point within a network where data is either
17

created, processed, or transmitted. The network node [320] here refers to
connection point(s) on the communication network that is capable of receiving,
processing and/or transmitting the information over the communication network.
For e.g., an Access and Mobility Function (AMF) [106] (as shown in FIG. 1) is the
5 network node for managing access and mobility aspects, such as UE registration,
connection, and reachability. It also handles mobility management procedures like handovers and paging within the 5G communication network. The system [300] comprises at least one installation and commissioning system (IAC system/ I&C system) [302]. The IAC system [302] further comprises at least one transceiver unit
10 [304]; at least one processing unit [306]; at least one execution unit [308]; at least
one detection unit [310] and at least one determination unit [312]. Also, all of the components/ units of the IAC system [302] inside the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the FIG. 3, all units shown within the system [300] should also be assumed to be connected
15 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 number of said units, as required to implement the features of the present disclosure. In an 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/
20 network entity.
[0059] The system [300] is configured for the installation and commissioning of
the network node [320] in the network, with the help of the interconnection between
the components/units of the system [300]. The installation of the network node
25 [320] includes planning the network layout, and configuring software to manage
the communication network and its security. The commissioning here refers to the process of checking, inspecting and testing every operational component of the communication network.
18

[0060] The transceiver unit [304] is configured to receive, a request for the installation and the commissioning of the network node [320].
[0061] Thereafter, the processing unit [306] of the system [300] automatically
5 generates a set of Office Dependent Data (ODD) based on the request. The ODD
refers to the information and configurations that are specific to the management,
operation, and maintenance of network node(s)/ network functions and
infrastructure of the network. This may include data related to network node
configuration, parameters, connections of the node with other entities, etc. and used
10 while installation of a network node.
[0062] In an exemplary aspect of the present disclosure, the ODD is generated in a
predefined format at the network node [320]. For e.g., at the network node [320]
(such as AMF [106]), the ODD is generated in original file extension for excel (XLS
15 format).
[0063] In an exemplary aspect of the present disclosure, the ODD is generated in the predefined format at the network node [320] via one or more macros. The predefined format being the XLS format that allows validation in fields in effective
20 way with the help of the one or more macros. Here, macros may refer to an action
or a set of actions that are used to automate repetitive tasks. The one or more macros helps to generate data in required format i.e., XLS by automating the generation of the ODD repetitively in the XLS format. The ODD captured in the XLS format enables a review or validation of the data in a simplified manner.
25
[0064] After the generation of the set of ODD, the execution unit [308] of the system [300] performs a review action associated with the set of ODD based on predefined ODD review rules. The review action involves evaluation and analysis of the ODD for ensuring accuracy, completeness and relevance required for
30 installation and commissioning of the network node [320]. In an implementation of
19

the present disclosure, the review action may be performed manually by the
network administrator or other authorised personnel in the office. In another
implementation of the present disclosure, the review action can be automated by
way of scripts that use programmable user logic. In another implementation, the
5 review action can be performed in a combined way, that is, manual review as well
as automated review combined as per the need. If there are any desired changes, the
execution unit [308] may update the data of the set of ODD based on the review
with the ODD. Thus, the review action may help in identifying the data suitability
for performing I&C of the network nodes.
10
[0065] Further, the detection unit [310] detects a status associated with the set of
ODD based on the review action. The status is one of a positive ODD status and a
negative ODD status. In an exemplary aspect of the present disclosure, the positive
ODD status is detected at the detection unit [310] in an event a successful response
15 associated with the review action is received at the detection unit [310]. The
successful response refers to an outcome of the review action indicating that the set
of ODD requires no changes pursuant to the review action. Therefore, upon
obtaining the positive ODD status, the installing and commission (I&C) can be
taken up.
20
[0066] Further, the processing unit [306] is configured to generate a plurality of
metadata based on the set of ODD and the positive ODD status. This means that in
case the ODD is valid and requires no changes pursuant to the review action, the
processing unit [306] will use the set of ODD to generate the metadata to further
25 processing to generate the actual data that can be used for installation and
commissioning of the network node. The metadata here refers to a set of essential details about the network node. For example, in case of AMF node, the metadata may comprise, but not limited to, data related to allowed PLMNs, equivalent PLMNs, MME logical information, MME physical information, etc.
30
20

[0067] Further, the determination unit [312] determines a target configuration
associated with the request based on the metadata. These details are determined
based on the details available related to the environment in which the network node
is installed, the configuration files and other files available for installation of the
5 network node. That is, the target configuration is determined further based on a set
of configuration parameters, wherein the set of configuration parameters may comprise data related to host name, network name, associated databases, interface ports, switch(es) and ports linked with the network node [320]. Furthermore, the execution unit [308] triggers the installing and commissioning of the network node
10 [320] based on the target configuration. Reiterating from above, the installation of
the network node [320] includes planning the network layouts and configuring software to manage the communication network and its security. The commissioning here refers to the process of checking, inspecting and testing every operational component of the network project.
15
[0068] In an exemplary aspect of the present disclosure, the execution unit [308] is further configured to perform a data update action associated with the set of ODD based on the negative ODD status. It is to be noted that the negative ODD status is detected at the detection unit [310] in an event an unsuccessful response associated
20 with the review action is received at the detection unit [310]. The unsuccessful
response refers to an outcome of the review action indicating that the set of ODD requires changes pursuant to the review action. Therefore, the negative ODD status calls for changes in the set of ODD before the installing and commission (I&C) is taken up. Further, the data update action refers to carrying out updates in the ODD
25 that results in the creation of the new record of the ODD.
[0069] Referring to FIG. 4, an exemplary method flow diagram [400] installation
and commissioning of a network node [320] in a network, in accordance with
exemplary implementations of the present disclosure is shown. In general, a
30 network node may be construed as a connection point within a network where data
is either created, processed, or transmitted. The network node [320] here refers to
21

connection point(s) on the communication network that is capable of receiving,
processing and/or transmitting the information over the communication network..
For e.g., an Access and Mobility Function (AMF) [106] (as shown in FIG. 1) is the
network node for managing access and mobility aspects, such as UE registration,
5 connection, and reachability. It also handles mobility management procedures like
handovers and paging within the 5G communication network. The installation of
the network node [320] includes planning the network layout and servers, and
configuring software to manage the communication network and its security. The
commissioning here refers to the process of checking, inspecting and testing every
10 operation component of the communication network. 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].
15 [0070] At step [404], the method [400] comprises receiving, by a transceiver unit
[304] at an installation and commissioning system [302] (IAC system), a request for the installation and commissioning of the network node [320].
[0071] At step [406], the method [400] comprises automatically generating, by a
20 processing unit [306] at the IAC system [302], a set of Office Dependent Data
(ODD) based on the request. The ODD refers to the information and configurations
that are specific to the management, operation, and maintenance of network
node(s)/ network functions and infrastructure of the network. This may include data
related to network node configuration, parameters, connections of the node with
25 other entities, etc. and used while installation of a network node.
[0072] In an exemplary aspect of the present disclosure, the ODD is generated in a
predefined format at the network node [320]. For e.g., at the network node [320]
(such as AMF [106]), the ODD is generated in original file extension for excel (XLS
30 format).
22

[0073] In an exemplary aspect of the present disclosure, the ODD is generated in
the predefined format at the network node [320] via one or more macros. The
predefined format being the XLS format that allows validation in fields in effective
5 way with the help of the one or more macros. Here, macros may refer to an action
or a set of actions that are used to automate repetitive tasks. The one or more macros helps to generate data in required format i.e., XLS by automating the generation of the ODD repetitively in the XLS format. The ODD captured in the XLS format enables a review or validation of the data in a simplified manner.
10
[0074] At step [408], the method [400] comprises performing, by an execution unit [308] at the IAC system [302], a review action associated with the set of ODD based on predefined ODD review rules. The review action involves evaluation and analysis of the ODD for ensuring accuracy, completeness and relevance required
15 for installation and commissioning of the network node [320]. In an implementation
of the present disclosure, the review action may be performed manually by the network administrator or other authorised personnel in the office. In another implementation of the present disclosure, the review action can be automated by way of scripts that use programmable user logic. In another implementation, the
20 review action can be performed in a combined way, that is, manual review as well
as automated review combined as per the need. If there are any desired changes, the execution unit [308] may update the data of the set of ODD based on the review with the ODD. Thus, the review action may help in identifying the data suitability for performing I&C of the network nodes.
25
[0075] At step [410], the method [400] comprises detecting, by a detection unit [310] at the IAC system [302], a status associated with the set of ODD based on the review action. The status can be one of a positive ODD status and a negative ODD status.
30
23

[0076] In an exemplary aspect of the present disclosure, the positive ODD status is
detected at the detection unit [310] in an event a successful response associated with
the review action is received at the detection unit [310]. The successful response
refers to an outcome of the review action indicating that the set of ODD requires no
5 changes pursuant to the review action. Therefore, upon obtaining the positive ODD
status, the installing and commission (I&C) can be taken up.
[0077] At step [412], the method [400] comprises generating, by the processing unit [306] at the IAC system [302], a plurality of metadata based on the set of ODD
10 and the positive ODD status. This means that in case the ODD is valid and requires
no changes pursuant to the review action, the processing unit [306] will use the set of ODD to generate the metadata to further processing to generate the actual data that can be used for installation and commissioning of the network node. The metadata here refers to a set of essential details about the network node. For
15 example, in case of AMF node, the metadata may comprise, but not limited to, data
related to allowed PLMNs, equivalent PLMNs, MME logical information, MME physical information, etc.
[0078] At step [414], the method [400] comprises determining, by a determination
20 unit [312] at the IAC system [302], a target configuration associated with the
request based on the metadata. These details are determined based on the details
available related to the environment in which the network node is installed, the
configuration files and other files available for installation of the network node.
That is, the target configuration is determined further based on a set of configuration
25 parameters, wherein the set of configuration parameters may comprise data related
to host name, network name, associated databases, interface ports, switch(es) and
ports linked with the network node [320].
[0079] At step [416], the method [400] comprises triggering, by the execution unit
30 [308], the installing and commissioning of the network node [320] based on the
target configuration. Reiterating from above, the installation of the network node
24

[320] includes planning the network layouts and configuring software to manage the communication network and its security. The commissioning here refers to the process of checking, inspecting and testing every operational component of the network project. 5
[0080] In an exemplary aspect of the present disclosure, the method [400] further comprises performing, by the execution unit [308], a data update action associated with the set of ODD based on the negative ODD status. It is to be noted that the negative ODD status is detected at the detection unit [310] in an event an
10 unsuccessful response associated with the review action is received at the detection
unit [310]. The unsuccessful response refers to an outcome of the review action indicating that the set of ODD requires changes pursuant to the review action. Therefore, the negative ODD status calls for changes in the set of ODD before the installing and commission (I&C) is taken up. Further, the data update action refers
15 to carrying out updates in the set of ODD that results in the creation of the new
record of the set of ODD.
[0081] Thereafter, the method [400] terminates at step [418].
20 [0082] The present disclosure further discloses a non-transitory computer-readable
storage medium storing instruction for an installation and commissioning of a network node [320] in a network, the storage medium comprising executable code which, when executed by one or more units of a system [300], causes a transceiver unit [304] to receive, a request for the installation and the commissioning of the
25 network node [320]. Further, the executable code, when executed causes the
transceiver unit [304] to receive a plurality of metadata based on the request. Further, the executable code, when executed causes a processing unit [306] to automatically generate a set of Office Dependent Data (ODD) based on the plurality of metadata. Further, the executable code, when executed causes an execution unit
30 [308] to perform a review action associated with the set of ODD based on
25

predefined ODD review rules. Further, the executable code, when executed causes a detection unit [310] to detect a status associated with the set of ODD based on the review action. The status is one of a positive ODD status and a negative ODD status. Further, the executable code, when executed causes a determination unit [312] to determine a target configuration associated with the request based on the metadata. Further, the executable code, when executed causes the execution unit [308] to trigger the installing and commissioning of the network node [320] based on the target configuration.
[0083] 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 encompassed within the scope of the present disclosure.
[0084] As is evident from the above, the present disclosure provides a technically advanced solution for installation and commissioning of the network node [320] in the communication network with desired configuration based on the automatically generated ODD. The present disclosure has the following advantages:
1. Ease of automated ODD preparation & review action that avoids possible operational installation and commissioning failures, therefore saving time and effort.
2. A speedy installation and commissioning for the network function (NF) across multiple sites by the required team.

3. Ease of ODD data review action enables an accurate commissioning of the network node [320] and avoids repetitive work in case of incorrect ODD data.
[0085] 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.

We Claim:
1. A method [400] for installation and commissioning of a network node [320] in
a network, the method [400] comprising:
- receiving, by a transceiver unit [304] at an installation and commissioning system [302] (IAC system), a request for the installation and commissioning of the network node [320];
- automatically generating, by a processing unit [306] at the IAC system [302], a set of Office Dependent Data (ODD) based on the request;
- performing, by an execution unit [308] at the IAC system [302], a review action associated with the set of ODD based on predefined ODD review rules;
- detecting, by a detection unit [310] at the IAC system [302], a status associated with the set of ODD based on the review action, wherein the status is one of a positive ODD status and a negative ODD status;
- generating, by the processing unit [306] at the IAC system [302], a plurality of metadata based on the set of ODD and the positive ODD status;
- determining, by a determination unit [312] at the IAC system [302], a target configuration associated with the request based on the metadata; and
- triggering, by the execution unit [308], the installing and commissioning of the network node [320] based on the target configuration.

2. The method [400] as claimed in claim 1, wherein the ODD is generated in a predefined format at the network node [320].
3. The method [400] as claimed in claim 2, wherein the ODD is generated in the predefined format at the network node [320] via one or more macros.
4. The method [400] as claimed in claim 1, wherein the positive ODD status is detected at the detection unit [310] in an event a successful response associated with the review action is received at the detection unit [310].
5. The method [400] as claimed in claim 1, further comprises performing, by the execution unit [308], a data update action associated with the set of ODD based

on the negative ODD status, wherein the negative ODD status is detected at the detection unit [310] in an event an unsuccessful response associated with the review action is received at the detection unit [310].
6. The method [400] as claimed in claim 1, wherein the target configuration is determined further based on a set of configuration parameters and the set of ODD, wherein the set of configuration parameters is received with the request.
7. A system [300] for an installation and commissioning of a network node [320] in a network, the system [300] comprising an installation and commissioning system (IAC system) [302], the IAC system [302] further comprising:
- a transceiver unit [304] configured to:
• receive, a request for the installation and the commissioning of the
network node [320];
- a processing unit [306] connected to at least the transceiver unit [304], the
processing unit [306] configured to:
• automatically generate a set of Office Dependent Data (ODD) based on
the request;
- an execution unit [308] connected to at least the processing unit [306], the
execution unit [308] configured to:
• perform a review action associated with the set of ODD based on
predefined ODD review rules;
- a detection unit [310] connected to at least the execution unit [308], the
detection unit [310] configured to:
• detect a status associated with the set of ODD based on the review
action, wherein the status is one of a positive ODD status and a negative
ODD status;
wherein the processing unit [306] is further configured to generate a plurality of metadata based on the set of ODD and the positive ODD status; and
- a determination unit [312] connected to at least the detection unit [310], the
determination unit [312] configured to:

• determine a target configuration associated with the request based on the metadata, and
wherein the execution unit [308] is further configured to trigger the installing and commissioning of the network node [320] based on the target configuration.
8. The system [300] as claimed claim 7, wherein the ODD is generated in a predefined format at the network node [320].
9. The system [300] as claimed claim 8, wherein the ODD is generated in the predefined format at the network node [320] via one or more macros.
10. The system [300] as claimed in claim 7, wherein the positive ODD status is detected at the detection unit [310] in an event a successful response associated with the review action is received at the detection unit [310].
11. The system [300] as claimed in claim 7, wherein the execution unit [308] is further configured to perform a data update action associated with the set of ODD based on the negative ODD status, wherein the negative ODD status is detected at the detection unit [310] in an event an unsuccessful response associated with the review action is received at the detection unit [310].
12. The system [300] as claimed in claim 7, wherein the target configuration is determined further based on a set of configuration parameters and the set of ODD, wherein the set of configuration parameters is received with the request.