System and method for managing user data in a network

Abstract

A system (108) and method (500) for managing user data to enhance user experience in a communication network (106). The capturing of set of data parameters related to the plurality of events occur on a user equipment (104). The encrypted set of data parameters is stored in a storage unit (114) of the user equipment (104). By launching an application on the user equipment (104) the encrypted data parameters are synced to a centralized server (110). Further, if the synchronization process fails then re-launch of the application on the user equipment is performed for re-synchronization of the encrypted set of data parameters to the centralized server (110). Upon processing of the encrypted set of data parameters used for analytics and reporting.

Description

SYSTEM AND METHOD FOR MANAGING USER 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 wireless cellular communication. More particularly, the present disclosure relates to a system and method for managing user data in a communication 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 ‘Application Programming Interface (API)’ used hereinafter in the specification refers to application programming interface which acts as an interface for communication between two or more applications or components in a user equipment.

[0005] The expression ‘encryption’ used hereinafter in the specification refers to process that converts original data into unreadable format to prevent unauthorized use of the data in network transmission.

[0006] The expression ‘decrypting’ used hereinafter in the specification refers to process that transforms encrypted data that is unreadable format to original format.

[0007] The expression ‘centralized repository’ used hereinafter in the specification refers to a single point of access to user data through a network. The centralized repository stores all the user data at one point providing wider data visibility, data collaboration, and consistency in data.

[0008] The expression ‘RSRP’ used hereinafter in the specification refers to reference signal received power (RSRP). It is a measure of the received power level in a cell network. It plays a vital role in assessing the quality of cellular connections and optimizing network performance.

[0009] The expression ‘RSRQ’ used hereinafter in the specification refers to reference signal received quality (RSRQ). It is a measure for the quality of the reference signal received in the user device. It plays a crucial role in accessing the level of interference and noise in the received signal.

[0010] The expression ‘RSSI’ used hereinafter in the specification refers to reference signal strength indicator (RSSI) is basic measure for signal strength. It is the measurement of the power level that is received by the user equipment. It indicates the strength and quality of the signal being received by the user equipment.

[0011] The expression ‘UL’ used hereinafter in the specification refers to uplink which is the signal that leaves the user equipment and going back to the service provider cell tower.

[0012] The expression ‘DL’ used hereinafter in the specification refers to downlink is the signal transmitted from the service provider cell tower to the user equipment.

[0013] The expression ‘TAC’ used hereinafter in the specification refers to tracking area code which plays an important role in network management and allows for efficient tracking and identification of User Equipment (UE) while moving within the network service.

[0014] The expression ‘cell ID’ used hereinafter in the specification refers to unique identifier that are assigned to each cell within the network. Cell ID enables the user equipment to identify and differentiate individual cells so as connect to a specific cell for telecommunication.

[0015] The expression ‘PCI’ used hereinafter in the specification refers to Physical cell ID that indicates the physical identity of a cell during the cell selection process. PCI is a unique identifier for individual cells within a cellular network.

[0016] The expression ‘average uplink (UL) signal rate’ used hereinafter in the specification refers to the average rate at which data is uploaded that is the speed at which the information is uploaded to network or the transmission rate of a user equipment.

[0017] The expression ‘average downlink (DL) signal rate’ used hereinafter in the specification refers to the average rate at which data is downloaded that is the speed at which data from the network is downloaded to a user equipment.BACKGROUND OF THE DISCLOSURE

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

[0019] Wireless communication involves the transmission of voice and data without cables or wires. Physical connections are replaced by electromagnetic signals to facilitate communication between users via their devices. Electromagnetic signals, such as radio waves, carry voice, data, video or signals over a communication path. These signals travel faster compared to wired services and covers long distance communications effectively at low cost.

[0020] Currently, the number of users devices utilizing wireless communication networks is continuously increasing. However, many users face issues such as low network coverage, no coverage in certain areas or low internet speeds due to the large number of users using the wireless communication networks. Further, users may experience issues with their devices, which may later be linked to the service provider. To identify network problems, data relatedto users or their locations needs to be analyzed. Analyzing the data allows for the resolution of user problems and the implementation of preventive actions.

[0021] Therefore, there is a need to provide a method and a system that can address the shortcomings of existing solutions.SUMMARY OF THE DISCLOSURE

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

[0023] The present disclosure discloses a system and method for managing user data in a communication network. The method includes capturing, by one or more processor(s), a set of data parameters related to a plurality of events occurred on a user equipment. The method further includes performing, by the one or more processor(s), encryption on the set of data parameters. The method further includes storing, by the one or more processor(s), the encrypted set of data parameters in a storage unit of the user equipment. The method further includes upon launch of an application on the user equipment (104), synchronizing, by the one or more processor(s), the encrypted set of data parameters to a centralized server. The method further includes determining, by the one or more processor(s), whether the encrypted set of data parameters was successfully synchronized to the centralized server. The method further includes in response to determining that the encrypted set of data parameters was successfully synchronized to the centralized server, processing, by the one or more processor(s), the encrypted set of data parameters for use in analytics and reporting.

[0024] In some embodiment, the method further includes in response to determining that the encrypted set of data parameters was not successfully synchronized to the centralized server, initiating, by the one or more processor(s), a re- synchronization of the encrypted set of data parameters to the centralized server during at least one of a re-launch of the application and occurrence of one or more of the plurality of events on the user equipment.

[0025] In some embodiment, the set of data parameters comprises a plurality of network parameters and a plurality of user equipment parameters.

[0026] In some embodiment, the method further includes processing the encrypted set of data parameters by decrypting, by the one or more processor(s), the encrypted set of data parameters at predefined time intervals to obtain the set of data parameters in an unstructured format. The method further includes converting, by the one or more processor(s) (202), the unstructured form of decrypted set of data parameters into a structured format. The method further includes storing the structured format of the set of data parameters in a centralized repository.

[0027] In some embodiment, the method further includes the plurality of events of the user equipment comprises screen status of the user equipment, application launch status, network coverage status, location service status, switching between Wireless Fidelity (Wi-Fi) and cellular network, reference signal received power (RSRP) threshold, application launch status and connectivity service status.

[0028] In some embodiment, the method further includes the plurality of network parameter comprising network signal strength, network type, network subtype, average signal rate, average uplink (UL) signal rate, average downlink (DL) signal rate, cell ID, Physical Cell ID (PCI), connection type, geographic coordinates, average reference signal received power (RSRP), average reference signal received quality (RSRQ), received signal strength indicator (RSSI), mobile network code (MNC), mobile country code (MCC), tracking area code (TAC) and international mobile subscriber identity (IMSI).

[0029] In some embodiment, the method includes the plurality of user equipment parameters comprises international mobile equipment identity (IMEI), media access control (MAC) address, build number, device ID, device operating system (OS), battery level, device connectivity, device manufacturer and device model number.

[0030] In some embodiment, the method further includes mapping the captured set of data parameters to a unique identification code associated with the user equipment.

[0031] In another embodiment, a system for managing user data in a communication network. The system includes a data capturing module configured to: capture a set of data parameters related to a plurality of events occurred on a user equipment. The system further includes encrypt the captured set of data parameters. The system further includes store the encrypted set of data parameters in a storage unit of the user equipment. The system further includes a data synchronization module configured to: synchronize the encrypted set of data parameters to a centralized server upon an application launch on the user equipment. The system further includes determine whether the encrypted set of data parameters was successfully synchronized to the centralized server. The system further processes the encrypted set of data parameters for use in analytics and reporting in response to determining that the encrypted set of data parameters was successfully synchronized to the centralized server.

[0032] In some embodiment, the system further includes initiate a resynchronization of the encrypted set of data parameters to the centralized server in case of synchronization failure, triggered by at least one of a re-launch of the application and occurrence of one or more of the plurality of events on the user equipment. The system further includes process the encrypted set of data parameters for analytics and reporting upon successful synchronization.

[0033] In some embodiment, the system includes comprising a data migration module configured to: convert the unstructured form of decrypted set of data parameters into a structured format. The system further includes store the structured format of the set of data parameters in a centralized repository.

[0034] In some embodiment, the system includes the plurality of events of the user equipment that comprises screen status of the user equipment, network coverage status, location service status, switching between Wireless Fidelity (WiFi) and cellular network, reference signal received power (RSRP) threshold, application launch status and connectivity service status.

[0035] In some embodiment, the system includes the plurality of network parameter comprising network signal strength, network type, network subtype, average signal rate, average uplink (UL) signal rate, average downlink (DL) signal rate, cell ID, Physical Cell ID (PCI), connection type, geographic coordinates, average reference signal received power (RSRP), average reference signal received quality (RSRQ), received signal strength indicator (RSSI), mobile network code (MNC), mobile country code (MCC), tracking area code (TAC) and international mobile subscriber identity (IMSI).

[0036] In some embodiment, the system includes the plurality of user equipment parameters comprises international mobile equipment identity (IMEI), media access control (MAC) address, build number, device ID, device operating system (OS), battery level, device connectivity, device manufacturer and device model number.

[0037] In some embodiment, the system includes mapping the captured set of data parameters to a unique identification code associated with the user equipment.

[0038] In another exemplary embodiment, a user equipment communicatively coupled to a system. The coupling includes a processor and a computer readable storage medium storing a set of instruction for execution by the processor. The set of instructions includes encrypting the captured set of data parameters. The set of instructions includes store the encrypted set of data parameters in a storage unit of the user equipment. The set of instructions further includes a data synchronization module configured to: synchronize the encrypted set of data parameters to a centralized server upon an application launch on the user equipment. The set of instructions further includes determine whether the encrypted set of data parameters was successfully synchronized to the centralized server. The set of instructions further includes processing the encrypted set of data parameters for use in analytics and reporting in case of determining that the encrypted set of data parameters was successfully synchronized to the centralized server.

[0039] In another exemplary embodiment, a computer program product includes a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium includes set of instructions when executed by one or more processors, cause the one or more processors to perform the set of instructions. The set of instructions includes encrypting the captured set of data parameters. The set of instructions includes storing the encrypted set of data parameters in a storage unit of the user equipment. The set of instructions further includes a data synchronization module configured to: synchronize the encrypted set of data parameters to a centralized server upon an application launch on the user equipment. The set of instructions further includes determining whether the encrypted set of data parameters was successfully synchronized to the centralized server. The set of instructions further includes processing the encrypted set of data parameters for use in analytics and reporting in case of determining that the encrypted set of data parameters was successfully synchronized to the centralized server.

[0040] OBJECTS OF THE DISCLOSURE

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

[0042] An object of the present disclosure is to provide a system and a method for capturing and synchronizing event-based passive user data in a communication network to enhance user experience.

[0043] Another object of the present disclosure is to provide a system and a method that capture network parameters and user equipment parameters based on a plurality of events that occurred on a user equipment.

[0044] Another object of the present disclosure is to provide a system and a method that stores the captured data per-user basis to uniquely identify users and promptly resolve real-time service issues.

[0045] Yet another object of the present disclosure is to provide a system and a method that address real-time user equipment network issues.

[0046] Yet another object of the present disclosure is to provide a system and a method that analyze and report captured network parameters to network service providers to enhance user experience.

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

[0048] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0049] FIG. 1 illustrates a network architecture for managing user data in a communication network, in accordance with an embodiment of the present disclosure.

[0050] FIG. 2 illustrates an example of a system for managing user data in a communication network, in accordance with an embodiment of the present disclosure.

[0051] FIG. 3 illustrates an example of a user equipment for managing user data in a communication network, in accordance with an embodiment of the present disclosure.

[0052] FIG. 4 illustrates an example flow diagram for managing user data flow after data gets synced to a centralized server, in accordance with an embodiment of the present disclosure.

[0053] FIG. 5 illustrates a flowchart of the method for managing user data in a communication network, in accordance with an embodiment of the present disclosure.

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

[0055] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100- Network architecture102-1, 102-2... 102-N- Users104-1, 104-2... 104-N- User equipments106- Network108- System110- Centralized server112- Centralized repository114-1, 114-2... 114-N- Storage unit202- Processor(s)204- Memory206- Interface208- Processing engine(s)212- Data capturing module214- Data synchronization module216- Data migration module218- Other unit(s)210- Database302- User equipment610- External storage device620- Bus630- Main memory640- Read-only memory650- Mass storage device660- Communication port(s)670- ProcessorDETAILED DESCRIPTION OF THE DISCLOSURE

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

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

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

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

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

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

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

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

[0064] Currently, the number of users devices utilizing wireless communication networks is continuously increasing. However, many users face issues such as low network coverage, no coverage in certain areas or low internetspeeds due to the large number of users using the wireless communication networks. Further, users may experience issues with their devices, which may later be linked to the service provider. To identify network problems, data related to users, or their locations needs to be analyzed. Analyzing the data allows for the resolution of user problems and the implementation of preventive actions.

[0065] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a system and a method for capturing and synchronizing event-based passive user data in a communication network. The captured data is stored on a per-user basis to uniquely identify the user and resolve any real-time problems they encounter. Further, it involves analyzing and monitoring area-specific network parameter data across different networks. Furthermore, data is captured at regular intervals in the user’s local database and subsequently synced (using a sync API) to a backend on the launch of an application.

[0066] The various embodiments throughout the disclosure will be explained in more detail with reference to FIGs. 1-6.

[0067] FIG. 1 illustrates a network architecture 100 for managing user data in a communication network, in accordance with an embodiment of the present disclosure. In an aspect, the capturing and synchronizing of event-based passive user data may be performed by a mobile application.

[0068] In an aspect, the managing user data involves collecting, synching, and analyzing network parameters and user equipment parameters of a user equipment (UE). The user data are managed in a central repository or a database to ensure data integrity, security, privacy, and scalability. The UE interacts with the central repository or the database to process, store, and organize user data based on a predefined time interval. The predefined time interval may be a second, a minute, an hour, or a day. For example, the UE may sync with the central repository or database every 2 minutes. The user data may include passive data and active data. The passive data is data that are gathered from the UE in the background, even while the user is working with the UE. The active data is datagiven by the user to the UE as an input. In examples, the user data be be eventbased passive user data.

[0069] In an aspect, the event-based passive user is the data collected from the UE in response to specific events or actions that occur on the UE (device). The specific events may include a UE Screen ON / Off, an application launch, a Global Positioning System (GPS) On / Off, an airplane mode, a network coverage, and a network switching (Wireless fidelity to Long-Term Evolution (LTE) or 5G or 6G).

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

[0071] In an embodiment, the user equipment 104 may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device(e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the user equipment 104 may include, but is not limited to, any electrical, electronic, electro -mechanical, or an equipment, or a combination ofone 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 user equipment 104 may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user 102 or the entity such as touch pad, touch enabled screen, electronic pen, and the like.

[0072] In an embodiment, each of the user equipment 104-1, 104-2... 104-N has a storage unit 114-1, 114-2 ... 114-N for storing a set of data parameters related to a plurality of events. The set of data parameters includes a plurality of network parameters and a plurality of user equipment parameters. The storage unit 114 may store the data captured during user interaction with the plurality of events. For example, the storage unit 114 may be embedded or coupled with the UE 104. The storage unit 114 stores user data, system files, applications and any other information for the functioning of the device. The storage unit 114 may include a flash memory, an external storage (SD card), a network attached storage (NAS), and a Solid-State Drive (SSD). A person of ordinary skill in the art will appreciate that the user equipment 104 may not be restricted to the mentioned devices and various other devices may be used.

[0073] In an aspect, the plurality of events includes screen status of the user equipment (104), application launch status, network coverage status, location service status, switching between Wireless Fidelity (Wi-Fi) and cellular network, reference signal received power (RSRP) threshold, application launch status and connectivity service status.

[0074] In an aspect, the plurality of network parameters includes network signal strength, network type, network subtype, average signal rate, average uplink (UE) signal rate, average downlink (DE) signal rate, cell ID, Physical Cell ID (PCI), connection type, geographic coordinates, average reference signal received power (RSRP), average reference signal received quality (RSRQ), received signal strength indicator (RSSI), mobile network code (MNC), mobilecountry code (MCC), tracking area code (TAC) and international mobile subscriber identity (IMSI). The geographic coordinates include a latitude position and a longitude position of the user equipment 104. In an exemplary aspect, the geographic coordinates are represented as decimal numbers. For example, the latitude coordinates are represented as 19.242326533556284 for a location.

[0075] The network signal strength is a measure of the power received by the user equipment 104. In an exemplary aspect, the network signal strength is calculated using decibel milliwatts(dBm). The signal strength is represented between 0 to -100 dBm. When the value is closer to 0, the user equipment 104 may have desired signal strength and reliable connection.

[0076] In an exemplary aspect, the network type and the network subtype may include, but is not limited to, Personal Area Network (PAN), Local Area Network (LAN), Wireless Local Area Network (WLAN) and Metropolitan Area Network (MAN). For example, the user equipment 104 may be connected to a wireless- fidelity (Wi-Fi). Further, the network subtype may be secondary connectivity to the user equipment 104.

[0077] In an exemplary aspect, the connection type may include, but is not limited to, mobile network, Wi-fi, USB tethering and hotspot. The connection type may be a mobile network connection such as 2G, 3G, 4G LTE, 5G and 6G or like cellular network generation.

[0078] The average uplink (UL) signal rate is the average rate at which data is uploaded, i.e., the speed at which the information is uploaded to network or the transmission rate of a user equipment 104.

[0079] The average downlink (DL) signal rate is the average rate at which data is downloaded, i.e., the speed at which data from the network is downloaded to a user equipment 104.

[0080] The reference signal received power (RSRP) is a measure of the received power level in a cell network. RSRP is used for assessing the quality of cellular connections and optimizing network performance.

[0081] The reference signal received quality (RSRQ) is a measure for the quality of the reference signal received in the user device (user equipment 104).RSRQ is used for accessing the level of interference and noise in the received signal.

[0082] The reference signal strength indicator (RSSI) is basic measure for signal strength. RSSI is the measurement of the power level that is received by the user equipment. RSSI value indicates the strength and quality of the signal being received by the user equipment 104.

[0083] The Tracking Area code (TAC) allows for efficient tracking and identification of User Equipment (UE) while moving within the network service.

[0084] In an aspect, the plurality of user equipment parameters includes international mobile equipment identity (IMEI), media access control (MAC) address, build number, device ID, device operating system (OS), battery level, device connectivity, device manufacturer and device model number. These parameters are unique to each of the user equipment.

[0085] In an embodiment, each of the user equipment 104 may have a unique identifier attribute associated therewith. In an embodiment, the unique identifier attribute may include international mobile equipment identity (IMEI), device ID, Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, International Mobile Subscriber Identity (IMS I), Subscriber Permanent Identifier (SUPI) and the like.

[0086] In an aspect, the plurality of events includes screen status of the user equipment, application launch status, network coverage status, location service status, switching between Wireless Fidelity (Wi-Fi) and cellular network, reference signal received power (RSRP) threshold, application launch status and connectivity service status.

[0087] The network architecture 100 may include a centralized server 110, a centralized repository 112 and a network 106. In an aspect, the centralized server 110 stores the set of data parameters in an encrypted format. The encrypted format may be understood as an unstructured form of originally captured set of data parameters. The centralized repository 112 may be a single storage medium to store the decrypted structured form of the set of data parameters. In an aspect, the centralized repository 112 is a storage medium or service that enables storingdata, files or resources in a central location. The centralized repository 112 may be accessible by the users 102, an application, or the system 108 and serves as a primary source for accessing, managing, and distributing the data. The centralized repository provides a consistent and authoritative source of information or resources. For example, all the user data and activities, such as access control, updates, and backups, are managed from a single point, which facilitates easier monitoring and maintenance of the data in the repository.

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

[0089] FIG. 2 illustrates an example of a system for managing event-based passive user data in a communication network, in accordance with an embodiment of the present disclosure.

[0090] FIG. 2 with reference to FIG. 1, illustrates an exemplary representation of the system 108 for managing user data in a communication network, in accordance with an embodiment of the present disclosure. The system 108 includes one or more processor(s) 202, a memory 204, a processing engine 208, a database 218, and an interface(s) 206. In an exemplary embodiment, the processing engine 208 may include one or more modules selected from any of a data capturing module 212, a data synchronization module 214, a data migration module 216, and other unit(s) 218 having functions that may include, but are not limited to, testing, storage, and peripheral functions, such as wireless communication unit for remote operation, audio unit for alerts and the like.

[0091] In an embodiment, the data capturing module 212 may be configured to capture a set of data parameters related to a plurality of events of the user equipment 104 via an application programming interface (API). The set of data parameters includes a plurality of network parameters and a plurality of user equipment parameters. The data capturing module 212 may collect the data from the user equipment 104 by scanning, identifying, recognizing, recording, storing data from the plurality of events. The captured set of data parameters are stored in the storage unit 114 of the user equipment 104 in an encrypted form. The data capturing module 212 encrypts the captured set of data parameters. In an aspect, the encryption is a process that converts original data into unreadable format to prevent unauthorized use of the data in network transmission.

[0092] In an embodiment, the data synchronization module 214 may be configured to synchronize the encrypted set of data parameters to a centralized server 110 upon an application launch on the user equipment 104. The data synchronization module 214 may determine whether the encrypted set of data parameters was successfully synchronized to the centralized server 110. In an aspect, the data synchronization module 214 may initiate a re-synchronization of the encrypted set of data parameters to the centralized server 110 in case of synchronization failure, triggered by at least one of a re-launch of the application and occurrence of one or more of the plurality of events on the user equipment 104. The data synchronization module 214 may process the encrypted set of data parameters for analytics and reporting purposes upon successful synchronization. In an aspect, the data synchronization module 214 may be configured to decrypt the encrypted set of data parameters at predefined time intervals to obtain the set of data parameters in an unstructured format.

[0093] According to an implementation, the data synchronization module 214 may be configured to synchronize the encrypted set of data parameters to the centralized server 110 when an application is launched via the application programming interface (API) in the user equipment 104. The data synchronization module 214 may receive the encrypted set of data parameters from the storage unit 114 of the user equipment 104. When the user launches the application viathe API, the set of data parameters may be received by the data synchronization module 214. The data synchronization module 214 receives the set of data parameters each time the user launches the application on the user equipment 104 via API. In an aspect, the synchronization is a process of consolidating data from each of the user equipment 104-1, 104-2... 104-N and storing it in the centralized server 110 to maintain data consistency.

[0094] In an aspect, prior to performing synchronization of the encrypted set of data parameters to the centralized server 110, the data synchronization module 214 is configured to map the captured set of data parameters to a unique identification code associated with the user equipment 104. In an exemplary aspect, the data synchronization module 214 may receive the encrypted set of data parameters from each of the user equipment 104. The data synchronization module 214 may generate a unique code for each of the encrypted set of data parameters to identify the user data corresponding to the user equipment 104. The unique code generated may be a numerical, alpha-numerical, special character and like expression. The data synchronization module 214 maps the data with a unique identification code for enabling user identification.

[0095] In an aspect, the application launched via API may be integrated with a software development kit (SDK). The application syncs the set of data parameters with the centralized server 110 at a specific time interval or at regular time intervals. The specific time interval may be determined by the user 102. In an exemplary aspect, the specific time interval may be the day next to the day when the events are stored in the user equipment 104. For example, the day on which events are captured on the user equipment 104 may be today (T Day). The synchronization of data parameters to the centralized server 110 may be performed the next day (T+l day).

[0096] In an aspect, the centralized server 110 may perform decryption process on the stored encrypted set of data parameters. The decryption process involves transformation of the encrypted set of data parameters that are in unreadable format to original format of the set of data parameters. The decryption process enables the reading of the set of data parameters. The decryption processprovides an unstructured form of set of data parameters. The unstructured form may be an unorganized data format such as raw text, multimedia content, like emails, videos, photos, audio files, and webpages.

[0097] In an embodiment, the data migration module 216 may perform the decryption process on the stored encrypted set of data parameters. In an implementation, the data migration module 216 may be configured to convert the unstructured form of the decrypted set of data parameters into a structured format and store the structured format of the set of data parameters in a centralized repository 112.

[0098] In an embodiment, the data migration module 216 may be configured to convert an unstructured format of decrypted set of data parameters into a structured format and store in a central repository 112. The unstructured format (or form) of the decrypted set of data parameters are stored in a distributed event streaming platform. In an exemplary aspect, the distributed event streaming platform may be any open-source event streaming platform.

[0099] The unstructured form of decrypted set of data parameters are converted into structured form in the central repository 112. The structured form may be a standardized format of information such as a table format with rows and columns categorized based on data type. The data type may include character, numbers, decimal, fraction, alpha-numeric, etc.

[0100] In an aspect, the structured form of set of data parameters are stored in row and column wise manner mapped with unique identification code generated for each of the user 102 for their user equipment 104. The structured form may be a tabular format with rows and columns. The set of data parameters can be categorized into columns and rows based captured on the plurality of events of the user equipment 104.

[0101] FIG. 3 illustrates an example of a user equipment 300 for managing user data in a communication network, in accordance with an embodiment of the present disclosure.

[0102] Referring to FIG. 3, the user equipment 302 (for example, user equipment 104) may capture passive user data related to a plurality of events(304-318). The plurality of events (304-318) which may take place in the user equipment 302. The plurality of events (304-318) may be captured by using a software development kit (SDK) integrated into a plurality of applications.

[0103] The plurality of events (304-318) comprises device screen on / off, application launch, a global positioning system (GPS) on / off, airplane mode of the device, a reference signal received power (RSRP) threshold, no coverage, switching from long-term evolution (LTE) / new radio (NR) to Wi-Fi and Wi-Fi to LTE / NR switch.

[0104] The events (304-318) are captured at regular intervals. The captured data is stored in the user equipment 302. The captured data is then synced to a centralized server 110 upon the launch of an application. The captured data is stored user-wise in the centralized server 110. The stored data in the centralized repository 112 is used for solving real-time user problems (e.g., low network, low internet speed, etc.). The captured data is used for reporting and analysis purposes.

[0105] In an embodiment, capturing subscriber identity module (SIM) data based on the events by making use of different API’s. The SIM data may comprise data and voice. The APIs may capture user parameters and network parameters. In order to capture the plurality of user parameters and plurality of network parameters, continuously sensing events and getting triggers for the events on the device. In this way, the plurality of events is continuously identified. The captured set of data parameters and events are used to resolve end user’s problems corresponding to networks and devices. Further, identifying network problems such as low coverage and low RSRP threshold events on continuous usage of users by keeping service ON all the time.

[0106] In an aspect, the API refers to mechanisms that form a software interface to link an application program to the services and functions of another application, operating system, network operating system, driver, or software program. The API is basically a tool that allows different applications to communicate with each other.

[0107] FIG. 4 illustrates an example flow diagram 400 for managing user data flow after data gets synced to the centralized server 110, in accordance with an embodiment of the present disclosure.

[0108] A software development kit (SDK) may be integrated with a plurality of applications of the device to capture the plurality of events 304-318 (as shown in FIG. 3)

[0109] At step 412, the method 400 includes capturing the set of data parameters related to the plurality of events 304-318 on T-Day (402) by the user equipment 302. The captured event-based data is stored in an application of the user equipment 104. The plurality of events 304-318 comprises screen on / off, app launch, airplane mode, and no coverage. On the basis of the events, row -wise data is captured in the user equipment 302 and stored in the storage unit 114 of the user equipment 302. Further, along with event-based data, a plurality of signal and network and device configuration details are captured. The data corresponding to a specific user is stored by generating user’s device identifier (ID). In this way, device ID generation may help in tagging users uniquely. The device ID is used to identify the data corresponding to the specific user.

[0110] At step 414, the method 400 includes syncing of the set of data parameters on T+l-Day (at step 404), when a user launches the application on the user equipment 302, the stored data may get synced to the centralized server 110. Data in the centralized server 110 may get synced in the encrypted format. Also, the application on the user equipment checks whether the stored data is synced to the centralized server 110 or not.

[0111] In an aspect, the application launched via API may be integrated with a software development kit (SDK). The application syncs the set of data parameters with the centralized server 110 at a specific interval time or regular time intervals. The specific time interval may be determined by the user 102. In an exemplary aspect, the specific time interval may the day next to storing of events in the user equipment 302. For example, the day on which events are captured on the user equipment 302 may be today (T Day). The synchronization of data parameters with the centralized server 110 may be next day (T+l day).

[0112] At step 416, the method 400 includes detecting whether the stored data in the storage unit 114 of the user equipment 104 is not synced (or failed) to the centralized server 110, then the application again tries to sync data on the next launch or event.

[0113] In an aspect, the application launched via API enables to sync the set of data parameters to the centralized server 110. When the user launches the application the set of data parameters performs the syncing process. If the syncing process fails, then the application tries to sync the set of data parameters on next launch of the application or retries to sync again.

[0114] At step 418, the method 400 includes a batch processing process to sync the data to the centralized server 110. Once the data is synced to the centralized server 110, the data in the centralized server 110 is processed in a batch process. The batch process may take place at regular intervals (e.g., after every 2 mins interval). In an aspect, the batch process is data processing in batches (or groups) at regular intervals. The centralized server 110 then performs a decryption process to decrypt the data.

[0115] In an aspect, the decryption process involves transformation of the encrypted set of data parameters that is unreadable format to original format of the set of data parameters. The decryption process provides an unstructured form of set of data parameters.

[0116] At step 420, the method 400 includes storing the processed data in a distributed event streaming platform. The data is stored in the distributed event streaming platform in an unstructured format. In an aspect, the unstructured form may be an unorganized data format such as raw text, multimedia content, like emails, videos, photos, audio files, and webpages.

[0117] At step 422, the method 400 includes the data from the distributed event streaming platform is stored in a database (e.g., HBase) in a structured manner (e.g., column-wise). The data may store user wise and area wise in the centralized repository 112. In an aspect, the structured form of set of data parameters are stored in row and column wise manner mapped with unique identification code generated for each of the user 102 for their user equipment302. The structured form may be a tabular format with rows and columns. The set of data parameters can be categorized into columns and rows based captured on the plurality of events of the user equipment 302.

[0118] At step 424, the method 400 includes the stored data in the centralized repository 112 is used for reporting the network performance data to the network service provider. In an aspect, the network performance data enables the network service provider to enhance the user experience.

[0119] At step 426, the method 400 includes the stored data in the centralized repository 112 is used for analytics. The user-wise stored data is used to identify the users uniquely to help in resolving the user’s problems in real-time during the service. The area-wise stored data may be analyzed and monitored to find out issues related to different network parameters over different networks. This helps in taking a proactive approach and troubleshooting end users’ issues in real-time. The network issues may comprise low network, low internet speed, low coverage, low RSRP threshold, etc.

[0120] FIG. 5 illustrates a flowchart of the method (500) for managing user data in a communication network, in accordance with an embodiment of the present disclosure.

[0121] At step 502, the method 500 includes capturing, by the one or more processor(s) 202, a set of data parameters related to the plurality of events of a user equipment 104 via an application programming interface (API). The set of data parameters comprises a plurality of network parameters and a plurality of user device parameter.

[0122] In an aspect, the plurality of network parameters includes network signal strength, network type, network subtype, average signal rate, average uplink (UL) signal rate, average downlink (DL) signal rate, cell ID, Physical Cell ID (PCI), connection type, geographic coordinates, average reference signal received power (RSRP), average reference signal received quality (RSRQ), received signal strength indicator (RSSI), mobile network code (MNC), mobile country code (MCC), tracking area code (TAC) and international mobile subscriber identity (IMSI). The geographic coordinates include a latitude positionand a longitude position of the user equipment 104. In an exemplary aspect, the geographic coordinates are represented as decimal numbers. For example, the latitude coordinates are represented as 19.242326533556284 for a location.

[0123] The network signal strength is a measure of the power received by the user equipment 104. In an exemplary aspect, the network signal strength is calculated using decibel milliwatts(dBm). The signal strength is represented between 0 to -100 dBm. When the value is closer to 0, the user equipment 104 may have desired signal strength and reliable connection.

[0124] In an exemplary aspect, the network type and the network subtype may include, but is not limited to, Personal Area Network (PAN), Local Area Network (LAN), Wireless Local Area Network (WLAN) and Metropolitan Area Network (MAN). For example, the user equipment 104 may be connected to a wireless- fidelity (Wi-Fi). Further, the network subtype may be secondary connectivity to the user equipment 104.

[0125] In an exemplary aspect, the connection type may include, but is not limited to, mobile network, Wi-fi, USB tethering and hotspot. The connection type may be a mobile network connection such as 2G, 3G, 4G LTE, 5G and 6G or like cellular network generation.

[0126] The average uplink (UL) signal rate is the average rate at which data is uploaded, i.e., the speed at which the information is uploaded to network or the transmission rate of a user equipment 104.

[0127] The average downlink (DL) signal rate is the average rate at which data is downloaded, i.e., the speed at which data from the network is downloaded to a user equipment 104.

[0128] The reference signal received power (RSRP) is a measure of the received power level in a cell network. RSRP is used for assessing the quality of cellular connections and optimizing network performance.

[0129] The reference signal received quality (RSRQ) is a measure for the quality of the reference signal received in the user device (user equipment 104). RSRQ is used for accessing the level of interference and noise in the received signal.

[0130] The reference signal strength indicator (RSSI) is basic measure for signal strength. RSSI is the measurement of the power level that is received by the user equipment. RSSI value indicates the strength and quality of the signal being received by the user equipment 104.

[0131] In an aspect, the plurality of events includes screen status of the user equipment (104), application launch status, network coverage status, location service status, switching between Wireless Fidelity (Wi-Fi) and cellular network, reference signal received power (RSRP) threshold, application launch status and connectivity service status.

[0132] In an aspect, the plurality of user equipment parameters includes, but not limited to, international mobile equipment identity (IMEI), media access control (MAC) address, build number, device ID, device operating system (OS), battery level, device connectivity, device manufacturer and device model number. These parameters are unique to each of the user equipment.

[0133] In an embodiment, each of the user equipment 104 may have a unique identifier attribute associated therewith. In an embodiment, the unique identifier attribute may include international mobile equipment identity (IMEI), device ID, Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, International Mobile Subscriber Identity (IMS I), Subscriber Permanent Identifier (SUPI) and the like.

[0134] In an aspect, the plurality of events includes screen status of the user equipment (UE), application launch status, network coverage status, location service status, switching between Wireless Fidelity (Wi-Fi) and cellular network, reference signal received power (RSRP) threshold, application launch status and connectivity service status. For example, the screen status of the UE may include an ON state and an OFF state.

[0135] In an aspect, the RSRP threshold may be a typical range for determining quality of received signal. For example, the typical range for desired quality of received signal may be -44dbm.

[0136] At step 504, the method 500 includes performing, by the one or more processor(s) 202, encryption on the set of data parameters related to the pluralityof events. In an aspect, the encryption is a process that converts original data into unreadable format to prevent unauthorized use of the data in network transmission. In an aspect, the one or more processor(s) 202 performs encryption on the set of data parameters by converting the original form of data parameters into unintelligence form for preventing unauthorized use of the data parameters. For example, the data parameter may be a network coverage status. If the network coverage status is active status. The original form is “active”. The one or more processor(s) 202 may encrypt the unintelligence form such that “dfwlyh” using encryption.

[0137] At step 506, the method 500 includes storing, by the one or more processor(s) 202, the encrypted set of data parameters in a storage unit 114 of the user equipment 104. In an aspect, the encrypted data parameters are initially stored in the storage unit 114 of the user equipment 104 for a certain time. For example, the certain time may for a day (T- day).

[0138] At step 508, the method 500 includes synchronizing, by the one or more processor(s) 202, the encrypted set of data parameters to a centralized server 110 by launching of an application on the user equipment 104. In an aspect, the synchronization of the encrypted set of data parameters to a centralized server 110 is performed by launching an application via the application programming interface (API) in the user equipment 104. The process of synchronizing involves transferring the encrypted set of data parameters to the centralized server 110.

[0139] Upon launch of an application on the user equipment 104 by the one or more processor(s) 202, the encrypted set of data parameters may be synchronized to the centralized server 110. In an exemplary aspect, when the user 102 using the UE 104 launches the application for synching the encrypted set of data parameters with the centralized server 110. The encrypted set of data parameters is stored in the storage unit 114 of the UE 104 for a T-day. For example, the T-day may be 24thNov, 2024. If the application is launched in the UE on 24thNov, 2024, the encrypted set of data parameters may be synched with the centralized server 110. For example, the process of synchronization involvesensuring that the data stored in the centralized server 110 is kept consistent with the data locally stored in the storage unit 114

[0140] At step 510, the method 500 includes determining, by the one or more processor(s) 202, whether the encrypted set of data parameters was successfully synchronized to the centralized server 110. The processor 202 determines whether the encrypted set of data parameters are successfully transferred to the centralized server 110 by checking the last updated timestamp in the application. In an exemplary aspect, the updated timestamp is checked in the application for maintaining data consistency.

[0141] In an aspect, the one or more processor(s) 202 may check the updated timestamp to ensure that the encrypted set of data parameters was successfully synchronized to the centralized server 110. For example, when the UE 104 syncs the encrypted set of data parameters with the centralized server 110, the UE stores the time of updation such as a timestamp in the centralized server 110. For example, the timestamp may include a date and a time. If the data is synched at 10.05 AM on Nov 24, 2024. The timestamp may be stored as 2024-11-24 10:05 AM.

[0142] At step 512, the method 500 includes in response to determining that the encrypted set of data parameters was successfully synchronized to the centralized server (110), processing, by the one or more processor(s) (202), the encrypted set of data parameters for use in analytics and reporting.

[0143] In an aspect, if the said synchronization is successful, the set of data parameters are decrypted in batch process at the centralized server 110 for storing the decrypted in the centralized repository 112.

[0144] In an embodiment, the method 500 includes in response to determining that the encrypted set of data parameters was not successfully synchronized to the centralized server 110, initiating, by the one or more processor(s) 202, a re-synchronization of the encrypted set of data parameters to the centralized server 110. The application may be re-launched for resynchronization or may be synched during occurrence of the plurality of events on the user equipment 104.

[0145] In an aspect, if the synchronization fails the application programming interface (API) triggers retry or try in next user’s sync attempt. For example, the data parameters are stored in the storage unit 114 for a day (T- day). The data parameters may be synced to the centralized server on next day or forthcoming day (T+l) or when the application is launched by the user.

[0146] In an exemplary aspect, the centralized repository 112 may be accessed by the service provider to resolve the network issue faced by the user equipment 104 based on the set of data parameters of the corresponding user 104.

[0147] In an aspect, the method 500 includes decrypting, by the one or more processor(s) (202), the encrypted set of data parameters at predefined time intervals to obtain the set of data parameters in an unstructured format. The predefined time intervals are determined by user. For example, the predefined time intervals may be every 2 minutes. In an aspect, the decryption process may take place at regular intervals (e.g., after every 2 mins interval) in batch process. The data processing in batches (or groups) at regular intervals. The centralized server 110 then performs a decryption process to decrypt the data. The decryption process involves converting the encrypted data into its original or readable form. For example, if the encrypted data is “knoor” and the encryption key is 3. The decrypted data may be “hello”.

[0148] In an aspect, the method 500 includes converting, by the one or more processor(s) (202), the unstructured form of decrypted set of data parameters into a structured format, wherein the structured form of set of data parameters store in a centralized repository 112. In an aspect, the structured form of set of data parameters are stored in row and column wise manner mapped with unique identification code generated for each of the user 102 for their user equipment 104. The structured form may be a tabular format with rows and columns. The set of data parameters can be categorized into columns and rows based captured on the plurality of events of the user equipment 104.

[0149] In an aspect, the method 500 includes analyzing and reporting based on computed network performance data to a service provider for enhanced user experience. In an aspect, the consolidated stored in the centralized repository 112is used for analyzing and reporting the network performance to the service provider. In an aspect, the reported information is used by the service provider to solve issues such as low coverage, low internet speed and other network related troubleshoots.

[0150] In an embodiment, the one or more processor(s) 202 may map the captured set of data parameters to a unique identification code associated with the UE 104. The mapped data may be stored in the centralized repository 112. The captured set of data parameters such as the plurality of network parameters and the user equipment parameters may be mapped along with the unique identification code associated with the UE 104. For example, the unique identification code may be a serial number. When the UE 104 connects with the system 108 through the network 106, the one or more processor(s) 202 may generate a serial number uniquely for the UE 104. For example, the UE (104-1) may be assigned with the serial number 12A1. These serial numbers and the captured set of data parameters are mapped and stored in the centralized repository 112.

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

[0152] 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), communication port(s) (660), and a processor (670). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (670) may include various modules associated with embodiments of the present disclosure. The communication port(s) (660) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (660) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.

[0153] 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) chips 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 device (650) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.

[0154] The bus (620) communicatively couples the processor (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.

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

[0156] The present disclosure provides technical advancement related to capturing the plurality of event-based passive user data in a communication network. This advancement addresses the limitations of existing solutions by the captured event data is stored in the storage unit of the user equipment. The eventsare captured at regular intervals and synced with the centralized repository. The disclosure involves collecting and analysing the network parameters and user specific parameters which offer significant improvements in network performance and enhanced user experience. By implementing capturing a plurality of event based passive user data, the disclosed invention provides real-time solutions for network issues, resulting in enhanced user experience in the communication network.

[0157] 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.ADVANTAGES OF THE PRESENT DISCLOSURE

[0158] The present disclosure provides a system and method for capturing a plurality of event based passive user data to enhance user experience in a communication network.

[0159] The present disclosure provides a system and method for real-time solution for troubleshooting network issues faced by users.

[0160] The present disclosure provides a system and a method that enable the network service provider to determine coverage strength at different user locations.

[0161] The present disclosure provides a system and a method for collecting user data and network data in a proactive approach.

Claims

We claim:

1. A method (500) for managing user data in a communication network, the method (500) comprising: capturing, by one or more processor(s) (202), a set of data parameters related to a plurality of events occurred on a user equipment (104); performing, by the one or more processor(s) (202), encryption on the set of data parameters; storing, by the one or more processor(s) (202), the encrypted set of data parameters in a storage unit (114) of the user equipment (104); upon launch of an application on the user equipment (104), synchronizing, by the one or more processor(s) (202), the encrypted set of data parameters to a centralized server (110); determining, by the one or more processor(s) (202), whether the encrypted set of data parameters was successfully synchronized to the centralized server (110); and in response to determining that the encrypted set of data parameters was successfully synchronized to the centralized server (110), processing, by the one or more processor(s) (202), the encrypted set of data parameters for use in analytics and reporting.

2. The method (500) as claimed in claim 1, wherein the set of data parameters comprises a plurality of network parameters and a plurality of user equipment parameters.

3. The method (500) as claimed in claim 1 further comprising in response to determining that the encrypted set of data parameters was not successfully synchronized to the centralized server (110), initiating, by the one or more processor(s) (202), a re-synchronization of the encrypted set of data parameters to the centralized server (110) during at least one of a re-launchof the application and occurrence of one or more of the plurality of events on the user equipment (104).

4. The method (500) as claimed in claim 1, wherein processing the encrypted set of data parameters further comprising: decrypting, by the one or more processor(s) (202), the encrypted set of data parameters at predefined time intervals to obtain the set of data parameters in an unstructured format; converting, by the one or more processor(s) (202), the unstructured form of decrypted set of data parameters into a structured format; and storing the structured format of the set of data parameters in a centralized repository (112).

5. The method (500) as claimed in claim 1, wherein the plurality of events occurred on the user equipment (104) comprises screen status of the user equipment (104), application launch status, network coverage status, location service status, switching between Wireless Fidelity (Wi-Fi) and cellular network, reference signal received power (RSRP) threshold, application launch status and connectivity service status.

6. The method (500) as claimed in claim 1, wherein the plurality of network parameter comprises network signal strength, network type, network subtype, average signal rate, average uplink (UL) signal rate, average downlink (DL) signal rate, cell ID, Physical Cell ID (PCI), connection type, geographic coordinates, average reference signal received power (RSRP), average reference signal received quality (RSRQ), received signal strength indicator (RSSI), mobile network code (MNC), mobile country code (MCC), tracking area code (TAC), and international mobile subscriber identity (IMSI).

7. The method (500) as claimed in claim 1, wherein the plurality of user equipment parameters comprises international mobile equipment identity (IMEI), media access control (MAC) address, build number, device ID, device operating system (OS), battery level, device connectivity, device manufacturer and device model number.

8. The method (500) as claimed in claim 1 further comprising mapping the captured set of data parameters to a unique identification code associated with the user equipment (104).

9. A system (108) for capturing and synchronizing event-based passive user data in a communication network, the system (108) comprising: a data capturing module (212) configured to: capture a set of data parameters related to a plurality of events occurred on a user equipment (104); encrypt the captured set of data parameters; and store the encrypted set of data parameters in a storage unit (114) of the user equipment (104); a data synchronization module (214) configured to: synchronize the encrypted set of data parameters to a centralized server (110) upon an application launch on the user equipment (104); determine whether the encrypted set of data parameters was successfully synchronized to the centralized server (110); processing, by the one or more processor(s) (202), the encrypted set of data parameters for use in analytics and reporting in response to determining that the encrypted set of data parameters was successfully synchronized to the centralized server (110).

10. The system (108) as claimed in claim 7, wherein the set of data parameters comprises a plurality of network parameters and a plurality of user equipment parameters.

11. The system (108) as claimed in claim 7, further the data synchronization module is configured to: in response to determining that the encrypted set of data parameters was not successfully synchronized to the centralized server (110), initiate, a re- synchronization of the encrypted set of data parameters to the centralized server (110) during at least one of a re-launch of the application and occurrence of one or more of the plurality of events on the user equipment (104).

12. The system (108) as claimed in claim 7, wherein the data synchronization module (214) is further configured to decrypt the encrypted set of data parameters at predefined time intervals to obtain the set of data parameters in an unstructured format.

13. The system (108) as claimed in claim 7 further comprising a data migration module (216) configured to: convert the unstructured form of decrypted set of data parameters into a structured format; and store the structured format of the set of data parameters in a centralized repository (112).

14. The system (108) as claimed in claim 7, wherein the plurality of events occurred on the user equipment (104) comprises screen status of the user equipment (104), application launch status, network coverage status, location service status, switching between Wireless Fidelity (Wi-Fi) and cellular network, reference signal received power (RSRP) threshold, application launch status and connectivity service status.

15. The system (108) as claimed in claim 7, wherein the set of parameters include a plurality of network parameters, and wherein the plurality of network parameters include comprises network signal strength, network type, network subtype, average signal rate, average uplink (UL) signal rate, average downlink (DL) signal rate, cell ID, Physical Cell ID (PCI), connection type, geographic coordinates, average reference signal received power (RSRP), average reference signal received quality (RSRQ), received signal strength indicator (RSSI), mobile network code (MNC), mobile country code (MCC), tracking area code (TAC), and international mobile subscriber identity (IMSI).

16. The system (108) as claimed in claim 7, wherein the set of parameters include a plurality of user equipment parameters, and wherein the plurality of user equipment parameters comprises international mobile equipment identity (IMEI), media access control (MAC) address, build number, device ID, device operating system (OS), battery level, device connectivity, device manufacturer and device model number.

17. The system (108) as claimed in claim 7, wherein the data synchronization module (214) is configured to map the captured set of data parameters to a unique identification code associated with the user equipment (104).

18. A user equipment (104) communicatively coupled to a system (108), the user equipment (104) comprising: a processor (202); and a computer readable storage medium storing a set of instruction for execution by the processor (202), the set of instructions comprises: capturing a set of data parameters related to a plurality of events occurred on a user equipment (104); encrypting the captured set of data parameters; andstoring the encrypted set of data parameters in a storage unit (114) of the user equipment (104); synchronizing the encrypted set of data parameters to a centralized server (110) upon an application launch on the user equipment (104); determining whether the encrypted set of data parameters was successfully synchronized to the centralized server (110); and processing the encrypted set of data parameters for use in analytics and reporting in case of determining that the encrypted set of data parameters was successfully synchronized to the centralized server (110).

19. A computer program product comprising a non -transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of: capturing a set of data parameters related to a plurality of events occurred on a user equipment (104); encrypting the captured set of data parameters; and storing the encrypted set of data parameters in a storage unit (114) of the user equipment (104); synchronizing the encrypted set of data parameters to a centralized server (110) upon an application launch on the user equipment (104); determining whether the encrypted set of data parameters was successfully synchronized to the centralized server (110); and processing the encrypted set of data parameters for use in analytics and reporting in case of determining that the encrypted set of data parameters was successfully synchronized to the centralized server (110).

Images