Platform cascade information synchronization method and platform cross-domain interaction method

Abstract

The invention provides a platform cascade information synchronization method and a platform cross-domain interaction method, and relates to the technical field of the Internet of Things, and the method comprises the following steps: a superior platform sends a request for querying equipment association information of the superior platform to a storage layer of the superior platform; the storage layer of the superior platform inquires and obtains an equipment main body data model of the current-level platform according to the equipment id of the current-level platform contained in the request, and returns an equipment main body data model response of the current-level platform to the superior platform; the equipment main body data model is defined and described by a triple of'equipment id, equipment code and channel code '. According to the method, after the superior platform uses the new equipment data model, the data model contains the equipment key information, the incidence relation of the storage layer can be directly changed, the platform at the level does not need to be accessed through cascading, and the storage layer directly returns the result to the superior platform, so that data conversion does not need to be performed during cross-domain information synchronization, and the efficiency is improved. And the synchronization performance is greatly improved.

Description

Technical Field

[0001] The present invention relates to the technical field of Internet of Things, and in particular to a platform cascade information synchronization method and a platform cross-domain interaction method. Background Art

[0002] GB / T28181 "Technical Requirements for Information Transmission, Exchange, and Control of Security Video Surveillance Network Systems" is designed to support multi-level cascading. Protocol exchange and video transmission are achieved between platforms through national standard protocols. IoT needs to manage all devices including cloud video. Each platform saves the information of the lower-level platform and generates a mapping method on this platform, such as the ID of its own platform. When operating across domains, one more query and conversion is required. Therefore, when synchronizing information across domains, data conversion is required, resulting in low synchronization performance; and when indexing, it relies heavily on the southbound access layer, and each request and return requires the intervention of the storage service, resulting in slow response and low throughput. Summary of the invention

[0003] The purpose of the present invention is to provide a platform cascade information synchronization method and a platform cross-domain interaction method, aiming to solve the existing technical problems that data conversion is required when synchronizing information across domains, resulting in low synchronization performance; and the indexing is heavily dependent on the southbound access layer, and each request and return requires the intervention of the storage service, resulting in slow response speed and low throughput. The specific technical solution is as follows:

[0004] A platform cascade information synchronization method, the method comprising the following steps:

[0005] S100, the upper-level platform sends a request to the storage layer of the upper-level platform to query the device association information of the current-level platform;

[0006] S200. The storage layer of the upper-level platform obtains the device main body data model of the current-level platform according to the device id of the current-level platform contained in the request, and returns the device main body data model response of the current-level platform to the upper-level platform; the device main body data model stored in the storage layer of the upper-level platform is defined and described by the triplet of [device id, device code, channel code].

[0007] Furthermore, a device id represents a unique identifier used to identify an entity or data record.

[0008] Furthermore, the device ID has less than 16 characters.

[0009] Furthermore, the device code represents a unique code of a specific device and is used to distinguish different devices.

[0010] Furthermore, the number of characters of the device code is less than 16 characters.

[0011] Furthermore, the channel code represents a channel identifier of a device, and is used to distinguish different channels of the device.

[0012] Furthermore, the number of characters of the channel code is less than 16 characters.

[0013] Furthermore, in the device main body data model, there are separators between the device ID and the device code, and between the device code and the channel code, respectively. The separator is a special character used to separate different data fields.

[0014] Furthermore, the number of characters of the separator is 1 character.

[0015] The present invention also provides a platform cross-domain interaction method, the method comprising the following steps:

[0016] S1000, the main platform uses the device main data model to request the southbound access layer. The device main data model is defined and described by the triple of [device id, device code, channel code];

[0017] S2000, the southbound access layer parses the device coding information according to the device main data model, and directly requests the device according to the device coding information;

[0018] S3000, the device function returns a response to the southbound access layer;

[0019] S4000, southbound access layer returns platform functions to the main platform.

[0020] The present invention provides a platform cascade information synchronization method and a platform cross-domain interaction method, which has the following features:

[0021] Beneficial effects:

[0022] (1) The present invention sends a request for querying the device association information of the current platform to the storage layer of the upper-level platform through the upper-level platform; the storage layer of the upper-level platform obtains the device main data model of the current platform according to the device ID of the current platform contained in the request, and returns the device main data model response of the current platform to the upper-level platform; the device main data model stored in the storage layer of the upper-level platform is defined and described by the triple of [device id, device code, channel code]; therefore, after the upper-level platform uses the new device data model, the data model already contains the key information of the device, and the storage layer association relationship can be directly changed without cascading access to the current platform. The storage layer directly returns the result to the upper-level platform, so that no data conversion is required when synchronizing information across domains, which greatly improves the synchronization performance.

[0023] (2) By reducing the primary data query and mapping process, the present invention optimizes device operations. In scenarios with large data volume requests, by directly using characters containing device attribute information, bandwidth consumption is significantly reduced, and data interaction efficiency between platforms is improved, thereby greatly enhancing the system's response speed and throughput. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 is a schematic diagram of the process of updating device association information in an existing cascading synchronization scenario;

[0025] Figure 2 is a schematic flowchart of the platform cascading information synchronization method according to an embodiment of the present invention;

[0026] Figure 3 is a schematic diagram of the process of the platform cascading information synchronization method according to an embodiment of the present invention;

[0027] Figure 4 is a schematic diagram of the device main body data model according to an embodiment of the present invention;

[0028] Figure 5 is a schematic diagram of the process of an existing platform cross-domain interaction method;

[0029] Figure 6 is a schematic flowchart of the platform cross-domain interaction method according to an embodiment of the present invention;

[0030] Figure 7 is a schematic diagram of the process of the platform cross-domain interaction method according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0031] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings provided by the present invention. According to the following description, the advantages and features of the present invention will be clearer. It should be noted that the drawings are all in a very simplified form and use non-precise scales, only for the purpose of facilitating and clearly assisting in explaining the objectives of the embodiments of the present invention.

[0032] In the description of the present invention, unless otherwise clearly defined and limited, the terms "connected" and "linked" shall be interpreted in a broad sense. For example, it can be a fixed connection, a detachable connection, or integrated; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, and it can be the internal communication of two components or the interaction relationship between two components. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0033] In the description of the present invention, the orientation or positional relationships such as "upper", "lower", "left", "right", "front", "rear", "center", "horizontal", "vertical", "top", "bottom", "inner", "outer", etc. are based on the orientation or positional relationships shown in the drawings. These are only for the convenience of description and simplifying operations, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation. Therefore, it should not be construed as a limitation to the present invention.

[0034] Refer to Figure 1 As shown, the steps for updating the device association information in the existing cascaded synchronization scenario are as follows:

[0035] 1. The upper-level platform requests device data information and queries the device information using the device ID of the upper-level platform. Since the device information is stored at this level, it is necessary to access this level through the cascaded channel to query the device association information.

[0036] 2. After the local platform receives the request, it accesses the storage layer using the device ID to query the device information.

[0037] 3. The storage layer returns the real device information, which includes the device ID at this level and other information.

[0038] 4. The local platform returns the device information upward.

[0039] 5. After the upper-level platform receives the information from the local platform, it updates the device information associated with the device ID to the storage layer.

[0040] 6. The storage layer returns a response for the change in the device association relationship.

[0041] In the platform cascading scenario, information synchronization is a basic capability. In the original scenario, for batch synchronization of associated data, it is necessary to retrieve according to the entity ID and then update the entity association information one by one. Each change in the entity information will perform a large number of retrieval and change operations, greatly reducing the overall performance of data synchronization.

[0042] An embodiment of the present invention provides a platform cascading information synchronization method. Refer to Figure 2 、 3 As shown, it includes the following steps:

[0043] S100. The upper-level platform sends a request to the storage layer of the upper-level platform to query the device association information of the local platform.

[0044] S200. The storage layer of the upper-level platform queries the device main data model of the local platform according to the device ID of the local platform included in the request, and returns the device main data model of the local platform as a response to the upper-level platform; the device main data model stored in the storage layer of the upper-level platform is defined and described by a triple of [device ID, device code, channel code].

[0045] Based on the idea of national standard coding, the design scheme of the device main body data model first needs to ensure the global uniqueness of data. Although UUID (Universally Unique Identifier) can effectively solve the global uniqueness problem, it lacks business attribute information itself. Therefore, it is necessary to design a method that can ensure cross-system unique description while also describing business attributes. For this purpose, the present invention introduces an innovative method, using a triple to describe the device main body [id, device code, channel code]: using the device id to describe the life cycle of the device within the system, and the id will be different if the same device is deleted and re-added; for cross-system interaction, referring to the design of GB / T28181 and combining with domain design, the southbound access uses the device code to abstractly describe the accessor, and the channel code is used to describe the access main body (such as a device) of the accessor. In this way, a one-to-many description of the accessor is completed within the system, and at the same time, it supports the one-to-many access description of the accessor accessing the system main body, with strong scalability.

[0046] In the embodiment of the present invention, the superior platform sends a request to the storage layer of the superior platform to query the device association information of the local platform; the storage layer of the superior platform queries the device main body data model of the local platform according to the device id of the local platform included in the request, and returns the device main body data model of the local platform to the superior platform as a response; the device main body data model stored in the storage layer of the superior platform is defined and described by the triple [device id, device code, channel code]; therefore, after the superior platform uses the new device data model, the key information of the device is already included in the data model, and the association relationship of the storage layer can be directly changed without cascading access to the local platform, and the storage layer directly returns the result to the superior platform, so that data conversion is not required when synchronizing information across domains, greatly improving the synchronization performance.

[0047] Specifically, refer to Figure 4 As shown, the device id represents a unique identifier used to identify an entity or data record.

[0048] In a preferred embodiment, the number of characters of the device id is less than 16 characters.

[0049] The device code represents the unique code of a specific device, used to distinguish different devices.

[0050] In a preferred embodiment, the number of characters of the device code is less than 16 characters.

[0051] The channel code represents the channel identifier of the device, used to distinguish different channels of the device.

[0052] In a preferred embodiment, the number of characters of the channel code is less than 16 characters.

[0053] In one embodiment, in the device main body data model, there are delimiters between the device ID and the device code, and between the device code and the channel code. The delimiter is a special character used to separate different data fields; it may be a comma (,), a semicolon (;), a slash ( / ), etc.

[0054] In a preferred embodiment, the number of characters of the delimiter is 1 character.

[0055] Refer to Figure 5 As shown, the working process of the existing platform cross-domain interaction method is as follows:

[0056] 1. The main platform requests platform functions from the southbound access layer and retrieves using the original device ID model;

[0057] 2. The southbound access layer needs to query the storage layer mapping relationship according to the device ID;

[0058] 3. The storage layer returns the real device mapping relationship;

[0059] 4. The southbound access layer requests device functions using the real device information;

[0060] 5. The device returns a function response to the southbound access layer;

[0061] 6. The southbound access layer returns a platform function response to the main platform.

[0062] In the existing platform cross-domain interaction method, it is necessary to use the platform device ID to retrieve device information for operating the device. The request link is: main platform > southbound access layer > storage layer > device layer. The original southbound access layer has a heavy dependence, and each request and return requires the intervention of the storage service, which greatly reduces the performance of the system.

[0063] The embodiment of the present invention provides a platform cross-domain interaction method. Refer to Figure 6 、 7 As shown, it includes the following steps:

[0064] S1000. The main platform requests the southbound access layer using the device main body data model, and the device main body data model is defined and described by the triple [device ID, device code, channel code];

[0065] S2000. The southbound access layer parses out the device code information according to the device main body data model and directly requests the device according to the device code information;

[0066] S3000. The device function returns a response to the southbound access layer;

[0067] S4000. The southbound access layer returns the platform function to the main platform.

[0068] The above-mentioned cross-domain interaction method of the platform in the embodiment of the present invention optimizes the device operation by reducing one data query and mapping process. In the scenario of a large amount of data requests, by directly using characters containing device attribute information, the bandwidth consumption is significantly reduced, and the data interaction efficiency between platforms is improved, thereby greatly enhancing the response speed and throughput of the system.

[0069] Those skilled in the art of this technology should understand that the present invention can be implemented in many other specific forms without departing from the spirit and scope of the present invention. Based on the embodiments of the present invention, any changes and modifications made by those of ordinary skill in the art of the present invention according to the above disclosure are within the protection scope of the claims.

Claims

1. A platform cascade information synchronization method, characterized in that: The method comprises the following steps: S100, the upper-level platform sends a request to the storage layer of the upper-level platform to query the device association information of the current-level platform; S200. The storage layer of the upper-level platform obtains the device main body data model of the current-level platform according to the device id of the current-level platform contained in the request, and returns the device main body data model response of the current-level platform to the upper-level platform; the device main body data model stored in the storage layer of the upper-level platform is defined and described by the triplet of [device id, device code, channel code].

2. The platform cascade information synchronization method according to claim 1, characterized in that: Device ID represents a unique identifier that is used to identify an entity or data record.

3. The platform cascade information synchronization method according to claim 2, characterized in that: The device ID must contain less than 16 characters.

4. The platform cascade information synchronization method according to claim 1, characterized in that: The device code is a unique code for a specific device and is used to distinguish different devices.

5. The platform cascade information synchronization method according to claim 4, characterized in that: The device code contains fewer than 16 characters.

6. The platform cascade information synchronization method according to claim 1, characterized in that: The channel code indicates the channel identification of the device and is used to distinguish different channels of the device.

7. The platform cascade information synchronization method according to claim 6, characterized in that: The channel code contains fewer than 16 characters.

8. The platform cascade information synchronization method according to claim 1, characterized in that: In the device main body data model, there are separators between the device ID and the device code, and between the device code and the channel code, respectively. The separator is a special character used to separate different data fields.

9. The platform cascade information synchronization method according to claim 8, characterized in that: The number of characters for the separator is 1.

10. A platform cross-domain interaction method, characterized in that: The method comprises the following steps: S1000, the main platform uses the device main data model to request the southbound access layer. The device main data model is defined and described by the triple of [device id, device code, channel code]; S2000, the southbound access layer parses the device coding information according to the device main data model, and directly requests the device according to the device coding information; S3000, the device function returns a response to the southbound access layer; S4000, southbound access layer returns platform functions to the main platform.

Images