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 PROCESSOR-IMPLEMENTED METHOD FOR MONITORING SUBSCRIBER SESSION LOGS DATA, AND SCHEDULED REPORT GENERATION
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 processor-implemented method for monitoring subscriber session logs data, and scheduled report generation.
BACKGROUND OF DISCLOSURE
[0003] 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.
[0004] Subscriber session logs data are generated as networks provide services to users, such as voice calls, video calls, messaging, etc. The high volume and velocity of subscriber session logs data make the network service providers difficult to collate and analyze. Particularly, it is difficult to dynamically visualize subset of fields of subscriber log data in real time. Analyzing the data in real time is important for quickly

identifying areas of concern, inefficiencies, bottlenecks, degradation of performance, and track performance trends, among others. Such analysis may help operators to perform preventative maintenance, and horizontally or vertically expand network capabilities.
[0005] Further, operators may wish to have reports of visualizations of subscriber session logs data on a periodical basis. Existing solutions do not provide to periodically execute and generate a report of a predefined data analysis or visualization suite for subscriber session logs data. Additionally, procuring data from the network in real-time and integrating existing dashboards present a significant challenge to the art. [0006] Patent document number US20230216874A1 titled “System and method for real time distributed adaptive cube aggregation, heuristics based hierarchical clustering and anomaly detection framework for high volume streaming datasets” discloses efficient parsing semi-structured deep packet inspection traffic data tied to a telecommunications entity. Another patent document US8239527B2 titled “ System and interface for monitoring information technology assets” discloses an application service provider (ASP)-based interface and system for analyzing performance and costs of respective enterprise information technology assets from the correlation of metrics data of enterprise SNMP-enabled devices. It provides a fully-managed Application Service Provider (ASP)-based system to monitor, alert, analyze and report on the performance and costs of global Information Technology (IT) assets from a single user interface; including application usage, device metrics and Internet Service Provider (ISP) performance across Data, Wireless, Voice over IP (VoIP), Virtual Private Networks (VPN), and Servers (collectively an “IT analytics systems”). [0007] 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.
OBJECTS OF THE PRESENT DISCLOSURE

[0008] Some of the objects of the present disclosure, which at least one embodiment
herein satisfies are as listed herein below.
[0009] A primary object of the embodiments of the present invention is to provide
a system and a method for monitoring subscriber session logs data and scheduled report 5 generation thereof.
[0010] Yet another object of the embodiments of the present invention is to provide
a system and a method that provides a dashboard for monitoring a plurality of
performance metrics.
[0011] Yet another object of the embodiments of the present invention is to provide 10 a system and a method that provides insights on the health and performance of the
network.
[0012] Yet another object of the embodiments of the present invention is to provide
a system and a method that periodically generates and provides reports for network
performance monitoring. 15 [0013] Yet another object of the embodiments of the present invention is to provide
a system and a method for identifying causes for degradation in performance and
perform preventative maintenance of the network.
[0014] Yet another object of the embodiments of the present invention is to provide
a system and a method that streamlines process of monitoring and reporting network 20 performance.
[0015] These and other objectives and advantages of the embodiments of the present
invention will become readily apparent from the following detailed description taken
in conjunction with the accompanying drawings.
25 SUMMARY
[0016] The following details present a simplified summary of the embodiments of
the present invention to provide a basic understanding of the several aspects of the
embodiments of the present invention. This summary is not an extensive overview of
the embodiments of the present invention. It is not intended to identify key/critical
4

elements of the embodiments of the present invention or to delineate the scope of the embodiments of the present invention. Its sole purpose is to present the concepts of the embodiments of the present invention in a simplified form as a prelude to the more detailed description that is presented later. 5 [0017] The other objects and advantages of the embodiments of the present invention will become readily apparent from the following description taken in conjunction with the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many
10 changes and modifications may be made within the scope of the embodiments of the present invention without departing from the spirit thereof, and the embodiments of the present invention include all such modifications.
[0018] The present disclosure discloses a system and a method for scheduled report generation based on subscriber session logs data. The processor-implemented method
15 includes receiving, by a receiving engine, through a user interface (UI), a request to schedule a generation of one or more reports on one or more key performance metrics from subscriber session logs. The method further includes processing, by a scheduler engine, the request to initiate a trigger to generate the one or more reports at the requested schedule. The method further includes processing, by a processor, a set of
20 parameters indicative of fields of subscriber session logs data to obtain the one or more key performance metrics. The method further includes generating, by the processor, the one or more reports based on the key performance metrics. The method further includes communicating, the generated one or more reports to a monitoring unit based on the requested schedule.
25 [0019] In an embodiment, the processor-implemented method includes requesting,
by a workflow engine associated with a load balancer unit requesting to a database for
a data computation. The method includes creating a pattern and communicating the
request along with the pattern to the scheduler engine for scheduling the one or more
reports by the workflow engine.
5

[0020] In an embodiment, the request includes one or more key parameters of the set of parameters indicative of fields of subscriber session logs data for generating the one or more reports.
[0021] In an embodiment, processing the set of parameters includes analyzing, one 5 or more key parameters of the set of parameters to obtain the key performance metrics by the processor.
[0022] In an embodiment, the processor-implemented method includes aggregating the set of parameters of the subscriber session log data for computing one or more composite values by the processor. The method further includes applying the
10 composite values to generate one or more reports based on the key performance metrics by the processor.
[0023] In an embodiment, the processor-implemented method includes allowing the user to provide a plurality of filters for filtering the subscriber session logs data by the one or more fields associated therewith.
15 [0024] In an embodiment, the processor-implemented method includes executing a data visualization suite for generating a set of visualization of the subscriber session logs data defined by the user for periodical monitoring and maintenance. The method further includes computing cell level data and subscriber level data in the subscriber session logs data.
20 [0025] In another embodiment, a system for scheduled report generation based on subscriber session logs data, the system includes a processor to fetch and execute computer-readable instructions stored in a memory of the system. The system includes a memory 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
25 create or share data packets over a network service. The system includes an interface
to provide a communication pathway for one or more components of the system. The
system includes a database comprising data for performing at least one of: storing or
generating a result of functionalities implemented by a plurality of components of at
least one of: the processor or a plurality of processing engines, wherein the processing
6

engine comprises at least one of: a receiving engine, a scheduler engine and a visualization engine. The system includes the receiving engine configured to receive a request via user interface (UI) for scheduling a generation of one or more reports on one or more key performance metrics from subscriber session logs. The system 5 includes the scheduler engine to process the request to initiate a trigger to generate the one or more reports at the requested schedule. The system includes the processor processing a set of parameters indicative of fields of subscriber session logs data to obtain the one or more key performance metrics. The system includes the processor configured to generate the one or more reports based on the key performance metrics.
10 The system includes the processor configured to communicates the generated one or more reports to a monitoring unit based on the requested schedule. The system includes the scheduler engine to initiate a scheduler for periodically triggering generation of the one or more reports. The system includes the visualization engine to retrieve subscriber session log data from the database.
15 [0026] In an embodiment, the system includes a load balancer unit associated with the monitoring unit for managing the first set of signals received from the monitoring unit.
[0027] In an embodiment, the system includes the receiving engine configured to allow a user (304) to provide a plurality of filters for filtering the subscriber session
20 logs data by one or more fields associated therewith.
[0028] In an embodiment, the system includes the first set of signals comprises a set of parameters indicative of fields of subscriber session logs data used for generating reports on one or more key performance metrics. [0029] In an embodiment, the system includes the periodic trigger, which is initiated
25 periodically at predetermined intervals selected by the user via the monitoring unit.
[0030] In an embodiment, the system includes the visualization engine configured
to execute a data visualization suite for generating a set of visualizations of the
subscriber session logs data defined by the user for periodical monitoring and
maintenance.
7

[0031] In an embodiment, the system includes the visualization engine, which is configured to compute composite values derived from one or more fields in the subscriber session logs data.
[0032] In an embodiment, the system includes the visualization engine, which is 5 configured to compute cell-level data and subscriber level in the subscriber session logs data.
[0033] In an embodiment, the system includes the visualization engine configured to periodically transmit the generated one or more reports based on receiving triggers, from the scheduler engine to the monitoring unit.
10 [0034] In another embodiment, a user equipment communicatively coupled to a system, the user equipment includes a processor and a computer readable storage medium storing instruction for execution by the processor. The instructions include receiving, by a receiving engine through a user interface (UI), a request to schedule a generation of one or more reports on one or more key performance metrics from
15 subscriber session logs. The instructions further include processing, by a scheduler engine, the request to initiate a trigger to generate the one or more reports at the requested schedule. The instruction includes processing a set of parameters indicative of fields of subscriber session logs data to obtain the one or more key performance metrics. The instruction includes generating, the one or more reports based on the key
20 performance metrics. The instructions further include communicating, by the processor, the generated one or more reports to a monitoring unit based on the requested schedule.
[0035] In an embodiment, the computer program product includes a non-transitory computer-readable medium comprising instructions that, when executed by one or
25 more processors, cause the one or more processors to perform the set of instructions.
The instructions include receiving, by a receiving engine through a user interface (UI),
a request to schedule a generation of one or more reports on one or more key
performance metrics from subscriber session logs. The instructions further include
processing, by a scheduler engine, the request to initiate a trigger to generate the one
8

or more reports at the requested schedule. The instruction includes processing a set of parameters indicative of fields of subscriber session logs data to obtain the one or more key performance metrics. The instruction includes generating, the one or more reports based on the key performance metrics. The instructions further include communicating, 5 by the processor, the generated one or more reports to a monitoring unit based on the requested schedule.
[0036] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments of the present invention that others can, by 10 applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments.
15 BRIEF DESCRIPTION OF THE DRAWINGS
[0037] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis
20 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
25 components.
[0038] FIG. 1 illustrates an exemplary architecture for monitoring subscriber session logs data and scheduled report generation therefor, according to an embodiment of the present disclosure;
9

[0039] FIG. 2 illustrates a block diagram of the system, according to an embodiment of the present disclosure;
[0040] FIG. 3 illustrates a flow diagram for monitoring subscriber session logs data and scheduled report generation thereof, according to an embodiment of the present 5 disclosure;
[0041] FIG. 4 illustrates a flowchart of a processor-implemented method for monitoring subscriber session logs data, and scheduled report generation, according to an embodiment of the present disclosure; and
[0042] FIG. 5 illustrates an exemplary computer system in which or with which 10 embodiments of the present disclosure may be implemented.
[0043] The foregoing shall be more apparent from the following more detailed description of the disclosure.
LIST OF REFERENCE NUMERALS
15 101- Network Architecture
102-1,102-2…-102-N- Users
104-1,104-2...- 104-N-User equipment
106- Network
108- System 20 110- Monitoring unit
202- Processor(s)
204- Memory
206- Interface(s)
208- Processing Engine(s) 25 210- Database
212- Receiving Engine
214- Visualization Engine
216- Scheduler Engine
218- Other unit(s)
10

304- User
310- User Interface (UI) 370- Load Balancer 330- Workflow 5 340- Platform Scheduler of CRONs (PSC) 350- DFS
510- External storage device 520- Bus
530- Main memory 10 540- Read-only memory 550- Mass storage device 560- Communication Port(s) 570- Processor
15 DETAILED DESCRIPTION OF DISCLOSURE
[0044] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described
20 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.
25 [0045] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be
11

understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth. [0046] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary 5 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
10 obscuring the embodiments.
[0047] 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.
15 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.
20 [0048] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to
25 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.
12

[0049] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases 5 “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. [0050] The terminology used herein is for the purpose of describing particular
10 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,
15 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. [0051] The present disclosure discloses a system and a method for scheduled report
20 generation based on subscriber session logs data. The processor-implemented method includes receiving, by a receiving engine, through a user interface (UI), a request to schedule a generation of one or more reports on one or more key performance metrics from subscriber session logs. The method further includes processing, by a scheduler engine, the request to initiate a trigger to generate the one or more reports at the
25 requested schedule. The method further includes processing, by a processor, a set of parameters indicative of fields of subscriber session logs data to obtain the one or more key performance metrics. The method further includes generating, by the processor, the one or more reports based on the key performance metrics. The method further
13

includes communicating, the generated one or more reports to a monitoring unit based on the requested schedule.
[0052] An aspect of the dashboard creation and scheduling system for performance network monitoring is its ability to automate and streamline the entire process of 5 monitoring and reporting network performance. By providing a centralized platform to create, save, and execute reports, it offers a comprehensive and efficient solution for network administrators. The automated scheduling feature sets this invention apart by eliminating the need for manual report generation. Administrators can set up recurring schedules, such as daily, weekly, or monthly, and the system will generate the reports
10 automatically at the specified intervals. Dashboard ability to send the reports to designated recipients enhances communication and collaboration among stakeholders. It offers a centralized solution that empowers administrators to effectively monitor and analyze network performance, identify issues, and take prompt actions for network optimization. The computation layer computes cell level and subscriber level data. By
15 incorporating the precomputation of subscriber’s data, the invention optimizes the performance and response time of the system, enabling efficient real-time monitoring and analysis of network performance metrics. Dashboard can consolidate data from multiple sources and visualize key metrics in real-time, allowing them to quickly identify areas of concern and track performance trends. The dashboard creation and
20 scheduling system automates the report generation process, saving valuable time for network administrators. Reports can be generated automatically at scheduled intervals, reducing the need for manual intervention. By having regular and automated reports delivered through the dashboard system, administrators can proactively identify performance degradation or potential bottlenecks before they escalate into major
25 issues.
[0053] 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.
14

[0054] The term DFS as used herein, refers to distributed file system (DFS) is data storage and management scheme that enables access to data files from shared storage across any one of multiple networked servers.
[0055] The term UI as used herein, refers to User interface (UI) is used as a point of 5 human-computer interaction and communication in a device.
[0056] The various embodiments throughout the disclosure will be explained in more detail with reference to FIGs. 1-5.
[0057] FIG. 1 illustrates an exemplary architecture 100 for monitoring subscriber session logs data and scheduled report generation therefor, according to an embodiment
10 of the present disclosure. In an aspect, a dashboard for monitoring a plurality of performance metrics and scheduled report generation may be performed by a mobile application.
[0058] 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
15 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
20 collectively referred to as the user equipment 104. A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three user equipments 104 are depicted in FIG. 1, however any number of the user equipments 104 may be included without departing from the scope of the ongoing description.
25 [0059] 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
15

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 5 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
10 aid, a microphone, a keyboard, and input devices for receiving input from the user 102 or the entity such as touch pad, touch enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the user equipment 104 may not be restricted to the mentioned devices and various other devices may be used. The architecture may include a monitoring unit 110 having a user interface that provides
15 audio-visual indications to the user based on a set of signals transmitted by the system 108. In an embodiment, the monitoring unit 110 may be implemented on a user equipment (UE) 104, and/or the system (108).
[0060] In an embodiment, the user equipment 104 may include smart devices operating in a smart environment, for example, an Internet of Things (IoT) system. In
20 such an embodiment, the user equipment 104 may include, but is not limited to, smart phones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system,
25 smart home system, other devices for monitoring or interacting with or for the users 102 and/or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the user equipment 104 may include, but is not limited to, intelligent, multi-sensing, network-connected devices, which can integrate seamlessly
16

with each other and/or with a central server or a cloud-computing system or any other device that is network-connected.
[0061] 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 be a fifth-5 generation (5G) network, a 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
10 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. In an embodiment, each of the UE 104 may have a unique identifier attribute associated therewith. In an embodiment, the unique identifier attribute may be
15 indicative of 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. [0062] In an embodiment, the network 106 may include one or more base stations, which the UEs 104 may connect to and request services from. The base station may be
20 a network infrastructure that provides wireless access to one or more terminals associated therewith. The base station may have coverage defined to be a predetermined geographic area based on the distance over which a signal may be transmitted. The base station may include, but not be limited to, wireless access point, evolved NodeB (eNodeB), 5G node or next generation NodeB (gNB), wireless point,
25 transmission/reception point (TRP), and the like. In an embodiment, the base station
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
17

processors associated thereto, and a plurality of network function units such as 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 5 embodiment, subscriber session logs data may be created when each of the operational units or network functions interact with each other and the UE 104 for providing services.
[0063] In an embodiment, the system 108 may be coupled to a monitoring unit 110 that may provide an interface to the user 102 for monitoring and analysing data. In an
10 embodiment, the monitoring unit 110 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 110 may be configured to provide real-time visualizations of subscriber session logs data provided by the system 108.
15 [0064] In accordance with embodiments of the present disclosure, system 108 may be designed and configured to provide monitoring subscriber session logs data. In an embodiment, the system 108 may also be configured to provide periodical reports on a predefined data visualization suite. [0065] FIG. 2 illustrates a block diagram 200 of the system 108, according to an
20 embodiment of the present disclosure.
[0066] According to embodiment, a system for monitoring subscriber session logs data, and scheduled report generation is provided. The system comprises a processor 202, a memory 204, an interface 206, a database 210, a processing engine(s) 208. The processing engine 208 comprising a receiving engine 212, a scheduler engine 216 and
25 a visualization engine 214. The processor 202 is configured to fetch and execute
computer-readable instructions stored in a memory 204 of the system. The memory
204 is 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 interface 206 is configured
18

to provide a communication pathway for one or more components of the system. A monitoring unit 110 coupled with the system 108. The monitoring unit 110 is configured to provide the first set of signals indicative of a request to periodically generate one or more reports. The database 210 comprises data for performing at least 5 one of storing or generating a result of functionalities implemented by a plurality of components of at least one of the processor 202 or the processing engine 208. The receiving engine 212 is configured to receive the first set of signals indicative of a request to periodically generate one or more reports from the monitoring unit 110. The scheduler engine 216 is configured to initiate a scheduler for periodically triggering 10 generation of the one or more reports. The visualization engine 214 is configured to retrieve subscriber session log data from the database 210.
[0067] 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 15 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-20 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. 25 [0068] 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
19

system 108. Examples of such components include, but are not limited to, processing unit/engine(s) 208 and a database 210.
[0069] In an embodiment, the processing unit/engine(s) 208 may be implemented as a combination of hardware and programming (for example, programmable 5 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
10 engine(s) 208 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) 208. In such examples, the system 108 may include the machine-readable storage medium storing the instructions and the
15 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. [0070] In an embodiment, the database 210 includes data that may be either stored
20 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.
25 [0071] In an exemplary embodiment, the processing engine 208 may include one or
more engines selected from any of the receiving engine 212, the visualization engine
214, the scheduler engine 216, and other engines 218 having functions that may
include, but are not limited to, testing, storage, and peripheral functions, such as
wireless communication unit for remote operation, audio unit for alerts and the like.
20

[0072] In an embodiment, the receiving engine 212 may be configured to receive the first set of signals indicative of a request to schedule a generation of one or more reports on one or more key performance metrics from subscriber session logs. The schedule may be defined by the user. In an embodiment, the first set of signals may 5 include request comprising one or more key performance metrics to be obtained from the set of parameters indicative of fields of subscriber session logs data. In an embodiment, the set of parameters may include, but not be limited to, one or more fields of subscriber session logs data. In an embodiment, the set of parameters may include fields which include, but are not limited to, a device ID, a session duration, an
10 IP address, a location, a network type, a Quality of service (QoS) parameters, and a bandwidth.
[0073] In an embodiment, the key performance metrics is a measurement of the some of the key parameters. The key performance metrics may be used to analyze and improve the network performance. In an embodiment, the one or more key parameters
15 may include one or more parameters from the set of parameters defined/selected by the user (for example, through filters). In an example, the one or more key parameters may include a session duration, a session count, a data usage, a session setup time and a session termination time. [0074] In another example, the one or more key parameters may include a session
20 success rate, a session drop rate, a connection speed and a QoS metrics.
[0075] In an embodiment, the one or more key performance metrics may indicate the health and performance of the network and identify issues or bottlenecks causing degradations in performance. In an embodiment, the monitoring unit 110 may be operated by the user 102 or an operator. In an embodiment, the monitoring units 110
25 may request visualizations of data from the system 108. In an embodiment, the
receiving engine 212 may allow users 102 to provide a plurality of filters for filtering
the subscriber session logs data by one or more fields associated therewith.
[0076] In an embodiment, the scheduler engine 216 may initiate a scheduler for
periodically triggering generation of the one or more reports. In an embodiment, the
21

trigger may be initiated by an external scheduler unit. In other embodiments, the trigger may be self-generated using an internal timer. In an embodiment, the trigger may be initiated periodically in predetermined intervals. In an embodiment, the predetermined interval may be specified by the users 102 of the system 108. In an embodiment, the 5 predetermined interval may be selected by the user 102 using the interface of the monitoring unit 110. The predetermined interval may be daily, weekly, or monthly, but not limited thereto. In some examples, the trigger may be initiated on demand by the user. In an embodiment, the scheduler engine 216 may self-generate the triggers by using command line utilities such as pattern, but not limited thereto. For example, the
10 pattern may be a CRON pattern. The CRON pattern may be a command expression used for triggering the scheduler engine 216 for generating one or more reports. The CRON pattern may describe the individual details of the schedule. The expression in CRON pattern may be one or more combination of numbers, letters, words, special characters. For example, the CRON pattern may be “0 0 12 * * ?” which triggers the
15 scheduling engine 216 to perform an activity at 12 PM every day.
[0077] In an embodiment, the visualization engine 214 may retrieve the subscriber session log data from the database 210. In an embodiment, the database 210 may be a distributed file sharing unit having the subscriber session log data. The visualization engine 214 may generate the one or more reports based on the subscriber session log
20 data retrieved from the database 210. In an embodiment, generating the one or more reports may include the one or more visualizations of the subscriber session data. In an embodiment, the visualization engine 214 may execute a data visualization suite for generating a set of visualization of the subscriber session data. The visualization may be defined by the user 102. The visualization may provide the user with an
25 understanding of issues in the network that can be helpful in periodical monitoring and
maintenance. In an embodiment, the visualization engine 214 may be configured to
compute composite values derived from one or more fields in the subscriber session
logs data. In an example, the fields may contain network parameters such as an IP
address, a port number, a host ID, etc. The composite values may be combination of
22

values from the one or more fields. For example, the composite values have merged data of the fields such as IP address and port number, merged as single data. In an embodiment, the visualization engine 214 may be configured to compute a cell level data and a subscriber level data in the subscriber session logs data. In an example, the 5 cell level data include the user 102 connected base station information such as a Cell ID, a location, a frequency and a coverage. The subscriber level data may include a name, a device ID, a device number to identify desired user’s subscriber session logs data. In an embodiment, the visualization engine 214 may be configured to suitably modify portions of the reports when users 102 cause a change in the set of parameters.
10 [0078] The visualization engine 214, via the scheduler or the scheduler engine 216, may periodically transmit the generated reports to the monitoring unit 110. In an embodiment, the visualization engine 214 may generate and transmit the reports on receiving triggers from the scheduler engine 216. In an embodiment, the generated reports may be transmitted via telecommunication channels, including, but not limited
15 to, via e-mails, notifications, or publications in websites, dedicated dashboards, and the like.
[0079] In an embodiment, a load balancer 370 unit is associated with monitoring unit 110 for managing the first set of signals received from the monitoring unit 110. [0080] FIG. 3 illustrates a flow diagram 300 for monitoring subscriber session logs
20 data and scheduled report generation thereof, according to an embodiment of the present disclosure.
[0081] At step 306, the method 300 includes scheduling reports by the user 304 on UI 310. In an aspect, scheduling is a process of assigning resources to perform a specific task based on the user input.
25 [0082] At step 308, the load balancer unit 370 receives the request for generating of
one or more report from a UI 310. In an aspect, the load balancer unit 370 distributes
the network traffic among the available resources. In an aspect, the load balancer unit
370 receives the request for task from the user via the UI 310.
[0083] At step 312, the load balancer unit 370 checks for the available instance with
23

the workflow engine 330 for serving the user request. For example, the load balancer unit 370 checks for the available instance by determining a status of the workflow engine 330 for serving the user. The status may include work-in-progress, queued and available. The workflow engine 330 receives the requests from the UI 310 via the load 5 balancer unit 370 for a report generation. The workflow engine 330 initiates the request for the report generation. In an exemplary aspect, the workflow engine initiates the report generation for the specific date range provided in the request. For example, the specific date range may be 14th July 2023 to 15th July 2023. [0084] At step 314, the workflow engine 330 requests a distributed file system
10 (DFS) 350 for the data for a pattern creation of one or more reports based on the request. For example, the pattern may be a CRON pattern. In an exemplary aspect, the data may be subscriber log data of the user stored in the DFS 350.
[0085] At step 316, the workflow engine 330 creates the pattern and forwards the request to platform scheduler of CRONs (PSC) 340 which schedules the report. For
15 example, the pattern may be a CRON pattern. The CRON pattern may be a command expression used for intimating the user triggering to the PSC 340 for generating one or more reports. The CRON pattern may describe the individual details of the schedule. The expression in CRON pattern may be one or more combination of numbers, letters, words, special characters. For example, the CRON pattern may be “0 0 12 * * ?” which
20 triggers the PSC to perform an activity at 12 PM every day. In an aspect, the platform scheduler of CRONs (PSC) may be a micro-service that is used for intimation of user trigger for generating report.
[0086] At step 318, the PSC 340 sends an acknowledgement the UI 310 for that the task has been created. In an example, the PSC 340 sends the acknowledgement that the
25 CRON pattern has been created for scheduling the report.
[0087] At step 320, the DFS 350 sends the requested data required for generation of
the one or more reports along with the acknowledgment to the workflow engine 330.
In an example, the distribution file system (DFS) 350 sends data for report generation
to the workflow engine 330. The data may be a subscriber log data of the user stored
24

in the DFS 350.
[0088] At step 322, the workflow engine 330 shows the report on UI 310 based on the subscriber log data received from the DFS 350. In an example, the workflow engine 330 shows the generated report based on the subscriber log data received from the DFS 5 350.
[0089] FIG. 4 illustrates a flowchart 400 of a processor-implemented method for monitoring subscriber session logs data, and scheduled report generation, according to an embodiment of the present disclosure. [0090] At step 402, a receiving engine 212 may receive a request to schedule a
10 generation of one or more reports. The reports are generated based on one or more key performance metrics from subscriber session logs.
[0091] At step 404, a schedular engine 216 may process the received requested schedule for generating one or more reports. The schedular engine may initiate a trigger to generate the one or more reports. In an example, the request scheduling can be
15 triggered at a time interval by the user. The time interval can be hourly, weekly and monthly.
[0092] At step 406, a processor 202 may process a set of parameters indicative of fields of subscriber session logs data to obtain the one or more key performance metrics for generating the one or more reports. The reports are generated based on the key
20 performance metrics. In an embodiment, the set of parameters may include, but not limited to, a device ID, a session duration, an IP address, a location, a network type, a Quality of service (QoS) parameters and a bandwidth.
[0093] At step 408, the processor 202 may generate the one or more reports based on the key performance metrics. In an exemplary aspect, the key performance metrics
25 is a measurement of the some of the key parameters. The key performance metrics may be used to analyze and improve the network performance. In an embodiment, the key parameters may include a session duration, a session count, a data usage, a session setup time and a session termination time.
25

[0094] In another example, the key parameters may include a session success rate, a session drop rate, a connection speed and a quality of service (QoS) metrics. [0095] At step 410, the processor 202 may communicates with a monitoring unit 110 that the one or more reports has been generated based on the requested schedule. 5 In an example, the processor 202 communicates the generated reports to the monitoring unit 110. The generated reports may have the key performance metrics of the network based on the request.
[0096] In an embodiment, the processor may process one or more composite values from one or more fields in the subscriber session logs data by the processor. In an
10 aspect, the processor may compute the composite values based on the subscriber session log data. The subscriber session log data may have one or more fields. For example, the fields may contain network parameters such as an IP address, a port number, a host ID, etc. The composite values may be a combination of values from one or more fields. The composite values are merged data of the fields such IP address
15 and port number as single data.
[0097] In an embodiment, the first set of signals comprises a set of parameters indicative of fields of subscriber session logs data for generating the one or more reports. In an embodiment, the set of parameters may include a device ID, a session duration, an IP address, a location, a network type, a Quality of service (QoS)
20 parameters and a bandwidth.
[0098] In an embodiment, the method further includes allowing the user to provide a plurality of filters for filtering the subscriber session logs data by one or more fields associated therewith. In an example, the plurality of filters may include a network parameter and a connectivity parameter. The network parameter may include a latency,
25 a data traffic and a signal quality filtering the subscriber session logs. The connectivity parameter may include a wired and a wireless connection for filtering the subscriber session logs.
26

[0099] In an embodiment, retrieving further comprises executing a data visualization suite for generating a set of visualization of the subscriber session logs data as requested by the user for periodical monitoring and maintenance. [00100] FIG. 5 illustrates an exemplary computer system 500 in which or with which 5 embodiments of the present disclosure may be implemented. 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
10 ports 560. Processor 570 may include various modules associated with embodiments of the present disclosure, such as one or more engines selected from any of a receiving engine 212, a visualization engine 214, a scheduler engine 216, and other engines 218. [00101] 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
15 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. [00102] In an embodiment, the memory 530 may be Random Access Memory
20 (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. [00103] In an embodiment, the mass storage 550 may be any current or future mass
25 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
27

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). [00104] 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, 5 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. [00105] Optionally, operator and administrative interfaces, e.g., a display, keyboard,
10 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
15 computer system 500 limit the scope of the present disclosure.
[00106] The various embodiments of the present disclosure provide a system and a method for monitoring subscriber session logs data and scheduled report therefor. The present disclosure provides a system and a method that provides a dashboard for monitoring a plurality of performance metrics. The present disclosure provides a
20 system and a method that provides insights on the health and performance of the network. The present disclosure provides a system and a method that provides periodically generates and provides reports for network performance monitoring. The present disclosure provides a system and a method for identifying causes for degradation in performance and perform preventative maintenance of the network. The
25 present disclosure provides a system and a method that streamlines process of
monitoring and reporting network performance. The system provides a centralized and
visual representation of network performance metrics, allowing administrators to have
a comprehensive view of their network infrastructure. Automating the report
generation process saves significant time and effort for network administrators. With
28

the insights gained from the reports, administrators can identify areas of improvement and optimize network performance. The system enables the sharing of reports with designated recipients, promoting better communication and collaboration among teams. 5 [00107] The present disclosure provides technical advancement related to scheduled report generation based on subscriber session logs data in a communication network. This advancement addresses the limitations of existing solutions by automating the report generation process by saving the time of a network administrator. The disclosure automates and streamlines the process of monitoring and reporting network
10 performance by providing a centralized platform to create, save, and execute reports. The disclosure offers a comprehensive and efficient solution for network administrators. By implementing scheduled report generation based on the subscriber session log data, the disclosed invention enhances automatic report generation at scheduled intervals, resulting in providing a comprehensive view of their network
15 infrastructure to the network administrator.
[00108] 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 technology. These and other changes in the preferred embodiments of
20 the technology will be apparent to those skilled in the art from the technology herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the technology and not as limitation.
ADVANTAGES OF THE PRESENT DISCLOSURE
25 [00109] The present disclosure provides a system and method for centralized
and visual representation of network performance metrics, allowing administrators to
have a comprehensive view of their network infrastructure.
[00110] The present disclosure enables automating the report generation process
that saves significant time and effort for a network administrator.
29

[00111] The present disclosure facilitates the network administrator by
providing various insights through reports to improve and optimize the network performance.
[00112] The present disclosure enables sharing of reports with the designated
5 recipient promoting better communication and collaboration among the administrators.
30

WE CLAIM:
5 1. A processor-implemented method for scheduled report generation based on
subscriber session logs data, the method comprising:
receiving (404), by a receiving engine (212) through a user interface (UI) (310),
a request to schedule a generation of one or more reports on one or more key
performance metrics from subscriber session logs;
10 processing, by a scheduler engine (216), the request to initiate a trigger to
generate the one or more reports at the requested schedule;
processing (410), by a processor (202), a set of parameters indicative of fields of subscriber session logs data to obtain the one or more key performance metrics;
generating, by the processor (202), the one or more reports based on the key 15 performance metrics; and
communicating (414), by the processor (202), the generated one or more reports to a monitoring unit (110) based on the requested schedule.
2. The processor-implemented method as claimed in claim 1, the method
comprising:
20 requesting, by a workflow engine (330) associated with a load balancer (370)
unit, to the database (210), for a data computation; and
creating, by the workflow engine (330), a pattern and communicating the request along with the pattern to the scheduler engine (216) for scheduling the one or more reports.
25 3. The processor-implemented method as claimed in claim 1, wherein the request
comprises one or more key parameters of the set of parameters indicative of fields of subscriber session logs data for generating the one or more reports.
31

4. The processor-implemented method as claimed in claim 3, wherein the
processing the set of parameters comprising:
analyzing, by the processor(s) (202), one or more key parameters of the set of parameters in the subscriber session log data to obtain the key performance metrics.
5 5. The processor-implemented method as claimed in claim 1, the method
comprising:
aggregating, by the processor(s) (202), the set of parameters of the subscriber session log data for computing one or more composite values; and
applying, by the processor(s) (202), the composite values to generate one or 10 more reports based on the key performance metrics.
6. The processor-implemented method as claimed in claim 1, the method
comprising:
providing the user (304) to a plurality of filters for filtering the subscriber session logs data by the one or more fields associated therewith. 15
7. The processor-implemented method as claimed in claim 5, wherein the
retrieving comprises:
executing a data visualization suite for generating a set of visualization of the subscriber session logs data defined by the user (304) for periodical monitoring and 20 maintenance; and
computing cell level data and subscriber level data in the subscriber session logs data.
8. A system (108) for scheduled report generation based on subscriber session logs
25 data, the system comprising:
a processor (202) to fetch and execute computer-readable instructions stored in a memory (204) of the system;
32

the memory (204) 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;
a database (210) comprising data for performing at least one of: storing or
5 generating a result of functionalities implemented by a plurality of components of at
least one of: the processor (202) or a plurality of processing engines (208), wherein the
plurality of processing engines (208) comprises at least one of: a receiving engine
(212), and a scheduler engine (216);
the receiving engine (212), to receive a request via user interface (UI) (310) 10 for scheduling a generation of one or more reports on one or more key performance metrics from subscriber session logs;
the scheduler engine (216) configured to process the request to initiate a trigger
to generate the one or more reports at the requested schedule; and
the processor (202) configured to:
15 process a set of parameters indicative of fields of subscriber session logs
data to obtain the one or more key performance metrics;
generate the one or more reports based on the key performance metrics; and
communicate the generated one or more reports to a monitoring unit
20 (110) based on the requested schedule.
9. The system (108) as claimed in claim 8, the system (108) comprising a load
balancer (370) unit associated with the monitoring unit (110) for managing the first set
of signals received from the monitoring unit (110).
10. The system (108) as claimed in claim 8, wherein the receiving engine (212)
25 allows a user (304) to provide a plurality of filters for filtering the subscriber session
logs data by one or more fields associated therewith.
33

11. The system (108) as claimed in claim 8, wherein the first set of signals
comprises a set of parameters indicative of fields of subscriber session logs data used
for generating reports on one or more key performance metrics.
12. The system (108) as claimed in claim 8, wherein the periodic trigger is initiated
5 periodically in predetermined intervals selected by the user via the monitoring unit
(110).
13. The system (108) as claimed in claim 8, further comprising the visualization
engine (214) configured to execute a data visualization suite for generating a set of
visualizations of the subscriber session logs data as defined by the user (304) for
10 periodical monitoring and maintenance.
14. The system (108) as claimed in claim 13, wherein the visualization engine (214)
is configured to compute composite values derived from one or more fields in the
subscriber session logs data.
15. The system (108) as claimed in claim 13, wherein the visualization engine (214)
15 is configured to compute cell-level data and subscriber level in the subscriber session
logs data.
16. The system (108) as claimed in claim 13, wherein the visualization engine (214)
is configured to periodically transmit the generated one or more reports based on
receiving triggers, from the scheduler engine (216) to the monitoring unit (110).
20 17. A user equipment (104) communicatively coupled to a system (108), the user equipment comprising:
a processor; and
a computer readable storage medium storing instruction for execution by the processor, wherein the instructions comprising:
34

receiving, through a user interface (UI) (310), a request to schedule a generation of one or more reports on one or more key performance metrics from subscriber session logs;
processing, the request to initiate a trigger to generate the one or more reports 5 at the requested schedule;
processing, a set of parameters indicative of fields of subscriber session logs data to obtain the one or more key performance metrics;
generating, the one or more reports based on the key performance metrics; and
communicating, the generated one or more reports to a monitoring unit (110) 10 based on the requested schedule.