System and method for providing network service in a service affected area

Abstract

The present disclosure relates to a system (108) and a method (400) for providing at least one network service in a service affected area. The method (400) comprises receiving (402), by a receiving unit (218), one or more input data associated with one or more affected network sites. The method (400) comprises analyzing (404), by a processing unit (224), the one or more input data to generate a recovery list of the affected network sites. The method (400) comprises determining (406), by the processing unit (224), at least one configuration change to be applied to each of the affected network sites of the generated recovery list using the analyzed input data. The method (400) comprises providing (408), by the processing unit (224), the at least one network service to each of the affected network sites by applying the determined at least one configuration change and initiating a handover.

Description

SYSTEM AND METHOD FOR PROVIDING NETWORK SERVICE IN A SERVICE AFFECTED AREARESERVATION 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 (JPL) 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.FIELD OF DISCLOSURE

[0002] The embodiments of the present disclosure generally relate to communication networks. In particular, the present disclosure relates to a system and a method for providing at least one network service in a service affected area.DEFINITIONS

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The term “configuration management module” used hereinafter in the specification refers to a module responsible for managing and updating configuration data of network elements, including one or more network sites, to ensure they operate according to predefined parameter values and service requirements.

[0005] The term “fault management module” used hereinafter in the specification refers to a module that detects, logs, and manages network faults and alarms.

[0006] The term “performance management Module” used hereinafter in the specification refers to a system component that continuously observes the operational status and performance of network sites.

[0007] The term “Master Data Base (MDB)” used hereinafter in the specification refers to a database or centralized data store that aggregates inputs from various network systems for processing and analysis.

[0008] The term “E-Tilt (Electrical Tilt)” used hereinafter in the specification refers to an electrical adjustment of a beam direction of an antenna, which is typically performed remotely through software. This method alters the vertical angle of the radiated signal without a physical change to the position of the antenna, thereby optimizing coverage and signal strength.

[0009] The term “user input” used hereinafter in the specification refers to manual data provided by personnel, such as insights about local terrain or temporary obstacles in the affected area.

[0010] The term “recovery list” used hereinafter in the specification refers to a prioritized list of affected network sites identified for configuration changes and service restoration.

[0011] The term “configuration change” used hereinafter in the specification refers to a modification in network parameters such as antenna tilt, power level, or frequency settings to restore service.

[0012] The term “handover” used hereinafter in the specification refers to the process of transferring user connectivity from one network site to another for maintaining continuous service.

[0013] The term “recovery alarm notification” used hereinafter in the specification refers to an alert indicating the operational recovery or status change of an affected network site.

[0014] The term “service affected area” used hereinafter in the specification refers to a geographical region experiencing degraded or disrupted telecom service due to network site failures.

[0015] The term “operative State” used hereinafter in the specification refers to the operational condition or status of a network site after configuration changes are applied.

[0016] The term “affected network sites” used hereinafter in the specification refers to one or more telecom sites whose normal operation is disrupted or degraded due to a natural disaster or fault condition, resulting in impaired service delivery.

[0017] The term “one or more abnormalities” used hereinafter in the specification refers to unexpected issues or deviations from standard network behaviour, including persistent alarms, inconsistent configuration parameters, or service-impacting faults that arise during or after recovery.

[0018] The term “at least one network service” may include, for example, voice communication, mobile broadband access, emergency alert transmission, or any other telecommunication service provisioned through the affected network site.

[0019] These definitions are in addition to those expressed in the art.BACKGROUND OF DISCLOSURE

[0020] 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.

[0021] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology wasanalog technology that offered only voice services. Further, when the second- generation (2G) technology was introduced, text messaging and data services became possible. The 3 G 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, 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. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further.

[0022] In the evolving landscape of telecommunication services, disruptions caused by natural calamities or disasters can severely impact the continuity of essential services. Further, natural disasters like hurricanes, earthquakes, and floods can cause significant disruptions to telecommunication services. These disruptions can impede communication, hinder emergency response efforts, and isolate communities.

[0023] Also, conventional methods for identifying and prioritizing recovery efforts rely heavily on manual intervention and lack automated systems capable of swiftly assessing the situation and initiating appropriate actions.

[0024] Existing challenges in disaster recovery for telecom services highlight several key issues. Firstly, the manual identification and prioritization of affected sites present significant hurdles. This manual approach tends to be slow and inefficient, particularly in large-scale disasters where timely action is crucial. Secondly, the limited scope of data analysis in manual methods poses challenges. Factors such as geographic location, infrastructure damage, and the severity of outages may not be effectively considered, leading to suboptimal prioritization of recovery efforts. Thirdly, delayed service restoration exacerbates the situation, prolonging disruptions and impeding recovery initiatives. Lastly, the limited automation in existing disaster recovery plans further complicates matters. Heavyreliance on manual intervention increases the risk of errors and slows the restoration process, highlighting the need for more efficient and automated solutions.

[0025] Further, the consequences of the challenges in telecom service disaster recovery are far-reaching and impactful. Communication outages from these challenges can significantly hinder critical infrastructure and services, such as healthcare and emergency response systems, which rely heavily on uninterrupted communication networks. Moreover, disruptions in communication can disrupt economic activity, affecting businesses that depend on reliable networks for operations and transactions. Public safety may also be compromised as individuals may face difficulties contacting emergency services or receiving timely assistance during crises. These consequences underscore the urgent need for effective and efficient disaster recovery solutions in telecommunications.

[0026] There is, therefore, a need in the art to provide a method and a system that can overcome the shortcomings of the existing prior arts.OBJECTIVES OF THE PRESENT DISCLOSURE

[0027] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.

[0028] An objective of the present disclosure is to provide a system and a method that identify and prioritize telecom sites affected by natural disasters or calamities, or by any other events that impact or alter the area’s structural, physical, or geographic setup, thereby streamlining the recovery process.

[0029] Another objective of the present disclosure is to provide a system and a method to gather data about service-affecting sites from various sources.

[0030] Another objective of the present disclosure is to provide a system and a method that analyzes the gathered data comprehensively, considering factors such as infrastructure damage, severity of outages, and geographical location to prioritize sites for restoration.

[0031] Another objective of the present disclosure is to provide a system and a method that implements recommended changes to the identified sites through a configuration management system, ensuring swift and effective restoration of critical communication services.

[0032] Another objective of the present disclosure is to provide a system and a method that tracks the progress of the recovery process, promptly identifies any abnormalities, and provides stakeholders with real-time updates on recovery efforts.

[0033] Other objectives 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.SUMMARY

[0034] In an exemplary embodiment, a method for providing at least one network service in a service affected area. The method comprises receiving, by a receiving unit, one or more input data associated with one or more affected network sites located in the service affected area from one or more data sources. The method comprises analyzing, by a processing unit, the one or more input data to generate a recovery list of the affected network sites according to one or more parameters. The method comprises determining, by the processing unit, at least one configuration change to be applied to each of the affected network sites of the generated recovery list using the analyzed input data. The method comprises providing, by the processing unit, the at least one network service to each of the affected network sites of the generated recovery list by applying the determined at least one configuration change and initiating a handover between at least one affected network site selected from the generated recovery list and at least one active network site.

[0035] In some embodiments, the one or more input data comprise a set of network parameters, geographic locations of the affected network sites, a set of antenna parameters, a set of predefined parameter values, an Electrical tilt (E-Tilt)of each antenna associated with each affected network site, an antenna type, a type of the affected network site, and last updated configuration changes.

[0036] In some embodiments, the receiving unit receives at least one user input from a user for modifying the at least one determined configuration change.

[0037] In some embodiments, the at least one configuration change comprises an antenna tilt configuration, a frequency configuration, a power adjustment, a network configuration change, a sector modification, a network slicing change, and a beamforming adjustment.

[0038] In some embodiments, the one or more data sources comprise a configuration management module, a fault management module, a performance management module, and a database.

[0039] In some embodiments, the one or more parameters comprise an inter-antenna distance, a total number of handovers, a handover type, a handover threshold, a handover count, a handover latency, a signal strength, a set of cell selection parameters, a user location tracking parameter, and a network site operative parameter.

[0040] In some embodiments, the processing unit generates one or more reports summarizing the recovery information corresponding to each affected network site.

[0041] In some embodiments, the processing unit monitors at least one operative state of each affected network site after a predefined time interval and at regular intervals to identify one or more abnormalities

[0042] In some embodiments, the processing unit detects at least one recovery alarm notification corresponding to each of the one or more affected network sites from the one or more data sources.

[0043] In an exemplary embodiment, a system for providing at least one network service in a service affected area is disclosed. The system includes areceiving unit configured to receive one or more input data associated with one or more affected network sites located in the service affected area from one or more data sources. The system further includes a processing unit configured to analyze the one or more input data to generate a recovery list of the affected network sites according to one or more parameters. The system further determines at least one configuration change to be applied to each of the affected network sites of the generated recovery list using the analyzed input data. The system further provides the at least one network service to each of the affected network sites of the generated recovery list by applying the determined at least one configuration change and initialize a handover between at least one affected network site selected from the generated recovery list and at least one active network site

[0044] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for providing at least one network service in a service affected area. The method includes receiving, by a receiving unit, one or more input data associated with one or more affected network sites located in the service affected area from one or more data sources. The method comprises analyzing, by a processing unit, the one or more input data to generate a recovery list of the affected network sites according to one or more parameters. The method comprises determining, by the processing unit, at least one configuration change to be applied to each of the affected network sites of the generated recovery list using the analyzed input data. The method comprises providing, by the processing unit, the at least one network service to each of the affected network sites of the generated recovery list by applying the determined at least one configuration change and initiating a handover between at least one affected network site selected from the generated recovery list and at least one active network site.

[0045] 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.BRIEF DESCRIPTION OF DRAWINGS

[0046] 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. 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 the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0047] FIG. 1 illustrates an exemplary network architecture for providing at least one network service in a service affected area, in accordance with embodiments of the present disclosure.

[0048] FIG. 2A illustrates an exemplary system architecture for providing at least one network service in the service affected area, in accordance with embodiments of the present disclosure.

[0049] FIG. 2B illustrates a block diagram of a system for providing at least one network service in the service affected area, in accordance with embodiments of the present disclosure.

[0050] FIG. 3 illustrates an exemplary flow diagram of a method for providing at least one network service in the service affected area, in accordance with embodiments of the present disclosure.

[0051] FIG. 4 illustrates another exemplary flow diagram of the method for providing at least one network service in the service affected area, in accordance with embodiments of the present disclosure.

[0052] FIG. 5 illustrates an exemplary computer system in which or with which the system may be implemented in accordance with an embodiment of the present disclosure.

[0053] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102-1, 102-2. . . 102-N - A plurality of users104-1, 104-2... 104-N - User Equipments (UEs)106 - Network108 - System200A - System architecture202- Master Database (MDB)204- Network Management Platform (NMP)206 - Fault management module208 - Performance management module210- Radio Planning team212- Radio optimization team214- Sales and marketing team216- Configuration management module200A - Block diagram218 - Receiving unit220 - Memory222 - Interface(s)224 - Processing unit300 - Flow diagram400 - Flow diagram500 - A computer system510 - External storage device520 - Bus530 - Main memory540 - Read only memory550 - Mass storage device560 - Communication port(s)570 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

[0054] 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 all 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.

[0055] 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.

[0056] 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.

[0057] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations 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.

[0058] 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 notnecessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

[0059] 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.

[0060] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly 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 and all combinations of one or more of the associated listed items.

[0061] In a telecommunications network, the continuous availability and reliable performance of services are essential, particularly in the face of unforeseen disruptions such as natural calamities. When a natural disaster strikes, it can severely impact numerous network sites, leading to widespread service outages.The absence of an automated and prioritized approach to identify and restore these affected sites can result in significant delays in service recovery, inefficient allocation of resources, and prolonged downtime for users. This lack of a systematic recovery mechanism not only degrades user experience but also undermines the trust in network service providers during critical times. Therefore, it is required to swiftly assess the impact of disasters, identify the most critical sites for restoration, and implement targeted recovery actions to minimize service disruption.

[0062] In an aspect, the present disclosure provides a system and method for disaster management and network service recovery that automatically identifies and prioritizes network sites affected by a natural calamity. The system and the method then facilitate the restoration of network services by applying determined changes and initiating handovers between recovered and active network sites. The resulting automated prioritization and restoration process significantly reduces downtime, ensures a technically sound and rapid recovery, and enhances user satisfaction.

[0063] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 5.

[0064] FIG. 1 illustrates an exemplary network architecture for providing at least one network service in a service affected area, in accordance with embodiments of the present disclosure.

[0065] Referring to FIG. 1, the network architecture (100) may include one or more user equipments (UEs) (104-1, 104-2... 104-N) associated with one or more users (102-1, 102-2... 102-N) in an environment. 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 “computingdevice(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although two 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. In an embodiment, each of the user equipment (104) may have a first unique identifier attribute associated therewith. In an embodiment, the first unique identifier attribute may be indicative of Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, International Mobile Subscriber Identity (IMSI), Subscriber Permanent Identifier (SUPI) and the like.

[0066] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the user equipment (104) may include but is not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the user equipment (104) may include, but is not limited to, intelligent, multi-sensing, network-connected devices that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0067] In an embodiment, the UE (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 head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, 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, electromechanical, 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 touchpad, touch-enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the user equipment (104) may not be restricted to the mentioned devices and various other devices may be used.

[0068] Referring to FIG. 1, the UE (104) may communicate with a system (108) via the network (106). The UE (104) may be communicatively coupled with the network (106). The communicative coupling comprises receiving, from the UE (104), a connection request by the network (106), sending an acknowledgment of the connection request to the UE (104), and transmitting a plurality of signals in response to the connection request. As such, the network (106) may enable the UE (104) to communicate with other UEs (104) via a wired or wireless network. In an embodiment, the network (106) may include at least one of a Fourth Generation (4G) network, a Fifth Generation (5G) network, a Sixth Generation (6G) network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0069] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) mayinclude 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).

[0070] FIG. 2A illustrates an exemplary system architecture (200A) of the system (108) for providing at least one network service in the service affected area, in accordance with an embodiment of the present disclosure.

[0071] In an aspect, the system architecture (200A) includes a Master Database (MDB) (202), a Network Management Platform (NMP) (204), a fault management module (206), a performance management module (208) and a configuration management module (216). In an aspect, the system architecture (200A) may also include a radio optimization team (212), a radio planning team (210), and a sales and marketing team (214).

[0072] The NMP (204) may communicate with and receive manual inputs or insights from the fault management module (206), the performance management module (208) and the configuration management module (216), via each of their corresponding interfaces. Furthermore, the NMP (204) is communicatively coupled to the MDB (202), serving as a central repository of network data. Each of these interconnections may be established over the network (106), which may comprise one or more wired or wireless communication channels. In another example, the system (108) may be embedded into the User Equipment (UE) (104). The system (108) may be remotely accessible through the UE (104).

[0073] In an aspect, the MDB (202) may store information related to various network sites divided into a plurality of sectors. In an aspect, a sector refers to a specific geographical coverage area or angular segment served by a portion of a network site's antenna array, designed to provide network service within that defined spatial region. In an aspect, each sector is served by a plurality of antennas. In a further aspect, each antenna may have a number of ports (bands) that areconfigured to operate on different technology. In an example, the MDB (202) may store a set of network site identifiers, a set of antenna identifiers corresponding to each sector, and other telecommunication network operator-specific information stored in a specific nomenclature. In an aspect, the telecommunication network operator-specific nomenclature may include information such as geography name, geography site name, and geography cluster name of a specific eNodeB, etc. In an aspect, the MDB (202) may serve as a central repository for all data within the network. The MDB (202) may store data collected from various sources.

[0074] In a further embodiment, the MDB (202) serves as a centralized repository for storing comprehensive data pertinent to the telecommunications network. The MDB (202) may store details concerning the physical elements of the network, encompassing information about towers, fiber optic cables, equipment locations, and their respective specifications. The MDB (202) may store configuration settings and parameters associated with network equipment, comprising data on cell tower configurations, routing protocols, and service parameters crucial for network functionality. The MDB (202) may store historical records of network performance metrics, such as call quality, data throughput, signal strength, and service availability across various locations, are stored within the MDB (202). The MDB (202) may maintain data pertaining to subscribers, including their geographical locations, service subscriptions, and usage patterns, aiding in the provision of tailored services and targeted network optimizations.

[0075] In an embodiment, the MDB (202) may be configured to communicate with the processing unit (224) over the network (106). The network (106) may enable the UE (104) to communicate between devices and / or with a data network.

[0076] In an aspect, the NMP (204) relies on the MDB (202) as a primary data source for conducting disaster management and recovery operations efficiently. The NMP (204) may retrieve relevant information based on specific needs, such as:Identifying service disruptions by analysing historical performance data and current fault notifications.• Prioritizing recovery efforts by considering network infrastructure details and affected customer locations.• Adjusting network configurations by referencing existing settings and desired optimization strategies

[0077] In an aspect, once the relevant data is retrieved from the MDB (202), the relevant data may be channelled into the processing unit (224) to undergo several tasks. Further, the NMP (204) analyzes the data using algorithms to identify patterns, trends, and anomalies. This analytical process aims to discern patterns, detect trends, and identify anomalies within the dataset. Based on the analysis, the NMP (204) may decide how to respond to a disaster, such as prioritizing recovery efforts or optimizing network configurations. These decisions may involve prioritizing recovery efforts, optimizing network configurations, or implementing other strategic responses tailored to the situation. In some cases, the NMP (204) might directly trigger actions based on the analysis, such as sending configuration updates to network equipment through the configuration management module (216).

[0078] In an embodiment, the NMP (204) may utilize Application Programming Interfaces (APIs) provided by the MDB (202) to perform specific data retrieval and manipulation tasks. In some systems, the NMP (204) may directly access the MDB (202) to fetch needed data.

[0079] In an embodiment, the fault management module (206) may be implemented as an independent module or as part of the NMP. While the NMP (202) provides the overall framework and system to manage the network (106), the fault management module (206) continuously monitors the network (106) for various faults that can disrupt service. This enables the fault management module (206) to work in conjunction with, or extend, the functionality of existing NMPsystems. The fault management module (206) may detect faults occurring within the network (106). The fault management module (206) may continuously monitor the network (106) for various faults that can disrupt service. This monitoring may involve:• Analysing network performance metrics like call quality, data throughput, and signal strength.• Detecting abnormal behaviour in network equipment through sensor data or error messages. o Receiving notifications from other network components about detected issues.

[0080] Following the detection of a fault, the fault management module (206) may initiate a comprehensive process aimed at identifying its underlying cause. The fault management module (206) may examine historical data and fault patterns to isolate potential triggers with the historical data being fetched from the MDB (202). Furthermore, the fault management module (206) may cross-reference information from different network sections to delineate the affected area, employing diagnostic tools to extract additional insights. Once the root cause of the fault is identified, the fault management module (206) may promptly trigger alarm / alerts to other components of the system (108). The alerts may serve as vital notifications, facilitating swift responses to mitigate the fault's impact. Specifically, the alerts may prompt the NMP (204) to conduct further analysis and decisionmaking, alert the configuration management module (216) to potential equipment adjustments, and inform network operations personnel for investigative purposes or field technician dispatch if necessary.

[0081] In an embodiment, the performance management module (208) may monitor various metrics to assess the overall health and performance of the network, playing a crucial role in identifying areas most impacted by the disaster. The performance management module (208) may continuously gather data on variousnetwork performance metrics. These metrics may broadly be categorized into three areas:• Service Quality: Metrics like call quality (dropped calls, call setup time), data throughput (download / upload speeds), and latency (signal delay) indicate how well the network delivers services to the users (102).• Network Availability: Metrics like uptime (percentage of time the network is operational), packet loss (percentage of data packets not reaching their destination), and signal strength reflect the overall accessibility and reliability of the network.• Resource Utilization: Metrics like CPU and memory usage on network equipment, along with available bandwidth, provide insights into network capacity and potential bottlenecks.

[0082] In an aspect, the performance management module (208) may analyze the collected data to discern trends, anomalies, and potential performance issues within the network (106). The performance management module (208) gets this collected data from various network elements and systems it monitors, and from historical data stored in the MDB (202). This analytical process includes identifying areas characterized by consistently poor call quality, low data throughput, or weakened signal strength. Additionally, the performance management module (208) may detect sudden fluctuations in metrics that may signify network congestion, equipment malfunctions, or service disruptions, thus facilitating prompt intervention. By correlating performance data with other network information, such as geographic location, the performance management module (208) may pinpoint specific areas experiencing issues of no connectivity or link failure. This information can then be directly linked to the fault management module (206) for a more comprehensive diagnosis.

[0083] In an embodiment, the configuration management module (216) may facilitate recovery efforts by allowing remote adjustments to optimizeperformance and restore service. The configuration management module (216) may be a central repository for storing network equipment configurations. These configurations may define various parameters that govern the network's operation, including cell tower settings like transmission power, frequency bands, and cell size, routing protocols determining how data packets are forwarded across the network, security settings for access control and data encryption and service parameters like call quality prioritization or data throttling rules.

[0084] The radio optimization team (212) may focus on optimizing radio communication networks, ensuring efficient spectrum use, minimizing interference, and maximizing coverage and capacity. The radio planning team (210) may plan the deployment of radio communication networks, including site selection, antenna placement, and frequency planning, to meet coverage and capacity requirements. The sales and marketing team (214) may oversee the overall business aspects of the system (108), including strategy, planning, budgeting, and stakeholder communication. They may use insights from the processing unit (224) to make data-driven decisions and drive business growth.

[0085] Although FIG. 2A shows exemplary components of the system (108), in other embodiments, the system (108) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2A. Additionally, or alternatively, one or more components of the system (108) may perform functions described as being performed by one or more other components of the system (108).

[0086] FIG. 2B illustrates an exemplary block diagram (200B) of the system(108) for providing at least one network service in the service affected area, in accordance with an embodiment of the present disclosure.

[0087] Referring to FIG. 2B, the system (108) may include an interface(s) (222) that may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) (222) may facilitate communication to / from the system (108). Theinterface(s) (222) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, the processing unit (224) and the master database (202) . For the purposes of describing the block diagram (200B) of the system (108), the master database (202) is consistently referred to as a database (202).

[0088] In an embodiment, the processing unit (224) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing unit (224). 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 unit (224) may be processor-executable instructions stored on a non- transitory machine-readable storage medium, and the hardware for the processing unit (224) may include 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 unit (224). In such examples, the system (108) may include 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 unit (224) may be implemented by electronic circuitry.

[0089] Among other capabilities, the processing unit (224) may be configured to fetch and execute computer-readable instructions stored in a memory (220) of the system (108). The memory (220) 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 (220) may include 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.

[0090] In an embodiment, the database (202) may include data that may be either stored or generated as a result of functionalities implemented by the processing unit (224). In an embodiment, the database (202) may be separate from the system (108). In an embodiment, the database (202) may be indicative of including, but not limited to, a relational database, a distributed database, a cloudbased database, or the like.

[0091] In an embodiment, the system (108) is deployed within the network management platform (NMP) (204) that includes the processing unit (224) to perform the functionalities described herein.

[0092] In an embodiment, the receiving unit (218) may be configured to receive one or more input data associated with one or more affected network sites located in the service-affected area. The one or more input data may be obtained from one or more data sources. The one or more data sources may include the configuration management module (216), the fault management module (206), the performance management module (208), and the database (202). The one or more input data received may reflect various aspects of network performance, faults, topology, and prior configuration adjustments, facilitating a comprehensive understanding of the network environment.

[0093] In an embodiment, the one or more input data received by the receiving unit (218) may comprise a set of network parameters established by the network operator to represent the intended operational state of a network site, geographic locations of the affected network sites, a set of antenna parameters, a set of predefined parameter values, an Electrical tilt (E-Tilt) of each antenna associated with each affected network site, an antenna type, a type of the affected network site, and last updated configuration changes. Examples of the set of network parameters include but are not limited to. For instance, if a site’s current configuration shows an E-Tilt of +2° while the predefined parameter value is -2°, the discrepancy indicates a deviation that may affect coverage or interference performance. During recovery, such discrepancies are identified and corrected byaligning the actual values to the predefined parameter values to ensure the network site operates as intended. The processing unit (204) obtains the predefined parameter values from the MDB (202).

[0094] In an embodiment, the receiving unit (218) may further be configured to receive at least one user input from the user (102). The at least one user input may be utilized for modifying at least one configuration change that is determined by the processing unit (224). The system (108) may therefore support manual overrides or user-defined adjustments in specific cases where automation may be sub-optimal or require expert judgment.

[0095] In particular, the processing unit (224) may utilize historical and current data retrieved from the database (202), fault event logs from the fault management module (206), performance statistics from the performance management module (208), and configuration data from the configuration management module (216).

[0096] In an embodiment, the processing unit (224) may be configured to analyze the one or more input data to generate a list or a recovery list of the affected network sites. The recovery list is a prioritized compilation of affected network sites identified by the system (108) that may require urgent restoration of services.The generation of the recovery list may be based on one or more parameters such as an inter-antenna distance, a total number of handovers, a handover type, a handover threshold, a handover count, a handover latency, a signal strength, a set of cell selection parameters, a user location tracking parameter, and a network site operative parameter. The processing unit (224) may evaluate the one or more parameters in accordance with predefined rules or thresholds. The predefined rules or thresholds are either fetched from the MDB (202) or defined by a user input, and can be redefined or reprogrammed by network operations personnel as part of the configuration of the system (108) to determine which affected sites should be prioritized for recovery.

[0097] In an embodiment, the processing unit (224) may be configured to monitor at least one operative state of each affected network site after a predefined time interval and at regular intervals. The at least one operative state used hereinafter in the specification refers to a measurable parameter or condition indicating the functional status of a network site, such as power status, signal strength, configuration compliance, or connectivity, which helps determine whether the site is operating within acceptable thresholds post-recovery. The monitoring may be performed to identify one or more abnormalities, ensuring that postrecovery performance remains within acceptable operational parameters. The acceptable operational parameters are a predefined set of threshold values or performance criteria, such as signal quality, latency, throughput, power levels, and handover success rate, that a network site must satisfy to be considered functioning normally within the intended service standards.

[0098] In an embodiment, the processing unit (224) may also be configured to detect at least one recovery alarm notification corresponding to each of the one or more affected network sites from the one or more data sources. Such detection may serve as an early indicator of restoration or failure, allowing the system (108) to adapt its recovery strategy dynamically.

[0099] In an embodiment, the processing unit (224) may further be configured to determine at least one configuration change to be applied to each of the affected network sites of the generated recovery list using the analyzed input data. The at least one configuration change may include, but are not limited to, an antenna tilt configuration, a frequency configuration, a power adjustment, a network configuration change, a sector modification, a network slicing change, and a beamforming adjustment. The at least one configuration change is selected to restore and / or simply alter the network performance in the service affected area. The service affected area is a geographical region in which one or more network services are disrupted or degraded due to issues such as natural disasters, equipment failures, or configuration anomalies affecting one or more network sites within that region.

[0100] In an embodiment, the processing unit (224) may apply the at least one determined configuration change to each affected network site of the generated recovery list in order to provide the at least one network service. In addition, the processing unit (224) may initialize the handover between at least one affected network site selected from the recovery list and at least one active network site, wherein the handover involves transferring ongoing connections or service sessions from the affected site to a neighbouring active site to ensure uninterrupted service continuity during the recovery process. This ensures continuous service availability for the users ( 102) within the service-affected area by redirecting traffic to stable or enhanced nodes.

[0101] In an embodiment, the processing unit (224) may be configured to generate one or more reports summarizing the recovery information corresponding to each affected network site. The one or more generated reports may be utilized by the operators such as the radio optimization team (212), the radio planning team (210) or the sales and marketing team (214). These teams may use insights from the processing unit (224) to make data-driven decisions and drive business growth to assess the effectiveness of the recovery process, understand trends, and implement improvements in future incidents.

[0102] FIG. 3 illustrates an exemplary flow diagram of a method (300) for providing at least one network service in the service affected area, in accordance with an embodiment of the present disclosure. Each step of the method (300) may be performed by various units (e.g., the configuration management module (216), the fault management module (206), the performance management module (208), connected to the processing unit (224) of the system (108).

[0103] At step 302, gathering service affecting sites from the configuration management module (216). The method (300) begins by collecting data related to network sites that have reported service-affecting alarms. The data is retrieved from the configuration management module (216), which interfaces with the faultmanagement module (206) to identify sites experiencing critical faults or degradations.

[0104] At step 304, gathering geographic location of sites. The method (300) retrieves the geographical coordinates information of the impacted sites. The information may be sourced from the database (202) or location-aware inventory systems and provides spatial context for the recovery process.

[0105] At step 306, gathering physical properties of sites. The method (300) collects data on the physical attributes of each affected site. The physical properties may include electrical tilt (E-Tilt), antenna types, tower types, or other hardwarespecific characteristics. The data may be accessed via the configuration management module (216) or through network inventory databases coupled to the processing unit (224).

[0106] At step 308, manual feed if any. The method (300) allows for manual feed i.e. manual inputs from users like ground-level insights such as localized information from field engineers, urban constraints, or site-specific business priorities. The radio planning team (210) may feed in such data through an input interface or manual override mechanism.

[0107] At step 310, algorithm execution. The collected data is processed by the algorithm, implemented as part of the processing unit (224). The processing unit (224) applies the algorithm to analyse all gathered data, such as service-affecting status, geographic data, physical site parameters, and manual feeds, to identify which affected sites should be prioritized for recovery. The logic may use rulebased filters, weighted scoring, or AI / ML models, depending on deployment configuration.

[0108] At step 312, result, potential priority sites for recovery. The method (300) yields a prioritized list of sites deemed critical for immediate recovery. The list is generated based on the output of the algorithm and is presented to the operators for further action.

[0109] At step 314, recommended changes are executed through the configuration management module (216). Once priority sites are identified and recovery strategies are determined, the recommended changes (e.g., configuration adjustments, repairs) are initiated and executed through the configuration management module (216).

[0110] At step 316, reporting and monitoring. This step involves generating reports that summarize the recovery progress and establishing the system (108) for ongoing monitoring. This monitoring tracks the status of the restoration efforts and the performance of the recovered sites.

[0111] At step 318, addressing abnormalities. The method (300) actively monitors for abnormalities. The abnormalities may include failed command responses, unanticipated Key Performance Indicators (KPIs), or lack of recovery progress. Such abnormalities are flagged and either re-routed through automation or escalated for manual review.

[0112] At step 320, alarm monitoring. The method (300) continues to monitor alarms through the configuration management module (216). Any new faults or alerts detected during or after the recovery process are captured and correlated with existing recovery tasks to ensure ongoing situational awareness.

[0113] Finally, at step 322, closed-loop automation till full recovery. The entire process operates as a closed-loop system, implying continuous, iterative execution of these steps. The cycle continues, with ongoing assessment, analysis, and execution, until full-service recovery across all affected sites is achieved.

[0114] FIG. 4 illustrates an exemplary flow diagram of a method (400) for providing at least one network service in the service affected area, in accordance with an embodiment of the present disclosure. Each step of the method (400) may be performed by various units (e.g., the fault management module (206), the performance management module (208), and the configuration management module (216)).

[0115] At step 402, receiving, by the receiving unit (218), one or more input data associated with one or more affected network sites located in the service affected area from one or more data sources. The receiving unit (218) is configured to obtain the one or more input data. In an aspect, the one or more data sources may comprise the configuration management module (216), the fault management module (206), the performance management module (208), and a central repository, such as the Master Database (MDB) or the database (202). For example, the fault management module (206) detects service disruption data, such as alarms indicating equipment failure or loss of connectivity. The performance management module (208) collects network performance data, such as degraded signal strength, increased latency, or unusual traffic patterns. The MDB (202) provides static network parameters and historical data. The receiving unit (218) aggregates this diverse data to provide a comprehensive view of the affected network environment.

[0116] The one or more input data received by the receiving unit (218) comprise the set of network parameters, geographic locations of the affected network sites, the set of antenna parameters, the set of predefined parameter values, the Electrical tilt (E-Tilt) of each antenna associated with each affected network site, the antenna type, the type of the affected network site, and last updated configuration changes. For instance, the geographic location data allows for pinpointing the exact areas impacted by the disaster, while the E-Tilt and antenna type provide critical information about the physical configuration of antennas that might need adjustment for restoration. For example, an affected macrocell may have a value of E-Tilt of -3°, where the value represents the vertical downtilt angle of the antenna beam achieved through phase adjustments across antenna elements. The last configuration change might include a frequency reallocation.

[0117] The method (400) further comprises receiving, by the receiving unit (218), at least one user input from the user (102) for modifying the at least one determined configuration change. This allows for manual intervention or expert judgment to override or refine automated decisions, for example, if on-site personnel have unique information about localized damage or specific restorationpriorities not captured by automated sensors. In certain scenarios, expert users such as network planners or regional engineers may wish to intervene based on fieldlevel knowledge. For example, a planner may input that the E-Tilt change for Site D should be limited to -2° due to physical obstructions like a hill nearby. This input is integrated before finalizing changes.

[0118] At step 404, analyzing, by a processing unit (224), the one or more input data to generate a recovery list of the affected network sites (104) according to one or more parameters. The processing unit (224) analyzes the combined data received from the fault management module (206), performance management module (208), and the MDB (202). This analysis by the processing unit (224) involves evaluating the gathered input data against predefined rules or dynamic thresholds using the algorithm. The generation of the recovery list is performed by the processing unit (224) based on one or more parameters that enable the prioritization of recovery efforts. In an aspect, the one or more parameters comprise an inter-antenna distance, the total number of handovers, the handover type, the handover threshold, the handover count, the handover latency, the signal strength, the set of cell selection parameters, the user location tracking parameter, and the network site operative parameter. For example, the processing unit (224) might prioritize sites where a significant number of active user sessions (indicated by user location tracking parameter) were abruptly terminated, or where the signal strength has dropped below a critical threshold across multiple sectors. This comprehensive analysis culminates in generating a prioritized list of affected network sites that require immediate attention. For instance, if Site A has a higher number of dropped handovers and sub-optimal signal coverage compared to other affected sites, the Site A may be assigned a higher recovery priority. A scoring algorithm may be used, where each site is ranked based on cumulative weights of parameters like antenna density, user load in the area, and proximity to important coverage zones like hospitals or business districts.

[0119] The method (400) further comprises detecting, by the processing unit (224), the at least one recovery alarm notification corresponding to each of theone or more affected network sites (104) from the one or more data sources. Such detection by the processing unit (224), often from the fault management module (206), contributes to the real-time understanding of network status, aiding in the accurate determination of affected sites and their recovery priority.

[0120] At step 406, determining, by the processing unit (224), at least one configuration change to be applied to each of the affected network sites of the generated recovery list using the analyzed input data. The method (400) evaluates and recommends corrective actions. Based on the analysis of the input data, the processing unit (224) selects specific configuration adjustments for each prioritized affected network site (104). The configuration changes can include but are not limited to adjusting the electrical or mechanical antenna tilt, reallocating frequency bands, power boosting, modifying sector beam patterns, reconfiguring slicing parameters, or adjusting beamforming weights. For instance, if the analysis identifies severe signal interference, a frequency configuration change to an alternative channel might be determined. If a particular sector's coverage is found to be deficient, an antenna tilt configuration change to broaden or redirect coverage could be determined. In an instance, if a particular site has an E-Tilt of -6° and serves a region now requiring higher coverage, the processing unit (224) may suggest modifying the E-Tilt to -3° and increasing transmission power by 2 dB. These configuration changes are tailored based on both site characteristics and network-level KPIs.

[0121] At step 408, providing, by the processing unit (224), the at least one network service to each of the affected network sites (104) of the generated recovery list by applying the determined at least one determined configuration change. The processing unit (224) applies the determined changes by transmitting instructions to the configuration management module (216), which then implements the necessary adjustments on the network equipment. For example, commands are sent to reconfigure cell tower settings, re-establish routing protocols, or adjust power levels. In addition, the processing unit (224) is configured to initiate a handover between at least one affected network site (104) selected from thegenerated recovery list (once its service is restored or improved) and at least one active network site. This handover initiation, managed by the processing unit (224), ensures continuous service availability for users (102) within the service-affected area by dynamically redirecting the User Equipment (UE) (104) traffic to stable or newly enhanced nodes, thereby maintaining connectivity during and after the restoration process. In parallel, the method (400) may trigger dynamic handovers or load balancing procedures between affected and nearby operational sites to temporarily maintain service continuity while the recovery is in progress. For instance, if Site B is under recovery but cannot immediately serve users, a handover may be initiated to its neighbouring Site C, which has sufficient spare capacity. This allows uninterrupted service during configuration application and validation.

[0122] In an embodiment, the method (400) further comprises monitoring, by the processing unit (224), at least one operative state of each affected network site (104) after a predefined time interval and at regular intervals to identify one or more abnormalities. The processing unit (224), potentially in conjunction with the performance management module (208), continuously observes the performance and operational status of the recovered sites so that post-recovery performance remains within acceptable operational parameters and to detect any new or recurring issues, such as persistent signal degradation, unexpected increases in error rates, or failures in the new configuration settings.

[0123] In a further embodiment, the method (400) comprises generating, by the processing unit (224), one or more reports summarizing the recovery information corresponding to each affected network site (104). These one or more generated reports provide comprehensive insights into the restoration efforts, including the precise duration of outage, the specific configuration changes applied, the observed resulting service improvements (e.g., before-and-after throughput figures), and any remaining abnormalities. The one or more generated reports may be utilized by various operators and internal teams, such as the radio optimization team (212), the radio planning team (210), or the sales and marketing team (214), to facilitate informed decision-making and strategic responses. For example, theradio optimization team (212) can use the reports to fine-tune network performance post-recovery, while the radio planning team (210) can assess the effectiveness of site selection and antenna placement in disaster scenarios for future network resilience planning. For example, the report for Site E may note: "E-Tilt changed from -4° to -2°", "Handover redirected to Site F for 30 minutes”, “Post-recovery RSRP improved by 6 dB."

[0124] FIG. 5 illustrates a computer system (500) in which or with which the embodiments of the present disclosure may be implemented.

[0125] As shown in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), communication port(s) (560), and a processor (570) . A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port for use with a modem -based 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 port(s) (560) may be chosen depending on a network (106), such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.

[0126] The main memory (530) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution which can be used to store information and / or instructions. Exemplary mass storage device (550) includes, but is 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), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.

[0127] The bus (520) communicatively couples the processor (570) with the other memory, storage, and communication blocks. The bus (520) may be, e.g., a Peripheral Component Interconnect / Peripheral Component Interconnect Extended 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 (570) to the computer system.

[0128] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (520) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (560). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.

[0129] In an exemplary embodiment, a system for providing at least one network service in a service affected area is disclosed. The system includes a receiving unit configured to receive one or more input data associated with one or more affected network sites located in the service affected area from one or more data sources. The system further includes a processing unit configured to analyze the one or more input data to generate a recovery list of the affected network sites according to one or more parameters. The system further determines at least one configuration change to be applied to each of the affected network sites of the generated recovery list using the analyzed input data. The system further provides the at least one network service to each of the affected network sites of the generated recovery list by applying the determined at least one configuration change andinitialize a handover between at least one affected network site selected from the generated recovery list and at least one active network site

[0130] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for providing at least one network service in a service affected area. The method includes receiving, by a receiving unit, one or more input data associated with one or more affected network sites located in the service affected area from one or more data sources. The method comprises analyzing, by a processing unit, the one or more input data to generate a recovery list of the affected network sites according to one or more parameters. The method comprises determining, by the processing unit, at least one configuration change to be applied to each of the affected network sites of the generated recovery list using the analyzed input data. The method comprises providing, by the processing unit, the at least one network service to each of the affected network sites of the generated recovery list by applying the determined at least one configuration change and initiating a handover between at least one affected network site selected from the generated recovery list and at least one active network site.

[0131] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made, and 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 is to be implemented merely as illustrative of the disclosure and not as a limitation.

[0132] The present disclosure provides a technical advancement in disaster management and network service restoration by automatically identifying and prioritizing affected telecom sites for recovery. Unlike traditional manual orreactive recovery processes, the present disclosure enables rapid, data-driven, and prioritized restoration of critical communication services following natural calamities. The present disclosure integrates diverse real-time network data with physical site properties and local knowledge to generate an optimized recovery plan. The present disclosure significantly reduces network downtime, improves service reliability, and enhances customer trust in the network service provider during emergency situations.ADVANTAGES OF THE PRESENT DISCLOSURE

[0133] The present disclosure described herein above has several technical advantages including, but not limited to, the realization of the system and the method that:1. enables a swift response to network disruptions caused by natural disasters by automating the detection of service disruptions and prioritizing recovery efforts;2. optimizes the allocation of resources and prioritizes the restoration of service-disrupted network elements, ensuring that essential services are quickly reestablished for users in the affected area;3. proactive monitoring of the restoration process by continuously analyzing performance metrics and generating reports; and4. enhance the overall user experience.

Claims

We claim:

1. A method (400) for providing at least one network service in a service affected area, the method (400) comprising: receiving (402), by a receiving unit (218), one or more input data associated with one or more affected network sites located in the service affected area from one or more data sources; analyzing (404), by a processing unit (224), the one or more input data to generate a recovery list of the affected network sites according to one or more parameters; determining (406), by the processing unit (224), at least one configuration change to be applied to each of the affected network sites of the generated recovery list using the analyzed input data; and providing (408), by the processing unit (224), the at least one network service to each of the affected network sites of the generated recovery list by applying the determined at least one configuration change and initiating a handover between at least one affected network site selected from the generated recovery list and at least one active network site.

2. The method (400) as claimed in claim 1, wherein the one or more input data comprise a set of network parameters, geographic locations of the affected network sites, a set of antenna parameters, a set of predefined parameter values, an Electrical tilt (E-Tilt) of each antenna associated with each affected network site, an antenna type, a type of the affected network site, and last updated configuration changes.

3. The method (400) as claimed in claim 1, further comprising receiving, by the receiving unit (218), at least one user input from a user (102) for modifying the at least one determined configuration change.

4. The method (400) as claimed in claim 1, wherein the at least one configuration change comprises an antenna tilt configuration, a frequency configuration, a power adjustment, a network configuration change, a sector modification, a network slicing change, and a beamforming adjustment.

5. The method (400) as claimed in claim 1, wherein the one or more data sources comprise a configuration management module (216), a fault management module (206), a performance management module (208), and a database (202).

6. The method (400) as claimed in claim 1, wherein the one or more parameters comprise an inter-antenna distance, a total number of handovers, a handover type, a handover threshold, a handover count, a handover latency, a signal strength, a set of cell selection parameters, a user location tracking parameter, and a network site operative parameter.

7. The method (400) as claimed in claim 1, further comprising generating, by the processing unit (224), one or more reports summarizing the recovery information corresponding to each affected network site.

8. The method (400) as claimed in claim 1, further comprising monitoring, by the processing unit (224), at least one operative state of each affected network site after a predefined time interval and at regular intervals to identify one or more abnormalities.

9. The method (400) as claimed in claim 1, further comprising detecting, by the processing unit (224), at least one recovery alarm notification corresponding to each of the one or more affected network sites from the one or more data sources.

10. A system (108) for providing at least one network service in a service affected area, the system (108) comprises: a receiving unit (218) configured to receive one or more input data associated with one or more affected network sites located in the service affected area from one or more data sources; a processing unit (224) configured to: analyze the one or more input data to generate a recovery list of the affected network sites according to one or more parameters; determine at least one configuration change to be applied to each of the affected network sites of the generated recovery list using the analyzed input data; and provide the at least one network service to each of the affected network sites of the generated recovery list by applying the determined at least one configuration change and initialize a handover between at least one affected network site selected from the generated recovery list and at least one active network site.

11. The system (108) as claimed in claim 10, wherein the one or more input data comprise a set of network parameters, geographic locations of the affected network sites, a set of antenna parameters, a set of predefined parameter values, an Electrical tilt (E-Tilt) of each antenna associated with each affected network site, an antenna type, a type of the affected network site, and last updated configuration changes.

12. The system (108) as claimed in claim 10, wherein the receiving unit (218) is configured to at least one user input from a user (102) for modifying the at least one determined configuration change.

13. The system (108) as claimed in claim 10, wherein the at least one configuration change comprises an antenna tilt configuration, a frequency configuration, a power adjustment, a network configuration change, a sector modification, a network slicing change, and a beamforming adjustment.

14. The system (108) as claimed in claim 10, wherein the one or more data sources comprise a configuration management module (216), a fault management module (206), a performance management module (208), and a database (202).

15. The system (108) as claimed in claim 10, wherein the one or more parameters comprise an inter-antenna distance, a total number of handovers, a handover type, a handover threshold, a handover count, a handover latency, a signal strength, a set of cell selection parameters, a user location tracking parameter, and a network site operative parameter.

16. The system (108) as claimed in claim 10, wherein the processing unit (224) is further configured to generate one or more reports summarizing the recovery information corresponding to each affected network site.

17. The system (108) as claimed in claim 10, wherein the processing unit (224) is further configured to monitor at least one operative state of each affected network site after a predefined time interval and at regular intervals to identify one or more abnormalities.

18. The system (108) as claimed in claim 10, wherein the processing unit (224) is further configured to detect at least one recovery alarm notification corresponding to each of the one or more affected network sites from the one or more data sources.

19. 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 execute a method (400) for providing at least one network service in a service affected area, the method (400) comprising: receiving, by a receiving unit (218), one or more input data associated with one or more affected network sites located in the service affected area from one or more data sources; analyzing, by a processing unit (224), the one or more input data to generate a recovery list of the affected network sites according to one or more parameters; determining, by the processing unit (224), at least one configuration change to be applied to each of the affected network sites of the generated recovery list using the analyzed input data; and providing, by the processing unit (224), the at least one network service to each of the affected network sites of the generated recovery list by applying the determined at least one configuration change and initiating a handover between at least one affected network site selected from the generated recovery list and at least one active network site.

Images