DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
SYSTEM AND METHOD FOR STITCHING SUBSCRIBER PROFILE WITH TRACE DATA
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention relates to the field of wireless communication systems, more particularly relates to a method and system for stitching subscriber profile with trace data.
BACKGROUND OF THE INVENTION
[0002] In today's telecommunications networks, network operators provide services to their customers, including voice calls, data transfers, messaging, and other network-related functionalities. When customers encounter issues or have complaints about these services, they typically reach out to the customer support team for assistance. To effectively address these issues, it is crucial for the support team to have access to accurate subscriber identification information.
[0003] In the context of a Fifth Generation (5G) network, the data flow from the Radio Access Network (RAN) primarily captures the Subscriber Permanent Identifier (SUPI), such as the International Mobile Subscriber Identity (IMSI), which is a unique identifier associated with each subscriber's SIM card. However, the Mobile Station International Subscriber Directory Number (MSISDN), which is the subscriber's phone number, is not sent in the data records generated by the network nodes. This absence of the MSISDN-SUPI mapping poses a challenge when it comes to troubleshooting and resolving customer-reported issues.
[0004] To better illustrate this challenge, let's consider an example. Suppose the customer encounters a network issue, such as poor call quality or data connectivity problems. They need to raise a complaint with the customer support team, providing their MSISDN (phone number) and location details. The support team, in turn, utilizes a solution dashboard like a trace collector to investigate and resolve the issue. However, without the mapping between the MSISDN and the SUPI, the support team is unable to directly link the customer's reported problem with the corresponding network data captured by the RAN, which primarily contains the SUPI.
[0005] Therefore, there is a need to overcome this challenge and enable efficient troubleshooting.
SUMMARY OF THE INVENTION
[0006] One or more embodiments of the present disclosure provide a method and system for stitching subscriber profile with trace data.
[0007] In one aspect of the present invention, a method for stitching subscriber profile with trace data is disclosed. The method includes the step of capturing, by one or more processors, the trace data from one or more Radio Access Network (RAN) nodes. The method includes the step of fetching, by the one or more processors, the subscriber profile from a first database using the captured trace data. The method includes the step of mapping, by the one or more processors, the fetched subscriber profile with the trace data. The method includes the step of storing, by the one or more processors, the mapped data pertaining to the fetched subscriber profile with the trace data in a second database.
[0008] In one embodiment, the subscriber profile includes at least one of, Mobile Station International Subscriber Directory Number (MSISDN), Global Phone Subscriber Identity (GPSI), and Integrated Circuit Card Identifier (ICCID).
[0009] In another embodiment, the mapping pertaining to the fetched subscriber profile with the trace data is performed by the one or more processors in a real time.
[0010] In yet another embodiment, the mapping pertaining to the fetched subscriber profile with the trace data is further enriched in each of the data records included in the second database.
[0011] In yet another embodiment, the enriched data is displayed to the user via a user interface to troubleshoot issues raised by a subscriber.
[0012] In yet another embodiment, the trace data pertains to call summary logs of the subscriber and Subscriber Permanent Identifiers (SUPI).
[0013] In yet another embodiment, the subscriber profile is fetched from the first database using a SUPI (IMSI) retrieved from the captured trace data.
[0014] In another aspect of the present invention, a system for stitching subscriber profile with trace data is disclosed. The system includes a capturing unit, configured to capture the trace data from one or more Radio Access Network (RAN) nodes. The system includes a fetching unit, configured to fetch the subscriber profile from a first database using the captured trace data. The system includes a mapping unit, configured to, map, the fetched subscriber profile with the trace data. The system includes a storage unit, configured to store, the mapped data pertaining to the fetched subscriber profile with the trace data in a second database.
[0015] In another aspect of the present invention, a network operator equipment is disclosed. One or more primary processors communicatively coupled to one or more processors. The one or more primary processors coupled with a memory. The memory stores instructions which when executed by the one or more primary processors causes the UE to transmit the request to fetch the subscriber profile from the database. The UE is configured to render enriched data pertaining to the subscriber profile with the trace data utilizing the user interface.
[0016] In yet another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by a processor is disclosed. The processor is configured to capture the trace data from a one or more Radio Access Network (RAN) nodes. The processor is configured to fetch the subscriber profile from a first database using the captured trace data. The processor is configured to map, the fetched subscriber profile with the trace data. The processor is configured to store the mapped data pertaining to the fetched subscriber profile with the trace data in a second database.
[0017] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0018] 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.
[0019] FIG. 1 is an exemplary block diagram of an environment for stitching subscriber profile with trace data, according to one or more embodiments of the present invention;
[0020] FIG. 2 is an exemplary block diagram of a system for stitching subscriber profile with trace data, according to one or more embodiments of the present invention;
[0021] FIG. 3 is an exemplary flow diagram of the system of FIG. 2, according to one or more embodiments of the present invention;
[0022] FIG. 4 is an exemplary block diagram of an architecture can be implemented in the system of FIG.2, according to one or more embodiments of the present invention;
[0023] FIG. 5 is a flow diagram illustrating a method for stitching subscriber profile with trace data, according to one or more embodiments of the present disclosure.
[0024] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0025] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0026] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0027] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0028] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of an environment 100 for stitching subscriber profile with trace data, according to one or more embodiments of the present invention. The environment 100 includes a network 105, a network operator equipment 110, a server 115, and a system 120. The network operator equipment 110 aids a user to interact with the system 120 for transmitting the request to fetch the subscriber profile from a first database (shown in FIG.2) and rendering the enriched data pertaining to the subscriber profile with the trace data utilizing a user interface 215 (shown in FIG.2). In an embodiment, the user includes a support team member or a network analyst. In an embodiment, the subscriber includes a customer who encounters a network issue, let us consider for an example, poor call quality or data connectivity problems.
[0029] For the purpose of description and explanation, the description will be explained with respect to the network operator equipment 110, or to be more specific will be explained with respect to a first network operator equipment 110a, a second network operator equipment 110b, and a third network operator equipment 110c, and should nowhere be construed as limiting the scope of the present disclosure. Each of the network operator equipment 110 from the first network operator equipment 110a, the second network operator equipment 110b, and the third network operator equipment 110c is configured to connect to the server 115 via the network 105.
[0030] In an embodiment, the first network operator equipment 110a is one of, but is not limited to, hubs, switches, routers, bridges, gateways, modems, repeaters, and access points.
[0031] In an embodiment, each of the second network operator equipment 110b, and the third network operator equipment 110c is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0032] The network 105 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 105 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0033] The server 115 may include by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise, a defense facility, or any other facility that provides content.
[0034] The environment 100 further includes the system 120 communicably coupled to the server 115 and each of the first network operator equipment 110a, the second network operator equipment 110b, and the third network operator equipment 110c via the network 105. The system 120 is configured for stitching the subscriber profile with the trace data. The system 120 is adapted to be embedded within the server 115 or is embedded as the individual entity, as per multiple embodiments of the present invention.
[0035] Operational and construction features of the system 120 will be explained in detail with respect to the following figures.
[0036] FIG. 2 is an exemplary block diagram of the system 108 for stitching the subscriber profile with the trace data, according to one or more embodiments of the present invention.
[0037] The system 120 includes a processor 205, a memory 210, a user interface 215, a first database 240, and a second database 245. For the purpose of description and explanation, the description will be explained with respect to one or more processors 205, or to be more specific will be explained with respect to the processor 205 and should nowhere be construed as limiting the scope of the present disclosure. The one or more processor 205, hereinafter referred to as the processor 205 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
[0038] As per the illustrated embodiment, the processor 205 is configured to fetch and execute computer-readable instructions stored in the memory 210. The memory 210 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 210 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like.
[0039] The user interface 215 includes a variety of interfaces, for example, interfaces for a Graphical User Interface (GUI), a web user interface, a Command Line Interface (CLI), and the like. The user interface 215 facilitates communication of the system 120. In one embodiment, the user interface 215 provides a communication pathway for one or more components of the system 120. Examples of the one or more components include, but are not limited to, the network operator equipment 110, the first database 240, and the second database 245.
[0040] The first database 240 and the second database 245 are configured to store the data from the network operator equipment 110. The first database 240 and the second database 245 are one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 250 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0041] Further, the processor 205, in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 205. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for processor 205 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the processor 205. In such examples, the system 120 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 120 and the processing resource. In other examples, the processor 205 may be implemented by electronic circuitry.
[0042] In order for the system 120 to stitch the subscriber profile with trace data. The processor 205 includes a capturing unit 220, a fetching unit 225, a mapping unit 230, and a storage unit 235 communicably coupled to each other. In an embodiment, operations and functionalities of the capturing unit 220, the fetching unit 225, the mapping unit 230, and the storage unit 235 can be used in combination or interchangeably.
[0043] The capturing unit 220 is configured to capture the trace data from one or more Radio Access Network (RAN) nodes. The RAN nodes are components in a mobile communication network for providing wireless connectivity between the network operator equipment 110 and a core network. The RAN nodes can handle various tasks related to radio transmission, reception, and management. In an embodiment, the RAN include is at least one of, next-generation Node B (gNB). In an alternate embodiment, the RAN includes but not limited to the evolved Node B (eNB), and Base Transceiver Station (BTS). The trace data includes, but not limited to, user identifier such as SUPI, cell identifiers, call detailed records, or summary logs.
[0044] Upon capturing the trace data from the one or more RAN nodes, the fetching unit 225 is configured to fetch the subscriber profile from a first database 240 using the captured trace data. In an embodiment, the first database 240 includes but not limited to, an Inventory Management System (IMS). The first database 240 is a system or framework designed to consolidate and manage all inventory-related data and processes across various network elements and services in a unified manner, which ensures that inventory data is accurate, up-to-date, and accessible across different departments and systems.
[0045] As per the one embodiment, the subscriber profile includes at least one of, Mobile Station International Subscriber Directory Number (MSISDN), Global Phone Subscriber Identity (GPSI), and Integrated Circuit Card Identifier (ICCID). The Mobile Station International Subscriber Directory Number (MSISDN) is a unique number that identifies a mobile phone number internationally. The MSISDN is used for routing calls and Short Message Service (SMS) messages to the correct recipient. The Global Phone Subscriber Identity (GPSI) is a unique identifier used to globally identify a subscriber's phone number across different networks. The GPSI is part of the architecture defined in the context of the IP Multimedia Subsystem (IMS) and next-generation networks, such as 5G. The Integrated Circuit Card Identifier (ICCID) is a unique identifier assigned to each SIM (Subscriber Identity Module) card. The ICCID is used to identify the SIM card internationally and is typically stored in the SIM card itself. The ICCID identifier is essential for managing and tracking the SIM cards, ensuring the SIM cards are uniquely recognized across different networks and operators.
[0046] As per one or more embodiments, the subscriber profile is not limited to Fifth Generation (5G) identities. In an alternate embodiment, the subscriber profile includes, but is not limited to Second Generation (2G), Third Generation (3G), Fourth Generation (4G) identities. The subscriber profile is fetched from the first database 240 using a Subscriber Permanent Identifier (SUPI), such as an International Mobile Subscriber Identity (IMSI), retrieved from the captured trace data.
[0047] Upon fetching the subscriber profile from the first database 240 using the captured trace data, the mapping unit 230 is configured to map the fetched subscriber profile with the trace data. The mapping pertaining to the fetched subscriber profile with the trace data is performed by the mapping unit 230 in real time. The real-time mapping process ensures that the subscriber profile is accurately aligned with the captured trace data. By performing this operation in real time, the mapping unit 230 enables immediate correlation and analysis, facilitating prompt and precise insights into network performance of a subscriber.
[0048] Upon mapping the fetched subscriber profile with the trace data, the storage unit 235 is configured to store the mapped data pertaining to the fetched subscriber profile with the trace data in a second database 245. The mapping pertaining to the fetched subscriber profile with the trace data is further enriched in each of the data records included in the second database 245. The enriched data is displayed to the user via the user interface 215 to troubleshoot issues raised by the subscriber. By doing so, the system 120 achieves aligning MSISDNs with SUPIs, overcoming the limitation of the one or more RAN nodes generated call summary logs that only capture SUPIs without MSISDNs. The call summary logs are enriched with the MSISDN data. The MSISDN data is fetched using the SUPI. The system 120 ensures the availability of accurate mapping information, empowering the user to effectively analyze and resolve customer-reported issues based on the data records and the subscriber profiles.
[0049] FIG. 3 illustrates an exemplary block diagram of an architecture that can be implemented in the system of FIG.2, according to one or more embodiments of the present invention. More specifically, FIG. 3 illustrates the system 120 configured for stitching the subscriber profile with trace data. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first network operator equipment 105a for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0050] As mentioned earlier in FIG.1, In an embodiment, the first network operator equipment 105a may encompass electronic apparatuses. These devices are illustrative of, but not restricted to, modems, routers, switches, laptops, tablets, smartphones (including phones), or other devices enabled for web connectivity. The scope of the first network operator equipment 105a explicitly extends to a broad spectrum of electronic devices capable of executing computing operations and accessing networked resources, thereby providing users with a versatile range of functionalities for both personal and professional applications. This embodiment acknowledges the evolving nature of electronic devices and their integral role in facilitating access to digital services and platforms. In an embodiment, the first network operator equipment 105a can be associated with multiple users. Each of the first network operator equipment 105a is communicatively coupled with the processor 205.
[0051] The first network operator equipment 105a includes one or more primary processors 305 communicably coupled to the one or more processors 205 of the system 120. The one or more primary processors 305 are coupled with a memory 310 storing instructions which are executed by the one or more primary processors 305. Execution of the stored instructions by the one or more primary processors 305 enables the first network operator equipment 105a to transmit the request to fetch the subscriber profile from the first database 240.
[0052] Furthermore, the one or more primary processors 305 within the first network operator equipment 105a are uniquely configured to execute a series of steps as described herein. This configuration underscores the processor 205 capability to stitch the subscriber profile with the trace data. The operational synergy between the one or more primary processors 305 and the additional processors, guided by the executable instructions stored in the memory 310.
[0053] As mentioned earlier in FIG.2, the system 120 includes the one or more processors 205, the memory 210, the user interface 215, the first database 240, and the second database 245. The operations and functions of the one or more processors 205, the memory 210, the user interface 215, the first database 240, and the second database 245 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 120 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0054] Further, the processor 205 includes the capturing unit 220, the fetching unit 225, the mapping unit 230, and the storage unit 235. The operations and functions of the capturing unit 220, the fetching unit 225, the mapping unit 230, and the storage unit 235 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 120 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 120 in FIG. 3, should be read with the description provided for the system 120 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0055] FIG. 4 is an exemplary block diagram of an architecture 400 which can be implemented in the system 120 of FIG.2, according to one or more embodiments of the present invention.
[0056] The architecture 400 of the system 120 includes several components and their connections to enable the alignment of subscriber identification information for effective issue identification and troubleshooting.
[0057] In one implementation, the architecture 400 of the system 120 includes GNBs 405a-405c. The GNBs 405a-405c include but not limited to, Radio Access Network (RAN) nodes. The GNBs 405a-405c, alternatively referred as to GNodeBs, represent the network nodes responsible for providing connectivity and managing radio resources in a 5G network. The GNBs 405a-405c capture and generate the RAN data, specifically the SUPI (Subscriber Permanent Identifier) or the IMSI (International Mobile Subscriber Identity) values, associated with the subscribers. However, the MSISDN (Mobile Station International Subscriber Directory Number) or the GPSI (Global Phone Subscriber Identity) values, which are the subscribers' phone numbers, are not sent in the data records by the GNBs 405a-405c.
[0058] In one implementation, the architecture 400 of the system 120 includes the processor 205. The processor acts as a middleware that bridges a gap between the RAN data captured by the GNBs 405a-405c and the subscriber details, such as the MSISDN and the SUPI. The processor 205 integrates with various systems and performs the mapping between the MSISDN and the SUPI to enable efficient troubleshooting.
[0059] In one implementation, the architecture 400 of the system 120 includes the first database 240, also known as the IMS, serves as a central repository for storing subscriber-related information. It contains data such as IMSI, MSISDN, and ICCID (Integrated Circuit Card Identifier). The processor 205 fetches the subscriber details directly from the first database 240 using an ingestion layer 410.
[0060] In one implementation, the architecture 400 of the system 120 includes the ingestion layer 410. The ingestion layer 410 acts as a connector between the processor 205 and the first database 240. The ingestion layer 410 retrieves the subscriber details, including the IMSI, the MSISDN, and the ICCID, from the first database 240 at configurable time intervals. The ingestion layer 410 ensures the timely supply of this information to the processor 205 for further processing.
[0061] In an embodiment, the processor 205 is configured to receive the subscriber details from the ingestion layer 410 and performs the necessary operations to create and store the mapping between the MSISDN and the SUPI. The processor 205 is configured to create a separate point in the second database 245. The MSISDN-SUPI values are then made available for further analysis and troubleshooting.
[0062] In one implementation, the processor 205 is further configured to ensure the mapping information is synched in real time and with an intelligent AI/ML engine, the processor 205 is configured to monitor the performance, behavior, and take corrective actions in real time. In an embodiment, by synching the information with the AI/ML engine, the system 120 can enrich the information and train the AI/ML engine further without relying on the third-party applications or systems.
[0063] In one implementation, the architecture 400 of the system 120 includes the second database 245. The second database 245 is a storage location where the processor 205 stores the MSISDN-SUPI mapping. This data repository allows for efficient access to the mapping information, enabling end users to retrieve the necessary details for analyzing and resolving customer-reported issues.
[0064] By combining these components and their functionalities, the system 120 allows for the stitching of the subscriber profile by aligning the MSISDN to the SUPI and vice versa. This enables the user, such as a support team member or network analyst using a trace collector dashboard, to correlate customer-reported issues with the corresponding RAN data captured by the GNBs 4052-405c.
[0065] For example, when the subscriber raises a complaint with the customer support team, providing their MSISDN and location details, the support team can utilize the processor 205 and access the MSISDN-SUPI mapping stored in the second database 245. This mapping information allows to link the customer's reported issue with the relevant RAN data, which primarily contains the SUPI. The user can analyze the data records and troubleshoot the issue effectively, leading to a faster resolution and improved customer experience.
[0066] FIG. 5 is a flow diagram illustrating a method 500 for stitching subscriber profile with trace data, according to one or more embodiments of the present disclosure. For the purpose of description, the method 500 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0067] At step 505, the method 500 includes the step of capturing the trace data from one or more Radio Access Network (RAN) nodes by the capturing unit 220. The RAN nodes are components in a mobile communication network for providing wireless connectivity between the network operator equipment 110 and a core network. In an embodiment, the RAN include is at least one of, next-generation Node B (gNB). In an alternate embodiment, the RAN includes but not limited to the evolved Node B (eNB), and Base Transceiver Station (BTS).
[0068] At step 510, the method 500 includes the step of fetching the subscriber profile from the first database 240 using the captured trace data by the fetching unit 225. In an embodiment, the first database 240 includes but not limited to, an Inventory Management System (IMS).
[0069] At step 515, the method 500 includes the step of mapping the fetched subscriber profile with the trace data by the mapping unit 230. The mapping pertaining to the fetched subscriber profile with the trace data is performed by the mapping unit 230 in real time. The real-time mapping process ensures that the subscriber profile is accurately aligned with the captured trace data. By performing this operation in real time, the mapping unit 230 enables immediate correlation and analysis, facilitating prompt and precise insights into network performance of the subscriber.
[0070] At step 520, the method 500 includes the step of storing the mapped data pertaining to the fetched subscriber profile with the trace data in the second database 245 by the storage unit 235. The mapping pertaining to the fetched subscriber profile with the trace data is further enriched in each of the data records included in the second database 245. The enriched data is displayed to the user via the user interface 215 to troubleshoot issues raised by the subscriber.
[0071] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 205. The processor 205 is configured to capture the trace data from one or more Radio Access Network nodes. The processor 205 is configured to fetch the subscriber profile from a first database 240 using the captured trace data. The processor 205 is configured to map the fetched subscriber profile with the trace data. The processor 205 is configured to store the mapped data pertaining to the fetched subscriber profile with the trace data in a second database 245.
[0072] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-5) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0073] The present disclosure provides technical advancement for aligning the MSISDNs with the SUPIs, overcoming the limitation of the GNB-generated call summary logs that only capture the SUPIs without the MSISDNs. The present disclosure ensures the availability of accurate mapping information, empowering the end user to effectively analyze and resolve customer-reported issues based on the data records and the subscriber profile.
[0074] The system and method of the present embodiment offer following advantages:
[0075] Enhanced Troubleshooting: The invention enables the alignment of MSISDNs with SUPIs, providing a comprehensive view of the subscriber profile. This alignment allows the users, such as support team members or network analysts, to easily correlate customer-reported issues with the RAN data captured by GNBs. It streamlines the troubleshooting process, leading to faster and more accurate issue identification and resolution.
[0076] Improved Customer Experience: By efficiently addressing customer-reported issues, the invention enhances the overall customer experience. The ability to quickly identify and resolve network service problems translates to reduced downtime, improved service quality, and increased customer satisfaction.
[0077] Effective Data Analysis: The invention provides the users with the necessary mapping of the MSISDNs and the SUPIs, empowering them to analyze data records in a more precise and targeted manner. With access to the complete subscriber profile, including MSISDNs and associated SUPIs, the user can extract valuable insights from the data, identify patterns, and make informed decisions for optimizing network performance.
[0078] Streamlined Network Operations: By aligning MSISDNs with SUPIs, the invention streamlines network operations and maintenance. The accurate mapping of subscriber profiles allows for efficient monitoring, troubleshooting, and resource allocation, leading to improved network efficiency and reduced operational costs.
[0079] Scalability and Flexibility: The solution can be implemented in various telecommunications networks, including 5G networks, making it scalable and adaptable to different environments. It can integrate with existing systems and processes, allowing for seamless deployment and integration without significant disruptions or infrastructure changes.
[0080] Real-Time Access to Mapping Information: The invention provides real-time access to the MSISDN-SUPI mapping information. This allows the users to retrieve and utilize the mapping data whenever needed, enabling immediate troubleshooting and analysis of network issues.
[0081] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS

[0082] Environment - 100;
[0083] Network-105;
[0084] Network operator equipment- 110;
[0085] Server - 115;
[0086] System -120;
[0087] Processor - 205;
[0088] Memory - 210;
[0089] User interface-215;
[0090] Capturing unit – 220;
[0091] Fetching unit– 225;
[0092] Mapping unit – 230;
[0093] Storage unit– 235;
[0094] First database-240;
[0095] Second database-245;
[0096] Primary processor- 305;
[0097] Memory- 310;
[0098] GNBs-405a-405c;
[0099] Ingestion layer-410.

,CLAIMS:CLAIMS
We Claim:
1. A method (500) for stitching subscriber profile with trace data, the method (500) comprising the steps of:
capturing, by one or more processors (205), the trace data from one or more Radio Access Network (RAN) nodes;
fetching, by the one or more processors (205), the subscriber profile from a first database (240) using the captured trace data;
mapping, by the one or more processors (205), the fetched subscriber profile with the trace data; and
storing, by the one or more processors (205), the mapped data pertaining to the fetched subscriber profile with the trace data in a second database (245).

2. The method (500) as claimed in claim 1, wherein the subscriber profile includes at least one of, Mobile Station International Subscriber Directory Number (MSISDN), Global Phone Subscriber Identity (GPSI), and Integrated Circuit Card Identifier (ICCID).

3. The method (500) as claimed in claim 1, wherein the mapping pertaining to the fetched subscriber profile with the trace data is performed by the one or more processors (205) in a real time.

4. The method (500) as claimed in claim 1, wherein the mapping pertaining to the fetched subscriber profile with the trace data is further enriched in each of a data record included in the second database (245).

5. The method (500) as claimed in claim 4, wherein the enriched data is displayed to the user via a user interface (215) to troubleshoot issues raised by a subscriber.

6. The method (500) as claimed in claim 1, wherein the trace data pertains to call summary logs of the subscriber and Subscriber Permanent Identifiers (SUPI).

7. The method (500) as claimed in claim 1, wherein the subscriber profile is fetched from the first database (240) using a SUPI (IMSI) retrieved from the captured trace data.

8. A system (120) for stitching subscriber profile with trace data, the system (120) comprises:
a capturing unit (220), configured to, capture, the trace data from one or more Radio Access Network (RAN) nodes;
a fetching unit (225), configured to, fetch, the subscriber profile from a first database (240) using the captured trace data;
a mapping unit (230), configured to, map, the fetched subscriber profile with the trace data; and
a storage unit (235), configured to, store, the mapped data pertaining to the fetched subscriber profile with the trace data in a second database (245).

9. The system (120) as claimed in claim 7, wherein the subscriber profile includes at least one of, Mobile Station International Subscriber Directory Number (MSISDN), Global Phone Subscriber Identity (GPSI), and Integrated Circuit Card Identifier (ICCID).

10. The system (120) as claimed in claim 7, wherein the mapping pertaining to the fetched subscriber profile with the trace data is performed by the mapping unit (230) in real time.

11. The system (120) as claimed in claim 7, wherein the mapping pertaining to the fetched subscriber profile with the trace data is further enriched in each of a data record included in the second database (245).

12. The system (120) as claimed in claim 10, wherein the enriched data is displayed to the user via a user interface to troubleshoot issues raised by a subscriber.

13. The system (120) as claimed in claim 10, wherein the subscriber profile is fetched from the first database (240) using a SUPI (IMSI) retrieved from the captured trace data.

14. A network operator equipment (110), comprising:
one or more primary processors (305) communicatively coupled to one or more processors (205), the one or more primary processors (305) coupled with a memory (310), wherein said memory (310) stores instructions which when executed by the one or more primary processors (305) causes the network operator equipment to:
transmit, the request to fetch the subscriber profile from the first database (240);
render, the enriched data pertaining to the subscriber profile with the trace data utilizing the user interface (215); and
wherein the one or more processors (205) is configured to perform the steps as claimed in claim 1.