FORM 2
THE PATENTS ACT, 1970 (39 of 1970) THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(See section 10; rule 13)
TITLE OF THE INVENTION
SYSTEM AND METHOD FOR ENRICHING DATA WITH USER EQUIPMENT ATTRIBUTES
APPLICANT
JIO PLATFORMS LIMITED
of Office-101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad -
380006, Gujarat, India; Nationality : India
The following specification particularly describes
the invention and the manner in which
it is to be performed

RESERVATION 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.
FIELD OF DISCLOSURE
[0002] The embodiments of the present disclosure generally relate to
communication networks. In particular, the present disclosure relates to a system and a method for enriching data with user equipment attributes.
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] Data enrichment is the process of combining data from internal
sources with disparate data from other internal source or data from external sources.
[0005] Original Equipment Manufacturers (OEMs) are companies that
manufacture products or components that are used in another company's end products. OEMs might produce components like processors, memory chips, or displays that are integrated into smartphones, computers, or other consumer electronics devices.

[0006] Clear codes indicate reasons for failures or other issues in the
network. The codes provide information about issues like busy signals, timeouts, restrictions, congestion, equipment failures, protocol errors and more.
[0007] Error messages indicate errors occurring in the network. Error
messages provide information about issues such as transmission error, data packet loss, network latency, configuration errors, etc.
[0008] Subscriber detail records (SDRs) are a type of data record used in
telecommunications and network management to capture information about subscriber activity, usage, and interactions within a telecommunications network. These records contain detailed information about individual subscribers' interactions with network services, such as calls, messages, data usage, and other transactions.
[0009] An operator, also known as a service provider, is a provider of
communications services that owns or controls all the elements necessary to sell and deliver services to an end user (e.g., subscriber).
[0010] Type Allocation Code (TAC) is a code at the beginning of
International Mobile Equipment Identity (IMEI) number that identifies cellular devices, including its manufacturer, model number, and regulatory approval.
[0011] International Mobile Equipment Identity (IMEI) number is a unique
15-digit serial number for identifying a device.
[0012] Mobile Station International Subscriber Directory Number
(MSISDN) is a number that uniquely identifies a subscription in a mobile network. An MSISDN is the phone number associated with a single SIM card and is the number to which the user calls or sends an SMS message.

[0013] International Mobile Subscriber Identity (IMSI) is a number that
uniquely identifies every user of a cellular network.
[0014] Subscription Permanent Identifier (SUPI) is a unique identifier used
to represent a subscriber's permanent identity in a 5G network.
[0015] Correlation values are used to understand the relationship between
different parameters or variables.
[0016] Root cause analysis (RCA) is a systematic process used to identify
the underlying reasons or root causes of network failures or issues. The RCD is used to identify and address the root causes of network failures, thereby improving network reliability, performance, and resilience over time.
BACKGROUND OF DISCLOSURE
[0017] 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.
[0018] Cellular networks provide services to a plurality of user equipment
(UE). These UEs may have different specifications and configurations, which may not necessarily comply with standards, thereby causing network issues and failures. While cellular networks try to identify and reduce network failures, often the fault is in the UE. Existing data analytics of cellular network data tends to be insufficient in discerning whether network failures are caused by malfunctioning of the network or the UE. For instance, a UE may not be able to appropriately access services such as Voice over New Radio (VoNR) due to non-compliance with standards, inherent bugs, or specifications that do not support the service. However, the network may

not be able to identify the cause of the issue with subscriber data or session logs alone. Often device level data, such as device brand, model, chipsets, specifications, configurations, and the like, are stored separately and difficult to correlate with subscriber data and other operational data generated as the network provides services to UEs.
[0019] There is, therefore, a need in the art to provide a method and a system
that can overcome the shortcomings of the existing prior arts.
SUMMARY
[0020] In an exemplary embodiment, a method for identifying a plurality of
network entities associated with a plurality of user equipments causing network issues in a network is described. The method comprises receiving, by a processor, a set of packet code data generated by the plurality of network entities, wherein the set of packet code data is indicative of clear codes or error messages causing network issues or failures. The method further comprises enriching, by the processor, subscriber detail records (SDRs) in the set of packet code data by associating the SDRs in the set of packet code data with a plurality of user equipment attributes. The method comprises determining, by the processor, a correlation value between each of the plurality of user equipment attributes and each of clear codes in the set of packet code data. The method further comprises identifying, by the processor, the correlation value beyond a predetermined performance threshold range. The method comprises based on the identified correlation value, identifying, by the processor, the user equipment attribute as a source of a network issue. The method further comprises sending, by the processor, an alert signal to one network entity of the plurality of network entities corresponding to the identified user equipment attribute.

[0021] In some embodiments, the user equipment is identified based on a
type allocation code (TAC) associated with a unique identifier of the user equipment in the SDRs.
[0022] In some embodiments, the plurality of network entities comprises a
subscriber of the user equipment, an original equipment manufacturer (OEM) of the user equipment, and an operator.
[0023] In some embodiments, the user equipment attributes comprise
specification attribute, model attribute, manufacturer attribute, configuration attribute, software version attribute, unique identifier attributes, hardware attribute, chipset type attribute, and communication standard attribute.
[0024] In some embodiments, the SDRs comprises subscriber names,
subscriber addresses, unique identifiers. The unique identifiers comprise a mobile station international subscriber directory number (MSISDN), an international mobile equipment identity (IMEI) number, an international mobile subscriber identity (IMSI), a subscriber permanent identifier (SUPI).
[0025] In some embodiments, the alert signal comprises recommendations
to the operator for resolving the network issue, notification to the user equipment to update the software version of the user equipment or check for settings of the user equipment.
[0026] In another exemplary embodiment, a system for identifying a
plurality of network entities associated with a plurality of user equipments causing network issues in a network is described. The system comprises a data acquisition unit configured to receive a set of packet code data generated by the plurality of network entities. The set of packet code data is indicative of clear codes or error messages causing network issues or failures. A normalizer unit is configured to enriching subscriber detail records (SDRs) in the set of packet code data by associating the SDRs in the set of packet code data with a plurality of user

equipment attributes. A correlation unit is configured to determine a correlation value between each of the plurality of user equipment attributes and each of clear codes in the set of packet code data. The correlation unit is configured to identify the correlation value beyond a predetermined performance threshold range. Based on the identified correlation value, the correlation unit is configured to identify the user equipment attribute as a source of a network issue. A sending unit is configured to send an alert signal to one network entity of the plurality of network entities corresponding to the identified user equipment attribute.
[0027] In some embodiments, the user equipment is identified based on a
type allocation code (TAC) associated with a unique identifier of the user equipment in the SDRs.
[0028] In some embodiments, the plurality of network entities comprises a
subscriber of the user equipment, an original equipment manufacturer (OEM) of the user equipment and an operator.
[0029] In some embodiments, the user equipment attributes comprise
specification attribute, model attribute, manufacturer attribute, configuration attribute, software version attribute, unique identifier attributes, hardware attribute, chipset type attribute, and communication standard attribute.
[0030] In some embodiments, the SDRs comprises subscriber names,
subscriber addresses, unique identifiers. The unique identifiers comprise mobile station international subscriber directory number (MSISDN), international mobile equipment identity (IMEI) number, international mobile subscriber identity (IMSI), subscriber permanent identifier (SUPI).
[0031] In some embodiments, the alert signal comprises recommendations
to the operator for resolving the network issue, notification to the user equipment to update the software version of the user equipment or check for settings of the user equipment.

[0032] In some embodiments, a user equipment is communicatively
coupled with a system. The coupling comprises steps of receiving, by the system, a connection request and sending, by the system, an acknowledgment of the connection request to the UE. The coupling further comprises transmitting a plurality of signals in response to the connection request. The system is configured for identifying a plurality of network entities associated with a plurality of user equipments causing network issues in a network.
OBJECTS OF THE PRESENT DISCLOSURE
[0033] Some of the objects of the present disclosure, which at least one
embodiment herein satisfies are as listed herein below.
[0034] An object of the present disclosure is to provide a system and a
method for enriching data with user equipment attributes.
[0035] Another object of the present disclosure is to provide a system and a
method that correlates user equipment attributes with packet code data collected and stored by the network.
[0036] Another object of the present disclosure is to provide a system and a
method that monitors user equipment-wise distribution of clear code data.
[0037] Another object of the present disclosure is to provide a system and a
method that notifies the user or original equipment manufacturers of faults in the user equipment.
[0038] Another object of the present disclosure is to provide a system and a
method that provides a dashboard for analyzing the enriched packet code data.

[0039] Another object of the present disclosure is to provide a system and a
method that resolves the identified network issue(s) to improve subscriber experience.
BRIEF DESCRIPTION OF DRAWINGS
[0040] 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 the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0041] FIG. 1 illustrates an exemplary network architecture for enriching
data with user equipment attributes, in accordance with embodiments of the present disclosure.
[0042] FIG. 2 illustrates a block diagram of a system, in accordance with
embodiments of the present disclosure.
[0043] FIG. 3 illustrates an exemplary implementation of the system, in
accordance with embodiments of the present disclosure.
[0044] FIG. 4 illustrates a flowchart of a method for identifying a plurality
of network entities associated with a plurality of user equipments causing network issues in a network, in accordance with embodiments of the present disclosure.

[0045] FIG. 5 illustrates an exemplary computer system in which or with
which embodiments of the present disclosure may be implemented.
[0046] The foregoing shall be more apparent from the following more
detailed description of the disclosure.
DETAILED DESCRIPTION OF DISCLOSURE
[0047] 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 all 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.
[0048] 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.
[0049] 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.
[0050] Also, it is noted that individual embodiments may be described as a
process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0051] 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 in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.
[0052] 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.
[0053] The terminology used herein is for the purpose of describing
particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly 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 and all combinations of one or more of the associated listed items.
[0054] The present disclosure relates to a system and a method for enriching
data with user equipment attributes. The system receives a set of packet code data generated by network entities associated with plurality of user equipments in the network. The set of clear codes being indicative of clear codes or error messages causing network issues or failures. The system enriches Subscriber Detail Records (SDRs) data in the packet code data by associating one or more user equipment (UE) attributes therewith. The system determines a correlation value corresponding to pairs between each of the UE attributes and each of clear codes in the packet code data. The system identifies one or more UE attributes as a source of a network issue when the correlation value between the UE attribute and the set of clear codes is beyond a predetermined performance threshold range. The system transmits a set of alert signals to notify entities of the identified UE attribute for resolution.
[0055] The various embodiments throughout the disclosure will be
explained in more detail with reference to FIGs. 1-5.

[0056] FIG. 1 illustrates an exemplary network architecture (100) for
enriching data with user equipment attributes, in accordance with embodiments of the present disclosure.
[0057] Referring to FIG. 1, the network architecture (100) may include one
or more computing devices or user equipments (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)”, “user device” 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.
[0058] 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 of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the 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 operator or the entity such as touch pad, touch enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the user equipment (104) may not be restricted to the mentioned devices and various other devices may be used.
[0059] Referring to FIG. 1, the user equipment (104) may communicate
with a system (108) through a network (106). In an embodiment, the network (106) may include at least one of a Fifth Generation (5G) network, 6G network, or the like. The network (106) may enable the user equipment (104) to communicate with other devices in the network architecture (100) and/or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.
[0060] In an embodiment, each UE (104) may have set of attributes that
correspond to including, but not limited to, specification attribute, model attribute, manufacturer attribute, configuration attribute, software version attribute, unique identifier attributes, hardware attribute, chipset type attribute, technology attribute and the like, associated therewith.
[0061] In an aspect, the specification attribute may include, but not limited
to, hardware specifications, communication interfaces (e.g., wired, or wireless), operating system, security, connectivity, etc. In an aspect, model attribute may include, but not limited to, brand name, manufacturer, model name, model number, processor, storage, sensors, form factor (e.g., physical design, shape), etc. In an aspect, the manufacturer attribute may include, but not limited to, product design,

materials, quality of products, etc. In an aspect, the configuration attribute may include, but not limited to, network settings, notification settings, security settings, privacy settings, power settings, etc. In an aspect, the software version attribute may include, but not limited to, feature updates, security updates, software versions, etc. In an aspect, the hardware attribute may include, but not limited to, processor, memory, storage, material, etc. In an aspect, the chipset type attribute may include, but not limited to, processor, graphics processor, controller, memory, peripheral interfaces, etc. In an aspect, the technology attribute may include, but not limited to, wireless technology, location services, authentication, sensors, etc.
[0062] In an embodiment, the unique identifier attribute may be indicative
of, but not limited to, Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, International Mobile Subscriber Identity (IMSI), Subscriber Permanent Identifier (SUPI) and the like.
[0063] In an embodiment, the network (106) may include at least one of a
Fifth Generation (5G) network, Sixth Generation (6G) network, or the like. The network (106) may enable the user equipment (104) to communicate with other devices in the network architecture (100) and/or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.
[0064] In an embodiment, the network (106) may include one or more base
stations (112), which the UEs (104) may connect to and request services from. The base station (112) may be a network infrastructure that provides wireless access to one or more terminals associated therewith. The base station (112) may have

coverage defined to be a predetermined geographic area based on the distance over which a signal may be transmitted. The base station (112) may include, but not be limited to, wireless access point, evolved NodeB (eNodeB), 5G node or next generation NodeB (gNB), wireless point, transmission/reception point (TRP), and the like. In an embodiment, the base station (112) may include one or more operational units that enable telecommunication between two or more UEs. In an embodiment, the one or more operational units may include, but not be limited to, transceivers, baseband unit (BBU), remote radio unit (RRU), antennae, mobile switching centres, radio network control units, one or more processors associated thereto, and a plurality of network entities (110) such as, but not limited to, Access and Mobility Management Function (AMF) unit, Session Management Function (SMF) unit, Network Exposure Function (NEF) units, or any custom built functions executing one or more processor-executable instructions, but not limited thereto. In an aspect, the plurality of network entities (110) may include, but not limited to, a subscriber of the user equipment, an original equipment manufacturer (OEM) of the user equipment and an operator.
[0065] In an embodiment, the network (106) may generate one or more
operational data as the network (106) provides services to the UE (104). The operational data may include, but not be limited to, attributes associated with the base stations, subscriber session logs, instance objects created by network functions, call detail records (CDR), one or more health and performance metrics associated with the network (106), and the like. In an example, subscriber session logs may be generated as the network (106) provides services to the UE (104). The subscriber session logs may include, but not be limited to, unique attributes of the base stations and the UEs (104), sessions created between the UE (104) and the network entities, session start and termination times, and other service specific attributes. In an embodiment, the operational data may be used to compute one or more Key Performance Indicators (KPIs) for assessing performance of the network (106). In an embodiment, Key Performance Indicators (KPIs) of network may include, but not limited to, coverage, capacity, mobility, quality of service (QoS),

fault management, etc. In an embodiment, the operational data may also include the clear codes transmitted between the network entities of the network (106), which may indicate network failures or issues experienced by the network (106). In an example, the network failures or issues may include, but not limited to, network congestion, packet loss, latency, jitter, configuration error, security issues, software issues, etc.
[0066] In an aspect, the network issues or failures may be, but not limited
to, subscriber-related issues or failures, original equipment manufacturer (OEM) related issues or failures and operator related issues or failures.
[0067] In an aspect, the subscriber-related issues or failures may comprise,
but not limited to, activation failures, provisioning errors, SIM card malfunction, SIM card registration failure, authentication, compatibility issues, weak or no signal coverage, handover failures, service restrictions, device configuration issues, inappropriate network mode selection, fraudulent activity, security breaches, regulatory and compliance issues, etc.
[0068] In an aspect, the OEM related issues or failures may comprise, but
not limited to, hardware defects (e.g., component failure, physical damage, etc.), software bugs or glitches (e.g., firmware issues, operating system problems, etc.), design flaws, quality control issues (e.g., manufacturing defects, testing failures, etc.), compatibility and interoperability problems (e.g., network protocol issues, integration challenges, etc.), security vulnerabilities (e.g., data privacy concerns, etc.), lack of support or updates for older devices.
[0069] In the aspect, the operator related issues or failures may comprise,
but not limited to, network congestion (e.g., high traffic load, poor resource allocation), hardware and infrastructure problems, faulty network configuration, scheduled downtime, upgrade issues, network security breaches, fraudulent

activities, regulatory compliance (e.g., license compliance, legal restrictions), interconnectivity and roaming problems, etc.
[0070] In an embodiment, the operational data may also include the one or
more packet code data or clear codes exchanged between the network entities (110) for providing services to the UE (104). In an aspect, the set of packet code data generated by network entities typically refers to data packets exchanged within a network. The packets contain information necessary for the network to function, manage traffic, and ensure communication between devices. The information may comprise, but not limited to, packets routing information, management information (e.g., routing, error checking, congestion control, QoS, session information), network performance monitoring and troubleshooting, network diagnostics and troubleshooting to identify issues, error detection.
[0071] In an embodiment, the network (106) may also maintain one or more
Subscriber Detail Records (SDRs) that include, but not limited to, name, address, unique identifier attributes, and any other information identifying the user (102) of the network (106).
[0072] In an embodiment, the system (108) may be coupled to a monitoring
unit that may provide an audio-visual interface to the user (102) for visualizing and analysing data. In an embodiment, the monitoring unit may provide an interface, including, but not limited to, a Graphical User Interface (GUI), an Application Programming Interface (API) or a Command Line Interface (CLI). In an embodiment, the monitoring unit may be configured to provide real-time analysis of data provided by the system (108). An operator may use the monitoring unit to monitor and analyze the data stored in a database (210) (shown in FIG. 2).
[0073] In an embodiment, the system (108) may be configured to receive a
set of packet code data generated by the network entities (110) of the network (106). In an embodiment, the set of packet code data may include clear code or error

messages, which can be used for inferring network issues or failures encountered during the operation of the network (106). In an embodiment, the packet code data may be associated with the SDR data. In an embodiment, the SDR data may uniquely identify the UEs (104) using a Type Allocation Code (TAC) associated with the unique identifier attributes of the UEs (104). In an embodiment, the packet code data may be validated before further processing.
[0074] In an embodiment, the system (108) may enrich the SDR data by
associating the one or more UE attributes therewith, thereby associating the one or more UE attributes with the packet code data. In an embodiment, the SDR data in the packet code data may be enriched with the one or more UE attributes based on the TAC. In an embodiment, the system (108) may provide a dashboard on the monitoring unit that may allow the operator of the system (108) to analyze and visualize the enriched data. In an example, the dashboard may enable the operator to list UEs (104) with model attributes or specification attributes encountering the highest or lowest count of errors and identifies UEs (104) with performance metrics or subscriber experience metrics below a predetermined threshold.
[0075] In an embodiment, the system (108) may determine a correlation
value corresponding to pairs of each of the one or more UE attributes and each of clear codes in the set of packet code data. To determine the correlation values corresponding to pairs of each of UE attributes and each of the clear codes, the system, collecting data corresponding to each of UE attributes and the each of clear codes. The type of correlation coefficient is decided based on the nature of data (e.g., linear or nonlinear). The correlation coefficient is calculated for each of UE attributes and the each of clear codes. The correlation values are interpreted. The correlation coefficients are calculated separately for each user equipment attribute with each clear code to create a matrix of correlation values.
[0076] In an embodiment, the system (108) may identify one or more of the
UE attributes as the source of a network issue when the correlation values between

the UE attribute and the set of clear codes are beyond a predetermined performance threshold range. In an aspect, the predetermined performance threshold range may refer to a set range of acceptable performance levels that have been determined for a particular system, process, or product. The threshold range may serve as a benchmark against which actual performance can be measured and evaluated. In an aspect, predetermining of the performance threshold range comprises identifying relevant performance metrics. Existing data corresponding to the performance metrics is collected under normal operating conditions. The collected data corresponding to performance metrics is analysed to identify ranges and patterns of performance metrics. The threshold value range for each performance metric is determined based on analysis. In this way, the performance threshold range is predetermined. In an example, latency threshold range comprises below 50ms = normal latency, between 50ms-100ms = acceptable latency, beyond 100ms = potential issue and packet loss threshold range comprises normal packet loss is less than 1%, moderate packet loss = between 1% to 5% and beyond 5% = potential issues. The correlation values for the packet loss and the latency = 0.7. The correlation values above 0.7 indicate network congestion or equipment issues. On detecting correlation values exceeds 0.7, the system indicates high network congestion occurs. The system identifies network configurations and traffic patterns as source of network outage. The user can check which network configurations such as router and switch logs indicate for any signs of congestion or errors. In an example, the system (108) may identify the subset of UE attributes, such as the model attributes, that are either positively or negatively correlated with clear codes in the packet code data, such as call drop reasons. In such examples, the system (108) may identify the model attribute value having the correlation values higher than the predetermined performance threshold range for the call drop reason clear code and associate the model attribute value as the source for network issue or failure. In this way, the user equipment attributes are correlated with the error/clear codes for the session and derives root cause analysis (RCA) for the given user equipment failure scenarios. The user equipment level issue correlation may help

the user for identification of the set of devices leading to the network issues and/or failures.
[0077] In an embodiment, the system (108) may transmit a set of alert
signals intimating the source of the network issue to the user (102), operator of the system (108), or any related entity. In an embodiment, the related entity may include original equipment manufacturers (OEMs) of the UEs (104). In an embodiment, the network issue may be resolved by the recipients of the set of alert signals. In an embodiment, the set of alert signals may include one or more recommendations for resolving the network issue. In an example, the system (108) may recommend the user (102) to update the software version of the UE (104). In an embodiment, the system (108) may be associated with a generative Artificial Intelligence (AI) engine connected to a knowledge base that analyses the correlation values and generates one or more recommendations therefrom.
[0078] In an embodiment, the system (108) may monitor the KPIs based on
the pre-defined performance threshold ranges. In case the KPIs breach the performance threshold ranges, an alert may be transmitted to the user (102) or the operator of the system (108) to identify source of the network issue of failure.
[0079] In an embodiment, alerts are generated based on which the user will
conduct further analysis on the correlated data. The real-time notifications will be sent to the device manufacturer for issue resolution, as well as to the subscribers using those devices to perform upgrades.
[0080] In an embodiment, the user equipment (104) is communicatively
coupled with the system (108). The system (108) may receive a connection request from the UE (104). The system (108) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. The system (108) is configured for

identifying a plurality of network entities associated with a plurality of user equipments causing network issues in the network (106).
[0081] In accordance with embodiments of the present disclosure, the
system (108) may be designed and configured for enriching data with UE attributes for network issue identification and analysis.
[0082] FIG. 2 illustrates a block diagram (200) of the system (108), in
accordance with embodiments of the present disclosure.
[0083] In an aspect, the system (108) may include one or more processor(s)
(202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as Random Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.
[0084] Referring to FIG. 2, the system (108) may include an interface(s)
(206). The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I/O devices, storage devices, and the like. The interface(s) (206) may facilitate communication to/from the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such

components include, but are not limited to, processing unit/engine(s) (208) and a database (210).
[0085] In an embodiment, the processing unit/engine(s) (208) may be
implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) (208) may include a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (208). In such examples, the system (108) may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry.
[0086] In an embodiment, the database (210) includes data that may be
either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engines (208). In an embodiment, the database (210) may be separate from the system (108). In an embodiment, the database (210) may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like.
[0087] In an exemplary embodiment, the processing engine (208) may
include one or more units selected from any of a data acquisition unit (212), a normalizer unit (214), a correlation unit (216), a sending unit (218) and other units

(220) 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.
[0088] In an embodiment, each of the processing engines (208) may be
communicatively coupled to implement the system (108) and method of the present disclosure.
[0089] The data acquisition unit (212) may receive a set of packet code data
generated by a plurality of network entities associated with the plurality of user equipments (104) in the network (106). The set of packets code data is indicative of clear codes or error messages causing network issues or failures. The network entities comprise a subscriber of the user device (104), an OEM (original equipment manufacturer) of the user device and an operator. In an aspect, configuring the data acquisition unit to receive the set of packet code data generated by the plurality of network entities comprises choosing interfaces of the data acquisition unit that match the output ports or protocols of the network entities. The internet protocol (IP) addresses are assigned to the data acquisition unit to establish network connectivity with the network entities. Based on the assigned IP addresses, the data acquisition unit establishes connection with the network entities. Then, the data acquisition unit receives the set of packet code data generated by the network entities. Further, tests may conduct to verify that the data acquisition unit correctly receive and interpret the packet code data from the network entities.
[0090] The normalizer unit (214) may enrich subscriber detail records
(SDRs) in the packet code data by associating the SDRs with the plurality of user equipment attributes. The user device attributes comprise specification attribute, model attribute, manufacturer attribute, configuration attribute, software version attribute, unique identifier attributes, hardware attribute, chipset type attribute, and communication standard attribute. The SDRs comprises subscriber name, subscriber address, unique identifier. The unique identifier comprises mobile

station international subscriber directory number (MSISDN), international mobile equipment identity (IMEI) number, international mobile subscriber identity (IMSI), subscriber permanent identifier (SUPI).
[0091] The correlation unit (216) may determine a correlation value
between each of the plurality of user device attributes and each of clear codes in the packet code data. The correlation unit (216) configured to identify the correlation value beyond a predetermined performance threshold range. Based on identified correlation value, the correlation unit (216) may identify the user device attribute as a source of a network issue.
[0092] The user device (104) is uniquely identified based on a type
allocation code (TAC) associated with the unique identifier attribute of the user device (104) in the SDRs. In an aspect, the user device (e.g., user equipment (UE)) in networks is identified using a type allocation code (TAC), which is part of the international mobile equipment identity (IMEI) number. IMEI is a unique identifier assigned to each mobile device by the manufacturer. IMEI consists of several components, including the type allocation code (TAC). The TAC is first 8 digits of IMEI number. The TAC is used to identify the model and variant of the user device. Further, the network uses the IMEI, including the TAC, to identify and authenticate the user devices connecting to their networks. When the user device attempts to connect to the network, the network uses the IMEI with the TAC to verify the user device's identity and determine if the user device is allowed to access network services based on its TAC and other parameters (such as authentication keys). The TAC is further used for security purposes. The TAC information is used to trace devices in the enforce regulatory compliance or illegal activities, etc.
[0093] The sending unit (218) may send an alert signal to one of the network
entities of the identified user device attribute. The alert signal comprises recommendations to the operator for resolving the network issue, notification to the user to update the software version of the user device or check for the device

settings. This facilitates the user to easily drill down into debugging down to the device level. Additionally, notifying the Original Equipment Manufacturer (OEM) vendor for checking and resolving issues related to the device. Notifications are sent to the customer to check device settings and install the latest updates.
[0094] In an embodiment, the system (108) for identifying the plurality of
network entities associated with the plurality of user equipments (104) causing network issues in the network comprises steps as: the network entities may send subscriber data record (SDR) data to the system (108). The system (108) may enrich the received data based on the policies and stores the enriched data in the database. The data is fetched from the database. The device level details (e.g., Brand, Model, Make, Chipset, Device Type, VoNR, VoWiFi etc.) are stitched with each record of SDR data based on the type allocation code (TAC). The system correlates the device details with the network error codes /clear codes for the subscriber session. Then, the system derives root cause for the given device failure scenarios. The device details are used to view device wise distribution details in the service monitoring reports for clear code analysis. Further, the system monitors device details based on threshold defined values for network level parameters. In case of any breach of the defined threshold value (lower or higher), an alert is generated for the user to check for it whether the breach is related due to failure for specific devices, or it is device independent. In the event of device related network issue, notifications will be sent to OEM Vendor for resolution of the problem as well as the subscriber for installation of latest updates.
[0095] FIG. 3 illustrates an exemplary implementation (300) of the system
(108), in accordance with embodiments of the present disclosure.
[0096] The forthcoming exemplary implementation is described in the
context of correlating UE attributes with SDR data and identifying source of network issue therefrom. In an aspect, the system (108) may include a graphical user interface, such as the monitoring unit (not shown in FIG).

[0097] In an embodiment, the packet code data may be transmitted to the
data acquisition unit (212) by the network entities (110). In an embodiment, the data acquisition unit (212) may validate the packet code data received from the network entities (110). In an embodiment, the data acquisition unit (212) may transmit the SDR data to the normalizer unit (214), which may enrich the SDR data by associating the UE attributes therewith. In an embodiment, the normalizer unit (214) may enrich the data based on one or more policies associated therewith. In an example, the normalizer unit (214) may fetch the data from the data acquisition unit (212) and associate the UE attributes, such as brand, model, make, chipset, device type, VoNR, VoWiFi and the like, for example, with each record based on a Type Allocation Code (TAC). In an embodiment, the normalizer unit (214) may store the enriched data in the database (210).
[0098] In an embodiment, the correlation unit (216) may correlate the UE
attributes with the network error/clear codes in the set of clear codes and identify the source of the network issue or failure. In an example, the correlation unit (216) may identify source of the network error by generating and analyzing distributions of the UEs and clear codes over a selected geographical region. In such examples, if one or more UE attributes correlate with occurrence of one or more clear codes in one or more portions of the geographical region, the system (108) may identify the one or more UE attributes as the source of the network issue. In such examples, if the network (106) observes increased rates of call drops or inaccessibility of Internet from one or more UEs (104) having a common model attribute in the geographical region, the system (108) may associate the network issue with the model of the UE (104) and may transmit the set of alert signals to the OEM of the model. The OEM may upgrade the UE (104) or fix bugs therein to resolve the network issue.
[0099] In an example where the network issue relates to hardware of the UE
(104), the system (108) may send a notification to the OEM vendor for resolution of the hardware issue with the UE (104). In an example where the network issue

relates to the software of the UE (104), the system (108) may send a notification to the UE (104) for installation of latest updates.
[00100] FIG. 4 illustrates a flowchart of a method (400) for identifying a
plurality of network entities associated with a plurality of user equipments causing network issues in the network (106), in accordance with embodiments of the present disclosure.
[00101] At step (402), receiving, by a processor such as the processor (202)
of FIG. 2, a set of packet code data generated by the plurality of network entities. The set of packet code data is indicative of clear codes or error messages causing network issues or failures. The network entities comprise a subscriber of the user equipment (104), an original equipment manufacturer (OEM) of the user equipment, and an operator.
[00102] At step (404), enriching, by the processor, subscriber detail records
(SDRs) in the set of packet code data by associating the SDRs in the set of packet code data with a plurality of user equipment attributes.
[00103] At step (406), determining, by the processor, a correlation value
between each of the plurality of user equipment attributes and each of clear codes in the set of packet code data.
[00104] At step (408), identifying, by the processor, the correlation value
beyond a predetermined performance threshold range.
[00105] At step (410), based on the identified correlation value, identifying,
by the processor, the user equipment attribute as a source of a network issue. The user equipment (104) is identified based on a type allocation code (TAC) associated with a unique identifier of the user equipment in the SDRs.

[00106] At step (412), sending, by the processor, an alert signal to one
network entity of the plurality of network entities corresponding to the identified user equipment attribute.
[00107] FIG. 5 illustrates an exemplary computer system (500) in which or
with which embodiments of the present disclosure may be implemented.
[00108] As shown in FIG. 5, the computer system (500) may include an
external storage device (510), a bus (520), a main memory (530), a read only memory (540), a mass storage device (550), a communication port (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor (570) and communication ports (560). Processor (570) may include various modules associated with embodiments of the present disclosure.
[00109] In an embodiment, the communication port (560) may be any of an
RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port (560) 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 (500) connects.
[00110] In an embodiment, the memory (530) may be Random Access
Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor (570).
[00111] In an embodiment, the mass storage (550) may be any current or
future mass storage solution, which may be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to,

Parallel Advanced Technology Attachment (PATA) or Serial Advanced 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 (e.g., SATA arrays).
[00112] In an embodiment, the bus (520) communicatively couples the
processor(s) (570) with the other memory, storage and communication blocks. The bus (520) may be, e.g., a Peripheral Component Interconnect (PCI)/PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB) or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system (500).
[00113] Optionally, operator and administrative interfaces, e.g., a display,
keyboard, joystick, and a cursor control device, may also be coupled to the bus (520) to support direct operator interaction with the computer system (500). Other operator and administrative interfaces may be provided through network connections connected through the communication port (560). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (500) limit the scope of the present disclosure.
[00114] While considerable emphasis has been placed herein on the preferred
embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the disclosure and not as limitation.

[00115] The present disclosure provides technical advancement related to
device level issues in the network. This advancement addresses the limitations of existing solutions by device level issue correlation for identification of the set of devices leading to the network issues and/or failures. The disclosure involves performing of the device details enrichment in the subscriber data records (SDRs) received from the network elements and generating alert based on which the end user performs issues resolution, which offer significant improvements in identification of which set of devices are contributing to majority of network issues/failures.
ADVANTAGES OF THE PRESENT DISCLOSURE
[00116] The present disclosure provides a system and a method for enriching
data with user equipment attributes.
[00117] The present disclosure provides a system and a method that
correlates user equipment attributes with packet code data collected and stored by the network.
[00118] The present disclosure provides a system and a method that monitors
user equipment-wise distribution of clear code data.
[00119] The present disclosure provides a system and a method that notifies
the user or original equipment manufacturers of faults in the user equipment.
[00120] The present disclosure provides a system and method that provides
a dashboard for analyzing the enriched packet code data.
[00121] The present disclosure provides a system and a method that resolves
the identified network issue(s) to improve subscriber experience.

We Claim:
1. A method (400) for identifying a plurality of network entities associated
with a plurality of user equipments (104) causing network issues in a
network (106), the method (400) comprising:
receiving (402), by a processor, a set of packet code data generated by the plurality of network entities, wherein the set of packet code data is indicative of clear codes or error messages causing network issues or failures;
enriching (404), by the processor, subscriber detail records (SDRs) in the set of packet code data by associating the SDRs in the set of packet code data with a plurality of user equipment attributes;
determining (406), by the processor, a correlation value between each of the plurality of user equipment attributes and each of clear codes in the set of packet code data;
identifying (408), by the processor, the correlation value beyond a predetermined performance threshold range;
based on the identified correlation value, identifying (410), by the processor, the user equipment attribute as a source of a network issue; and
sending (412), by the processor, an alert signal to one network entity of the plurality of network entities corresponding to the identified user equipment attribute.
2. The method (400) as claimed in claim 1, wherein the user equipment (104) is identified based on a type allocation code (TAC) associated with a unique identifier of the user equipment (104) in the SDRs.
3. The method (400) as claimed in claim 1, wherein the plurality of network entities comprises a subscriber of the user equipment (104), an original equipment manufacturer (OEM) of the user equipment, and an operator.

4. The method (400) as claimed in claim 1, wherein the user equipment attributes comprise specification attribute, model attribute, manufacturer attribute, configuration attribute, software version attribute, unique identifier attributes, hardware attribute, chipset type attribute, and communication standard attribute.
5. The method (400) as claimed in claim 1, wherein the SDRs comprises subscriber names, subscriber addresses, unique identifiers, wherein the unique identifiers comprise a mobile station international subscriber directory number (MSISDN), an international mobile equipment identity (IMEI) number, an international mobile subscriber identity (IMSI), a subscriber permanent identifier (SUPI).
6. The method (400) as claimed in claim 1, wherein the alert signal comprises recommendations to the operator for resolving the network issue, notification to the user equipment to update the software version of the user equipment or check for settings of the user equipment.
7. A system (108) for identifying a plurality of network entities associated with a plurality of user equipments (104) causing network issues in a network comprising:
a data acquisition unit (212) configured to receive a set of packet code data generated by the plurality of network entities, wherein the set of packet code data is indicative of clear codes or error messages causing network issues or failures;
a normalizer unit (214) configured to enriching subscriber detail records (SDRs) in the set of packet code data by associating the SDRs in the set of packet code data with a plurality of user equipment attributes;
a correlation unit (216) configured to determine a correlation value between each of the plurality of user equipment attributes and each of clear codes in the set of packet code data;

the correlation unit (216) configured to identify the correlation value beyond a predetermined performance threshold range;
based on the identified correlation value, the correlation unit (216) configured to identify the user equipment attribute as a source of a network issue; and
a sending unit (218) configured to send an alert signal to one network entity of the plurality of network entities corresponding to the identified user equipment attribute.
8. The system (108) as claimed in claim 7, wherein the user equipment (104) is identified based on a type allocation code (TAC) associated with a unique identifier of the user equipment in the SDRs.
9. The system (108) as claimed in claim 7, wherein the plurality of network entities comprises a subscriber of the user equipment, an original equipment manufacturer (OEM) of the user equipment and an operator.
10. The system (108) as claimed in claim 7, wherein the user equipment attributes comprise specification attribute, model attribute, manufacturer attribute, configuration attribute, software version attribute, unique identifier attributes, hardware attribute, chipset type attribute, and communication standard attribute.
11. The system (108) as claimed in claim 7, wherein the SDRs comprises subscriber names, subscriber addresses, unique identifiers, wherein the unique identifiers comprise mobile station international subscriber directory number (MSISDN), international mobile equipment identity (IMEI) number, international mobile subscriber identity (IMSI), subscriber permanent identifier (SUPI).
12. The system (108) as claimed in claim 7, wherein the alert signal comprises recommendations to the operator for resolving the network issue,

notification to the user equipment to update the software version of the user equipment or check for settings of the user equipment.
13. A user equipment (104) communicatively coupled with a system (108), the coupling comprises steps of:
receiving a connection request;
sending an acknowledgment of connection request to the system (108); and
transmitting a plurality of attributes of the user device to the system (108), wherein the system (108) is configured for identifying a plurality of network entities associated with a plurality of user equipments causing network issues in a network (106) as claimed in claim 7.