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 DEFINING DATA ACCESS IN AN INVENTORY MANAGEMENT
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 generally to wireless communication systems, and in particular, to a method and a system for defining data access in an Inventory Management (IM).
BACKGROUND OF THE INVENTION
[0002] Inventory Management (IM) is an open, standards-based, cloud-native application that provides an intelligent inventory of communications services and resources – from 5G to Fiber – across physical and virtual network technologies.
[0003] IM is a standards-based telecommunications inventory management application that enables you to model and manage customers, services, and resources. IM supports complex business relationships and provides full life-cycle management of services and resources.
[0004] It may be desired by the user to see the details of the equipments deployed in the site in a particular manner. For example, number of equipments located in the site, the details of the card and ports in those equipments, etc. Another user using the same interface may want to see the details of the same equipments deployed in the same site from a different perspective or arranged in a different manner. These different users may have different purposes, position or roles in the organisation.
[0005] Also, suppose an issue, fault or a problem arises in any of the fibre links, ports, it is desired to see the exact location of the port to know where the fault has arisen so that personnel can be assigned and sent to the exact location for resolution of the issue at the earliest. Further, it is also desired that the user is able to organise the inventory of equipments in the site so that the same is visible as per his requirement for better and efficient management.
[0006] It is known in the art traditionally for the inventory systems to have a predefined hierarchy. The user fills-in the information in such predefined and frozen hierarchy which are ready-made. The user is not allowed to make changes or tweak with the predefined hierarchy. For example, a database table will have predefined structure, with frozen list of columns and headers. In such cases, the user is allowed to make entries only in fixed columns. The user does not have an option, for example, to create or add a column to the table. Similarly, deletion of a column / header is also not possible.
[0007] Consequently, the way in which the data can be viewed is also frozen and there is only one single frozen view possible for ally and any user of the system. It is desired that different users may want to look at the data in a certain way that fits their purpose best.
[0008] There is therefore a need for a solution that overcomes the above challenges and provides for a system and method for customizable viewing of the data in the IM as per the requirement of different users of the system. Each user should be able to view the data in the desired manner and hierarchy that suits his purpose and should able to customise the view in real time. It is further desired that the method should enable real-time customisation of the hierarchy for viewing and organising the data as and when required.
BRIEF SUMMARY OF THE INVENTION
[0009] One or more embodiments of the present disclosure provide a system and method of defining data access in an Inventory Management (IM).
[0010] In one aspect of the present invention, a system for defining data access in an Inventory Management (IM) is disclosed. The system includes a user input receiving unit configured to collect a user input through one or more exposed Application Programming Interfaces (APIs). The user input defines link between two or more of site name, building name, floor name, rack name, shelf name, slot name, equipment name, chassis name, card name, and port name. The system further includes a generating unit configured to create a customizable hierarchy of a combination of physical resources and logical resources based on the user input. The system further includes a model finalizing unit configured to finalize one or more models for viewing data of the resources based on the user input. For viewing the data of the resources, tables, columns, and rows are defined within the one or more models.
[0011] The system is further configured to modify, based on the user input, number of levels in the customizable hierarchy and a sequence of models present in the customizable hierarchy in real time.
[0012] In another aspect of the present invention, a method of defining data access in an IM is disclosed. The method includes the step of collecting a user input for creating a customizable hierarchy of a combination of physical resources and logical resources. The user input is collected through one or more exposed APIs and defines link between two or more of site name, building name, floor name, rack name, shelf name, slot name, equipment name, chassis name, card name, and port name. The method further includes the step of finalizing one or more models for viewing data of the resources based on the user input.
[0013] The method further includes the step of comprising modifying number of levels in the customizable hierarchy and a sequence of models present in the customizable hierarchy in real time. In a first hierarchy, a site name is shown at first level, list of shelfs is shown at a second level, list of equipment is shown at a third level, list of chassis is shown at a fourth level, list of cards is shown at a fifth level, and a list of ports is shown at a sixth level. In a second hierarchy, a list of ports is shown at a first level, list of cards is shown at a second level, list of chassis is shown at a third level, list of equipment is shown at a fourth level, list of shelfs is shown at a fifth level, and a site name is shown at a sixth level.
[0014] 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
[0015] 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.
[0016] FIG. 1 illustrates an exemplary block diagram of an environment for defining data access in an Inventory Management (IM), according to one or more embodiments of the present invention;
[0017] FIG. 2 illustrates an exemplary block diagram of a system for defining data access in an IM, according to one or more embodiments of the present invention;
[0018] FIG. 3 illustrates a block diagram of the system and a first User Equipment (UE) communicating with each other, according to one or more embodiments of the present system;
[0019] FIG. 4a illustrates a first hierarchy of resources in a model and FIG. 4b illustrates a second hierarchy of resources in a model, according to one or more embodiments of the present invention; and
[0020] FIG. 5 illustrates a flow diagram of a method of defining data access in an IM, according to one or more embodiments of the present invention.
[0021] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0022] 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.
[0023] 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.
[0024] 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.
[0025] The present disclosure provides a method and system for creating on-demand customizable hierarchies as per user requirement for equipment’s deployed in an organization, system, network and the like. A customizable user defined hierarchy in which a user wants to see the data from an Inventory Management (IM) can be created at any time through exposed Application Programming Interfaces (APIs).
[0026] The present disclosure provides for organizing existing models in the IM in different ways as per the user’s requirement in real time without requiring a change in the code i.e., a hierarchy of models can be created in any number of ways as per user requirement without the need to write a code. This reduces the time and efforts of the end-users using IM GUI who want to see the data in different ways. The hierarchy in which user wants to see the data from IM can be created at any time through the exposed APIs. In accordance with an embodiment, in the IM, the table, columns, rows and the like are all dynamic. That is to say, the same can be altered on demand as per user requirement in real time.
[0027] FIG. 1 illustrates an exemplary block diagram of an environment 100 for defining data access in an Inventory Management (IM), according to one or more embodiments of the present invention. The environment 100 includes a user equipment 110. For the purpose of description and explanation, the description will be explained with respect to one or more User Equipments (UE) 110, or to be more specific will be explained with respect to a first UE 110a, a second UE 110b, and a third UE 110c, and should nowhere be construed as limiting the scope of the present disclosure.
[0028] In an embodiment, each of the first UE 110a, the second UE 110b, and the third UE 110c is one of, but are 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, general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0029] Each of the first UE 110a, the second UE 110b, and the third UE 110c is further configured to transmit a request from a user via an interface module to a communication network 105 to avail one or more services. In one embodiment, the one or more services include, but not limited to, finalizing one or more models for viewing data via the communication network 105. The models referenced at several places within this disclosure corresponds to an information model including details of representation of concepts and relationships, constraints, rules, and operations to specify data semantics for the IM.
[0030] A person skilled in the art will appreciate that the UE 110 may include more than one processor and communication ports. The communication port(s) may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) may be chosen depending on a network, such as, but not limited to, a Local Area Network (LAN), a Wide Area Network (WAN), or any of the networks to which the computer system connects.
[0031] The communication network 105 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 communication network 105 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 environment 100 further includes a server 115 accessible via the communication network 105. The server 115 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, a defence facility, or any other facility that provides content.
[0033] The environment 100 further includes a system 125 communicably coupled to the server 115 and each of the first UE 110a, the second UE 110b, and the third UE 110c via the communication network 105. The system 125 is configured to allow data access in an Inventory Management. The system 125 is adapted to be embedded within the server 115 or is embedded as the individual entity, as per multiple embodiments of the present invention. However, for the purpose of description, the system 125 is described as an integral part of the server 115, without deviating from the scope and limiting the scope of the present disclosure.
[0034] In various embodiments, the system 125 may be generic in nature and may be integrated with any application including a System Management Facility (SMF), an Access and Mobility Management Function (AMF), a Business Telephony Application Server (BTAS), a Converged Telephony Application Server (CTAS), any SIP (Session Initiation Protocol) Application Server which interacts with core Internet Protocol Multimedia Subsystem (IMS) on Industrial Control System (ISC) interface as defined by Third Generation Partnership Project (3GPP) to host a wide array of cloud telephony enterprise services, a System Information Blocks (SIB)/ and a Mobility Management Entity (MME).
[0035] The environment 100 further includes a distributed data lake 130 communicably coupled to each of the first UE 110a, the second UE 110b, and the third UE 110c, the server 115, and the system 125 via the communication network 105. The distributed data lake 130 is a data repository providing storage and computing for structured and unstructured data, such as for machine learning, streaming, or data science. The distributed data lake 130 allows users and/or organizations to ingest and manage large volumes of data in an aggregated storage solution for business intelligence or data products. The distributed data lake 130 may be implemented and utilize different technologies. For example, in one implementation, Hadoop may be deployed with the Spark processing engine and HBase, a NoSQL database that runs on top of Hadoop Distributed File System (HDFS). In another implementation, Spark may be used against data stored in Amazon Simple Storage Service (S3).
[0036] Operational and construction features of the system 125 will be explained in detail successively with respect to different figures.
[0037] FIG. 2 illustrates an exemplary block diagram of a system 125 for defining data access in an Inventory Management, according to one or more embodiments of the present invention.
[0038] As per the illustrated embodiment, the system 125 includes one or more processors 205, a memory 210, and an input/output interface unit 215. The one or more processor 205, hereinafter referred to as the processor 205 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 125 includes one or more processors 205. However, it is to be noted that the system 125 may include multiple processors as per the requirement and without deviating from the scope of the present disclosure. Among other capabilities, the one or more processors 205 is configured to fetch and execute computer-readable instructions stored in the memory 210. The memory 210 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 210 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.
[0039] In an embodiment, the input/output (I/O) interface unit 215 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 interface unit 215 facilitates communication of the system 125. In one embodiment, the I/O interface unit 215 provides a communication pathway for one or more components of the system 125. Examples of such components include, but are not limited to, the UE 110, a backend database 240, and a distributed cache 250.
[0040] The backend database 240 is one of, but is 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 database, and so forth. The foregoing examples of the backend database 240 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.
[0041] The distributed cache 250 is a pool of random-access memory (RAM) of multiple networked computers into a single in-memory data store for use as a data cache to provide fast access to data. The distributed cache 250 is essential for applications that need to scale across multiple servers or are distributed geographically. The distributed cache 250 ensures that data is available close to where it’s needed, even if the original data source is remote or under heavy load.
[0042] Further, the one or more processors 205, 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 one or more processors 205. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the one or more processors 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for one or more processors 205 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the one or more processors 205. In such examples, the system 125 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 125 and the processing resource. In other examples, the one or more processors 205 may be implemented by electronic circuitry.
[0043] In order for the system 125 to define data access in an Inventory Management (IM), the processor 205 includes a user input receiving unit 220, a generating unit 225, and a model finalizing unit 230 communicably coupled to each other.
[0044] The user input receiving unit 220 of the processor 205 is communicably connected to each of the first UE 110a, the second UE 110b, and the third UE 110c via the communication network 105. Accordingly, the user input receiving unit 220 is configured to collect a user input through one or more exposed Application Programming Interfaces (APIs). The user input defines link between two or more of site name, building name, floor name, rack name, shelf name, slot name, equipment name, chassis name, card name, and port name.
[0045] The one or more processors 205 further includes the generating unit 225 in communication with the user input receiving unit 220. More specifically, the generating unit 225 is communicably coupled with the user input receiving unit 220 to create a customizable hierarchy of a combination of physical resources and logical resources based on the user input. The hierarchy refers to a sequence of presentation of information of the physical resources and the logical resources to the user. The user may access such information in a sequential manner by scrolling down using a User Interface (UI) or clicking information displayed at a higher level. In one hierarchy, a site name is shown at first level, list of shelfs is shown at a second level, list of equipment is shown at a third level, list of chassis is shown at a fourth level, list of cards is shown at a fifth level, and a list of ports is shown at a sixth level. In another hierarchy, a list of ports is shown at a first level, list of cards is shown at a second level, list of chassis is shown at a third level, list of equipment is shown at a fourth level, list of shelfs is shown at a fifth level, and a site name is shown at a sixth level.
[0046] The one or more processors 205 further includes the model finalizing unit 230 in communication with the generating unit 225 to finalize one or more models for viewing data of the resources based on the user input. Within the one or more models for viewing data, tables, columns, and rows are defined. A name of the customizable hierarchy could also be defined based on the user input. Further, the number of levels in the customizable hierarchy and a sequence of models present in the customizable hierarchy can be modified i.e. added or subtracted in real time.
[0047] Referring to FIG. 3 illustrating a block diagram of the system 125 and the first UE 110a communicating with each other, a preferred embodiment of the system 125 is described. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 110a for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0048] The first UE 110a includes one or more primary processors 305 communicably coupled to the one or more processors 205 of the system 125. The one or more primary processors 305 are coupled with a memory unit 310 storing instructions which are executed by the one or more primary processors 305. Execution of the stored instructions by the one or more primary processors 305 enables the first UE 110a to provide a user input to the system 125 for creating a customizable hierarchy of a combination of physical resources and logical resources.
[0049] The first UE 110a further includes a kernel 315 which is a core component serving as the primary interface between hardware components of the first UE 110a and the plurality of services at the backend database 240. The kernel 315 is configured to provide the plurality of services on the first UE 110a to resources available in the communication network 105. The resources include one of a Central Processing Unit (CPU), memory components such as Random Access Memory (RAM) and Read Only Memory (ROM).
[0050] A user request made using the first UE 110a for defining data access in the Inventory Management (IM) may be directed to the system 125 through a load balancer 340. The load balancer 340 directs the user requests to one of multiple data processing units (present in the system 125) based on an active load of user requests. The load balancer 340 may be implemented as a hardware-based load balancer or a software-based load balancer.
[0051] In the preferred embodiment, the user input receiving unit 220 of the one or more processors 205 is communicably connected to the kernel 315 of the first UE 110a. The user input receiving 220 is configured to collect a user input for creating a customizable hierarchy of a combination of physical resources and logical resources. The user input is collected through one or more exposed Application Programming Interfaces (APIs).
[0052] The one or more processors 205 includes the generating unit 225 communicably connected to the user input receiving unit 220 to create a customizable hierarchy of a combination of physical resources and logical resources based on the user input. The one or more processors 205 further includes the model finalizing unit 230 in communication with the generating unit 225 to finalize one or more models for viewing data of the resources based on the user input. The one or more models may include a first model 350, a second model 355, and a nth model 360. Each model may be uniquely created based on the user input received from a corresponding user and may be stored in the backend database 240.
[0053] FIG. 4a illustrates a first hierarchy of resources in a model and FIG. 4b illustrates a second hierarchy of resources in a model, according to one or more embodiments of the present invention. The hierarchy of resources may be understood as link between different models and a sequence/manner in which information of different resources is presented to the user. As illustrated in the first hierarchy shown in FIG. 4a, the site name is shown at the first level, the list of shelfs is shown at the second level, the list of equipment is shown at the third level, the list of chassis is shown at the fourth level, the list of cards is shown at the fifth level, and the list of ports is shown at the sixth level. In the first hierarchy, several models are linked with each other in a top to bottom manner, as described above. Each model is linked with a parent model (a model present above) and a child model (a model present below), except a first model and a last model in the first hierarchy. Further, each model provides details of a resource represented by itself and some details of a resource represented by its parent/child model. For example, a port model may provide port data, such as port name and status. The port model may also provide ciName linking to a card model. A chassis model may provide data related to chassis, such as chassis name, status, and type. The chassis model may also provide an equipment name or equipment ID linking to an equipment model.
[0054] As illustrated in the second hierarchy shown in FIG. 4b, the list of ports is shown at the first level, the list of cards is shown at the second level, the list of chassis is shown at the third level, the list of equipment is shown at the fourth level, the list of shelfs is shown at the fifth level, and the site name is shown at the sixth level. In the second hierarchy, several models are linked with each other in a top to bottom manner, as described above. Each model is linked with a parent model and a child model, except a first model and a last model in the secind hierarchy. Further, each model provides details of a resource represented by itself and some details of a resource represented by its parent/child model. For example, a port model may provide port data, such as port name and status. The port model may also provide ciName linking to a card model. A chassis model may provide data related to chassis, such as chassis name, status, and type. The chassis model may also provide an equipment name or equipment ID linking to an equipment model.
[0055] The user may access the information at the lower level by scrolling down using the UI or clicking information displayed at the higher level. For example, the user may click onto or scroll down the information presented on the first level to view the information at the second level. The user is also able to shift his view of information between the first hierarchy and the second hierarchy as per his requirement in real time. This can be done as per user requirement in real time and on-demand irrespective of the way the data is linked in the storage. The user is also able to create a new hierarchy without the need to write or modify any code and view the information according to the new hierarchy in real time. For creating any hierarchy, the user would be able to select a sequence of models, their linking, and the manner in which information of the resources is stored and presented to the user. For example, if a model stores the information in a tabular format, the rows, columns, and their count can be defined by the user. Once created, the same user or any other user can easily make required customizations.
[0056] FIG. 5 illustrates a flow diagram of a method 500 of defining data access in an Inventory Management (IM), according to one or more embodiments of the present invention. For the purpose of description, the method 500 is described with the embodiments as illustrated in FIG. 2 and FIG. 3 and should nowhere be construed as limiting the scope of the present disclosure.
[0057] At step 505, the method 500 includes the step of collecting, by the user input receiving unit 220 of the one or more processors 205, the user input for creating a customizable hierarchy of a combination of physical resources and logical resources. In one embodiment, the user input is collected through one or more exposed Application Programming Interfaces (APIs). The user input defines link between two or more of site name, building name, floor name, rack name, shelf name, slot name, equipment name, chassis name, card name, and port name. The hierarchy refers to a sequence of presentation of information of the physical resources and the logical resources to the user. For example, presenting the site name at a first level, the list of shelfs at a second level, the list of equipment at a third level, the list of chassis at a fourth level, the list of cards at a fifth level, and the list of ports at a sixth level. Similarly, any hierarchy may be defined as per the user input.
[0058] At step 510, the method 500 includes the step of finalizing, by the model finalizing unit 230 of the one or more processors 205, one or more models for viewing information of the physical resources and the logical resources based on the user input. Within the one or more models for viewing data, tables, columns, and rows are defined. The user may finalize multiple hierarchies for viewing the information of the physical resources and the logical resources in different manner i.e. sequences. The user may also define a name of each customizable hierarchy finalized by him. Further, the number of levels in the customizable hierarchy and a sequence of models present in the customizable hierarchy can be modified i.e. added or subtracted by the user in real time.
[0059] 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 205. The processor 205 is configured to collect a user input, from a User Equipment (UE) 110 for creating a customizable hierarchy of a combination of physical resources and logical resources. The user input is collected through one or more exposed Application Programming Interfaces (APIs). The processor 205 is further configured to finalize one or more models for viewing data of the resources based on the user input.
[0060] 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.
[0061] The above-described techniques (of creating hierarchies) of the present disclosure provide multiple advantages, including obviating the need to write a code or modify the code for creating new customised and customizable hierarchies. The problem solved by this invention is that models in IM can be managed in different ways as per user’s requirement in real time without making change in code i.e., different hierarchies of models can be created in many ways. This reduces the time and efforts of the end users using IM GUI (Graphic User Interface) but want to see the information in different ways. The hierarchy in which user wants to see the data from IM can be created at any time through exposed APIs. This saves a lot of time and development efforts and provides flexibility to users to organize and view model related data in different ways and thereby enhance user experience.
[0062] 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
[0063] Environment - 100;
[0064] Communication network - 105;
[0065] User Equipment - 110;
[0066] Server - 115;
[0067] System - 125;
[0068] Distributed data lake – 130;
[0069] One or more processors -205;
[0070] Memory – 210;
[0071] User input receiving unit – 220;
[0072] Generating unit – 224;
[0073] Model finalizing unit – 230;
[0074] Database – 240;
[0075] Distributed cache – 250;
[0076] First UE – 110a;
[0077] Primary processor of first UE - 305;
[0078] Memory unit of first UE – 310;
[0079] Kernel – 315;
[0080] Load balancer – 340;
[0081] First model – 350;
[0082] Second model – 355;
[0083] Nth model – 360;
[0084] Processor of non-transitory computer-readable medium - 605.

,CLAIMS:CLAIMS
We Claim:
1. A method (500) of defining data access in an Inventory Management (IM), the method (500) comprises the steps of:
collecting (505), by one or more processors (205), a user input for creating a customizable hierarchy of a combination of physical resources and logical resources, wherein the user input is collected through one or more exposed Application Programming Interfaces (APIs); and
finalizing (510), by the one or more processors (205), one or more models for viewing data of the resources based on the user input.

2. The method (500) as claimed in claim 1, wherein the user input defines link between two or more of site name, building name, floor name, rack name, shelf name, slot name, equipment name, chassis name, card name, and port name.

3. The method (500) as claimed in claim 1, wherein within the one or more models for viewing data, tables, columns, and rows are defined.

4. The method (500) as claimed in claim 1, comprising modifying, based on the user input, number of levels in the customizable hierarchy and a sequence of models present in the customizable hierarchy in real time.

5. The method (500) as claimed in claim 1, wherein in a first hierarchy, a site name is shown at first level, list of shelfs is shown at a second level, list of equipment is shown at a third level, list of chassis is shown at a fourth level, list of cards is shown at a fifth level, and a list of ports is shown at a sixth level.

6. The method (500) as claimed in claim 1, wherein in a second hierarchy, a list of ports is shown at a first level, list of cards is shown at a second level, list of chassis is shown at a third level, list of equipment is shown at a fourth level, list of shelfs is shown at a fifth level, and a site name is shown at a sixth level.

7. A system (125) for defining data access in an Inventory Management (IM), the system (125) comprises:
a user input receiving unit (220) configured to collect a user input through one or more exposed Application Programming Interfaces (APIs);
a generating unit (225) configured to create a customizable hierarchy of a combination of physical resources and logical resources based on the user input; and
a model finalizing unit (230) configured to finalize one or more models for viewing data of the resources based on the user input.

8. The system (125) as claimed in claim 7, wherein the user input defines link between two or more of site name, building name, floor name, rack name, shelf name, slot name, equipment name, chassis name, card name, and port name.

9. The system (125) as claimed in claim 7, wherein within the one or more models for viewing data, tables, columns, and rows are defined.

10. The system (125) as claimed in claim 7, wherein the system (125) further performs modifying, based on the user input, number of levels in the customizable hierarchy and a sequence of models present in the customizable hierarchy in real time.

11. A User Equipment (UE) (110) comprising:
a processor (305) coupled with a memory (310), wherein said memory (310) stores instructions which when executed by the processor (305) causes the UE (110) to:
provide a user input for creating a customizable hierarchy of a combination of physical resources and logical resources, wherein the user input is provided through one or more exposed Application Programming Interfaces (APIs),
wherein the processor (305) is configured to perform the steps as claimed in claim 1.