Data management method for forming data element network by using data elements as digital objects

Abstract

The invention provides a data management method for forming a data element network by using data elements as digital objects, which comprises the following steps of: constructing the data element network which comprises a root node, a child node, a data element seller and the data elements; the seller generates a unique identifier for the data element as a custom object individual code of the MA identification system and registers metadata of the custom object individual code to the seller corresponding to the child node; calling a data element through an MA identification system; addressing to corresponding child nodes step by step and establishing DOIP connection; the child nodes are positioned to corresponding seller element libraries; reading corresponding data elements according to the corresponding element result codes; combining the element result and the element metadata information as a digital object, converting the digital object into a binary bit stream, and writing the binary bit stream into DOIP connection; searching the data element: issuing a search task to the child node by the root node through the DOIP connection; the child nodes perform fuzzy search on the data elements; and returning the search result to the digital object metadata information. According to the invention, efficient management and circulation of data elements in different transaction centers are realized.

Description

Technical Field

[0001] The present invention relates to the field of data management technology, and in particular to a data management method, device, equipment and medium for forming a data element network with data elements as digital objects. Background Art

[0002] With the development of big data, the Internet of Things, cloud computing and other fields, data sharing and circulation are becoming increasingly important.

[0003] However, traditional data management systems are usually independent of each other, and data between different systems are difficult to share and integrate, resulting in low utilization of data resources. In the data trading market, although the existing data transmission solutions can guarantee the basic transmission of data, they are insufficient in terms of security, reliability and adaptability, resulting in limited circulation efficiency of data in different trading centers. Summary of the invention

[0004] The present invention provides a data management method, device, equipment and medium in which data elements are used as digital objects to form a data element network, which solves the problem of how to achieve efficient circulation of data in different transaction centers.

[0005] In order to achieve the above objectives, this application adopts the following technical solutions:

[0006] In a first aspect, a data management method is provided in which data elements are used as digital objects to form a data element network, comprising:

[0007] Constructing a data element network that complies with the MA identification system, the data element network including a root node, child nodes, data element sellers, and data elements;

[0008] The data element seller generates a unique identifier for the data element generated by it as a custom object individual code, and registers the metadata of the data element under the child node corresponding to the data element seller;

[0009] Call the data element through the MA identification system: address the corresponding sub-node step by step through the unique identification and establish a DOIP connection; the sub-node locates the corresponding seller component library through the unique identification; reads the corresponding data element according to the corresponding component result code; combines the component result and the component metadata information as a digital object; converts the digital object into a binary bit stream and writes it into the DOIP connection;

[0010] Searching of the data element: the root node issues a search task to the child node through the established DOIP connection; the child node performs a fuzzy search on the data element through a similarity algorithm; and the search result is returned to the digital object metadata information.

[0011] In a first possible implementation of the first aspect, the root node is configured to be independently deployed or mounted on a system that complies with the MA identification system; the child node is registered to the root node as a lower level of the root node, and is configured with a unique child node code under the root node; the data element seller is configured with a unique identifier, and is configured with a unique code as a lower level of the child node; each of the data elements is configured with a unique code under the data element seller.

[0012] Based on the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the structure of the MA identification system includes a user identifier, an object category, and an individual code of the custom object;

[0013] The sub-node code and the unique identifier of the data element seller constitute the object category.

[0014] In a third possible implementation manner of the first aspect, before performing the step of calling the data element through the MA identification system, the following steps are performed:

[0015] The child node first determines whether it is the digital object of the node according to the unique identifier of the digital object; if it is the digital object of the node, the component result library is directly read.

[0016] In a second aspect, a data management device is provided in which data elements are used as digital objects to form a data element network, comprising:

[0017] A data element network module, used to construct a data element network that complies with the MA identification system, wherein the data element network includes a root node, child nodes, data element sellers, and data elements;

[0018] A data element registration module, used for the data element seller to generate a unique identifier for the data element generated by the data element as a custom object individual code, and register the metadata of the data element under the sub-node corresponding to the data element seller;

[0019] The data element calling module is used to call the data element through the MA identification system: address the corresponding sub-node step by step through the unique identification and establish a DOIP connection; the sub-node is located in the corresponding seller component library through the unique identification; read the corresponding data element according to the corresponding component result code; combine the component result and the component metadata information as a digital object; convert the digital object into a binary bit stream and write it into the DOIP connection;

[0020] The data element search module is used for searching the data element: the root node sends the search task to the child node through the established DOIP connection; the child node performs fuzzy search on the data element through a similarity algorithm; and returns the search result to the digital object metadata information.

[0021] In a first possible implementation of the second aspect, the root node is configured to be independently deployed or mounted on a system that complies with the MA identification system; the child node is registered to the root node as the next level of the root node, and is configured with a unique child node code under the root node; the data element seller is configured with a unique identification, and is configured with a unique code as the next level of the child node; each of the data elements is configured with a unique code under the data element seller.

[0022] Based on the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the structure of the MA identification system includes a user identifier, an object category, and an individual code of the custom object;

[0023] The subnode code and the unique identifier of the data element seller constitute the object category. In a third possible implementation of the second aspect, before performing the step of calling the data element through the MA identification system, the following steps are performed:

[0024] The child node first determines whether it is the digital object of the node according to the unique identifier of the digital object; if it is the digital object of the node, the component result library is directly read.

[0025] According to a third aspect, an electronic device is provided, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the data management method in which data elements are used as digital objects to form a data element network as described in the first aspect.

[0026] In a fourth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the data management method in which data elements are used as digital objects to form a data element network as described in the first aspect are implemented.

[0027] This application realizes the efficient management and circulation of data elements in different trading centers by using data elements as digital objects to form a data element network. Through the MA identification system, each data element has a unique identification in the network. Combined with the hierarchical structure of root nodes and child nodes, it breaks the data island and realizes efficient sharing and integration of data. On this basis, through standardized protocols, the registration and calling process of data elements is simplified, the automation of data management is improved, and efficient data search and discovery are realized. At the same time, through protocols and security mechanisms, the security and integrity of data during transmission are guaranteed, and it can further adapt to different network environments and equipment requirements, with good scalability and flexibility. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 A schematic flow chart of a data management method for a data element network composed of a data element as a digital object provided in an embodiment of the present application;

[0029] Figure 2 A schematic diagram of the structure of an MA identification system provided in an embodiment of the present application;

[0030] Figure 3 A schematic flow chart of calling a data element through an MA identification system provided in an embodiment of the present application;

[0031] Figure 4 A structural block diagram of a data management device that uses a data element as a digital object to form a data element network provided in an embodiment of the present application;

[0032] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to further explain the technical means and effects adopted by the present invention to achieve the predetermined purpose, the technical solutions in the embodiments of the present application are clearly described. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of the present application.

[0034] The terms "first", "second", etc. in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0035] The description of the method flow in the specification of the present application and the steps of the flowchart in the drawings of the present specification do not have to be strictly executed according to the step numbers, and the method steps can be executed in a different order. Moreover, some steps can be omitted, multiple steps can be combined into one step, and / or one step can be decomposed into multiple steps.

[0036] In the following, in conjunction with the accompanying drawings and preferred embodiments, the data management method, device, equipment and medium for the data elements provided in the embodiments of the present application as digital objects constituting a data element network are described in detail as follows.

[0037] First, the application scenario of the data management method in which the data elements of the embodiment of the present application are used as digital objects to constitute a data element network is described in detail.

[0038] Traditional data management systems are usually independent of each other, forming data islands. Data between different systems are difficult to share and integrate, resulting in low utilization of data resources. In existing data management, the registration and call process of data often requires complex configuration and manual operation, which is inefficient and error-prone. In a large-scale data environment, how to quickly and accurately search and find the required data is a challenge. Existing data search technology usually relies on keyword matching, but this method does not work well when faced with complex data structures and diverse data types.

[0039] In response to the above technical problems, the present application provides a data management method in which data elements are used as digital objects to constitute a data element network. The method aims to achieve efficient sharing and circulation of data by constructing a data element network composed of data elements as digital objects through a standardized identification system, a hierarchical network structure, and an efficient DOIP protocol, while ensuring the security and adaptability of data; at the same time, it also improves the standardization and accuracy of data management and enhances the scalability and flexibility of the system.

[0040] See also Figure 1 , the embodiment of the present application provides a data management method in which data elements are used as digital objects to form a data element network, such as Figure 1 As shown, the data management of the embodiment of the present application includes:

[0041] Step S1, constructing a data element network that complies with the MA identification system, the data element network includes a root node, child nodes, data element sellers and data elements.

[0042] The structure of the MA identification system includes user identification, object category and custom object individual code, see Figure 2 The root node, as the global management node of the data element network, is responsible for coordinating and managing all child nodes; the child nodes are responsible for managing the data component sellers and their components; the data component sellers are responsible for managing and providing specific data components; the data component is the smallest independently usable data unit with specific functions or uses in data management and transactions.

[0043] In some possible implementations, the root node is configured to be independently deployed or mounted on a system that complies with the MA identification system; the child node is the next level of the root node, the child node is registered to the root node, and has a unique child node code under the root node; the data component seller has a unique identification and has a unique code as the next level of the child node; each data component has a unique code under the data component seller.

[0044] In specific implementation, the root node can be deployed independently or mounted in a system that complies with the MA identification system. Subnodes must be registered to the root node. The registration adopts the digital object IRP protocol of the Digital Network (the underlying implementation of the IRP protocol is one of TCP / TLS / UDP), which can adapt to various network environments. The root node identifier can be customized or used as a user identifier in the MA representation system.

[0045] The child node is the next level of the root node and has a unique code under the root node. The data element seller of the next level has a unique identifier and has a unique code as the next level of the child node. Each data element under the seller has a unique code under the seller.

[0046] For example:

[0047] MA.XXX.XXXX.123 / 110100TC0.171020878246565 / CHN110101112024001232, where [MA.XXX.XXXX.123] is the user ID applied for by the Data Element Network in the MA identification system, [110100TC0] is the sub-node code, [171020878246565] is the seller ID, the sub-node code + the seller ID together constitute the object category, and [CHN110101112024001232] is the custom object individual code.

[0048] Step S2: The data component seller generates a unique identifier for the data component it generates as the custom object individual code, and registers the metadata of the data component under the child node corresponding to the data component seller.

[0049] In the specific implementation process, when the data component seller generates the data component, he generates a unique ID as the custom object individual code, and registers the data component metadata to the corresponding data component seller under the data element network subnode through the interface. The component metadata information can be expressed in JSON format and written into the data element network subnode when registering.

[0050] In some possible implementations, when the metadata of a data component is registered under the data component seller corresponding to the child node, if the child node code in the object category (child node code + seller identifier) ​​is inconsistent with the child node currently registered and called, the following steps are performed:

[0051] The registration request first calls the local element network subnode interface;

[0052] If the child node code is different from the root node code, return to the root node for addressing;

[0053] Find the corresponding object category from the root node and route the component information through the root node to the corresponding child node.

[0054] During the specific implementation process, after finding the corresponding object category from the root node, the component information is routed to the corresponding child node through the digital network DOIP protocol (the underlying implementation of the DOIP protocol is one of TCP / TLS / UDP) via the root node, and the DOIP protocol corresponding addDo (add digital object) basic operation is called to write the component metadata.

[0055] Step S3, calling the data element through the MA identification system: addressing the corresponding child node step by step through the unique identification and establishing a DOIP connection; the child node locates the corresponding seller component library through the unique identification; reads the corresponding data element according to the corresponding component result code; combines the component result and the component metadata information as a digital object; converts the digital object into a binary bit stream and writes it into the DOIP connection.

[0056] In some possible implementations, before performing the step of calling the data element through the MA identification system, the following steps are performed:

[0057] The child node first determines whether it is the digital object of this node based on the unique identifier of the digital object; if it is the digital object of this node, it directly reads the component result library.

[0058] In other words, the calling of data components is divided into the following two cases, see Figure 3 :

[0059] Initiate a call at the root node or higher level through the MA identification system: address the corresponding child node step by step through the unique identification, establish a DOIP connection, and through the basic operation of retrieve in the data network, the child node locates the corresponding seller component library through the seller identification, and reads the corresponding data component according to the corresponding component result code. The component result is assembled with the component metadata as a digital object, converted into binary bits and written into the Element returned by DOIP.

[0060] Initiate a call directly at a child node: When calling a component, the element network child node first determines whether it is a digital object of this node based on the unique identifier of the digital object. If it is, it directly reads the component result library. If not, it routes to the corresponding child node through the root node. The subsequent steps are basically the same as the above case of initiating a call at the root node or higher level through the MA identification system.

[0061] Step S4, search of data elements: the root node sends the search task to the child node through the established DOIP connection; the child node performs fuzzy search on the data element through a similarity algorithm; and returns the search result to the digital object metadata information.

[0062] Based on the above technical solution, this application realizes the efficient management and circulation of data elements in different trading centers by using data elements as digital objects to form a data element network. Through the MA identification system, each data element has a unique identification in the network. Combined with the hierarchical structure of root nodes and child nodes, data silos are broken and efficient data sharing and integration are realized. On this basis, through the standardized IRP protocol and DOIP protocol, the registration and calling process of data elements is simplified, the automation of data management is improved, and efficient data search and discovery are realized. At the same time, through protocols and security mechanisms, the security and integrity of data during transmission are guaranteed, and it can further adapt to different network environments and equipment requirements, with good scalability and flexibility.

[0063] See also Figure 4 , corresponding to the above-mentioned data element as a digital object to form a data element network data management method embodiment, the present application embodiment provides a data element as a digital object to form a data element network data management device, the data management device comprising:

[0064] The data element network module 1001 is used to construct a data element network that complies with the MA identification system, and the data element network includes a root node, child nodes, data element sellers, and data elements;

[0065] A data component registration module 1002 is used for the data component seller to generate a unique identifier for the data component generated by the data component seller as a custom object individual code, and register the metadata of the data component under the subnode corresponding to the data component seller;

[0066] The data element calling module 1003 is used to call the data element through the MA identification system: address the corresponding sub-node step by step through the unique identification and establish a DOIP connection; the sub-node is located in the corresponding seller component library through the unique identification; read the corresponding data element according to the corresponding component result code; combine the component result and the component metadata information as a digital object; convert the digital object into a binary bit stream and write it into the DOIP connection;

[0067] The data element search module 1004 is used for searching the data element: the root node sends the search task to the child node through the established DOIP connection; the child node performs a fuzzy search on the data element through a similarity algorithm; and returns the search result to the digital object metadata information.

[0068] Furthermore, the root node is configured to be independently deployed or mounted on a system that complies with the MA identification system; the child node is registered to the root node as the next level of the root node, and is configured with a unique child node code under the root node; the data element seller is configured with a unique identification, and is configured with a unique code as the next level of the child node; each of the data elements is configured with a unique code under the data element seller.

[0069] Furthermore, the structure of the MA identification system includes a user identification, an object category and an individual code of the custom object;

[0070] The sub-node code and the unique identifier of the data element seller constitute the object category.

[0071] Furthermore, before performing the step of calling the data element through the MA identification system, the following steps are performed:

[0072] The child node first determines whether it is the digital object of the node according to the unique identifier of the digital object; if it is the digital object of the node, the component result library is directly read.

[0073] The above-mentioned data elements as a data management device for a data element network composed of digital objects implement the steps and various processes of the data management method embodiment of the above-mentioned data elements as digital objects composed of a data element network, and can achieve the same technical effect. To avoid repetition, they will not be repeated here.

[0074] See also Figure 5, corresponding to the above-mentioned data elements as digital objects constituting a data element network data management method embodiment, the present application embodiment provides an electronic device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the steps and various processes of the above-mentioned data elements as digital objects constituting a data element network data management method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0075] The memory 1009 can be used to store software programs and various data. The memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 1009 may include a volatile memory or a non-volatile memory, or the memory 1009 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 1009 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0076] The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1010.

[0077] Corresponding to the above-mentioned data elements as digital objects constituting a data element network data management method embodiment, the embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by the processor, the steps and various processes of the above-mentioned data elements as digital objects constituting a data element network data management method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0078] The processor is the processor in the electronic device described in the above embodiment of the present application. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0079] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0080] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0081] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A data management method in which data elements are used as digital objects to form a data element network, characterized in that: include: Constructing a data element network that complies with the MA identification system, the data element network including a root node, child nodes, data element sellers, and data elements; The data element seller generates a unique identifier for the data element generated by it as a custom object individual code, and registers the metadata of the data element under the child node corresponding to the data element seller; Calling the data element through the MA identification system: addressing the corresponding sub-node step by step through the unique identification and establishing a DOIP connection; The child node locates the corresponding seller component library through the unique identifier; reads the corresponding data component according to the corresponding component result code; combines the component result and the component metadata information as a digital object; converts the digital object into a binary bit stream and writes it into the DOIP connection; Searching of the data element: the root node issues a search task to the child node through the established DOIP connection; the child node performs a fuzzy search on the data element through a similarity algorithm; and the search result is returned to the digital object metadata information.

2. The data management method according to claim 1, wherein the data elements are used as digital objects to form a data element network, characterized in that: The root node is configured to be independently deployed or mounted in a system that complies with the MA identification system; the child node is the next level of the root node, the child node is registered to the root node, and a unique child node code is configured under the root node; the data component seller is configured with a unique identification, and is configured with a unique code as the next level of the child node; Each of the data elements is configured with a unique code under the data element seller.

3. The data management method according to claim 2, wherein the data elements are used as digital objects to form a data element network, characterized in that: The structure of the MA identification system includes user identification, object category and the individual code of the custom object; The sub-node code and the unique identifier of the data element seller constitute the object category.

4. The data management method according to claim 1, wherein the data elements are used as digital objects to form a data element network, characterized in that: Before performing the step of calling the data element through the MA identification system, perform the following steps: The child node first determines whether it is the digital object of the node according to the unique identifier of the digital object; if it is the digital object of the node, the component result library is directly read.

5. Data elements as digital objects constitute a data management device for a data element network, characterized in that: include: A data element network module, used to construct a data element network that complies with the MA identification system, wherein the data element network includes a root node, child nodes, data element sellers, and data elements; A data element registration module, used for the data element seller to generate a unique identifier for the data element generated by the data element as a custom object individual code, and register the metadata of the data element under the sub-node corresponding to the data element seller; A data element calling module, used to call the data element through the MA identification system: address the corresponding sub-node step by step through the unique identification and establish a DOIP connection; The child node locates the corresponding seller component library through the unique identifier; reads the corresponding data component according to the corresponding component result code; combines the component result and the component metadata information as a digital object; converts the digital object into a binary bit stream and writes it into the DOIP connection; The data element search module is used for searching the data element: the root node sends the search task to the child node through the established DOIP connection; the child node performs fuzzy search on the data element through a similarity algorithm; and returns the search result to the digital object metadata information.

6. The data management device according to claim 5, wherein the data elements are used as digital objects to form a data element network, characterized in that: The root node is configured to be independently deployed or mounted in a system that complies with the MA identification system; the child node is the next level of the root node, the child node is registered to the root node, and a unique child node code is configured under the root node; the data component seller is configured with a unique identification, and is configured with a unique code as the next level of the child node; Each of the data elements is configured with a unique code under the data element seller.

7. The data management device according to claim 6, wherein the data elements are used as digital objects to form a data element network, characterized in that: The structure of the MA identification system includes user identification, object category and the individual code of the custom object; The sub-node code and the unique identifier of the data element seller constitute the object category.

8. The data management device according to claim 5, wherein the data elements are used as digital objects to form a data element network, characterized in that: Before performing the step of calling the data element through the MA identification system, perform the following steps: The child node first determines whether it is the digital object of the node according to the unique identifier of the digital object; if it is the digital object of the node, the component result library is directly read.

9. An electronic device, characterized in that: The electronic device comprises: a memory, a processor and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the steps of the data management method in which the data elements as described in any one of claims 1 to 4 are used as digital objects to form a data element network are implemented.

10. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the data management method as described in any one of claims 1 to 4 are implemented as data elements constituting a data element network as digital objects.

Images