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 AUTOMATING DEPLOYMENT OF A 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 AUTOMATING DEPLOYMENT OF A NETWORK
FIELD OF DISCLOSURE
[0001] Embodiments of the present disclosure generally relates to field of telecommunication radio network deployment. More particularly, the present disclosure relates to methods and systems for automating deployment of 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 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. 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] In the deployment of a wireless communication network, multiple stake holders are involved at every stage of different milestones and in performing various tasks. This mechanism creates communication gap between various stake holders when manual communication is used for assignment of tasks to perform the respective task execution. It is

also difficult to monitor the tracking of deployment status of each radio product in a network, various tasks execution within SLA, and assignment of task to respective stakeholder etc.
[0005] Further, over the period of time, various solutions have been developed to improve the deployment of wireless communication networks. However, there are certain challenges with existing solutions. For instance, the existing solutions are generic and fail to monitor accurately all tasks and milestones of various stake holders during the deployment of the wireless communication network, and also the existing solutions do not provide an automation plan for deployment of an entire radio product network or wireless communication network.
[0006] Thus, there exists an imperative need in the art for providing automation plan to build process for radio product network deployment, which the present disclosure aims to address.
SUMMARY OF THE DISCLOSURE
[0007] 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.
[0008] An aspect of the present disclosure may relate to a method for automating deployment of a network. The method includes identifying, by an identification unit, a set of requirement parameters from a stored collection of digital survey forms data. Next, the method includes identifying, by the identification unit, a set of entities and a set of deployment stages required for the network deployment, based on the identified set of requirement parameters. Next, the method includes generating, by a processing unit, one or more sets of execution tasks, wherein each of the execution task from the one or more sets of execution tasks has a pre-defined service level agreement (SLA) and wherein a first set of execution tasks from the one or more sets of execution tasks is associated with a first deployment stage from the set of deployment stages. The method then, includes assigning, by the processing unit, the first set of execution tasks, to the one or more entities from the set of entities. Next, the method includes updating, by the processing unit, a status for each execution task from the first set of execution tasks, with a state associated with each of the execution task. Thereafter, the method includes sending, by a transceiver unit, an auto escalation notification to a target entity from the set of entities in an

event the pre-defined SLA is breached for at least one execution task from the first set of execution tasks.
[0009] In an exemplary aspect of the present disclosure, the method further describes, that the network is a 5G radio product network.
[0010] In an exemplary aspect of the present disclosure, the method further describes, that the set of entities comprises at least one of a set of stakeholders and a set of digital platforms and the set of deployment stages comprises at least one of a first deployment stage, a second deployment stage, a third deployment stage and a fourth deployment stage.
[0011] In an exemplary aspect of the present disclosure, the method further describes, that each of the deployment stage from the set of deployment stages, is performed successively in sequence, and wherein, the assignment of a set of execution tasks from the one or more sets of execution tasks associated with a successive deployment stage from the set of deployment stages, is performed at initiation of the successive deployment stage.
[0012] In an exemplary aspect of the present disclosure, the method further describes that, the collection of digital survey forms data comprises at least one of a planning survey, a technical site survey, and backhaul availability.
[0013] In an exemplary aspect of the present disclosure, the method further describes that, in response to assigning each execution task from the first set of execution tasks, an auto email notification is sent to each of the assigned one or more entities from the set of entities.
[0014] In an exemplary aspect of the present disclosure, the method further describes that, the state for each of the assigned execution tasks from the first set of execution tasks is at least one of new, in-progress, completed, rejected and re-assigned.
[0015] In an exemplary aspect of the present disclosure, the method further describes that, the status is updated periodically based on the state of each of the execution tasks from the first set of execution tasks.

[0016] In an exemplary aspect of the present disclosure, the method further describes, that, an auto email notification is sent to one or more entities from the set of entities in an event the pre-defined SLA is breached for one or more execution tasks from the first set of execution tasks.
[0017] In an exemplary aspect of the present disclosure, the method further describes that, the SLA breach event is detected, when a fault is identified with at least one of a quality and a timeline associated with the at least one execution task from the first set of execution tasks.
[0018] In an exemplary aspect of the present disclosure, the method further describes that, the first set of execution tasks associated with the first deployment stage comprises at least a nominal coverage generation and a nominal coverage validation.
[0019] In an exemplary aspect of the present disclosure, the method further describes that, a second set of execution tasks from the one or more sets of execution tasks associated with the second deployment stage comprises at least one or more site identification and scope release for the network deployment.
[0020] In an exemplary aspect of the present disclosure, the method further describes, that, a third set of execution tasks from the one or more sets of execution tasks associated with the third deployment stage comprises at least a planning survey, backhaul availability, technical site survey, commercial request and approval, local body no objection certificate clearance, ready for infra survey, equipment installation, small cell provisioning and Access and Mobility Function (AMF) provisioning.
[0021] In an exemplary aspect of the present disclosure, the method further describes that, a fourth set of execution tasks from the one or more sets of execution tasks associated with the fourth deployment stage comprises at least an agreement signing and uploading, rental and vendor billing, material movement, logical data upload, utilities, battery, gNodeB creation in Gi interface.
[0022] Another aspect of the present disclosure may relate to a system for automating deployment of a network. The system comprising an identification unit, the identification unit configured to: identify, a set of requirement parameters from a stored collection of digital

survey forms data, identify, a set of entities and a set of deployment stages required for the network deployment, based on the identified set of requirement parameters. The system further comprising a processing unit connected at least to the identification unit, the processing unit configured to: generate one or more sets of execution tasks, wherein each of the execution task from the one or more sets of execution tasks has a pre-defined service level agreement (SLA) and wherein a first set of execution tasks from the one or more sets of execution tasks is associated with a first deployment stage from the set of deployment stages, assign the first set of execution tasks, to the one or more entities from the set of entities, update a status for each execution task from the first set of execution tasks, with a state associated with each of the execution task. The system furthermore comprising a transceiver unit connected at least to the processing unit, the transceiver unit configured to sending an auto escalation notification to a target entity from the set of entities in an event the pre-defined SLA is breached for at least one execution task from the first set of execution tasks.
[0023] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for automating deployment of a network, the instructions include executable code which, when executed by a one or more units of a system, causes: identifying, by an identification unit, a set of requirement parameters from a stored collection of digital survey forms data; identifying, by the identification unit, a set of entities and a set of deployment stages required for the network deployment, based on the identified set of requirement parameters; generating, by a processing unit, one or more sets of execution tasks, wherein each of the execution task from the one or more sets of execution tasks has a pre-defined service level agreement (SLA) and wherein a first set of execution tasks from the one or more sets of execution tasks is associated with a first deployment stage from the set of deployment stages; assigning, by the processing unit, the first set of execution tasks, to the one or more entities from the set of entities; updating, by the processing unit, a status for each execution task from the first set of execution tasks, with a state associated with each of the execution task; sending, by a transceiver unit, an auto escalation notification to a target entity from the set of entities in an event the pre-defined SLA is breached for at least one execution task from the first set of execution tasks.
[0024] Yet another aspect of the present disclosure may relate to a user equipment (UE) for automating deployment of a network, the UE comprising a system, wherein the system comprises an identification unit, the identification unit configured to: identify, a set of

requirement parameters from a stored collection of digital survey forms data, identify, a set of entities and a set of deployment stages required for the network deployment, based on the identified set of requirement parameters; a processing unit connected at least to the identification unit, the processing unit configured to generate one or more sets of execution tasks, wherein each of the execution task from the one or more sets of execution tasks has a pre-defined service level agreement (SLA) and wherein a first set of execution tasks from the one or more sets of execution tasks is associated with a first deployment stage from the set of deployment stages, assign the first set of execution tasks, to the one or more entities from the set of entities, update a status for each execution task from the first set of execution tasks, with a state associated with each of the execution task; a transceiver unit connected at least to the processing unit, the transceiver unit configured to sending an auto escalation notification to a target entity from the set of entities in an event the pre-defined SLA is breached for at least one execution task from the first set of execution tasks.
OBJECTS OF THE DISCLOSURE
[0025] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0026] It is an object of the present disclosure to provide a system and a method for providing automation plan to build process for radio product network deployment.
[0027] It is another object of the present disclosure to provide a solution that can take into consideration all tasks and milestones of various stake holders that may be required during the deployment of the wireless communication network to provide an automation plan for building a process of the deployment of the wireless communication network.
[0028] It is yet another object of the present disclosure to provide a solution that is able to create an abstraction layer between network providers and rollout management and operations, thereby leading to faster adaptability to specific requirements such as massive capacity, infinitesimal latency, supreme reliability, personalized customer experience, etc.
[0029] It is yet another object of the present disclosure to provide a solution that can send auto email notifications to respective task executors and auto escalation email to a stakeholder, for

example to a L1 person who is the key responsible person, in case the task is not executed within the SLA.
[0030] It is yet another object of the present disclosure to provide a solution that can fully automate a mass rollout of new sites during deployment of a wireless communication network, thereby not only enhancing the customer experience but also increasing the engineering efficiency.
DESCRIPTION OF THE DRAWINGS
[0031] 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.
[0032] FIG. 1 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0033] FIG. 2 illustrates an exemplary block diagram of a system for automating deployment of a network, in accordance with exemplary implementations of the present disclosure.
[0034] FIG. 3 illustrates a method flow diagram for automating deployment of a network in accordance with exemplary implementations of the present disclosure.
[0035] FIG. 4 illustrates an exemplary block diagram for automating deployment of a network in accordance with exemplary implementations of the present disclosure.

[0036] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
5 [0037] 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
10 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.
[0038] The ensuing description provides exemplary embodiments only, and is not intended to 15 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. 20
[0039] 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 25 diagram form in order not to obscure the embodiments in unnecessary detail.
[0040] 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 30 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.
9

[0041] 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
5 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
10 other elements.
[0042] 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
15 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
20 working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[0043] 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
25 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
30 implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
10

[0044] 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 5 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.
[0045] As used herein “interface” or “user interface refers to a shared boundary across which 10 two or more separate components of a system exchange information or data. The interface may also be referred 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.
15 [0046] All modules, units, components used herein, unless explicitly excluded, 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
20 Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0047] 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 25 system.
[0048] Furthermore, a telecommunication radio network deployment plays an important role in providing efficient and effective data and voice related services to users of a wireless network operator. A radio network deployment involves multiple stages of work to finally get 30 the radio network installed. These stages involve, a large variety of different aspects to be considered, e.g., characteristics of the application and communication services requiring wireless connectivity, the overall business case, spectrum regulations, characteristics of the industrial site, and so on. Moreover, the radio network deployment is a crucial activity to address continuous increase on capacity and coverage demands on mobile networks. By fully
11

automating the mass rollout of new sites, it not only enhances customer experience, but also provides increased engineering efficiency. Being able to create an abstraction layer between network providers and rollout management and operations, may empower faster adaptability to specific requirements such as massive capacity, infinitesimal latency, supreme reliability, 5 personalized customer experience, etc.
[0049] As discussed in the background section, the current known solutions for network deployment are generic and fail to monitor accurately all tasks and milestones of various stake holders during the deployment of the wireless communication network, and also the existing 10 solutions do not provide an automation plan for deployment of an entire radio product network or wireless communication network.
[0050] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system for automating
15 deployment of a network such as radio product network or the wireless communication network. The automation of plan to build process as provided by the present disclosure provides the end-to-end module for entire network such as 5G radio plan to build process on where the various radio deployment tasks are auto assigned to each stakeholder/user with system/automatically generated email notification. Also, basis the implementation of the
20 features of the present disclosure, the stakeholders may execute the task on a digital platform, subsequent tasks and milestone are assigned automatically to respective stakeholders with notification, and if any of the task is not matching with the pre-defined SLA, an auto escalation email may be triggered to L1 and L2 levels of responsible persons. The entire life cycle of the radio network products is also monitored with customized user-friendly and user defined
25 dashboard, based on the implementation of features of the present disclosure.
[0051] FIG. 1 illustrates an exemplary block diagram of a computing device [1000] 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 [1000] 30 may also implement a method for automating deployment of a network utilising the system. In another implementation, the computing device [1000] itself implements the method for automating deployment of a network using one or more units configured within the computing device [1000], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
12

[0052] The computing device [1000] may include a bus [1002] or other communication mechanism for communicating information, and a hardware processor [1004] coupled with bus [1002] for processing information. The hardware processor [1004] may be, for example, a
5 general-purpose microprocessor. The computing device [1000] may also include a main memory [1006], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [1002] for storing information and instructions to be executed by the processor [1004]. The main memory [1006] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the
10 processor [1004]. Such instructions, when stored in non-transitory storage media accessible to the processor [1004], render the computing device [1000] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [1000] further includes a read only memory (ROM) [1008] or other static storage device coupled to the bus [1002] for storing static information and instructions for the processor
15 [1004].
[0053] A storage device [1010], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [1002] for storing information and instructions. The computing device [1000] may be coupled via the bus [1002] to a display [1012], such as a cathode ray
20 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 [1014], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [1002] for communicating information and command selections to the processor [1004]. Another type of user input device may be a cursor controller [1016], such as a mouse, a
25 trackball, or cursor direction keys, for communicating direction information and command selections to the processor [1004], and for controlling cursor movement on the display [1012]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
30 [0054] The computing device [1000] 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 [1000] causes or programs the computing device [1000] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [1000] in response to the processor
13

[1004] executing one or more sequences of one or more instructions contained in the main memory [1006]. Such instructions may be read into the main memory [1006] from another storage medium, such as the storage device [1010]. Execution of the sequences of instructions contained in the main memory [1006] causes the processor [1004] to perform the process steps 5 described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[0055] The computing device [1000] also may include a communication interface [1018] coupled to the bus [1002]. The communication interface [1018] provides a two-way data
10 communication coupling to a network link [1020] that is connected to a local network [1022]. For example, the communication interface [1018] 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 [1018] may be a local area network (LAN) card to provide a data communication
15 connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [1018] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
20 [0056] The computing device [1000] can send messages and receive data, including program code, through the network(s), the network link [1020] and the communication interface [1018]. In the Internet example, a server [1030] might transmit a requested code for an application program through the Internet [1028], the ISP [1026], the Host [1024], the local network [1022] and the communication interface [1018]. The received code may be executed by the processor
25 [1004] as it is received, and/or stored in the storage device [1010], or other non-volatile storage for later execution.
[0057] Referring to FIG. 2, an exemplary block diagram of a system [200] for automating deployment of a network, is shown, in accordance with the exemplary implementations of the 30 present disclosure. The system [200] comprises at least one identification unit [202], at least one at processing unit [204], least one transceiver unit [206] and at least one storage unit [208]. Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system [200] should also be assumed to be connected to each other. Also, in FIG. 2 only a few
14

units are shown, however, the system [200] may comprise multiple such units or the system [200] may comprise any such number of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [200] may be present in a user device/ computing device [1000] to implement the features of the present disclosure. The 5 system [200] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation, the system [200] may reside in a server or a network entity. In yet another implementation, the system [200] may reside partly in the server/ network entity and partly in the user device.
10 [0058] The system [200] is configured for automating deployment of a network, with the help of the interconnection between the components/units of the system [200]. The system [200] is configured for providing automation plan to build process for radio product network deployment, with the help of the interconnection between the components/units of the system [200]. In an exemplary aspect, the network is a 5G radio product network. In an exemplary
15 aspect, the network may be such as, but not limited to, 4G, 6G radio product network and the like. In an exemplary aspect, the network may be such as a mobile network.
[0059] The system [200] comprises an identification unit [202]. The identification unit [202] is configured to identify, a set of requirement parameters from a stored collection of digital
20 survey forms data in a storage unit [208], and further identify, a set of entities and a set of deployment stages required for the network deployment, based on the identified set of requirement parameters. The identification unit [202] of the system [200] may identify the set of requirement parameters from the stored collection of digital survey forms data in the storage unit [208]. In order to deploy 5G radio product network (such as RAN product) for new or
25 existing sites, identification unit [202] may identify the set of requirement parameters such as but not limited to, site/location details, height and azimuth of radio tower, backhaul to be used, etc. from the stored collection of digital survey form data in the storage unit [208]. In an exemplary aspect, the stored collection of digital survey forms data in the storage unit [208] comprises at least one of a planning survey, a technical site survey, and backhaul availability.
30 The digital survey may be done for location specific, service demand specific and user experience specific requirement(s) for new or existing site(s). The planning survey may involve collecting details about a site/location where the radio network tower needs to be installed or deployed. The technical site survey may involve identifying the height and azimuth. It may also involve taking 360-degree photographs of the site to identify the neighbouring
15

environment and location layout. The backhaul availability survey may involve identifying a wireless backhaul such as using fibre optic or microwave. The requirement parameters derived from these survey forms may include, the details about the location/site identified, height and azimuth of the radio tower, what backhaul to be used, etc.
5 [0060] Further, the identification unit [202] of the system [200] may identify the set of entities and a set of deployment stages required for the network deployment based on the identified set of requirement parameters. In an exemplary aspect, the set of entities comprises at least one of a set of stakeholders and a set of digital platforms. The set of deployment stages comprises at
10 least one of a first deployment stage, a second deployment stage, a third deployment stage and a fourth deployment stage based on the identified set of requirement parameters. In an exemplary aspect, each of the deployment stage from the set of deployment stages, is performed successively in sequence, and wherein, the assignment of a set of execution tasks from the one or more sets of execution tasks associated with a successive deployment stage
15 from the set of deployment stages, is performed at initiation of the successive deployment stage. In an exemplary aspect, the processing unit [204] may process from the first deployment stage to fourth deployment stage via executing associated related task(s) in sequence manner.
[0061] In an exemplary aspect, the digital platform may be a centralised platform, which is 20 accessible by a mobile or web portal. The digital platform syncs all details for mobile and web portal in real-time. In an exemplary aspect, the digital platform may be of a network service provider and vendor.
[0062] The identification unit [202] may send the identified set of entities and the set of 25 deployment stages required for the network deployment based on the identified set of requirement parameters to a processing unit [204] of the system [200] for further processing.
[0063] The processing unit [204] of the system [200] is connected at least to the identification unit [202]. The processing unit [204] is configured to generate one or more sets of execution 30 tasks, wherein each of the execution task from the one or more sets of execution tasks has a pre-defined service level agreement (SLA) and wherein a first set of execution tasks from the one or more sets of execution tasks is associated with a first deployment stage from the set of deployment stages.
16

[0064] The pre-defined SLA may have, such as, but not limited to, information for agreed and predefined condition(s) or order(s) for execution of the set of tasks, stakeholder details and access level of authorised user(s) for executing task(s) and taking action(s).
5 [0065] The processing unit [204] is further configured to assign the first set of execution tasks, to the one or more entities from the set of entities, such as at least one of the set of stakeholders and the set of digital platforms. In an exemplary aspect, the first set of execution tasks associated with the first deployment stage comprises at least a nominal coverage generation and a nominal coverage validation. Here, nominal refers to the tentative site where the radio
10 tower needs to be installed. The nominal coverage generation may include generation of a prediction about the coverage footprint. Further, the nominal coverage validation may include generation of a prediction that how the tentative site will provide the coverage.
[0066] The processing unit [204], is further configured to update a status for each execution 15 task from the first set of execution tasks, on a management view dashboard, with a state associated with each of the execution task. In an exemplary aspect, status for each of the assigned execution tasks from the first set of execution tasks is at least one of new, in-progress, completed, rejected and re-assigned. A new status is assigned to a task along with the task assignment. When the task is being executed and it is work in progress for the task, then an in-20 progress status is assigned. When the task gets completed and is handed over, the status is updated to completed. If, because of SLA breach, the task is rejected by the key person responsible, the status is updated to rejected. When the rejected task is again assigned to an entity, the status is updated to re-assigned. Further, the status is updated periodically by the processing unit [204], based on the state of each of the execution tasks from the first set of 25 execution tasks.
[0067] The system [200] further comprises a transceiver unit [206] connected at least to the processing unit [204]. The transceiver unit [206] is configured for sending an auto escalation notification to a target entity from the set of entities in an event the pre-defined SLA is breached 30 for at least one execution task from the first set of execution tasks. The SLA breach event is detected, when a fault is identified with a timeline associated with the at least one execution task from the first set of execution tasks. If an assigned task is not completed within the timeline as specified in the SLA, then the SLA breach event is detected, which is escalated to a key responsible person by an escalation notification. The SLA breach event is detected by
17

processing unit [204] and shared with the transceiver unit [206] for taking further action such as sending a notification. The target entity who receives the auto escalation notification is the key responsible person who oversees the network deployment.
5 [0068] In an exemplary aspect, the transceiver unit [206] is further configured to send an auto email notification to each of the assigned one or more entities from the set of entities, in response to assigning each execution task from the first set of execution tasks.
[0069] In an exemplary aspect, the first set of execution tasks associated with the first 10 deployment stage comprises at least a nominal coverage generation and a nominal coverage validation. Here, nominal refers to the tentative site where the radio tower needs to be installed. The nominal coverage generation may include generation of a prediction about the coverage footprint. Further, the nominal coverage validation may include generation of a prediction that how the tentative site will provide the coverage. 15
[0070] In an exemplary aspect, the second set of execution tasks from the one or more sets of execution tasks associated with the second deployment stage comprises at least one or more site identification and scope release for the network deployment. In this stage, the tentative site is identified and a plan detailing the radio tower deployment at the tentative site is released. 20 This plan covers the end-to-end life cycle of the radio tower deployment.
[0071] In an exemplary aspect, the third set of execution tasks from the one or more sets of execution tasks associated with the third deployment stage comprises at least a planning survey, backhaul availability, technical site survey, commercial request and approval, local body no
25 objection certificate clearance, ready for infra survey, equipment installation, and Access and Mobility Function (AMF) provisioning. The planning survey may involve collecting details about a site/location where the radio network tower needs to be installed or deployed. The technical site survey may involve identifying the height and azimuth. It may also involve taking 360-degree photographs of the site to identify the neighbouring environment and location
30 layout. The backhaul availability survey may involve identifying a wireless backhaul such as using fibre optic or microwave. The requirement parameters derived from these survey forms may include the details about the location/site identified, height and azimuth of the radio tower, what backhaul to be used, etc. Further, based on the identified site and whether it is a commercial site or a private site, required permissions in the form of rent agreement or a tie up
18

with the private owner is sought. Next, a permission from the local governing body, like a municipal corporation, is to be taken in the form of no objection clearance. Once, the clearance is granted by the local governing body, an infra survey is conducted. The infra survey involves, testing of the soil at the site and the testing of the building where the radio tower needs to be 5 installed. The soil is tested to check if it can hold and handle the tower. Finally, once all these surveys and tests are conducted, the next task is to install the tower and provision the Access and Mobility Function (AMF) which is the core of 5G network to which the RAN will connect to provide services to users.
10 [0072] In an exemplary aspect, the fourth set of execution tasks from the one or more sets of execution tasks associated with the fourth deployment stage comprises at least an agreement signing and uploading, rental and vendor billing, material movement, logical data upload, utilities, battery, gNodeB creation in Gi interface. Once the tower is installed at the identified site, the final tasks involve signing an agreement with local governing body and the owner of
15 the site. The agreement is uploaded and stored in the storage unit [208]. All the other data, related to tools, utilities, battery are also uploaded and stored in the storage unit [208]. Finally, the base station (gNodeB) is created and Gi interface is established to complete the setup of the radio tower to provide wireless connectivity.
20 [0073] In an exemplary aspect, as used herein, number of deployment stages are not restricted to any number, it may customizable based on network deployment stages and plans. Further, the functioning of the deployment stages are not restricted to any single stage. It may be performed in any combination of stages separately or in combination of the stages.
25 [0074] It should be noted that the terms "first", "second", “third”, “fourth”, and the like, herein do not denote any order, ranking, quantity, or importance, but rather are used to distinguish one stage from another.
[0075] Referring to FIG. 3, an exemplary method flow diagram [300] for automating 30 deployment of a network, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [300] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement the features of the present disclosure. Also, as shown in Figure 3, the method [300] starts at step [302].
19

[0076] At step [304], the method [300] as disclosed by the present disclosure, comprises identifying, by an identification unit [202], a set of requirement parameters from a stored collection of digital survey forms data. The method [300] implemented by the identification
5 unit [202] of the system [200] may identify the set of requirement parameters from the stored collection of digital survey forms data in a storage unit [208]. In order to deploy 5G radio product network (such as RAN product) for new or existing sites, identification unit [202] may identify the set of requirement parameters such as but not limited to, site/location details, height and azimuth of radio tower, backhaul to be used, etc. from the stored collection of digital
10 surveys form data in the storage unit [208]. In an exemplary aspect, the stored collection of digital survey forms data in the storage unit [208[, comprises at least one of a planning survey, a technical site survey, and backhaul availability. The digital survey may be done for location specific, service demand specific and user experience specific requirement(s) for new or existing site(s). The planning survey may involve collecting details about a site/location where
15 the radio network tower needs to be installed or deployed. The technical site survey may involve identifying the height and azimuth. It may also involve taking 360-degree photographs of the site to identify the neighbouring environment and location layout. The backhaul availability survey may involve identifying a wireless backhaul such as using fibre optic or microwave. The requirement parameters derived from these survey forms may include, the
20 details about the location/site identified, height and azimuth of the radio tower, what backhaul to be used, etc.
[0077] Next, at step [306], the method [300] as disclosed by the present disclosure comprises identifying, by the identification unit [202], a set of entities and a set of deployment stages
25 required for the network deployment, based on the identified set of requirement parameters. In an exemplary aspect, the set of entities comprises at least one of a set of stakeholders and a set of digital platforms. The set of deployment stages comprises at least one of a first deployment stage, a second deployment stage, a third deployment stage and a fourth deployment stage based on the identified set of requirement parameters.
30
[0078] In an exemplary aspect, each of the deployment stage from the set of deployment stages, is performed successively in sequence, and wherein, the assignment of a set of execution tasks from the one or more sets of execution tasks associated with a successive deployment stage from the set of deployment stages, is performed at initiation of the successive deployment
20

stage. In an exemplary aspect, the processing unit [204] may process from the first deployment stage to fourth deployment stage via executing associated related task(s) in a sequenced manner.
5 [0079] In an exemplary aspect, the digital platform may be a centralised platform, which is accessible by a mobile or web portal. The digital platform syncs all details for mobile and web portal in real-time. In an exemplary aspect, the digital platform may be of a network service provider and vendor. The identification unit [202] may send the identified set of entities and the set of deployment stages required for the network deployment based on the identified set
10 of requirement parameters to a processing unit [204] for further processing.
[0080] In an exemplary aspect, the network is a 5G radio product network. In an exemplary aspect, the network may be such as, but not limited to, 4G, 6G radio product network and the like. In an exemplary aspect, the network may be such as a mobile network.
15
[0081] Next, at step [308], the method [300] as disclosed by the present disclosure comprises generating, by the processing unit [204], one or more sets of execution tasks, wherein each of the execution task from the one or more sets of execution tasks has a pre-defined service level agreement (SLA) and wherein a first set of execution tasks from the one or more sets of
20 execution tasks is associated with a first deployment stage from the set of deployment stages. In an exemplary aspect, the first set of execution tasks associated with the first deployment stage comprises at least a nominal coverage generation and a nominal coverage validation. Here, nominal refers to the tentative site where the radio tower needs to be installed. The nominal coverage generation may include generation of a prediction about the coverage
25 footprint. Further, the nominal coverage validation may include generation of a prediction that how the tentative site will provide the coverage.
[0082] The pre-defined SLA may have such as, but not limited to, information for agreed and predefined condition(s) or order(s) for execution of the set of tasks, stakeholder details and 30 access level of authorised user(s) for executing task(s) and taking action(s).
[0083] The processing unit [204] is further configured to assign the first set of execution tasks, to the one or more entities from the set of entities, such as at least one of the set of stakeholders and the set of digital platforms. The processing unit [204], is further configured to update a
21

status for each execution task from the first set of execution tasks, on a management view dashboard, with a state associated with each of the execution task. In an exemplary aspect, status for each of the assigned execution tasks from the first set of execution tasks is at least one of new, in-progress, completed, rejected and re-assigned. A new status is assigned to a task
5 along with the task assignment. When the task is being executed and it is work in progress for the task, then an in-progress status is assigned. When the task gets completed and is handed over, the status is updated to completed. If, because of SLA breach, the task is rejected by the key person responsible, the status is updated to rejected. When the rejected task is again assigned to an entity, the status is updated to re-assigned. Further, the status is updated
10 periodically by the processing unit [204], based on the state of each of the execution tasks from the first set of execution tasks.
[0084] Next, at step [310], the method [300] as disclosed by the present disclosure comprises assigning, by the processing unit [204], the first set of execution tasks, to the one or more 15 entities from the set of entities. Further, the processing unit [204] may assign the first set of execution tasks, to the one or more entities from the set of entities. In an exemplary aspect, the one or more entities comprises at least one of the set of stakeholders and the set of digital platforms.
20 [0085] In an exemplary aspect, the first set of execution tasks associated with the first deployment stage comprises at least a nominal coverage generation and a nominal coverage validation.
[0086] Next, at step [312], the method [300] as disclosed by the present disclosure comprises 25 updating, by the processing unit [204], a status for each execution task from the first set of execution tasks, on a management view dashboard, with a state associated with each of the execution task. The method [300] implemented by the processing unit [204] may update the status for each execution task from the first set of execution tasks, on a management view dashboard, with a state associated with each of the execution task. In an exemplary aspect, 30 status for each of the assigned execution tasks from the first set of execution tasks is at least one of new, in-progress, completed, rejected and re-assigned. A new status is assigned to a task along with the task assignment. When the task is being executed and it is work in progress for the task, then an in-progress status is assigned. When the task gets completed and is handed over, the status is updated to completed. If, because of SLA breach, the task is rejected by the
22

key person responsible, the status is updated to rejected. When the rejected task is again assigned to an entity, the status is updated to re-assigned. Further, the status is updated periodically by the processing unit [204], based on the state of each of the execution tasks from the first set of execution tasks.
5 [0087] Next, at step [314], the method [300] as disclosed by the present disclosure comprises sending, by a transceiver unit [206], an auto escalation notification to a target entity from the set of entities in an event the pre-defined SLA is breached for at least one execution task from the first set of execution tasks. The SLA breach event is detected, when a fault is identified
10 with a timeline associated with the at least one execution task from the first set of execution tasks. If an assigned task is not completed within the timeline as specified in the SLA, then the SLA breach event is detected, which is escalated to a key responsible person by an escalation notification. The SLA breach event is detected by processing unit [204] and shared with the transceiver unit [206] for taking further action such as sending a notification. The target entity
15 who receives the auto escalation notification in an event of SLA breach is the key responsible person who oversees the network deployment.
[0088] In an exemplary aspect, the transceiver unit [206] is further configured to send an auto email notification to each of the assigned one or more entities from the set of entities, in 20 response to assigning each execution task from the first set of execution tasks.
[0089] Thereafter, the method [300] terminates at step [316].
[0090] FIG. 4 illustrates a block diagram [400] for automating deployment of a network in 25 accordance with exemplary implementations of the present disclosure. As shown in FIG. 4, the block diagram [400] comprises a first deployment stage [402], a second deployment stage [404], a third deployment stage [406] and fourth deployment stage [408].
[0091] First deployment stage [402] comprises at least a nominal coverage generation and a 30 nominal coverage validation. In an exemplary aspect, the first set of execution tasks associated with the first deployment stage comprises at least a nominal coverage generation and a nominal coverage validation. Here, nominal refers to the tentative site where the radio tower needs to be installed. The nominal coverage generation may include generation of a prediction about
23

the coverage footprint. Further, the nominal coverage validation may include generation of a prediction that how the tentative site will provide the coverage.
[0092] Further, the second deployment stage [404] comprises at least one or more site 5 identification and scope release for the network deployment. In this stage, the tentative site is identified and a plan detailing the radio tower deployment at the tentative site is released. This plan covers the end-to-end life cycle of the radio tower deployment.
[0093] Further, the third deployment stage [406] comprises at least a planning survey, backhaul 10 availability, technical site survey, commercial request and approval, local body no objection certificate clearance, ready for infra survey, equipment installation, and Access and Mobility Function (AMF) provisioning. The planning survey may involve collecting details about a site/location where the radio network tower needs to be installed or deployed. The technical site survey may involve identifying the height and azimuth. It may also involve taking 360-15 degree photographs of the site to identify the neighbouring environment and location layout. The backhaul availability survey may involve identifying a wireless backhaul such as using fibre optic or microwave. The requirement parameters derived from these survey forms may include the details about the location/site identified, height and azimuth of the radio tower, what backhaul to be used, etc. Further, based on the identified site and whether it is a 20 commercial site or a private site, required permissions in the form of rent agreement or a tie up with the private owner is sought. Next, a permission from the local governing body, like a municipal corporation, is to be taken in the form of no objection clearance. Once, the clearance is granted by the local governing body, an infra survey is conducted. The infra survey involves, testing of the soil at the site and the testing of the building where the radio tower needs to be 25 installed. The soil is tested to check if it can hold and handle the tower. Finally, once all these surveys and tests are conducted, the next task is to install the tower and provision the Access and Mobility Function (AMF) which is the core network to which the RAN will connect to provide services to users.
30 [0094] Furthermore, the fourth deployment stage [408] comprises at least an agreement signing and uploading, rental and vendor billing, material movement, logical data upload, utilities, battery, gNodeB creation in Gi interface. Once the tower is installed at the identified site, the final tasks involve signing an agreement with local governing body and the owner of the site. The agreement is uploaded and stored in the storage unit [208]. All the other data related to
24

tools, utilities, battery are also uploaded and stored in the storage unit [208]. Finally, the base station (gNodeB) is created and Gi interface is established to complete the setup of the radio tower to provide wireless connectivity.
5 [0095] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for automating deployment of a network, the instructions include executable code which, when executed by a one or more units of a system [200], causes: an identification unit [202] of the system [200] to identify a set of requirement parameters from a stored collection of digital survey forms data in a storage unit [208]; the identification unit
10 [202] of the system [200] to identify a set of entities and a set of deployment stages required for the network deployment, based on the identified set of requirement parameters; a processing unit [204] of the system [200] to generate one or more sets of execution tasks, wherein each of the execution task from the one or more sets of execution tasks has a pre-defined service level agreement (SLA) and wherein a first set of execution tasks from the one or more sets of
15 execution tasks is associated with a first deployment stage from the set of deployment stages; the processing unit [204] of the system [200] to assign the first set of execution tasks, to the one or more entities from the set of entities; the processing unit [204] of the system [200] to update a status for each execution task from the first set of execution tasks, on a management view dashboard, with a state associated with each of the execution task; a transceiver unit [206]
20 of the system [200] to send an auto escalation notification to a target entity from the set of entities in an event the pre-defined SLA is breached for at least one execution task from the first set of execution tasks.
[0096] Yet another aspect of the present disclosure may relate to a user equipment (UE) that 25 comprises: an identification unit [202] of the system [200] configured to identify a set of requirement parameters from a stored collection of digital survey forms data in the storage unit [208]. The identification unit [202] further configured to identify a set of entities and a set of deployment stages required for the network deployment, based on the identified set of requirement parameters. A processing unit [204] of the system [200] configured to generate 30 one or more sets of execution tasks, wherein each of the execution task from the one or more sets of execution tasks has a pre-defined service level agreement (SLA) and wherein a first set of execution tasks from the one or more sets of execution tasks is associated with a first deployment stage from the set of deployment stages. The processing unit [204] of the system further configured to assign the first set of execution tasks, to the one or more entities from the
25

set of entities; the processing unit [204] of the system [200] to update a status for each execution task from the first set of execution tasks, on a management view dashboard, with a state associated with each of the execution task. A transceiver unit [206] of the system [200] configured to send an auto escalation notification to a target entity from the set of entities in an 5 event the pre-defined SLA is breached for at least one execution task from the first set of execution tasks.
[0097] As is evident from the above, the present disclosure provides a technically advanced solution for providing automation plan to build a process for radio product network
10 deployment. By fully automating the mass rollout of new sites, it not only enhances customer experience but also increases engineering efficiency. The present disclosure enables creation of an abstraction layer between network providers and rollout management and operations, which empowers faster adaptability to specific requirements such as massive capacity, infinitesimal latency, supreme reliability, personalized customer experience, etc.
15
[0098] While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in
20 the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
[0099] 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.
25 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
30 described herein, are considered to be encompassed within the scope of the present disclosure.
26

We Claim
1. A method [300] for automating deployment of a network, the method
[300] comprising:
‐ identifying, by an identification unit [202], a set of requirement parameters from a stored collection of digital survey forms data;
‐ identifying, by the identification unit [202], a set of entities and a set of deployment stages required for the network deployment, based on the identified set of requirement parameters;
‐ generating, by a processing unit [204], one or more sets of execution tasks, wherein each of the execution task from the one or more sets of execution tasks has a pre-defined service level agreement (SLA) and wherein a first set of execution tasks from the one or more sets of execution tasks is associated with a first deployment stage from the set of deployment stages;
‐ assigning, by the processing unit [204], the first set of execution tasks, to the one or more entities from the set of entities;
‐ updating, by the processing unit [204], a status for each execution task from the first set of execution tasks, with a state associated with each of the execution task;
‐ sending, by a transceiver unit [206], an auto escalation notification to a target entity from the set of entities in an event the pre-defined SLA is breached for at least one execution task from the first set of execution tasks.
2. The method [300] as claimed in claim 1, wherein the network is a 5G radio product network.
3. The method [300] as claimed in claim 1, wherein the set of entities comprises at least one of a set of stakeholders and a set of digital platforms and the set of deployment stages comprises at least one of the first

deployment stage, a second deployment stage, a third deployment stage and a fourth deployment stage.
4. The method [300] as claimed in claim 1, wherein each of the deployment stage from the set of deployment stages, is performed successively in sequence, and wherein, the assignment of a set of execution tasks from the one or more sets of execution tasks associated with a successive deployment stage from the set of deployment stages, is performed at initiation of the successive deployment stage.
5. The method [300] as claimed in claim 1, wherein the collection of digital survey forms data comprises at least one of a planning survey, a technical site survey, and backhaul availability.
6. The method [300] as claimed in claim 1, wherein in response to assigning each execution task from the first set of execution tasks, an auto email notification is sent to each of the assigned one or more entities from the set of entities.
7. The method [300] as claimed in claim 1, wherein the status for each of the assigned execution tasks from the first set of execution tasks is at least one of new, in-progress, completed, rejected and re-assigned.
8. The method [300] as claimed in claim 7, wherein the status is updated periodically based on the state of each of the execution tasks from the first set of execution tasks.
9. The method [300] as claimed in claim 1, wherein an auto email notification is sent to one or more entities from the set of entities in an event the pre¬defined SLA is breached for one or more execution tasks from the first set of execution tasks.

10. The method [300] as claimed in claim 1, wherein the SLA breach event is detected, when a fault is identified with a timeline associated with the at least one execution task from the first set of execution tasks.
11. The method [300] as claimed in claim 1, wherein the first set of execution tasks associated with the first deployment stage comprises at least a nominal coverage generation and a nominal coverage validation.
12. The method [300] as claimed in claim 3, wherein a second set of execution t a s k s f ro m t h e on e or m o re s e t s of e x ec u t i o n t a s k s a s so c i a t e d with the second deployment stage comprises at least one or more site identification and scope release for the network deployment.
13. The method [300] as claimed in claim 3, wherein a third set of execution tasks from the one or more sets of execution tasks associated with the third deployment stage comprises at least a planning survey, backhaul availability, technical site survey, commercial request and approval, local body no objection certificate clearance, ready for infra survey, equipment installation, and Access and Mobility Function (AMF) provisioning.
14. The method [300] as claimed in claim 3, wherein a fourth set of execution tasks from the one or more sets of execution tasks associated with the fourth deployment stage comprises at least an agreement signing and uploading, rental and vendor billing, material movement, logical data upload, utilities, battery, gNodeB creation in Gi interface.
15. The method [300] as claimed in claim 1, wherein the status for each execution task from the first set of execution tasks is displayed on a management view dashboard.

16. A system [200] for automating deployment of a network, the system [200]
comprising:
‐ an identification unit [202], the identification unit [202] configured to: o identify, a set of requirement parameters from a stored
collection of digital survey forms data, o identify, a set of entities and a set of deployment stages required for the network deployment, based on the identified set of requirement parameters; ‐ a processing unit [204] connected at least to the identification unit [202], the processing unit [204] configured to: o generate one or more sets of execution tasks, wherein each of the execution task from the one or more sets of execution tasks has a pre-defined service level agreement (SLA) and wherein a first set of execution tasks from the one or more sets of execution tasks is associated with a first deployment stage from the set of deployment stages, o assign the first set of execution tasks, to the one or more
entities from the set of entities, o update a status for each execution task from the first set of execution tasks, with a state associated with each of the execution task; ‐ a transceiver unit [206] connected at least to the processing unit [204], the transceiver unit [206] configured to: ‐ send an auto escalation notification to a target entity from the set of entities in an event the pre-defined SLA is breached for at least one execution task from the first set of execution tasks.
17. The system [200] as claimed in claim 16, wherein the network is a 5G radio
product network.

18. The system [200] as claimed in claim 16, wherein the set of entities comprises at least one of a set of stakeholders and a set of digital platforms and the set of deployment stages comprises at least one of the first deployment stage, a second deployment stage, a third deployment stage and a fourth deployment stage.
19. The system [200] as claimed in claim 16, wherein each of the deployment stage from the set of deployment stages, is performed successively in sequence, and wherein, the assignment of a set of execution tasks from the one or more sets of execution tasks associated with a successive deployment stage from the set of deployment stages, is performed at initiation of the successive deployment stage.
20. The system [200] as claimed in claim 16, wherein the collection of digital survey forms data comprises at least one of a planning survey, a technical site survey, and backhaul availability.
21. The system [200] as claimed in claim 16, wherein the transceiver unit [206] is further configured to send an auto email notification to each of the assigned one or more entities from the set of entities, in response to assigning each execution task from the first set of execution tasks.
22. The system [200] as claimed in claim 16, wherein the status for each of the assigned execution tasks from the first set of execution tasks is at least one of new, in-progress, completed, rejected and re-assigned.
23. The system [200] as claimed in claim 22, wherein the status is updated periodically by the processing unit [204], based on the state of each of the execution tasks from the first set of execution tasks.
24. The system [200] as claimed in claim 16, wherein the transceiver unit [206] is configured to send an auto email notification to one or more entities from

the set of entities in an event the pre-defined SLA is breached for one or more execution tasks from the first set of execution tasks.
25. The system [200] as claimed in claim 16, wherein the SLA breach event is detected, when a fault is identified with a timeline associated with the at least one execution task from the first set of execution tasks.
26. The system [200] as claimed in claim 16, wherein the first set of execution tasks associated with the first deployment stage comprises at least a nominal coverage generation and a nominal coverage validation.
27. The system [200] as claimed in claim 18, wherein a second set of execution t a s k s f ro m t h e on e or m o re s e t s of e x ec u t i o n t a s k s a s so c i a t e d with the second deployment stage comprises at least one or more site identification and scope release for the network deployment.
28. The system [200] as claimed in claim 18, wherein a third set of execution tasks from the one or more sets of execution tasks associated with the third deployment stage comprises at least a planning survey, backhaul availability, technical site survey, commercial request and approval, local body no objection certificate clearance, ready for infra survey, equipment installation, and Access and Mobility Function (AMF) provisioning.
29. The system [200] as claimed in claim 18, wherein a fourth set of execution tasks from the one or more sets of execution tasks associated with the fourth deployment stage comprises at least an agreement signing and uploading, rental and vendor billing, material movement, logical data upload, utilities, battery, gNodeB creation in Gi interface.

30. The system [200] as claimed in claim 16, wherein the status for each execution task from the first set of execution tasks is displayed on a management view dashboard.
31. A user equipment (UE) for automating deployment of a network, the UE comprising a system [200], wherein the system [200] comprises:
‐ an identification unit [202], the identification unit [202] configured to: o identify, a set of requirement parameters from a stored
collection of digital survey forms data, o identify, a set of entities and a set of deployment stages required for the network deployment, based on the identified set of requirement parameters; ‐ a processing unit [204] connected at least to the identification unit [202], the processing unit [204] configured to: o generate one or more sets of execution tasks, wherein each of the execution task from the one or more sets of execution tasks has a pre-defined service level agreement (SLA) and wherein a first set of execution tasks from the one or more sets of execution tasks is associated with a first deployment stage from the set of deployment stages, o assign the first set of execution tasks, to the one or more
entities from the set of entities, o update a status for each execution task from the first set of execution tasks, on a management view dashboard, with a state associated with each of the execution task; ‐ a transceiver unit [206] connected at least to the processing unit [204], the transceiver unit [206] configured to: ‐ send an auto escalation notification to a target entity from the set of entities in an event the pre-defined SLA is breached for at least one execution task from the first set of execution tasks.