DESC: FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR DYNAMIC DATA TRANSFORMATION
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention relates to the field of data analytics and communications between different software and hardware platforms, more particularly relates to a method and system for dynamic data transformation.
BACKGROUND OF THE INVENTION
[0002] Numerous application programming interfaces (“APIs”) are being developed to exchange data and instructions among disparate systems, applications, and computing devices. As systems and applications computing devices using different platforms proliferate, sharing content in one format to a device running a program that is only capable of accessing and displaying content in another format can be challenging. Typically, while dealing with multiple clients in a dynamic data environment, and where data is to be provided to clients, there is often a problem adapting to changing requirements due to lack of uniform data standards.
[0003] For example, if a username is stored in a server database it may be stored in a variable like “username”, but the format of the username as required by a client may be in a different format such as ‘user-name’. Incase such changes need to be made manually; it would be time consuming as well as inefficient. Hence, there is a need to automate such transformation of data in different file formats or versions based on a client requirement. The improved method and system should facilitate intelligent rendering of data for multiple clients.
SUMMARY OF THE INVENTION
[0004] One or more embodiments of the present disclosure provide a method and system for dynamic data transformation.
[0005] In one aspect of the present invention, the system for dynamic transformation is disclosed. The system includes a transceiver configured to receive a data request from an application via one or more Application Programming Interfaces (APIs) to execute the data request. The system further includes a determination unit, configured to determine whether data included in at least one of, the data request and response data pertaining to the execution of the received data request requires transformation. The system further includes an in response to determining, the data included in at least one of, the data request and the response data requires transformation, a transformation unit, configured to, dynamically transform, the data included in at least one of, the data request and the response data based on the determination.
[0006] In an embodiment, the determination unit determines whether data included in at least one of, the data request and a response data pertaining to the execution of the received data request requires transformation, further configured to transmit, the data request to a destination or transmits the response data to the application in response to determining, the data included in at least one of, the data request and the response data is not required to be transformed.
[0007] In an embodiment, the data included in a header, a query, a protocol and body of the data request and the response data are dynamically transformed by the transformation unit.
[0008] In an embodiment, the dynamically transforming data pertains to at least one of, manipulating and converting formats of the data request and the response data.
[0009] In another aspect of the present invention, the method for dynamic data transformation is disclosed. The method includes the step of receiving a data request from an application via one or more Application Programming Interfaces (APIs) to execute the data request. The method further includes the step of determining whether data included in at least one of, the data request and response data pertaining to the execution of the received data request requires transformation. The method further includes the step of in response to determining, the data included in the at least one of, the data request and the response data requires transformation, dynamically transforming, the data included in the at least one of, the data request and the response data based on the determination.
[0010] In another aspect of the invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions are executed by a processor. The processor is configured to receive a data request from an application via one or more Application Programming Interfaces (APIs) to execute the data request. The processor is configured to determine whether data included in at least one of, the data request and response data pertaining to the execution of the received data request requires transformation. The processor is configured to, in response to determining, the data included in at least one of, the data request and the response data requires transformation, dynamically transform, the data included in at least one of, the data request and the response data based on the determination.
[0011] In another aspect of invention, User Equipment (UE) is disclosed. The UE includes one or more primary processors communicatively coupled to one or more processors, the one or more primary processors coupled with a memory. The processor causes the UE to transmit the data request to the one or more processors from the client application via a one or more Application Programming Interfaces (APIs).
[0012] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0014] FIG. 1 is an exemplary block diagram of an environment for dynamic data transformation, according to one or more embodiments of the present invention;
[0015] FIG. 2 is an exemplary block diagram of a system for dynamic data transformation according to one or more embodiments of the present invention;
[0016] FIG. 3 is a schematic representation of a workflow of the system of FIG. 1, according to the one or more embodiments of the present invention;
[0017] FIG. 4 is an exemplary block diagram of an architecture of the system of the FIG. 2, according to one or more embodiments of the present invention;
[0018] FIG. 5 is a signal flow diagram for dynamic data transformation, according to one or more embodiments of the present invention; and
[0019] FIG. 6 is a schematic representation of a method for dynamic data transformation, according to one or more embodiments of the present invention.
[0020] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0021] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0022] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0023] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0024] As per various embodiments depicted, the present invention discloses a method and system for dynamic data transformation.
[0025] FIG. 1 illustrates an exemplary block diagram of an environment 100 for dynamic data transformation, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 102, a server 104, a network 106 and a system 108 communicably coupled to each other for dynamic data transformation.
[0026] As per the illustrated embodiment and for the purpose of description and illustration, the UE 102 includes, but not limited to, a first UE 102a, a second UE 102b, and a third UE 102c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 102 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 102a, the second UE 102b, and the third UE 102c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 102”.
[0027] In an embodiment, the UE 102 is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0028] The environment 100 includes the server 104 accessible via the network 106. The server 104 may include, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0029] The network 106 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 106 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0030] The network 106 may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 106 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0031] The environment 100 further includes the system 108 communicably coupled to the server 104 and the UE 102 via the network 106. The system 108 is configured for dynamic data transformation. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
[0032] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0033] FIG. 2 is an exemplary block diagram of the system 108 for dynamic data transformation, according to one or more embodiments of the present invention.
[0034] As per the illustrated embodiment, the system 108 includes one or more processors 202, a memory 204, a user interface 206, and a database 208. For the purpose of description and explanation, the description will be explained with respect to one processor 202 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 108 may include more than one processors 202 as per the requirement of the network. The one or more processors 202, hereinafter referred to as the processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
[0035] As per the illustrated embodiment, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0036] In an embodiment, the user interface 206 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 206 facilitates communication of the system 108. In one embodiment, the user interface 206 provides a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the UE 102 and the database 208.
[0037] The database 208 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 208 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0038] In an embodiment, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a transceiver 210, a determination unit 212, and a transformation unit 214 communicably coupled to each other for dynamic data transformation.
[0039] The transceiver 210, the determination unit 212, and the transformation unit 214 in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 202. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 204 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[0040] In an embodiment, to dynamically transform the data, the receiving unit 210 is configured to receive a data request from an application via one or more Application Programming Interfaces (APIs) to execute the data request. The data request is a query or command sent from one application to another through an API to retrieve, modify, or manipulate data. The application is a software system that utilizes APIs to interact with other software systems or services to achieve certain goals. The application includes, but not limited to, web application, mobile application, desktop application, or any other type of software that needs to communicate with external services for data or functionality. The API refers to a set of protocols, tools, and definitions that allow different software applications and network functions to communicate with each other.
[0041] Upon receiving the data request from the application, response data pertaining to the execution of the received data request is transmitted to the application. Further, the determination unit 212 is configured to determine whether data included in the at least one of, the data request and the response data pertaining to the execution of the received data request requires transformation. The data refers to the information that is being sent, received, or processed as part of the request. The data can be, but not limited to, query parameters, path parameters, headers, body data, response data. The response data is the information returned by the API in response to the data request. The response data includes, but is not limited to, requested information, processing results, metadata.
[0042] In response to determining, the data included in at least one of, the data request and the response data requires transformation, the transformation unit 214 is configured to dynamically transform the data included in at least one of, the data request and the response data based on the determination. The dynamically transforming data pertains to at least one of, manipulating and converting formats of the data request and the response data. The manipulating the data request and the response refers to the process of altering or modifying the data in various ways to meet specific requirements or improve its usability. The manipulating the data request and response data includes, but not limited to, the filtering data, aggregating data, sorting data, enriching data, cleaning data, transforming data structure, normalizing data. The data included in a header, a query, a protocol and body of the data request and the response data are dynamically transformed by the transformation unit 214.
[0043] In particular, the determination unit 212 determines whether the data included in at least one of, the data request and the response data requires transformation in a header of the data request. If the transformation in the header of the data request is required, the transformation unit 214 transforms the parameters of the header of the data request. For example, if the client application sends the header containing a variable for username in a format like “user-id”, but the destination requires the variable in another format such as “userID”, then the transformation unit 214, is configured to make the desired transformation. For example, the format of the variable user-id is transformed to userID in the header.
[0044] Similarly, the determination unit 212 determines whether the data included in at least one of, the data request and the response data requires transformation in a query parameter of the data request. For example, if a destination is sending a Query Parameter in a first format like “user-name”, but the client application requires the query parameter in a second format like “UserName”, then the transformation unit 214, transforms the query parameter from the first format “user-name” to the second format which is “UserName”.
[0045] Further, the determination unit 212 determines whether the data included in at least one of, the data request and the response data requires transformation in a body of the data request. For example, if the client application is sending a customer identifier in the body of the data request in a first format such as “customerId” but the destination requires the customer identifier in a second format such as “consumerId”, then the transformation unit 214 identifies such a requirement through the body of the data request and makes the transformation.
[0046] Alternatively, in response to determining the data included in at least one of, the data request and the response data is not required to be transformed, the determination unit 212 is further configured to transmit the data request to a destination or transmit the response data to the client application.
[0047] Therefore, the system 108 requires minimum changes in the code of the API engine, as plurality of data transformation requirements are met using the transformations performed internally within the server 104. Thus, the system 108 provides flexibility and efficiency to the code.
[0048] FIG. 3 describes a preferred embodiment of the system 108 of FIG. 2, according to various embodiments of the present invention. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 112a and the system 108 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0049] As mentioned earlier in FIG. 1, each of the first UE 112a, the second UE 112b, and the third UE 112c may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 112a without deviating from the scope of the present disclosure and limiting the scope of the present disclosure. The first UE 112a includes one or more primary processors 302 communicably coupled to the one or more processors 202 of the system 108.
[0050] The one or more primary processors 302 are coupled with a memory 304 storing instructions which are executed by the one or more primary processors 302. Execution of the stored instructions by the one or more primary processors 302 enables the first UE 112a to transmit the data request to the one or more processors 202 from the client application via the one or more APIs.
[0051] As mentioned earlier in FIG. 2, the one or more processors 202 of the system 108 is configured for dynamically transforming the data. As per the illustrated embodiment, the system 108 includes the one or more processors 202, the memory 204, the user interface 206, and the database 208. The operations and functions of the one or more processors 202, the memory 204, the user interface 206, and the database 208 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0052] Further, the processor 202 includes the transceiver 210, the determination unit 212, and the transformation unit 214. The operations and functions of the transceiver 210, the determination unit 212, and the transformation unit 214 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 108 in FIG. 3, should be read with the description as provided for the system 108 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0053] FIG. 4 is an exemplary block diagram of an architecture 400 that can be implemented in the system 108 for dynamic data transformation, according to one or more embodiments of the present invention.
[0054] The architecture 400 includes an API transformation engine 412, that is configured to transform and manipulate the APIs. The architecture 400 depicts a plurality of providers such as provider1 406a, provider2 406b, provider3 406c which acts as an internal microservices and a plurality of consumers, such as consumer1 410a, consumer3 410b, consumer4 410c. The API transformation engine 412 includes a plurality of APIs, that is API1 408a, API2 408b, API3 408c and API4 408d which are made available through in one or more domains such as domain 402, and domain 404. The API transformation engine 412 transforms and manipulates data through the plurality of APIs, API1 408a, API2 408b, API4 408c and API5 408d and provides the data to the plurality of consumers, consumer1 410a, consumer2 410b, consumer3 410c. In an embodiment, the API transformation engine 412 is at least one of Common Application Programming Interface Framework (CAPIF).
[0055] In an embodiment, the data request is received from the plurality of consumers, consumer1 410a, consumer2 410b, consumer3 410c via the plurality of APIs, API1 408a, API2 408b, API3 408c and API4 408d to execute the data request.
[0056] Upon receiving the data request from the plurality of consumers, the consumer1 410a, consumer2 410b, consumer3 410c, the API transformation engine 412 is configured to determine whether the transformation is required in the header, query parameter or the body of the received data request or in the response data. If the transformation of the received data request or the response data is required, the API transformation engine is configured to make the desired transformation.
[0057] Alternatively, if the transformation of the received data request or the response data is not required, the data request is transmitted to the destination or the response data is transmitted to the plurality of consumers, consumer1 410a, consumer2 410b, consumer3 410c. In particular, the API transformation engine 412 modifies the received data if the transformation is required at the providers such as provider1 406a, provider2 406b, provider3 406c. Further, the providers such as provider1 406a, provider2 406b, provider3 406c transmits the response data to the plurality of consumers such as consumer1 410a, consumer2 410b, consumer3 410c via the API transformation engine 412.

[0058] In an embodiment, the API transformation engine 412 receives the request through one or more third-party API. The transformation rules provided herein enable the API transformation engine 412 to apply the transformation rules and forward the transformed response to a destination application. As a result, the plurality of consumers, consumer1 410a, consumer2 410b, consumer3 410c receive the response in a desired format.
[0059] FIG. 5 is a signal flow diagram for dynamic data transformation, according to one or more embodiments of the present invention. For the purpose of description, the signal flow diagram is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0060] At step 502, the receiving unit 210 receives the data request from the application via the one or more APIs. The data request is associated with the execution of the data request.
[0061] At step 504, upon receiving the data request from the application at the receiving unit 210, the determination unit 212 is configured to determine whether data included in the at least one of, the data request and the response data pertaining to the execution of the received data request requires transformation.
[0062] At step 506, in response to determining, the data included in at least one of, the data request and the response data requires transformation, the transformation unit 214 is configured to dynamically transform the data included in at least one of, the data request and the response data based on the determination. The dynamically transforming data pertains to at least one of, manipulating and converting formats of the data request and the response data. The data included in a header, a query, a protocol and body of the data request and the response data are dynamically transformed by the transformation unit 214.
[0063] At step 508, upon transforming the data included in at least one of the data request and response data, the transformed data included in at least one of the data request and response data is transmitted to the API consumer application.
[0064] At step 510, if the data included in the at least one of the data request and response data does not require transformation, the data included in the at least one of the data request and response data is transmitted to the API consumer application.
[0065] FIG. 6 is a flow diagram of a method 600 for dynamic data transformation, according to one or more embodiments of the present invention. For the purpose of description, the method 600 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0066] At step 602, the method 600 includes the step of receiving the data request from the application, via one or more APIs to execute the data request by the receiving unit 210.
[0067] At step 604, the method 600 includes the step of determining whether data included in the at least one of, the data request and response data pertaining to the execution of the received data request requires transformation by the determination unit 212.
[0068] At step 606, the method 600 includes the step of dynamically transforming the data included in the at least one of, the data request and the response data based on the determination by the transformation unit 214, in response to determining the data included in the at least one of the data request and the response data requires transformation. The dynamically transforming data pertains to at least one of, manipulating and converting formats of the data request and the response data. The data included in a header, a query, a protocol and body of the data request and the response data are dynamically transformed by the transformation unit 214.
[0069] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 202. The processor 202 is configured to receive the data request from the application via the one or more APIs to execute the data request. The processor 202 is further configured to determine whether data included in at least one of, the data request and response data pertaining to the execution of the received data request requires transformation. The processor 202 is further configured to dynamically transform, the data included in at least one of, the data request and the response data based on the determination, in response to determining, the data included in at least one of, the data request and the response data requires transformation.
[0070] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-6) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0071] The present disclosure incorporates technical advancement that the system requires minimum changes in the code of the API engine, as plurality of data format requirements are met using transformations performed internally within the server. Further, the disclosed system provides flexibility and efficiency to the code.
[0072] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS

[0073] Environment- 100
[0074] User Equipment (UE)- 102
[0075] Server- 104
[0076] Network- 106
[0077] System -108
[0078] Processor- 202
[0079] Memory- 204
[0080] User Interface- 206
[0081] Database- 208
[0082] Transceiver- 210
[0083] Determination Unit- 212
[0084] Transformation Unit- 214
[0085] One or more primary processor- 302
[0086] Memory – 304
[0087] Domain- 402, 404
[0088] Provider1- 406a
[0089] Provider2- 406b
[0090] Provider3- 406c
[0091] API1- 408a
[0092] API2- 408b
[0093] API3- 408c
[0094] API4- 408d
[0095] Consumer1- 410a
[0096] Consumer3 -410b
[0097] Consumer4 -410c
[0098] API transformation engine- 412
,CLAIMS:CLAIMS:
We Claim:
1. A method (600) for dynamic data transformation, the method (600) comprising the steps of:
receiving, by one or more processors (202), a data request from an application via one or more Application Programming Interfaces (APIs) to execute the data request;
determining, by the one or more processors (202), whether data included in at least one of, the data request and response data pertaining to the execution of the received data request requires transformation; and
in response to determining, the data included in the at least one of, the data request and the response data requires transformation, dynamically transforming, by the one or more processors (202), the data included in the at least one of, the data request and the response data based on the determination.

2. The method (600) as claimed in claim 1, wherein the step of determining, whether data included in at least one of, the data request and response data pertaining to the execution of the received data request requires transformation, further include the step of:
transmitting, by the one or more processors (202), the data request to a destination or transmitting the response data to the application in response to determining, the data included in at least one of, the data request and the response data is not required to be transformed.

3. The method (600) as claimed in claim 1, wherein the data included in a header, a query, a protocol and body of the data request, and the response data are dynamically transformed by the one or more processors (202).

4. The method (600) as claimed in claim 1, wherein dynamically transforming data pertains to at least one of, manipulating and converting formats of the data request and the response data.

5. A system (108) for dynamic data transformation, the system (108) comprising:
a transceiver (210), configured to, receive, a data request from an application via one or more Application Programming Interfaces (APIs) to execute the data request;
a determination unit (212), configured to, determine, whether data included in at least one of, the data request and response data pertaining to the execution of the received data request requires transformation; and
in response to determining, the data included in at least one of, the data request and the response data requires transformation, a transformation unit (214), configured to, dynamically transform, the data included in at least one of, the data request and the response data based on the determination.

6. The system (108) as claimed in claim 5, wherein the determination unit (212) determines, whether data included in at least one of, the data request and a response data pertaining to the execution of the received data request requires transformation, further configured to:
transmit, the data request to a destination or transmits the response data to the application in response to determining, the data included in at least one of, the data request and the response data is not required to be transformed.

7. The system (108) as claimed in claim 5, wherein the data included in a header, a query, a protocol and body of the data request, and the response data are dynamically transformed by the transformation unit (214).

8. The system (108) as claimed in claim 5, wherein the dynamically transforming data pertains to at least one of, manipulating and converting formats of the data request and the response data.

9. A User Equipment (UE) (102), comprising:
one or more primary processors (302) communicatively coupled to one or more processors (202), the one or more primary processors (302) coupled with a memory (304), wherein said memory (304) stores instructions which when executed by the one or more primary processors (302) causes the UE (102) to:
transmit, the data request to the one or more processors (202) from the client application via a one or more Application Programming Interfaces (APIs); and
wherein the one or more processors (202) is configured to perform the steps as claimed in claim 1.