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 MANAGING RELATIONSHIP BETWEEN DATA ITEMS
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 a relationship managing method and system, and in particular, to a method and a system for establishing relationship between data items in a Inventory Management (IM).
BACKGROUND OF THE INVENTION
[0002] An Inventory Management (IM) is an open, standards-based, cloud-native application that provides an intelligent inventory of communications services and resources – from fifth generation (5G) to Fiber – across physical and virtual network technologies. The IM is a standards-based telecommunications inventory management application that enables you to model and manage customers, services, and resources. The IM supports complex business relationships and provides full life-cycle management of services and resources.
[0003] It is known in the art traditionally that the relationships between data items (or data elements) in a data structure need to be predetermined and fixed. That is, the link between the data elements in the data structure are predetermined / pre-decided and fixed before the data structure can be created and populated. For example, for records of students from the same school in a table (say, Table 1), the name of the school may be a common link for establishing a relational structure among them. This relationship between the data / records is predetermined and fixed. This leads to a fixed data structure and the relationship are frozen and cannot be modified on the go.
[0004] It may happen so that as per a new requirement, a relationship between the data elements in two different tables or even the same tables needs to be changed (removed or added / delinking or linking). Besides, it may be required to add new data elements or change (link or de-link) the existing relationship between the data elements. For example, when the results are declared for the students, a new table (Table 2) containing the results may have student ID, name, address, etc. It may be required to link these records in the new table with the table (Table 1) of the school as in the example above.
[0005] In the prior arts, for establishing the relationship, for example between table 1 and table 2, a new attribute may generally be introduced. This adds to the database table columns and requires effort and is time-consuming. A foreign key (FK) is a column or combination of columns that is used to establish and enforce a link between the data in two tables. These keys not only need to be defined at a database layer but also require code modification. This is inefficient, prone to multiple changes, takes time and breaks the integration.
[0006] Alternatively, a change in the relational structure in the database can only be made by change / modification in the code. This is both time consuming and requires a lot of man hours.
[0007] It is desired that the linking or delinking of entities should be achieved without the need of adding any new attributes merely for the purpose of linking and also without writing or modifying the code to save time and efforts.
[0008] There is therefore a need for a solution that overcomes the above challenges and provides for a system and method for linking and delinking of the data elements dynamically and as per requirement.
SUMMARY OF THE INVENTION
[0009] One or more embodiments of the present disclosure provide a system and a method for establishing relationship between data items in an Inventory Management (IM).
[0010] In one aspect of the present invention, a method for managing a relationship between data items. The method includes selecting, by one or more processor, a first data item. Further, the method includes providing, by the one or more processor, at least one first identifier attribute value associated with the first data item. Further, the method includes selecting, by the one or more processor, a second data item. Further, the method includes providing, by the one or more processor, at least one second identifier attribute value associated with the second data item. Further, the method includes linking, by the one or more processor, the first data item and the second data item using the at least one first identifier attribute value and the at least one second identifier attribute value. Further, the method includes modifying, by the one or more processor, the relationship between the first data item and the second data item in response to linking.
[0011] In another aspect of the present invention, a system for managing dynamic modification of a relationship between data items. The system includes a selection module configured to select a first data item. Further, the selection module is configured to provide at least one first identifier attribute value associated with the first data item. Further, the selection module is configured to select a second data item. Further, the selection module is configured to provide at least one second identifier attribute value associated with the second data item. Further, the system includes a linking module configured to link the first data item and the second data item using the at least one first identifier attribute value and the at least one second identifier attribute value. Further, the system includes a modification module configured to manage the relationship between the first data item and the second data item in response to linking.
[0012] In an embodiment, linking the first data item and the second data item using the at least one first identifier attribute value and the at least one first identifier attribute value includes generating, by the one or more processors, a link identifier at the run time, storing, by the one or more processors, the generated link identifier in the first data item and the second data item, storing, by the one or more processors, a plurality of details associated with the generated link identifier in a data structure, and linking, by the one or more processors, the first data item and the second data item using the generated link identifier.
[0013] In an embodiment, the data structure is a link model, where the data structure is stored independent of the first data item and the second data item, and is configured to store a plurality of links between at least two data entities.
[0014] In an embodiment, the first data item includes at least one of a first table and a A-end model. In an embodiment, the second data item includes at least one of a second table and a Z-end model.
[0015] In an embodiment, modifying the relationship between the data items includes at least one of linking the relationship between the data items and delinking the relationship between the data items.
[0016] In an embodiment, the data items are placed in at least one of same tables, same models, different tables and different models.
[0017] In an embodiment, the relationship between the data items is modified without having a commonality between the data items.
[0018] 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
[0019] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. 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.
[0020] FIG. 1 is an exemplary block diagram of an environment for managing a relationship between data items, according to various embodiments of the present disclosure;
[0021] FIG. 2 is a block diagram of a system of FIG. 1, according to various embodiments of the present disclosure;
[0022] FIG. 3 is an example schematic representation of the system of FIG. 1 in which various entities operations are explained, according to various embodiments of the present system;
[0023] FIG. 4 shows a sequence flow diagram illustrating a method for managing the relationship between the data items, according to various embodiments of the present disclosure;
[0024] FIG. 5 is an example flow chart illustrating a method for linking and delinking data elements in data structures, in accordance with an embodiment of the invention;
[0025] FIG. 6 is a bock diagram illustrating an example of linking and de-linking of data elements, in accordance with an embodiment of the invention; and
[0026] FIG. 7 illustrates a system architecture for linking and de-linking data elements in a database, in accordance with an embodiment of the invention.
[0027] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have been necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.
[0028] The foregoing shall be more apparent from the following detailed description of the invention.

DETAILED DESCRIPTION OF THE INVENTION
[0029] 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.
[0030] 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.
[0031] 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.
[0032] The terms “data items” and “data elements” are used interchangeably in the patent disclosure.
[0033] Various embodiments of the invention provide a method for managing a relationship between data items. The method includes selecting, by one or more processor, a first data item. Further, the method includes providing, by the one or more processor, at least one first identifier attribute value associated with the first data item. Further, the method includes selecting, by the one or more processor, a second data item. Further, the method includes providing, by the one or more processor, at least one second identifier attribute value associated with the second data item. Further, the method includes linking, by the one or more processor, the first data item and the second data item using the at least one first identifier attribute value and the at least one second identifier attribute value. Further, the method includes modifying, by the one or more processor, the relationship between the first data item and the second data item in response to linking.
[0034] The present disclosure is about establishing, dynamically, any kind of a link or relationship between any two entities of any two models / tables (whether the entities or elements belong to the same or different tables /models). The entities for which a change in relationship (linking or de-linking) is required may be from the same or different tables / models. That is to say, a user can link/delink any two entries of an IM, an ecommerce platform, and a finance platform any time without changing the structure of model/table or the entity and without the need of writing or modifying the code. This saves a lot of user’s time and efforts wherein, earlier a developer had to pre-determine the relational structure of a database (DB), and any changes in the fixed structure could not be made without making changes / modification in the code.
[0035] The present disclosure provides for dynamic capability of the IM to link / delink a plurality of records without the need for changing / modifying the code for the structure of the DB (Database). Each of the plurality of records may be present in the same tables / models or different tables / models and may have no apparent commonality. A commonality between the records is not required for linking / delinking. In accordance with an embodiment of the invention, this is achieved without the need of any changes required in the code because all the links are made generic in nature which have A-end model / table name along with a set of identifier attributes as well as Z-end model / table name along with another set of identifier attributes. In an embodiment, this step is performed at an application server.
[0036] The method can be used for managing the relationship between the data items without using a foreign key (FK).
[0037] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing a relationship between data items, according to various embodiments of the present disclosure. The environment 100 comprises a plurality of user equipment’s (UEs) 102-1, 102-2, ……,102-n. The at least one UE 102-n from the plurality of the UEs 102-1, 102-2, ……102-n is configured to connect to a system 108 via a communication network 106.
[0038] In accordance with yet another aspect of the exemplary embodiment, the plurality of UEs 102 may be a wireless device or a communication device that may be a part of the system 108. The wireless device or the UE 102 may include, but are not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet 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 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 or VoIP capabilities. A person skilled in the art will appreciate that the plurality of UEs 102 may include a fixed landline, a landline with assigned extension within the network.
[0039] The plurality of UEs 102 may comprise a memory 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 might be configured or designed to store data. The data may pertain to attributes and access rights specifically defined for the plurality of UEs 102. The UE 102 may be accessed by the user, to receive the data item determined by the system 108. The communication network 106, may use one or more communication interfaces/protocols such as, for example, Voice Over Internet Protocol (VoIP), 802.11 (Wi-Fi), 802.15 (including Bluetooth™), 802.16 (Wi-Max), 802.22, Cellular standards such as Code Division Multiple Access (CDMA), CDMA2000, Wideband CDMA (WCDMA), Radio Frequency Identification (e.g., RFID), Infrared, laser, Near Field Magnetics, etc.
[0040] The system 108 is communicatively coupled to a server 104 via the communication network 106. The server 104 can be, for example, but not limited to a standalone server, a server blade, a server rack, an application server, a bank of servers, a business telephony application server (BTAS), a server farm, a cloud server, an edge server, home server, a virtualized server, one or more processors executing code to function as a server, or the like. In an implementation, the server 104 may operate at various entities or a single entity (include, but is not limited to, a vendor side, a service provider side, a network operator side, a company side, an organization side, a university side, a lab facility side, a business enterprise side, a defence facility side, or any other facility) that provides service.
[0041] The communication 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 communication 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.
[0042] The communication 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 communication 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.
[0043] The system 108 may include one or more processors coupled with a memory 204, wherein the memory 204 may store instructions which when executed by the one or more processors may cause the system 108 managing a relationship between the data items in the communication network 106 or the server 104. An exemplary representation of the system 108 for such purpose, in accordance with embodiments of the present disclosure, is shown in FIG. 2 as system 108. In an embodiment, the system 108 may include one or more processor(s) 202. The one or more processor(s) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) may be configured to fetch and execute computer-readable instructions stored in the memory of the system 108. 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.
[0044] The environment 100 further includes the system 108 communicably coupled to the remote server 104 and each UE of the plurality of UEs 102 via the communication network 106. The remote server 104 is configured to manage the relationship between the data items.
[0045] The system 108 is adapted to be embedded within the remote server 104 or is embedded as the individual entity. The system 108 is designed to provide a centralized and unified view of data and facilitate efficient business operations. The system 108 is authorized to access to update/create/delete one or more parameters of their relationship between the data items, which gets reflected in real-time independent of the complexity of network.
[0046] In another embodiment, the system 108 may include an enterprise provisioning server (for example), which may connect with the remote server 104. The enterprise provisioning server provides flexibility for enterprises, ecommerce, finance to update/create/delete information related to the data items in real time as per their business needs. A user with administrator rights can access and retrieve the data items and perform real-time analysis in the system 108.
[0047] The system 108 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 business telephony application server (BTAS), 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 implementation, system 108 may operate at various entities or single entity (for example include, but is not limited to, a vendor side, service provider side, a network operator side, a company side, an organization side, a university side, a lab facility side, a business enterprise side, ecommerce side, finance side, a defence facility side, or any other facility) that provides service.
[0048] However, for the purpose of description, the system 108 is described as an integral part of the remote server 104, without deviating from the scope of the present disclosure. Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0049] Referring to FIG. 2, FIG. 2 illustrates a block diagram of the system (108) provided for managing the relationship between data items, according to one or more embodiments of the present invention. As per the illustrated embodiment, the system 108 includes the one or more processors 202, the memory 204, an input/output interface unit 206, a display 208, and an input device 210. Further the system 108 may comprise one or more processors 202. 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 108 includes one processor 202. However, it is to be noted that the system 108 may include multiple processors as per the requirement and without deviating from the scope of the present disclosure.
[0050] The information related to the data items may be provided or stored in the memory 204 of the system 108. Among other capabilities, 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.
[0051] The memory 204 may comprise any non-transitory storage device including, for example, volatile memory such as Random-Access Memory (RAM), or non-volatile memory such as Electrically Erasable Programmable Read-only Memory (EPROM), flash memory, and the like. In an embodiment, the system may include an interface(s). The interface(s) may comprise 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 interface(s) may facilitate communication for the system. The interface(s) may also provide a communication pathway for one or more components of the system. Examples of such components include, but are not limited to, processing unit/engine(s) and a database. The processing unit/engine(s) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s).
[0052] The information related to the data items may further be configured to render on the user interface 206. The user interface 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 user interface 206 may be rendered on a display 208, implemented using Liquid Crystal Display (LCD) display technology, Organic Light-Emitting Diode (OLED) display technology, and/or other types of conventional display technology. The display 208 may be integrated within the system 108 or connected externally. Further the input device(s) 210 may include, but not limited to, keyboard, buttons, scroll wheels, cursors, touchscreen sensors, audio command interfaces, magnetic strip reader, optical scanner, etc.
[0053] The system 108 may further comprise a centralized database 218. The centralized database 218 may be communicably connected to the processor 202 and the memory 204. The centralized database 218 may be configured to store and retrieve the data item pertaining to features, or services of the enterprise, an ecommerce, and the finance, access rights, attributes, approved list, and authentication data provided by an administrator. Further the remote server 104 may allow the system 108 to update/create/delete one or more parameters of their information related to the data items, which provides flexibility to roll out multiple variants of the data items as per business needs. In another embodiment, the centralized database 218 may be outside the system 108 and communicated through a wired medium and wireless medium.
[0054] 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 the 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 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 an electronic circuitry.
[0055] In order for the system 108 to manage the relationship between the data items, the processor 202 includes a selection module 212, a linking module 214, and a modification module.
[0056] The selection module 212, the linking module 214, and the modification module 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 the electronic circuitry.
[0057] In order for the system 108 to managing dynamic modification of the relationship between the data items, the selection module 212, the linking module 214, and the modification module are communicably coupled to each other.
[0058] The selection module 212 selects a first data item. The first data item, for example, includes a first table and a A-end model. Further, the selection module 212 provides a first identifier attribute value (e.g., name of the company, name of the person, year, or the like) associated with the first data item. Further, the selection module 212 selects a second data item. The second data item, for example, includes a second table and a Z-end model. The data items are placed in at least one of same tables, same models, different tables and different models. Further, the selection module 212 provides a second identifier attribute value associated with the second data item.
[0059] The linking module 214 links the first data item and the second data item using the first identifier attribute value and the second identifier attribute value. In an embodiment, the linking module 214 generates the link identifier at the run time and stores the generated link identifier in the first data item and the second data item. In an embodiment, an information related to the generated link identifier is stored in a link model. Further, the linking module 214 stores a plurality of details (e.g., identifier, range, specific usage or the like) associated with the generated link identifier in a data structure. Further, the linking module 214 links the first data item and the second data item using the generated link identifier.
[0060] The modification module 216 manages the relationship between the first data item and the second data item in response to linking. In an embodiment, the relationship between the data items is modified without having a commonality between the data items. In an embodiment, the relationship between the data items is modified by linking the relationship between the data items. In another embodiment, the relationship between the data items is modified by delinking the relationship between the data items. In an example, the relationship between the first data item and the second data item managed in response to linking is explained in FIG. 6.
[0061] FIG. 3 is an example schematic representation of the system 300 of FIG. 1 in which various entities operations are explained, according to various embodiments of the present system. Referring to FIG. 3, FIG. 3 describes the system 300 for managing dynamic modification of a relationship between data items. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the UE 102 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.
[0062] As mentioned earlier, the first UE 102-1 includes one or more primary processors 305 communicably coupled to the one or more processors 202 of the system 108. The one or more primary processors 305 are coupled with a memory 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 102-1 to transmit the data item update request from the user via an interface module to the system 108 in order to register for a service related to the data item update request. The execution of the stored instructions by the one or more primary processors 305 further enables the first UE 102-1 to transmit location coordinates from where the data item update request is initiated to the one or more processors 202.
[0063] As mentioned earlier, the one or more processors 202 is configured to transmit the response content related to the data item update request to the first UE 102-1. More specifically, the one or more processors 202 of the system 108 is configured to transmit the response content from a kernel 315 to at least one of the first UE 102-1 in response to modifying at least one response content by a plurality of response contents in response to receiving the data item update request from the administrator. The kernel 315 is a core component serving as the primary interface between hardware components of the first UE 102-1 and the system 108. The kernel 315 is configured to provide the plurality of response contents hosted on the system 108 to access resources available in the communication network 106. The resources include one of a Central Processing Unit (CPU), memory components such as Random Access Memory (RAM) and Read Only Memory (ROM).
[0064] As per the illustrated embodiment, the system 108 includes the one or more processors 202, the memory 204, the input/output interface unit 206, the display 208, and the input device 210. The operations and functions of the one or more processors 202, the memory 204, the input/output interface unit 206, the display 208, and the input device 210 are already explained in FIG. 2. For the sake of brevity, we are not explaining the same operations (or repeated information) in the patent disclosure.
[0065] Further, the processor 202 includes the selection module 212, the linking module 214 and the modification module 216. The operations and functions of the selection module 212, the linking module 214 and the modification module 216 are already explained in FIG. 2. For the sake of brevity, we are not explaining the same operations (or repeated information) in the patent disclosure.
[0066] FIG. 4 is a flow chart (400) illustrating a method for managing the relationship between the data items, according to various embodiments of the present system.
[0067] At 402, the method includes selecting the first data item. In an embodiment, the method allows the selection module 212 to select the first data item.
[0068] At 404, the method includes providing the first identifier attribute value associated with the first data item. In an embodiment, the method allows the selection module 212 to provide the first identifier attribute value associated with the first data item.
[0069] At 406, the method includes selecting the second data item. In an embodiment, the method allows the selection module 212 to select the second data item.
[0070] At 408, the method includes providing the second identifier attribute value associated with the second data item. In an embodiment, the method allows the selection module 212 to provide the second identifier attribute value associated with the second data item.
[0071] At 410, the method includes linking the first data item and the second data item using the first identifier attribute value and the second identifier attribute value. In an embodiment, the method allows the linking module 214 to link the first data item and the second data item using the first identifier attribute value and the second identifier attribute value.
[0072] At 412, the method includes modifying the relationship between the first data item and the second data item in response to linking. In an embodiment, the method allows the modification module 216 to modify the relationship between the first data item and the second data item in response to linking
[0073] FIG. 5 is an example flow chart (500) illustrating a method for linking and delinking data item (or data elements) in data structures, in accordance with an embodiment of the invention. At 502, the first table to be linked is selected as A-end model / table. At 504, the identifier attribute values of the selected first table are then filled in the identifiers (e.g., identifier 1, identifier 2, identifier 3…. Identifier 5). At 506, the second table to be linked is selected as Z-end model / table. At 508, the identifier attribute values of the selected second table are then filled in the identifiers (e.g., identifier 1, identifier 2, identifier 3…. Identifier 5). At 510, the unique link-ID is dynamically generated at the run time and stored in both the first table and the second table. The link details corresponding to that link-ID is stored in a separate model/table of links which has a generic structure so as to accommodate link between any two types of entities. For example, “Link” as shown in FIG. 6.
[0074] FIG. 6 is a bock diagram (600) illustrating an example of linking and de-linking of data elements, in accordance with an embodiment of the invention. FIG. 6 shows an employee table/model (602) and an IT Assets table / model (604). The employee table/model (602) includes an EmpID, a name, a department, a manager, an organization and links. The IT Assets table / model (604) includes an AssetID, a serialNo, a devicetype, device details, a warranty and links. To link these two entities, the unique link-ID (606) is dynamically generated at the run time and stored in both the entities. The link details corresponding to the unique link-ID is stored in the separate model/table of links which has a generic structure so as to accommodate link between any two types of entities. For example, table “Link” as shown in FIG. 6.
[0075] The table “Link” contains the A-end details and the Z-end details. In A-end details, model name of the employee table and other identifiers such as Employee ID (identifier 1), Name (identifier 2), Department (identifier 3) and so on are stored. In Z-end details, model name of the IT Assets table and another set of identifiers such as Asset ID (identifier 1), SerialNo (identifier 2), Device Type (identifier 3) and so on are stored. In various embodiments, the number of identifiers may vary. In an embodiment, the number of identifiers is five. It may be apparent in case a table or model has less than five elements, the remaining identifiers in the “Link” table may be left empty.
[0076] In an embodiment, the invention puts no limitation on the way the data is stored. The normalization technique ensures that the elements are linked to one another irrespective of the way the data is stored.
[0077] FIG. 7 illustrates a system architecture 700 for linking and de-linking data elements in the database (e.g., graph DB 708a-708n), in accordance with an embodiment of the invention. The system architecture 700 shows a plurality of IMs (IM1, IM2, IM3) 706a-706n, and corresponding databases - Graph DB 708a-708n. The Link details corresponding to the link-ID is stored in a separate model/table of links. For example, “Link” as shown in FIG. 6, is stored in a distributed data lake 712. The plurality of IMs (IM1, IM2, IM3) 706a-706n are communicated with the load balancer 704 and a distributed cache 710, where the load balancer 704 is communicated with the external system interface 702.
[0078] As such, the above techniques of the present disclosure provide multiple advantages. The establishing of any relationship between any two entities of any two models/tables (same or different) is made fully dynamic. The same can be achieved any time without changing the structure of model/table or the entity or without the need to write or modify the code. This saves a lot of user’s time as well as efforts and provides flexibility to users to organize data in different ways. A commonality between the records is not required for linking / delinking.
[0079] Also, all the links are made generic in nature having the A-end model / table name along with other identifier attributes as well as Z-end model / table name along with another set of identifier attributes. A unique link-ID is dynamically generated at the run time and stored in both entities. The link details corresponding to the link-ID is stored in a separate model/table of links which has a generic structure so as to accommodate link between any two types of entities without changing the structure of model/table or the entity or without the need to write or modify the code. This saves a lot of user’s time as well as efforts and provides flexibility to users to organize data in different ways.
[0080] The proposed method can be used across a inventory management (IM) platform, an ecommerce platform, a finance platform, etc.
[0081] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIGS. 1-7) 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.
[0082] 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
[0083] Environment - 100
[0084] UEs– 102, 102-1-102-n
[0085] Server - 104
[0086] Communication network - 106
[0087] System – 108
[0088] Processor – 202
[0089] Memory – 204
[0090] User Interface – 206
[0091] Display – 208
[0092] Input device – 210
[0093] Selection module - 212
[0094] Linking module - 214
[0095] Modification module – 216
[0096] Centralized Database – 218
[0097] System - 300
[0098] Primary processors -305
[0099] Memory– 310
[00100] Kernel– 315
[00101] System architecture – 700
[00102] External system interface - 702
[00103] Load balancer – 704
[00104] IM(s) - 706a-706n
[00105] Graphic DB(s) - 708a-708n
[00106] Distributed cache - 710
[00107] Distributed data lake - 712

,CLAIMS:CLAIMS:
We Claim
1. A method for managing a relationship between data items, the method comprising the steps of:
selecting, by one or more processors (202), a first data item;
providing, by the one or more processors (202), at least one first identifier attribute value associated with the first data item;
selecting, by the one or more processors (202), a second data item;
providing, by the one or more processor (202), at least one second identifier attribute value associated with the second data item;
linking, by the one or more processors (202), the first data item and the second data item using the at least one first identifier attribute value and the at least one second identifier attribute value; and
modifying, by the one or more processors (202), the relationship between the first data item and the second data item in response to linking.

2. The method as claimed in claim 1, wherein linking the first data item and the second data item using the at least one first identifier attribute value and the at least one first identifier attribute value comprises:
generating, by the one or more processors (202), a link identifier at the run time;
storing, by the one or more processors (202), the generated link identifier in the first data item and the second data item;
storing, by the one or more processors (202), a plurality of details associated with the generated link identifier in a data structure, and
linking, by the one or more processors (202), the first data item and the second data item using the generated link identifier.

3. The method as claimed in claim 2, wherein the data structure is a link model, wherein the data structure is stored independent of the first data item and the second data item, and is configured to store a plurality of links between at least two data entities.

4. The method as claimed in claim 1, wherein the first data item comprises at least one of a first table and a A-end model, and wherein the second data item comprises at least one of a second table and a Z-end model.

5. The method as claimed in claim 1, wherein modifying the relationship between the data items comprises at least one of linking the relationship between the data items and delinking the relationship between the data items.

6. The method as claimed in claim 1, wherein the data items are placed in at least one of same tables, same models, different tables and different models.

7. The method as claimed in claim 1, wherein the relationship between the data items is modified without having a commonality between the data items .

8. A system (108) for managing dynamic modification of a relationship between data items, the system (108) comprising:
a selection module (212) configured to:
select a first data item;
provide at least one first identifier attribute value associated with the first data item;
select a second data item; and
provide at least one second identifier attribute value associated with the second data item;
a linking module (214) configured to:
link the first data item and the second data item using the at least one first identifier attribute value and the at least one second identifier attribute value; and
a modification module (216) configured to:
manage the relationship between the first data item and the second data item in response to linking.

9. The system (108) as claimed in claim 8, wherein the linking module (214) is further configured to:
generate a link identifier at the run time;
store the generated link identifier in the first data item and the second data item;
store a plurality of details associated with the generated link identifier in a data structure, and
link the first data item and the second data item using the generated link identifier.

10. The system (108) as claimed in claim 9, wherein an information related to the generated link identifier is stored in a link model.

11. The system (108) as claimed in claim 8, wherein the first data item comprises at least one of a first table and a A-end model, wherein the second data item comprises at least one of a second table and a Z-end model.

12. The system (108) as claimed in claim 8, wherein modifying the relationship between the data items comprises at least one of linking the relationship between the data items and delinking the relationship between the data items.

13. The system (108) as claimed in claim 8, wherein the data items are placed in at least one of same tables, same models, different tables and different models.

14. The system (108) as claimed in claim 8, wherein the relationship between the data items is modified without having a commonality between the data items.