Method and system for managing subscriber data in a network

Abstract

The disclosure relates to a method (400) and system (108) for managing subscriber data in a network (106) A processing engine (208) is configured to receive an input data file associated with one or more subscribers from a source and extract one or more parameters from the received file. The extracted parameters are compared with subscriber parameters stored in a database (210) to identify corresponding subscriber data. Once identified, the processing engine (208) performs at least one operation on the subscriber data, such as deletion, validation, or updating of records. By automating these operations, the disclosed system ensures accurate and efficient management of subscriber data in large-scale network databases, reduces the risk of errors, and optimizes resource utilization while maintaining data integrity and system performance.

Description

METHOD AND SYSTEM FOR MANAGING SUBSCRIBER DATA 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 (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.TECHNICAL FIELD

[0002] The present disclosure relates generally to the field of telecommunications. The present disclosure relates to a system and a method for managing subscriber data in a network. In particular, the present disclosure relates to a system and a method for bulk deletion of subscriber data based on Media Access Control Identification (MAC ID) in a network.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 expression “subscriber data” used hereinafter in the specification refers to information associated with a network subscriber, including but not limited to personal identifiers, account and billing information, device details, location data, and service usage metrics, which are stored and managed within telecommunication network databases.

[0005] The expression “deletion” used hereinafter in the specification refers to the process of removing subscriber data from a network database, which may be carried out through physical deletion, logical deletion, or archival deletion, each having different implications for data accessibility and compliance.

[0006] The expression “unsubscribing” used hereinafter in the specification refers to the process of terminating or deactivating a subscriber’s association with network services, which involves deletion or deactivation of corresponding subscription records from one or more network databases to prevent further service access.

[0007] The expression “Media Access Control Identification (MAC ID)” used hereinafter in the specification refers to a unique hardware identifier assigned to a network interface card (NIC) or device for communication at the data link layer, typically represented as a 48-bit address, and used by telecommunication networks to identify and authenticate devices.

[0008] The expression “Bulk deletion” used hereinafter in the specification refers to a process of deleting a large number of records or data entries from a database or a storage medium in a single operation or series of operations. Bulk deletion is used to manage large datasets efficiently, perform regular cleanups, or comply with data policies.

[0009] The expression “extracting” used hereinafter in the specification refers to a process of retrieving data from a data source, a file, or a database. The extracted data may be used for analyzing, reporting, or integration purposes.

[0010] The expression “parsing” used hereinafter in the specification refers to a process of analyzing and interpreting data or queries to extract useful information or transform the data or queries into various format. The process of parsing involvesconverting data from one format to another or extracting specific data from a large dataset.

[0011] The expression “validating” used hereinafter in the specification refers to a process of checking to ensure that the structure or format of the given data complies with predefined rules or standards.

[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 modern telecommunication networks, vast volumes of subscriber- related data are generated, transmitted, and stored within various network databases to ensure seamless connectivity and efficient service delivery. Such subscriber data is diverse in nature, comprising personal details (e.g., identifiers, authentication credentials), account and billing information, device identifiers and configurations, location and mobility data, as well as service usage and interaction metrics. This data may be updated in real-time during active sessions or periodically synchronized based on network policies. With the exponential growth in the number of subscribers and connected devices, the volume of accumulated subscriber data continuously increases, creating challenges in storage, retrieval, and overall database management. As a result, periodic or event-triggered deletion of outdated, redundant, or obsolete subscriber records becomes essential for optimizing database utilization and ensuring compliance with regulatory and operational requirements.

[0015] Conventionally, subscriber data deletion in these networks has been carried out through manual administrative processes. Such manual interventions are not only labour-intensive but also inefficient and error-prone, particularly in large-scale systems where subscriber records may span multiple distributed databases. Data deletion requests typically arise due to factors such as regulatory compliance obligations (e.g., data retention limits, privacy requirements), routine data maintenance, or explicit user requests to unsubscribe or terminate services. The manual workflow often requires operators to first identify the specific subscriber records to be removed, validate the correctness of the identified records, and then execute the deletion operation while ensuring compliance with applicable policies. This multistep process introduces delays and risks, as human errors can compromise data integrity, lead to inconsistencies across databases, and degrade overall system reliability. Furthermore, accidental deletions are frequently irreversible in nature and underscore the vulnerability of manual deletion approaches and necessitate continuous monitoring and corrective interventions.

[0016] The manual deletion of the subscriber data also exacerbates the complexity of database administration, particularly due to the existence of different deletion methods such as physical deletion (complete removal of data from storage), logical deletion (marking records as inactive or unavailable without actual removal), and archival deletion (transferring data to long-term storage). Each of these methods has distinct implications for data accessibility, regulatory compliance, and system performance. When subscriber data deletions are performed manually in environments experiencing high network or database input traffic, the risk of database contention and deadlocks significantly increases, further degrading system performance. This may manifest as slower query responses, prolonged processing delays, and inefficient resource utilization. Consequently, traditional deletion techniques fall short in providing the efficiency, reliability, and scalability required for managing subscriber data in modem, high-capacity telecommunication networks.

[0017] Therefore, there is a need for a system and a method that overcomes the limitations of the prior art.OBJECTIVES OF THE DISCLOSURE

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

[0019] An objective of the present disclosure is to provide a system and a method for bulk deletion of subscriber data from a database in a network.

[0020] Another objective of the present disclosure is to provide a system and a method for streamlining and automating the bulk deletion of subscriber data in large- scale databases using unique identifiers.

[0021] Another objective of the present disclosure is to provide a system and a method that enables simultaneous deletion of multiple subscriber data entries without impacting database performance.

[0022] Another objective of the present disclosure is to provide a system and a method for customized deletion of subscriber data based on various deletion scenarios.

[0023] Yet another objective of the present disclosure is to provide a system and a method that facilitates efficient management of subscriber data deletion within the network.

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

[0025] In an exemplary embodiment, a method for managing subscriber data in a network is described. The method comprising receiving, by a processing engine, at least one input data file associated with at least one subscriber from a source. The method comprising extracting, by the processing engine, at least one parameter from the received at least one input data file. The method comprising comparing, by the processing engine, the extracted at least one parameter with at least one subscriber parameter stored in a database. The method comprising based on the comparison, identifying, by the processing engine, the subscriber data corresponding to the extracted at least one parameter. The method comprising performing, by the processing engine, at least one operation associated with the identified subscriber data.

[0026] In an embodiment, the method comprising verifying, by the processing engine, the received at least one input data file using at least one attribute. The at least one attribute comprises at least one of a file size, a file type, and a file status.

[0027] In an embodiment, the method comprising validating, by the processing engine, the extracted at least one parameter using at least one validating parameter. The at least one validating parameter comprises of a parameter length, a parameter format, a parameter type, a parameter character set and a combination thereof.

[0028] In an embodiment, the method comprising removing, by the processing engine, the identified subscriber data associated with the extracted at least one parameter from the database.

[0029] In an embodiment, the method comprising monitoring, by the processing engine, the removal of the identified subscriber data to provide a feedback related to a status of the removal to a third party.

[0030] In an embodiment, the method comprising confirming, by the processing engine, successful completion of the removal of the identified subscriber data to the third party.

[0031] In an embodiment, the method comprising recording, by the processing engine, the removed subscriber data to generate a report associated with the removed subscriber data.

[0032] In an embodiment, the method comprising transmitting, by the processing engine, the generated report to the third party.

[0033] In an embodiment, the extracted at least one parameter comprises of at least one Media Access Control (MAC) Identifier (ID) associated with the at least one subscriber.

[0034] In an exemplary embodiment, a system for managing subscriber data in a network is described. The system comprising a memory and a processing engine coupled to the memory and is configured to execute instructions stored in the memory. The processing engine is configured to receive at least one input data file associated with at least one subscriber from a source. The processing engine is configured to extract at least one parameter from the received at least one input data file. The processing engine is configured to compare the extracted at least one parameter with at least one subscriber parameter stored in a database. The processing engine is configured to identify the subscriber data corresponding to the extracted at least one parameter based on the comparison. The processing engine is configured to perform at least one operation associated with the identified subscriber data.

[0035] In an exemplary embodiment, the present disclosure discloses a user equipment (UE) communicatively coupled with a network. The coupling comprises steps of receiving, by the network, a connection request from the UE. The coupling comprises steps of sending, by the network, an acknowledgment of the connection request to the UE. The coupling comprises steps of transmitting a plurality of signals in response to the connection request. The subscriber data in the network is managed by a method comprising receiving, by a processing engine, at least one input data fileassociated with at least one subscriber from a source. The method comprising extracting, by the processing engine, at least one parameter from the received at least one input data file. The method comprising comparing, by the processing engine, the extracted at least one parameter with at least one subscriber parameter stored in a database. The method comprising based on the comparison, identifying, by the processing engine, the subscriber data corresponding to the extracted at least one parameter. The method comprising performing, by the processing engine, at least one operation associated with the identified subscriber data.

[0036] In yet another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing subscriber data in a network. The method comprising receiving, by a processing engine, at least one input data file associated with at least one subscriber from a source. The method comprising extracting, by the processing engine, at least one parameter from the received at least one input data file. The method comprising comparing, by the processing engine, the extracted at least one parameter with at least one subscriber parameter stored in a database. The method comprising based on the comparison, identifying, by the processing engine, the subscriber data corresponding to the extracted at least one parameter. The method comprising performing, by the processing engine, at least one operation associated with the identified subscriber data.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0037] 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 thepresent 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.

[0038] FIG. 1 illustrates an exemplary network architecture of a system for managing subscriber data in a network, in accordance with an embodiment of the present disclosure.

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

[0040] FIG. 3 illustrates an exemplary flow diagram of a method for managing the subscriber data in the network, in accordance with an embodiment of the present disclosure.

[0041] FIG. 4 illustrates another exemplary flow diagram of the method for managing the subscriber data in the network, in accordance with an embodiment of the present disclosure.

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

[0043] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100- Network architecture102- User104- User equipment106- Network108- System200- Block diagram 202- Processor(s)204- Memory206- Interface(s)208- Processing Engine210- Database 300, 400- Flow diagram500 - Computer system510 - External Storage Device520 - Bus530 - Main Memory 540 - Read Only Memory550 - Mass Storage Device560 - Communication Port570 - ProcessorDETAILED DESCRIPTION

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

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

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

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

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

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

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

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

[0052] In advanced network architectures, subscriber information is stored in a central database as subscriber records, which are accessed by various NetworkFunctions (NFs) to provide services to users. The subscriber information encompasses a wide range of data about each subscriber, including personal details like names and contact information, account specifics such as subscription plans and billing records, user device-related data including identifiers and model specifics, user location data reflecting geographic usage, and service interaction records detailing usage patterns and service requests.

[0053] As telecommunications networks expand, the volume of these subscriber records can become substantial. Subscriber data deletion is essential for several reasons. Firstly, the subscriber data deletion ensures compliance with data protection laws, which mandate removing personal information after a certain period or upon request to safeguard user privacy. Secondly, the subscriber data deletion helps manage the database effectively by removing outdated or redundant records, thereby reducing storage costs and enhancing system performance. Regular data deletion also improves system efficiency by minimizing the risk of performance issues associated with handling large volumes of data and enhances security by reducing the risk of data breaches and unauthorized access. Efficiently managing the bulk deletions of the subscriber data is essential to preserving the integrity and performance of the database. Traditional deletion methods often fall short in large-scale environments, as manual processes can result in inefficiencies, data integrity issues, and degraded performance.

[0054] To address the challenge of efficiently managing subscriber data in the telecommunication network, the present disclosure employs a bulk deletion module to streamline the deletion process of subscriber data in bulk. The deletion process may be provided with an input file including unique identifiers (for example, Media Access Control Identifiers (MAC IDs)) associated with the subscribers to be deleted. By employing the bulk deletion module, a network administrator can efficiently remove multiple subscriber records from the database in a single operation. The automated deletion process may save time and resources compared to manual deletion. Thepresent disclosure enables managing subscriber data efficiently and effectively in telecommunications networks, particularly in a case of large-scale database operations.

[0055] In an embodiment, the bulk deletion module may interact with one or more NFs in the network to ensure that subscriber data is deleted in a controlled, validated, and policy-driven manner. For instance, prior to initiating a bulk deletion operation, the bulk deletion module may transmit a validation request to functions such as an Authentication, Authorization, and Accounting (AAA) function, a Unified Data Management (UDM) function, or other subscriber management entities (e.g., Home Subscriber Server (HSS), Policy Control Function (PCF), or Access and Mobility Management Function (AMF)) to confirm the status of the targeted subscriber records. These NFs may perform verification checks including, but not limited to determining whether the subscriber is currently registered in the network, identifying whether any ongoing communication or data sessions are active, validating whether any lawful interception or monitoring obligations apply, and ensuring that data retention periods mandated by regulatory authorities have been satisfied. Upon successful validation and receipt of clearance from the relevant NFs, the bulk deletion module may proceed with securely removing the corresponding subscriber records from the central database. In some embodiments, the module may also log the NF confirmations along with metadata such as timestamp, identifiers of deleted records, and authorization tokens to maintain an auditable trail. This controlled interaction between the bulk deletion module and NFs ensures that active services are not disrupted, unauthorized deletions are prevented, and the overall deletion process remains compliant with operational policies and regulatory requirements.

[0056] The present disclosure allows the network administrator to delete multiple subscriber data in bulk with minimal effort and time. The present disclosure utilizes unique identifiers of the subscriber device to delete the subscriber data from the database. The usage of unique identifiers may reduce the risk of accidental deletingincorrect records and help to maintain data integrity within the database. The deletion operation disclosed in the present disclosure may handle a large-scale operation. The deletion operation may be implemented to delete a few subscriber data or thousands of subscriber data based on the criteria defined by the network administrator. In an embodiment, the criteria for deletion may vary depending on operational requirements, compliance policies, or user requests. For example, the deletion criteria may include, but are not limited to, the age of data (e.g., subscriber data older than a predefined threshold such as three years), data associated with inactive or de-registered subscribers, specific deletion requests raised by end users, compliance with regulatory or legal mandates (such as privacy regulations), or administrative policies for optimizing database performance. In an embodiment, the administrator may define customized criteria such as deletion of data corresponding to a specific service type, billing account, or network usage pattern. By allowing configurable deletion criteria, the system ensures that subscriber data removal is flexible, policy-driven, and adaptable to diverse network requirements.

[0057] In an example scenario, before initiating bulk deletion, the bulk deletion module may communicate with one or more NFs such as the UDM, PCF, or Authentication Server Function (AUSF) to verify the status of the subscriber data marked for deletion. For instance, the UDM may confirm whether a subscriber is inactive or permanently de-registered, while the PCF may validate that no active policy sessions are associated with the subscriber. After receiving confirmation from the respective NFs does the bulk deletion module proceed with removal of the subscriber data. This interaction ensures that deletion is performed in a controlled and validated manner, avoiding accidental removal of data still required for active services. Thus, the workload on administrators is minimized, which enhances the overall performance of the database in the network.

[0058] The present disclosure discloses a system and a method for bulk deletion that can streamline and automate the deletion of subscriber data from a database using unique identifiers (MAC IDs). By leveraging automation, the risk of errors in the deletion is reduced, ensuring the accurate deletion of subscriber data. Additionally, the system and method provide scalability and customization options that enable flexibility to adapt to different network requirements and deletion scenarios.

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

[0060] FIG. 1 illustrates an exemplary network architecture (100) of a system (108) for managing subscriber data in a network (106), in accordance with an embodiment of the present disclosure.

[0061] As illustrated in 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 collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2... 104-N) may be collectively referred to as the UE (104). Although only three UEs (104) are depicted in FIG. 1, however, any number of the UE (104) may be included without departing from the scope of the ongoing description.

[0062] 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 UEs (104) may include, but are 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 UEs (104) may include, but not limited to, intelligent, multisensing, network- connected devices that may integrate seamlessly with each other and / or with a central server or a cloud- computing system or any other device that is network-connected.

[0063] Additionally, in some embodiments, 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 headmounted 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 UE (104) may include, but are not limited to, any electrical, electronic, electromechanical, or 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 touchpad, 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.

[0064] Referring to FIG. 1, the UE (104) may communicate with the system (108) through the network (106) for sending or receiving various types of data. In anembodiment, the network (106) may include at least one of a fifth generation (5G) network, 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.

[0065] In an embodiment, the network (106) may include, 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. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet- switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0066] In an embodiment, the UE (104) is communicatively coupled with the network (106) through the system (108). The network (106) may receive a connection request from the UE (104). The network (106) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. The system (108) is configured to manage the subscriber data in the network (106).

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

[0068] FIG. 2 illustrates an exemplary block diagram (200) of the system (108), in accordance with an embodiment of the present disclosure. FIG. 2 is explained in conjunction with FIG. 1.

[0069] Referring to FIG. 2, 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 random-access memory (RAM), or non-volatile memory such as erasable programmable read only memory (EPROM), flash memory, and the like.

[0070] 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) may facilitate 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 engine (208) and a database (210).

[0071] In an embodiment, the system (108) may include a processing engine (208) that may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (208). In an embodiment, the processing engine (208) may be referred to as a bulk deletion module and may be configured to perform automated and large-scale deletion of subscriber data from the database based on predefined criteria, while ensuring accuracy, integrity, and compliance. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine (208). In such examples, the system may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine- readable storage medium may be separate but accessible to the system and the processing resource. In other examples, the processing engine (208) may be implemented by electronic circuitry. In an embodiment, the processing engine (208) may be configured for bulk deletion of subscriber data from the database (210).

[0072] In an embodiment, the system (108) may include the database (210) that includes data that may be either stored or generated as a result of functionalities implemented by any of the components of the one or more processor(s) (202) or the processing engine (208).

[0073] In an embodiment, the system (108) may be configured for managing subscriber data in the network (106). The system (108) may be configured to enable the deletion of one or more subscriber data from the database. The subscriber data may refer to information associated with a network subscriber that is maintained within the database for identification, authentication, billing, or network management purposes. In an aspect, the subscriber data may include unique subscriber identifiers such as International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI), Media Access Control (MAC) address, or Internet Protocol (IP) address. Further, the subscriber data may comprise account-related information such as subscriber name, subscription plan details, and billing records, as well as network usage information including call detail records, data session logs, and internet usage statistics. Additionally, the subscriber data may include connection-related information such as timestamps, device identifiers, and access network details. The deletion may be performed as a bulk deletion. In an aspect, the bulk deletion involves a process of removing a large number of subscriber data from the database (210) in a single operation. The bulk deletions are done to manage data size, remove outdated or irrelevant data, or maintain performance and storage efficiency.

[0074] In an embodiment, the system (108) comprising the memory (204) and the processing engine (208) coupled to the memory (204) and is configured to execute instructions stored in the memory (204). In an embodiment, the processing engine (208) is configured to receive at least one input data file associated with at least one subscriber from a source. The source may include, for example, a network management system, an operations support system (OSS), a business support system (BSS), or an administrative user interface. The input data file may be generated automatically by the network based on predefined triggers, such as expiration of a subscription, fulfillment of a retention period, or receipt of a user request to unsubscribe, or may be manually uploaded by a network administrator. In an embodiment, the input file may be received by the processing engine (208) through one or more communication channels, such asa secure file transfer protocol (SFTP), an application programming interface (API), a network interface, or a manual upload via a graphical user interface (GUI). In an embodiment, the input file may be received in different formats including text, Comma- Separated Values (CSV), Extensible Markup Language (XML), or JavaScript Object Notation (JSON). The input data file may contain structured information, such as subscriber identifiers, account details, device-related information, or unique identifiers like Media Access Control Identifications (MAC IDs), which facilitate precise identification of the subscriber records stored in the database (210). By enabling the reception of such input data files from different sources, the processing engine (208) ensures flexibility, interoperability, and accurate mapping of subscriber records targeted for deletion.

[0075] In an embodiment, the processing engine (208) is further configured to verify the received at least one input data file using at least one attribute. The at least one attribute comprises at least one of a file size, a file type, and a file status. In an embodiment, the processing engine (208) is further configured to verify the received input data file using at least one attribute to ensure the integrity and validity of the file prior to processing. The at least one attribute may include, but is not limited to, a file size, a file type, and a file status. For example, verification of the file size ensures that the input data file is within a permissible threshold, thereby avoiding incomplete or corrupted files. Verification of the file type ensures that the input data file is in an acceptable format such as CSV, XML, JSON, or plain text, which can be successfully parsed by the processing engine (208). Verification of the file status may include checking whether the input data file is complete, accessible, and free from transmission errors or corruption. By performing such attribute-level verifications, the processing engine (208) prevents processing of invalid or incompatible input data files, thereby reducing the likelihood of erroneous deletions and improving the overall robustness of subscriber data management operations.

[0076] In an embodiment, the processing engine (208) is configured to extract at least one parameter from the received at least one input data file. In an embodiment, the extracted at least one parameter comprises of at least one Media Access Control (MAC) Identifier (ID) associated with the at least one subscriber. In an embodiment, the extracted parameter may include, but is not limited to, subscriber identifiers, account references, or device-related identifiers. Specifically, the extracted parameter may comprise at least one MAC ID uniquely associated with the subscriber or the subscriber’s device. The MAC ID serves as a hardware-level identifier, enabling precise mapping of the subscriber record to be deleted within the database (210).

[0077] In an aspect, the extraction process may involve parsing the input data file, which may be formatted as a text file, CSV file, XML file, or JSON file. For example, when the input data file is a CSV file containing a column of MAC IDs, the processing engine (208) is configured to read and extract each MAC ID entry from the column for further processing. In another example, where the input data file is an XML file, the processing engine (208) identifies the XML tag associated with the MAC ID parameter and retrieves the corresponding values for one or more subscribers. In yet another example, the input data file may include a list of multiple MAC IDs corresponding to different subscribers scheduled for deletion. The processing engine (208) extracts each MAC ID from the list and batches the identifiers into a structured format. By handling different input formats and extracting the relevant parameters with precision, the processing engine (208) enables efficient and reliable execution of bulk or customized subscriber data deletions.

[0078] In an embodiment, the processing engine (208) is configured to compare the extracted at least one parameter with at least one subscriber parameter stored in the database (210). In an embodiment, the processing engine (208) is configured to validate the extracted at least one parameter using at least one validating parameter. The at least one validating parameter comprises of a parameter length, aparameter format, a parameter type, a parameter character set and a combination thereof. The processing engine (208) is configured to compare the extracted at least one parameter with at least one subscriber parameter stored in the database (210) in order to ensure accuracy and consistency of deletion operations. In an embodiment, the processing engine (208) is further configured to validate the extracted parameter using at least one validating parameter before performing the comparison. The validating parameter may include, but is not limited to, a parameter length, a parameter format, a parameter type, a parameter character set, or any suitable combination thereof. For example, in the case where the extracted parameter is a MAC ID, the processing engine (208) may validate the MAC ID by checking whether it conforms to the standard format of a 48-bit hexadecimal address represented by twelve alphanumeric characters separated by colons or hyphens (e.g., “OO: 1A:2B:3C:4D:5E”). In another example, validation may include verifying that the parameter length matches the required twelvecharacter length, that the characters belong to the valid hexadecimal set [0-9, A-F], and that the type of parameter corresponds to a device-level identifier rather than a subscriber account number.

[0079] In an additional aspect, the processing engine (208) may further validate whether the path provided for the parameter within the input data file is correct and accessible. For instance, when the parameter is embedded in a structured XML or JSON file, the processing engine (208) verifies that the tag name or key path specified for the parameter is valid and corresponds to the expected schema. Similarly, when the parameter is provided in a CSV file, the processing engine (208) ensures that the column path or header mapping is valid and correctly associated with the subscriber parameter to be deleted. Such path validation prevents errors due to misplaced, missing, or incorrectly referenced parameters in the input data file. By performing both parameter-level and path-level validations prior to comparison, the processing engine (208) ensures that only legitimate, well-formed, and properly referenced subscriber records are targeted for deletion from the database (210).

[0080] In an embodiment, the processing engine (208) is configured to identify the subscriber data corresponding to the extracted at least one parameter based on the comparison. In an embodiment, the processing engine (208) is configured to identify subscriber data corresponding to the extracted parameter based on the comparison performed with subscriber parameters stored in the database (210). The identification process ensures that the extracted parameter, such as the MAC ID, International Mobile Subscriber Identity (IMSI), or account number, is accurately mapped to the correct subscriber record within the database (210).

[0081] For example, when the extracted parameter is a MAC ID, the processing engine (208) locates the subscriber record in the database whose device entry contains a matching MAC ID. In another example, when the extracted parameter is the IMSI, that is a unique numeric identifier assigned to each mobile subscriber in a cellular network, typically stored in the Subscriber Identity Module (SIM) card, and used by the network to authenticate and manage subscriber services. IMSI, the processing engine (208) searches the database for the subscriber profile associated with that IMSI and marks it as the record scheduled for deletion. In yet another example, if multiple parameters (e.g., MAC ID + account number) are provided in the input file, the processing engine (208) cross-verifies them against corresponding fields in the database, thereby enhancing the accuracy of identification and preventing accidental deletion of unrelated subscriber data.

[0082] By accurately identifying the subscriber data using validated parameters, the processing engine (208) establishes a precise link between the input data file and the records in the database (210), thereby enabling the system (108) to perform efficient and error-free deletion operations.

[0083] In an embodiment, the processing engine (208) is configured to perform at least one operation associated with the identified subscriber data. In an embodiment, for performing the at least one operation, the processing engine (208) is furtherconfigured to remove the identified subscriber data associated with the extracted at least one parameter from the database and monitor the removal of the identified subscriber data to provide a feedback related to a status of the removal to a third party. In an embodiment, the processing engine (208) is configured to confirm successful completion of the removal of the identified subscriber data to the third party, record the removed subscriber data to generate a report associated with the removed subscriber data and transmit the generated report to the third party. The identified subscriber data is deleted by matching the extracted unique identifiers, such as MAC IDs or IMSIs, with the corresponding records stored in the database (210). Once a match is confirmed, the processing engine (208) executes a removal command to permanently delete the subscriber data from the database. The deletion may be performed in bulk or sequentially, depending on the number of records, without affecting the overall performance of the database. The processing engine (208) may further be configured to monitor the removal process in real-time and generate a feedback signal indicative of the status of the removal. The feedback is transmitted to a third party, such as a network administrator, the OSS, or the BSS.

[0084] In another embodiment, upon successful completion of the removal, the processing engine (208) is configured to transmit a confirmation message to the third party, thereby ensuring transparency and reliability of the deletion operation. Additionally, the processing engine (208) may record the details of the removed subscriber data, such as the parameter type, the parameter value, the time of deletion, and the status of deletion, in order to generate a structured report. In an embodiment, the processing engine (208) may determine the removed subscriber data based on deletion logs, internal transaction records, or acknowledgements received from the database (210) after executing the deletion command. For example, upon deleting subscriber data associated with a particular MAC ID, the processing engine (208) may record the MAC ID, the corresponding subscriber identity, timestamp of deletion, and status of the deletion as part of the structured report. The generated report may then betransmitted to the third party for auditing, compliance, or archival purposes. In an aspect, the structured report may include report headers comprising information such as a report identifier, report title, generation timestamp, administrator or system ID initiating the deletion, and the type of deletion operation (for example, bulk deletion or customized deletion). The body of the report may further detail the deleted subscriber records, including unique identifiers such as MAC IDs, IMSIs, or Internet Protocol (IP) addresses and corresponding deletion statuses. The generated report may then be transmitted to the third party for auditing, compliance, or archival purposes. Upon successful completion of the deletion process, the processing engine (208) is configured to generate a confirmation message to the administrator or third party such as a regulatory authority, a compliance monitoring system, or a network auditing tool, indicating that the operation was successfully executed. In addition to the confirmation, the processing engine (208) provides a detailed summary of the deleted records. The summary may include, for example, the number of records deleted, the unique identifiers such as MAC IDs or IMSIs corresponding to the deleted records, the timestamp of deletion, and the status of the operation. By providing such confirmation and summary, the system ensures accountability, traceability, and transparency in bulk deletion operations, thereby assisting the administrator in verifying the accuracy and completeness of the executed deletion process.

[0085] In example scenarios, the feedback generated by the processing engine (208) may include one or more of the following: “subscriber not found” if the extracted parameter does not match any record in the database (210); “file not uploaded” if the expected input file containing Media Access Control Identifications (MAC IDs) or other subscriber identifiers has not been received; “file corrupted” if the uploaded input file fails validation checks such as file size, format, or integrity; or “partial deletion” if only a subset of the identified subscriber records could be removed due to database contention or errors. Such detailed feedback ensures that the third party is made awareof the exact status of the deletion operation, thereby supporting error handling, corrective action, and reliable management of subscriber data.

[0086] FIG. 3 illustrates an exemplary flow diagram of a method (300) for managing the subscriber data in the network (106), in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with FIGs 1 and 2.

[0087] In step 302, the method (300) of bulk deletion of the subscriber data, based on the MAC IDs of a plurality of subscribers in the network (106), may get initiated.

[0088] At step 304, the at least one input data file get loaded on the system which is connected to the processing engine (208). The at least one input data file may include a text file, a CSV file, a excel file, and a spreadsheet. The input file may include the list of Media Access Control Identifications (MAC IDs) corresponding to the plurality of subscribers. The input file may indicate the plurality of subscribers along with the list of MAC IDs. The list of MAC IDs is used as an input data for initiating the bulk deletion of the plurality of subscriber data. In an aspect, the input file may be loaded to the processing engine (208) from a local memory of the system (108). For example, the local memory may be a random-access memory (RAM), a cache memory, and a secondary memory. In an aspect, the processing engine (208) may establish a connection for enabling interaction with the database (210) for the deletion process. For example, the connection may involve a data transmission, a data request, storing data, executing a query, and managing subscriber logs. In an aspect, the one or more processor(s) (202) may interact with the database (210) to perform the deletion process.

[0089] At step 306, the processing engine (208) may determine whether the received input file is valid or not. For example, the processing engine (208) may validate the received input file based on various file parameters. The file parameters may include, but are not limited to, a file name, a file format, a file extension, a filesize, and a file path. In an aspect, the processing engine (208) may extract one or more of these parameters from the input file and verify them against predefined validation rules or formats. The processing engine (208) may further determine the validity of the file based on the compliance of the extracted parameters with such predefined formats. For instance, if the input file is expected to follow a valid directory structure, such as path: / / C:\User\ANAP127\Input_docl.csv, the processing engine (208) may check whether the file path syntax is correct, the file extension corresponds to a supported type (e.g., CSV, XML, or JSON), and the file size falls within an acceptable threshold. If any of these validations fail, such as an incorrect path, unsupported format, or a corrupted / incomplete file, the processing engine (208) may classify the file as invalid and trigger an error notification to the network administrator.

[0090] At step 308, in case of the received input file (input data file) is not a valid file, the processing engine (208) may show an error message to the user or network administrator. For example, the error message may include an invalid file message, a does not exist message, and a file not supported message.

[0091] At step 310, in case of the received input file is the valid file, the processing engine (208) may read and parse the input file. For example, reading and parsing the input file involves accessing the list of MAC IDs in the file and bringing them into a temporary memory for processing. For example, the temporary memory may be a cache memory.

[0092] At step 312, the processing engine (208) may fetch one or more subscriber information corresponding to each of the Media Access Control (MAC) Identifiers (IDs) from the database (210). In an aspect, the subscriber information may include, but is not limited to, a subscriber identity (ID), connection logs, Internet Protocol (IP) address, account-related information, and network usage data. For example, the subscriber identity (ID) may correspond to an International Mobile Subscriber Identity (IMSI) or a unique customer ID assigned by the operator. Theconnection logs may indicate details of previous network sessions, such as timestamps and duration of connections. The IP address may represent the dynamic or static address allocated to the subscriber device. The account information may include subscription details, billing status, or prepaid / postpaid plan information. The network usage data may capture parameters such as data consumption, call records, and roaming activities. By fetching such comprehensive subscriber information, the processing engine (208) ensures accurate identification and mapping of the subscriber data that is associated with the MAC ID, which in turn facilitates precise and reliable execution of subsequent deletion operations.

[0093] At step 314, the processing engine (208) may perform a check for the existence of the subscriber data in the database (210). In an aspect, the one or more processor(s) may perform the check based on the unique identifier. For example, the unique identifier may be the MAC IDs. The MAC IDs may be used to identify a single network interface in a one-to-one communication. The MAC ID may be represented as “OO:1A:2B:3C:4D:5E”.

[0094] At step 316, based on the subscriber data check performed by the processing engine (208), if the subscriber data is not found in the data file corresponding to a particular MAC ID, then the particular MAC ID may be skipped from the deletion process. For example, if the processing engine (208) checks for the subscriber information in the database corresponding to the MAC ID ‘OO:1A:2B:3C:4D:5E’ is not found, then that particular MAC ID is skipped for deletion. In an aspect, the deletion process may be performed sequentially based on the MAC ID. The deletion process may be initiated for each of the identified subscriber data.

[0095] At step 318, if the subscriber data is found, then the specific MAC ID related subscriber data may be deleted from the database (210) by the one or more processor(s) (202). For example, if the one or more processor(s) checks for thesubscriber information in the database corresponding to the MAC ID ’OO:1A:2B:3C:4D:7A’ is found, then that particular MAC ID is deleted from the database (210).

[0096] In an aspect, the processing engine (208) may monitor the deletion process and provide a summary report to the network administrator. The network administrator may be the user. For example, the summary report may include a total record deleted, a subscriber ID, a subscriber name, a timestamp, and a subscriber MAC ID. The summary report may include a status and one or more potential issues. For example, the status may indicate the status of deletion of the subscriber data. The status may include a complete status and an incomplete status, corresponding to each of the subscriber data. The one or more potential issues may include a missing data, an incorrect data, and a corrupted data.

[0097] At step 320, the processing engine (208) may terminate the deletion process.

[0098] FIG. 4 illustrates another exemplary flow diagram of the method (400) for managing the subscriber data in the network (106), in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIGs 1, 2, and 3.

[0099] At step (402), the method (400) includes receiving, by a processing engine (208), at least one input data file associated with at least one subscriber from a source. In an embodiment, the method (400) includes verifying, by the processing engine (208), the received at least one input data file using at least one attribute, The at least one attribute comprises at least one of a file size, a file type, and a file status.

[0100] At step (404), the method (400) includes extracting, by the processing engine (208), at least one parameter from the received at least one input data file. In an embodiment, the extracted at least one parameter comprises of at least one MediaAccess Control (MAC) Identifier (ID) associated with the at least one subscriber. In an embodiment, the method (400) includes validating, by the processing engine (208), the extracted at least one parameter using at least one validating parameter, The at least one validating parameter comprises of a parameter length, a parameter format, a parameter type, a parameter character set and a combination thereof.

[0101] At step (406), the method (400) includes comparing, by the processing engine (208), the extracted at least one parameter with at least one subscriber parameter stored in a database (210).

[0102] At step (408), the method (400) includes identifying, by the processing engine (208), the subscriber data corresponding to the extracted at least one parameter based on the comparison.

[0103] At step (410), the method (400) includes performing, by the processing engine (208), at least one operation associated with the identified subscriber data. In an embodiment, the at least one operation comprising removing, by the processing engine (208), the identified subscriber data associated with the extracted at least one parameter from the database. In an embodiment, the at least one operation comprising monitoring, by the processing engine (208), the removal of the identified subscriber data to provide a feedback related to a status of the removal to a third party.

[0104] In an embodiment, the method (400) includes confirming, by the processing engine (208), successful completion of the removal of the identified subscriber data to the third party.

[0105] In an embodiment, the method (400) includes recording, by the processing engine (208), the removed subscriber data to generate a report associated with the removed subscriber data.

[0106] In an embodiment, the method (400) includes transmitting, by the processing engine (208), the generated report to the third party.

[0107] In an exemplary embodiment, the present disclosure discloses a user equipment (UE) communicatively coupled with a network. The coupling comprises steps of receiving, by the network, a connection request from the UE. The coupling comprises steps of sending, by the network, an acknowledgment of the connection request to the UE. The coupling comprises steps of transmitting a plurality of signals in response to the connection request. The subscriber data in the network is managed by a method comprising receiving, by a processing engine, at least one input data file associated with at least one subscriber from a source. The method comprising extracting, by the processing engine, at least one parameter from the received at least one input data file. The method comprising comparing, by the processing engine, the extracted at least one parameter with at least one subscriber parameter stored in a database. The method comprising based on the comparison, identifying, by the processing engine, the subscriber data corresponding to the extracted at least one parameter. The method comprising performing, by the processing engine, at least one operation associated with the identified subscriber data.

[0108] In yet another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing subscriber data in a network. The method comprising receiving, by a processing engine, at least one input data file associated with at least one subscriber from a source. The method comprising extracting, by the processing engine, at least one parameter from the received at least one input data file. The method comprising comparing, by the processing engine, the extracted at least one parameter with at least one subscriber parameter stored in a database. The method comprising based on the comparison, identifying, by theprocessing engine, the subscriber data corresponding to the extracted at least one parameter. The method comprising performing, by the processing engine, at least one operation associated with the identified subscriber data.

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

[0110] 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), a communication port (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor (570) and communication ports (560). The processor (570) may include various modules associated with embodiments of the present disclosure.

[0111] In an embodiment, the communication port (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 fibre, a serial port, a parallel port, or other existing or future ports. The communication port (560) may be chosen depending on the network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (500) connects.

[0112] In an embodiment, the memory (530) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. 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).

[0113] In an embodiment, the mass storage device (550) may be any current or future mass storage solution, which may 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 TechnologyAtachment (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 (e.g., SATA arrays).

[0114] In an embodiment, the bus (520) communicatively couples the processor(s) (570) with the other memory, storage, and communication blocks. The bus (520) 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 (570) to the computer system (500).

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

[0116] The present disclosure provides a technical advantage in the field of telecommunication networks, particularly in subscriber data management, by enabling automated and efficient deletion of subscriber records. The system performs bulk deletion of subscriber data from a network database, streamlines and automates large- scale deletion operations using unique identifiers, and ensures simultaneous removal of multiple records without compromising database performance. Once the deletion process is successfully completed, the system generates a confirmation mechanism, such as a structured report containing details of the deleted records (e.g., record identifiers, deletion time, and status), and transmits the report to the networkadministrator or a third-party compliance body for auditing and validation. Additionally, a notification message may be provided indicating successful completion and the number of records removed. The deletion criteria may include subscriber data older than a retention period, user-initiated deletion requests, de-registered or inactive accounts, or compliance with regulatory mandates. These features collectively enable automated, transparent, and flexible deletion of subscriber data, optimize resource utilization, and enhance the overall scalability of the network. Furthermore, it supports customized deletion scenarios, thereby offering flexibility to meet diverse regulatory and operational requirements. These advantages collectively enable efficient management of subscriber data deletion, optimize resource utilization, and enhance the overall performance and scalability of the network.ADVANTAGES OF THE PRESENT DISCLOSURE

[0117] The present disclosure provides a method and a system for performing bulk deletion of subscriber data from a database in a network.

[0118] The present disclosure provides a method and a system for streamlining and automating bulk deletion of subscriber data for a large-scale database using unique identifiers such as Media Access Control (MAC) Identifiers (IDs).

[0119] The present disclosure provides a method and a system for deleting multiple subscriber data simultaneously without affecting the performance of a database.

[0120] The present disclosure provides a method and a system for performing customized deletion based on different deletion scenarios, such as deletion using specific identifiers, ranges of identifiers, or file-based criteria.

[0121] The present disclosure provides a method and a system for enabling efficient management of subscriber data deletion in the network by ensuring accuracy, maintaining data integrity, and providing confirmation or reports to administrators.

[0122] The present disclosure provides a method and a system for optimizing resource utilization within the network to enhance network performance while minimizing the administrative workload.

[0123] The present disclosure provides a method and a system for automating the deletion process, allowing network administrators to delete multiple subscriber records in bulk with minimal effort and in a fraction of the time it would take manually.

[0124] The present disclosure provides a method and a system for ensuring precise deletion of subscriber records associated with targeted identifiers, thereby reducing the risk of erroneous deletions and safeguarding database integrity.

[0125] The present disclosure provides a method and a system for handling large-scale operations, making the solution suitable for telecommunications networks with extensive subscriber databases, while maintaining high performance even during bulk deletions.

[0126] The present disclosure provides a method and a system for offering flexibility in defining deletion criteria, thereby enabling tailored deletion operations in line with the specific requirements of different network scenarios.

[0127] The present disclosure provides a method and a system for performing bulk deletion of subscriber data from a database in a network, where the deletion may be carried out based on specific conditions such as data age (e.g., records older than three years), user-initiated requests, subscriber deregistration, or compliance with regulatory mandates, thereby ensuring accurate and policy-driven deletion.

[0128] The present disclosure provides a method and a system for performing bulk deletion of subscriber data from a database in a network, where interaction with the NFs ensures controlled execution of the deletion process. The NFs may authenticate or validate subscriber data prior to bulk deletion, confirm service disconnection or deregistration events, and synchronize with the bulk deletion module to maintain network-wide consistency, thereby preventing accidental deletion of active subscriber records.

[0129] The present disclosure provides a method and a system for ensuring security in the deletion process by implementing mechanisms such as administrator authentication, role-based access control, cryptographic verification of deletion commands, and audit logging of deletion activities, thereby preventing unauthorized or malicious deletions.

[0130] The present disclosure provides a method and a system for including feedback mechanisms, where the system generates structured deletion confirmation reports indicating deleted identifiers, deletion status, timestamps, and error summaries, and transmits the reports to administrators or third-party compliance entities without affecting overall network performance.

[0131] The present disclosure provides a method and a system for handling errors and recovery in deletion operations by retrying failed deletions, isolating problematic records, maintaining detailed error logs, and notifying administrators in case of failure, thereby ensuring reliability, traceability, and operational resilience.

[0132] The present disclosure provides a method and a system for addressing compliance with data protection laws and regulations, including but not limited to international, regional, and jurisdiction-specific mandates, by ensuring secure, auditable, and policy-driven deletion of subscriber data while maintaining accountability, data transparency, and legal adherence.

Claims

CLAIMS1. A method (400) for managing subscriber data in a network (106), the method (400) comprising: receiving (402), by a processing engine (208), at least one input data file associated with at least one subscriber from a source; extracting (404), by the processing engine (208), at least one parameter from the received at least one input data file; comparing (406), by the processing engine (208), the extracted at least one parameter with at least one subscriber parameter stored in a database (210); based on the comparison, identifying (408), by the processing engine (208), the subscriber data corresponding to the extracted at least one parameter; and performing (410), by the processing engine (208), at least one operation associated with the identified subscriber data.

2. The method (400) as claimed in claim 1, further comprising: verifying, by the processing engine (208), the received at least one input data file using at least one attribute, wherein the at least one attribute comprises at least one of a file size, a file type, and a file status.

3. The method (400) as claimed in claim 1, further comprising: validating, by the processing engine (208), the extracted at least one parameter using at least one validating parameter, wherein the at least one validating parameter comprises of a parameter length, a parameter format, a parameter type, a parameter character set and a combination thereof.

4. The method (400) as claimed in claim 1, wherein the at least one operation comprising:removing, by the processing engine (208), the identified subscriber data associated with the extracted at least one parameter from the database; and monitoring, by the processing engine (208), the removal of the identified subscriber data to provide a feedback related to a status of the removal to a third party.

5. The method (400) as claimed in claim 4, further comprising: confirming, by the processing engine (208), successful completion of the removal of the identified subscriber data to the third party; recording, by the processing engine (208), the removed subscriber data to generate a report associated with the removed subscriber data; and transmitting, by the processing engine (208), the generated report to the third party.

6. The method (400) as claimed in claim 1, wherein the extracted at least one parameter comprises of at least one Media Access Control (MAC) Identifier (ID) associated with the at least one subscriber.

7. A system (108) for managing subscriber data in a network (106), the system (108) comprising: a memory (204); a processing engine (208) coupled to the memory (204) and is configured to execute instructions stored in the memory (204) to: receive at least one input data file associated with at least one subscriber from a source; extract at least one parameter from the received at least one input data file;compare the extracted at least one parameter with at least one subscriber parameter stored in a database (210); based on the comparison, identify the subscriber data corresponding to the extracted at least one parameter; and perform at least one operation associated with the identified subscriber data.

8. The system (108) as claimed in claim 7, wherein the processing engine (208) is further configured to: verify the received at least one input data file using at least one attribute, wherein the at least one attribute comprises at least one of a file size, a file type, and a file status.

9. The system (108) as claimed in claim 7, wherein the processing engine (208) is further configured to: validate the extracted at least one parameter using at least one validating parameter, wherein the at least one validating parameter comprises of a parameter length, a parameter format, a parameter type, a parameter character set and a combination thereof.

10. The system (108) as claimed in claim 7, wherein, for performing the at least one operation, the processing engine (208) is further configured to: remove the identified subscriber data associated with the extracted at least one parameter from the database; and monitor the removal of the identified subscriber data to provide a feedback related to a status of the removal to a third party.

11. The system (108) as claimed in claim 10, wherein the processing engine (208) is further configured to: confirm successful completion of the removal of the identified subscriber data to the third party; record the removed subscriber data to generate a report associated with the removed subscriber data; and transmit the generated report to the third party.

12. The system (108) as claimed in claim 7, wherein the extracted at least one parameter comprises of at least one Media Access Control (MAC) Identifier (ID) associated with the at least one subscriber.

13. A user equipment (UE) communicatively coupled with a network (106), the coupling comprises steps of: receiving, by the network (106), a connection request from the UE; sending, by the network (106), an acknowledgment of the connection request to the UE; and transmitting a plurality of signals in response to the connection request, wherein subscriber data in the network (106) is managed by a method as claimed in claim 1.

14. 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 managing subscriber data in a network (106), the method (400) comprising: receiving (402), by a processing engine (208), at least one input data file associated with at least one subscriber from a source;extracting (404), by the processing engine (208), at least one parameter from the received at least one input data file; comparing (406), by the processing engine (208), the extracted at least one parameter with at least one subscriber parameter stored in a database (210); based on the comparison, identifying (408), by the processing engine (208), the subscriber data corresponding to the extracted at least one parameter; and performing (410), by the processing engine (208), at least one operation associated with the identified subscriber data.

Images