FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR GENERATING A TARGET
FILTERED DATA”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR GENERATING A TARGET FILTERED
DATA
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to information technology. More particularly, embodiments of the present disclosure relate to method and system for generating a target filtered data.
BACKGROUND
[0002] The following description of the 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 is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] In existing solutions, the process of filtering and retrieving data based on a specific criteria is often cumbersome and inflexible. Traditional systems typically hard-code filter keys and their corresponding configurations directly into the software. This approach has several significant drawbacks. Firstly, it requires extensive development efforts to introduce or modify filter keys for different business contexts such as accounts, products, services, and other entities. Each new requirement necessitates changes in the codebase, leading to longer development cycles and increased risk of introducing errors. Moreover, as businesses evolve and new entities or filtering needs arise, the necessity to continually update the software becomes a substantial burden, consuming valuable resources and time.
[0004] Furthermore, in these traditional systems, any change in the filter key configurations typically demands a system restart to take effect. This process can

disrupt service availability, leading to downtime and potential loss of business continuity. The lack of a dynamic and flexible approach to manage filter key configurations means that businesses cannot quickly adapt to changing requirements or efficiently handle complex filtering scenarios. This limits the system's ability to provide precise and relevant data to meet diverse business needs, thereby hindering overall operational efficiency and responsiveness.
[0005] Thus, there exists an imperative need in the art to provide a method and system for generating a target filtered data, which the present disclosure aims to address.
SUMMARY
[0006] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0007] An aspect of the present disclosure may relate to a method for generating a target filtered data. The method includes receiving, by a transceiver unit, a retrieve data request, wherein the retrieve data request comprises at least a request filter key. Next, the method includes retrieving, by a retrieval unit from a cache memory, a target filter key configuration from a set of predefined filter key configurations based on the request filter key. Thereafter, the method includes generating, by a filtered data generator unit, the target filtered data associated with the request filter key based on the retrieving the target filter key configuration from the set of predefined filter key configurations.
[0008] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the transceiver unit, the set of predefined filter key configurations; receiving, by the transceiver unit via an interface, an update filter

key configuration request. Further, the method comprises identifying, by an analysis unit, one or more target predefined filter key configuration from the set of predefined filter key configurations based on the update filter key configuration request. Further, the method includes generating, by the analysis unit, a set of updated filter key configurations based on the one or more target predefined filter key configuration and finally storing, by the analysis unit in the cache memory, the set of updated filter key configurations generated based on the one or more target predefined filter key configuration.
[0009] In an exemplary aspect of the present disclosure, each filter key configuration from the set of predefined filter key configurations comprises a set of filter key parameters.
[0010] In an exemplary aspect of the present disclosure, the update filter key configuration request comprises a request for updating at least one filter key parameter from the set of filter key parameters associated with at least one predefined filter key configurations from the set of predefined filter key configurations.
[0011] In an exemplary aspect of the present disclosure, each updated filter key configuration from the set of updated filter key configurations comprises at least one updated filter key parameter based on the updated filter key configuration request.
[0012] Another aspect of the present disclosure may relate to a system for generating a target filtered data. The system comprises a transceiver unit configured to receive a retrieve data request, wherein the retrieve data request comprises at least a request filter key. The system further comprises a retrieval unit connected to at least the transceiver unit, the retrieval unit is configured to retrieve from a cache memory, a target filter key configuration from a set of predefined filter key configurations based on the request filter key. The system further comprises a

filtered data generator unit connected to at least the retrieval unit, the filtered data generator unit is configured to generate the target filtered data associated with the request filter key based on the retrieving of the target filter key configuration from the set of predefined filter key configurations.
[0013] Yet another aspect of the present disclosure may relate to a User Equipment (UE). The UE may include a memory and a processor coupled to the memory. The processor may be configured to transmit a retrieve data request comprising at least a request filter key to a system. The retrieve data request is used by the system for generating a target filtered data based on: receiving the retrieve data request, retrieving a target filter key configuration from a set of predefined filter key configurations based on the request filter key and generating the target filtered data associated with the request filter key based on the retrieving the target filter key configuration from the set of predefined filter key configurations.
[0014] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing one or more instructions for generating a target filtered data, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit of the system to receive a retrieve data request, wherein the retrieve data request comprises at least a request filter key. Further, the executable code which, when executed by the one or more units of the system, causes a retrieval unit of the system to retrieve from a cache memory of the system, a target filter key configuration from a set of predefined filter key configurations based on the request filter key. Furthermore, the executable code which, when executed by the one or more units of the system, causes a filtered data generator unit of the system to generate the target filtered data associated with the request filter key based on the retrieval of the target filter key configuration from the set of predefined filter key configurations.
OBJECTS OF THE INVENTION

[0015] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0016] It is an object of the present disclosure to provide a system and a method for generating a target filtered data.
[0017] It is another object of the present disclosure to provide a system and a method for generating query data through target filter key mechanism.
[0018] It is yet another object of the present disclosure to provide a system and a method for developing a framework for filter key, which claims zero development task in future even for most complicated scenarios.
DESCRIPTION OF THE DRAWINGS
[0019] 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. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0020] FIG. 1 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.

[0021] FIG. 2 illustrates an exemplary block diagram of a system for generating a target filtered data, in accordance with exemplary implementations of the present disclosure.
[0022] FIG. 3 illustrates an exemplary method flow diagram indicating the process for generating a target filtered data, in accordance with exemplary implementations of the present disclosure.
[0023] FIG. 4, an exemplary block diagram of a system [400] architecture for generating a target filtered data, is shown, in accordance with the exemplary implementations of the present disclosure.
[0024] FIG. 5 depicts an exemplary process flow diagram, for generating a target filtered data, in accordance with exemplary implementations of the present disclosure.
[0025] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0026] 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 may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.

[0027] 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. 5 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.
[0028] Specific details are given in the following description to provide a thorough 10 understanding of the embodiments. However, it will be understood by one of ordinary skills in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. 15
[0029] 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 may be performed in parallel or 20 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.
[0030] The word “exemplary” and/or “demonstrative” is used herein to mean 25 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 30 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
8

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.
5 [0031] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital
10 Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding, data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or
15 processing unit is a hardware processor.
[0032] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a
20 communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable
25 of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
30 [0033] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a
9

form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data 5 that may be required by one or more units of the system to perform their respective functions.
[0034] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information 10 or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
15 [0035] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller,
20 Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0036] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, 25 information, or a combination thereof between units/components within the system and/or connected with the system.
[0037] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-30 mentioned and other existing problems in this field of technology by providing a method and system for generating a target filtered data.
10

[0038] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by developing a framework for filter key, that claims Zero development task in future even for most complicated 5 scenarios. For e.g., if earlier, address was to be returned in customer for filter key input – “Address” and now business wants only shipping address within address array, DIF has configurations for it through xpath as shown below.
[0039] Hereinafter, exemplary embodiments of the present disclosure will be 10 described with reference to the accompanying drawings.
[0040] FIG. 1 illustrates an exemplary block diagram of a computing device [100] (also referred herein as a computer system [100]) upon which the features of the present disclosure may be implemented in accordance with exemplary
15 implementation of the present disclosure. In an implementation, the computing device [100] may also implement a method for generating a target filtered data utilising the system. In another implementation, the computing device [100] itself implements the method for generating a target filtered data using one or more units configured within the computing device [100], wherein said one or more units are
20 capable of implementing the features as disclosed in the present disclosure.
[0041] The computing device [100] may include a bus [102] or other communication mechanism for communicating information, and a processor [104] coupled with bus [102] for processing information. The processor [104] may be, for
25 example, a general-purpose microprocessor. The computing device [100] may also include a main memory [106], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [102] for storing information and instructions to be executed by the processor [104]. The main memory [106] also may be used for storing temporary variables or other intermediate information
30 during execution of the instructions to be executed by the processor [104]. Such instructions, when stored in non-transitory storage media accessible to the processor
11

[104], render the computing device [100] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [100] further includes a read only memory (ROM) [108] or other static storage device coupled to the bus [102] for storing static information and 5 instructions for the processor [104].
[0042] A storage device [110], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [102] for storing information and instructions. The computing device [100] may be coupled via the bus [102] to a
10 display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [114], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [102] for communicating information and command selections to the processor
15 [104]. Another type of user input device may be a cursor controller [116], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [104], and for controlling cursor movement on the display [112]. The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
20 the device to specify positions in a plane.
[0043] The computing device [100] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [100] causes
25 or programs the computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [100] in response to the processor [104] executing one or more sequences of one or more instructions contained in the main memory [106]. Such instructions may be read into the main memory [106] from another storage medium,
30 such as the storage device [110]. Execution of the sequences of instructions contained in the main memory [106] causes the processor [104] to perform the
12

process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
5 [0044] The computing device [100] also may include a communication interface [118] coupled to the bus [102]. The communication interface [118] provides a two-way data communication coupling to a network link [120] that is connected to a local network [122]. For example, the communication interface [118] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
10 a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [118] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [118] sends and receives electrical,
15 electromagnetic or optical signals that carry digital data streams representing various types of information.
[0045] The computing device [100] can send messages and receive data, including program code, through the network(s), the network link [120] and the
20 communication interface [118]. In the Internet example, a server [130] might transmit a requested code for an application program through the Internet [128], the ISP [126], the local network [122], the host [124] and the communication interface [118]. The received code may be executed by the processor [104] as it is received, and/or stored in the storage device [110], or other non-volatile storage for later
25 execution.
[0046] The computing device [100] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device [100] include, but are not limited only to, personal computers, 30 laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks
13

such as data storage, retrieval, and analysis. Additionally, computing device [100] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications. 5
[0047] Referring to FIG. 2, an exemplary block diagram of a system [200] for generating a target filtered data, is shown, in accordance with the exemplary implementations of the present disclosure. As depicted in FIG. 2, the system [200] may include at least one transceiver unit [202], at least one retrieval unit [204], at
10 least one filtered data generator unit [206], at least one analysis unit [208] and at least one cache memory [210]. Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 2 only a few units are shown, however,
15 the system [200] may comprise multiple such units or the system [200] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
[0048] The system [200] is configured for generating a target filtered data, with the 20 help of the interconnection between the components/units of the system [200].
[0049] In one example, in operation, the transceiver unit [202] may receive a retrieve data request. The retrieve data request may be associated with such as, but not limited to, service enquiry, plan offering, product details and the like. Further, 25 the retrieve data request may include at least a request filter key. The request filter key may be associated with the retrieve data request. In an exemplary aspect, the request filter key may comprise such as, but not limited to, address, account, plan, product, service and the like.
30 [0050] For example, when a user or an application needs specific customer data, they send a retrieve data request to the system. This request includes a request filter
14

key, such as "Address" or "Product," indicating the specific subset of data required. The transceiver unit [202] captures this request and processes the request filter key to ensure that only the relevant data is retrieved and returned.
5 [0051] Thereafter, the retrieval unit [204], connected to at least the transceiver unit [202], may retrieve, from the cache memory [210], a target filter key configuration from a set of predefined filter key configurations based on the request filter key. For example, when the transceiver unit [202] receives a data request with the filter key "Address," the retrieval unit [204] is tasked with identifying and retrieving the
10 corresponding filter key configuration from the cache memory [210]. The configuration outlines the specific parameters and rules for filtering and formatting the requested data. The cache memory [210] stores the predefined configurations to enable quick and efficient access, reducing the need for time-consuming database queries or processing.
15
[0052] The system [200] further comprises the filtered data generator unit [206], connected to at least the retrieval unit [204], to generate the target filtered data associated with the request filter key based on the retrieving of the target filter key configuration from the set of predefined filter key configurations. For example,
20 after the retrieval unit [204] has fetched the filter key configuration for "Address" from the cache memory [210], the filtered data generator unit [206] uses this configuration to filter the customer data accordingly. Suppose the customer data includes various attributes such as account details, product purchases, service information, and addresses. The filter key configuration will specify that only the
25 address-related information is to be included in the final output. The filtered data generator unit [206] processes the raw data, extracts the necessary address information as per the configuration, and compiles it into a coherent JSON object to be returned as the response.
30 [0053] The transceiver unit [202] is further configured to receive the set of predefined filter key configurations, and receive, via an interface, an update filter
15

key configuration request. For example, the initial setup of the system includes a predefined set of filter key configurations stored in the cache memory [210]. These configurations might specify how to filter data for various entities such as "Account," "Product," and "Service." The transceiver unit [202] can receive these 5 configurations from a central repository or an administrative interface and load them into the cache memory for immediate use by the retrieval and filtered data generator units. In another example, if pre-defined filter key configurations expose account data or customer personal details such as but not limited to organization name, customer name, mobile, email etc. then the application programming
10 interface (API) has to accept a newly introduced parameter such as RESOURCE and display details related to resource only. This newly introduces parameter would be updated in configuration. Furthermore, post updating this parameter and dynamically adding the updated filter key configuration request in command line interface (CLI), the system [200] would return resource details based on the
15 requested API details that the filter key – RESOURCE has been received.
[0054] Exemplarily, when business requirements evolve, and there is a need to modify or add new filter keys, the transceiver unit [202] facilitates this process through an interface. Suppose the business decides that the existing "Address" filter 20 key now needs to include a more specific sub-filter for "Shipping Address." An administrator can send an update filter key configuration request via the interface. The transceiver unit [202] receives this request and communicates it to the analysis unit [208].
25 [0055] The analysis unit [208] is further configured to identify target predefined filter key configurations from the set of predefined filter key configurations based on the update filter key configuration request, generate a set of updated filter key configurations based on the one or more target predefined filter key configuration, and store, in the cache memory [210], the set of updated filter key configurations
30 generated based on the one or more target predefined filter key configuration. For example, suppose the current predefined filter key configuration includes filter keys
16

such as "Account," "Product," and "Service." An update request is received to modify the "Product" filter key to include additional attributes like "Product Availability" and "Product Warranty." Upon receiving this update request via the transceiver unit [202], the analysis unit [208] identifies the existing "Product" filter 5 key configuration from the set of predefined configurations. Once the target configuration is identified, the analysis unit [208] generates a new set of filter key configurations that incorporate the requested updates. This might involve adding new XPath expressions or JSON paths that define how to extract the "Product Availability" and "Product Warranty" information from the data source. The
10 updated configuration is then constructed to reflect these changes accurately. After generating the updated filter key configurations, the analysis unit [208] stores these new configurations in the cache memory [210]. It would be appreciated by the person skilled in the art that by storing the updated configurations in the cache, subsequent data retrieval requests using the "Product" filter key will now include
15 the additional attributes specified in the update request. The immediate reflection of changes without the need for a system restart significantly enhances the system's flexibility and responsiveness. In one example, when configurations are ready and identifiable from cache memory [210] or database, and a particular configured filter key is received by the system [200], the system [200] identifies the particular
20 configuration from cache memory [210] to look-up filter key from available configurations. The particular configuration is identified based on the API name (event name) and data entity. The data entity may include data such as but not limited to customer data, product catalogue data or reference data. Now, that the system [200] has deduced particular configuration from set of available
25 configurations, it will find the views to return. The views herein refer to Xpath of the elements within stored data JSON to return.
[0056] For instance, if a business needs to comply with new regulatory
requirements that mandate the inclusion of "Customer Consent Status" in the data
30 returned for the "Customer" filter key, the analysis unit [208] can quickly update
the relevant configurations. The new configuration specifying how to extract and
17

include "Customer Consent Status" will be generated and stored in the cache memory [210], ensuring that all future data retrievals adhere to the new compliance requirements.
5 [0057] In an exemplary embodiment, each filter key configuration from the set of predefined filter key configurations comprises a set of filter key parameters. For example, for a filter key configuration for "Customer." The configuration might include parameters such as "Name," "Address," "Account Details," and "Purchase History." Each parameter specifies the specific data elements to be included when
10 the "Customer" filter key is used. If a request is made with the filter key "Customer," the system will use this configuration to retrieve and return data that includes the customer's name, address, account details, and purchase history, but exclude other unrelated information. The set of filter key parameters are the “phrases” with which, list of views to return the response are mapped in configuration. For example, if the
15 phrase is ACCOUNT, the filter key configuration receives the phrase ACCOUNT and returns only the account details. The account details are identified by XPath notations. As used herein, XPath is a hierarchical term that every parameter in the JSON data stores. The XPath of account details to return may be identified by code and only those parameter values may be returned in the response.
20
[0058] In an exemplary embodiment, the update filter key configuration request comprises a request for updating at least one filter key parameter from the set of filter key parameters associated with at least one predefined filter key configuration from the set of predefined filter key configurations. For example, if the predefined
25 filter key configuration for "Product" includes parameters such as "Product Name," "Category," and "Price," an update request might seek to add a new parameter "Stock Availability." The request would specify this new parameter, prompting the system to modify the existing "Product" filter key configuration to include "Stock Availability" along with the existing parameters.
30
18

[0059] In an exemplary embodiment, each updated filter key configuration from the set of updated filter key configurations comprises at least one updated filter key parameter based on the updated filter key configuration request. For example, an initial filter key configuration for "Employee" includes parameters such as "Name," 5 "Department," and "Role." If an update filter key configuration request is made to add the parameter "Remote Work Status," the system will generate an updated filter key configuration. This new configuration will now include "Name," "Department," "Role," and the newly added "Remote Work Status." Thus, subsequent data retrievals using the "Employee" filter key will return information including the 10 remote work status of each employee, reflecting the latest data requirements.
[0060] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a
15 particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended
20 functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0061] Referring to FIG. 3, an exemplary method flow diagram [300] for generating a target filtered data, in accordance with exemplary implementations of 25 the present disclosure is shown. In an implementation the method [300] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 3, the method [300] starts at step [302].
30 [0062] At step [304], the method [300] as disclosed by the present disclosure comprises receiving, by a transceiver unit [202], a retrieve data request, wherein the
19

retrieve data request comprises at least a request filter key. The retrieve data request may be associated with such as, but not limited to, service enquiry, plan offering, product details and the like. The retrieve data request may comprise at least the request filter key. The request filter key may be associated with the retrieve data 5 request. In an exemplary aspect, the request filter key may comprise such as, but not limited to, address, account, plan, product, service and the like. For example, when a user or an application needs specific customer data, they send a retrieve data request to the system. This request includes a request filter key, such as "Address" or "Product," indicating the specific subset of data required. The transceiver unit 10 [202] captures this request and processes the request filter key to ensure that only the relevant data is retrieved and returned.
[0063] At step [306], the method [300] as disclosed by the present disclosure comprises retrieving, by a retrieval unit [204] from a cache memory [210], a target
15 filter key configuration from a set of predefined filter key configurations based on the request filter key. For example, when the transceiver unit [202] receives a data request with the filter key "Address," the retrieval unit [204] is tasked with identifying and retrieving the corresponding filter key configuration from the cache memory [210]. The configuration outlines the specific parameters and rules for
20 filtering and formatting the requested data. The cache memory [210] stores the predefined configurations to enable quick and efficient access, reducing the need for time-consuming database queries or processing.
[0064] At step [308], the method [300] as disclosed by the present disclosure 25 comprises generating, by a filtered data generator unit [206], the target filtered data associated with the request filter key based on the retrieving of the target filter key configuration from the set of predefined filter key configurations. For example, after the retrieval unit [204] has fetched the filter key configuration for "Address" from the cache memory [210], the filtered data generator unit [206] uses this 30 configuration to filter the customer data accordingly. Suppose the customer data includes various attributes such as account details, product purchases, service
20

information, and addresses. The filter key configuration will specify that only the address-related information is to be included in the final output. The filtered data generator unit [206] processes the raw data, extracts the necessary address information as per the configuration, and compiles it into a coherent JSON object 5 to be returned as the response.
[0065] Thereafter, the method [300] terminates at step [310].
[0066] Referring to FIG. 4, an exemplary block diagram of a system [400]
10 architecture for generating a target filtered data, is shown, in accordance with the
exemplary implementations of the present disclosure. In an implementation the
system architecture [400] may include a subscription engine [402], an Evolved
Packet core (EPC) [404], a Fulfilment management system (FMS) [406], at least
one load balancer [408], one or more channels [410] comprising a Point of Sale
15 (POS) [410a], a Device Management Platform (DMP) [410b], a SELFCARE
[410c], and a Customer Relationship Management User Interface (CRM UI)
[410d]. Further the system architecture [400] may include an Identity Access
Management (IAM) instance [412], a Data Information Framework (DIF) instance
[414], an Operations, Administration, and Management (OAM) instance [416], one
20 or more databases [418], and one or more interconnected units [420].
[0067] The system architecture [400] comprises the subscription engine [402] containing data related to one or more users/subscribers and the evolved packet core (EPC) [404]. Both the subscription engine [402] and the EPC [404] are connected 25 to the FMS [406].
[0068] The system architecture [400] further comprises the load balancer [408] that
manages the traffic from the FMS [406], ensuring efficient distribution of requests
from the subscription engine [402] and the EPC [404]. It handles both HTTPS and
30 Web Socket requests, directing them to appropriate instances within the engine. In
21

an exemplary aspect, the subscription engine [402] may contain data related to one or more users and one or more subscribers.
[0069] Furthermore, the system architecture [400] comprises the one or more 5 channels [410] which are connected to the load balancer [408]. Further, the one or more channels [410] include such as, but not limited to, the Point of Sale (POS) [410a], the Device Management Platform (DMP) [410b], the SELFCARE [410c], and the Customer Relationship Management User Interface (CRM UI) [410d]. Further, the one or more channels [410] may use the Hyper Text Transmission 10 Protocol (HTTP) or the Web Sockets (WS) for providing a secure communication between the one or more channels [410] and the load balancer [408].
[0070] The load balancer [408] is further connected to one or more instances such as but not limited to the IAM instance [412], the DIF instance [414] and the OAM
15 instance [416]. Further, the one or more instances may facilitate in management of one or more data related to users and subscribers and/or may facilitate in the connection of the subscription engine [402] with at least one of the EPC [404], the FMS [406], the one or more channels [410], the one or more databases [418], and the one or more interconnected units [420]. In an exemplary aspect, the IAM
20 instance [412] secures user applications and data at the access gateway. It provides robust defence against malicious login attempts and safeguards credentials by enabling risk-based access controls, ensuring identity protection tools and strong authentication options without disrupting ‘business-as-usual’ processes. In an exemplary aspect, the OAM instance [416] provides a framework for managing and
25 controlling network systems. Furthermore, it manages the registry of microservices (small, independent processes that together form a larger application), their dependencies, and other information required for the microservices to communicate with each other.
30 [0071] Further, the one or more databases [418] may include plurality of databases such as but not limited to database 1 (DB1), database 2 (DB2), database 3 (DB3)
22

etc. The one or more databases may be utilized for storing data related to the IAM instance [412], the DIF instance [414] and the OAM instance [416].
[0072] In an exemplary aspect, the one or more interconnected units [420] may 5 include interaction with the one or more instances. The one or more interconnected units [420] may further include a FMS [420a], a unified assurance platform (UAP) [420b] and a Customer Relationship Management (CRM) [420c] via the HTTP for User Authentication and management. In an exemplary aspect, the UAP [420b] provides a platform that enables telecom operators to track and resolve customer 10 complaints and issues, with modules for ticket creation, assignment, tracking, escalation, and reporting. In an exemplary aspect, the CRM [420c] platform simplifies lead generation, customer support, order management, document verification, and a host of other processes.
15 [0073] Referring to FIG. 5 an exemplary process flow diagram [500], for generating a target filtered data, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the process [500] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement the features of the present
20 disclosure. Also, as shown in FIG. 5, the method [500] starts at step [502].
[0074] At step 504, a data request that comes from a channel may be retrieved. The transceiver unit [202] receives the retrieve data request, wherein the retrieve data request comprises at least a request filter key. The retrieve data request may be 25 associated with such as, but not limited to, service enquiry, plan offering, product details and the like.
[0075] At step 506, the DIF may process the request and deduce the filter key.
30 [0076] At step 508, filter key configurations may be created beforehand i.e., a set of predefined filter key configurations may be created beforehand. The retrieval
23

unit [204], retrieves a target filter key configuration from a set of predefined filter key configurations based on the request filter key. For example, when the transceiver unit [202] receives a data request with the filter key "Address," the retrieval unit [204] is tasked with identifying and retrieving the corresponding filter key configuration from the cache memory [210].
[0077] At step 510, a determination may be made to ascertain whether the API is received or not to further alter created filter key configuration. In one example, in case the API is not received then a request may be sent back requesting the API. In another example, if the API is not received then the process may be terminated. In another example, if the API is not received the process will proceed without the created filter key configuration.
[0078] In case, if the API is received, the method proceeds to step 512. At step 512, based on the received API, the filter key configuration that were created beforehand may then be updated from the database (DB) and the Cache memory [210]. The analysis unit [208] generates a set of updated key configurations based on the one or more predefined filter key configurations.
[0079] At step 514, filter key configurations from cache may be retrieved. The retrieval unit [204] retrieves from the cache memory [210], the target filter key configurations.
[0080] At step 516, the generic algorithm to get filtered data from holistic data based on filter key may be executed.
[0081] At step 518, response may be returned.
[0082] At step 520, the process [500] terminates.

[0083] The present disclosure further discloses a User Equipment (UE). The UE may include a memory and a processor coupled to the memory. The processor may be configured to transmit a retrieve data request comprising at least a request filter key to a system. The retrieve data request may be used by the system for generating a target filtered data based on: receiving the retrieve data request, retrieving a target filter key configuration from a set of predefined filter key configurations based on the request filter key and generating the target filtered data associated with the request filter key based on the retrieving the target filter key configuration from the set of predefined filter key configurations.
[0084] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for generating a target filtered data, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit [202] of the system [200] to receive a retrieve data request, wherein the retrieve data request comprises at least a request filter key. Further, the executable code which, when executed by the one or more units of the system, causes a retrieval unit [204] of the system [200] to retrieve from a cache memory [210] of the system [200], a target filter key configuration from a set of predefined filter key configurations based on the request filter key. Furthermore, the executable code which, when executed by the one or more units of the system, causes a filtered data generator unit [206] of the system [200] to generate the target filtered data associated with the request filter key based on the retrieval of the target filter key configuration from the set of predefined filter key configurations.
[0085] As is evident from the above, the present disclosure provides a technically advanced solution for generating query data through target filter key mechanism. The present solution envisages many advantages as compared to the earlier followed practices such as all logic changes in the present solution are handled solely by configurations and these configurations are present in server/processor’s cache memory. Any change in the filter key configuration (done by hitting an API)

is immediately reflected into cache memory, thus, avoiding the need for restart and optimizes seamless transition to new filter key configurations.
[0086] It should be noted that the terms "first", "second", "primary", "secondary", "target" and the like, herein do not denote any order, ranking, quantity, or importance, but rather are used to distinguish one element from another.
[0087] While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We Claim:
1. A method for generating a target filtered data, the method comprising:
receiving, by a transceiver unit [202], a retrieve data request, wherein the retrieve data request comprises at least a request filter key;
retrieving, by a retrieval unit [204] from a cache memory [210], a target filter key configuration from a set of predefined filter key configurations based on the request filter key; and
generating, by a filtered data generator unit [206], the target filtered data associated with the request filter key based on the retrieving the target filter key configuration from the set of predefined filter key configurations.
2. The method as claimed in claim 1 further comprising:
receiving, by the transceiver unit [202], the set of predefined filter key configurations;
receiving, by the transceiver unit [202] via an interface, an update filter key configuration request;
identifying, by an analysis unit [208], one or more target predefined filter key configuration from the set of predefined filter key configurations based on the update filter key configuration request;
generating, by the analysis unit [208], a set of updated filter key configurations based on the one or more target predefined filter key configuration; and
storing, by the analysis unit [208] in the cache memory [210], the set of updated filter key configurations generated based on the one or more target predefined filter key configuration.
3. The method as claimed in claim 2, wherein the update filter key configuration
request comprises a request for updating at least one filter key parameter from
the set of filter key parameters associated with at least one predefined filter key
configurations from the set of predefined filter key configurations.

4. The method as claimed in claim 2, wherein each updated filter key configuration from the set of updated filter key configurations comprises at least one updated filter key parameter based on the updated filter key configuration request.
5. The method as claimed in claim 1, wherein each filter key configuration from the set of predefined filter key configurations comprises a set of filter key parameters.
6. A system [200] for generating a target filtered data, the system [200] comprising:
a transceiver unit [202] configured to receive a retrieve data request, wherein the retrieve data request comprises at least a request filter key.
a retrieval unit [204] connected to at least the transceiver unit [202], the retrieval unit [204] configured to retrieve from a cache memory [210], a target filter key configuration from a set of predefined filter key configurations based on the request filter key; and
a filtered data generator unit [206] connected to at least the retrieval unit [204], the filtered data generator unit [206] configured to generate the target filtered data associated with the request filter key based on the retrieval of the target filter key configuration from the set of predefined filter key configurations.
7. The system [200] as claimed in claim 6 wherein:
the transceiver unit [202] is connected to an analysis unit [208], the transceiver unit [202] configured to:
receive the set of predefined filter key configurations, and receive, via an interface, an update filter key configuration request; and the analysis unit [208] is configured to:

identify one or more target predefined filter key configuration from the set of predefined filter key configurations based on the update filter key configuration request,
generate a set of updated filter key configurations based on the one or more target predefined filter key configuration, and
store, in the cache memory [210], the set of updated filter key configurations generated based on the one or more target predefined filter key configuration.
8. The system [200] as claimed in claim 7, wherein the update filter key configuration request comprises a request for updating at least one filter key parameter from the set of filter key parameters associated with at least one predefined filter key configurations from the set of predefined filter key configurations.
9. The system [200] as claimed in claim 7, wherein each updated filter key configuration from the set of updated filter key configurations comprises at least one updated filter key parameter based on the updated filter key configuration request.
10. The system [200] as claimed in claim 6, wherein each filter key configuration from the set of predefined filter key configurations comprises a set of filter key parameters.
11. A User Equipment (UE) comprising:
a memory; and
a processor coupled to the memory, the processor configured to transmit a retrieve data request comprising at least a request filter key to a system [200], wherein the retrieve data request is used by the system [200] for generating a target filtered data based on:
receiving the retrieve data request,

retrieving a target filter key configuration from a set of predefined filter key configurations based on the request filter key; and
generating the target filtered data associated with the request filter key based on the retrieving the target filter key configuration from the set of predefined filter key configurations.