Method and system for managing network services for customers in a network

Abstract

The present disclosure provides a method (600) and a system (108) for managing network services for customers in a network (106). The method involves identifying customers utilizing the network services based on one or more predefined criteria. The method further includes storing customer data in a data sheet and analyzing the stored data to determine a bulk operation to be performed for the identified customers. The method includes sending at least one of a suspend application programming interface (API) request and a resume API request to a network server based on the determination. The method also includes suspending the network services for the customers or resuming the network services for the customers based on the received request. The method and the system enable automated, large-scale, and resource-efficient network service management with enhanced reliability and operational accuracy.

Description

METHOD AND SYSTEM FOR MANAGING NETWORK SERVICESFOR CUSTOMERS IN A NETWORKRESERVATION 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 method and a system for managing one or more network services for a plurality of customer accounts in a communication network.DEFINITION

[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 ‘Bulk suspension tool’ used hereinafter in the specification refers to a component that is configured to suspend and / or resume network services for a large number of customers at the same time or in a bulk.

[0005] The term ‘Suspend network services’ used herein hereinafter in the specification refers to a process of temporarily restricting or disabling access to one or more network services associated with customers. This includes termination of activedata sessions, blocking of new service requests, and updating of service status indicators in corresponding network databases to prevent unauthorized or unpaid service usage.

[0006] The term “Resume network services” used herein refers to a process of reinstating access to one or more network services previously suspended for customers. This includes reactivating session permissions, restoring valid subscription or rental plan parameters, updating service status indicators in network databases, and enabling the customer to access network resources again.

[0007] The term ‘PGW’ used hereinafter in the specification refers to a provisioning gateway. The PGW manages customer data and handles data flow between customers and the network.

[0008] The term ‘CHF-BNG node’ used hereinafter in the specification refers to a charging function and broadband network gateway. Upon receiving a suspend API request or a resume API request, the CHF-BNG updates the policy enforcement point to block service packets or resume service packets.

[0009] The term ‘API’ used hereinafter in the specification refers to an application programming interface. The API allows communication and execution of commands such as suspending and resuming the network services.

[0010] The term ‘Suspend API request’ used hereinafter in the specification refers to a command instructing the suspension of the customer's network access based on specific conditions.

[0011] The term ‘Resume API request’ used hereinafter in the specification refers to a command instructing the resumption of previously suspended network access for customers based on specific conditions.

[0012] These definitions are in addition to those expressed in the art.BACKGROUND

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

[0014] In telecommunications, effective management of network services is essential for ensuring operational efficiency, protecting revenue loss, and maintaining service integrity across large subscriber bases. Network operators often manage millions of subscribers to provide network services, and one of their primary concerns is revenue loss due to unauthorized or fraudulent use of network services. The network operators often face challenges in controlling access to their network services, particularly when it comes to preventing unauthorized use or fraud. Even after identifying the subscribers or customers, most network operators face challenges in restricting or stopping network services immediately for fraudulent cases. At present, the network operators often rely on manual graphical user interface (GUI)-based tools, which are used to identify and suspend the subscribers manually (for example, one by one). However, they are often slow and may struggle with performance issues when processing a high volume of data. Additionally, the GUI-based tools often consume a large number of system resources during processing, resulting in slow results, leading to poor operational efficiency.

[0015] There is, therefore, a need in the art to provide a method and a system that can mitigate the disadvantages of the prior art.SUMMARY OF THE DISCLOSURE

[0016] In an exemplary embodiment, a method for managing one or more network services for a plurality of customers in a communication network is described. The method includes identifying, by a processing unit, the plurality of customer accounts utilizing the one or more network services based on one or more predefined operational criteria. The method includes storing, by the processing unit, service- related data associated with the plurality of customer accounts in at least one data structure, based on the identification. The method includes determining, by the processing unit, at least one bulk management operation to be executed for the identified plurality of customer accounts based on the stored service-related data. The method includes transmitting, by the processing unit, one or more control requests via an application programming interface (API) to at least one network server based on the determination. Further, the at least one network server executes the at least one bulk management operation for the identified plurality of customer accounts based on the received one or more control requests.

[0017] In some embodiments, the predefined operational criteria includes one or more business, technical, regulatory, or operational conditions, including but not limited to subscription expiry, fraud detection, payment status, service policy violation, or system-generated trigger.

[0018] In some embodiments, the service-related data includes one or more data elements associated with each of the plurality of customer accounts, including but not limited to unique identifiers, current service status, information indicative of the bulk operation to be performed, types or categories of network services associated with the plurality of customers, and one or more timestamps indicating data update events.

[0019] In some embodiments, the one or more network services include at one or more communication, data, media, or value-added services.

[0020] In some embodiments, the one or more control requests is one of a stop service request or a resume service request.

[0021] In some embodiments, the at least one bulk management operation is automatically executed through an integrated workflow comprising data retrieval, update generation, and service control command transmission

[0022] In some embodiments, the at least one bulk management operation is at least one of: suspending, resuming, activating, deactivating, throttling, or modifying the one or more network services.

[0023] In some embodiments, the method includes notifying, by the at least one network server, at least one network gateway node about a service status related to the one or more network services for the plurality of customer accounts retrieving, by the at least one network gateway node, subscriber information associated with the plurality of customer accounts from a database validating, by the at least one network gateway node, the service status associated with the plurality of customer accounts based on one or more parameters; and updating, by the at least one network gateway node, one or more network configurations associated with the plurality of customer accounts based on the validated service status.

[0024] In another exemplary embodiment, a system for managing one or more network services for a plurality of customer accounts in a communication network is described. The system includes a processing unit configured to identify the plurality of customer accounts utilizing the one or more network services based on one or more predefined operational criteria, store service-related data associated with the plurality of customer accounts in at least one data structure, based on the identification, determine at least one bulk management operation to be executed for the plurality of customer accounts based on the stored service-related data and transmit one or more control request via an application programming interface to at least one network serverbased on the determination. Further, the at least one network server is configured to exceute the at least one bulk management operation for the plurality of customer accounts based on the received one or more control requests.

[0025] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The method includes identifying, by a processing unit, the plurality of customer accounts utilizing the one or more network services based on one or more predefined operational criteria. The method includes storing, by the processing unit, service-related data associated with the plurality of customer accounts in at least one data structure, based on the identification. The method includes determining, by the processing unit, at least one bulk management operation to be executed for the identified plurality of customer accounts based on the stored service-related data. The method includes transmitting, by the processing unit, one or more control requests via an application programming interface (API) to at least one network server based on the determination. Further, the at least one network server executes the at least one bulk management operation for the identified plurality of customer accounts based on the received one or more control requests.

[0026] 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.OBJECTIVES OF THE PRESENT DISCLOSURE

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

[0028] An objective of the present disclosure is to provide a system and a method for suspending or resuming network services for customers.

[0029] Another objective of the present disclosure is to provide a bulk suspension tool that can be customized to meet specific criteria or conditions, offering control over affected entities.

[0030] Another objective of the present disclosure is to offer efficiency in a workflow of suspending or resuming network services by using the bulk suspension tool that can be integrated with scripts to pull data from worksheets (for example, Excel sheets), apply changes, and push updates, all within a single automated workflow.

[0031] Another objective of the present disclosure is to provide an optimized feature that can handle large-scale operations efficiently.

[0032] 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.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

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

[0034] FIG. 1 illustrates an exemplary network architecture in which or with a system configured for managing one or more network services for a plurality ofcustomer accounts in a communication network may be implemented, in accordance with embodiments of the present disclosure.

[0035] FIG. 2 illustrates an exemplary block diagram of the system configured for managing the one or more network services for the plurality of customer accounts in the communication network, in accordance with embodiments of the present disclosure.

[0036] FIG. 3 illustrates an exemplary system architecture for managing the one or more network services for the plurality of customer accounts in the communication network, in accordance with an embodiment of the present disclosure.

[0037] FIG. 4 illustrates an exemplary process flow for suspending the one or more network services for the plurality of customer accounts in the communication network, in accordance with an embodiment of the present disclosure.

[0038] FIG. 5 illustrates an exemplary process flow for resuming the one or more network services for the plurality of customer accounts in the communication network, in accordance with an embodiment of the present disclosure.

[0039] FIG. 6 illustrates an exemplary flow diagram of a method for managing the one or more network services for the plurality of customer accounts in the communication network, in accordance with an embodiment of the present disclosure.

[0040] FIG. 7 illustrates an exemplary computer system in which or with which the embodiments of the present disclosure may be implemented.

[0041] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102 - User(s)104 - User Equipments (UEs)106 - Network 108 - System200 -Block Diagram202 - Processor(s)204 - Memory206 - Interface(s) 208 - Processing Unit210 - Database300 - System Architecture302 - Bulk Suspension tool304 - Network Server 306 - Suspend Module308 - Resume Module310 - Database400 - Process Flow Diagram500 - Process Flow Diagram600 - Method Flow Diagram700 - Computer System710 - External Storage Device720 - Bus730 - Main Memory740 - Read Only Memory750 - Mass Storage Device760 - Communication Port(S)770 - ProcessorDETAILED DESCRIPTION

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

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

[0044] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of the 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.

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

[0046] 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 ordinaryskill 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.

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

[0048] The terminology used herein is to describe particular embodiments only and is not intended to limit 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 otherequivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

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

[0050] In conventional techniques, network operators often rely on manual graphical user interface (GUI)-based tools used to identify and suspend subscribers manually. These GUI-based tools can stop access to network services; however, they are often slow and may cause performance issues when processing a high volume of data. Moreover, the GUI-based tools consume a large amount of system resources during processing, leading to slow execution and poor operational efficiency. To address the challenges associated with conventional techniques, the present disclosure provides a bulk suspension tool for suspending or resuming network services for customers efficiently. The bulk suspension tool enables network operators to immediately stop or resume a subscriber’s service if the customer’s recharge has already expired but is still using the services. The bulk suspension tool allows the network operators to suspend or resume services for a large number of subscribers simultaneously, even when different customers have different suspension codes. In cases where customers continue using services after their recharge expiry and the operator is unable to stop them, this tool provides an easy and reliable method to stop or resume services instantly. The bulk suspension tool ensures quick suspension of data services to prevent revenue loss and can also resume services if suspensions are notremoved due to technical reasons. Furthermore, the bulk suspension tool automates the suspension and resumption process, significantly reducing the time and manual effort required compared to handling each suspension individually. Performing multiple suspensions in a single operation is faster than processing them one at a time. The bulk suspension tool can be customized to meet specific criteria or conditions, offering greater control over which customers are affected. The bulk suspension tool ensures that all specified customers are suspended simultaneously, maintaining uniformity and control across the affected users. Additionally, the bulk suspension tool integrates seamlessly with other systems and scripts, enabling operators to pull data from an Excel sheet, apply changes, and push updates in a single automated workflow. Unlike GUI- based tools, the bulk suspension tool efficiently handles large-scale operations and requires fewer system resources, making it ideal for use on servers or in environments where resource optimization is critical.

[0051] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0052] FIG. 1 illustrates an exemplary network architecture 100 in which or with which a system 108 configured managing one or more network services for a plurality of customer accounts in a communication network 106 may be implemented, in accordance with embodiments of the present disclosure.

[0053] In an embodiment, the network architecture 100 may include one or more user equipment (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. Further, the user 102 may correspond to a network administrator or a network service provider. Similarly, a person of ordinary skill in the art will understand that one or more UEs 104-1, 104- 2... 104-N may be individually referred to as the UE 104 and collectively referred to asthe UEs 104. Although three UEs 104 are depicted in FIG. 1, however, any number of the UEs 104 may be included without departing from the scope of the ongoing description.

[0054] In another implementation, the UE 104 may function as smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE 104 may include, but is not limited to, smart phones, 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 UE 104 may include, but is not limited to, intelligent, multisensing, network- connected devices, which 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.

[0055] In an embodiment, the UE 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, wherein the UE 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. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0056] In FIG. 1, the UE 104 may communicate with the system 108 via a telecommunication network 106 (interchangeably referred to as a network 106). In order to establish communication, initially, the telecommunication network 106 is configured to receive a connection request from the UE 104. In response to receiving the connection request, the telecommunication network 106 is configured to send an acknowledgment of the connection request to the UE 104. Further, a plurality of signals is transmitted in response to the connection request. Based on the connection request, the sessions are created in the telecommunication network 106. In an embodiment, the network 106 includes at least one of the 4G network, the 5G network, the 6G network, or the like. The telecommunication network 106 may enable the UE 104 to communicate with other devices in the network architecture 100 and / or with the system 108.

[0057] 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), 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. In another embodiment, the telecommunication network 106 includes, by way of example but not limitation, 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.

[0058] In an implementation, the system 108 may be a bulk adjustment tool. In one embodiment, when the UE 104 communicates with the system 108 (i.e., the bulk suspension tool), the process for managing the suspension or resumption of network services is initiated. The UE 104 represents a subscriber device that is currently accessing network services through the operator’s network infrastructure. Upon detecting that the recharge validity of the UE 104 has expired, but the subscriber is still utilizing network services, the system 108 identifies the subscriber as a target for suspension. The system 108 reads the data of such customers, including relevant service identifiers and suspension codes, from a network database. In cases where multiple subscribers have different suspension codes, the system 108 retrieves and categorizes each accordingly.

[0059] After retrieving all the required customer-related data, the system 108 stores it in a datasheet and initiates a bulk operation. The system 108 then sends appropriate Application Programming Interface (API) requests to a Packet Gateway (PGW) server to either stop or resume the subscriber’s network services based on the operational command. Once the stop or resume requests are executed, the PGW server updates the subscriber’s service status in their corresponding database servers. Subsequently, a Charging Function (CHF) and Broadband Network Gateway (BNG) node fetch the updated information from the database servers to ensure synchronization and consistency across the network.

[0060] Furthermore, when a subscriber wishes to resume network services after suspension, the UE 104 again communicates with the system 108 through a service request. The system 108 follows the same operational flow, sending resume API requests to the PGW node servers, which in turn reactivate the subscriber’s access to network services and update the corresponding records in the database servers. The system 108 ensures an automated, efficient, and uniform mechanism for managing service suspension and resumption across multiple subscribers simultaneously.

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

[0062] FIG. 2 illustrates an exemplary block diagram of the system 108 configured for managing the one or more network services for the plurality of customer accounts in the communication network 106, in accordance with an embodiment of the present disclosure.

[0063] In an embodiment, the system 108 may include one or more processor(s) 202. The one or more processor(s) 202 may be implemented as one or more microprocessors, microcomputers, 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 a 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 include any non-transitory storage device including, for example, volatile memory such as a Random- Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

[0064] In an embodiment, the system 108 may include an interface(s) 206. The interface(s) 206 may include a variety of interfaces, for example, interfaces for data input and output devices (VO), storage devices, and the like. The interface(s) 206 mayfacilitate communication through the system 108. The interface(s) 206 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, a processing unit 208 and a database 210.

[0065] In an implementation, the processing unit 208 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the system 108. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing unit 208 may be processor-executable instructions stored on a non- transitory machine-readable storage medium and the hardware for the processing unit 208 may include a processing resource (for example, the one or more processors 202) to execute such instructions. In one implementation, the processing unit 208 and the processor(s) 202 may be operatively coupled to each other and to the interface(s) 206 to enable seamless data acquisition, decoding, and dispatching of received information for further handling or storage.

[0066] In an embodiment, the system 108 facilitates suspending or resuming the one or more network services for the plurality of customer accounts. Herein, suspending the one or more network services refers to the temporary deactivation or restriction of access to certain or all network services, whereas resuming the one or more network services refers to bringing the customer accounts back to their associated network services status after the suspension or restoration of access to the one or more network services or the customers accounts whose network services were previously suspended. In an aspect, the one or more network services may include one or more communication, data, media, or value-added services. In an example, the one or more network services may be voice call services, short message services (SMS), multimediamessaging services (MMS), data or internet services, video streaming services, and similar.

[0067] In an implementation, the system 108 may be interchangeably referred to as a bulk suspension tool. The bulk suspension tool facilitates the automatic identification, suspension and resumption of the one or more network services for the plurality of customer accounts. The bulk suspension tool automates the process of suspending or resuming the one or more network services, significantly reducing the time and manual effort required compared to handling each suspension individually. It should be appreciated that employing the bulk suspension tool allows for the simultaneous processing of multiple suspensions in one operation, which is considerably more efficient and faster than processing them one at a time.

[0068] In an embodiment, the processing unit 208 is configured to identify the plurality of customer accounts utilizing the one or more network services based on one or more predefined operational criteria. The one or more predefined operational criteria refer to the specific conditions or rules that are predefined by a network operator to determine when the one or more network services for the plurality of customer accounts should be suspended or resumed. In an aspect, the one or more predefined operational criteria may include one or more business, technical, regulatory, or operational conditions, including but not limited to subscription expiry, fraud detection, payment status, service policy violation, or system-generated trigger. In an example, the one or more predefined criteria for suspending the customer accounts may be an expired recharge, detection of fraudulent activity, violation of terms of service, payment issues, government orders, legal compliance, and technical issues and the like. Additionally, the one or more predefined criteria for resuming the network services for the plurality of customer accounts may include renewal of recharge, resolution of fraudulent activity, confirmation of payment, compliance with legal orders, resuming requestsfrom the customers, clearance of orders from the government, resolution of technical issues, and similar.

[0069] In order to identify the plurality of customer accounts, the processing unit 208 may continuously monitor service-related data of each customer accounts, such as service usage records, recharge status, billing information, network access logs and similar information, according to one or more predefined operational criteria. For example, upon receiving a periodic or an event-based trigger, the processing unit 208 executes a rule-based or algorithmic matching process to compare service-related data against the one or more predefined operational criteria. For instance, customer accounts or subscribers whose recharge validity period has expired but are still generating active data sessions are automatically flagged as unauthorized user accounts. Similarly, detection of irregular usage patterns, mismatched customer identities, or excessive data consumption may indicate fraudulent activity, prompting the identified customer to be included in a suspension list. In case of payment issues, such as failed auto-renewal or outstanding bills, the corresponding customer accounts are also identified. For government or legal compliance cases, the system 108 may automatically extract a list of targeted customers as per official directives. Additionally, in the event of technical issues, for instance, when a malfunctioning customer's device causes network interference, the affected customers are temporarily identified for suspension until the issue is resolved.

[0070] In an embodiment, based on the identification, the processing unit 208 is configured to store service-related data associated with the plurality of customer accounts in at least one data structure. In an aspect, the at least one data structure may include but not limited to a datasheet. The datasheet serves as a centralized repository or tabular dataset that maintains the latest operational state and service-related details of all identified customers. This datasheet may be stored in a network management database such as the database 210, a centralized data server, or within a dedicated datastorage module associated with the system 108, ensuring secure access and integrity of customer-related service data. In an aspect, the service-related service data includes one or more data elements associated with each of the plurality of customer accounts, including but not limited to unique identifiers, current service status, information indicative of the bulk operation to be performed, types or categories of network services associated with the plurality of customers, and one or more timestamps indicating data update events. For example, key parameters such uniquely associated with the each customer (for example, International Mobile Subscriber Identity (IMSI), Mobile Station International Subscriber Directory Number (MSISDN), or account number), a current service status of the plurality of customers (such as active, suspended, or resumed), details of the bulk management operation to be executed, (such as whether the identified customer is marked for suspension, resumption, or modification of a service), a type of network service affected (for example, data, voice, or messaging). Further, the processing unit 208 may also generate a timestamp for each record to indicate the exact time and date of the last update made to the service-related data. The processing unit 208 may dynamically update the at least one data structure whenever a new set of customer accounts is identified or when any operational command (such as ‘stop’ or ‘resume’) is executed. Once updated, the at least one data structure acts as the primary input for the system 108.

[0071] In an example, consider a situation where 5,000 customer accounts have been identified for suspension due to expired recharge and non-payment issues. The processing unit 208 retrieves each subscriber’s details, such as subscription ID, MSISDN, and records them in the datasheet. For every subscriber, the system 108 updates the current service status field to ‘Pending Suspension’, specifies the bulk operation type as stop services. Further, the processing unit 208 generates a timestamp (e.g., date and time) for each record to indicate when the data was last updated.

[0072] In an embodiment, the processing unit 208 is configured to determine at least one bulk management operation to be executed for the identified plurality of customer accounts based on the stored service-related data. The at least one bulk management operation is one of: suspending, resuming, activating, deactivating, throttling, or modifying the one or more network services. In an aspect, the at least one bulk management operation is automatically executed through an integrated workflow comprising data retrieval, update generation, and service control command transmission. The processing unit 208 examines the current service status (for example, active, expired, suspended, or pending resumption) and correlates it with operational policies defined by the network operator. If the customer’s record indicates that the recharge validity has expired, fraudulent activity has been detected, or a regulatory order mandates disconnection, the processing unit 208 automatically selects suspend service as the bulk operation. Conversely, if a previously suspended subscriber has completed payment, renewed a subscription, or the technical issue causing suspension has been resolved, the processing unit 208 selects resume service as the bulk operation. For example, the datasheet contains 8,000 customer account records and out of these, 5,000 records indicate expired recharge with current service status marked as “active”, while 3,000 records show “payment received” with service status marked as “suspended.” The processing unit 208 analyzes this data and determines that the appropriate bulk operation for the 5,000 customer accounts is “suspend service” to prevent unauthorized usage, while for the remaining 3,000 customer accounts, the operation is “resume service” since their dues have been cleared.

[0073] In an embodiment, the processing unit 208 is configured to transmit one or more control request via an application programming interface (API) to at least one network server based on the determination. In an aspect, the one or more control request may be one of a stop service request or a resume service request. For example, once the at least one bulk management operation type is determined, the processing unit 208 transmits the respective application programming interface (API) request,such as a SUSPEND API request or a RESUME API request, to the at least one network server, such as a provisioning gateway (PGW) server, for further implementation. The network server (i.e., the PGW server) acts as the primary control point responsible for managing customers sessions and enforcing service-level policies. When the stop service request is received, the PGW server immediately terminates the ongoing data sessions or restricts access to specific network services for the identified customers. Conversely, when the resume service request is received, the PGW server reactivates the customer’s session, restoring access to authorized network services. Following the execution of either command, the at least one network server (i.e., the PGW server) updates all associated customer information, such as service state, session identifiers, and data usage status, in its internal database servers, ensuring that the latest service state is accurately reflected within the database.

[0074] In an aspect, the SUSPEND API request may trigger a suspend module within the network server to suspend the one or more network services for the identified plurality of customers. The suspend module processes the SUSPEND API request and halts the flow of data packets between the customer’s device and the network 106. The network server may further update its particular internal database servers to reflect the service-related data and set the one or more network service statuses to ‘SUSPEND’, indicating that the identified plurality of customers are required to be suspended. Alternatively, if the RESUME API request is received for the identified plurality of customer accounts then the at least one network server updates this information in the internal database servers and sets the service status as ‘RESUME’, indicating that the identified plurality of customer accounts are required to be resumed.

[0075] Further, the at least one network server is configured to notify at least one network gateway node, such as a charging function broadband network gateway (CHF-BNG) node. The notification to the CHF-BNG node involves sending a signal or message that includes the newly updated service status for the identified plurality ofcustomer accounts. For example, the service status for the customers that is marked as ‘SUSPEND’ or the service of the customer accounts that has been marked as ‘RESUME’. The CHF-BNG nodes retrieve (or fetch) the updated subscriber information from the PGW’s database servers. The CHF component validates charging and balance-related parameters to ensure that service resumption or suspension aligns with billing and policy rules. Simultaneously, the CHF-BNG node performs the necessary configuration changes at the access network layer, such as updating routing tables, modifying Quality of Service (QoS) parameters, or blocking / unblocking service flows for the affected subscribers.

[0076] In an exemplary scenario, 2,000 customer accounts are identified for suspension due to expired recharge. Once the processing unit 208 sends the “SUSPEND” API request, the PGW server terminates all active data sessions for the identified customers and marks their status as “suspended” in the database. The CHF- BNG nodes then fetch this updated data, where the CHF validates the charging status (e.g., no active balance remaining) and the BNG enforces the access control changes to ensure complete disconnection from the network. Similarly, for resumption of services, once the customers recharge their accounts or fulfill the required criteria, the processing unit 208 sends a “RESUME” API request to the PGW server. The PGW server reactivates the suspended data sessions and updates the corresponding service status in its database as “active.” Subsequently, the CHF-BNG nodes fetch the updated data, where the CHF ensures the billing and balance are compliant, and the BNG restores network access and related configurations for all resumed subscribers.

[0077] By processing multiple suspensions or resumptions in a single bulk operation, the system 108 significantly reduces processing time and manual effort compared to handling each subscriber individually. The bulk approach ensures uniform control, as all identified customers are suspended or resumed simultaneously, maintaining consistency across the network. It also optimizes system resource usage,allowing large-scale operations such as suspending customers accounts in bulk or resuming customers accounts in bulk without performance degradation by utilizing the at least one bulk one operation, and enhances operational scalability, enabling thousands of subscribers to be managed efficiently. Moreover, immediate suspension of expired or unauthorized users helps prevent revenue loss, while rapid resumption ensures minimal service downtime for compliant customers. The automation and integration with datasheets and API workflows further reduce repetitive tasks and provide a traceable, auditable record of all operations. This bulk suspension and resumption capability improves speed, efficiency, and reliability in network service management.

[0078] In an embodiment, the system 108 is configured perform large-scale suspension and resumption of network services, and to provide real-time monitoring, predictive analytics, automated compliance integration, and multi-operation control to enhance operational intelligence and automation within telecommunication networks.

[0079] In an aspect, the system 108 may include a real-time monitoring and adjustment module configured to continuously track the status of the at least one ongoing bulk operation, such as suspension or resumption requests. This module enables dynamic modification or termination of specific operations based on live progress indicators, failure logs, or system alerts. For instance, if a subset of suspension requests fails due to network latency or system error, the network operator can dynamically reinitiate only the failed requests without restarting the entire bulk process.

[0080] In an aspect, the system 108 may analyze historical customer data, recharge cycles, and network performance parameters to identify potential revenue leakage scenarios or service anomalies before they occur. For example, the system 108 may predict that a group of subscribers is likely to continue accessing data services1 post recharge expiry and automatically schedule suspension requests in advance, ensuring proactive revenue protection.

[0081] In an aspect, the system 108 provides integration with external operational systems, such as billing platforms, compliance engines, and regulatory audit databases, through secure APIs. This integration allows automatic validation of subscriber payments, entitlement checks, and policy compliance before executing bulk suspension or resumption requests. For instance, if a customer has a pending payment confirmation, the system 108 may delay resumption until validation is received from the billing server, ensuring error-free and compliant operation.

[0082] Although FIG. 2 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. 2. 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.

[0083] FIG. 3 illustrates an exemplary system architecture 300 for managing the one or more network services for the plurality of customer accounts in the communication network 106, in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with FIGS. 1 and 2.

[0084] In an embodiment, the system architecture includes a bulk suspension tool 302, and a network server 304. In an example, the network server 304 may be the PGW server. The network server 304 may further include a suspend module 306, a resume module 308 and a database 310.

[0085] In an aspect, the bulk suspension tool (or bulk suspension utility) 302 identifies the plurality of customer accounts based on the one or more predefined operational criteria. For example, the bulk suspension tool 302 identifies the pluralityof customer accounts who are using the one or more network services after their recharge has expired. If different customers have different suspension codes, the bulk suspension tool 302 identifies those suspension codes as well. Further, the bulk suspension tool 302 stores the service- related data for the plurality of customer accounts in the data sheet (Excel sheet).

[0086] In an aspect, the bulk suspension tool 302 may determine the at least one bulk operation to be executed for the identified plurality of customer accounts based on the stored service-related data. Further, based on the determined bulk operation, the bulk suspension tool 302 sends the suspend or resume application programming interface (API) requests 312 to the network server 304 (for e.g., provisioning gateway (PGW) server) for suspending or resuming the one or more network services for the identified customers.

[0087] Further, the network server 304 may notify the CHF-BNG node (not shown in FIG. 3 for the sake of clarity). The CHF BNG node fetches all the updated information of the identified customers from the database 310 and performs the necessary changes in the database. For example, the CHF BNG node updates the network services status as ‘SUSPEND’ to suspend the identified customers. Moreover, the CHF BNG node updates the network services status as ‘RESUME’ to resume the identified customers. Finally, the network server 304 sends a response 314 to the bulk suspension tool 302 to update that the identified customers are suspended or resumed.

[0088] FIG. 4 illustrates an exemplary process flow 400 for suspending the one or more network services for the plurality of customer accounts in the communication network 106, in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIG 1, FIG. 2 and FIG. 3.

[0089] In an aspect, the system 300 analyses the service-related data for customers who are using the one or more network services after their recharge hasexpired. Moreover, the system 300 also identifies suspension codes if different customers (subscribers) have different suspension codes.

[0090] Upon analyzing and identifying such customers, the service-related data is stored in the data sheet i.e., an excel sheet. At step 402, the suspend request (suspend API request) is sent to the network server 304 (i.e., the PGW server).

[0091] At step 404, the network server 304 performs a check to determine if the MAC ID of each identified customer exists in the database 310.

[0092] Branch ‘Yes’ is followed in case the MAC ID for each identified customer exists in the database 310. Alternatively, branch ‘No’ is followed in case the network server 304 determines that the MAC IDs of the customers do not exist in the database 310. Further, at step 408, the suspend request is rejected.

[0093] At step 406, the network server 304 determines if the identified customers corresponding to the MAC IDs have been already suspended.

[0094] Upon identifying that the identified customers are already suspended at step 406, the branch ‘Yes’ is followed, and at step 410, the suspend request is rejected.

[0095] Alternatively, when it is determined that the identified customers are not suspended, the branch ‘No’ is followed. Further, at step 412, the network server 304 suspends the one or more network services that are being utilized by the identified customers.

[0096] Following the suspension, resumption, at step 414, the CHF-BNGnodes fetch the updated customer information and update the database servers accordingly, such as valid suspended physical cell IDs (PCIDs) of the identified customers.

[0097] FIG. 5 illustrates an exemplary process flow 500 for resuming the one or more network services for the plurality of customer accounts in the communicationnetwork 106, in accordance with an embodiment of the present disclosure. FIG. 5 is explained in conjunction with FIG. 1, FIG. 2, FIG. 3.

[0098] In an embodiment, based on the service-related data stored in the datasheet (as described with reference to FIG. 3), the bulk suspension tool 302 determines that the at least one bulk operation to be performed is the resumption of services for the identified plurality of customer accounts. At step 502, the bulk suspension tool 302 transmits a resume request to the network server 304 to initiate the resumption of the one or more network services for the plurality of customer accounts.

[0099] At step 504, the network server 304 performs a verification in its internal database 310 to determine whether the MAC IDs of the identified plurality of customer accounts. This check ensures that only valid and registered customer devices are processed for resumption. If the MAC IDs are found in the database (branch “Yes”), the network server 304 proceeds to step 506 to check whether the corresponding customers’ network services have already been resumed. This verification prevents redundant operations and ensures that only customers who are currently suspended are processed for resumption.

[0100] If the MAC IDs are not found in the database 310 (branch “No”), the process follows step 508, where the resume request is rejected. Similarly, if the network services for the identified MAC IDs are already resumed (branch “Yes” at step 506), the resume request is rejected at step 510 to avoid unnecessary or conflicting operations.

[0101] When the customers are valid and currently suspended (branch “No” at step 506), the process follows to step 512, where the network server 304 resumes the one or more network services for the identified plurality of customer accounts. Following the resumption, at step 514, the CHF -BNG nodes fetch the updated customer information and update the database accordingly. The CHF validates the chargingstatus, while the BNG ensures that the corresponding valid rental plans or network services for the identified customer PCIDs are correctly activated.

[0102] FIG. 6 illustrates an exemplary flow diagram 600 of a method for managing the one or more network services for the plurality of customer accounts in the communication network 106, in accordance with an embodiment of the present disclosure. FIG. 6 is explained in conjunction with FIG. 2.

[0103] At step 602, the method 600 includes identifying, by a processing unit 208, the plurality of customer accounts utilizing the one or more network services based on one or more predefined operational criteria. The one or more network services may one or more communication, data, media, or value-added services. In an aspect, the one or more predefined operational criteria may include the predefined operational criteria comprise one or more business, technical, regulatory, or operational conditions, including but not limited to subscription expiry, fraud detection, payment status, service policy violation, or system-generated trigger.

[0104] At step 604, the method 600 includes storing, by the processing unit 208, service-related data associated with the plurality of customer accounts in at least one data structure, based on the identification. In an aspect, the service-related data may include one or more data elements associated with each of the plurality of customer accounts, including but not limited to unique identifiers, current service status, information indicative of the bulk operation to be performed, types or categories of network services associated with the plurality of customers, and one or more timestamps indicating data update events.

[0105] At step 606, the method 600 includes determining, by the processing unit 208, at least one bulk management operation to be executed for the identified plurality of customer accounts based on the stored service-related data. The at least one bulk management operation is one of: suspending, resuming, activating, deactivating,throttling, or modifying the one or more network services. In an aspect, the bulk management operation is automatically executed through an integrated workflow comprising data retrieval, update generation, and service control command transmission.

[0106] At step 608, the method 600 includes transmitting, by the processing unit 208, one or more control request via a application programming interface (API) to at least one network server based on the determination. In an aspect, the one or more control requests is one of a stop service request or a resume service request. In an aspect, the at least one network server executes the at least one bulk management operation for the identified plurality of customer accounts based on the received one or more control requests. In an aspect, the at least one network server is configured to notify at least one network gateway node about a service status related to the one or more network services for the plurality of customer accounts. Further, the at least one network gateway node is configured to retrieve subscriber information associated with the plurality of customer accounts from a database (210). Further, the at least one network gateway node is configured to validate the service status associated with the plurality of customer accounts based on one or more parameters and update one or more network configurations associated with the plurality of customer accounts based on the validated service status.

[0107] In operation, the process typically begins at a Graphical User Interface (GUI), where an authorized user inputs or uploads subscriber- related information (e.g., subscriber IDs, MAC IDs, suspension codes, or operation type). This input is transmitted to the system 108, which validates the received data, structures it into predefined message formats, and triggers corresponding service control requests. The system 108 then communicates with the PGW server via the API, responsible for executing the actual suspension or resumption of data sessions for the identified plurality of customer accounts. Upon performing the requested operation, the PGWserver updates its internal database servers with the latest customer service status. Subsequently, the PGW server notifies the CHF-BNG node to update service-related data to synchronize charging, policy enforcement, and access control configurations.

[0108] FIG. 7 illustrates an example computer system 700 in which or with which the embodiments of the present disclosure may be implemented.

[0109] As shown in FIG. 7, the computer system 700 may include an external storage device 710, a bus 720, a main memory 730, a read-only memory 740, a mass storage device 750, a communication port(s) 760, and a processor 770. A person skilled in the art will appreciate that the computer system 700 may include more than one processor and communication ports. The processor 770 may include various modules associated with embodiments of the present disclosure. The communication port(s) 760 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 ports(s) 760 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 700 connects.

[0110] In an embodiment, the main memory 730 may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 740 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 770. The mass storage device 750 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).

[0111] In an embodiment, the bus 720 may communicatively couple the processor(s) 770 with the other memory, storage, and communication blocks. The bus 720 may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) 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 770 to the computer system 700.

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

[0113] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The method includes identifying, by a processing unit, the plurality of customer accounts utilizing the one or more network services based on one or more predefined operational criteria. The method includes storing, by the processing unit, service-related data associated with the plurality of customer accounts in at least one data structure, based on the identification. The method includes determining, by the processing unit, at least one bulk management operation to be executed for the identified plurality of customer accounts based on the stored service-related data. The method includes transmitting, by the processing unit, one or more control requests via an application programming interface (API) to at least one network server based on the determination. Further, the at least one network server executes the at least one bulk management operation for theidentified plurality of customer accounts based on the received one or more control requests.

[0114] The present disclosure provides a technical advancement in the field of network service management within telecommunication networks by introducing a system (i.e., a bulk suspension tool) for efficiently suspending or resuming subscriber services. Unlike conventional GUI-based tools that rely on manual intervention and suffer from slow performance and high system resource consumption, the bulk suspension tool automates the process of identifying and managing subscribers who have exhausted their recharge or require service suspension. By reading customer data, categorizing suspension codes, and sending bulk API requests to network server such as PGW, the bulk suspension tool ensures that service suspension or resumption occurs quickly, accurately, and uniformly across multiple subscribers.

[0115] The bulk suspension tool allows customization based on specific criteria, providing operators fine-grained control over which subscribers are affected while maintaining consistency and synchronization across all network databases. Integration with automated workflows and external data sources, such as Excel sheets, further reduces manual effort and enables large-scale operations with minimal resource usage. This automated, scalable approach minimizes revenue loss due to unauthorized usage, reduces operational overhead, and enhances the overall efficiency and reliability of network service management. Overall, the bulk suspension tool represents a significant improvement over conventional techniques by providing faster execution, resource optimization, uniform control, and automated, large-scale management of subscriber services in telecommunication networks.

[0116] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions orexamples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

[0117] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0118] 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

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

[0120] The present disclosure offers an automated approach to suspend or resume network services, where the bulk suspension tool automates the process,significantly reducing the time and manual effort required compared to handling each suspension individually. Performing multiple suspensions or resumptions in a single operation is faster than executing them one by one.

[0121] The present disclosure ensures that all specified customers are suspended simultaneously by using the bulk adjustment tool, which helps in maintaining uniformity and control over the affected customers.

[0122] The present disclosure offers a customizable approach, where the bulk suspension tool can be configured to meet specific criteria or operational conditions, allowing network operators to selectively control which customers or subscriber groups are affected.

[0123] The present disclosure offers a uniform control mechanism, where the bulk suspension tool ensures that all specified customers are suspended or resumed simultaneously, thereby maintaining uniformity and consistency across the affected customer base.

[0124] The present disclosure offers an integrated workflow solution, where the bulk suspension tool seamlessly integrates with other systems such as PGW server, scripts, and data sources to automate tasks such as pulling data from Excel sheets, applying changes, and pushing updates in a single automated workflow.

[0125] The present disclosure offers a scalable and efficient solution, where the bulk suspension tool can handle large-scale operations effectively, unlike GUI-based tools that often face performance degradation when processing high volumes of subscriber data.

[0126] The present disclosure provides a real-time monitoring and dynamic adjustment mechanism that enables continuous tracking of ongoing bulk operations. The system facilitates dynamic adjustment of suspension or resumption requestswithout interrupting active processes. This ensures higher operational accuracy, faster issue resolution, and improved control over large-scale network management tasks.

[0127] The present disclosure further offers predictive analytics for proactive service management, where historical network data and service usage patterns are analyzed to forecast potential service anomalies, fraudulent behaviors, or recharge expirations. The system enables the initiation of preventive actions such as early suspension triggers or service reminders, reducing the likelihood of revenue leakage and enhancing network reliability.

[0128] The present disclosure also enables integration with external systems for automated compliance and payment validation. Through secure interfaces with billing, policy, and regulatory systems, the bulk suspension tool automatically validates payment records, subscriber entitlements, and legal compliance before executing bulk operations. This automation minimizes human error, ensures adherence to operational standards, and improves end-to-end transparency in network service management.

[0129] The present disclosure supports multiple types of bulk operations beyond stop or resume, including bandwidth throttling, quality-of-service (QoS) adjustment, or service tier modification. This multi-operation capability extends the utility of the system across diverse network scenarios, providing operators with a unified platform for managing customer services dynamically while maintaining network stability and optimizing resource utilization.

[0130] The present disclosure offers a resource-optimized approach, where the bulk suspension tool requires fewer system resources compared to GUI-based tools, making it suitable for server-based environments and improving overall operational efficiency.

[0131] The present disclosure offers a revenue protection mechanism, where the bulk suspension tool enables network operators to quickly stop or resume network services to prevent potential revenue loss due to unauthorized or expired usage, thereby maintaining service integrity and operational reliability.

Claims

We claim:

1. A method (600) for managing one or more network services for a plurality of customer accounts in a communication network (106), the method comprising: identifying (602), by a processing unit (208), the plurality of customer accounts utilizing the one or more network services based on one or more predefined operational criteria; storing (604), by the processing unit (208), service-related data associated with the plurality of customer accounts in at least one data structure, based on the identification; determining (606), by the processing unit (208), at least one bulk management operation to be executed for the identified plurality of customer accounts based on the stored service-related data; and transmitting (608), by the processing unit (208), one or more control requests via an application programming interface (API) to at least one network server (304) based on the determination, wherein the at least one network server (304) executes the bulk management operation for the identified plurality of customer accounts based on the received one or more control requests.

2. The method (600) as claimed in claim 1, wherein the one or more predefined operational criteria comprise one or more business, technical, regulatory, or operational conditions, including but not limited to subscription expiry, fraud detection, payment status, service policy violation, or system-generated trigger.

3. The method (600) of claim 1, wherein the service-related data comprises one or more data elements associated with each of the plurality of customer accounts, including but not limited to unique identifiers, current service status, informationindicative of the bulk operation to be performed, types or categories of network services associated with the plurality of customers, and one or more timestamps indicating data update events.

4. The method (600) as claimed in claim 1, wherein the one or more network services comprises one or more communication, data, media, or value-added services.

5. The method (600) as claimed in claim 1, wherein the one or more control requests is one of a stop service request or a resume service request.

6. The method (600) as claimed in claim 1, wherein the bulk management operation is automatically executed through an integrated workflow comprising data retrieval, update generation, and service control command transmission.

7. The method (600) as claimed in claim 1, wherein the bulk management operation comprises at least one of: suspending, resuming, activating, deactivating, throttling, or modifying the one or more network services.

8. The method (600) as claimed in claim 1, comprising: notifying, by the at least one network server (304), at least one network gateway node about a service status related to the one or more network services for the plurality of customer accounts; retrieving, by the at least one network gateway node, subscriber information associated with the plurality of customer accounts from a database (210);validating, by the at least one network gateway node, the service status associated with the plurality of customer accounts based on one or more parameters; and updating, by the at least one network gateway node, one or more network configurations associated with the plurality of customer accounts based on the validated service status.

9. A system (108) for managing one or more network services for a plurality of customer accounts in a communication network (106), the system (108) comprising: a processing unit (208) configured to: identify the plurality of customer accounts utilizing the one or more network services based on one or more predefined operational criteria; store service-related data associated with the plurality of customer accounts in at least one data structure, based on the identification; determine at least one bulk management operation to be executed for the plurality of customer accounts based on the stored service-related data; and transmit one or more control requests via an application programming interface (API) to at least one network server (304) based on the determination, wherein the at least one network server (304) is configured to execute the at least one bulk management operation for the plurality of customer accounts based on the received one or more control requests.

10. The system (108) as claimed in claim 9, wherein the one or more predefined operational criteria comprise one or more business, technical, regulatory, or operational conditions, including but not limited to subscription expiry, fraud detection, payment status, service policy violation, or system-generated trigger.

11. The system (108) as claimed in claim 9, wherein the service-related data comprises one or more data elements associated with each of the plurality of customer accounts, including but not limited to unique identifiers, current service status, information indicative of the bulk operation to be performed, types or categories of network services associated with the plurality of customers, and one or more timestamps indicating data update events.

12. The system (108) as claimed in claim 9, wherein the one or more network services comprises one or more communication, data, media, or value-added services.

13. The system (108) as claimed in claim 9, wherein the one or more control requests is one of a stop service request or a resume service request.

14. The system (108) as claimed in claim 9, wherein the bulk management operation is automatically executed through an integrated workflow comprising data retrieval, update generation, and service control command transmission.

15. The system (108) as claimed in claim 9, wherein the bulk management operation comprises at least one of: suspending, resuming, activating, deactivating, throttling, or modifying the one or more network services.

16. The system (108) as claimed in claim 9, comprises notifying, by at least one network server (304), at least one network gateway node about a service status related to one or more network services for the plurality of customer accounts; retrieving, by the at least one network gateway node, subscriber information associated with the plurality of customer accounts from a database (210);validating, by the at least one network gateway node, the service status associated with the plurality of customer accounts based on one or more parameters; and updating, by the at least one network gateway node, one or more network configurations associated with the plurality of customer accounts based on the validated service status.

17. 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 (600) for managing one or more network services for a plurality of customer accounts in a communication network (106), the method (600) comprising: identifying (602), by a processing unit (208), the plurality of customer accounts utilizing the one or more network services based on one or more predefined operational criteria; storing (604), by the processing unit (208), service-related data associated with the plurality of customer accounts in at least one data structure, based on the identification; determining (606), by the processing unit (208), at least one bulk management operation to be executed for the identified plurality of customer accounts based on the stored service-related data; and transmitting (608), by the processing unit (208), one or more control requests via an application programming interface (API) to at least one network server (304) based on the determination, wherein the at least one network server (304) executes the bulk management operation for the identified plurality of customer accounts based on the received one or more control requests.

Images