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 AUTOMATICALLY RETRIEVING A TARGET PLAN OFFERING 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 AUTOMATICALLY RETRIEVING A TARGET PLAN OFFERING DATA
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to database management systems. More particularly, embodiments of the present disclosure relate method and system for automatically retrieving a target plan offering 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 database management systems, there is a requirement to handle operations where a data is required to be fetched frequently, but the same operations does not need to be modified frequently. For such requests, every time a request comes for fetching the data, the databases are searched, and the data is retrieved from the databases. The larger the size of the database, larger the number of computations may be made. The technical problem in the prior known solutions lies in the process of handling requests that come to caching units which are used for fast retrieval of highly sought entities. That is, as mentioned above, there are several operations for which update/create data calls (i.e., the set of commands for updating/creating the data in the database) are relatively low and GET data calls (i.e., the set of commands for fetching the data from the database) are substantially high. Currently, when any such request comes, a large number of computations and database operations are performed, resulting in substantial lag and a detrimental

impact on overall performance of the database management systems. For instance, when examining the underlying tables that may be present in the database (i.e., where the data may be present in the form of tables, i.e., tabular manner, in the database), the existing solutions encounter inefficiencies and unnecessary delays during operations related to database management.
[0004] The systems’ inefficiencies and unnecessary delays during these operations become evident when analyzing the data from the database (for selecting the relevant data to be fetched from the database). These challenges need to be addressed to enhance the efficiency and speed of retrieving consolidated tags related to handling requests, i.e., the requests related to selecting and fetching the relevant data from the database. For example, in case of services offered by a telecom service provider, the provider may give several options/plans to the users to select from, as per the users’ needs. The information related to relevant plan(s) for a user may be termed as a target plan offering data, throughout this disclosure.
[0005] Thus, there exists an imperative need in the art to provide a solution for automatically retrieving a target plan offering data, which the present disclosure aims to address.
SUMMARY OF THE DISCLOSURE
[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 automatically retrieving a target plan offering data. The method comprises receiving, by a transceiver unit, a query plan offering data request, wherein the query plan offering data request comprises at least one query plan offering data identifier. Further, the

method comprises identifying, by an identification unit from a cache database, a target plan offering data identifier associated with the target plan offering data comprising one or more target plan offering values from a set of prestored plan offering data values based on a matching of the query plan offering data identifier and one or more prestored plan offering data identifiers. Further, the method comprises automatically retrieving, by an analysis unit from the cache database, the target plan offering data comprising one or more target plan offering values associated with the query plan offering data request based on the identifying the target plan offering data identifier from the cache database.
[0008] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the transceiver unit, 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 parameters. Further, in this implementation, the method comprises generating, by the analysis unit, a first database comprising one or more tables based on the one or more datasets, wherein at least a plan offering data table from the one or more tables is associated with a plan offering data parameter from the one or more dataset parameters, and wherein the plan offering data table comprises one or more plan offering data values. Further, in this implementation, the method comprises generating, by the analysis unit, the cache database comprising the one or more prestored plan offering data identifiers based on the plan offering data table, wherein each prestored plan offering data identifier from the one or more prestored plan offering data identifiers are associated with at least the set of prestored plan offering data values from the one or more plan offering data values.
[0009] In an exemplary aspect of the present disclosure, the one or more prestored plan offering data values associated with each prestored plan offering data identifier is at least one of a plan billing type data value associated with said prestored plan offering data identifier, a plan stacked queue data value associated with said prestored plan offering data identifier, a plan applicability data value associated

with said prestored plan offering data identifier, a plan sale channel data value associated with said prestored plan offering data identifier, and a geographical location data value associated with said prestored plan offering data identifier.
[0010] In an exemplary aspect of the present disclosure, the target plan offering data comprising the one or more target plan offering values is at least one of a plan billing type data value associated with the target plan offering data identifier, a plan stacked queue data value associated with the target plan offering data identifier, a plan applicability data value associated with the target plan offering data identifier, a plan sale channel data value associated with the target plan offering data identifier, and a geographical location data value associated with the target plan offering data identifier.
[0011] In an exemplary aspect of the present disclosure, the target plan offering data associated with the target plan offering data identifier is automatically retrieved in a consolidated predefined format.
[0012] Another aspect of the present disclosure may relate to a system for automatically retrieving a target plan offering data. The system comprises a transceiver unit configured to receive, a query plan offering data request, wherein the query plan offering data request comprises at least one query plan offering data identifier. Further, the system comprises an identification unit connected to at least the transceiver unit. The identification unit is configured to identify, from a cache database, a target plan offering data identifier associated with the target plan offering data comprising one or more target plan offering values from a set of predefined plan offering data values based on a matching of the query plan offering data identifier and one or more prestored plan offering data identifiers. Further, the system comprises an analysis unit connected at least to the identification unit. The analysis unit is configured to automatically retrieve, from the cache database, the target plan offering data comprising the one or more target plan offering values

associated with the query plan offering data request based on the identification of the target plan offering data identifier from the cache database.
[0013] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for automatically retrieving a target plan offering 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 query plan offering data request, wherein the query plan offering data request comprises at least one query plan offering data identifier. Further, the instructions include executable code which, when executed causes an identification unit of the system to identify, from a cache database, a target plan offering data identifier associated with the target plan offering data comprising one or more target plan offering values from a set of predefined plan offering data values based on a matching of the query plan offering data identifier and one or more prestored plan offering data identifiers. Further, the instructions include executable code which, when executed causes an analysis unit of the system to automatically retrieve, from the cache database, the target plan offering data comprising the one or more target plan offering values associated with the query plan offering data request based on the identification of the target plan offering data identifier from the cache database.
[0014] Yet another aspect of the present disclosure may relate to a User Equipment (UE). The UE comprises: 1) a transmitter, configured to transmit to a system a request for automatic retrieval of a target plan offering data; and 2) a receiver, configured to receive from the system, a response to the request, wherein the response comprises an indication of the automatic retrieval of a target plan offering data. The response is generated by the system based on: 1) receiving, by a transceiver unit, a query plan offering data request, wherein the query plan offering data request comprises at least one query plan offering data identifier, 2) identifying, by an identification unit from a cache database, a target plan offering data identifier associated with the target plan offering data comprising one or more target plan offering values from a set of prestored plan offering data values based

on a matching of the query plan offering data identifier and one or more prestored plan offering data identifiers, and 3) automatically retrieving, by an analysis unit from the cache database, the target plan offering data comprising one or more target plan offering values associated with the query plan offering data request based on the identifying the target plan offering data identifier from the cache database.
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 method and a system that facilitates pre-population of plan offering data with key value pair in a cache database.
[0017] It is another object of the present disclosure to provide a method and a system that facilitates fetching of the plan offering data from the cache database with reduced computations.
[0018] It is yet another object of the present disclosure to provide a method and a system that facilitates high performance of the system by avoiding unnecessary computations, reducing computation time and database dips.
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 automatically retrieving a target plan offering data, in accordance with exemplary implementations of the present disclosure.
[0022] FIG. 3 illustrates a method flow diagram for automatically retrieving a target plan offering data, in accordance with exemplary implementations of the present disclosure.
[0023] FIG. 4 illustrates a method flow diagram for an exemplary scenario for automatically retrieving a target plan offering data, in accordance with exemplary implementations of the present disclosure.
[0024] FIG. 5 illustrates an exemplary system architecture of a system for automatically retrieving a target plan offering 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. 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 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.
[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 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 serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[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 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 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 communication device” may be any electrical, electronic, and/or computing device or equipment, capable of implementing the one or more 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 of implementing the one or more features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the one or more features of the present disclosure.
[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 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 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 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.
[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, 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, 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. As disclosed, when any request for data retrieval from one or more databases comes, a large number of computations and database operations are performed, resulting in substantial lag and a detrimental impact on overall performance. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of automatically retrieving a target plan offering data, especially for operations for which update/create data calls are relatively low and GET data calls are substantially high.
[0038] Fig. 1 illustrates an exemplary block diagram of a computing device [100] 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 [100] may implement a method for automatically retrieving a target plan offering data utilising the system of the present disclosure. In another implementation, the computing device [100] itself implements the method for automatically retrieving a target plan offering data using one or more units configured within the computing device [100], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
[0039] The computing device [100] may include a bus [102] or other communication mechanism for communicating information, and a hardware processor [104] coupled with bus [102] for processing information. The hardware processor [104] may be, for 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 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 [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 instructions for the processor [104].
[0040] 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 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 [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]. This 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 the device to specify positions in a plane.
[0041] 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 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, 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 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.
[0042] 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 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, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0043] The computing device [100] can send messages and receive data, including program code, through the network(s), the network link [120] and the 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 execution.

[0044] Referring to FIG. 2, an exemplary block diagram of a system [200] for
automatically retrieving a target plan offering data, is shown, in accordance with
the exemplary implementations of the present disclosure. The system [200]
comprises at least one transceiver unit [202], at least one identification unit [204],
5 at least one cache database [206], and at least one analysis unit [208]. Also, all of
the components/ units of the system [200] are assumed to be connected to each
other unless otherwise indicated below. Also, in FIG. 2 only a few units are shown,
however, 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
10 of the present disclosure. Further, in an implementation, the system [200] may be
present in a server or a network entity. In yet another implementation, the system [200] may be in connection with the server/ network entity and the user equipment (UE).
15 [0045] The system [200] is configured for automatically retrieving a target plan
offering data, with the help of the interconnection between the components/units of the system [200]. Here, the target plan offering data refers to a plan that may be shown to a user based on certain requirements of the user. For example, a user has a requirement of more internet data as compared to calls and messages, then the
20 target plan offering data may comprise one or more plans that offer more internet
data as compared to calls and messages. In other words, the target plan offering data comprises one or more subscription plans for the user.
[0046] Particularly, the transceiver unit [202] is configured to receive one or more
25 datasets comprising a set of data values, wherein each dataset from the one or more
datasets is associated with one or more dataset parameters. The one or more datasets
may refer to the raw data that is a bulk data comprising information about customer,
product catalog data, master reference data, customer invoicing data, billing details,
geographical information, etc. The dataset parameters are the parameters in a raw
30 data, i.e., the one or more datasets, that may be initially received for creating one or
more tables. These dataset parameters together form one or more datasets. Further,
15

the one or more tables may be created using the dataset parameters. Furthermore,
the one or more tables based on the one or more datasets may be used to create at
least one of a first database and a cache database [206]. Also, the first database may
be, for example, a Structured Query Language based (SQL) database, or any such
5 database, as may be appreciated by a person skilled in the art, that may be useful
for implementing the features of the present disclosure.
[0047] After the transceiver unit [202] receives the one or more datasets, the analysis unit [208] is configured to generate a first database comprising the one or
10 more tables based on the one or more datasets, wherein at least a plan offering data
table from the one or more tables is associated with a plan offering data parameter from the one or more dataset parameters, and wherein the plan offering data table comprises one or more plan offering data values. The one or more tables in the first database may be created using the raw data and may comprise complete data of all
15 the plans and/or products offered to the users by a provider / service provider. Also,
the plan offering data table may comprise values (i.e., plan offering data values) related to various parameters related to plans that may be offered to one or more users. The plan offering data values may be the values associated with each of the one or more dataset parameters. In an example, the one or more tables may
20 comprise, but not limited to, a plan offering table, a sales channel mapping table, a
geographic location master table, and a segmentation table etc. Furthermore, in an implementation the plan offering data values are the values which are stored for the one or more dataset parameters. For example, a dataset parameter is “location,” and value is “Delhi,” “Mumbai” etc.
25
[0048] Further, the analysis unit [208] is configured to generate a cache database [206] comprising the one or more prestored plan offering data identifiers based on the plan offering data table, wherein each prestored plan offering data identifier from the one or more prestored plan offering data identifiers is associated with at
30 least the set of prestored plan offering data values from the one or more plan
offering data values. The prestored plan offering data identifiers, in an
16

implementation, may be generated at the first database and transmitted from the
first database to the cache database. The prestored plan offering data identifiers
maybe plan identifiers (plan IDs) that define, for example, the subscription plan for
users. For example, Data100 plan, CallUnlimited Plan, Roaming500 Plan, etc. For
5 example, various plans for the users may be developed and pre-stored in a database.
For example, the Data100 plan may comprise offering 100GB (gigabytes) of internet data to users for a month at 100 Mbps (megabits per second) speed, and the CallUnlimited Plan may offer users with unlimited calling for a year, etc. Here, in this above exemplary Data100 plan, a parameter may be data speed and the value
10 for the data speed parameter (that is one of the plan offering data values) may be
100 Mbps. Similarly, another parameter may be data amount and the value for data amount parameter (that is one of the plan offering data values) may be 100 GB. Also, for example, this Data100 plan is available for Rs. 200 per month. Then the plan billing type data value that is associated with the plan offering data identifier
15 (i.e., Data100 plan, in this example) is Rs. 200. In an implementation, these plans
(i.e., the subscription plans) along with all the values of the related parameters may be pre-stored in the database, and fetched according to the need, or the query of the user. Also, each plan may be associated with an identifier, for providing to the users when needed. Similarly, there can be other values associated with other parameters
20 such as plan applicability data parameter, plan sales channel data parameter. Also,
the plan offering data values may be according to the plan that is prepared for a set of users, say for example, users located in a geographical area, and the set of pre-stored plan offering data values may be the set of all areas. Further, the prestored plan offering data values may be stored in a consolidated form in a pre-defined
25 format. Further, this consolidated pre-defined format may be the javascript object
notation (JSON) format. Furthermore, the plan offering data may be associated with the plan offering data identifiers (i.e., the prestored plan offering data identifiers) and may be pre-populated in the cache database. Here, the plan offering data for only those of the one or more tables may be saved in the cache database [206] for
30 which CREATE/ UPDATE calls are low and GET calls are high. Moreover, the
one or more prestored plan offering data values associated with each prestored plan
17

offering data identifier is at least one of a plan billing type data value associated
with said prestored plan offering data identifier, a plan stacked queue data value
associated with said prestored plan offering data identifier, a plan applicability data
value associated with said prestored plan offering data identifier, a plan sale channel
5 data value associated with said prestored plan offering data identifier, and a
geographical location data value associated with said prestored plan offering data identifier. Moreover, both the databases i.e., the first database and the cache database are in reconciliation with each other i.e., the data in both the databases may remain consistent with each other.
10
[0049] After, the creation of the databases the transceiver unit [202] is further configured to receive, a query plan offering data request, wherein the query plan offering data request comprises at least a query plan offering data identifier. The query plan offering the data identifier may be the query request that is received by
15 the transceiver unit [202] with a plan identifier (plan ID). In an example, a user may
input a query or search for a relevant plan available with a provider. For this, the user may input the query using a user interface. This query of the user may be received by the transceiver unit [202] as the query plan offering data request. For example, a user may input the query or select via a user interface, about a plan, i.e.,
20 Data100 plan. Here, the user may want to look for the values that may be provided
to the user in case the user chooses this plan (i.e., subscription plan). The values may be for example, 100 GB of data at a speed of 100 Mbps for 1 month.
[0050] The identification unit [204] is connected to at least the transceiver unit
25 [202]. After, the transceiver unit [202] receives the query plan offering data request,
the identification unit [204] is configured to identify, from the cache database [206],
a target plan offering data identifier associated with the target plan offering data
comprising one or more target plan offering values from a set of prestored plan
offering data values based on a matching of the query plan offering data identifier
30 and one or more prestored plan offering data identifiers. This matching, in an
implementation, may be based on generally known matching or searching
18

techniques, such as linear search, binary search, semantic search, etc. The target
plan identifier is identified by the identification unit [204], wherein the target plan
identifier is pre-stored/ pre-populated in the cache database [206] and the target plan
offering data identifier is identified according to query plan offering data identifier.
5 In an implementation, the target plan offering data identifier may be same as the
query plan offering data identifier. In another implementation, the query plan offering data identifier may be mapped to a single target plan offering data identifier, and the target plan offering data identifier may be identified based on this mapped query plan offering data identifier. For example, for the purpose of
10 identification of the target plan offering data identifier associated with the target
plan offering data, the identification unit may use input parameters and/or selection from the user. The input parameters, for example, may be matched with the parameters in the available data, i.e., values or parameters provided by the user in query may be searched in the prestored plan offering data values, and relevant plan
15 offering data identifier(s) may be identified. Further the target plan offering data
comprises the one or more target plan offering values. The one or more target plan offering values is at least one of a plan billing type data value associated with the target plan offering data identifier, a plan stacked queue data value associated with the target plan offering data identifier, a plan applicability data value associated
20 with the target plan offering data identifier, a plan sale channel data value associated
with the target plan offering data identifier, and a geographical location data value associated with the target plan offering data identifier.
[0051] The analysis unit [208] connected at least to the identification unit [204].
25 After identifying the target plan data identifier, the analysis unit [208] is configured
to automatically retrieve, from the cache database [206], the target plan offering data comprising the one or more target plan offering values associated with the query plan offering data request based on the identifying the target plan offering data identifier. Therefore, as soon as the transceiver unit [202] receives the query
30 plan offering data identifier, the identification unit [204] identifies the target plan
offering data identifier based on a matching of the query plan offering data
19

identifier, and the analysis unit [208] retrieves the target plan offering data
according to the query plan identifier offering data identifier. Moreover, the target
plan offering data associated with the target plan offering data identifier is
automatically retrieved in a consolidated predefined format, wherein the
5 consolidated predefined format may be the javascript object notation (JSON)
format. Thus, the data when retrieved from the database, may further be shown to the user via a user interface. Also, here, automatically retrieving refers to the process of retrieving a relevant information for a user base on the query of the user.
10 [0052] Referring to FIG. 3, an exemplary method flow diagram [300] for
automatically retrieving a target plan offering data, in accordance with exemplary implementations of 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
15 present disclosure. Also, as shown in Figure 3, the method [300] starts at step 302
and goes to step 304. Here, the target plan offering data refers to a plan that may be shown to a user based on certain requirement of the user. For example, a user has a requirement of more internet data as compared to calls and messages, then the target plan offering data may comprise one or more plans that offer more internet data as
20 compared to calls and messages. In other words, the target plan offering data
comprises one or more subscription plans for the user.
[0053] At step 304, the method [300] comprises receiving, by the transceiver unit [202], one or more datasets comprising a set of data values, wherein each dataset
25 from the one or more datasets is associated with one or more dataset parameters.
The one or more datasets may refer to the raw data that is a bulk data comprising information about customer, product catalog data, master reference data, customer invoicing data, billing details, geographical information, etc. The dataset parameters are the parameters in a raw data, i.e., the one or more datasets, that may
30 be initially received for creating one or more tables. These dataset parameters
together form one or more datasets. Further, the one or more tables may be created
20

using the dataset parameters. Furthermore, the one or more tables based on the one
or more datasets may be used to create at least one of a first database and a cache
database [206]. Also, the first database may be, for example, a SQL based database,
or any such database, as may be appreciated by a person skilled in the art, that may
5 be useful for implementing the features of the present disclosure.
[0054] After the transceiver unit [202] receives the one or more datasets, at step 306, the method comprises generating, by the analysis unit [208], a first database comprising the one or more tables based on the one or more datasets, wherein at
10 least a plan offering data table from the one or more tables is associated with a plan
offering data parameter from the one or more dataset parameters, and wherein the plan offering data table comprises one or more plan offering data values. The one or more tables in the first database may be created using the raw data and may comprise complete data of all the plans and/or products offered to the users by a
15 provider / service provider. Also, the plan offering data table may comprise values
(i.e., plan offering data values) related to various parameters related to plans that may be offered to one or more users. The plan offering data values may be the values associated with each of the one or more dataset parameters. In an example, the one or more tables may comprise, but not limited to, a plan offering table, a
20 sales channel mapping table, a geographic location master table, and a segmentation
table etc. Furthermore, in an implementation the plan offering data values are the values which are stored for the one or more dataset parameters. For example, a dataset parameter is “location,” and value is “Delhi,” “Mumbai” etc.
25 [0055] Further, at step 308, the method comprises generating, by the analysis unit
[208], the cache database [206] comprising the one or more prestored plan offering data identifiers based on the plan offering data table, wherein each prestored plan offering data identifier from the one or more prestored plan offering data identifiers is associated with at least the set of prestored plan offering data values from the one
30 or more plan offering data values. The prestored plan offering data identifiers, in an
implementation, may be generated at the first database and transmitted from the
21

first database to the cache database. The prestored plan offering data identifiers
maybe plan identifiers (plan IDs) that define, for example, the subscription plan for
users. For example, Data100 plan, CallUnlimited Plan, Roaming500 Plan, etc. For
example, various plans for the users may be developed and pre-stored in a database.
5 For example, the Data100 plan may comprise offering 100GB (gigabytes) of
internet data to users for a month at 100 Mbps (megabits per second) speed, and the CallUnlimited Plan may offer users with unlimited calling for a year, etc. Here, in this above exemplary Data100 plan, a parameter may be data speed and the value for the data speed parameter (that is one of the plan offering data values) may be
10 100 Mbps. Similarly, another parameter may be data amount and the value for data
amount parameter (that is one of the plan offering data values) may be 100 GB. Also, for example, this Data100 plan is available for Rs. 200 per month. Then the plan billing type data value that is associated with the plan offering data identifier (i.e., Data100 plan, in this example) is Rs. 200. In an implementation, these plans
15 (i.e., the subscription plans) along with all the values of the related parameters may
be pre-stored in the database, and fetched according to the need, or the query of the user. Also, each plan may be associated with an identifier, for providing to the users when needed. Similarly, there can be other values associated with other parameters such as, but not limited to, plan applicability data parameter (that may indicate
20 validity of the plan, etc.), plan sales channel data parameter (that may indicate a
channel used to sell the product, such as a web platform or a mobile application, etc.). Also, the plan offering data values may be according to the plan that is prepared for a set of users, say for example, users located in a geographical area, and the set of pre-stored plan offering data values may be the set of all areas.
25 Further, the prestored plan offering data values may be stored in a consolidated
form in a pre-defined format. Further, this consolidated pre-defined format may be the javascript object notation (JSON) format. Furthermore, the plan offering data may be associated with the plan offering data identifiers (i.e., the prestored plan offering data identifiers) and may be pre-populated in the cache database. Here, the
30 plan offering data for only those of the one or more tables may be saved in the cache
database [206] for which CREATE/ UPDATE calls are low and GET calls are high.
22

Moreover, the one or more prestored plan offering data values associated with each
prestored plan offering data identifier is at least one of a plan billing type data value
associated with said prestored plan offering data identifier, a plan stacked queue
data value associated with said prestored plan offering data identifier, a plan
5 applicability data value associated with said prestored plan offering data identifier,
a plan sale channel data value associated with said prestored plan offering data
identifier, and a geographical location data value associated with said prestored plan
offering data identifier. Moreover, both the databases i.e., the first database and the
cache database are in reconciliation with each other i.e., the data in both the
10 databases may remain consistent with each other.
[0056] Thereafter, at step 310, the method comprises receiving, by a transceiver unit [202], a query plan offering data request, wherein the query plan offering data request comprises at least one query plan offering data identifier. The query plan
15 offering the data identifier may be the query request that is received by the
transceiver unit [202] with a plan identifier (plan ID). In an example, a user may input a query or search for a relevant plan available with a provider. For this, the user may input the query using a user interface. This query of the user may be received by the transceiver unit [202] as the query plan offering data request.
20
[0057] Further, at step 312, the method comprises identifying, by an identification unit [204] from the cache database [206], a target plan offering data identifier associated with the target plan offering data comprising one or more target plan offering values from a set of prestored plan offering data values based on a matching
25 of the query plan offering data identifier and one or more prestored plan offering
data identifiers. This matching, in an implementation, may be based on generally known matching or searching techniques, such as linear search, binary search, semantic search, etc. The target plan identifier is identified by the identification unit [204], wherein the target plan identifier is pre-stored/ pre-populated in the cache
30 database [206] and the target plan offering data identifier is identified according to
query plan offering data identifier. In an implementation, the target plan offering
23

data identifier may be same as the query plan offering data identifier. In another
implementation, the query plan offering data identifier may be mapped to a single
target plan offering data identifier, and the target plan offering data identifier may
be identified based on this mapped query plan offering data identifier. For example,
5 for the purpose of identification of the target plan offering data identifier associated
with the target plan offering data, the identification unit may use input parameters and/or selection from the user. The input parameters, for example, may be matched with the parameters in the available data, i.e., values or parameters provided by the user in query may be searched in the prestored plan offering data values, and
10 relevant plan offering data identifier(s) may be identified. Further the target plan
offering data comprises the one or more target plan offering values. The one or more target plan offering values is at least one of a plan billing type data value associated with the target plan offering data identifier, a plan stacked queue data value associated with the target plan offering data identifier, a plan applicability
15 data value associated with the target plan offering data identifier, a plan sale channel
data value associated with the target plan offering data identifier, and a geographical location data value associated with the target plan offering data identifier.
[0058] Moreover, at step 314, the method comprises automatically retrieving, by
20 an analysis unit [208] from the cache database [206], the target plan offering data
comprising the one or more target plan offering values associated with the query
plan offering data request based on the identifying the target plan offering data
identifier. Therefore, as soon as the transceiver unit [202] receives the query plan
offering data identifier, the identification unit [204] identifies the target plan
25 offering data identifier based on a matching of the query plan offering data
identifier, and the analysis unit [208] retrieves the target plan offering data
according to the query plan identifier offering data identifier. Moreover, the target
plan offering data associated with the target plan offering data identifier is
automatically retrieved in a consolidated predefined format, wherein the
30 consolidated predefined format may be the javascript object notation (JSON)
format. Thus, the data when retrieved from the database, may further be shown to
24

the user via a user interface. Also, here, automatically retrieving refers to the process of retrieving a relevant information for a user base on the query of the user.
[0059] Referring, FIG. 4 illustrates a method flow diagram for an exemplary
5 scenario for automatically retrieving a target plan offering data in accordance with
exemplary implementations of the present disclosure. In an implementation the process is performed by the system [200].
[0060] The process begins, at the step S1, wherein the system [200] receives a data
10 creation request. The data may be sent to the system [200] from functional systems.
These functional systems, for example, may be, but not limited to, CRM (Customer
Relationship Management), EPC (Enterprise Product Catalogue) and GIS
(Geographical Information System). Here, the CRM data may relate to a
combination of practices, strategies and technologies used by the companies for
15 managing and analysing the customer interaction and data throughout the customer
lifecycle, the EPC data may relate to a combination commercial and technical
products, wherein the commercial products may be seen by the customer and the
technical products may be seen by the back-end server, and the GIS data may relate
to a systematic integration of hardware and software for capturing, storing,
20 displaying, updating manipulating and analysing spatial data.
[0061] At step S2, after, the system [200] receives the request for creation of data,
the system [200] persists the data into first database, i.e., the system [200] stores
the data at first database (for instance at SQL based database). In an
25 implementation, the system [200] continuously and/or frequently persists data into
the first database without receiving the request for creation of the data.
[0062] Further, at the step S3, the process notifies the data in the Cache database
[206]. During notifying the data in the cache database [206] the process also
30 comprises consolidation of data from first database by dipping into the required
tables (i.e., the tables of the data in the first database) using different algorithms and
25

number of computations for different types of data. Further, the system [200]
prepares a singular JSON for each record containing all JSON tags for the data.
This JSON will be useful when the query request for fetching the data is received,
where the request comprises the identifier and the data is fetched only with the
5 identifier without dipping into the first database, thereby decreasing the numbers of
computations for each query request. Thus, the data, i.e., the singular JSON containing all JSON tags for the data, may be populated/stored in the cache database [206]. The data stored in the first database and the cache database is in reconciliation with each other i.e., the data remains consistent in both the databases. 10
[0063] Further, in the process at step S4 the system [200], it is checked whether the request received at the transceiver unit [202] contains filters, pagination and sorting, or the request contains identifier(s) for fetching data from the singular JSON file.
15 [0064] If the request includes the filters, pagination, and sorting the records will be
fetched from the first database as shown at step S5. Moreover, if the system retrieves request containing identifiers(s), the records will be fetched from the cache database [206] with identifiers in the request as Key as shown at step S6.
20 [0065] Finally, at step S7, the system [200] returns the response from the at least
one of the first database and the cache database and the process ends.
[0066] FIG. 5 illustrates an exemplary implementation environment [500] where a system [200] is configured for automatically retrieving a target plan offering data,
25 in accordance with exemplary implementations of the present disclosure. In a
preferred embodiment, the implementation environment [500] comprises a plurality of components. For example, and by no way limiting the scope of the present subject matter, the implementation environment [500] comprises an Enterprise Product Catalogue (EPC) [502], a Fulfilment management system (FMS) [504], a
30 subscription engine [514], a plurality of channels [506], a load balancer [508], a
group server entity [510] comprising a plurality of instances, and a set of database
26

[512]. The set of databases may include a database 1, database 2, and a database 3. The EPC [502] is a centralised data repository which drives Business Support System (BSS) telecom operations and some network nodes for e.g., 5G charging system, called Policy Control Function (PCF) etc. 5
[0067] The group server entity [510] may comprise an Operations and Maintenance
(OAM) instance which deals with the maintenance and operation of all the
microservice instances and communicates with outer products related to alarms,
Key Performance Indicators (KPIs) or other management, and health check-up
10 information. Further, the group server entity [510] may comprise a Data
Information Framework (DIF) instance.
[0068] The channels [506] are configured to provide input data to the group server entity [510] through a load balancer [508]. In an embodiment, some examples of
15 the channels [506] include but are not limited to a channel 1 [506A], a channel 2
[506B], a channel 3 [506C] and a CRM user interface (UI) [506D]. The channels [506] which are tightly coupled to the CRM e.g. CRM User Interface (UI) communicate directly via the load balancer [508] while other systems which belong to different products communicate to the group server entity [510] using the FMS
20 [504]. FMS is a middleware which links two different products and performs
language translations or workflow management. For example, if one product understands Simple Object Access Protocol (SOAP) protocol while the other one understands RESTful services, the FMS [504] translate the messages between these 2 nodes and ensure seamless communication. The group server entity [510] is also
25 connected with the FMS [504], SMP (Service Management Platform) [516], and
CRM server [518]. The DIF instance may comprise a copy of the CRM server [518], EPC, and Geographical Information System (GIS) which caches the business data and provides API for fast access. The SMP [516] deals with the installation processes at customer premises, handling repair mechanism and technician visit to
30 network sites.
27

[0069] In a preferred embodiment, an admin user operates the CRM UI [506D] to trigger the CRUD (Create/ Read/ Update/ Delete) operation on the group server entity [510] via the load balancer [508] or FMS.
5 [0070] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for automatically retrieving a target plan offering 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 query plan offering data request, wherein the query plan offering data
10 request comprises at least one of a query plan offering data identifier. Further, the
instructions include executable code which, when executed causes an identification unit [204] of the system [200] to identify, from a cache database [206] of the system [200], a target plan offering data identifier comprising one or more target plan offering values from a set of predefined plan offering data values based on a
15 matching of the query plan offering data identifier and the one or more prestored
plan offering data identifiers. Further, the instructions include executable code which, when executed causes an analysis unit [208] of the system [200] to automatically retrieve, from the cache database [206], the target plan offering data comprising the one or more target plan offering values associated with the query
20 plan offering data request based on the identification of the target plan offering data
from the cache database [206].
[0071] Further the present disclosure also discloses a User Equipment (UE). The UE comprises: 1) a transmitter, configured to transmit to a system [200] a request
25 for automatic retrieval of a target plan offering data; and 2) a receiver, configured
to receive from the system [200], a response to the request, wherein the response comprises an indication of the automatic retrieval of a target plan offering data. The response is generated by the system [200] based on: 1) receiving, by a transceiver unit [202], a query plan offering data request, wherein the query plan offering data
30 request comprises at least one query plan offering data identifier, 2) identifying, by
an identification unit [204] from a cache database [206], a target plan offering data
28

identifier associated with the target plan offering data comprising one or more target
plan offering values from a set of prestored plan offering data values based on a
matching of the query plan offering data identifier and one or more prestored plan
offering data identifiers, and 3) automatically retrieving, by an analysis unit [208]
5 from the cache database [206], the target plan offering data comprising one or more
target plan offering values associated with the query plan offering data request based on the identifying the target plan offering data identifier from the cache database [206].
10 [0072] As is evident from the above, the present disclosure provides a technically
advanced solution for automatically retrieving a target plan offering data. The present solution facilitates the pre-population of nested JSON data into the Cache DB. A pre-defined set of instructions are employed for each entity, ensuring that the JSON is structured in a nested format with key-value pairs. This pre-population
15 process is performed ahead of runtime, optimizing the system's performance. When
a query request is received during runtime, the Data Information Framework (DIF) simply retrieves the relevant JSON data from the Cache DB and returns it without the need for additional computations or database dips. This approach significantly reduces unnecessary overhead and enhances the overall performance of the system.
20 By minimizing the computational workload and leveraging pre-populated data, the
solution achieves high efficiency and responsiveness in handling query requests.
[0073] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and
25 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 be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
30
29

[0074] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented 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 the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

We Claim:
1. A method for automatically retrieving a target plan offering data, the
method comprising:
- receiving, by a transceiver unit [202], a query plan offering data request, wherein the query plan offering data request comprises at least one query plan offering data identifier;
- identifying, by an identification unit [204] from a cache database [206], a target plan offering data identifier associated with the target plan offering data comprising one or more target plan offering values from a set of prestored plan offering data values based on a matching of the query plan offering data identifier and one or more prestored plan offering data identifiers; and
- automatically retrieving, by an analysis unit [208] from the cache database [206], the target plan offering data comprising one or more target plan offering values associated with the query plan offering data request based on the identifying the target plan offering data identifier from the cache database [206].
2. The method as claimed in claim 1, the method comprising:
- receiving, by the transceiver unit [202], 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 parameters;
- generating, by the analysis unit [208], a first database comprising one or more tables based on the one or more datasets, wherein at least a plan offering data table from the one or more tables is associated with a plan offering data parameter from the one or more dataset parameters, and wherein the plan offering data table comprises one or more plan offering data values; and
- generating, by the analysis unit [208], the cache database [206] comprising the one or more prestored plan offering data identifiers based on the plan

offering data table, wherein each prestored plan offering data identifier from the one or more prestored plan offering data identifiers is associated with at least the set of prestored plan offering data values from the one or more plan offering data values.
3. The method as claimed in claim 1, wherein the one or more prestored plan offering data values associated with each prestored plan offering data identifier is at least one of a plan billing type data value associated with said prestored plan offering data identifier, a plan stacked queue data value associated with said prestored plan offering data identifier, a plan applicability data value associated with said prestored plan offering data identifier, a plan sale channel data value associated with said prestored plan offering data identifier, and a geographical location data value associated with said prestored plan offering data identifier.
4. The method as claimed in claim 1, wherein the target plan offering data comprising the one or more target plan offering values is at least one of a plan billing type data value associated with the target plan offering data identifier, a plan stacked queue data value associated with the target plan offering data identifier, a plan applicability data value associated with the target plan offering data identifier, a plan sale channel data value associated with the target plan offering data identifier, and a geographical location data value associated with the target plan offering data identifier.
5. The method as claimed in claim 4, wherein the target plan offering data associated with the target plan offering data identifier is automatically retrieved in a consolidated predefined format.
6. A system for automatically retrieving a target plan offering data, the system comprising:

• a transceiver unit [202] configured to receive, a query plan offering data request, wherein the query plan offering data request comprises at least one query plan offering data identifier;
• an identification unit [204] connected to at least the transceiver unit [202], the identification unit [204] configured to identify, from a cache database [206], a target plan offering data identifier associated with the target plan offering data comprising one or more target plan offering values from a set of predefined plan offering data values, based on a matching of the query plan offering data identifier and one or more prestored plan offering data identifiers; and
• an analysis unit [208] connected at least to the identification unit [204], the analysis unit [208] configured to automatically retrieve, from the cache database [206], the target plan offering data comprising the one or more target plan offering values associated with the query plan offering data request based on the identification of the target plan offering data identifier from the cache database [206].
7. The system as claimed in claim 6, wherein:
- the transceiver unit [202] is configured to receive 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 parameters;
- the analysis unit [208] is configured to generate a first database comprising one or more tables based on the one or more datasets, wherein at least a plan offering data table from the one or more tables is associated with a plan offering data parameter from the one or more dataset parameters, and wherein the plan offering data table comprises one or more plan offering data values; and
the analysis unit [208] is further configured to generate a cache database [206] comprising the one or more prestored plan offering data identifiers based on the plan offering data table, wherein each prestored plan offering data identifier from the one or more prestored plan offering data identifiers

is associated with at least the set of prestored plan offering data values from the one or more plan offering data values.
8. The system as claimed in claim 6, wherein the one or more prestored plan offering data values associated with each prestored plan offering data identifier is at least one of a plan billing type data value associated with said prestored plan offering data identifier, a plan stacked queue data value associated with said prestored plan offering data identifier, a plan applicability data value associated with said prestored plan offering data identifier, a plan sale channel data value associated with said prestored plan offering data identifier, and a geographical location data value associated with said prestored plan offering data identifier.
9. The system as claimed in claim 6, wherein the target plan offering data comprises the one or more target plan offering values, and wherein the one or more target plan offering values is at least one of a plan billing type data value associated with the target plan offering data identifier, a plan stacked queue data value associated with the target plan offering data identifier, a plan applicability data value associated with the target plan offering data identifier, a plan sale channel data value associated with the target plan offering data identifier, and a geographical location data value associated with the target plan offering data identifier.
10. The system as claimed in claim 9, wherein the target plan offering data associated with the target plan offering data identifier is automatically retrieved in a consolidated predefined format.
11. A User Equipment (UE), the UE comprises:
- a transmitter, configured to transmit to a system [200] a request for automatic retrieval of a target plan offering data; and

- a receiver, configured to receive from the system [100], a response to the request, wherein the response comprises an indication of the automatic retrieval of a target plan offering data, and wherein the response is generated by the system [200] based on:
o receiving, by a transceiver unit [202], a query plan offering data request, wherein the query plan offering data request comprises at least one query plan offering data identifier, o identifying, by an identification unit [204] from a cache database [206], a target plan offering data identifier associated with the target plan offering data comprising one or more target plan offering values from a set of prestored plan offering data values based on a matching of the query plan offering data identifier and one or more prestored plan offering data identifiers, and o automatically retrieving, by an analysis unit [208] from the cache database [206], the target plan offering data comprising one or more target plan offering values associated with the query plan offering data request based on the identifying the target plan offering data identifier from the cache database [206].