Data storage and sharing method, entity and storage medium

Abstract

The embodiment of the invention provides a data storage and sharing method, an entity and a storage medium, and the method comprises the steps: obtaining matrix mapping information from total matrix mapping information of global hardware based on an application function deployed by a first entity; the matrix mapping information represents a corresponding relationship between the first entity and the resources of the global application object stored on the first entity; extracting a first application function and a model object library of the first application object from global resources in the matrix mapping information; based on the first application function of the first application object and a model object library, determining a data link, and performing data sharing with a second application object; the second application object and the first application object have a sharing relationship. According to the embodiment of the invention, the validity of data storage can be improved, and the real-time performance of mass data access can be improved.

Description

Technical Field

[0001] This application relates to the field of data storage, and in particular to a method and entity for storing and sharing data, and a storage medium. Background Technology

[0002] With the development of large-scale energy storage systems, the safety of these systems faces challenges. To improve the comprehensive monitoring of safety parameters in energy storage systems, especially battery systems, a single energy storage power station will generate massive amounts of monitoring data points, numbering in the millions per second, requiring massive storage capacity.

[0003] In the current energy storage power station field, the typical method for massive storage is to access storage through parallel access of single or multiple hardware system resources, or to expand storage capacity through static configuration. These methods suffer from insufficient flexibility and some waste of storage system resources. Furthermore, the stored data exhibits poor real-time performance when used on demand by applications in high-traffic and high-real-time scenarios. Summary of the Invention

[0004] The embodiments of this application aim to provide a data storage and sharing method, entity, and storage medium, which can improve the effectiveness of data storage and the real-time nature of data access.

[0005] The technical solution of this application is implemented as follows:

[0006] This application provides a data storage and sharing method, the method including:

[0007] The application functions deployed based on the first entity obtain matrix mapping information from the global hardware's total matrix mapping information; the matrix mapping information represents the correspondence between the resources of the first entity and the global application objects stored thereon.

[0008] Extract the first application function and model object library of the first application object from the global resources in the matrix mapping information;

[0009] Based on the first application function and model object library of the first application object, a data link is determined, and data sharing with the second application object is carried out; the second application object has a sharing relationship with the first application object.

[0010] Understandably, since the matrix mapping information is related to the first entity, it separates the first application function of the first application object and the model object library from its global resources, thus decoupling the first application function from the model object library. This decoupling of information association in the stored matrix mapping information improves the flexibility of subsequent information updates and expansions, and enhances the effectiveness of data storage. When the first application object and the second application object interact, data can be sent directly through the data link. In scenarios where the first and second application objects belong to different entities, this reduces the data request interaction process. By using the data link determined based on the first application function of the first application object and the model object library, rapid data sharing of massive amounts of data among multiple entities is achieved, improving the real-time performance of massive data access.

[0011] In the above scheme, the application function deployed based on the first entity obtains matrix mapping information from the global hardware's total matrix mapping information, including:

[0012] Based on the application functions of each application object deployed by the first entity, deployment requests are issued;

[0013] Receive matrix mapping information segmented from the overall matrix mapping information of the global hardware, based on deployment requirements.

[0014] It is understandable that by issuing deployment requests through the application functions of each application object deployed by the first entity, the first entity can receive deployment requests and obtain matrix mapping information segmented from the total matrix mapping information of the global hardware. Thus, the first entity can obtain its own corresponding matrix mapping information so that it can share data through the matrix mapping information in the future.

[0015] In the above scheme, based on the first application function and model object library of the first application object, a data link is determined to share data with the second application object, including:

[0016] Based on the first application function and model object library of the first application object, configure the link multicast protocol to determine the data link;

[0017] Based on the second application function identifier group extracted from the global resources in the matrix mapping information, data is shared with the second application object through a data link; wherein, the second application function identifier group corresponds to the second application object; the first entity and the second entity use the same data transmission protocol for data transmission.

[0018] Understandably, since the first entity and the second entity use the same data transmission protocol for data transmission, the interaction process for data requests is reduced in scenarios where the first application object and the second application object belong to different entities. By configuring the link multicast protocol based on the first application object's first application function and model object library, the data link is determined, enabling rapid data sharing of massive amounts of data among multiple entities and improving the real-time performance of massive data access.

[0019] In the above scheme, the data link includes: a first data link;

[0020] Based on the first application function and model object library of the first application object, configure the link multicast protocol to determine the data link, including:

[0021] Given that the first application function of the first application object represents the publishing function, multiple first data queue information is determined based on the attribute information of each model in the publishing model object library; the multiple first data queue information includes publishing identifier and first link layer data packet respectively; the model object library includes the publishing model object library;

[0022] Based on information from multiple first data queues, a link multicast protocol is configured to determine the first data link.

[0023] Understandably, when the first application function of the first application object represents the publishing function, multiple first data queues are determined based on the attribute information of each model in the publishing model object library, providing data to be shared subsequently. Furthermore, based on the multiple first data queues, a link multicast protocol is configured to determine the first data link. Data transmission via this first data link eliminates the need for compatibility configurations between entities, enabling rapid data sharing of massive amounts of data among multiple entities and improving the real-time performance of massive data access.

[0024] In the above scheme, the attribute information includes: model importance and dynamic priority;

[0025] Based on the attribute information of each model in the published model object library, multiple first data queue information are determined, including:

[0026] The order in which the model object libraries of each model are sent is determined based on at least one of the model importance and dynamic priority of each model in the published model object library.

[0027] Based on the sending order, information about multiple first data queues is determined.

[0028] Understandably, the sending order of the model object library for each model is determined based on at least one of the model importance and dynamic priority of each model in the published model object library. Based on the sending order, multiple first data queue information is determined, so that the multiple first data queue information has order. When publishing data in the future, it can be ensured that data with high importance or high priority is sent first, thereby improving the timeliness and effectiveness of data in the data sharing process.

[0029] In the above scheme, based on the second application function identifier group extracted from the global resources in the matrix mapping information, data sharing is performed with the second application object through a data link, including:

[0030] If it is determined that the model object library will be published, then based on the second application function identifier group, the first link layer data packet of the published model object library will be sent to the second entity through the first data link.

[0031] Understandably, based on the second application function identifier group, during the process of sending the first link layer data packet to the second entity through the first data link, no compatibility configuration between entities is required, which enables rapid data sharing of massive amounts of data among multiple entities and improves the real-time performance of massive data access.

[0032] In the above scheme, the data link includes: a second data link;

[0033] Based on the first application function and model object library of the first application object, configure the link multicast protocol to determine the data link, including:

[0034] In the case where the first application function of the first application object represents the subscription function, the multicast filtering address of the second data link is configured based on the target address of the subscription model object library, and the second data link is monitored; the model object library includes the target address of the subscription model object library.

[0035] Understandably, when the first application function of the first application object represents the subscription function, the multicast filtering address of the second data link is configured based on the target address of the subscription model object library, and the second data link is monitored to facilitate subsequent data sharing through the second data link. Since no compatibility configuration between entities is required, rapid data sharing of massive amounts of data among multiple entities can be achieved, improving the real-time performance of massive data access.

[0036] In the above scheme, based on the second application function identifier group extracted from the global resources in the matrix mapping information, data sharing is performed with the second application object through a data link, including:

[0037] Based on the second application function identifier group, the second link layer data packets sent by the second entity are received through the second data link.

[0038] Understandably, based on the second application function identifier group, the second data link receives the second link layer data packets sent by the second entity. Since receiving the second link layer data packets sent by the second entity through the second data link does not require compatibility configuration between entities, it enables rapid data sharing of massive amounts of data among multiple entities, improving the real-time performance of massive data access.

[0039] In the above scheme, the target publishing model object library includes: a first publishing identifier, a model encoding identifier, and a storage resource identifier; the subscription model object library includes: a second publishing identifier, an entity identifier, and a group of subscription identifiers.

[0040] Based on the target publishing model object library and the subscription model object library corresponding to the first application object, the second link layer data packets are filtered and extracted to determine the subscription data, including:

[0041] If the first publication identifier and the second publication identifier match successfully, the model code identifier will be matched with the entity identifier.

[0042] If the model encoding identifier and the entity identifier match successfully, the storage resource identifier will be matched with the subscription identifier group.

[0043] If the storage resource identifier and the subscription identifier group match successfully, the model encoding identifier is parsed. If the model encoding identifier is a valid identifier in the local configuration model information, the subscription data information is determined.

[0044] Understandably, since the subscription data is determined by matching the model code identifier with the entity identifier after the first publication identifier and the second publication identifier have successfully matched, and then matching the storage resource identifier with the subscription identifier group after the model code identifier and the entity identifier have successfully matched, and then parsing the model code identifier if the storage resource identifier and the subscription identifier group have successfully matched, and determining the model code identifier if the model code identifier is a valid identifier in the locally configured model information, this process involves a series of identifier matching operations, which can remove invalid information and improve the effectiveness of data processing.

[0045] The above scheme also includes the following methods:

[0046] If the global resources for updating matrix mapping information are updated online, then an update deployment request is issued based on the application functions of each application object deployed by the first entity.

[0047] Receive updated matrix mapping information, which is segmented from the global hardware's total matrix mapping information in response to update deployment requirements;

[0048] Based on the updated matrix mapping information, the updated model object library is confirmed for future data sharing.

[0049] It is understandable that, since the matrix mapping information is information related to the first entity, the first application function of the first application object and the model object library in its global resources are separate and different information, thus decoupling the first application function from the model object library. Therefore, the stored matrix mapping information achieves decoupling in terms of information association. After updating the matrix mapping information, the updated model object library is confirmed, which improves the flexibility of updating and expanding the model object library and enhances the effectiveness of data storage.

[0050] The above scheme also includes the following methods:

[0051] When the application function represents the publishing function, the updated model object library is notified to the subscribed second application objects.

[0052] Understandably, this allows the published model object library of the first entity to be synchronized with the local model library of the second entity, facilitating subsequent data sharing.

[0053] The above scheme also includes the following methods:

[0054] When the application function represents the publishing function, if the global resource for updating matrix mapping information is not updated online, then it is determined whether to send the publishing model object library.

[0055] Understandably, when using the application's functional representation to publish the function, if the global resource for updating matrix mapping information is not updated online, it's necessary to determine whether to send the published model object library to achieve data sharing. Determining whether to send the published model object library without updating matrix mapping information avoids duplicate data transmission, thereby improving the efficiency of data sharing and the effectiveness of data transmission.

[0056] In the above scheme, the matrix mapping information includes: entity identifier, storage resource identifier, first application function identifier, second application function identifier group, and model object library; wherein, when the first application function identifier is a publishing identifier, the second application function identifier group is a subscription identifier group, and the model object library is a publishing model object library; when the first application function identifier is a subscription identifier, the second application function identifier group is a publishing identifier group, and the model object library is a subscribed model object library.

[0057] It is understandable that the matrix mapping information related to the first entity is separated from the first application function and model object library of the first application object in its global resources, thus decoupling the first application function from the model object library. Therefore, the stored matrix mapping information achieves decoupling in information association, improving the flexibility of subsequent information updates and expansions, and enhancing the effectiveness of data storage.

[0058] In the above scheme, the model object library includes: model encoding identifier, model importance, dynamic priority, associated storage resources and associated functional resources; associated functional resources include: associated publishing resources or associated subscription resources.

[0059] Understandably, further explanation of the model object library can provide a more intuitive understanding of its contents. The model object library is an updatable resource library, which facilitates subsequent data updates and thus improves the effectiveness of data storage.

[0060] In the above scheme, the data transmission protocol includes unicast protocol, multicast protocol, or broadcast protocol.

[0061] Understandably, data transmission protocols include unicast, multicast, or broadcast protocols, providing diversity in data transmission protocols.

[0062] This application provides an entity comprising: an acquisition unit, an extraction unit, and a sharing unit, wherein...

[0063] The acquisition unit is used to acquire matrix mapping information from the global hardware's total matrix mapping information based on the application functions deployed on the first entity; the matrix mapping information represents the correspondence between the resources of the first entity and the global application objects stored thereon.

[0064] The extraction unit is used to extract the first application function and model object library of the first application object from the global resources in the matrix mapping information;

[0065] The sharing unit is used to determine the data link based on the first application function and model object library of the first application object, and to share data with the second application object; the second application object has a sharing relationship with the first application object.

[0066] This application provides an entity including: a processor and a memory, wherein,

[0067] Memory, used to store computer programs;

[0068] A processor is used to retrieve and run computer programs from memory to perform the aforementioned methods of data storage and sharing.

[0069] This application provides a computer-readable storage medium storing executable instructions for implementing the above-described data storage and sharing method when executed by a processor.

[0070] This application provides a data storage and sharing method, entity, and storage medium. The method includes: obtaining matrix mapping information from the global hardware's overall matrix mapping information based on the application functions deployed on a first entity; the matrix mapping information characterizes the correspondence between the resources of the first entity and the global application objects stored thereon; extracting the first application function and model object library of the first application object from the global resources in the matrix mapping information; determining a data link based on the first application function and model object library of the first application object, and sharing data with a second application object; the second application object has a sharing relationship with the first application object. By adopting the above scheme, since the matrix mapping information is information related to the first entity, and the first application function and model object library of the first application object are separate and distinct information from its global resources, the first application function and model object library are decoupled. Therefore, the stored matrix mapping information achieves decoupling in information association, improving the flexibility of subsequent information updates and expansions, and enhancing the effectiveness of data storage. When the first application object and the second application object interact with each other, they can directly send data through the data link. In scenarios where the first application object and the second application object are different entities, the interaction process of data request is reduced. By using the data link determined based on the first application function of the first application object and the model object library, massive data can be quickly shared among multiple entities, improving the real-time performance of massive data access. Attached Figure Description

[0071] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0072] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0073] Figure 1 An optional flowchart illustrating a data storage and sharing method provided in an embodiment of this application. Figure 1 ;

[0074] Figure 2A schematic diagram of an optional distributed storage scheme scenario for a data storage and sharing method provided in an embodiment of this application;

[0075] Figure 3 A schematic diagram of an optional matrix mapping information for a data storage and sharing method provided in an embodiment of this application;

[0076] Figure 4 A schematic diagram of an optional model data block for a data storage and sharing method provided in an embodiment of this application;

[0077] Figure 5 An optional flowchart illustrating a data storage and sharing method provided in an embodiment of this application. Figure 2 ;

[0078] Figure 6 An optional flowchart illustrating a data storage and sharing method provided in an embodiment of this application. Figure 3 ;

[0079] Figure 7 An optional flowchart illustrating a data storage and sharing method provided in an embodiment of this application. Figure 4 ;

[0080] Figure 8 An optional flowchart illustrating a data storage and sharing method provided in an embodiment of this application. Figure 5 ;

[0081] Figure 9 A schematic diagram of the structure of an entity provided in an embodiment of this application;

[0082] Figure 10 This is a schematic diagram of the structure of another entity provided in an embodiment of this application. Detailed Implementation

[0083] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the specific technical solutions of this application will be further described in detail below with reference to the accompanying drawings of the embodiments of this application. The following embodiments are used to illustrate this application, but are not intended to limit the scope of this application.

[0084] Unless otherwise defined, all technical and scientific terms used in this application have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terminology used in this application is for the purpose of describing embodiments of this application only and is not intended to be limiting of this application.

[0085] In the following description, references to "some embodiments," "this embodiment," "this application embodiment," and examples, etc., describe a subset of all possible embodiments. However, it is understood that "some embodiments" may be the same subset or different subset of all possible embodiments and may be combined with each other without conflict.

[0086] If the application documents contain similar descriptions such as "first / second", the following explanation shall be added: In the following description, the terms "first / second / third" are used only to distinguish similar objects and do not represent a specific order of objects. It is understood that "first / second / third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0087] Figure 1 This is an optional flowchart illustrating a data storage and sharing method provided in an embodiment of this application, such as... Figure 1 As shown, the data storage and sharing method includes the following steps:

[0088] S101. Based on the application function deployed on the first entity, obtain matrix mapping information from the total matrix mapping information of the global hardware; the matrix mapping information represents the correspondence between the resources of the first entity and the global application objects stored thereon.

[0089] In some embodiments of this application, the data storage and sharing methods are adapted to power systems and massive data processing scenarios.

[0090] In some embodiments of this application, with the development of large-scale energy storage systems, the safety of these systems faces challenges. To improve energy storage systems, this application establishes a global model matrix mapping information for distributed storage of massive amounts of data.

[0091] In some embodiments of this application, the executing entity is any one of multiple entities, namely the first entity. In power system and massive data processing scenarios, the first entity can be a first server. The first server is an accessed distributed storage server. The first server can be an edge server, a cloud server, etc.

[0092] The data storage and sharing method provided in this application embodiment can be applied to different data storage scenarios, and this application embodiment is not limited thereto. When the first server is a cloud server, in the scenario of applying it to an energy storage system, the first server can be an energy storage system cloud platform. This energy storage system cloud platform can connect to and manage the energy storage system. Through the energy storage system cloud platform, the operating data collected by each energy storage system's devices is stored and shared.

[0093] Furthermore, in the case where the first server is an edge server, in the energy storage system scenario, the first server can also be the controller in the Energy Management System (EMS) of the distributed energy storage system, i.e., an industrial control computer. The energy storage system can include: energy storage devices, a Battery Management System (BMS), and other energy management systems.

[0094] In some embodiments of this application, the application functionality deployed by the first entity may include: subscription functionality, and / or, publishing functionality.

[0095] In some embodiments of this application, matrix mapping information represents the correspondence between a first entity and the resources of the global application objects stored thereon. The matrix mapping information is global model data resources allocated to the first entity after object segmentation of the global model object information based on the entity connected to the energy storage power station. The matrix mapping information includes: entity identifier, storage resource identifier, first application function identifier, second application function identifier group, and model object library; wherein, when the first application function identifier is a publishing identifier, the second application function identifier group is a subscription identifier group, and the model object library is a publishing model object library; when the first application function identifier is a subscription identifier, the second application function identifier group is a publishing identifier group, and the model object library is a subscribed model object library.

[0096] In some embodiments of this application, the global hardware's overall matrix mapping information can reflect the location of all data resources. Different data resources are stored in different entity hardware, thereby distributing all data resources through multiple entities. Each entity corresponds to a matrix mapping information. The matrix mapping information stores entity identifiers and storage resource identifiers, thus reflecting the correspondence between entities and storage resources.

[0097] In some embodiments of this application, the first entity is any entity that is accessed.

[0098] In some embodiments of this application, the first entity can obtain matrix mapping information by issuing deployment requests based on the application functions of each application object deployed by the first entity. It then receives matrix mapping information segmented from the total matrix mapping information of the global hardware in response to the deployment requests.

[0099] In some embodiments of this application, the process of the first entity obtaining matrix mapping information is as follows: the application functions of each application object deployed by the first entity send a deployment request to the system that manages the data storage. The system that manages the data storage then extracts the matrix mapping information corresponding to the first entity from the total matrix mapping information of the global hardware based on the application functions of each application object deployed by the first entity.

[0100] For example, Figure 2 This is a schematic diagram of an optional distributed storage scheme scenario for a data storage and sharing method provided in an embodiment of this application, such as... Figure 2 As shown, the energy storage power station configures global model object information based on model data resources. The power station's global dynamic matrix mapping includes multiple hardware (entity) ID-dynamic matrix mappings: Hardware ID 1-dynamic matrix mapping, Hardware ID 2-dynamic matrix mapping, Hardware ID 3-dynamic matrix mapping, Hardware ID 4-dynamic matrix mapping, and Hardware ID n-dynamic matrix mapping. Each hardware ID-dynamic matrix mapping represents the correspondence between a resource ID and a hardware ID, i.e., the relationship between resources and hardware storage. For example, hardware ID 1 corresponds to resource ID 1. Each piece of hardware has different application functions. Some hardware has data publishing capabilities (equivalent to data publishers), some hardware has data subscription capabilities (equivalent to data subscribers), and some hardware has both data publishing and data subscription capabilities (equivalent to both data publishers and data subscribers). Data sharing is a dynamic publisher-subscriber relationship. For two pieces of hardware with a subscription relationship, the hardware with data publishing capabilities can send data to the hardware with data subscription capabilities, and the hardware with data subscription capabilities can receive data from the hardware with data publishing capabilities, thus achieving data sharing between different pieces of hardware.

[0101] It should be noted that the power plant global dynamic matrix mapping refers to the overall matrix mapping information of the global hardware; the hardware ID-dynamic matrix mapping refers to the matrix mapping information. Hardware ID is the entity identifier, and resource ID is the storage resource ID.

[0102] In some embodiments of this application, the matrix mapping information includes: entity identifier (i.e., entity identifier), storage resource identifier, publishing identifier (i.e., first application function identifier), and storage validity identifier (i.e., second application function identifier group) and model data block (i.e., model object library). The model data block includes model encoding identifier, model importance, dynamic priority, associated storage resource, and associated publishing resource. Associated functional resources include: associated publishing resources or associated subscription resources. Associated storage resources include entity identifier and storage resource identifier, and associated publishing resources include publishing identifier and link layer data packets.

[0103] For example, such as Figure 3 As shown, the matrix mapping information includes hardware device ID (i.e., entity identifier), storage resource ID (storage resource identifier), publication ID (i.e., first application function identifier), data subscription ID group (i.e., second application function identifier group), and multiple model data blocks. Each model data block represents a model data block…#mapping table. For example… Figure 4As shown, each model data block represents a model data block N# mapping table (mapping entry), which may include model code ID (i.e., model code identifier), model importance, dynamic priority, associated storage resources, and associated publishing resources. The associated storage resources include hardware device ID and storage resource ID, and the associated publishing resources include publishing ID and publishing information CRC (i.e., first link data packet).

[0104] S102. Extract the first application function and model object library of the first application object from the global resources in the matrix mapping information.

[0105] In some embodiments of this application, the model object library includes: model encoding identifier, model importance, dynamic priority, associated storage resources, and associated functional resources; the associated functional resources include: associated publishing resources or associated subscription resources.

[0106] In some embodiments of this application, the first entity can extract the first application function and model object library of the first application object from the global resources in the matrix mapping information based on the matrix mapping information and through the application functions (publishing function, subscription function) deployed by the first entity.

[0107] In some embodiments of this application, if the application function deployed by the first entity is a subscription function, the first entity can extract data from the global resources in the matrix mapping information to determine the subscription identifier and subscription model object library of the first application object.

[0108] In some embodiments of this application, if the application function deployed by the first entity is a publishing function, the first entity can extract data from the global resources in the matrix mapping information to determine the publishing identifier and publishing model object library of the first application object.

[0109] It should be noted that the first application function is determined by the application nature of the first application object. When the first application object is sending software, the first application function is the publishing function and has a publishing identifier.

[0110] S103. Based on the first application function and model object library of the first application object, determine the data link and perform data sharing with the second application object; the second application object has a sharing relationship with the first application object.

[0111] In some embodiments of this application, the data link includes: a first data link and a second data link.

[0112] In some embodiments of this application, the first entity configures a link multicast protocol based on the first application function and model object library of the first application object, thereby determining the data link. Based on the second application function identifier group extracted from global resources in the matrix mapping information, data is shared with the second application object via the data link.

[0113] In some embodiments of this application, when the first application function and model object library of the first application object on the first entity are a publishing identifier and a publishing model object library, a first data link is determined. Based on the subscription identifier group extracted from the global resources in the matrix mapping information, data sharing is performed with the second application object through the first data link.

[0114] In some embodiments of this application, when the first application function and model object library of the first application object on the first entity are a subscription identifier and a subscription model object library, a second data link is determined. Based on the publication identifier group extracted from the global resources in the matrix mapping information, data sharing is performed with the second application object through the second data link.

[0115] It should be noted that the second application object is the software installed on the second entity. When the first application object on the first entity has its first application function and model object library as a release identifier and release model object library, the first entity must synchronize its local model library.

[0116] Understandably, since the matrix mapping information is related to the first entity, it separates the first application function of the first application object and the model object library from its global resources, thus decoupling the first application function from the model object library. This decoupling of information association in the stored matrix mapping information improves the flexibility of subsequent information updates and expansions, and enhances the effectiveness of data storage. When the first application object and the second application object interact, data can be sent directly through the data link. In scenarios where the first and second application objects belong to different entities, this reduces the data request interaction process. By using the data link determined based on the first application function of the first application object and the model object library, rapid data sharing of massive amounts of data among multiple entities is achieved, improving the real-time performance of massive data access.

[0117] In some embodiments of this application, such as Figure 5 As shown, S101 can be implemented through S1011 and S1012, as follows:

[0118] S1011. Based on the application functions of each application object deployed by the first entity, issue deployment requests.

[0119] In some embodiments of this application, the deployment request is used to request matrix mapping information from the global hardware's total matrix mapping information, which is segmented to correspond to the application functions of each application object deployed by the first entity.

[0120] In some embodiments of this application, the first entity can obtain application functions based on the application objects deployed by the first entity and issue a deployment request.

[0121] S1012. Receive matrix mapping information that is segmented from the total matrix mapping information of the global hardware according to deployment requirements.

[0122] In some embodiments of this application, the first entity may receive a deployment request and obtain matrix mapping information segmented from the total matrix mapping information of the global hardware.

[0123] In some embodiments of this application, after the first entity sends a deployment request, the device storing the total matrix mapping information of the global hardware can extract the matrix mapping information corresponding to the deployment request of the first entity from the total matrix mapping information of the global hardware according to the deployment request, and send the matrix mapping information to the first entity.

[0124] It should be noted that the matrix mapping information is obtained by segmenting the total matrix mapping information of the global hardware based on the application functions deployed by the first entity.

[0125] It is understandable that by issuing deployment requests through the application functions of each application object deployed by the first entity, and receiving deployment requests, the first entity can obtain matrix mapping information segmented from the global hardware's total matrix mapping information. Thus, the first entity can obtain its own corresponding matrix mapping information, enabling subsequent data sharing through this matrix mapping information.

[0126] In some embodiments of this application, such as Figure 6 As shown, S103 can be implemented through S201 and S202, as follows:

[0127] S201. Based on the first application function and model object library of the first application object, configure the link multicast protocol to determine the data link.

[0128] In some embodiments of this application, when the first application function of the first application object represents the publishing function, the model object library of the first application object can be determined as the publishing model object library, the first entity configures the Ethernet data link multicast protocol, and the first data link is determined.

[0129] In some embodiments of this application, the published model object library contains multiple models with different levels of importance and different dynamic priorities.

[0130] In some embodiments of this application, when the first application function of the first application object represents the subscription function, the model object library of the first application object can be determined as the subscription model object library, and the first entity configures the multicast filtering address of the second data link, thereby determining the second data link.

[0131] S202. Based on the second application function identifier group extracted from the global resources in the matrix mapping information, data is shared with the second application object through a data link; wherein, the second application function identifier group corresponds to the second application object; the first entity and the second entity use the same data transmission protocol for data transmission.

[0132] In some embodiments of this application, the second application function identifier group corresponds to the second application object. The first entity and the second entity use the same data transmission protocol for data transmission.

[0133] In some embodiments of this application, the second entity is a distributed storage entity that installs the second application object.

[0134] In some embodiments of this application, the data transmission protocol includes unicast, multicast, or broadcast protocols. The protocol layer can be a Layer 2 protocol, a real-time protocol, a TCP / IP application protocol, etc.

[0135] In some embodiments of this application, a unicast protocol is a unicast routing protocol that forwards communication to a location on the Internet from a source host to a destination host via a router. The Internet has at least two networks connected by routers. Routers are network layer intermediary systems used to connect multiple networks together according to common network layer protocols (such as TCP / IP). A network is part of a networking infrastructure (including repeaters, hubs, and bridge / Layer 2 switches) connected by routers and associated with the same network layer address, called a network address or network ID. A multicast protocol allows data sent by one host to be replicated to multiple hosts joining the multicast through network routers and switches, providing a one-to-many communication method. The difference between multicast and the widely used unicast protocol is that when a host sends the same data to n hosts using a unicast protocol, the sending host needs to send it to each of the n hosts separately, for a total of n transmissions. When a host sends the same data to n hosts using a multicast protocol, it only needs to send it once; the data is replicated and sent to each receiver level by routers and switches in the network, thus saving both physical resources and network backbone bandwidth. A broadcast protocol refers to sending a message to all devices in a network, rather than to a specific device.

[0136] It's important to note that, compared to broadcast protocols, multicast protocols only copy data to the receiver after the receiver sends a request, thus saving bandwidth for the receiver. Broadcast, on the other hand, sends all broadcast information to all devices regardless of whether the receiver needs it, thereby consuming a significant amount of the receiver's access bandwidth.

[0137] In some embodiments of this application, the first entity shares data with the second application object through a data link based on the second application function identifier group extracted from the global resources in the matrix mapping information.

[0138] Understandably, since the first entity and the second entity use the same data transmission protocol for data transmission, the interaction process for data requests is reduced in scenarios where the first application object and the second application object belong to different entities. By configuring the link multicast protocol based on the first application object's first application function and model object library, the data link is determined, enabling rapid data sharing of massive amounts of data among multiple entities and improving the real-time performance of massive data access.

[0139] In some embodiments of this application, S201 can be implemented by S2011 and S2012, as follows:

[0140] S2011. In the case of the first application function representing the publishing function of the first application object, multiple first data queue information are determined based on the attribute information of each model in the publishing model object library; the multiple first data queue information respectively include the publishing identifier and the first link layer data packet; the model object library includes the publishing model object library.

[0141] In some embodiments of this application, the multiple first data queue information respectively include a publication identifier and a first link layer data packet; the model object library includes a published model object library.

[0142] In some embodiments of this application, the attribute information includes: model importance and dynamic priority.

[0143] In some embodiments of this application, when the first application function of the first application object represents the publishing function, multiple first data queue information are determined based on the model importance and dynamic priority of each model in the publishing model object library.

[0144] In some embodiments of this application, when the first entity determines to send and publish the model object library, the first entity needs to sort the publishing priority of the models according to the model importance and dynamic priority of each model in the publishing object library, and determine multiple first data queue information.

[0145] It should be noted that the first link layer data packet is the data information to be published corresponding to the model in the publishing model library. The publishing identifier is the identification information corresponding to the application function of the first entity.

[0146] It should be noted that the first link layer data packet carries the storage resources stored on the first entity.

[0147] In some embodiments of this application, the sending order of the model object library for each model is determined based on at least one of the model importance and dynamic priority of each model in the published model object library; and multiple first data queue information is determined based on the sending order.

[0148] It should be noted that each model has its own corresponding model code identifier.

[0149] In some embodiments of this application, the first entity may determine the sending order of the model object library for each model based on at least one of the model importance and dynamic priority of each model in the published model object library, and determine multiple first data queue information by the sending order.

[0150] For example, taking a model with four models, the order of sending the model object libraries for each model is determined based on at least one of the model importance and dynamic priority of each model in the published model object library, as follows: the model object library of the first model, the model object library of the second model, the model object library of the third model, and the model object library of the fourth model.

[0151] It should be noted that the first model is the model with the highest release importance and priority in the release model object library. The second model is the model with the second highest release importance and priority in the release model object library. The third model is the model with the third highest release importance and priority in the release model object library. The fourth model object library includes all models in the release model object library except for the first, second, and third models.

[0152] Understandably, the sending order of the model object library for each model is determined based on at least one of the model importance and dynamic priority of each model in the published model object library. Based on the sending order, multiple first data queue information is determined, so that the multiple first data queue information has order. When publishing data in the future, it can be ensured that data with high importance or high priority is sent first, thereby improving the timeliness and effectiveness of data in the data sharing process.

[0153] S2012. Based on multiple first data queue information, configure the link multicast protocol to determine the first data link.

[0154] In some embodiments of this application, the first entity may configure a link multicast protocol based on multiple first data queue information to determine the first data link.

[0155] In some embodiments of this application, if it is determined that a publishing model object library will be sent, a first link layer data packet of the publishing model object library will be sent to the second entity through the first data link based on the second application function identifier group.

[0156] Understandably, based on the second application function identifier group, during the process of sending the first link layer data packet to the second entity through the first data link, no compatibility configuration between entities is required, which enables rapid data sharing of massive amounts of data among multiple entities and improves the real-time performance of massive data access.

[0157] In some embodiments of this application, if it is determined that a publishing model object library will be sent, the first entity will, based on the second application function identifier group, send the first link layer data packet of the first model, the first link layer data packet of the second model, the first link layer data packet of the third model, and the first link layer data packet of the fourth model to the second entity in sequence through the first data link.

[0158] Understandably, when the first application function of the first application object represents the publishing function, multiple first data queues are determined based on the attribute information of each model in the publishing model object library, providing data to be shared subsequently. Furthermore, based on the multiple first data queues, a link multicast protocol is configured to determine the first data link. Data transmission via this first data link eliminates the need for compatibility configurations between entities, enabling rapid data sharing of massive amounts of data among multiple entities and improving the real-time performance of massive data access.

[0159] In some embodiments of this application, S103 can also be implemented by S203, as follows:

[0160] S203. When the first application function of the first application object represents the subscription function, based on the target address of the subscription model object library, configure the multicast filtering address of the second data link and listen to the second data link; the model object library includes the target address of the subscription model object library.

[0161] In some embodiments of this application, the model object library includes a target address for subscribing to the model object library.

[0162] In some embodiments of this application, when the first application function of the first application object represents the subscription function, the first entity can configure the multicast filtering address of the second data link through the target address of the subscription model object library and listen to the second data link.

[0163] Understandably, when the first application function of the first application object represents the subscription function, the multicast filtering address of the second data link is configured based on the target address of the subscription model object library, and the second data link is monitored to facilitate subsequent data sharing through the second data link. Since no compatibility configuration between entities is required, rapid data sharing of massive amounts of data among multiple entities can be achieved, improving the real-time performance of massive data access.

[0164] In some embodiments of this application, based on a second application function identifier group, a second link layer data packet sent by a second entity is received via a second data link.

[0165] In some embodiments of this application, when the second application function identifier group is a publishing identifier group, the first entity receives the second link layer data packet sent by the second entity through the second data link based on the publishing identifier group.

[0166] Understandably, based on the second application function identifier group, the second data link receives the second link layer data packets sent by the second entity. Since the second data link receives the second link layer data packets sent by the second entity, no compatibility configuration between entities is required. Therefore, it is possible to achieve rapid data sharing of massive amounts of data among multiple entities, thereby improving the real-time performance of massive data access.

[0167] In some embodiments of this application, after receiving a second link-layer data packet sent by a second entity via a second data link based on a second application function identifier group, the data storage and sharing method further includes the following steps:

[0168] S301. Filter and extract the data packets of the second link layer to determine the subscription data.

[0169] In some embodiments of this application, the first entity may filter and extract second link layer data packets to determine the subscription data.

[0170] In some embodiments of this application, the first entity obtains the target publishing model object library for subscribing to the second application object from the second link layer data packet; based on the target publishing model object library and the subscription model object library corresponding to the first application object, the second link layer data packet is filtered and extracted to determine the subscription data.

[0171] In some embodiments of this application, the target publishing model object library includes: a first publishing identifier, a model encoding identifier, and a storage resource identifier; the subscription model object library includes: a second publishing identifier, an entity identifier, and a group of subscription identifiers.

[0172] In some embodiments of this application, the first entity may match the first publication identifier with the second publication identifier. If the first publication identifier and the second publication identifier match successfully, the model encoding identifier is matched with the entity identifier. If the model encoding identifier and the entity identifier match successfully, the storage resource identifier is matched with the subscription identifier group. If the storage resource identifier and the subscription identifier group match successfully, the model encoding identifier is parsed. If the model encoding identifier is a valid identifier in the locally configured model information, the subscription data is determined.

[0173] In some embodiments of this application, the first entity can obtain the target published model object library from the second link layer data packet. The target published model object library includes: a first published identifier, a model encoding identifier, and a storage resource identifier; the subscription model object library includes: a second published identifier, an entity identifier, and a group of subscription identifiers. If the first published identifier matches the pre-registered information (i.e., the second published identifier), the storage resource information of the second link layer data packet is read; if the model encoding identifier of the storage resource information matches the entity identifier, the storage resource identifier in the storage resource information is read; if the storage resource identifier matches the storage valid identifier (i.e., the group of subscription identifiers), the model encoding identifier is parsed, and if the model encoding identifier is a valid identifier in the locally configured model information, the subscription data is extracted.

[0174] For example, the process of resolving model IDs through a dynamic protocol is performed according to the following steps:

[0175] 1) Read the broadcast ID (e.g., multicast MAC) from the information. If it does not match the multicast MAC information pool of the network card during initial registration, filter and drop the order; if the condition is met, proceed to step 2).

[0176] 2) Read the storage resource information and determine whether the model ID matches the hardware device ID. If they do not match, discard the process; if they meet the conditions, proceed to step 3).

[0177] 3) Read the local storage resource ID and determine whether the storage resource ID is a valid local storage ID (i.e., a data subscription ID group). If it does not match, discard it; if it meets the condition, proceed to step 4.

[0178] It should be noted that the ID can be information encoding or physical location.

[0179] 4) Parse the model code ID and determine whether the model code ID is a valid ID in the local configuration model table. If it does not match, discard it. If it meets the conditions, store the information locally and synchronize the information.

[0180] Understandably, the subscription data is determined by matching the model code identifier with the entity identifier after the first and second publication identifiers match successfully; then, if the model code identifier and entity identifier match successfully, the storage resource identifier is matched with the subscription identifier group; and finally, if the storage resource identifier and subscription identifier group match successfully, the model code identifier is parsed, and the final identifier is determined if the model code identifier is a valid identifier in the locally configured model information. Therefore, this process involves a series of identifier matching steps, which removes invalid information and improves the effectiveness of data processing.

[0181] S302. Store the subscription data in the local database corresponding to the first application object.

[0182] In some embodiments of this application, the first entity may store the subscription data in a local database corresponding to the first application object.

[0183] Understandably, filtering and extracting data packets at the second link layer can filter out data that is not subscribed to by the first entity, retain only the subscribed data, and store the subscribed data in a local database. This allows for precise data storage and improves the effectiveness of data sharing.

[0184] In some embodiments of this application, the data storage and sharing method further includes: if global resources for online updating matrix mapping information are used, then issuing an update deployment request based on the application functions of each application object deployed by the first entity. The updated matrix mapping information, segmented from the total matrix mapping information of the global hardware in response to the update deployment request, is received; based on the updated matrix mapping information, the updated model object library is confirmed for future data sharing.

[0185] In some embodiments of this application, if the first entity updates the global resources of matrix mapping information online, it needs to issue an update deployment request based on the application functions of each application object deployed by the first entity in order to obtain the updated matrix mapping information; based on the updated matrix mapping information, the updated model object library is confirmed for data sharing in the next instance.

[0186] Understandably, since the matrix mapping information is information related to the first entity, it separates the first application function of the first application object and the model object library from its global resources, thus decoupling the first application function from the model object library. Therefore, the stored matrix mapping information achieves decoupling in terms of information association. After updating the matrix mapping information, the updated model object library is confirmed, improving the flexibility of updating and expanding the model object library and enhancing the effectiveness of data storage.

[0187] In some embodiments of this application, when the application function characterizes the publishing function, the updated model object library is notified to the subscribed second application object.

[0188] In some embodiments of this application, after confirming the updated model object library based on the updated matrix mapping information, the updated model object library can be sent to the second application object that subscribes to the model publishing object library of the first entity via message and multicast.

[0189] Understandably, this allows the published model object library of the first entity to be synchronized with the local model library of the second entity, facilitating subsequent data sharing.

[0190] In some embodiments of this application, when the application function characterizes the publishing function, if the global resource of matrix mapping information is not updated online, it is determined whether to send the publishing model object library.

[0191] In some embodiments of this application, when the application function characterizes the publishing function, if the global resource for matrix mapping information is not updated online, it is determined whether to send the publishing model object library to achieve data sharing. If the publishing model object library is sent, multiple first data queue information is determined, and the first link data packet is sent sequentially; if the publishing model object library is not sent, the matrix mapping information is reacquired.

[0192] Understandably, when using the application's functional representation to publish the function, if the global resource for updating matrix mapping information is not updated online, it's necessary to determine whether to send the published model object library to achieve data sharing. Determining whether to send the published model object library without updating matrix mapping information avoids duplicate data transmission, thereby improving the efficiency of data sharing and the effectiveness of data transmission.

[0193] In some embodiments of this application, the process of determining the overall matrix mapping information of the global hardware is as follows: a large number of resources are classified to obtain multiple sub-resources, which are stored on each entity respectively; then, based on the application functions deployed on each entity, data subscription and / or resource extraction are performed to obtain subscription information and / or publication information corresponding to each entity; based on the subscription information and / or publication information corresponding to each entity, the storage valid identifier corresponding to each entity is determined; wherein, the storage valid identifier includes the publication storage valid identifier and / or subscription storage valid identifier.

[0194] For example, each entity subscribes to the model data of other entities based on the deployed application functions (e.g., subscriber functions, publisher functions), forming a valid subscription storage identifier, establishing a subscription relationship with other hardware, and filtering subscription information at runtime. Each entity extracts published resources to form a valid published storage identifier. The valid subscription storage identifier and the valid published storage identifier are used to store data in the global model matrix mapping information to achieve data sharing.

[0195] Understandably, based on the application functions corresponding to each entity, data subscription and / or resource extraction are performed to obtain the subscription information and / or publication information corresponding to each entity; based on the subscription information and / or publication information corresponding to each entity, the storage valid identifier corresponding to each entity is determined. After determining the storage valid identifier corresponding to each entity, data can be shared through the entity where the storage valid identifier is located, thereby realizing the on-demand use of data.

[0196] In some embodiments of this application, a first entity is used as an example for illustration. If the first entity has a subscription function, data subscription is performed to obtain the subscription information of the first entity; if the first entity has a publishing function, resource extraction is performed to obtain the publishing information of the first entity; if the first entity has both subscription and publishing functions, data subscription and resource extraction are performed to determine the subscription information and publishing information corresponding to the first entity.

[0197] For example, a first entity may have multiple software programs, namely subscription software and publishing software (i.e., the first entity has both subscription and publishing capabilities). Subscription software A has 10 models and a publishing identifier. Publishing software B has 20 models and a subscription identifier. Subscription software A and subscription software B can also share data; this is internal data sharing within the same entity.

[0198] Understandably, if the first entity has a subscription function, data subscription is performed to obtain the subscription information of the first entity; if the first entity has a publishing function, resource extraction is performed to obtain the publishing information of the first entity; if the first entity has both subscription and publishing functions, data subscription and resource extraction are performed to determine the subscription information and publishing information corresponding to the first entity. After determining the subscription information and / or publishing information corresponding to the first entity, data sharing between the first entity and the second entity can be achieved through the subscription information and / or publishing information.

[0199] In some embodiments of this application, such as Figure 7 As shown, the data publishing process of a hardware system (entity) with data publishing capabilities is as follows:

[0200] S1, Application loading matrix mapping information of the hardware system.

[0201] S2. Extract the release identifier and release model object library.

[0202] In some embodiments of this application, applications deployed on a hardware system (entity) can extract a release identifier and a release model object library based on the matrix mapping information after loading the matrix mapping information. The model object library includes multiple different models, each with corresponding stored resource data.

[0203] S3. Determine the first data queue information based on model importance and dynamic priority.

[0204] In some embodiments of this application, multiple first data queue information includes a publication identifier and a publication model object library.

[0205] S4. Configure the link multicast protocol and determine the first data sharing link.

[0206] S5. Whether to publish the model object library.

[0207] In some embodiments of this application, if a model object library is published, then S6 is executed; if a model object library is not published, then S1 is executed.

[0208] S6. Publish a library of model objects that are highly important and have a high priority.

[0209] In some embodiments of this application, a library of model objects with high importance and high priority is published, that is, a first link layer data packet of a model with high importance and high priority is published.

[0210] S7. Publish a library of model objects that are of secondary importance but high priority.

[0211] In some embodiments of this application, a library of model objects with secondary importance but high priority is published, that is, a first link layer data packet of a model with secondary importance but high priority is published.

[0212] S8. Publish a library of model objects with low importance but high priority.

[0213] In some embodiments of this application, a library of model objects with low importance and high priority is published, that is, a first link layer data packet of a model with low importance and high priority is published.

[0214] S9. Publish model object libraries with other importance and priority.

[0215] In some embodiments of this application, first link layer packets of other high-importance and high-priority models are published.

[0216] S10. Determine whether to update the matrix mapping information.

[0217] In some embodiments of this application, if the matrix mapping information is updated online, then S11 is executed; if the matrix mapping information is not updated online, then S5 is executed.

[0218] S11. Update the release identifier and release model object library.

[0219] In some embodiments of this application, S1 and S12 are executed after S11 is executed.

[0220] S12. Notify the subscribed second application objects of the updated release identifier and release model object library.

[0221] Understandably, there are no system-bound constraints on third-party software and hardware, making it suitable for big data distributed storage and sharing scenarios. Entities are not limited to cloud or edge application scenarios, and it can realize the data publishing function of the publishing server, thereby enabling data sharing with other entities.

[0222] In some embodiments of this application, such as Figure 8 As shown, the data reception process for hardware (entities) with data subscription capabilities is as follows:

[0223] S21, Application loading matrix mapping information of the hardware system.

[0224] In some embodiments of this application, the hardware system is the first entity, and the matrix mapping table is the global model matrix mapping information.

[0225] S22. Extract the subscription identifier and subscription model object library.

[0226] In some embodiments of this application, applications deployed on hardware or hardware systems (entities) can extract subscription identifiers and subscribed model object libraries based on matrix mapping information after loading the matrix mapping information. Applications on the hardware system can then obtain corresponding stored resource data from the subscribed model object libraries.

[0227] S23. Configure the multicast filtering address of the second data link according to the target address of the subscription, and listen to the second data sharing link.

[0228] S24. Upon receiving a second-link layer data packet, filter multicast address data packets that are not from the second data link.

[0229] S25. Parse the second link layer data packet of the target address.

[0230] S26. Extract the subscription data and transfer it to the local database corresponding to the first application object.

[0231] S27. Determine whether updated matrix mapping information has been received.

[0232] In some embodiments of this application, if updated matrix mapping information is received, S28 is executed; if updated matrix mapping information is not received, S24 is executed.

[0233] S28. Update the subscription model object library.

[0234] In some embodiments of this application, S21 is executed after S28.

[0235] It should be noted that the data sharing method of dynamic data publishing and subscription has the following characteristics:

[0236] 1) Supports static loading and subscription methods.

[0237] 2) Supports configuration of importance and priority to meet various scenarios such as high real-time, general real-time and non-real-time.

[0238] 3) Supports online dynamic modification of the model object library. Subscribing to modifications of the model object library does not require notifying the corresponding data nodes of other entities. Publishing modifications of the model object library requires multicast notification to other subscribed data nodes through a different message than the published model library.

[0239] 4) Supports filtering of non-subscribed target data for MAC multicast via Ethernet networking, while retaining subscribed target data.

[0240] 5) The publish-subscribe method is not limited to Ethernet star networks, but is also applicable to the interconnection model of ring network nodes.

[0241] Description of stored procedures for publishing and receiving data models:

[0242] 1) The data publisher must synchronize the local model library; this can be done through unicast, multicast, or broadcast protocols, and the protocol layer can be a Layer 2 protocol, a real-time protocol, or a TCP / IP application protocol, etc.

[0243] 2) One prerequisite for enabling updates is that the data receiver must modify and upgrade its local configuration library. The received information model must first be matched with the local configuration library; if they do not match, they are discarded; if they match, they are stored in the local model library. In other words, it is about updating and upgrading the information of existing models online.

[0244] Understandably, there are no system-bound constraints on third-party software and hardware, making it suitable for distributed storage and sharing scenarios for big data, not limited to cloud or edge applications. However, the information model defined in this application must be transmitted using the same application protocol type to avoid scenarios where protocol conversion would prevent the implementation of high-real-time, massive data applications. Cloud, edge, and end-to-cloud storage, implemented using the same application protocol, is best suited for scenarios with massive data models, but can also be used in information systems within industrial control networks, such as dynamic information sharing between multiple industrial control devices.

[0245] This application provides an entity, Figure 9 A schematic diagram of the structure of an entity provided in an embodiment of this application, such as... Figure 9 As shown, entity 9 includes: an acquisition unit 901, an extraction unit 902, and a sharing unit 903; wherein,

[0246] The acquisition unit 901 is used to acquire matrix mapping information from the total matrix mapping information of the global hardware based on the application functions deployed on the first entity; the matrix mapping information represents the correspondence between the resources of the first entity and the global application objects stored thereon.

[0247] Extraction unit 902 is used to extract the first application function and model object library of the first application object from the global resources in the matrix mapping information;

[0248] The sharing unit 903 is used to determine the data link based on the first application function and model object library of the first application object, and to share data with the second application object; the second application object has a sharing relationship with the first application object.

[0249] In some embodiments of this application, entity 9 includes: a sending unit 904 and a receiving unit 905;

[0250] The sending unit 904 is used to send out deployment requests based on the application functions of each application object deployed based on the first entity;

[0251] The receiving unit 905 is used to receive matrix mapping information that is segmented from the total matrix mapping information of the global hardware in accordance with deployment requirements.

[0252] In some embodiments of this application, entity 9 includes: configuration unit 906;

[0253] Configuration unit 906 is used to configure the link multicast protocol based on the first application function and model object library of the first application object, thereby determining the data link;

[0254] The sharing unit 903 is also used to share data with the second application object through a data link based on the second application function identifier group extracted from the global resources in the matrix mapping information; wherein the second application function identifier group corresponds to the second application object; the first entity and the second entity use the same data transmission protocol for data transmission.

[0255] In some embodiments of this application, the data link includes: a first data link;

[0256] Entity 9 includes: Determining unit 907;

[0257] The determining unit 907 is used to determine multiple first data queue information based on the attribute information of each model in the publishing model object library when the first application function characterizes the publishing function of the first application object; the multiple first data queue information respectively include publishing identifier and first link layer data packet; the model object library includes the publishing model object library;

[0258] Configuration unit 906 is also used to configure the link multicast protocol based on multiple first data queue information, thereby determining the first data link.

[0259] In some embodiments of this application, the attribute information includes: model importance and dynamic priority;

[0260] The determining unit 907 is also used to determine the sending order of the model object library for each model based on at least one of the model importance and dynamic priority of each model in the published model object library; and to determine multiple first data queue information based on the sending order.

[0261] In some embodiments of this application, the sending unit 904 is further configured to, if it is determined that the publishing model object library is to be sent, send a first link layer data packet of the publishing model object library to the second entity through the first data link based on the second application function identifier group.

[0262] In some embodiments of this application, the data link includes: a second data link;

[0263] Configuration unit 906 is also used to configure the multicast filtering address of the second data link based on the target address of the subscription model object library when the first application function characterizes the subscription function of the first application object, and to listen to the second data link; the model object library includes the target address of the subscription model object library.

[0264] In some embodiments of this application, the receiving unit 905 is configured to receive a second link layer data packet sent by a second entity through a second data link, based on a second application function identifier group.

[0265] In some embodiments of this application, the determining unit 907 is further configured to filter and extract the second link layer data packets to determine the subscription data; and store the subscription data in the local database corresponding to the first application object.

[0266] In some embodiments of this application, the acquisition unit 901 is used to acquire the target publishing model object library for subscribing to the second application object from the second link layer data packet;

[0267] The determining unit 907 is also used to filter and extract data packets from the second link layer based on the target publishing model object library and the subscription model object library corresponding to the first application object, and to determine the subscription data.

[0268] In some embodiments of this application, the target publishing model object library includes: a first publishing identifier, a model encoding identifier, and a storage resource identifier; the subscription model object library includes: a second publishing identifier, an entity identifier, and a group of subscription identifiers.

[0269] The determining unit 907 is also used to match the model code identifier with the entity identifier when the first publication identifier and the second publication identifier match successfully; match the storage resource identifier with the subscription identifier group when the model code identifier and the entity identifier match successfully; parse the model code identifier when the storage resource identifier and the subscription identifier group match successfully; and determine the subscription data when the model code identifier is a valid identifier in the local configuration model information.

[0270] In some embodiments of this application, the issuing unit 904 is further configured to issue an update deployment request based on the application functions of each application object deployed by the first entity if global resources for updating matrix mapping information online are used.

[0271] The receiving unit 905 is also used to receive updated matrix mapping information segmented from the total matrix mapping information of the global hardware in response to update deployment requirements;

[0272] The determination unit 907 is also used to confirm the updated model object library based on the updated matrix mapping information, so as to facilitate data sharing in the next instance.

[0273] In some embodiments of this application, the sending unit 904 is further configured to notify the subscribed second application object of the updated model object library when the application function characterization publishing function is applied.

[0274] In some embodiments of this application, the determining unit 907 is further configured to determine whether to send the publishing model object library if the global resource of matrix mapping information is not updated online when the application function characterization publishing function is used.

[0275] Based on the data storage and sharing methods of the above embodiments, this application also provides another entity, such as... Figure 10 As shown, Figure 10 This is a schematic diagram of the structure of another entity provided in an embodiment of this application. The entity 10 includes a processor 1001 and a memory 1002. The memory 1002 is used to store computer programs; the processor 1001 is used to call and run the computer programs from the memory to execute the data storage and sharing method as described in the above embodiments.

[0276] In the embodiments of this application, the processor 1001 described above can be at least one of the following: Application-Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), Central Processing Unit (CPU), Controller, Microcontroller, and Microprocessor. It is understood that for different devices, the electronic device used to implement the above processor function can also be other types, and the embodiments of this application do not specifically limit it.

[0277] This application provides a computer-readable storage medium storing a computer program for implementing, when executed by a processor, a data storage and sharing method as described in any of the above embodiments.

[0278] For example, the program instructions corresponding to a data storage and sharing method in this embodiment can be stored on storage media such as optical discs, hard disks, and USB flash drives. When the program instructions corresponding to a data storage and sharing method in the storage media are read or executed by an electronic device, the data storage and sharing method as described in any of the above embodiments can be implemented.

[0279] If the integrated unit is implemented as a software functional module and is not sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the method of this embodiment.

[0280] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, read-only memory (ROM), magnetic disks, or optical disks.

[0281] The modules described above as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules. They may be located in one place or distributed across multiple network units. Some or all of the modules may be selected to achieve the purpose of this embodiment according to actual needs.

[0282] Furthermore, the functional modules in the various embodiments of this application can all be integrated into one processing unit, or each module can be a separate unit, or two or more modules can be integrated into one unit; the integrated modules can be implemented in hardware or in a combination of hardware and software functional units. It should be understood that "an embodiment" or "one embodiment" mentioned in this application means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this disclosure. Therefore, "in one embodiment" or "in one embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Moreover, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0283] It should be understood that in the various embodiments of this application, the sequence numbers of the above steps / processes do not imply the order of execution. The execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this disclosure. The sequence numbers of the above embodiments of this disclosure are merely for descriptive purposes and do not represent the superiority or inferiority of the embodiments.

[0284] It should be noted that, in this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0285] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components may be combined, or integrated into another system, or some features may be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0286] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0287] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0288] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0289] The above description is merely an embodiment of this application, but the protection scope of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A method for storing and sharing data, characterized by, The method comprises: obtaining matrix mapping information from total matrix mapping information of global hardware based on application functions deployed by a first entity; the matrix mapping information represents a corresponding relationship between the first entity and resources of a global application object stored thereon; extracting a first application function of a first application object and a model object library from global resources in the matrix mapping information; determining a data link based on the first application function of the first application object and the model object library, and performing data sharing with a second application object; the second application object has a sharing relationship with the first application object.

2. The method of claim 1, wherein, The method comprises: issuing a deployment requirement based on application functions of each application object deployed by the first entity; receiving the matrix mapping information obtained from the total matrix mapping information of global hardware in response to the deployment requirement.

3. The method according to claim 1 or 2, characterized in that, The method comprises: configuring a link multicast protocol based on the first application function of the first application object and the model object library, thereby determining the data link; performing data sharing with the second application object through the data link based on a second application function identifier group extracted from the global resources in the matrix mapping information; the second application function identifier group corresponds to the second application object; the first entity and the second entity use the same data transmission protocol for data transmission.

4. The method of claim 3, wherein, The data link comprises a first data link. The method comprises: in a case where the first application function of the first application object represents a publishing function, determining a plurality of first data queue information based on attribute information of each model in a publishing model object library; the plurality of first data queue information respectively comprises a publishing identifier and a first link layer data packet; the model object library comprises the publishing model object library; configuring a link multicast protocol based on the plurality of first data queue information, thereby determining the first data link.

5. The method of claim 4, wherein, The attribute information comprises model importance and dynamic priority. The method comprises: determining a sending order of a model object library of each model based on at least one of model importance and dynamic priority of each model in the publishing model object library; determining the plurality of first data queue information based on the sending order.

6. The method according to claim 4 or 5, characterized in that, The method comprises: if it is determined to send the publishing model object library, sending the first link layer data packet of the publishing model object library to the second entity through the first data link based on the second application function identifier group.

7. The method of claim 3, wherein, The data link comprises a second data link. The first application function and the model object library based on the first application object are configured with a link groupcast protocol to determine a data link, including: In a case where the first application function of the first application object represents a subscription function, a multicast filter address of a second data link is configured based on a target address of a subscription model object library of the subscription, and the second data link is listened to; the model object library includes the target address of the subscription model object library.

8. The method of claim 7, wherein, The second application function identifier group extracted from the global resource in the matrix mapping information is used to share data with the second application object through the data link, including: Based on the second application function identifier group, a second link layer data packet sent by the second entity is received through the second data link.

9. The method of claim 8, wherein, The method further includes: Filtering and extracting processing of the second link layer data packet is performed to determine subscription data; The subscription data is stored in a local database corresponding to the first application object.

10. The method of claim 9, wherein, The filtering and extracting processing of the second link layer data packet to determine the subscription data includes: A target publishing model object library that subscribes to the second application object is obtained from the second link layer data packet; Based on the target publishing model object library and a subscription model object library corresponding to the first application object, filtering and extracting processing of the second link layer data packet is performed to determine the subscription data.

11. The method of claim 10, wherein, The target publishing model object library includes a first publishing identifier, a model code identifier, and a storage resource identifier; the subscription model object library includes a second publishing identifier, an entity identifier, and a subscription identifier group; The filtering and extracting processing of the second link layer data packet to determine the subscription data based on the target publishing model object library and the subscription model object library corresponding to the first application object includes: In a case where the first publishing identifier and the second publishing identifier match successfully, the model code identifier is matched with the entity identifier; In a case where the model code identifier and the entity identifier match successfully, the storage resource identifier is matched with the subscription identifier group; In a case where the storage resource identifier and the subscription identifier group match successfully, the model code identifier is parsed, and in a case where the model code identifier is a valid identifier in the locally configured model information, the subscription data is determined.

12. The method according to any one of claims 1 to 11, characterized in that, The method further includes: If the global resource of the matrix mapping information is updated online, an update deployment requirement is issued based on the application function of each application object deployed by the first entity; An updated matrix mapping information segmented from the total matrix mapping information of the global hardware is received in response to the update deployment requirement; Based on the updated matrix mapping information, an updated model object library is confirmed for data sharing next time.

13. The method of claim 12, wherein In a case where the application function represents a publishing function, the updated model object library is notified to the second application object that subscribes.

14. The method according to any one of claims 1 to 11, characterized in that, The method further includes: In the case of applying the function of characterizing publishing, if the global resource of the matrix mapping information is not updated on-line, it is determined whether to send a publishing model object library.

15. The method according to any one of claims 1 to 14, characterized in that, The matrix mapping information comprises entity identification, storage resource identification, first application function identification, second application function identification group and model object library; when the first application function identification is publishing identification, the second application function identification group is a subscription identification group, and the model object library is a publishing model object library; when the first application function identification is subscription identification, the second application function identification group is a publishing identification group, and the model object library is a subscription model object library.

16. The method according to any one of claims 1 to 14, characterized in that, The model object library comprises model code identification, model importance, dynamic priority, associated storage resource and associated function resource; the associated function resource comprises associated publishing resource or associated subscription resource.

17. The method according to any one of claims 3-11, characterized by, The data transmission protocol comprises unicast protocol, multicast protocol or broadcast protocol.

18. An entity, characterized in that, Comprise: An acquisition unit, an extraction unit and a sharing unit, wherein, The acquisition unit is configured to acquire matrix mapping information from total matrix mapping information of a global hardware based on an application function deployed by a first entity; the matrix mapping information represents a corresponding relationship between the first entity and a resource of a global application object stored thereon; The extraction unit is configured to extract a first application function of a first application object and a model object library from a global resource in the matrix mapping information; The sharing unit is configured to determine a data link based on the first application function of the first application object and the model object library, and perform data sharing with a second application object; the second application object has a sharing relationship with the first application object.

19. An entity, characterized in that, Comprise: A processor and a memory, wherein, The memory is configured to store a computer program; The processor is configured to call and run the computer program from the memory to execute the data storage and sharing method according to any one of claims 1 to 17.

20. A computer-readable storage medium, characterized in that, Executable instructions are stored for causing the processor to execute the data storage and sharing method according to any one of claims 1 to 17.

Images