Method and system for performing customer data adjustment

Abstract

The disclosure relates to a method (500) and system (108) for performing customer data adjustment operations in a network. The method includes authenticating, via an authentication unit (208), a user (102) using one or more authentication techniques to ensure that only authorized user can initiate the data adjustment operation. Upon successful authentication, a data management unit (210) stores customer-related adjustment data associated with the user (102). The data management unit (210) receives a bulk adjustment command from the user (102) through a command line interface (CLI) and forwards the command to a network node for execution. The network node determines adjustment parameters based on the stored data and predefined rules and performs the adjustments accordingly. The method facilitates large-scale data corrections, minimizes manual intervention, and ensures accurate, real-time compensation for customers.

Description

METHOD AND SYSTEM FOR PERFORMING CUSTOMER DATA ADJUSTMENTRESERVATION 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 performing a customer data adjustment operation.DEFINITION

[0003] The term ‘Customer data adjustment operation’ used hereinafter in the specification refers to adjusting or recovering and updating specific service-related changes in a customer’s account within a network. These adjustments may include adding data limits, changing service status, changing bandwidth and similar. This ensures the customer’s service is aligned with their plan or operational needs.

[0004] The term ‘Bulk data adjustment tool’ used hereinafter in the specification refers to a component that is configured to adjust data for a large number of customers simultaneously.

[0005] The term ‘CLI’ used hereinafter in the specification refers to a command-line interface. The CLI is a text-based interface where authorized users caninteract with the bulk adjustment tool by entering specific commands. For example, a bulk adjustment command can be entered using the CLI.

[0006] The term ‘CHF-BNG node’ used hereinafter in the specification refers to a charging function broadband gateway node. The CHF-BNG node is responsible for adjusting the customer data.

[0007] The term ‘bulk adjustment command’ used hereinafter in the specification refers to an instruction which is executed using the CLI to initiate the customer adjustment process.

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

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

[0010] Nowadays, data management plays an essential role in the operations of businesses across various industries. In telecommunication industries, managing customer data is essential for delivering reliable and personalized service. The customer data, which may include billing details, service preferences, usage statistics, and similar information, is used to offer tailored service plans, optimize customer experience, and meet regulatory compliance. With the rise of fifth-generation (5G) networks and now sixth-generation (6G) networks in a broadband network, ensuring the availability and integrity of customer data becomes even more important. However, data loss remains a significant challenge that can occur due to various reasons, such assystem failures (for example, a hardware crash or software malfunction), human errors (for example, accidental deletions of data or improper configuration), or cyber-attacks (for example, ransomware or malicious breaches).

[0011] Traditionally, data recovery methods such as backup and recovery, file recovery, log-based recovery, and similar are often used to restore lost data. However, these methods can be time-consuming and cumbersome and may not guarantee complete data restoration. Additionally, the traditional data recovery methods are often inconsistent, which may further lead to poor customer experience.

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

[0013] In an exemplary embodiment, a method for performing a customer data adjustment operation is described. The method includes authenticating, by an authentication unit, a user using one or more authentication techniques. The one or more authentication techniques are utilized for initiating the customer data adjustment operation. The method includes storing, by a data management unit, customer-related adjustment data associated with the user upon successful authentication. The method includes receiving, by the data management unit, a bulk adjustment command entered by the user and forwarding, by the data management unit, the bulk adjustment command to a network node for performing the customer data adjustment operation.

[0014] In some embodiments, for performing the customer data adjustment operation, the method includes determining, by the network node, one or more adjustment parameters based on the stored customer-related adjustment data and one or more predefined rules upon receiving the bulk adjustment command. Further, the method includes performing, by the network node, the customer data adjustment operation based on the determined one or more adjustment parameters.

[0015] In some embodiments, the network node includes one or more network elements, servers, or cloud-based computing nodes configured to receive the bulk adjustment command from the data management unit .

[0016] In some embodiments, the customer- related adjustment data includes service information associated with a plurality of customers that is stored in a secure manner to ensure data privacy and integrity.

[0017] In some embodiments, the one or more authentication techniques comprise at least one of at least one of single-factor authentication or multi-factor authentication techniques to ensure that only authorized users are permitted to initiate the customer data adjustment operation.

[0018] In another exemplary embodiment, a system for performing a customer data adjustment operation is described. The system includes an authentication unit and a data management unit. The authentication unit is configured to authenticate a user using one or more authentication techniques. The one or more authentication techniques are utilized for initiating the customer data adjustment operation. The data management unit is configured to store customer-related adjustment data associated with the user upon successful authentication, receive a bulk adjustment command entered by the user and forward the bulk adjustment command to a network node for performing the customer data adjustment operation.

[0019] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to perform a method for performing a customer data adjustment operation is described. The method includes authenticating, by an authentication unit, a user using one or more authentication techniques. The one or more authentication techniques are utilized for initiating the customer data adjustment operation. Themethod includes storing, by a data management unit, customer-related adjustment data associated with the user upon successful authentication. The method includes receiving, by the data management unit, a bulk adjustment command entered by the user and forwarding, by the data management unit, the bulk adjustment command to a network node for performing the customer data adjustment operation.

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

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

[0022] An objective of the present disclosure is to provide a system and a method for performing customer data adjustment and / or recovery (or restoration) operations.

[0023] Another objective of the present disclosure is to minimize downtime during a customer data adjustment or restoration process by implementing a commandbased restoration approach.

[0024] Yet another objective of the present disclosure is to provide a quick and reliable restoration of customer data through a streamlined bulk adjustment process.

[0025] Yet another objective of the present disclosure is to provide a bulk adjustment command line interface (CLI) command that executes the customer data adjustment operation in bulk, significantly reducing processing time and enhancing the system’s operational efficiency.

[0026] Another objective of the present disclosure is to simplify the customer data adjustment procedure, allowing administrators to perform the adjustments with minimal effort.

[0027] Another objective of the present disclosure is to optimize resource utilization by employing the bulk adjustment CLI command, which consumes fewer system resources.

[0028] Another objective of the present disclosure is to provide a system that is configured to scale horizontally to manage large customer datasets utilizing distributed systems for the bulk adjustment process.

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

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

[0031] FIG. 1 illustrates an exemplary network architecture in which or with a system configured for performing a customer data adjustment operation may be implemented, in accordance with embodiments of the present disclosure.

[0032] FIG. 2 illustrates an exemplary block diagram of the system configured for performing the customer data adjustment operation, in accordance with embodiments of the present disclosure.

[0033] FIG. 3 illustrates an exemplary system architecture for performing the customer data adjustment operation, in accordance with an embodiment of the present disclosure.

[0034] FIG. 4 illustrates an exemplary process flow for performing the customer data adjustment operation, in accordance with an embodiment of the present disclosure.

[0035] FIG. 5 illustrates an exemplary flow diagram of a method performing the customer data adjustment operation, in accordance with an embodiment of the present disclosure.

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

[0037] 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 - Network108 - System200 -Block Diagram202 - Processor(s) 204 - Memory206 - Interface(s)208 - Authentication Unit210 - Data Management Unit212 - Database 300 - System Architecture302 - Network node304 - Service plan determination module306 - Customer data extraction module308 - Database 310 - Local Memory400 - Process Flow Diagram500 - Method Flow Diagram600 - Computer System610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port(S)670 - ProcessorDETAILED DESCRIPTION

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

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

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

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

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

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

[0044] 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 other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0045] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that manyembodiments 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.

[0046] In the field of data management, particularly related to customer data, traditional data recovery techniques such as backup and restore, file recovery, or logbased recovery are often used to restore lost or corrupted data. However, these conventional techniques often exhibit several limitations. The traditional data restoration process is generally time-consuming and complex, often requiring manual intervention for each individual customer record. Moreover, traditional recovery mechanisms may not ensure complete data restoration and can result in inconsistencies across data records. Such inconsistencies not only affect the accuracy of restored data but also lead to degraded system performance and a poor customer experience. Additionally, graphical user interface (GUI)-based tools used for recovery are often resource-intensive and may struggle to handle large-scale data operations efficiently, particularly when processing high data volumes or executing repeated recovery tasks.

[0047] To overcome the limitations of conventional recovery mechanisms, the present disclosure provides an optimized system and method for reliable and efficient adjustment of customer data using a Bulk Adjustment Command-Line Interface (CLI) command. The method enables authorized users to perform bulk adjustments of customer data in a single operation, thereby eliminating the need for individual record handling. The CLI-based bulk adjustment mechanism integrates seamlessly with external systems and automation scripts, allowing data to be fetched from external sources (such as Excel sheets), modified as per predefined adjustment parameters, and updated automatically within the system. The system significantly reduces the time,complexity, and manual effort required for customer data restoration. The bulk adjustment CLI mechanism enhances operational efficiency, supports large-scale data processing, and consumes fewer system resources compared to GUI-based recovery tools. Furthermore, the method ensures consistency, reliability, and accuracy of customer data adjustments, thereby improving overall system performance and user experience.

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

[0049] FIG. 1 illustrates an exemplary network architecture 100 in which or with a system 108 configured for performing a customer data adjustment operation may be implemented, in accordance with embodiments of the present disclosure.

[0050] 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 as the 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.

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

[0052] 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, mobile phone, smartphone, 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.

[0053] In FIG. 1, the UE 104 may establish communication with 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. In an embodiment, 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.

[0054] In an exemplary embodiment, the user 102 may utilize the UE 104 to interact with the system 108 via the network 106. The UE 104 may provide an interactive user interface enabling the user 102 to initiate a bulk adjustment operation by entering a corresponding bulk adjustment command through a command-line interface (CLI) or a graphical interface. Upon initiation, the UE 104 transmits the bulk adjustment command to the system 108, thereby triggering the customer data adjustment process. The system 108 authenticates the user 102 to ensure that only authorized personnel can perform data adjustment operations. Once authentication is successful, the system 108 stores and reads customer-related data from a data sheet, identifying the specific records designated for adjustment. The command interfacewithin the system 108 then forwards the bulk adjustment command to a Charging Function-Broadband Network Gateway (CHF-BNG) node, which parses the bulk adjustment command to determine the scope of adjustment, such as customer identifiers, adjustment type, or range of data modification. The CHF-BNG node then executes the data adjustment and updates multiple customer records in a single operation to ensure consistency and efficiency. In an example, the user 102 may enter the bulk adjustment command for a plurality of airfiber customers, such as adjust bulk- - customers afl023,afl024,afl025, compensate 0.3 GB, period 3rdJanuary 2024, type carry forward. Here, the bulk adjustment command specifies the list of affected airfiber customers, the amount of data to be compensated (0.3 GB), the relevant billing period (3rdJanuary 2024), and the adjustment type (carry forward unused data). Upon receiving this command, the system 108 parses the instructions and forwards them to the network node (e.g., CHF-BNG) for execution.

[0055] In an embodiment, the UE 104 may provide real-time feedback to the user 102 regarding the status of the customer data adjustment operation, such as progress indicators, confirmation of successful adjustments, or error notifications in case of inconsistencies. This interactive feedback mechanism allows the user 102 to monitor, verify, or reinitiate the customer data adjustment operation. Upon completion, the system 108 performs verification to ensure that the data adjustment was executed successfully and that the updated data is accurate, accessible, and synchronized within the datasheet.

[0056] 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 performfunctions described as being performed by one or more other components of the network architecture 100.

[0057] FIG. 2 illustrates an exemplary block diagram of the system 108 configured for performing the customer data adjustment operation, in accordance with an embodiment of the present disclosure.

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

[0059] 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, an authentication unit 208, a data management unit 210 and a database 212.

[0060] In an implementation, the authentication unit 208 and the data management unit 210 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 authentication unit 208 and the data management unit 210 may be processor-executable instructions stored on a non-transitory machine- readable storage medium and the hardware for the authentication unit 208 and the data management unit 210 may include a processing resource (for example, the one or more processors 202) to execute such instructions. In one implementation, the authentication unit 208 and the data management unit 210 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. In an example, the system 108 may be interchangeably referred to as a bulk data adjustment tool. The system 108 (i.e., the bulk adjustment tool) facilitates the automatic identification and adjustment of data for a plurality of customers, i.e., a large number of customers or customers in bulk. The system 108 automates the process of adjusting the customer data in case the customer data is lost due to various conditions, such as system failures, human errors, changes in the policies of network operators, cyber-attacks, or similar, reducing the time and manual effort required compared to handling each customer data individually. Performing bulk adjustment in one operation is faster than processing them one at a time.

[0061] The customer data adjustment operation is the process of restoring, updating, or correcting various network services associated with the plurality of customers’ accounts in a particular network environment. The customer data adjustment operation is essential for managing one or more network services and ensuring that the one or more network service experience of each of the plurality of customers is consistent and accurate based on their subscription or usage. Due tosystem failures, human error, or cyber-attacks that lead to data loss or inconsistencies, the customer data adjustment operation adjusts or restores the lost data. The lost data may be, for example, loss of connectivity status, plan mismatch or misapplication, loss of customer device registration number, inaccurate billing or payment information, loss of bandwidth, and loss of data usage history.

[0062] In an embodiment, the authentication unit 208 is configured to authenticate a user (such as the user 102) using one or more authentication techniques. In an example, the user 102 may be a network administrator or network operator. The one or more authentication techniques are utilized for initiating the customer data adjustment operation. The authentication process involves identifying the authorized person to access the system 108 (i.e., the bulk data adjustment tool). The authentication process ensures that only an authorized user (such as the user 102) initiates the customer data adjustment operation, leading to more secure and reliable adjustments. In an aspect, the one or more authentication techniques may include single-factor or multifactor authentication techniques, such as a password-based authentication, a two- factor authentication involving a one-time password (OTP), a biometric authentication, a token-based authentication, a multi-factor authentication combining two or more authentication parameters, or a certificate-based authentication employing a digital certificate, which may be utilized for verifying the identity of the user 102.

[0063] In an aspect, the authentication unit 208 is triggered to start its processing when the user 102 attempts to access the system 108 (i.e., the bulk data adjustment tool) via a command interface. For example, when the user 102 launches the command interface to initiate the customer data adjustment operation, the system 108 automatically invokes the authentication unit 208 to verify the identity of the user 102 before allowing any further operations. The trigger may be generated by the user action, such as entering a username, clicking a login or submit button, and the like. Upon detecting such an action, the authentication unit 208 performs the authenticationprocess utilizing the one or more authentication techniques to ensure that the user 102 is authorized to perform the customer data adjustment operation. In a password-based authentication, the user 102 enters a valid username and password combination using the associated UE 104 to authenticate himself / herself before initiating the customer data adjustment operation. Further, the authentication unit 208 compares the entered username and password combination against stored credentials in a secure database. If the credentials are matched, the user is granted access to the system 108. In a two- factor authentication scenario, once the password is verified, a one-time password (OTP) is generated and sent to a registered mobile number or email of the user 102, which must be entered by the user 102 to complete the verification. In a biometric authentication, the user’s fingerprint or facial scan is matched with the pre-stored biometric data to confirm identity. In token-based authentication, the user 102 utilizes a security token or smart card that generates time-based or event-based codes for verification. In multi-factor authentication, the combination of credentials, such as a password and biometric verification, may be used to enhance security. In certificatebased authentication, a digital certificate issued by a trusted certificate authority (CA) is employed by the authentication unit 208 to verify the identity of the user 102 before allowing access to the system 108.

[0064] In an exemplary scenario, the user 102, who may be the network administrator managing a plurality of AirFiber accounts of the plurality of customers, first enters a username and password into the command interface provided by the system 108. Upon successful entry of correct credentials, the authentication unit 208 may prompt the user 102 for a second authentication factor, such as an OTP sent to the registered mobile number or email, or verification via a security token. Once the user 102 provides the OTP, the authentication unit 208 validates both authentication factors to ensure that the user 102 is authorized.

[0065] In an embodiment, upon successful authentication, the data management unit 210 is configured to store customer-related adjustment data associated with the user 102. The customer adjustment data may be stored in a datasheet, such as an Excel sheet, in a secure manner to ensure data privacy and integrity. In an aspect, the customer-related adjustment data may include service information associated with the plurality of customers, which may include, but are not limited to, unique customer identifiers such as media access control identifiers (MAC ID), customer data usage limits, billing cycle information, usage metrics, service preferences, and billing cycle information. The unique customer identifiers uniquely identify each customer to ensure accurate adjustments and may include values such as a Customer ID (e.g., AF1023), the media access control (MAC ID) of the equipment (such as an AirFiber router) associated with the customer, or an account number. The customer data usage limits define the maximum data a customer can use within a defined period, such as a daily limit of 1 GB, a monthly limit of 30 GB, or a capped plan of 50 GB per month. The billing cycle information specifies the start and end dates of a customer’s billing period to calculate charges, unused data, or compensations, for example, a cycle from the 1st to the 30th of a month or from the 15th of one month to the 14th of the next month. The usage metrics represent records of the customer’s actual data consumption used to determine adjustments, such as 0.7 GB used on a particular date, or a total of 28 GB consumed in a month. The service preferences correspond to customer-defined settings affecting service delivery or adjustments and may include a preferred compensation method (carry forward unused data versus bonus credit), preferred notification mode (short message service (SMS) or email), or selected plan features such as speed throttling after the data limit is reached.

[0066] In an example, for AirFiber customers, the datasheet may contain multiple rows, each corresponding to a unique subscriber account. Each row may include details such as the Customer ID, MAC ID of the customer’s AirFiber router, daily or monthly data limit (e.g., 1 GB per day), actual data consumed, unutilized data,compensated data for the next day, and billing period. For example, if an AirFiber customer with Customer ID AF1023 and MAC ID C8-7F-54-AB-9C-22 did not receive the full 1 GB data quota on a particular day due to a network fault, the datasheet entry for that customer may reflect 0.7 GB used and 0.3 GB pending compensation. This structured format enables the system 108 to easily identify the affected customers and perform accurate bulk data adjustment operations.

[0067] In an embodiment, the data management unit 210 is configured to receive a bulk adjustment command entered by the user 102. The bulk adjustment command may be received via a command line interface (CLI) or any other suitable user interface configured with predefined options or custom scripts. The bulk adjustment command represents an instruction from the authorized user to perform customer data adjustments for one or more customers in a single operation. For example, the bulk adjustment command may specify parameters such as the list of customers to be adjusted, the amount of unused data to be credited, the affected billing cycle, date and year, specific service attributes to be modified and similar. In an example, the user 102 may enter the bulk adjustment command for the plurality of airfiber customers, such as adjust bulk- customers afl023,afl024,afl025, compensate 0.3 GB, period January 3, 2024, type carry forward. Here, the bulk adjustment command specifies the list of affected airfiber customers, the amount of data to be compensated (0.3 GB), the relevant billing period (January 3, 2024), and the adjustment type (carry forward unused data).

[0068] In an embodiment, the data management unit 210 is configured to forward the bulk adjustment command to a network node for performing the customer data adjustment operation. In an aspect, the network node may be one or more network elements, servers, or cloud-based computing nodes. In an example, the network node may be a Charging Function (CHF) and Broadband Network Gateway (BNG) node. The CHF-BNG node 210 facilitates the execution of the customer data adjustmentoperation. The CHF-BNG node is responsible for managing network services and network traffic for customers, such as managing data flow related to broadband services, ensuring policy enforcement, and similar tasks.

[0069] Upon receiving the bulk adjustment command, the network node is configured to determine one or more adjustment parameters based on the stored customer-related adjustment data and one or more predefined rules. The one or more adjustment parameters may include data usage limits to be adjusted, scope of data to be adjusted, a compensation value, and an adjustment type. The network node first analyzes the customer-related adjustment data, such as the unique customer identifiers, (MAC ID, customer ID, etc.), data usage limits, usage metrics, service preferences, and billing cycle information, to identify discrepancies between the expected and actual data usage or service delivery. Additionally, the network node compares the actual usage metrics with the defined limits and evaluates whether any compensation or adjustment is required according to the predefined rules such as underutilization of data, billing cycle alignment, service preference compliance, maximum compensation limits, and priority handling for high-tier customers. Based on this analysis, the network node determines which the one or more adjustment parameters need adjustment, including the amount of data to be credited, the scope of affected customers or billing periods, the type of adjustment (e.g., carry forward unused data or bonus credit), and the specific compensation value. Further, the network node is configured to perform the customer data adjustment operation based on the determined one or more adjustment parameters. In an example, for an AirFiber customer with Customer ID AF1023 and a daily limit of 1 GB, the usage metrics may indicate that only 0.7 GB was consumed on a particular day. Based on predefined rules, the network node determines the data usage limit to be adjusted (0.3 GB), the scope of adjustment (e.g., daily usage for that specific customer), the compensation value (0.3 GB to be credited), and the adjustment type (carry forward unused data to the next day or apply bonus data credit). The network node may repeat this process for multiple customers, using theunique identifiers to ensure that adjustments are applied accurately and in accordance with their service preferences and billing cycle.

[0070] In an embodiment, once the data adjustment operation is performed, the system 108 initiates a verification process to ensure that the adjustment is executed successfully and the modified data is accessible and usable by the network and associated systems. The verification process may include performing a consistency check to confirm that the adjusted values, such as updated data usage limits, billing information, or compensation values, are correctly stored in the database 212 without corruption or loss. Further, the system 108 may validate the accessibility of the adjusted data by executing a read-back operation from the data management unit 210 and comparing the retrieved data with the intended adjustment parameters. In an example, if the data usage limit of a customer is increased from 100 GB to 120 GB, the system 108 verifies that the new limit is accurately reflected in the database 212.

[0071] In an embodiment, the system 108 is configured to provide real-time notifications to the plurality of customers upon completion of the data adjustment operation. Upon updating the customer-related adjustment data, the data management unit 210 generates a notification message indicating the adjustment details, such as the amount of data credited, the affected billing period, and the adjustment type. The notification may be delivered via one or more communication channels, including short message service (SMS), email, mobile application push notifications, or in-app alerts. In an example, when an AirFiber customer’s unused data of 0.3 GB is carried forward to the next day, the system 108 automatically sends a message notifying the customer of the updated data balance and the adjustment type. This enhances transparency, improves customer experience, and helps address potential disputes related to data compensation or adjustments.

[0072] In an embodiment, the system 108 is extended to support loT devices and 5G network environments, enabling automated customer data adjustments basedon device activity, real-time network data, or service requirements. The data management unit 210 collects usage metrics from connected loT devices or 5G network sessions, including data consumption, session duration, and service-specific parameters. Upon detecting discrepancies between allocated and actual usage, or based on predefined adjustment rules, the system 108 may automatically generate bulk adjustment commands for execution by the network node (e.g., CHF-BNG). In an example, for a smart home deployment, if multiple loT devices of the plurality of customers account consume less data than allocated during a billing cycle, the system 108 credits the unused portion in the next cycle or applies a bonus allocation according to the customer preferences. This ensures accurate, real-time adjustments, and improves service flexibility, of the system 108.

[0073] Further, the system 108 may incorporate artificial intelligence (Al) and machine learning models to perform predictive adjustments. The Al models analyze historical usage patterns, customer behavior, and network activity to proactively suggest or automatically apply adjustments. For example, if multiple loT devices associated with a single account of the customer consistently consume less data than allocated, the system 108 may predict future unused data and preemptively carry it forward, or detect anomalies indicating potential misuse or fraud. In an example, the system 108 credits unused data in the next billing cycle or applies a bonus allocation automatically, improving accuracy and customer experience.

[0074] In an embodiment, the system 108 is configured to optimize the data adjustment process using a distributed architecture to ensure scalability and efficient handling of large customer datasets or large volumes of concurrent data adjustments. The distributed architecture may include a plurality of interconnected processing nodes or microservices that divide the bulk adjustment tasks into smaller, parallel operations. Each processing node may be configured to handle a subset of customer-related adjustment data, such as customers belonging to a particular region, service plan, orbilling cycle, thereby reducing processing latency and avoiding system bottlenecks. In an example, when thousands of customers require simultaneous adjustment of data usage limits or compensation values, the distributed system dynamically allocates the workload across multiple compute instances to execute the adjustments in parallel. The network node may further employ load-balancing mechanisms to distribute incoming bulk adjustment commands evenly among processing nodes and use synchronization modules to maintain consistency of adjusted data across the distributed environment.

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

[0076] FIG. 3 illustrates an exemplary system architecture 300 configured to perform the customer data adjustment operation, in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with FIG. 1 and FIG. 2.

[0077] As shown in FIG. 3, the system architecture 300 includes a network node 302 , a service plan determination module 304, a customer data extraction module 306, a database 308 and a local memory 310.

[0078] In an embodiment, the bulk adjustment command is entered by the user 102 via the CLI or command interface of the bulk adjustment tool (referred to as the system 108 and not shown in FIG. 3 for the sake of clarity). The bulk adjustment tool forwards the bulk adjustment command to the network node (for e.g., CHF-BNG node) 302. Further, the network node 302 parses the bulk adjustment command to determine the specific parameters, such as the scope of the customer data to be adjusted, by reading and validating the customer-related adjustment data stored in the datasheet.

[0079] The network node 302 may perform a check to identify if the customer is valid. The customer data extraction module 306 is responsible for extracting all the customer-related information from the local memory 310. Upon determining that the customer is valid or the customer-related adjustment data exists in the local memory 310, network node 302 performs another check to fetch data about the customer's ongoing plan to identify whether the customer is associated with any ongoing plan, such that the customer adjustment operation can be performed. The service plan determination module 306 is responsible for extracting all the updates related to the customer’s plan, information about the customer’s ongoing service plan, service status, and billing information. Upon identifying that the customer’s plan exists, the customer data adjustment operation is performed by the network node 302. Further, the network node 302 updates the local memory 310 and the database 208 about the successful adjustment operation.

[0080] FIG. 4 illustrates an exemplary process flow 400 for performing the customer data adjustment operation, in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIG. 1, FIG. 2 and FIG. 3.

[0081] In an embodiment, the user 102 (or the CLI user) logs into the system 108 (i.e., bulk data adjustment tool) using the one or more authentication techniques. Upon successful authentication, the user 102 enters the bulk adjustment command using the CLI provided by the system 108 (i.e., bulk data adjustment tool). Further, the system 108 forwards the bulk adjustment command to the network node 302.

[0082] At step 402, the network node 302 executes the bulk adjustment command.

[0083] At step 404, the network node 302 reads and validates the customer- related adjustment data stored in the datasheet or customer adjustment Excel sheet. By reading and validating the datasheet, the network node 302 parses the bulk adjustmentcommand to determine the one or more adjustment parameters of the customer-related adjustment data, such as the scope of data to be adjusted.

[0084] At step 406, the network node 302 determines whether the identified customer exists in the local memory 310.

[0085] Upon determining that the customer exists in the local memory 310, branch ‘yes’ is followed from step 406. Further, at step 408, the network node 302 determines whether the identified customer has an ongoing plan or whether the customer’s plan exists. Alternatively, if the customer does not exist in the local memory 310, branch ‘no’ is followed from step 406 and at step 410, the bulk adjustment command is rejected.

[0086] Upon determining that the customer plan exists, branch ‘yes’ is followed from step 408 and at step 412, the customer data is adjusted by the network node 302. Once the customer data is adjusted, the network node 302 verifies that the adjustment is successful and that the customer data is accessible and usable.

[0087] Alternatively, branch ‘no’ is followed from step 408 if the network node 302 determines that the customer has no ongoing plan, and at step 414, the network node 302 rejects the bulk adjustment command.

[0088] FIG. 5 illustrates an exemplary flow diagram of a method 500 for performing the customer data adjustment operation, in accordance with an embodiment of the present disclosure. FIG. 5 is explained in conjunction with FIG. 2.

[0089] At step 502, the method 500 includes authenticating, by the authentication unit 208, the user 102 using the one or more authentication techniques. The one or more authentication techniques are utilized for initiating the customer data adjustment operation. In an aspect, the one or more authentication techniques includes at least one of single-factor authentication or multi-factor authentication techniques toensure that only authorized users are permitted to initiate the customer data adjustment operation.

[0090] At step 504, the method 500 includes storing, by the data management unit 210, customer-related adjustment data associated with the user upon successful authentication. In an aspect, the customer-related adjustment data comprises service information associated with a plurality of customers that is stored in a secure manner to ensure data privacy and integrity..

[0091] At step 506, the method 500 includes, receiving, by the data management unit 210, the bulk adjustment command entered by the user 102. In an aspect, the bulk adjustment command is entered via the CLI.

[0092] At step 508, the method 500 includes, forwarding, by the data management unit 210, the bulk adjustment command to the network node (i.e., the network node 302) for performing the customer data adjustment operation. Upon receiving the bulk adjustment command, the network node is configured to determine the one or more adjustment parameters based on the stored customer-related adjustment data and the one or more predefined rules. In an aspect, the one or more adjustment parameters may include data usage limits to be adjusted, scope of data to be adjusted, a compensation value, and an adjustment type. Further, the network node is configured to perform the customer data adjustment operation based on the determined one or more adjustment parameters.

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

[0094] As shown in FIG. 6, the computer system 600 may include an external storage device 610, a bus 620, a main memory 630, a read-only memory 640, a mass storage device 650, a communication port(s) 660, and a processor 670. A person skilled in the art will appreciate that the computer system 600 may include more than oneprocessor and communication ports. The processor 670 may include various modules associated with embodiments of the present disclosure. The communication port(s) 660 may be any of an RS-232 port for use with a 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) 660 may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 600 connects.

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

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

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

[0098] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to perform a method for performing a customer data adjustment operation is described. The method includes authenticating, by an authentication unit, a user using one or more authentication techniques. The one or more authentication techniques are utilized for initiating the customer data adjustment operation. The method includes storing, by a data management unit, customer-related adjustment data associated with the user upon successful authentication. The method includes receiving, by the data management unit, a bulk adjustment command entered by the user and forwarding, by the data management unit, the bulk adjustment command to a network node for performing the customer data adjustment operation.

[0099] The present disclosure provides a technical advancement in the field of broadband customer data management and service adjustment. A bulk adjustment utility is described that enables automated, rule-based adjustments across a large subscriber base simultaneously. By enabling automated and secure bulk adjustment of customer data usage based on stored adjustment data and predefined rules, the bulk adjustment utility introduces a robust, scalable, and fault-tolerant mechanism for managing large volumes of subscriber accounts. Furthermore, the bulk adjustment utility ensures that adjustments are verified for correctness and accessibility, while discrepancies or errors trigger automated reprocessing or administrative alerts, thereby preventing incorrect data modifications. Overall, the bulk adjustment utilitysignificantly reduces manual overhead, improves operational efficiency, minimizes errors in customer data adjustments, and enhances the scalability, reliability, and automation of broadband service management compared to conventional GUI-based approaches.

[0100] 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 or examples, 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.

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

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

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

[0104] The present disclosure provides a bulk adjustment tool for customer data adjustment operations.

[0105] The present disclosure enables rapid recovery of customer data through a command-based restoration process. This allows for quick execution of the command and significantly reduces downtime.

[0106] The present disclosure offers a resource-efficient solution that requires fewer system resources than GUI-based tools. This makes it suitable for running on servers or in environments where resource consumption is a concern.

[0107] The present disclosure simplifies the customer data restoration process, allowing administrators to restore data with a single command and making the process both straightforward and user-friendly.

[0108] The present disclosure provides an optimized approach for adjusting customer data for AirFiber customers (users). The process is streamlined and intuitive and requires minimal training for IT staff.

[0109] The present disclosure enhances the overall operational efficiency of the system by using a bulk adjustment command line interface (CLI) command, which significantly reduces the time required for the data restoration process done manually.

[0110] The present disclosure ensures uniform adjustment application across all customer records. The bulk adjustment CLI command often integrates well with other systems and scripts. It can be used to pull data from an Excel sheet, apply changes, and then push updates, all within a single automated workflow, minimizing the risk of human error and providing consistent and accurate adjustments.

[0111] The present disclosure significantly reduces the time and manual effort required compared to handling each customer's data individually by using the bulk adjustment CLI command, as performing bulk adjustment for multiple customers in one operation is faster than processing the adjustment for multiple customers one at a time.

Claims

CLAIMS1. A method (500) for performing a customer data adjustment operation, the method (500) comprising: authenticating (502), by an authentication unit (208), a user using one or more authentication techniques, wherein the one or more authentication techniques are utilized for initiating the customer data adjustment operation; storing (504), by a data management unit (210), customer-related adjustment data associated with the user upon successful authentication; receiving (506), by the data management unit (210), a bulk adjustment command entered by the user; and forwarding (508), by the data management unit (210), the bulk adjustment command to a network node for performing the customer data adjustment operation.

2. The method (500) as claimed in claim 1, wherein performing the customer data adjustment operation comprises: determining, by the network node, one or more adjustment parameters based on the stored customer-related adjustment data and one or more predefined rules upon receiving the bulk adjustment command; and performing, by the network node, the customer data adjustment operation based on the determined one or more adjustment parameters.

3. The method (500) as claimed in claim 1, wherein the network node comprises one or more network elements, servers, or cloud-based computing nodes configured to receive the bulk adjustment command from the data management unit (210).

4. The method (500) as claimed in claim 1, wherein the customer-related adjustment data comprises service information associated with a plurality of customers that is stored in a secure manner to ensure data privacy and integrity.

5. The method (500) as claimed in claim 1, wherein the one or more authentication techniques comprise at least one of single-factor authentication or multi-factor authentication techniques to ensure that only authorized users are permitted to initiate the customer data adjustment operation.

6. A system (108) for performing a customer data adjustment operation, the system (108) comprising: an authentication unit (208) configured to: authenticate a user using one or more authentication techniques, wherein the one or more authentication techniques are utilized for initiating the customer data adjustment operation; a data management unit (210) configured to: store customer-related adjustment data associated with the user upon successful authentication; receive a bulk adjustment command entered by the user; and forward the bulk adjustment command to a network node for performing the customer data adjustment operation.

7. The system (108) as claimed in claim 6, wherein for performing the customer data adjustment operation, the network node is configured to: determine one or more adjustment parameters based on the stored customer-related adjustment data and one or more predefined rules upon receiving the bulk adjustment command; andperform the customer data adjustment operation based on the determined one or more adjustment parameters.

8. The system (108) as claimed in claim 6, wherein the network node comprises one or more network elements, servers, or cloud-based computing nodes configured to receive the bulk adjustment command from the data management unit (210).

9. The system (108) as claimed in claim 6, wherein the customer-related adjustment data comprises service information associated with a plurality of customers that is stored in a secure manner to ensure data privacy and integrity.

10. The system (108) as claimed in claim 6, wherein the one or more authentication techniques comprise at least one of single-factor authentication or multi-factor authentication techniques to ensure that only authorized users are permitted to initiate the customer data adjustment operation.

11. 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 for performing a customer data adjustment operation, the method comprising: authenticating, by an authentication unit (208), a user using one or more authentication techniques, wherein the one or more authentication techniques are utilized for initiating the customer data adjustment operation; storing, by a data management unit (210), customer-related adjustment data associated with the user upon successful authentication; receiving, by the data management unit (210), a bulk adjustment command entered by the user; andforwarding, by the data management unit (210), the bulk adjustment command to a network node for performing the customer data adjustment operation.

Images