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
SYSTEM AND METHOD FOR MANAGING AN INVENTORY
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 disclosure relates to wireless networks, more particularly relates to a system and method for managing an inventory in the wireless networks.
BACKGROUND OF THE INVENTION
[0002] For multiple types of data sets (for example, site data, customer data, card data, or code data), different Application Programming Interfaces (APIs) may be exposed by the systems of the existing technologies. The system is equipped with multiple different kinds of APIs, and for each different type of data operation, the existing system calls a separate API from the multiple APIs.
[0003] However, with multiple APIs present, the system faces challenges with respect to integration. It becomes cumbersome for the system to consume multiple different APIs with different signatures for different datasets. Therefore, the system faces integration-level challenges.
[0004] Further, incorporating API level changes in the system is a time-consuming process. Furthermore, traditional inventory systems include multiple APIs which are interlinked and need to be invoked in some order so that particular information is created, modified, deleted, or viewed properly. This invariably leads to multiple API calls, multiple API schemas and signatures, API versioning and management of breaking changes, and different APIs for different activities. Moreover, every system which needs to integrate with inventory management system must adapt and implement all these APIs followed by system integration testing.
[0005] There is therefore a need for a solution that overcomes the above challenges and provides for a single API for performing all the different data processing operations including ‘create’ operations, ‘update’ operations, etc.
BRIEF SUMMARY OF THE INVENTION
[0006] One or more embodiments of the present disclosure provide a system and a method for managing an inventory.
[0007] In one aspect of the present invention, a method for managing an inventory is disclosed. The method includes the step of receiving, by one or more processors, a request from at least one of a User Equipment (UE), the request includes information such as, one of name of a model and name of a table, and attributes pertaining to one of the model and the table. The method includes the step of retrieving, by the one or more processors, a structure of one of the model and the table and at least one attribute pertaining to one of the retrieved tables and the model from a database. The method includes the step of performing, by the processor, an operation on an entity by modification of the at least one attribute within the structure retrieved from the database to one of create, read, update, and delete an entity in the inventory, and thereby managing the inventory.
[0008] In one embodiment, the operation is one of creating, reading, updating, and deleting.
[0009] In one embodiment, the modification of the at least attribute pertains to one of insertion, updating, and deletion of the at least one attribute.
[0010] In one embodiment, the method comprises the step of validating, by the one or more processors, availability of one of the name of the model and the name of the table in the database.
[0011] In one embodiment, the method comprises the step of validating, by the one or more processor, JavaScript Object Notation (JSON) data of the received request in response to retrieving the structure and the at least one attribute from the database.
[0012] In one embodiment, the structure of one of the model and the table and at least one attribute pertaining to one of the retrieved table and the model is retrieved from the database in response to validation of the availability of the one of the name of the model and the name of the table in the database.
[0013] In another aspect of the present invention, a system for managing an inventory is disclosed. The system includes a receiving unit. The receiving unit is configured to receive a request from at least one of a User Equipment (UE). The request includes information such as, one of name of a model and name of a table, and attributes pertaining to one of the model and the table. The system includes a retrieving unit. The retrieving unit is configured to retrieve a structure of one of the model and the table and at least one attribute pertaining to one of the retrieved table and the model from the database. The system includes an operation unit. The operation unit is configured to perform an operation on an entity by modification of the at least one attribute within the structure retrieved from the database to one of create, read, update, and delete an entity in the inventory, and thereby managing the inventory.
[0014] In another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by a processor is disclosed. The processor is configured to receive a request from at least one of a User Equipment (UE). The request includes information such as, one of name of a model and name of a table, and attributes pertaining to one of the model and the table. The processor is configured to retrieve a structure of one of the model and the table and at least one attribute pertaining to one of the retrieved table and the model from a database. The processor is configured to perform, an operation on an entity by modification of the at least one attribute within the structure retrieved from the database to one of create, read, update, and delete an entity in the inventory, and thereby managing the inventory.
[0015] 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
[0016] 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.
[0017] FIG. 1 is an exemplary block diagram of an environment for managing an inventory, according to various embodiments of the present invention;
[0018] FIG. 2 is an exemplary block diagram of the present system of FIG. 1 for managing the inventory, according to various embodiments of the present invention;
[0019] FIG. 3 is an exemplary embodiment of the system of FIG. 2, according to various embodiments of the present invention;
[0020] FIG. 4 is an exemplary block diagram of the system architecture for managing the inventory, according to various embodiments of the present invention; and
[0021] FIG. 5 shows a flow diagram of a method for managing the inventory, according to various embodiments of the present invention.
[0022] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0023] 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.
[0024] 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.
[0025] 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.
[0026] As per various embodiments depicted, the present invention discloses systems and methods for managing an inventory. The present disclosure provides for creating an Inventory Management (IM). The IM is configured to provide a generic Application Programming Interface (API) which is capable of performing different types of data processing. In the present invention, the IM achieves the flexibility of data processing by accepting the dataset or model name as a parameter in its API requests. This implementation allows interaction with the IM using a single standardized API, regardless of the specific dataset or model that is being worked with. By using the generic APIs, the entire process is simplified, and the user is able to use a single API to perform all the operations. The versatility of IM generic API design makes it useful for working with different datasets, in a more efficient way. For example, if a user or an external system wants to get details of any customer, Subscriber Identity Module (SIM) card or Mobile Station Integrated Services Digital Network (MSISDN), and create new customer dataset, then in such a case, the user may simply use a single API for all these data operation. All the data sets related to the operations may be modelled and stored in the IM inventory. Further, the IM is configured to be used by any system to interact with inventory management system and do changes or retrieve data. The API aids in linking multiple calls to the inventory so that the consuming system sees just one API for all the operations. This, advantageously, reduces the implementation effort and the integration effort and provides a comprehensive and unified interface for all activities involving the IM.
[0027] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing an inventory 110, according to various embodiments of the present invention. In one embodiment, the inventory 110 is configured to organizing the data. In one embodiment, the inventory 110 includes one or more entity attributes that are modelled and organized. In one embodiment, the model of the one or more entity attributes pertaining to but not limited to a product, an organization, a site, a port, details of the customer i.e. Subscriber Identity Module (SIM) details and/or Mobile Station Integrated Services Digital Network (MSISDN). In one embodiment, for example, the customer has attributes such as name, email, and address.
[0028] The environment 100 includes at least one User Equipment (UE) 102 configured to at least transmit a request from the at least one UE 102 to manage the inventory 110. In one embodiment, the request includes information but not limited to name of a model, name of a table, and attributes pertaining to one of the model and the table. In one embodiment, the at least one UE 102 is at least one of a first UE 102a, a second UE 102b, and a third UE 102c. In one embodiment, the first UE 102a, the second UE 102b, and the third UE 102c are communicatively connected to a system 106 via a network 104. The first UE 102a, the second UE 102b, the third UE 102c will henceforth collectively and individually be referred to as “the UE 102” without limiting the scope and deviating from the scope of the present disclosure.
[0029] The UE 102 includes, but are not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a tablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication capabilities, and the like.
[0030] The environment 100 further includes the server 108 communicably coupled to the UE 102 via the network 104. The server 108 includes 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, a defence facility, or any other facility that provides content.
[0031] The network 104 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 104 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.
[0032] The network 104 includes, by the way of example but not limitation, one or more wireless interfaces/protocols such as, for example, 802.11 (Wi-Fi), 802.15 (including Bluetooth™), 802.16 (Wi-Max), 802.22, Cellular standards such as CDMA, CDMA2000, WCDMA, Radio Frequency (e.g., RFID), Infrared, laser, Near Field Magnetics, etc.
[0033] The environment further includes the system 106 communicably coupled to the server 108 and the UE 102 via the network 104. The system 106 is configured to manage the inventory 110. Further, the system 106 is adapted to be embedded within the server 108 or is embedded as the individual entity. However, for the purpose of description, the system 106 is described as an integral part of the server 108, without deviating from the scope of the present disclosure.
[0034] Operational and construction features of the system 106 will be explained in detail with respect to the following figures.
[0035] Referring to FIG. 2, FIG. 2 illustrates an exemplary block diagram of the system 106 of FIG. 1 for managing the inventory 110, according to various embodiments of the present system. As per the illustrated embodiment, the system 106 includes one or more processors 202, a memory 204, an Input/Output (I/O) user interface 206, a display unit 208, an input device 210 and a database 220. 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. As per the illustrated embodiment, the system 106 includes one processor 202. However, it is to be noted that the system 106 may include multiple processors as per the requirement and without deviating from the scope of the present disclosure. Among other capabilities, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204.
[0036] 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 EPROM, flash memory, and the like. In an embodiment, the I/O user interface 206 includes a variety of interfaces, for example, interfaces for data input and output devices, referred to as Input/Output (I/O) devices, storage devices, and the like. The I/O user interface 206 facilitates communication of the system 106. In one embodiment, the I/O user interface 206 provides a communication pathway for one or more components of the system 106.
[0037] The I/O interface unit 206 may include functionality similar to at least a portion of functionality implemented by one or more computer system interfaces such as those described herein and/or generally known to one having ordinary skill in the art. The I/O interface unit 206 may be rendered on the display unit 208, implemented using LCD display technology, OLED display technology, and/or other types of conventional display technology. The display unit 208 is integrated within the system 106 or connected externally. Further the request may be configured to receive request, queries, or information from the user by using the input device 210. The input device 210 includes, but not limited to, keyboard, buttons, scroll wheels, cursors, touchscreen sensors, audio command interfaces, magnetic strip reader, optical scanner, etc.
[0038] The system 106 further comprises the database 220. The database 220 is communicably connected to the processor 202, and the memory 204. The database 220 is configured to store and retrieve data.
[0039] Further, the processor 202, 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 processor 202 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 202. In such examples, the system 106 comprises 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 106 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[0040] In order for the system 106 to manage the inventory 110, the processor 202 includes a receiving unit 212, a validation unit 214, a retrieving unit 216, and an operation unit 218, communicably coupled to each other.
[0041] The receiving unit 212 of the processor 202 is communicably connected to the UE 102 of the user, via the network 104. Accordingly, the receiving unit 212 is configured to receive the request from at least one of the UE 102. In one embodiment, the request includes information such as, but not limited to, name of a model, name of a table, and attributes pertaining to one of the model and the table. Thereafter, the receiving unit 212 transmits the request for one of name of the model and name of the table and attributes pertaining to one of the model and the table to the validation unit 214 for validation.
[0042] Upon receiving one of the name of the model, the name of the table and attributes pertaining to one of the model and the table from the receiving unit 212, the validation unit 214 validates an availability of one of the name of the requested model, and the requested table from the database 220. In one embodiment, the name of the model and the name of the table and attributes pertaining to the model and the table are pre-stored in the database 220. In another embodiment, the name of the model, name of the table and attributes pertaining to the model and the table are pre-stored in the server 108. The validation unit 214 further transmits the availability of one of the name of the model and the name of the table to the retrieving unit 216.
[0043] After receiving the availability of the requested one of the name of the model and the name of the table from the validation unit 214, the retrieving unit 216 is configured to retrieve a structure of one of the model and the table and at least one attribute pertaining to one of the retrieved model and the table from the database 220. In one embodiment, the structure describes the entity attribute relationship of one of the model and the table and at least one attribute pertaining to one of the model and the table.
[0044] After retrieving the structure, the validation unit 214 validates the received request in response to retrieving the structure and the at least one attribute from the database 220. In one embodiment, the validation unit 214 validates a JavaScript Notation (JSON) data or XML data of the retrieved structure of one of the model and the table and at least one attribute pertaining to the retrieved model and table. The structure of one of the model and the table and at least one attribute pertaining to the model and table are transmitted to the operation unit 218 for further processing.
[0045] Upon receiving the structure from the validation unit 214, the operation unit 218 is configured to perform an operation on the entity. The operation is performed on the entity by modification of the at least one attribute within the structure is retrieved from the database 220 to one of create, read, update, and delete the entity in the inventory 110. In one embodiment, the operation is one of the creating, reading, updating, and deleting. In one embodiment, the modification of the at least one attribute pertains to one of insertion, updating, and deletion of the at least one attribute.
[0046] As per one embodiment, the inventory 110 with its unique proposition provides a generic API which can be used by any system to interact with an inventory management system and perform changes or retrieve data. The API intelligently links a plurality of calls to the inventory 110 so that the system 106 utilizes one API for all the calls. In owing to this, the system 106 reduces implementation effort and integration effort and provides a comprehensive and unified interface for all activities involving the inventory 110.Further, the inventory 110 managed by the system 106 reduces the efforts and time required to perform various data operations like creating, reading, updating, and deleting. Furthermore, the inventory 110 managed by the system 106 reduces the complexity of managing multiple APIs for different data sets.
[0047] Referring to FIG. 3, FIG. 3 is an exemplary embodiment of the system architecture of FIG. 2, according to various embodiments of the present invention. As mentioned earlier in FIG. 1, each of the at least first UE 102a, the second UE 102b, and the third UE 102c are configured to at least transmit the request from the at least one UE 102 to manage the inventory 110. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to at least first UE 102a and the system 106 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure. The first UE 102a includes one or more primary processors 302 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 102a to transmit the request to the one or more processors 202 of the system 106.
[0048] The first UE 102a comprises the memory 304 such as a volatile memory (e.g., RAM), a non-volatile memory (e.g., disk memory, FLASH memory, EPROMs, etc.), an unalterable memory, and/or other types of memory. In one implementation, the memory 304 might be configured or designed to store data. The data may pertain to transmit the request and access rights specifically defined for the first UE 102a. The first UE 102a is accessed by the user, to transmit the request to the one or more processors 202. The first UE 102a is configured to transmit the request to the one or more processors 202 of the system 106 through the network 104.
[0049] For the sake of brevity, it is to be noted that a similar description related to the working and operation of the system 106 as illustrated in FIG. 3 has been omitted to avoid repetition. The limited description provided for the system 106 in FIG. 3, should be read with the description as provided for the system 106 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0050] Referring to FIG. 4, FIG. 4 illustrates an exemplary block diagram of the system architecture for managing the inventory 110, according to various embodiments of the present invention. As per illustrated embodiment, the Inventory Management (IM) system 106 includes one or more models m1, m2….mn. The one or more models m1, m2….mn includes one or more entity attributes entity attribute1, entity attribute2…., entity attributen. In an embodiment, examples of the one or more entity include, but are not limited to, the product, the organization, the site, details of the customer and the SIM details. For example, a customer has attributes such as name, email, and address. All the one or more entity attributes are modelled and stored in the database 220 of the system 106 based on the one or more data operations. In one embodiment, the one or more data operations are performed on one or more entity models by modifying at least one attribute. The one or more data operations includes, but not limited to, creating, reading, updating, and deleting the at least one attribute. In one embodiment, the modification of the at least one attribute pertains to one of insertion, updating, and deletion of the dataset.
[0051] In one embodiment, for example, when the UE 102 transmits the request to the processor 202 of the system 106 for creating m1 entity among one or more models m1, m2….mn . The processor 202 of the system 106 receives the request from the UE 102 to perform the one or more data operations. In one embodiment, the request includes information such as, one of name of the model, name of the table, and attributes pertaining to one of the requested model and the requested table. Upon receiving the request from the UE 102, the processor 202 of the system 106 validates for availability of one of name of the requested model, name of the requested table, and attributes pertaining to one of the requested model and the requested table from the database 220.
[0052] In one embodiment, based on the availability of one of name of the model, name of the table, and attributes pertaining to one of the model and the table, the system 106 retrieves the structure of the name of the model, name of the table, and attributes pertaining to one of the retrieved model and the table from the database 220. Furthermore, the validation unit 214 validates the JSON or XML data of the received request in response to retrieving the structure of one of the model, the table and the at least one attribute from the database 220.
[0053] In one embodiment, the structure of one of the model, the table and at least one attribute pertaining to one of the retrieved model and the table is retrieved from the database 220. In one embodiment, based on the validation of the availability of the one of the name of the model, the name of the table from the database 220, the structure of one of the model, the table and at least one attribute pertaining to one of the retrieved model and the table is retrieved from the database 220.
[0054] Based on the retrieving the structure of one of the name of the model and the name of the table from the database 220, the processor 202 of the system 106 performs the required one or more data operations. In one embodiment, the one or more data operations includes creating, reading, updating, and deleting. In one embodiment, the name of the model and the name of the table are stored as per standards and are pre-stored in the database 220.
[0055] Referring to FIG. 5, FIG. 5 illustrates a flow diagram of the method 500 for managing the inventory 110, according to various embodiments of the present invention. The method 500 is adapted to manage the inventory 110. For the purpose of description, the method 500 is described with the embodiments as illustrated in FIG. 1 and should nowhere be construed as limiting the scope of the present disclosure.
[0056] At step 502, the method 500 includes the step of receiving the request from at least one of the UE 102 from the receiving unit 212. In one embodiment, the request includes information such as, one of name of the model, name of the table, and attributes pertaining to one of the model and the table. The receiving unit 212 transmits the one of name of the model, name of the table and attributes pertaining to one of the model and the table to the validation unit 214 for validation.
[0057] At step 504, the method 500 includes the step of the validating the availability of the one of the name of the model, the name of the table in the database 220 by the validation unit 214. The validation unit 214 further transmits the availability of one of the name of the model and the name of the table to the retrieving unit 216 for further processing.
[0058] At step 506, the method 500 includes the step of retrieving the structure of one of the model, the table and at least one attribute pertaining to one of the retrieved table and the model from the database 220 by the retrieving unit 216. Thereafter, the retrieving unit 216 transmits the availability of the one of the name of the model and the name of the table to the validation unit 214. The validation unit 214 validates the JSON data or XML data of the received request in response to retrieving the structure of one of the model, the table and the at least one attribute from the database 220.
[0059] At step 508, the method 500 includes the step of performing an operation on the entity by modification of the at least one attribute within the structure retrieved from the database 220 to one of create, read, update and delete the entity in the inventory 110, and thereby managing the inventory 110.
[0060] In an embodiment, the present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by a processor 202. The processor 202 is configured to receive a request from at least one of a User Equipment (UE) 102. The request includes information such as, one of name of a model and name of a table, and attributes pertaining to one of the model and the table. The processor 202 is further configured to retrieve a structure of one of the model and the table and at least one attribute pertaining to one of the retrieved tables and the model from the database 220. The processor 202 is further configured to create an entity by insertion of the at least one attribute within the structure retrieved from the database 220 to create an entity in the inventory 110, and thereby managing the inventory 110.
[0061] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-5) 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.
[0062] The present disclosure incorporates technical advancement by simplifying the process of integration and enhancing interoperability for managing an inventory. The method of the IM provides a generic API which is capable of processing different kinds of data. Therefore, there is no need for different APIs to be integrated. A single API for any kind of dataset can be used to create an entity. So, instead of creating a separate APIs for each dataset or model, the process is streamlined by employing a single API. This integration with the inventory system reduces efforts and time required to perform various data operations. Further, the integration reduces the complexity of managing multiple APIs for different data sets. This is implemented by reusing the code. As such, a single code can be used and that can be reused. Furthermore, as mentioned above, the generic API may be used by any system to interact with the inventory management system and do changes or retrieve data. The generic API may intelligently link multiple calls to the inventory so that the consuming system uses just one API for all the calls. This reduces the implementation effort and the integration effort and provides a comprehensive and unified interface for all activities involving the IM.
[0063] 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
[0064] Environment - 100;
[0065] User Equipment- 102;
[0066] Network - 104;
[0067] System-106;
[0068] Server-108;
[0069] Inventory-110;
[0070] Processor(s) -202;
[0071] Memory- 204;
[0072] Input/Output (I/O) user interface-206;
[0073] Display unit- 208;
[0074] Input device-210;
[0075] Receiving unit - 212;
[0076] Validation unit-214;
[0077] Retrieving unit 216;
[0078] Operation unit-218;
[0079] Database-220;
[0080] Primary processor-302;
[0081] Memory unit of User Equipment-304.

,CLAIMS:CLAIMS
We Claim
1. A method (500) of managing an inventory (110), the method (500) comprising the steps of:
receiving, by one or more processors (202), a request from at least one of a User Equipment (UE) (102), the request includes information such as, one of name of a model and name of a table, and attributes pertaining to one of the model and the table;
retrieving, by the one or more processors (202), a structure of one of the model and the table and at least one attribute pertaining to one of the retrieved table and the model from a database (220); and
performing, by the processor (202), an operation on an entity by modification of the at least one attribute within the structure retrieved from the database (220) to one of create, read, update and delete an entity in the inventory (110), and thereby managing the inventory (110).

2. The method (500) as claimed in claim 1, wherein the operation is one of a creating, reading, updating, and deleting.

3. The method (500) as claimed in claim 1, wherein the modification of the at least attribute pertains to one of creation, insertion, updating, and deletion of the at least one attribute.

4. The method (500) as claimed in claim 1, wherein the method (500) comprises the step of validating, by the one or more processors (202), availability of one of the name of the model and the name of the table in a database (220).

5. The method (500) as claimed in claim 1, wherein the method (500) comprises the step of validating, by the one or more processor (202), JavaScript Object Notation (JSON) data of the received request in response to retrieving the structure and the at least one attribute from the database (220).

6. The method (500) as claimed in claim 1, wherein the structure of one of the model and the table and at least one attribute pertaining to one of the retrieved table and the model is retrieved from the database (220) in response to validation of the availability of the one of the name of the model and the name of the table in the database (220).

7. A system (106) for managing an inventory (110), the system (106) comprising:
a receiving unit (212) configured to receive, a request from at least one of a User Equipment (UE) (102), the request includes information such as, one of name of a model and name of a table, and attributes pertaining to one of the model and the table;
a retrieving unit (216) configure to retrieve, a structure of one of the model and the table and at least one attribute pertaining to one of the retrieved table and the model from a database (220); and
an operation unit (218) configured to perform, an operation on an entity by modification of the at least one attribute within the structure retrieved from the database (220) to one of create, read, update and delete an entity in the inventory (110), and thereby managing the inventory (110).

8. The system (106) as claimed in claim 7, wherein the operation is one of a creating, reading, updating, and deleting.

9. The system (106) as claimed in claim 7, wherein the modification of the at least attribute pertains to one of insertion, updating, and deletion of the at least one attribute.

10. The system (500) as claimed in claim 7, comprising a validation unit (216) configured to
validate, availability of one of the name of the model and the name of the table in a database (220); and
validate, JavaScript Object Notation (JSON) data of the received request in response to retrieving the structure and the at least one attribute from the database (220).

11. The system (106) as claimed in claim 7, wherein the structure of one of the model and the table and at least one attribute pertaining to one of the retrieved table and the model is retrieved from the database (220) in response to validation of the availability of the one of the name of the model and the name of the table in the database (220).

12. 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, a request to the one or more processors (202);
wherein the one or more processors (202) is configured to perform the steps as claimed in claim 1.