WO2025203072A1

WO2025203072A1 - System and method for network planning and deployment

Info

Publication number: WO2025203072A1
Application number: PCT/IN2025/050438
Authority: WO
Inventors: Pradeep Kumar Bhatnagar; Aayush Bhatnagar; Uday Shanbhag; Vivek Patel
Original assignee: Jio Platforms Ltd
Current assignee: Jio Platforms Ltd
Priority date: 2024-03-27
Filing date: 2025-03-24
Publication date: 2025-10-02
Anticipated expiration: 2026-09-27

Abstract

The present disclosure a system (108) and a method (500) for network planning and deployment. The method (500) comprises creating at least one workorder for the node based on a request received from a network entity (110). The method (500) comprises processing the created at least one workorder into one or more workflows to perform a first plurality of tasks on the one or more nodes. At least one node to which the at least one cell is to be added is determined based on the first plurality of performed tasks. A first plurality of health checks on the at least one determined node is performed to validate a status of the at least one determined node. The at least one cell is added on the at least one determined node based on at least one configuration created based on status validation.

Description

SYSTEM AND METHOD FOR NETWORK PLANNING AND DEPLOYMENT

RESERVATION OF RIGHTS

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

TECHNICAL FIELD

[0002] The present disclosure relates generally to the field of telecommunications. More particularly, the present disclosure relates to a system and a method network planning and deployment. The present disclosure relates to a system and a method for optimizing a performance of a radio access network (RAN).

BACKGROUND

[0003] 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. [0004] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, the fifth-generation (5G) technology is being deployed, with even faster data speeds, low latency, and the ability to connect multiple devices simultaneously.

[0005] As wireless technologies are advancing, there is a need to cope with the 5G requirements and deliver a high level of service to the users. A radio access network (RAN) is a type of network infrastructure used commonly for mobile networks that consists of radio base stations with large antennas. A RAN wirelessly connects user equipment to a core network. The radio access networks (RANs) are becoming more complex due to higher speeds, increased interconnected units, and the integration of various sub-networks into larger ones. Users can now send different types of data simultaneously, such as text, voice, video, and multimedia files. The demand for fast and reliable internet is increasing, especially for activities like gaming, audio, and video streaming on mobile devices. Users want better network quality to minimize delays and successfully make voice calls, leading to a growing interest in real-time monitoring performance of the radio access network (RAN).

[0006] Addition of a new cell or carrier in the RAN is a routine task performed by the network planning and deployment team to enhance the coverage or capacity of the RAN. Traditionally, adding a new cell or carrier involves design, configuration, monitoring, optimization, and troubleshooting, all of which require significant manual effort from the network planning team. Site surveys, configuration, optimization, and troubleshooting demand extensive hands-on work and human intervention, significantly slowing deployment and increasing operational costs. Incorrect frequency assignments, misconfigured parameters, or overlooked interference issues can negatively affect network performance and require additional time and resources to correct. As the network grows, the number of tasks and steps involved in planning and deployment increases, making it challenging to scale using traditional techniques. With more manual processes, the time and effort required also grow exponentially. The complexity of tasks, such as site surveys, frequency planning, interference management, and troubleshooting, increases with the size of the network, making manual handling of these tasks increasingly unmanageable. As a result, network planning teams struggle to scale, optimize, and deploy quickly.

[0007] Traditional techniques require a significant amount of manual effort from the network planning team when adding a new cell or carrier in the RAN. As a result, these traditional methods are inefficient and time-consuming for RAN planning and deployment.

[0008] Therefore, there is a need for an improved system and a method that overcomes the limitations of the prior arts and efficiently carry out the process of the addition of the new cell or the new carrier in the RAN and optimizes the performance of the radio access network (RAN).

SUMMARY OF THE DISCLOSURE

[0009] In an exemplary embodiment, a method for network planning and deployment is described. The method comprises creating, by a creation module, at least one workorder to add at least one cell on one or more nodes based on a request. The method further comprises processing, by an execution module, the at least one created workorder to generate one or more workflows to perform a first plurality of tasks on the one or more nodes. The method comprises determining, based on the first plurality of performed tasks, by a determining module, at least one node to which the at least one cell is to be added. The method comprises performing, by the execution module, a first plurality of health checks on the at least one determined node. The method further comprises validating, by the execution module, a status of the at least one determined node based on the first plurality of performed health checks. The method comprises based on the validation, creating, by the creation module, at least one configuration for adding the at least one cell on the at least one determined node. The method comprises adding, by the execution module, the at least one cell on the at least one determined node based on the at least one created configuration.

[0010] In some embodiments, the method further comprises receiving, by a receiving module, the request from a network entity.

[0011] In some embodiments, the first plurality of tasks comprises at least one of a network type analysis, a current capacity analysis, a load analysis, a traffic analysis, and a network topology analysis.

[0012] In some embodiments, the at least workorder comprises information corresponding to the one or more nodes, wherein the information comprises at least one of a node name, a node type, a frequency band, number of cells to be added, location details of the one or more nodes, and an identifier (ID).

[0013] In some embodiments, the status of the at least one determined node comprises at least one of a healthy state and an unhealthy state.

[0014] In some embodiments, the method further comprises performing, by the execution module, a second plurality of tasks on the at least one determined node comprising the at least one added cell. The second plurality of tasks comprises at least one of a software upgradation, a firmware upgradation, a second plurality of health checks, one or more parameters tunning, a post-checking procedure, and a restoration procedure.

[0015] In some embodiments, the at least one configuration comprises tunning and configuring one or more parameters based on at least one of band information, carrier information, location information, and cell type information. [0016] In another exemplary embodiment, a system for network planning and deployment is described. The system comprises a creation module configured to create at least one workorder to add at least one cell on one or more nodes based on a request and an execution module configured to process the at least one created workorder to generate one or more workflows to perform a first plurality of tasks on the one or more nodes. Based on the first plurality of performed tasks, a determining module is configured to determine at least one node to which the at least one cell is to be added. The execution module is configured to perform a first plurality of health checks on the at least one determined node and validate a status of the at least one determined node based on the first plurality of performed health checks. The creation module is configured to create at least one configuration for adding the at least one cell on the at least one determined node based on the validation. The execution module is configured to add the at least one cell on the at least one determined node based on the at least one created configuration.

[0017] In some embodiments, a receiving module is configured to receive the request from a network entity.

[0018] In some embodiments, the execution module is configured to perform a second plurality of tasks on the at least one determined node comprising the at least one added cell. The second plurality of tasks comprises at least one of a software upgradation, a firmware upgradation, a second plurality of health checks, one or more parameters tunning, a post-checking procedure, and a restoration procedure.

[0019] In yet another exemplary embodiment, a user equipment (UE) communicatively coupled with a system is described. The coupling comprises steps of receiving, by the system, a connection request from the UE, sending, by the system, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request. The system is configured for performing network planning and deployment. The system comprises a creation module configured to create at least one workorder to add at least one cell on one or more nodes based on a request and an execution module configured to process the at least one created workorder to generate one or more workflows to perform a first plurality of tasks on the one or more nodes. Based on the first plurality of performed tasks, a determining module is configured to determine at least one node to which the at least one cell is to be added. The execution module is configured to perform a first plurality of health checks on the at least one determined node and validate a status of the at least one determined node based on the first plurality of performed health checks. The creation module is configured to create at least one configuration for adding the at least one cell on the at least one determined node based on the validation. The execution module is configured to add the at least one cell on the at least one determined node based on the at least one created configuration.

[0020] In yet another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for network planning and deployment is described. The method comprises creating, by a creation module, at least one workorder to add at least one cell on one or more nodes based on a request. The method further comprises processing, by an execution module, the at least one created workorder to generate one or more workflows to perform a first plurality of tasks on the one or more nodes. The method comprises determining, based on the first plurality of performed tasks, by a determining module, at least one node to which the at least one cell is to be added. The method comprises performing, by the execution module, a first plurality of health checks on the at least one determined node. The method further comprises validating, by the execution module, a status of the at least one determined node based on the first plurality of performed health checks. The method comprises based on the validation, creating, by the creation module, at least one configuration for adding the at least one cell on the at least one determined node. The method comprises adding, by the execution module, the at least one cell on the at least one determined node based on the at least one created configuration.

[0021] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure, and are not restrictive.

OBJECTS

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

[0023] An object of the present disclosure is to provide a system and a method for efficient RAN planning and deployment.

[0024] Another object of the present disclosure is to provide a system and a method that efficiently carry out the process of the addition of the new cell or the new carrier in the RAN.

[0025] An object of the present disclosure is to provide a system and a method that provides a unique middleware and UI that helps in the realization of the automation of the process of the RAN planning and deployment.

[0026] An object of the present disclosure is to provide a system and a method for optimizing the performance of the RAN.

[0027] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING [0028] 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 is instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components, or circuitry commonly used to implement such components.

[0029] FIG. 1 illustrates an exemplary network architecture for implementing a system for network planning and deployment, in accordance with embodiments of the present disclosure.

[0030] FIG. 2 illustrates an exemplary block diagram of the system, in accordance with embodiments of the present disclosure.

[0031] FIG. 3 illustrates an exemplary system architecture of the system for network planning and deployment, in accordance with an embodiment of the present disclosure.

[0032] FIG. 4 illustrates an exemplary flow diagram of a method for network planning and deployment, in accordance with an embodiment of the present disclosure.

[0033] FIG. 5 illustrates another exemplary flow diagram of a method for network planning and deployment, in accordance with an embodiment of the present disclosure. [0034] FIG. 6 illustrates an exemplary computer system in which or with which the embodiments of the present disclosure may be implemented.

[0035] The foregoing shall be more apparent from the following more detailed description of the disclosure.

LIST OF REFERENCE NUMERALS

100 - Network Architecture

102-1, 102-2... 102-N - Users

104-1, 104-2... 104-N - User Equipments

106 - Network

108 - System

110 - Network Entity

200 - System Block Diagram

202 - One or More Processor(S)

204 - Memory

206 - Interfaces

208 - Processing Engine

210 - Database

212 - Creation Module

214 - Execution Module

216 - Determining Module 218 - Receiving Module

220 - Other Modules

300 - System Architecture

304 - Shared Load Balancer (LB) 306 - Web Servers

308 - Application Programming Interface (API) Gateway

310, 318 - Database Management System (DBMS)

312, 314 - Database

316 - Plurality of Internal Load Balancer (LB) 320 - External System

400 - Method Flow Diagram

500 - Method Flow Diagram

600 - Computer System

610 - External Storage Device 620 - Bus

630 - Main Memory

640 - Read Only Memory

650 - Mass Storage Device

660 - Communication Port(S) 670 - Processor

DETAILED DESCRIPTION

[0036] 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 can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0037] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

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

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

[0040] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.

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

[0042] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

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

[0044] Addition of a new cell or carrier in the RAN is a routine task performed by the network planning and deployment team to enhance the coverage or capacity of the RAN. Traditionally, adding a new cell or carrier involves design, configuration, monitoring, optimization, and troubleshooting, all of which require significant manual effort from the network planning team. Site surveys, configuration, optimization, and troubleshooting demand extensive hands-on work and human intervention, significantly slowing deployment and increasing operational costs. Incorrect frequency assignments, misconfigured parameters, or overlooked interference issues can negatively affect network performance and require additional time and resources to correct. As the network grows, the number of tasks and steps involved in planning and deployment increases, making it challenging to scale using traditional techniques. With more manual processes, the time and effort required also grow exponentially. The complexity of tasks, such as site surveys, frequency planning, interference management, and troubleshooting, increases with the size of the network, making manual handling of these tasks increasingly unmanageable. As a result, network planning teams struggle to scale, optimize, and deploy quickly.

[0045] Therefore, traditional techniques require a significant amount of manual effort from the network planning team when adding a new cell or carrier in the RAN. As a result, these traditional methods are inefficient and time-consuming for RAN planning and deployment.

[0046] Further, there is a need for an improved system and a method that overcomes the limitations of the prior arts that provides an automation of the process of the addition of the new cell or the new carrier in the RAN for quick RAN planning and deployment. [0047] In an aspect, the present disclosure provides an improved system and a method for efficiently carry out the process of the addition of the new cell or the new carrier in the RAN through an automation process.

[0048] In an aspect, the present disclosure provides an improved system and a method for an efficient RAN planning and deployment.

[0049] In an aspect, the present disclosure provides an improved system and a method that optimizes the performance of the RAN.

[0050] In an aspect, the present disclosure provides a unique middleware and UI that helps in the realization of the automation of the process of RAN planning and deployment.

[0051] In an aspect, the unique design of a module provided by the present disclosure helps in creating a workorder on the UI for the multiple nodes present in the RAN at different ground sites simultaneously in one go.

[0052] In an aspect, the created workorders may be further branched into individual work flows to perform tasks on individual nodes at different stages.

[0053] In an aspect, the UI allows a backend/network engineer to visualize radio activities at different ground sites. In an aspect, the backend/network engineer can perform different health checks on the node using the proposed UI to validate the operation of the node pre addition and the post addition.

[0054] In an aspect, the complex workflow may get materialized through the unique UI design proposed by the present disclosure.

[0055] In an aspect, the backend/network engineer may create a workorder for the node or the cell to be added in the RAN with all the required details. In an aspect, the required details may include a node name (e.g., a service access point (SAP) identifier (ID)), a band, a cell number, geography details etc. The SAP ID is an identifying label for network endpoints used in open systems interconnection (OSI) networking.

[0056] In an aspect, the health check in the RAN may get performed by executing some commands on an element management system (EMS) for the node on which the new cell is to be added. In an aspect, the EMS may validate the status and health of the node.

[0057] In an aspect, a minimum configuration which is required to add the cell on the node may get created using an administrator provided inputs and other logics on the data available in the RAN.

[0058] In an aspect, a node software and firmware upgradation may get performed if the node or any of its units are not on a latest software and firmware.

[0059] In an aspect, it is checked if the node is operational up and healthy by executing and validating the various health check commands.

[0060] In an aspect, at least one tuning and optimizing parameter may get generated using different logics on the data available in the RAN.

[0061] In an aspect, at least one tuning and optimizing parameter may get generated and executed on the cell or the node.

[0062] In an aspect, the post checks may get performed to check that if all the commands and executed correctly and if all the key performance indicator (KPI) of the node are normal or not.

[0063] In an aspect, any node level settings related to the node may get restored if required. [0064] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0065] FIG. 1 illustrates an exemplary network architecture (100) for implementing a system (108) for network planning and deployment, in accordance with embodiments of the present disclosure.

[0066] Referring to FIG. 1, the network architecture (100) may include one or more computing devices or user equipments (104-1, 104-2... 104-N) associated with one or more users (102-1, 102-2... 102-N) in an environment. The network architecture (100) may also include a network entity (110), a central database (112), and a network (106).

[0067] A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102-N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more user equipments (104-1, 104-2... 104-N) may be individually referred to as the user equipment (104) and collectively referred to as the user equipment (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three user equipments (104) are depicted in FIG. 1, however any number of the user equipments (104) may be included without departing from the scope of the ongoing description.

[0068] In an embodiment, the user equipment (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device(e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the user equipment (104) may include, but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general -purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device. The user equipment (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touch pad, touch enabled screen, electronic pen, and the like.

[0069] In an embodiment, each of the user equipment (104-1, 104-2... 104-N) includes a user interface via which the user (102) may provide one or more user inputs (e.g., request).

[0070] In an exemplary embodiment, the network (106) may include, but not be limited to, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. In an exemplary embodiment, the network (106) may include, but not be limited to, a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet- switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0071] In an aspect, the network architecture comprises a network entity (110). The network entity (110) may be any element that is part of a network, whether it's a physical device, a logical resource, or even a non-resource (e.g., a party or place or person). One or more network entities are interconnected and communicate with each other to enable data transmission and network operations. The network entity may monitor, configure, and troubleshoot network devices (e.g., UEs, base stations, server, access points) and resources.

[0072] In an embodiment, the user equipment (104) is communicatively coupled with the system (108). The system (108) may receive a connection request from the UE (104). The system (108) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. The system (108) may be configured for network planning and deployment.

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

[0074] FIG. 2 illustrates an exemplary block diagram (200) of the system (108) for network planning and deployment, in accordance with an embodiment of the present disclosure.

[0075] FIG. 2 with reference to FIG. 1 , illustrates the block diagram (200) of the system (108) for network planning and deployment.

[0076] The system (108) includes one or more processor(s) (202), a memory (204), a processing engine (208), a database (210), and an interface(s) (206). In an exemplary embodiment, the processing engine (208) may include one or more engines selected from any of a creation module (212), an execution module (214), a determining module (216), a receiving module (218), and other modules (220) having functions that may include but are not limited to testing, storage, and peripheral functions.

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

[0078] In an embodiment, the interface(s) (206) (also known as interfacing unit) may comprise a variety of interfaces, for example, interfaces for data input and output devices (RO), storage devices, and the like. The interface(s) (206) may facilitate communication through the processor(s) (202). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108).

[0079] The interface(s) (206) is included within the system (108) to serve as a medium for data exchange, configured to facilitate user interaction with the mobile application. The interface(s) (206) may be composed of interfaces for data input and output devices, storage devices, and the like, providing a communication pathway for the various components of the system (108). Examples of such components include, but are not limited to, the processing unit/engine(s) (208) and the database (210). [0080] In an embodiment, the processing unit/engine(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processorexecutable instructions stored on a non -transitory machine -readable storage medium and the hardware for the processing engine(s) (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (208). In such examples, the system (108) may comprise the machine -readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine -readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry.

[0081] In an embodiment, the database (210) is configured for serving as a centralized repository for storing and retrieving various operational data. The database (210) is designed to interact seamlessly with other components of the system (102) to support the system's functionality effectively. The database (210) may store data that may be either stored or generated as a result of functionalities implemented by any of the components of the one or more processor(s) (202) or the processing engines (208). In an embodiment, the database (210) may be separate from the system (108).

[0082] As illustrated in Fig. 2, the memory (204) and the one or more processors (202) may be configured to execute a set of instructions stored in the memory (204). These instructions may orchestrate a series of operations involving various components to streamline network planning and deployment.

[0083] In an aspect, the network planning is the process of strategically organizing and arranging the operations of a network to ensure smooth and efficient communication and data transfer. In an aspect, the network deployment is the process of installing and configuring network infrastructure (e.g., adding new cell) to ensure seamless connectivity and communication.

[0084] The creation module (212) is configured to create at least one workorder to add at least one cell on one or more nodes based on a request. The receiving module (218) is configured to receive the request from the network entity 110. In an aspect, the one or more nodes may be one or more base stations. The base station may be NodeB (3G), eNodeB (eNB) (4G), and gNodeB (gNB) (5G).

[0085] In an aspect, the network entity (110) may be at least one of a user and a network node. In an aspect, the request from the network entity (110) may be manual or automated. The request from the network entity (110) may receive through a user interface (UI). The user interface may be a graphical user interface (GUI), a command line interface (CLI), or an application programming interface (API). In an aspect, the GUI refers to a user interface that allows users to interact with the devices through visual elements (e.g., icons, windows, and menus). In an aspect, the command-line Interface (CLI) refers to a text-based user interface where the user interacts with the device by typing commands into a terminal or console. In an aspect, the application-programming interface (API) refers to a set of rules and protocols that allows different software applications or systems to communicate with each other. It defines the methods and data structures that applications can use to interact with the software component, operating system, or service. [0086] In an aspect, the network entity generates the automated request based on one or more predefined conditions. The one or more predefined conditions are determined based on requirements in network planning, network configurations and network optimizations.

[0087] In an aspect, the user may be a network administrator or a network operator. The network administrator or the network operator monitor the performance of the network through Key Performance Indicators (KPIs). KPIs include, but are not limited to, traffic load, handover, call rates, signal quality, throughput, network capacity, network coverage, etc.

[0088] In an aspect, the network node may be a base station, a network management function, a radio network controller. In an aspect, the base station refers to as a central point for communication, connecting user equipments to the network and enabling communication between them and the core network.

[0089] In an aspect, the network management function refers to a network function that involves the processes, tools, and applications used to ensure a network operates efficiently, effectively, and securely, encompassing functions like fault, configuration, accounting, performance, and security management.

[0090] In an aspect, the radio network controller (RNC) refers to a network component responsible for managing radio resources and facilitating communication between the base stations (NodeBs) and the core network, ensuring smooth handovers and efficient traffic management.

[0091] In an aspect, the work order may refer to a request or set of instructions that outlines a specific task or process that needs to be completed. The work order serves as a request for specific work to be completed, ensuring tasks are managed and tracked effectively within the system. [0092] The workorder is created based on data provided in the request. In an aspect, the workorder is created over the user interface. The details corresponding to the workorder is filled over the user interface (UI). In an aspect, the details are filled manually or automatically using the data provided in the request. The UI helps in the realization of the automation of the process of the network (e.g., random access network (RAN)) planning and deployment.

[0093] The data provided in the request is used to determine details corresponding to the cell to be added to the node. The at least workorder comprises information corresponding to the one or more nodes. The information comprises at least one of a node name, a node type, a frequency band, number of cells to be added, location details of the one or more nodes, and an identifier (ID).

[0094] The execution module (214) is configured to process the at least one created workorder to generate one or more workflows to perform a first plurality of tasks on the one or more nodes. The first plurality of tasks comprises at least one of a network type analysis, a network capacity analysis, a load analysis, a traffic analysis, and a network topology analysis.

[0095] In an aspect, the one or more workflows refer to a series of tasks or steps that are systematically organized and executed to complete a specific process. In an operative aspect, the at least one created workorder is processed to generate one or more workflows (e.g., tasks or steps) to perform the first plurality of tasks on the one or more nodes.

[0096] In an aspect, the network type analysis refers to an analysis for evaluating existing cellular network topology, including the types of cell sites (e.g., macro, micro, pico, femto), their coverage areas, capacity, and technology standards (e.g., 4G, 5G) to determine the optimal location and type of new cell site to add, aiming to improve network coverage, capacity, and user experience in specific areas with high traffic or poor signal strength. The network type analysis includes cell site analysis, traffic analysis, signal strength analysis, network technology (e.g., 4G, 5G) determination based on user demand and future upgrade plans, cell type analysis, etc.

[0097] In an aspect, the network capacity analysis refers to an analysis for evaluating how adding new cell towers to an existing cellular network impacts its overall data carrying capacity by assessing factors (e.g., coverage expansion, interference reduction, and increased spectrum reuse, etc.). The network capacity analysis determines whether adding new cells improves network performance in specific areas with high traffic demands. The network capacity analysis includes traffic analysis, cell site placement, spectrum allocation, cell load balancing, capacity metrics analysis. The capacity metric analysis comprises analysis of call drop rate, throughput, signal strength, etc.

[0098] In an aspect, the load analysis refers to an analysis for evaluating the current traffic distribution across existing cells within the network to identify areas of high congestion and determine the optimal location for adding a new cell. The load analysis includes traffic measurements, location data, coverage analysis, interference assessment, cell site information, etc.

[0099] In an aspect, the traffic analysis refers to an analysis for monitoring and analyzing existing network traffic patterns before adding a new cell to identify potential bottlenecks, capacity issues, and optimal placement for the new cell. The traffic analysis includes traffic volume, traffic distribution, traffic patterns (e.g., application usage, time, user behavior, geography, etc.), latency, throughput, traffic flow, congestion, etc.

[00100] In one aspect, the network topology analysis refers to an analysis that examines the existing network structure (physical and logical connections between devices) to determine the optimal placement of the new cell, considering factors (e.g., traffic flow, load balancing, signal strength, potential interference, etc.) to ensure efficient and reliable network performance after the addition of the cell.

[00101] The determining module (216) is configured to determine at least one node to which the at least one cell is to be added based on the first plurality of performed tasks. Based on results from the first plurality of performed tasks, the determining module (216) determines the at least one node to which the at least one cell is to be added (i.e., based on a combination of traffic analysis, signal quality, user density, capacity usage, interference, and network performance, the node to which a new cell to be added is determined).

[00102] In an example, users of an ABC part (TAC = 112) of city 1 experience poor signal quality and slow data speeds. The network operator performs an initial analysis of current network setup to understand where additional capacity or coverage is needed. The initial analysis comprises checking of network density, interference, traffic volume, and topography, etc. The network operator determines a location to add a new cell in the ABC part (TAC = 112) of the city 1 based on the analysis.

[00103] The execution module (214) is configured to perform a first plurality of health checks on the at least one determined node and validate a status of the at least one determined node based on the first plurality of performed health checks. The status of the at least one determined node comprises at least one of a healthy state and an unhealthy state. In an aspect, the health checks are performed on the at least one determined node to determine and validate its status. The first plurality of health checks comprises checking power availability, interference checks, internet protocol (IP) addressing, frequency and channel allocation, load balancing and traffic distribution, service integration, etc.

[00104] Based on the first plurality of performed health checks, the status of the at least one determined node is validated by assessing the feasibility and readiness of the new cell to be added to the determined node. The validation of status of the at least one determined node ensures that the new cell will integrate well into the existing network and meet performance, coverage, and capacity requirements.

[00105] If the status of the at least one determined node is healthy state (i.e., operational), then the process of addition of cell to the node is executed. Further, upon determining the status of the at least one determined node is unhealthy state (i.e., non-operational), then the execution mode is again configured to perform the first plurality of tasks and the first plurality of health checks to determine the status of the at least one determined node.

[00106] The creation module (212) is configured to create at least one configuration for adding the at least one cell to the at least one determined node based on the validation. Upon determining the status of the at least one determined node is healthy state (i.e., operational), the configuration for adding the one cell to the determined node is created. The at least one configuration comprises tunning and configuring one or more parameters based on at least one of band information, carrier information, location information, and cell type information.

[00107] In an aspect, the band information refers to the radio frequency range that the new cell will operate on. The band information comprises, but is not limited to, frequency band type, frequency range, coverage and speed, etc.

[00108] In an aspect, the carrier information refers to radio frequency details of a cell tower, including its frequency band, bandwidth, and cell identity (Cell Global Identifier - CGI), transmission mode, and cell power level, etc.

[00109] In an aspect, the location information refers to information corresponding to geographical coordinates (latitude and longitude) of the cell tower site, along with details (e.g., cell identifier (Cell ID), location area code (LAC), and mobile network code (MNC). [00110] In an aspect, the cell type information refers to information corresponding to cell type considerations (e.g., macrocell, microcell, picocell, and femtocell). Each cell type with varying coverage ranges is chosen based on the desired signal strength and capacity needed in a specific geographic area. In an aspect, the microcell refers to the largest type of cell covering entire cities or large geographical regions in the network. In an aspect, the microcell refers to a cell that provides coverage in smaller areas than the macrocell, such as a part of a city, suburban areas, or inside large buildings. In an aspect, the picocell refers to a cell that provides even smaller coverage than the microcell used in environments (e.g., shopping malls, office buildings, or other indoor areas). In an aspect, the femtocell is the smallest type of cell, used in residential or small business environments. It provides coverage for a very small area.

[00111] The configuration (i.e., cell type, frequency band, bandwidth, power, antenna configuration, etc.) for the at least one cell is determined. In an example, Cell Type = Macro, Cell Identity = 12345, Frequency Band = 2600 MHz, Carrier Frequency = 1920 MHz, Cell Radius = 2 km, transmission power = 40 dBm, 4x4 antenna (four antennas on both transmission and reception), Tracking Area Code = 112, etc.

[00112] The execution module (214) is configured to add the at least one cell on the at least one determined node based on the at least one created configuration. The at least one cell is added to the determined node based on the created configuration. In an example, based on the configuration (i.e., Cell Type = Macro, Cell Identity = 12345, Frequency Band = 2600 MHz, Carrier Frequency = 1920 MHz, Cell Radius = 2 km, transmission power = 40 dBm, 4x4 antenna (four antennas on both transmission and reception), Tracking Area Code = 112), the at least one cell is added to the determined node. [00113] The execution module (214) is further configured to perform a second plurality of tasks on the at least one determined node comprising the at least one added cell. The second plurality of tasks comprises at least one of a software upgradation, a firmware upgradation, a second plurality of health checks, one or more parameters tunning, a post-checking procedure, and a restoration procedure. In an aspect, upon adding the cell to the determined node, the execution module (214) performs the second plurality of tasks on the node (e.g., software update, firmware update, parameter tunning, health checks, post-checking, etc.).

[00114] In an aspect, the software upgradation refers to a process of updating software to ensure the software has the latest features, bug fixes, and optimizations.

[00115] In an aspect, the firmware upgradation refers to a process of updating the firmware, which is the low-level software that controls the hardware of the network node.

[00116] In an aspect, the health checks after cell addition refer to a process carried out after the new cell has been added to the network node to ensure that it is functioning correctly, seamlessly integrated, and providing optimal performance. These health checks are essential to validate that the new cell does not disrupt network service and operates as expected regarding connectivity, coverage, quality, and overall performance. In an aspect, the second plurality of health-checks comprises connectivity validation, signal strength, signal quality, coverage, performance, throughput, latency, handover, mobility, etc.

[00117] In an aspect, the parameters tuning refers to a process of adjusting and optimizing various configuration settings and parameters to ensure that the new cell functions efficiently within the network. By adjusting various settings such as transmission power, antenna tilt, load balancing, handover parameters, interference management, and quality of service (QoS), operators can optimize coverage, capacity, and overall performance.

[00118] In an aspect, the post checking refers to a process of checking whether the cell is working properly and that the network operates as expected. The post-checking is performed to validate the deployment, confirm that the new cell integrates seamlessly with the rest of the network, and ensure optimal performance. The post checking includes signal quality checking, interference monitoring, throughput testing, power usage, traffic pattern and coverage analysis, KPIs analysis, etc.

[00119] In an aspect, the restoration procedure refers to a process taken to restore or recover network functionality in case of issues or failures during or after the addition of a new cell to the network. The process ensures that the network returns to normal operation quickly and effectively, minimizing service disruption for end users.

[00120] In this way, the second plurality of tasks are performed on the node to which the new cell is added to validate the deployment, confirm that the new cell integrates seamlessly with the rest of the network, and ensure optimal performance.

[00121] FIG. 3 illustrates an exemplary system architecture of a system (108) for network planning and deployment, in accordance with an embodiment of the present disclosure.

[00122] In an aspect, the system (108) may include the plurality of user equipments (UEs) (104), a shared load balancer (304), a plurality of web servers (306), an API gateway (308), a database management system 1 (DBMS1) (310), a databasel (312), a database! (314), a plurality of internal load balancer (LB) (316), a database management system! (DBMS2) (318), and an external system (320). [00123] In an aspect, the API gateway (308) handles all the requests and performs the dynamic routing of network service applications. The API gateway works as a front door for all the requests and is also known as an edge server.

[00124] In an aspect, the database 1 (312) may include a relational database. In an aspect, the database! (314) may include a non-relational database that is a column- oriented database.

[00125] In an aspect, the external system (320) may include a plurality of UDSF servers. The UDSF stores dynamic state data for stateless network functions.

[00126] In an aspect, when the spark job for a particular task gets executed on demand from the user or the network operator, then data may get reported from the DBMS1. In an aspect, the DBMS1 (310) may include a cell DBMS. In an aspect, the DBMS2 (318) may include a UDSF DBMS.

[00127] In an aspect, a plurality of API servers or a plurality of application servers may be used to host service interacting with a plurality of UDSF servers (external system) (320).

[00128] In an aspect, the shared LB (304) may be configured to receive at least one API request from at least one UE (104) or at least one network operator. The shared LB (304) may be configured to forward the received at least one API request to a web server selected from the plurality of web servers (306). The web server (306) may forward the received at least one API request to the API gateway (308).

[00129] The plurality of web servers (306) is software and hardware that uses HTTP (Hypertext Transfer Protocol) and other protocols to respond to API requests made over the World Wide Web. The main job of a web server is to display website content through storing, processing, and delivering webpages to users. Besides HTTP, the plurality of web servers (306) also supports SMTP (Simple Mail Transfer Protocol) and FTP (File Transfer Protocol), used for email, file transfer and storage. The web server hardware is connected to the internet and allows data to be exchanged with other connected devices, while web server software controls how a user accesses hosted files. In an aspect, the plurality of web servers (306) may be configured to process the received the API requests and generates a plurality of processed API requests.

[00130] In an aspect, the API gateway (308) may forward the received at least one request to the DBMS1 (310). In an aspect, when the spark job for a particular task gets executed by on demand from the user or the network operator, then data may get reported from the DBMS1 (310). In an aspect, the DBMS1 may be connected to the databasel (312) and database! (314) and the internal LB (316). The internal LB (316) may be further connected to the DBMS2 (318). The external system (320) may be further connected to the DBMS2 (318) and the internal LB (316).

[00131] In an aspect, the backend/network engineer may create a workorder for the node or the cell to be added in the RAN with all the required details such as a node name (SAP ID), a band, a cell number, geography details etc. In an aspect, a health check in the RAN may get performed by executing commands on the external system (320) (EMS) for the node on which the new cell is to be added. In an aspect, the external system (320) (EMS) may validate the status and health of the node. In an aspect, the minimum configuration which is required to add the cell on the node may get created using an administrator provided inputs and other logics on the data available in the RAN. In an aspect, a node software and firmware upgradation may get performed if the node or any of its units are not on a latest software and firmware. In an aspect, it is checked if the node is operational up and healthy by executing and validating the various health check commands. In an aspect, at least one tuning and optimizing parameter may get generated using different logics on the data available in the RAN. In an aspect, the at least one tuning and optimizing parameter may get and executed on the cell or the node. In an aspect, post checks may get performed to check that if all the commands and executed correctly and if all the KPI of the node are normal or not. In an aspect, any node level settings to the node may get restored if required.

[00132] FIG. 4 illustrates a flow diagram of a method (400) for network planning and deployment, in accordance with an embodiment of the present disclosure.

[00133] FIG. 4 with reference to FIG. 2, illustrates the method (400) for performing for network planning and deployment.

[00134] At step (402), the method (400) includes determining whether the user that generate an input request on a user interface (UI) is an administrator or not.

[00135] At step (404), the method (400) includes upon determining that the user is the administrator, uploading an administrator settings and datatypes on the UI. In an aspect, the administrator settings refer to configuration options and controls that are available to users with administrator privileges. These settings give administrators the authority to manage, modify, and control various aspects of a system, application, or service, including user access, security, configuration, and system performance. In an aspect, the datatype is a classification that specifies which type of value a variable can store and determines what operations can be performed on that data.

[00136] At step (406), the method (400) includes upon determining that the user is not the administrator, downloading at least one template on the UI. In an aspect, the template is a pre-designed or pre-structured document, file, or framework that provides a structure, including formatting, layout, and design elements, that can be reused for similar tasks or processes.

[00137] At step (408), the method (400) includes validating the downloaded template and the cells are filled to grow in the template. [00138] At step (410), the method (400) includes uploading the filled template on the UI.

[00139] At step (412), the method (400) includes upon determining that the filled template file is not uploaded on the UI, reviewing the failure reasons and the correct information.

[00140] At step (416), the method (400) includes upon determining that the filled template file is uploaded on the UI successfully, submitting the success cell.

[00141] At step (418), the method (400) includes sending the data related to the success cell to a database for storage. In an aspect, the database may be an unstructured data storage function (UDSF) database.

[00142] At step (420), the method (400) includes determining whether all the data related to the cells is sent to the database.

[00143] At step (422), the method (400) includes upon determining that all the data related to the cells is not sent to the database, marking the cell for a retry again to send the cell data to the database.

[00144] At step (424), the method (400) includes upon determining that all the data related to the cells is sent to the database successfully, creating reports and sending emails to the users.

[00145] FIG. 5 illustrates another exemplary flow diagram of a method (500) for network planning and deployment, in accordance with an embodiment of the present disclosure.

[00146] FIG. 5 with reference to FIG. 2, illustrates the method (500) for network planning and deployment using the creation module (212), the execution module (214), the determining module (216), and the receiving module (218) of the system (108).

[00147] At step (502), the method (500) includes creating, by the creation module (212), at least one workorder to add at least one cell on one or more nodes based on a request. In an aspect, the one or more nodes may be one or more base stations. The base station may be NodeB (3G), eNodeB (eNB) (4G), and gNodeB (gNB) (5G).

[00148] The method (500) includes receiving, by the receiving module (218), the request from the network entity (110). In an aspect, the network entity (110) may be at least one of a user and a network node. In an aspect, the user may be a network administrator or a network operator. In an aspect, the network node may be a base station, a network management function, a radio network controller. In an aspect, the request from the network entity may be manual or automated.

[00149] The at least workorder comprises information corresponding to the one or more nodes, wherein the information comprises at least one of a node name, a node type, a frequency band, number of cells to be added, location details of the one or more nodes, and an identifier (ID).

[00150] At step (504), the method (500) includes processing, by the execution module (214), the at least one created workorder to generate one or more workflows to perform a first plurality of tasks on the one or more nodes. The first plurality of tasks comprises at least one of a network type analysis, a current capacity analysis, a load analysis, a traffic analysis, and a network topology analysis.

[00151] At step (506), the method (500) includes determining, based on the first plurality of performed tasks, by the determining module (216), at least one node to which the at least one cell is to be added. The node to which the at least one cell is to be added is determined based on the network type analysis, the current capacity analysis, the load analysis, the traffic analysis, and the network topology analysis. [00152] At step (508), the method (500) includes performing, by the execution module (214), a first plurality of health checks on the at least one determined node. In an aspect, the health checks are performed prior to the addition of the new cell to the determined node to ensure that the network (106) is ready for the new cell, minimizing the risk of issues or service degradation once the new cell is integrated. These health checks ensure that the network’s infrastructure, resources, and configurations are prepared to accommodate the new cell and that its integration will not negatively impact existing services. The first plurality of health checks comprises checking power availability, interference checks, internet protocol (IP) addressing, frequency and channel allocation, load balancing and traffic distribution, service integration, etc.

[00153] At step (510), the method (500) includes validating, by the execution module (214), a status of the at least one determined node based on the first plurality of performed health checks. The status of the at least one determined node comprises at least one of a healthy state and an unhealthy state. In an aspect, the health checks are performed on the at least one determined node to determine and validate its status. The validation of status of the at least one determined node ensures that the new cell will integrate well into the existing network and meet performance, coverage, and capacity requirements.

[00154] If the status of the at least one determined node is healthy state (i.e., operational), then the process of addition of cell to the node is executed. Further, upon determining the status of the at least one determined node is unhealthy state (i.e., non-operational), then the execution mode is again configured to perform the first plurality of tasks and the first plurality of health checks to determine the status of the at least one determined node.

[00155] At step (512), based on the validation, creating, by the creation module (212), at least one configuration for adding the at least one cell on the at least one determined node. Upon determining the status of the at least one determined node is healthy state (i.e., operational), the configuration for adding the one cell to the determined node is created. The at least one configuration comprises tunning and configuring one or more parameters based on at least one of band information, carrier information, location information, and cell type information.

[00156] At step (514), the method (500) includes adding, by the execution module (214), the at least one cell on the at least one determined node based on the at least one created configuration. The at least one cell is added to the determined node based on the created configuration.

[00157] The method (500) further includes performing, by the execution module (214), a second plurality of tasks on the at least one determined node comprising the at least one added cell. The second plurality of tasks comprises at least one of a software upgradation, a firmware upgradation, a second plurality of health checks, one or more parameters tunning, a post-checking procedure, and a restoration procedure. In an aspect, upon adding the cell to the determined node, the execution module (214) performs the second plurality of tasks on the node (e.g., software update, firmware update, parameter tunning, health checks, post-checking, etc.). The second plurality of tasks are performed on the node to which the new cell is added to validate the deployment, confirm that the new cell integrates seamlessly with the rest of the network (106), and ensure optimal performance.

[00158] FIG. 6 illustrates an example computer system (600) in which or with which the embodiments of the present disclosure may be implemented.

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

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

[00161] In an embodiment, the bus (620) may communicatively couple the processor(s) (670) with the other memory, storage, and communication blocks. The bus (620) may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCLX) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (670) to the computer system (600). [00162] In another embodiment, operator, and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus (620) to support direct operator interaction with the computer system (600). Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (660). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (600) limit the scope of the present disclosure.

[00163] The exemplary computer system (600) is configured to execute a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for network planning and deployment is described. The method comprises creating, by a creation module, at least one workorder to add at least one cell on one or more nodes based on a request. The method further comprises processing, by an execution module, the at least one created workorder to generate one or more workflows to perform a first plurality of tasks on the one or more nodes. The method comprises determining, based on the first plurality of performed tasks, by a determining module, at least one node to which the at least one cell is to be added. The method comprises performing, by the execution module, a first plurality of health checks on the at least one determined node. The method further comprises validating, by the execution module, a status of the at least one determined node based on the first plurality of performed health checks. The method comprises based on the validation, creating, by the creation module, at least one configuration for adding the at least one cell on the at least one determined node. The method comprises adding, by the execution module, the at least one cell on the at least one determined node based on the at least one created configuration.

[00164] The present disclosure provides technical advancement related to network planning and deployment. This advancement addresses the limitations of existing solutions by introducing automation to the process the addition of the new cell or the new carrier in the RAN for quick RAN planning and deployment. The disclosure involves a novel combination of creating a work order for multiple nodes in one go and then branches into multiple individual workflows to perform tasks on individual nodes at different stages. The UI allows a backend/network engineer to visualize radio activities at different ground sites. The backend/network engineer can perform different health checks on the node using the proposed UI to validate the operation of the node pre addition and the post addition.

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

ADVANCEMENTS OF THE PRESENT DISCLOSURE

[00166] The present disclosure described herein above has several technical advantages as follows:

[00167] The present disclosure efficiently carries out the process of the addition of the new cell or the new carrier in the RAN.

[00168] The present disclosure provides efficient RAN planning and deployment.

[00169] The present disclosure provides unique middleware and UI that help automate the process of RAN planning and deployment.

[00170] The present disclosure optimizes the performance of the RAN.

Claims

1. A method (500) for network planning and deployment, the method (500) comprising: creating (502), by a creation module (212), at least one workorder to add at least one cell on one or more nodes based on a request; processing (504), by an execution module (214), the at least one created workorder to generate one or more workflows to perform a first plurality of tasks on the one or more nodes; determining (506), based on the first plurality of performed tasks, by a determining module (216), at least one node to which the at least one cell is to be added; performing (508), by the execution module (214), a first plurality of health checks on the at least one determined node; validating (510), by the execution module (214), a status of the at least one determined node based on the first plurality of performed health checks; based on the validation, creating (512), by the creation module (212), at least one configuration for adding the at least one cell on the at least one determined node; and adding (514), by the execution module (214), the at least one cell on the at least one determined node based on the at least one created configuration.

2. The method (500) as claimed in claim 1, further comprising: receiving, by a receiving module (218), the request from a network entity (110).

3. The method (500) as claimed in claim 1, wherein the first plurality of tasks comprises at least one of a network type analysis, a current capacity analysis, a load analysis, a traffic analysis, and a network topology analysis.

4. The method (500) as claimed in claim 1, wherein the at least workorder comprises information corresponding to the one or more nodes, wherein the information comprises at least one of a node name, a node type, a frequency band, number of cells to be added, location details of the one or more nodes, and an identifier (ID).

5. The method (500) as claimed in claim 1, wherein the status of the at least one determined node comprises at least one of a healthy state and an unhealthy state.

6. The method (500) as claimed in claim 1, further comprising: performing, by the execution module (214), a second plurality of tasks on the at least one determined node comprising the at least one added cell, wherein the second plurality of tasks comprises at least one of a software upgradation, a firmware upgradation, a second plurality of health checks, one or more parameters tunning, a post-checking procedure, and a restoration procedure.

7. The method (500) as claimed in claim 1, wherein the at least one configuration comprises tunning and configuring one or more parameters based on at least one of band information, carrier information, location information, and cell type information.

8. A system (108) for network planning and deployment, the system (108) comprising: a creation module (212) configured to create at least one workorder to add at least one cell on one or more nodes based on a request; and an execution module (214) configured to process the at least one created workorder to generate one or more workflows to perform a first plurality of tasks on the one or more nodes; based on the first plurality of performed tasks, a determining module (216) is configured to determine at least one node to which the at least one cell is to be added; the execution module (214) configured to: perform a first plurality of health checks on the at least one determined node; and validate a status of the at least one determined node based on the first plurality of performed health checks; the creation module (212) configured to create at least one configuration for adding the at least one cell on the at least one determined node based on the validation; and the execution module (214) configured to add the at least one cell on the at least one determined node based on the at least one created configuration.

9. The system (108) as claimed in claim 8, wherein a receiving module (218) is configured to receive the request from a network entity (110).

10. The system (108) as claimed in claim 8, wherein the first plurality of tasks comprises at least one of a network type analysis, a current capacity analysis, a load analysis, a traffic analysis, and a network topology analysis.

11. The system (108) as claimed in claim 8, wherein the at least workorder comprises information corresponding to the one or more nodes, wherein the information comprises at least one of a node name, a node type, a frequency band, number of cells to be added, location details of the one or more nodes, and an identifier (ID).

12. The system (108) as claimed in claim 8, wherein the status of the at least one determined node comprises at least one of a healthy state and an unhealthy state.

13. The system (108) as claimed in claim 8, wherein the execution module (214) configured to perform a second plurality of tasks on the at least one determined node comprising the at least one added cell, wherein the second plurality of tasks comprises at least one of a software upgradation, a firmware upgradation, a second plurality of health checks, one or more parameters tunning, a post-checking procedure, and a restoration procedure.

14. The system (108) as claimed in claim 8, wherein the at least one configuration comprises tunning and configuring one or more parameters based on at least one of band information, carrier information, location information, and cell type information.

15. A user equipment (UE) communicatively coupled with a system (108), the coupling comprises steps of: receiving, by the system (108), a connection request from the UE; sending, by the system (108), an acknowledgment of the connection request to the UE; and transmitting a plurality of signals in response to the connection request, wherein the system (108) is configured for network planning and deployment as claimed in claim 8.

16. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method (500) for network planning and deployment, the method (500) comprising: creating (502), by a creation module (212), at least one workorder to add at least one cell on one or more nodes based on a request; processing (504), by an execution module (214), the at least one created workorder to generate one or more workflows to perform a first plurality of tasks on the one or more nodes; determining (506), based on the first plurality of performed tasks, by a determining module (216), at least one node to which the at least one cell is to be added; performing (508), by the execution module (214), a first plurality of health checks on the at least one determined node; validating (510), by the execution module (214), a status of the at least one determined node based on the first plurality of performed health checks; based on the validation, creating (512), by the creation module (212), at least one configuration for adding the at least one cell on the at least one determined node; and adding (514), by the execution module (214), the at least one cell on the at least one determined node based on the at least one created configuration.