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 PERFORMING A TARGET
ACTION”
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 PERFORMING A TARGET ACTION
TECHNICAL FIELD
5 [0001] Embodiments of the present disclosure generally relate to data performance
management systems. More particularly, embodiments of the present disclosure relate to a method and system for performing a target action by using dual- database approach.
10 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
15 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 the landscape of Electronic Design Interchange Format (EDIF) products,
20 efficient data retrieval plays a pivotal role in enhancing user experience and
operational efficiency. Traditionally, many EDIF products worldwide have
predominantly relied on a single type of database — SQL databases. However, this
conventional approach of relying on single type of database introduces inherent
limitations, particularly regarding performance and throughput per second. Despite
25 endeavours to optimize hardware configurations, the presence of a single database
type imposes a ceiling on system performance, hindering the realization of
maximum efficiency. Despite optimizing hardware configurations, the presence of
a single type of database hampers the ability to achieve maximum efficiency and
scalability, preventing it from reaching its full potential. Resolving this issue is
30 crucial to overcome the limitations imposed by the current reliance on SQL
databases and unlock enhanced performance capabilities in EDIF products.
2

[0004] Thus, there exists an imperative need in the art to overcome the above-stated challenges, which the present disclosure aims to address.
5 SUMMARY
[0005] 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
10 subject matter.
[0006] An aspect of the present disclosure may relate to a method for performing a target action. The method includes receiving, by a transceiver unit, a target action request. The target action request corresponds to a data creation request.
15 Additionally, the method includes maintaining, by a database manager, one or more
datasets comprising a set of data values. Each dataset from the one or more datasets is associated with one or more dataset parameter. The method also includes maintaining, by a database manager, a first database comprising one or more tables based on the one or more datasets. Each table from the one or more tables comprises
20 one or more first data values. The one or more first data values correspond to values
assigned to the one or more datasets. The method also includes maintaining, by the database manager, a cache database comprising one or more data identifiers based on the one or more tables. Each data identifier from the one or more data identifiers comprises at least a set of second data values from the one or more first data values.
25 The set of second data values is a subset of values from the one or more first data
values that are used for performing the target action for more than a predefined number of times. Further, the method includes receiving, by the transceiver unit, a retrieve entity request. The retrieve entity request comprises at least one of a query data identifier and a query data lookup parameter. Also, the method includes
30 identifying, by an analysis unit, one or more target data values associated with the
retrieve entity request from at least one of the first database and the cache database
3

based on at least one of the query data identifier and the query data lookup
parameter. Furthermore, the method includes performing, by the analysis unit, the
target action associated with the target action request based on identifying the one
or more target data values from at least one of the first database and the cache
5 database.
[0007] In an exemplary aspect of the present disclosure, the one or more data
identifiers is associated with at least: a customer, a product catalogue data, a master
reference data, a customer invoicing data, a billing details dataset, and a
10 geographical information.
[0008] In an exemplary aspect of the present disclosure, the query data identifier is a unique identifier assigned to a particular query by the database manager.
15 [0009] In an exemplary aspect of the present disclosure, the query data lookup
parameter is at least one of a data filter parameter, a data paging parameter, a data sorting parameter, and a data wildcard search parameter.
[0010] In an exemplary aspect of the present disclosure, the target action is at least
20 one of a key value fetch action, a data filtering action, a data paging action, and a
data sorting action.
[0011] In an exemplary aspect of the present disclosure, the one or more target data
values associated with at least the key value fetch action is identified from the cache
25 database, and the one or more target data values associated with at least one of the
data filtering action, the data paging action, and the data sorting action is identified from the first database.
[0012] In an exemplary aspect of the present disclosure, the method further
30 comprises maintaining, by the database manager, a consistency between the first
database and the cache database for providing data synchronization.
4

[0013] In an exemplary aspect of the present disclosure, to maintain the consistency
between the first database and the cache database, the method further comprises at
least: data mapping between the first database and the cache database. Further, the
5 method includes data transformation between the first database and the cache
database and normalizing data structures to eliminate redundancy across the first database and the cache database.
[0014] Another aspect of the present disclosure may relate to a system for
10 performing a target action. The system comprises a transceiver unit configured to
receive a target action request. The target action request corresponds to a data creation request. Further, the system comprises a database manager connected to at least the transceiver unit. The database manager is configured to maintain one or more datasets. The one or more datasets comprises a set of data values. Each dataset
15 from the one or more datasets is associated with one or more dataset parameter. The
database manager is further configured to maintain a first database based on the one or more datasets. The first database comprises one or more tables. Each table from the one or more tables comprises one or more first data values. The one or more first data values correspond to values assigned to the one or more datasets.
20 Additionally, the database manager is configured to maintain a cache database
based on the one or more tables. The cache database comprises one or more data identifiers and each data identifier from the one or more data identifiers comprises at least a set of second data values from the one or more first data values. The set of second data values is a subset of values from the one or more first data values
25 that are used for performing the target action for more than a predefined number of
times. Also, the transceiver unit is further configured to receive, a retrieve entity request that comprises at least one of a query data identifier and a query data lookup parameter. The system further comprises an analysis unit connected to at least the transceiver unit and the database manager. The analysis unit is configured to
30 identify one or more target data values associated with the retrieve entity request
from at least one of the first database and the cache database based on at least one
5

of the query data identifier and the query data lookup parameter, and perform the target action associated with the target action request based on the identification the one or more target data values from at least one of the first database and the cache database. 5
[0015] Yet another aspect of the present disclosure may relate to a user equipment (UE) configured to perform a target action. The UE comprises a memory and a processor connected to the memory. The processor is configured to send a target action request to a system, wherein the wherein the target action request
10 corresponds to a data creation request. Further, the system is configured to perform
the target action based on maintaining, by a database manager of the system, one or more datasets. The one or more datasets comprises a set of data values. Each dataset from the one or more datasets is associated with one or more dataset parameter. The database manager is further configured to maintain a first database based on the one
15 or more datasets. The first database comprises one or more tables. Each table from
the one or more tables comprises one or more first data values. The one or more first data values correspond to values assigned to the one or more datasets. Additionally, the database manager is configured to maintain a cache database based on the one or more tables. The cache database comprises one or more data
20 identifiers and each data identifier from the one or more data identifiers comprises
at least a set of second data values from the one or more first data values. The set of second data values is a subset of values from the one or more first data values that are used for performing the target action for more than a predefined number of times. Further, the system is configured to perform the target action based on
25 receiving, by a transceiver unit of the system, a retrieve entity request that
comprises at least one of a query data identifier and a query data lookup parameter. The system is configured to perform the target action based on identifying, by an analysis unit, one or more target data values associated with the retrieve entity request from at least one of the first database and the cache database based on at
30 least one of the query data identifier and the query data lookup parameter, and
performing the target action associated with the target action request based on the
6

identification the one or more target data values from at least one of the first database and the cache database.
[0016] Yet another aspect of the present disclosure may relate to a non-transitory
5 computer readable storage medium storing one or more instructions for performing
a target action, the instructions include executable code which, when executed by a one or more units of a system, causes: a transceiver unit of the system to receive, a target action request. The target action request corresponds to data creation request. Further, the instructions include executable code which, when executed by the one
10 or more units of the system, causes a database manager of the system to maintain
one or more datasets. The one or more datasets comprises a set of data values, and each dataset from the one or more datasets is associated with one or more dataset parameter. In addition, the instructions which, when executed by the one or more units of the system, causes the database manager of the system to maintain, a first
15 database based on the one or more datasets. The first database comprises one or
more tables and each table from the one or more tables comprises one or more first data values. The one or more first data values correspond to values assigned to the one or more datasets. Also, the instructions which, when executed by the one or more units of the system, causes the database manager of the system to maintain, a
20 cache database based on the one or more tables, wherein the cache database
comprises one or more data identifiers, and wherein each data identifier from the one or more data identifiers comprises at least a set of second data values from the one or more first data values. The set of second data values is a subset of values from the one or more first data values that are used for performing the target action
25 for more than a predefined number of times. The instructions which, when executed
by the one or more units of the system, causes the transceiver unit of the system to receive, a retrieve entity request that comprises at least one of a query data identifier and a query data lookup parameter. The instructions which, when executed by the one or more units of the system, causes an analysis unit of the system to identify
30 one or more target data values associated with the retrieve entity request from at
least one of the first database and the cache database based on at least one of the
7

query data identifier and the query data lookup parameter. The instructions which,
when executed by the one or more units of the system, causes the analysis unit of
the system to perform the target action associated with the target request based on
the identification the one or more target data values from at least one of the first
5 database and the cache database.
OBJECTS OF THE INVENTION
[0017] Some of the objects of the present disclosure, which at least one
10 embodiment disclosed herein satisfies are listed herein below.
[0018] It is an object of the present disclosure to provide a system and a method for maintaining dual-database approach.
15 [0019] It is another object of the present disclosure to provide a solution that
identifies a target database based on a target retrieve entity request.
[0020] It is yet another object of the present disclosure to provide a solution to
generate a response based on at least identifying the target database associated with
20 the target retrieve entity request.
DESCRIPTION OF THE DRAWINGS
[0021] The accompanying drawings, which are incorporated herein, and constitute
25 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
30 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
8

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.
5 [0022] FIG. 1 illustrates an exemplary block diagram of a system for performing a
target action, in accordance with exemplary implementations of the present disclosure.
[0023] FIG. 2 illustrates a method flow diagram for performing the target action,
10 in accordance with exemplary implementations of the present disclosure.
[0024] FIG. 3 illustrates an exemplary flow chart indicating for maintaining dual-database approach to perform the target action, in accordance with exemplary implementations of the present disclosure. 15
[0025] FIG. 4 illustrates an exemplary architecture of the system, in accordance with exemplary implementations of the present disclosure.
[0026] FIG. 5 illustrates an exemplary block diagram of a computing device upon
20 which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure.
[0027] The foregoing shall be more apparent from the following more detailed description of the disclosure. 25
DETAILED DESCRIPTION
[0028] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of
30 embodiments of the present disclosure. It will be apparent, however, that
embodiments of the present disclosure may be practiced without these specific
9

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

aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
known to those of ordinary skill in the art. Furthermore, to the extent that the terms
5 “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.
10 [0033] 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
15 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
20 processing unit is a hardware processor.
[0034] 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
25 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
30 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
11

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.
[0035] As used herein, “storage unit” or “memory unit” refers to a machine or
5 computer-readable medium including any mechanism for storing information in a
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
10 that may be required by one or more units of the system to perform their respective
functions.
[0036] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
15 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.
20 [0037] 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,
25 Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
[0038] As used herein the transceiver unit include at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals,
30 information or a combination thereof between units/components within the system
and/or connected with the system.
12

[0039] The present disclosure aims to overcome the problems mentioned in the
background section other existing problems in this field of technology by disclosing
a novel solution that addresses the challenge of data consistency and the split-brain
5 problem that can arise when using two types of databases, namely the cache DB
and the SQL-like DB. By implementing proper reconciliation measures between the cache DB and the SQL-like DB, the solution ensures that data remains consistent across both systems without any deviations. This reconciliation process ensures that any updates or modifications made in one database are propagated and
10 reflected accurately in the other database as well. By avoiding the split-brain
problem, where conflicting data versions can lead to data inconsistencies and integrity issues, the solution guarantees that the data remains reliable and coherent in both the cache DB and the SQL-like DB. This novel approach safeguards the integrity and consistency of the data, allowing seamless operation and reliable
15 access to information in the EDIF products using a dual database system.
[0040] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
20 [0041] FIG. 1 illustrates an exemplary block diagram of a system [100] for
performing a target action, in accordance with exemplary implementations of the present disclosure. The system [100] is a dual database system. The system [100] comprises at least one transceiver unit [102], at least one database manager [104], at least one analysis unit [106], at least one processing unit [112] and at least one
25 storage unit [114]. Also, all of the components/ units of the system [100] 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. 1 only a few units are shown, however, the system [100] may comprise multiple such units or the system [100] may comprise
30 any such numbers of said units, as required to implement the features of the present
disclosure. Further, in an implementation, the system [100] may be present in a user
13

device to implement the features of the present disclosure. The system [100] may
be a part of the user device/or may be independent of but in communication with
the user device (may also referred herein as a UE). In another implementation, the
system [100] may reside in a server or a network entity. In yet another
5 implementation, the system [100] may reside partly in the server/network entity and
partly in the user device.
[0042] The system [100] is configured for performing the target action, with the help of the interconnection between the components/units of the system [100]. The
10 target action may be associated with an action of at least: data creation, data search,
data management or data update. The data creation may include creating data by inserting a new customer record with details such as customer ID, name, email address, phone number, and address. The data search refers to searching for specific data that involves querying a customer table to find records where the email address
15 matches with stored/original email address of the customer. The data management
includes managing data that entails retrieving all customer details sorted in an order (example, alphabetically by name) from the customer table. The data update includes updating data that may be exemplified by changing or updating the phone number to a new number.
20
[0043] The system [100] is configured to perform the target action by maintaining dual-database approach using the components/units of the system [100].
[0044] The transceiver unit [102] of the system [100] is configured to receive a
25 target action request. The transceiver unit [102] may be associated with the
processing unit [112]. The processing unit [112] may be configured to process the
target action request. The target action request corresponds to at least one of: a data
creation request, data search request, data management request, or data update
request. The target action request may be received from one or more users. The one
30 or more users trigger actions within the system [100], by sending the target action
requests, to the transceiver unit [102]. The one or more users may be individuals or
14

group of individuals communicating with the system [100]. The one or more users
include but may not be limited to an administrator, an owner of an organization,
and an employee of the organization. For instance, a user may enter a search query
to retrieve some data from the system [100]. Such a data search request is received
5 at the transceiver unit [102].
[0045] In general, the transceiver unit [102] is an electronic device which is a
combination of a transmitter and a receiver. The transceiver unit [102] is configured
to follow one or more communication protocols and data transmission mechanisms
10 that, streamlines exchange of information between a database and one or more
external entities (such as web applications, desktop applications, third-party database systems, and the like). The transceiver unit [102] is connected to the database manager [104].
15 [0046] The database manager [104] is configured to maintain the one or more
datasets. The one or more datasets comprises a set of data values and each dataset from the one or more datasets is associated with one or more dataset parameter. The one or more datasets may correspond to data related to a customer, a product catalogue, master reference, customer invoicing, billings, geographical
20 information, and the like. The one or more datasets may be received from the one
or more users. For instance, a dataset is a customer, wherein the one or more parameters for the dataset “customer” may be at least one of: “name”, “address”, “contact information” and the like. Also, the set of data values corresponding to the dataset “customer” and the parameter “name” may be “value 1 - first name”, “value
25 2 - middle name”, and “value 3 – last name”. Additionally, the set of data values
corresponding to the dataset “customer” and the parameter “address” may be “value 1 – house number”, “value 2 - Street name”, “value 3 – City”, and “value 4 – state”.
[0047] The database manager [104] is further configured to maintain a first
30 database [108] based on the one or more datasets. The first database [108]
comprises one or more tables. Each table from the one or more tables comprises
15

one or more first data values. The one or more first data values correspond to values
assigned to the one or more datasets. For instance, the one or more first data values
may refer to an initial set of data values stored within the one or more tables of the
first database [108]. The one or more first data values may represent raw or original
5 data stored in the first database [108], organized within rows and columns of the
one or more tables. For example, in a customer table, the one or more first data values may include attributes such as customer ID, name, email address, phone number, and address. Each of the attributes contains actual data pertaining to individual customers.
10
[0048] Furthermore, the database manager [104] is configured to maintain a cache database [110] based on the one or more tables. The cache database [110] comprises one or more data identifiers. The one or more data identifiers is associated with at least a customer, a product catalogue data, a master reference data, a customer
15 invoicing data, a billing details dataset, and a geographical information. Each data
identifier from the one or more data identifiers comprises at least a set of second data values from the one or more first data values. The one or more first data values may include primary attributes. The one or more first data values may include a customer identifier, a name, an email address, a phone number, address attributes,
20 and the like. The set of second data values is a subset of values from the one or
more first data values that are used for performing the target action for more than a predefined number of times which means that the set of second data values is frequently used. The predefined number may be set by the database manager [104]. The set of second data values may include the one or more first data values that
25 may be frequently used for performing the target action. For instance, the set of
second data may include data for caching which may be frequently accessed. The email address and the phone number may be frequently accessed by the database manager [104] to send reminders and notifications to the user. The database manager [104] may set the email address and the phone number as cache data in the
30 cache database [110].
16

[0049] The set of second data values are derived from the one or more first data
values and are stored within the cache database [110]. The set of second data values
may be extracted or derived from the one or more first data values based on a
predefined criterion, such as frequency of use or relevance to the target action. For
5 instance, the set of second data values are selected to optimize query performance
and enhance efficiency of the system [100] by caching frequently accessed or
commonly used data. Unlike the one or more first data values, which store all
available data within the one or more tables, the set of second data values may
represent a subset of the original data that is deemed most relevant or frequently
10 accessed. For instance, if certain attributes (such as customer name, product price,
or invoice date) are frequently queried or used in target actions within the system [100], their corresponding values would be selected as the set of second data values and cached in the cache database [110].
15 [0050] The database manager [104] is connected with the storage unit [114]. The
storage unit [114] is configured to store the one or more datasets in the database manager [104].
[0051] Further, the transceiver unit [102] is configured to receive a retrieve entity
20 request. The retrieve entity request may comprise at least one of a query data
identifier and a query data lookup parameter. The retrieve entity request may
retrieve a particular query from the database manager [104]. The query data
identifier may be a unique identifier assigned to the particular query by the database
manager [104] within the system [100]. For instance, when a user submits a query
25 to retrieve specific data, the database manager [104] assigns a unique identifier to
that query. The query data identifier helps track and manage the query throughout
processing lifecycle of the query. Also, the query data identifier serves as a unique
reference point for individual queries within the system [100], enabling effective
query management, tracking, and accountability. Further, the query data lookup
30 parameter is a parameter used in the retrieve entity request. In addition, the query
data lookup parameter is one such parameter that helps refine criteria of searching
17

the query criteria. In one implementation, the query data lookup parameter may be at least a data filter parameter, a data paging parameter, a data sorting parameter, and a data wildcard search parameter.
5 [0052] The data filter parameter allows users to filter the data to specify the data
that is required to be retrieved based on a certain criterion such as a date range, a category, or any relevant parameter of the like to narrow down search results. Further, when dealing with large datasets, users might want to retrieve data in small, and manageable chunks. The data paging parameter enables users to specify how
10 many records they want to retrieve per page and which page of results they want to
access. In addition, the data sorting parameter may be used to specify an order in which the user wants the retrieved data to be sorted. The data may be sorted based on a specific attribute such as alphabetical order, numerical order, or chronological order. Further, the data wildcard search parameter may facilitate a flexible search
15 approach by allowing users to use wildcard characters to represent unknown parts
of a search query. The data wildcard search parameter is particularly useful when users want to search for data based on partial matches or patterns rather than exact matches.
20 [0053] Referring to the transceiver unit [102], the transceiver unit [102] is
associated with the analysis unit [106] of the system [100]. In an embodiment, the analysis unit [106] is connected to at least the transceiver unit [102] and the database manager [104]. The analysis unit [106] is configured to identify the one or more target data values associated with the retrieve entity request from at least one of the
25 first database [108] and the cache database [110] based on at least one of the query
data identifier and the query data lookup parameter. The analysis unit [106] may analyse at least one of the first database [108] and the cache database [110] to identify the one or more target data values. The analysis unit [106] is further configured to perform the target action associated with the target request based on
30 the identification of the one or more target values from at least one of the first
database [108] and the cache database [110]. The target action is at least one of a
18

key value fetch action, a data filtering action, a data paging action, and a data sorting
action. The one or more target data values associated with at least the key value
fetch action are identified from the cache database [110]. The one or more target
data values associated with at least one of: the data filtering action, the data paging
5 action, and the data sorting action are identified from the first database [108].
[0054] The database manager [104] is further configured to maintain a consistency between the first database [108] and the cache database [110] to provide data synchronization. To maintain the consistency between the first database [108] and
10 the cache database [110], the database manager [104] is further configured to
perform at least: data mapping between the first database [108] and the cache database [110]; data transformation between the first database [108] and the cache database [110]; and normalizing data structures to eliminate redundancy across the first database [108] and the cache database [110]. In an implementation of the
15 present disclosure, the data mapping between the first database [108] and the cache
database [110] may include establishing a relation between the first database [108] and the cache database [110]. In an implementation of the present disclosure, the data transformation refers to converting format of the data stored in the first database [108] to the format of the data stored in the cache database [110]. The data
20 transformation may include aggregation of data, filtering of data, reformatting of
data, and the like. In an implementation of the present disclosure, the normalizing
the data structures refers to organizing the data in the first database [108] and the
cache database [110] to find any duplicate data in the first database [108] and the
cache database [110].
25
[0055] Referring to FIG. 2, an exemplary method flow diagram [200] for
performing the target action, in accordance with exemplary implementations of the
present disclosure is shown. In an implementation the method [200] is performed
by the system [100]. Also, as shown in FIG. 2, the method [200] initiates at step
30 [202].
19

[0056] Following step [202], at step [204], the method [200] includes receiving, by
the transceiver unit [102], a target action request, wherein the target action request
corresponds to at least one of: a data creation request, data search request, data
management request, or data update request. The target action request may be
5 received from one or more users. The one or more users trigger actions within the
system [100], by sending the target action requests, to the transceiver unit [102]. The one or more users may be individuals or group of individuals communicating with the system [100]. The one or more users include but may not be limited to an administrator, an owner of an organization, and an employee of the organization.
10
[0057] At step [206], the method [200] includes maintaining, by the database manager [104], the one or more datasets comprising a set of data values. The set of data values may refer to the data stored in the one or more datasets. For instance, if the one or more datasets of a customer includes customer identifier, name, email
15 address, and phone number, the set of data values refers to information associated
with the one or more datasets. For instance, information associated with the customer identifier may be “007”, and information associated with the name may be “XYZ”, information associated with the email address may be “xyz@anywhere.com” and information associated with the phone number may be
20 “0001119999”. Each dataset from the one or more datasets is associated with one
or more parameters. The one or more parameters may define characteristics or properties of the data within the one or more datasets. The one or more parameters may define characteristics of the set of data values in the one or more datasets.
25 [0058] At step [208], the method [200] includes maintaining, by the database
manager [104], the first database [108], comprising one or more tables, based on the one or more datasets. The one or more tables are used for organizing related data into a coherent structure, facilitating efficient storage, retrieval, and manipulation of the data. The first database [108] may be an SQL-like database.
30 Each table from the one or more tables comprises one or more first data values. The
20

one or more first data values correspond to values assigned to the one or more datasets (as explained above in FIG. 1).
[0059] At step [210], the method [200] includes maintaining, by the database
5 manager [104], the cache database [110], comprising one or more data identifiers,
based on the one or more tables. The one or more data identifiers is associated with at least a customer, a product catalogue data, a master reference data, a customer invoicing data, a billing details dataset, and a geographical information. Each data identifier from the one or more data identifiers comprises at least a set of second
10 data values from the one or more first data values. The set of second data values is
a subset of values from the one or more first data values that are used for performing the target action for more than a predefined number of times which means that the set of second data values is frequently used. The predefined number may be set by the database manager [104].
15
[0060] At step [212], the method [200] includes receiving, by the transceiver unit [102], a retrieve entity request, wherein the retrieve entity request comprises at least one of a query data identifier and a query data lookup parameter. The query data identifier may be a unique identifier assigned to the particular query by the database
20 manager [104] within the system [100]. For instance, when a user submits a query
to retrieve specific data, the database manager [104] assigns a unique identifier to that query. The query data identifier helps track and manage the query throughout processing lifecycle of the query. Also, the query data identifier serves as a unique reference point for individual queries within the system [100], enabling effective
25 query management, tracking, and accountability. Generally, the query data lookup
parameter is a parameter used in the retrieve entity request. In addition, the query data lookup parameter is one such parameter that helps refine criteria of searching the query criteria. In one implementation, the query data lookup parameter may be at least a data filter parameter, a data paging parameter, a data sorting parameter,
30 and a data wildcard search parameter (as explained in FIG. 1).
21

[0061] At step [214], the method [200] includes identifying, by the analysis unit
[106], the one or more target data values associated with the retrieve entity request
from at least one of the first database [108] and the cache database [110] based on
at least one of the query data identifier and the query data lookup parameter.
5 Further, identifying the one or more target data values include processing of the
retrieve entity request based on one or more factors (such as filters) to extract the specific data values required to fulfil the retrieve entity request.
[0062] At step [216], the method [200] includes performing, by the analysis unit
10 [106], the target action associated with the target request based on identifying the
one or more target data values from at least one of the first database [108] and the
cache database [110]. The target action is at least one of a key value fetch action, a
data filtering action, a data paging action, and a data sorting action. The one or more
target data values associated with at least the key value fetch action are identified
15 from the cache database [110]. The one or more target data values associated with
at least one of: the data filtering action, the data paging action, and the data sorting action are identified from the first database [108].
[0063] At step [218], the method [200] terminates.
20
[0064] Referring to FIG. 3 an exemplary flow diagram of a method [300], for maintaining dual-database approach, in accordance with an implementation of the present disclosure. In an implementation, the system [100] as depicted in figure 1 may be configured to perform the method [300] as depicted in figure 3.
25
[0065] At step [302], the method [300] includes receiving a data creation request. The data creation request may be received from one or more users associated with the system [100].
22

[0066] At step [304], the method [300] includes persisting data associated with the data creation request into an SQL like database (DB). The SQL-like database corresponds to the first database [108] as mentioned in FIG. 1 and FIG. 2.
5 [0067] At step [306], the method [300] includes notifying the cache database [110].
Notifying the cache database [110] includes consolidating the data from one or
more SQL tables using one or more methods for different types of the data. The one
or more SQL tables corresponds to the one or more tables as explained in FIG. 1
and FIG. 2. In an exemplary implementation, notifying the cache database [110]
10 includes preparing a singular JSON for each record containing all JSON tags and
pre-populating the data in the cache database [110].
[0068] At step [308], the method [300] includes receiving a retrieve entity request
from a channel. If the retrieve entity request consists of filters, paginations and/ or
15 sorting, step [312] is performed, else if the retrieve entity request contains
identifier(s), step [310] is performed.
[0069] At step [310], the method includes dipping the cache database [110] with
identifier(s) in the retrieve entity request as key and fetch value. At step [312], the
20 method includes fetching the records from the SQL-like database based on one or
more of input filters, paginations, wildcard searches and sorting parameters based on the retrieve entity request.
[0070] At step [314], the method [300] includes returning a response for the
25 retrieved entity request.
[0071] Referring to FIG. 4 an exemplary system [400] architecture diagram, for maintaining dual-database approach in conjunction with system [100] as depicted in FIG. 1. 30
23

[0072] In an exemplary embodiment, the system architecture [400] may include
sub-components of the system [200] (as shown in FIG. 2) of the current disclosure.
In another embodiment, the architecture [400] may be used to implement the steps
of method [300] (as shown in FIG. 3) for dynamically creating a work order along
5 with the system [200] (as shown in FIG. 2) which is based on the architecture [400]
of the system. In a preferred embodiment, the architecture [400] of the system comprises a plurality of components. For example, and by no way limiting the scope of the present subject matter, the system architecture [400] (as shown in FIG. 4 ) comprises an evolved packet core (EPC) [402], a fulfilment management system
10 (FMS) [404], a plurality of channels [406], a load balancer [408], Service
Management Platform (SMP) [428], Data Information Framework (DIF) Realm [430], a customer relationship manager (CRM)/ customer engagement manager (CEM) server [410] comprising a plurality of micro-services and a database [412]. The channels [406] are configured to provide input data to the DIF Realm [430]
15 through a load balancer [408]. In an embodiment, some examples of the channels
include but are not limited to a POS [420], a data management platform DMP [422], a web portal [424] and a CRM user interface (UI) [426]. It is to be noted that the workflow engine is mix of generic configurations and it also provides space for custom logic so that all the milestones / order journeys can be autonomous and
20 segregated.
[0073] The CRM [410] server contain different micro services which cater to
different APIs. Each microservice serves a particular context, for e.g.-
• COP_MS deals with order related APIs – submit order,
25 query order, modify order.
• CIS instances deal with customer related APIs – create, modify or deactivate customer.
• L2O instances deals with APIs that manage the lifecycle of leads and prospects.
24

[0074] Further, the channels [406] are used to send requests for APIs to servers e.g.
the POS (Point of Sale) [420], the Digital Marketplace (DMP) [422], the web portal
[424], CRM UI [426], etc. The web portal [424] refers to a self-help portal via which
a user/customer can login, view his/her profile and manage his/her services. These
5 channels are connected to servers using load balancer [408] or the FMS [404]. The
channels [406] are tightly coupled to DIF Realm [430] through the load balancer
[408]. In an example, the CRM UI [426] communicates directly via the load
balancer [408] while the other systems which belong to different product such as
the web portal [424], the POS [420] communicates to the servers using the FMS
10 [404]. The FMS [404] is a middleware which links two different products and
performs language translations or workflow management.
[0075] The DIF Realm [430] is a Data Information Framework (DIF) ecosystem that refers to a specific environment or domain where DIF is implemented or
15 utilized. The DIF Realm [430] may be within a particular industry such as
telecommunication, healthcare, finance, or retail with its unique data requirements, and regulatory frameworks. In general, the DIF refers to a structured approach or system that manages and utilizes data within an organization. The DIF may include processes, standards, technologies, and policies designed to ensure that data is
20 collected, stored, processed, and accessed in a secure manner. Further, the DIF
Realm [430] includes at least one of an OAM instance [432], a DIF instance [434], and an IAM instance [436]. The OAM instance [432] deals with the maintenance and operation of all the microservice instances and communicate with outer products related to alarms, KPIs or other management, health check-up information.
25 The DIF instance [434] refers to a specific implementation of the DIF within a
particular context. For each context, there may be a separate DIF instance [434]. The IAM instance [436] refers to Identity and Access Management instance that manages user identities, roles and permissions for accessing resources securely.
25

[0076] The EPC (Enterprise Product Catalogue) [402] is a centralized data repository which drives BSS telecom operations and some network nodes. For e.g., 5G charging system, called PCF.
5 [0077] Further, the FMS (Fulfilment Management System) [404], a middleware,
which acts a mediator between two different products and at the same time, provides
language translation. E.g., if one product understands SOAP protocol while other
one understands RESTful services, the FMS [404] will translate the messages
between these 2 nodes and ensure seamless communication.
10
[0078] The Databases [412] are connected to the DIF Realm [430]/servers which
persist the business data related to customers, orders, leads, prospects and server
configurations.
15 [0079] Further, the SMP [428] refers to a Service Management Platform, which
deals with the installation processes at customer premises, handling repair mechanism and technician visit to network sites.
[0080] The present disclosure can also be implemented on a computing device
20 [500] as shown in FIG. 5. FIG. 5 illustrates an exemplary block diagram of the
computing device [500] upon which the features of the present disclosure may be
implemented in accordance with exemplary implementation of the present
disclosure. In an implementation, the computing device [500] may also implement
the method [400] for performing a target action. In another implementation, the
25 computing device [500] itself implements the method [400] for performing the
target action.
[0081] The computing device [500] may include a bus [502] or other
communication mechanism for communicating information, and a hardware
30 processor [504] coupled with bus [502] for processing information. The hardware
processor [504] may be, for example, a general-purpose microprocessor. The computing device [500] may also include a main memory [506], such as a random-
26

access memory (RAM), or other dynamic storage device, coupled to the bus [502]
for storing information and instructions to be executed by the processor [504]. The
main memory [506] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
5 processor [504]. Such instructions, when stored in non-transitory storage media
accessible to the processor [504], render the computing device [500] into a special-
purpose machine that is customized to perform the operations specified in the
instructions. The computing device [500] further includes a read only memory
(ROM) [508] or other static storage device coupled to the bus [502] for storing static
10 information and instructions for the processor [504].
[0082] A storage device [510], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [502] for storing information and instructions. The computing device [500] may be coupled via the bus [502] to a
15 display [512], 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 [514], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [502] for communicating information and command selections to the processor
20 [504]. Another type of user input device may be a cursor controller [516], such as
a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [504], and for controlling cursor movement on the display [512]. 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
25 the device to specify positions in a plane.
[0083] The computing device [500] 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 [500] causes
30 or programs the computing device [500] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the
27

computing device [500] in response to the processor [504] executing one or more
sequences of one or more instructions contained in the main memory [506]. Such
instructions may be read into the main memory [506] from another storage medium,
such as the storage device [510]. Execution of the sequences of instructions
5 contained in the main memory [506] causes the processor [504] to perform the
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.
10 [0084] The computing device [500] also may include a communication interface
[518] coupled to the bus [502]. The communication interface [518] provides a two-way data communication coupling to a network link [520] that is connected to a local network [522]. For example, the communication interface [518] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
15 a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [518] 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 [518] sends and receives electrical,
20 electromagnetic or optical signals that carry digital data streams representing
various types of information.
[0085] The computing device [500] can send messages and receive data, including program code, through the network(s), the network link [520] and the
25 communication interface [518]. In the Internet example, a server [530] might
transmit a requested code for an application program through the Internet [528], the ISP [526], the local network [522], the host [524] and the communication interface [518]. The received code may be executed by the processor [504] as it is received, and/or stored in the storage device [510], or other non-volatile storage for later
30 execution.
28

[0086] The present disclosure may relate to a user equipment (UE) configured to
perform a target action. The UE comprises a memory and a processor connected to
the memory. The processor is configured to send a target action request to a system
[100]. The target action request corresponds to a data creation request. Further, the
5 system [100] is configured to perform the target action based on maintaining, by a
database manager [104] one or more datasets. The one or more datasets comprises a set of data values. Each dataset from the one or more datasets is associated with one or more dataset parameter. The database manager [104] is further configured to maintain a first database [108] based on the one or more datasets. The first
10 database [108] comprises one or more tables. Each table from the one or more tables
comprises one or more first data values. The one or more first data values correspond to values assigned to the one or more datasets. Additionally, the database manager [104] is configured to maintain a cache database based on the one or more tables. The cache database [110] comprises one or more data identifiers
15 and each data identifier from the one or more data identifiers comprises at least a
set of second data values from the one or more first data values. The set of second data values is a subset of values from the one or more first data values that are used for performing the target action for more than a predefined number of times. Further, the system [100] is configured to perform the target action based on
20 receiving, by the transceiver unit [102], a retrieve entity request that comprises at
least one of a query data identifier and a query data lookup parameter. The system [100] is configured to perform the target action based on identifying, by an analysis unit [106], one or more target data values associated with the retrieve entity request from at least one of the first database [108] and the cache database [110] based on
25 at least one of the query data identifier and the query data lookup parameter, and
performing the target action associated with the target action request based on the identification the one or more target data values from at least one of the first database and the cache database.
30 [0087] The present disclosure further discloses a non-transitory computer readable
storage medium, storing instructions for performing a target action, the instructions
29

include executable code which, when executed by one or more units of a system
[100], causes a transceiver unit [102] of the system [100] to receive a target action
request that corresponds to at least one of: a data creation request, data search
request, data management request, and data update request. The instructions which,
5 when executed by one or more units of a system [100], causes a database manager
[104] of the system [100] to maintain one or more datasets comprising a set of data values. Each dataset from the one or more datasets is associated with the one or more dataset parameter. The instructions which, when executed by one or more units of a system [100], causes the database manager [104] of the system [100] to
10 maintain a first database [108] and a cache database [110]. The first database [108]
comprises one or more tables based on the one or more datasets. Each table from the one or more tables comprises one or more first data values. The one or more first data values correspond to values assigned to the one or more datasets. In addition, the cache database [110] comprises one or more data identifiers based on
15 the one or more tables. Each data identifier from the one or more data identifiers
comprises at least a set of second data values from the one or more first data values. The set of second data values is a subset of values from the one or more first data values that are used for performing the target action for more than a predefined number of times. Further, the instructions which, when executed by one or more
20 units of a system [100], causes the transceiver unit [102] of the system to receive a
retrieve entity request that comprises at least one of a query data identifier and a query data lookup parameter. Further, the instructions which, when executed by one or more units of a system [100], causes an analysis unit [106] of the system [100] to identify one or more target data values associated with the retrieve entity request
25 from at least one of the first database [108] and the cache database [110] based on
at least one of the query data identifier and the query data lookup parameter. Additionally, the instructions which, when executed by one or more units of a system [100], causes the analysis unit [106] of the system [100] to perform the target action associated with the target request based on identifying the one or more
30 target data values from at least one of the first database [108] and the cache database
[110].
30

[0088] As is evident from the above, the present disclosure provides a technically
advanced solution for performing a target action. The present disclosure provides a
dual-database approach, consisting of a primary database (first database [108]) and
5 a cache database [110], to optimize data accessibility and query performance. The
first database [108] serves as the central repository for all datasets, ensuring data
integrity and reliability, while the cache database [110] stores frequently accessed
data to minimize query response times. By strategically leveraging the cache
database [110], the system [100] accelerates data retrieval, particularly for
10 repetitive queries, while robust synchronization mechanisms ensure consistency
between both the databases. The dual-database approach of the present disclosure provides scalability, flexibility, and enhanced user experience, making it a technically advanced solution for managing data-intensive applications.
15 [0089] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to
20 be understood that the foregoing descriptive matter to be implemented is illustrative
and non-limiting.
[0090] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented
25 interchangeably. While specific embodiments may disclose a 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
30 the intended functionality described herein, are considered to be encompassed within the
scope of the present disclosure.
31

We Claim:
1. A method for performing a target action, the method comprising:
- receiving, by a transceiver unit [102], a target action request;
5 - maintaining, by a database manager [104], one or more datasets comprising
a set of data values, wherein each dataset from the one or more datasets is associated with one or more dataset parameter;
- maintaining, by the database manager [104], a first database [108]
comprising one or more tables based on the one or more datasets, wherein
10 each table from the one or more tables comprises one or more first data
values, wherein the one or more first data values correspond to values assigned to the one or more datasets;
- maintaining, by the database manager [104], a cache database [110]
comprising one or more data identifiers based on the one or more tables,
15 wherein each data identifier from the one or more data identifiers comprises
at least a set of second data values from the one or more first data values, wherein the set of second data values is a subset of values from the one or more first data values that are used for performing the target action for more than a predefined number of times;
20 - receiving, by the transceiver unit [102], a retrieve entity request, wherein
the retrieve entity request comprises at least one of a query data identifier and a query data lookup parameter;
- identifying, by an analysis unit [106], one or more target data values
associated with the retrieve entity request from at least one of the first
25 database [108] and the cache database [110] based on at least one of the
query data identifier and the query data lookup parameter; and
- performing, by the analysis unit [106], the target action associated with the
target action request based on identifying the one or more target data values
from at least one of the first database [108] and the cache database [110].
32

2. The method as claimed in claim 1, wherein the target action request
corresponds to at least one of: a data creation request, a data search request,
a data management request or a data update request.
3. The method as claimed in claim 1, wherein the one or more data identifiers
5 is associated with at least: a customer, a product catalogue data, a master
reference data, a customer invoicing data, a billing details dataset, and a geographical information.
4. The method as claimed in claim 1, wherein the query data identifier is a
unique identifier assigned to a particular query by the database manager
10 [104].
5. The method as claimed in claim 1, wherein the query data lookup parameter
is at least one of a data filter parameter, a data paging parameter, a data
sorting parameter, and a data wildcard search parameter.
6. The method as claimed in claim 1, wherein the target action is at least one
15 of a key value fetch action, a data filtering action, a data paging action, and
a data sorting action.
7. The method as claimed in claim 6, wherein the one or more target data
values associated with at least the key value fetch action is identified from
the cache database [110], and the one or more target data values associated
20 with at least one of the data filtering action, the data paging action, and the
data sorting action is identified from the first database [108].
8. The method as claimed in claim 1 further comprising:
- maintaining, by the database manager [104], a consistency between the first
database [108] and the cache database [110] for providing data
25 synchronization.
9. The method as claimed in claim 8, wherein maintaining the consistency
between the first database [108] and the cache database [110] further
comprises at least:
- data mapping between the first database [108] and the cache database [110];
30 - data transformation between the first database [108] and the cache database
[110]; and
33

- normalizing data structures to eliminate redundancy across the first database
[108] and the cache database [110].
10. A system for performing a target action, the system comprises:
- a transceiver unit [102] configured to:
5 o receive, a target action request;
- a database manager [104] connected to at least the transceiver unit [102],
the database manager [104] configured to:
o maintain one or more datasets, wherein the one or more datasets
comprises a set of data values, and wherein each dataset from the
10 one or more datasets is associated with one or more dataset
parameter;
o generate a first database [108] based on the one or more datasets,
wherein the first database [108] comprises one or more tables, and
wherein each table from the one or more tables comprises one or
15 more first data values, wherein the one or more first data values
correspond to values assigned to the one or more datasets; and
o generate a cache database [110] based on the one or more tables,
wherein the cache database [110] comprises one or more data
identifiers, and wherein each data identifier from the one or more
20 data identifiers comprises at least a set of second data values from
the one or more first data values, wherein the set of second data
values is a subset of values from the one or more first data values
that are used for performing the target action for more than a
predefined number of times;
25 wherein the transceiver unit [102] is further configured to receive, a retrieve
entity request, wherein the retrieve entity request comprises at least one of
a query data identifier and a query data lookup parameter;
- an analysis unit [106] connected to at least the transceiver unit [102] and the
database manager [104], the analysis unit [106] configured to:
30 o identify one or more target data values associated with the retrieve
entity request from at least one of the first database [108] and the
34

cache database [110] based on at least one of the query data identifier
and the query data lookup parameter; and
o perform the target action associated with the target action request
based on the identification the one or more target data values from
5 at least one of the first database [108] and the cache database [110].
11. The system as claimed in claim 10, wherein the target action request
corresponds to least one of: a data creation request, a data search request, a
data management request or a data update request.
12. The system as claimed in claim 10, wherein the one or more data identifiers
10 is associated with at least: a customer, a product catalogue data, a master
reference data, a customer invoicing data, a billing details dataset, and a geographical information.
13. The system as claimed in claim 10, wherein the query data identifier is a
unique identifier assigned to a particular query by the database manager
15 [104].
14. The system as claimed in claim 10, wherein the query data lookup parameter
is at least one of a data filter parameter, a data paging parameter, a data
sorting parameter, and a data wildcard search parameter.
15. The system as claimed in claim 10, wherein the target action is at least one
20 of a key value fetch action, a data filtering action, a data paging action, and
a data sorting action.
16. The system as claimed in claim 15, wherein the one or more target data
values associated with at least a key value fetch action are identified from
the cache database [110], and wherein the one or more target data values
25 associated with at least one of a data filtering action, a data paging action,
and a data sorting action are identified from the first database [108].
17. The system as claimed in claim 10, wherein the database manager [104] is
further configured to maintain a consistency between the first database
[108] and the cache database [110] to provide data synchronization.

18. The system as claimed in claim 17, wherein, to maintain the consistency
between the first database [108] and the cache database [110] the database
manager [104] is further configured to perform at least:
- data mapping between the first database [108] and the cache database [110];
5 - data transformation between the first database [108] and the cache database
[110]; and
- normalizing data structures to eliminate redundancy across the first database
[108] and the cache database [110].
19. A user equipment (UE) configured to perform a target action, the UE
10 comprises:
- a memory; and
- a processor connected to the memory, wherein the processor is configured to send a target action request to a system [100], wherein the wherein the target action request corresponds to a data creation request, and
15 wherein system [100] performs the target action based on:
- maintaining, by a database manager [104] of the system [100], one
or more datasets comprising a set of data values, wherein each dataset from
the one or more datasets is associated with one or more dataset parameter;
- maintaining, by the database manager [104] of the system [100], a
20 first database [108] comprising one or more tables based on the one or more
datasets, wherein each table from the one or more tables comprises one or more first data values, wherein the one or more first data values correspond to values assigned to the one or more datasets;
- maintaining, by the database manager [104] of the system [100], a
25 cache database [110] comprising one or more data identifiers based on the
one or more tables, wherein each data identifier from the one or more data
identifiers comprises at least a set of second data values from the one or
more first data values, wherein the set of second data values is a subset of
values from the one or more first data values that are used for performing
30 the target action for more than a predefined number of times;

- receiving, by a transceiver unit [102] of the system [100], a retrieve
entity request, wherein the retrieve entity request comprises at least one of
a query data identifier and a query data lookup parameter;
- identifying, by an analysis unit [106] of the system [100], one or
5 more target data values associated with the retrieve entity request from at
least one of the first database [108] and the cache database [110] based on at least one of the query data identifier and the query data lookup parameter; and
- performing, by the analysis unit [106] of the system [100], the target
10 action associated with the target action request based on identifying the one
or more target data values from at least one of the first database [108] and the cache database [110].