Data push control method, device, terminal and medium based on 1400 protocol

Abstract

The present application discloses a data push control method, apparatus, terminal and medium based on the 1400 protocol. The solution provided by the present application first receives a data push message pushed by a lower-level platform based on the GAT1400 protocol, wherein the data push message includes image data to be pushed, a device identifier for identifying the device identity and account information, and then matches the device relationship database and the device capability set database according to the device identifier and the account information to determine whether the device and account are trusted devices / accounts with a binding relationship and have 1400 capabilities. If so, the data push message is pushed to the upper-level platform to avoid pushing devices that do not have the capabilities to the upper-level platform.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data push control method based on the 1400 protocol. Background Art

[0002] With the development of the video surveillance industry and the strengthening of national regulatory requirements, institutions such as the Public Security Bureau, the Food and Drug Administration, and the Comprehensive Management Office will require that camera data from public areas or specific industries be pushed to their management platforms, i.e., the superior platforms.

[0003] At present, there are mainly two types of cameras that can meet the GAT1400 protocol. One is that the camera device itself has the protocol capability, and the other is that the camera itself does not have the protocol capability and needs to be converted through the protocol of the middleware or the lower-level platform before it can be put into use. In the first case, the device can be connected to the intensive platform through the normal installation and maintenance process, and the device automatically reports the capability set to confirm the device relationship and capability; but in the second case, the management personnel need to handle the synchronization of the device relationship and capability set before putting it into use, which is prone to the problem of pushing devices that do not have the capability to the upper-level platform. Summary of the Invention

[0004] The present application provides a data push control method, device, terminal and medium based on the 1400 protocol, which is used to achieve the invention purpose of avoiding pushing devices that do not have 1400 capabilities to the upper platform in the scenario where the national standard equipment that does not currently have 1400 capabilities is increased by the lower platform.

[0005] To solve the above technical problems, the first aspect of the present application provides a data push control method based on the 1400 protocol, including:

[0006] Receiving a data push message, wherein the data push message includes: image data captured by a camera device, a device identifier of the camera device, and account information of a lower-level platform to which the camera device is connected;

[0007] Matching the device identification and the account information with a preset device relationship database to obtain a device relationship matching result;

[0008] Matching the device identification and the account information with a preset device capability set database to obtain a capability set matching result;

[0009] When both the device relationship matching result and the capability set matching result are successful, the data push message is pushed to the upper-level platform.

[0010] Preferably, the configuration method of the device relationship database includes:

[0011] Obtaining, through a preset GB28181 protocol, a camera device and a device directory relationship of each of the camera devices, so as to assign a device identifier to the camera device according to the device directory relationship;

[0012] Bind the camera device to the account information of the connected lower-level platform and add it to the device tree;

[0013] The protocol capability identifier of the lower-level platform is obtained. If the protocol capability identifier meets the preset identification judgment condition, the camera device is synchronized to the device relationship database, wherein the protocol capability identifier is used to indicate whether the lower-level platform has the ability to run the 1400 protocol.

[0014] Preferably, the device capability set database configuration method includes:

[0015] After the lower-level platform completes registration, a subscription instruction is sent to the lower-level platform, so that the lower-level platform responds to the subscription instruction and synchronizes the camera devices with 1400 capabilities of this platform to the preset device capability set database according to the logic of the GAT1400 protocol.

[0016] Preferably, it also includes:

[0017] When it is detected that the first database is updated, the updated device identification and account information are matched with the second database. If the device identification and account information exist in the second database, the device identification and account information are used to update the device information.

[0018] Preferably, the first database is one of the device relationship database and the device capability set database, and the second database is another database corresponding to the first database.

[0019] A second aspect of the present application provides a data push control device based on the 1400 protocol, comprising:

[0020] A message receiving unit, configured to receive a data push message, wherein the data push message includes: image data captured by a camera device, a device identifier of the camera device, and account information of a lower-level platform to which the camera device is connected;

[0021] a device relationship matching unit, configured to match the device identification and the account information with a preset device relationship database to obtain a device relationship matching result;

[0022] a device capability matching unit, configured to match the device identifier and the account information with a preset device capability set database to obtain a capability set matching result;

[0023] The message push execution unit is configured to push the data push message to the upper-level platform when both the device relationship matching result and the capability set matching result are successful.

[0024] Preferably, the device further comprises: a device relationship database construction unit, configured to:

[0025] Obtaining, through a preset GB28181 protocol, a camera device and a device directory relationship of each of the camera devices, so as to assign a device identifier to the camera device according to the device directory relationship;

[0026] Bind the camera device to the account information of the connected lower-level platform and add it to the device tree;

[0027] The protocol capability identifier of the lower-level platform is obtained. If the protocol capability identifier meets the preset identification judgment condition, the camera device is synchronized to the device relationship database, wherein the protocol capability identifier is used to indicate whether the lower-level platform has the ability to run the 1400 protocol.

[0028] Preferably, the device further comprises: a device capability set database construction unit, configured to:

[0029] After the lower-level platform completes registration, a subscription instruction is sent to the lower-level platform, so that the lower-level platform responds to the subscription instruction and synchronizes the camera devices with 1400 capabilities of this platform to the preset device capability set database according to the logic of the GAT1400 protocol.

[0030] A third aspect of the present application provides a data push control terminal based on the 1400 protocol, comprising: a memory and a processor;

[0031] The memory is used to store program code, and the program code corresponds to a data push control method based on the 1400 protocol provided in the first aspect of the present application;

[0032] The processor is configured to read and execute the program code.

[0033] The fourth aspect of the present application provides a computer-readable storage medium, in which program code is stored. The program code is used to be read and executed by a processor to implement a data push control method based on the 1400 protocol as provided in the first aspect of the present application.

[0034] It can be seen from the above technical solutions that this application has the following advantages:

[0035] The solution provided in this application first receives the data push message pushed by the lower-level platform based on the GAT1400 protocol, wherein the data push message contains the image data to be pushed, the device identifier for identifying the device identity, and the account information. Then, according to the device identifier and the account information, it is matched with the device relationship database and the device capability set database to determine whether the device and account are trusted devices / accounts with a binding relationship and have 1400 capabilities. If so, the data push message is pushed to the upper-level platform to avoid pushing devices that do not have the capabilities to the upper-level platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0037] Figure 1 A logical diagram of the monitoring system architecture based on the 1400 protocol provided for this application.

[0038] Figure 2 This is a flow chart of an embodiment of a data push control method based on the 1400 protocol provided in this application.

[0039] Figure 3 This is a logical diagram of the push permission judgment of a data push control method based on the 1400 protocol provided in this application.

[0040] Figure 4 This is a flowchart of database construction in an embodiment of a data push control method based on the 1400 protocol provided in this application.

[0041] Figure 5 This is a structural diagram of an embodiment of a data push control device based on the 1400 protocol provided in this application.

[0042] Figure 6 This is a structural diagram of an embodiment of a data push control terminal based on the 1400 protocol provided by this application. DETAILED DESCRIPTION

[0043] Currently, there are three main types of cameras that support the GAT1400 protocol: dedicated cameras with native protocol capabilities and standard cameras that require protocol conversion. Standard cameras can be further categorized as follows: 1) those mounted on AI boxes or NVRs, where intermediate hardware such as AI boxes or NVRs convert the data to the 1400 protocol; and 2) those connected to lower-level platforms, where the lower-level platforms convert the data to the 1400 protocol for interaction with the centralized platform. In both cases, the synchronization of device relationships and capability sets is crucial to ensure accurate data push to the higher-level platform. Inaccurate device relationships and capability sets can affect the timeliness of snapshot information pushed from the centralized platform to the higher-level platform. Therefore, before using these cameras, the platform must first configure the device relationship information and protocol capability set information for each device. This increases the risk of human error in data push tasks, leading to the push of data from devices that lack the required capabilities to the higher-level platform.

[0044] The present application provides a data push control method, device, terminal and medium based on the 1400 protocol, which is used to achieve the invention purpose of avoiding pushing devices that do not have 1400 capabilities to the upper platform in the scenario where the national standard equipment that does not currently have 1400 capabilities is increased by the lower platform.

[0045] In order to make the purpose, features, and advantages of the invention of this application more obvious and easy to understand, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described below are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0046] First, a detailed description of an embodiment of a monitoring system based on the 1400 protocol provided by this application is provided, as follows:

[0047] like Figure 1 As shown, this embodiment provides a monitoring system based on the 1400 protocol, which is used to implement a data push control method based on the 1400 protocol provided in this application.

[0048] The system can be divided into three main modules: national standard cascade module, intensive business platform and 1400 platform. These three modules can be divided into three interconnected and integrated into a large terminal. Among them, the national standard cascade module is used to connect with the lower platform in accordance with the GB 28181 protocol, perform platform authentication and synchronize data such as equipment and directory, and push equipment and directory information to the intensive business platform for account binding and device tree; the intensive business platform is a module for managing all business information of the equipment, which can configure different business capabilities based on the equipment, equipment capability set, equipment account relationship, etc.; the 1400 platform is a module that connects with the upper and lower platforms in accordance with the GAT1400 protocol, receives snapshots pushed by the lower platform, and pushes the snapshots to one or more upper platforms according to the configuration.

[0049] like Figure 1 As shown, first, according to Figure 1 For values ​​0.1 to 0.3, the installation and maintenance personnel obtain the platform access information for GB28181 and GAT 1400 respectively through the national standard cascading module, enter the corresponding account of the lower-level platform, and configure the protocol capability identifier to declare whether the lower-level platform has (or partially has) 1400 capabilities. This completes the basic configuration of the lower-level platform.

[0050] Then, follow Figure 1 In steps 1.1 to 1.4, the national standard cascading module synchronizes devices and directories from the lower-level platform using search and subscription instructions in accordance with the GB 28181 protocol and the platform cascading process. The national standard cascading module assigns new national standard codes (device identifiers) to the synchronized devices and directories based on the centralized platform's rules. The devices are then synchronized to the centralized service platform, bound to corresponding accounts, and added to the device tree. If the lower-level platform is marked as "1400-capable," the device information is synchronized to the 1400 platform and device relationship data is entered. If a device is added, the 1400 platform compares the newly added device relationship database with the 1400-capable device capability set database synchronized from the lower-level platform. If the device already exists, the centralized platform is notified to update the device capability set.

[0051] according to Figure 1In steps 2.1-2.5, lower-level platforms can register with the 1400 platform based on their configuration information. Once the 1400 platform detects that a lower-level platform has completed registration, it issues a full device and image subscription instruction to the lower-level platform, enabling the lower-level platform to respond to the instruction and, following the GAT 1400 protocol standard process, synchronize 1400-capable devices to the 1400 platform through a search and subscription process to enter the device capability set database. This creates a device capability set database. If a device is added, the 1400 platform compares the newly added device capability set database with the device relationship database synchronized from the centralized service platform. If the device already exists, the centralized service platform is notified to add the device capability set. If a device is deleted, the centralized service platform is notified to delete the device capability set.

[0052] It is understandable that Figure 1 The order of 1.1 to 1.4 and 2.1 to 2.5 can be swapped without affecting the final result. After completing the above three steps, you can determine whether this device has a binding relationship (trusted) on the centralized platform and has 1400 capabilities.

[0053] Then, follow Figure 1 In 3.1-3.2, during the actual application phase, the camera device pushes the video stream to the lower-level platform, which analyzes the video stream frame by frame. If it finds an image that meets the capture conditions (face, motor vehicle, license plate, etc.), it saves it as an image, converts it to the 1400 protocol, and pushes it to the 1400 platform. The 1400 platform queries the device relationship (device relationship database) and capability set (device capability set database). If both exist, it pushes data messages to the specified upper-level platform based on the account.

[0054] The above is a detailed description of a system embodiment for implementing the data push control method based on the 1400 protocol provided by this application. The following is a detailed description of an embodiment of the data push control method based on the 1400 protocol provided by this application.

[0055] See also Figure 2 , this application provides an embodiment of a data push control method based on the 1400 protocol, including:

[0056] Step 101: Receive data push message;

[0057] The data push message includes: image data captured by the camera device, the device identification of the camera device, and the account information of the lower-level platform to which the camera device is connected.

[0058] Step 102: Match the device identification and account information with a preset device relationship database to obtain a device relationship matching result.

[0059] Step 103: Match the device identification and account information with the preset device capability set database to obtain a capability set matching result.

[0060] Step 104: When both the device relationship matching result and the capability set matching result are successful, a data push message is pushed to the upper-level platform.

[0061] It should be noted that steps 101 to 104 of this embodiment correspond to Figure 1 in Figure 1 3.1~3.2, first, the 1400 platform monitors the message push from the lower-level platform. After receiving the data message pushed by the lower-level platform, the device identifier and account information used to identify the device and user in the message are matched with the device relationship database and the device capability set database respectively to determine whether the device and the account are trusted devices / trusted accounts and have 1400 capabilities. If so, the data message is pushed to the upper-level platform. Otherwise, no push is made. The push permission judgment logic of this embodiment can be found in Figure 3 .

[0062] Furthermore, if Figure 4 As shown, the configuration method of the device relationship database mentioned in this embodiment includes:

[0063] Step 1001: Obtain the camera device and the device directory relationship of each camera device through the preset GB28181 protocol, and assign a device identifier to the camera device according to the device directory relationship;

[0064] Step 1002: Bind the camera device to the account information of the connected lower-level platform and add it to the device tree;

[0065] Step 1003: Acquire the protocol capability identifier of the lower-level platform. If the protocol capability identifier meets the preset identifier determination condition, synchronize the camera device to the device relationship database.

[0066] The protocol capability identifier is used to indicate whether the lower-level platform has the ability to run the 1400 protocol.

[0067] It should be noted that steps 1001 to 1003 of this embodiment correspond to Figure 1 In steps 1.1 to 1.3, the national standard cascading module synchronizes devices and directories from the lower-level platform through retrieval and subscription instructions according to the GB 28181 protocol and the platform cascading process. The national standard cascading module assigns new national standard codes (device identifiers) to the synchronized devices and directories based on the centralized platform rules. The devices are then synchronized to the centralized service platform, bound to the corresponding account, and added to the device tree. If the lower-level platform is marked as "1400-capable," the device information is synchronized to the 1400 platform and the device relationship data is entered. At this point, a device relationship database is obtained.

[0068] Furthermore, the device capability set database configuration method mentioned in this embodiment includes:

[0069] Step 1004: After the lower-level platform completes registration, it sends a subscription instruction to the lower-level platform, so that the lower-level platform responds to the subscription instruction and synchronizes the camera devices with 1400 capabilities of this platform to the preset device capability set database according to the logic of the GAT1400 protocol.

[0070] It should be noted that step 1004 of this embodiment corresponds to Figure 1 In 2.1 to 2.4, when the 1400 platform detects that a lower-level platform has completed registration, the 1400 platform sends a full device and image subscription instruction to the lower-level platform. The lower-level platform responds to the instruction and synchronizes 1400-capable devices to the 1400 platform through the retrieval and subscription process according to the standard GAT 1400 protocol process to enter the device capability set database. At this point, the device capability set database can be obtained.

[0071] Furthermore, it also includes:

[0072] When it is detected that the first database is updated, the updated device identification and account information are matched with the second database. If the device identification and account information exist in the second database, the device identification and account information are used to update the device information.

[0073] More specifically, the first database is one of a device relationship database and a device capability set database, and the second database is another database opposite to the first database.

[0074] Regardless of when device relationships or capability sets are synchronized, devices with permissions and capability sets can be matched, allowing for more flexible modification of device relationships and device capability sets.

[0075] The above is a detailed description of an embodiment of a data push control method based on the 1400 protocol provided by this application. The following is a detailed description of an embodiment of a data push control device based on the 1400 protocol provided by this application.

[0076] See also Figure 5 , the present application provides an embodiment of a data push control device based on the 1400 protocol, comprising:

[0077] The message receiving unit 201 is configured to receive a data push message, wherein the data push message includes: image data captured by a camera device, a device identifier of the camera device, and account information of a lower-level platform to which the camera device is connected;

[0078] The device relationship matching unit 202 is used to match the device identification and account information with a preset device relationship database to obtain a device relationship matching result;

[0079] The device capability matching unit 203 is used to match the device identification and account information with the preset device capability set database to obtain a capability set matching result;

[0080] The message push execution unit 204 is configured to push a data push message to the upper-level platform when both the device relationship matching result and the capability set matching result are successful.

[0081] Furthermore, the system further comprises: a device relationship database construction unit 2001, configured to:

[0082] Obtain the camera device and the device directory relationship of each camera device through the preset GB28181 protocol, so as to assign a device identifier to the camera device according to the device directory relationship;

[0083] Bind the camera device to the account information of the connected lower-level platform and add it to the device tree;

[0084] The protocol capability identifier of the lower-level platform is obtained. If the protocol capability identifier meets the preset identification judgment condition, the camera device is synchronized to the device relationship database, wherein the protocol capability identifier is used to indicate whether the lower-level platform has the ability to run the 1400 protocol.

[0085] Furthermore, the system further includes: a device capability set database construction unit 2002, configured to:

[0086] After the lower-level platform completes registration, it sends a subscription instruction to the lower-level platform, so that the lower-level platform responds to the subscription instruction and synchronizes the camera devices with 1400 capabilities of this platform to the preset device capability set database according to the logic of the GAT1400 protocol.

[0087] In addition, this embodiment also provides a detailed description of an embodiment of a data push control terminal based on the 1400 protocol and an embodiment of a computer-readable storage medium.

[0088] See also Figure 6 , the present application provides an embodiment of a data push control terminal based on the 1400 protocol, the types of terminals include but are not limited to: personal computers, industrial computers, servers and embedded intelligent devices, the terminal mainly comprises: a memory 33 and a processor 31, the memory 33 and the processor 31 can be connected via a communication bus 34;

[0089] The memory 33 is used to store program codes corresponding to a data push control method based on the 1400 protocol as described in the above embodiment;

[0090] The processor 31 is used to read and execute program codes.

[0091] The present application provides an embodiment of a computer-readable storage medium, in which program code is stored. The program code is used to be read and executed by a processor to implement a data push control method based on the 1400 protocol as provided in the above embodiment.

[0092] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the terminals, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0093] In the several embodiments provided in this application, it should be understood that the disclosed terminals, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0094] The terms "first," "second," "third," "fourth," and the like (if any) in the specification of the present application and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of the present application described herein, for example, can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product, or apparatus.

[0095] It should be understood that in this application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0096] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0097] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0098] If the integrated unit is implemented as a software functional unit and 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 the present invention, or the portion that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes various media that can store program code, such as a USB flash drive, a mobile hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0099] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A data push control method based on 1400 protocol, characterized in that: include: Receiving a data push message, wherein the data push message includes: image data captured by a camera device, a device identifier of the camera device, and account information of a lower-level platform to which the camera device is connected; Matching the device identification and the account information with a preset device relationship database to obtain a device relationship matching result; Matching the device identification and the account information with a preset device capability set database to obtain a capability set matching result; When both the device relationship matching result and the capability set matching result are successful, the data push message is pushed to the upper-level platform.

2. The data push control method based on the 1400 protocol according to claim 1, characterized in that: The configuration method of the device relationship database includes: Obtaining, through a preset GB28181 protocol, a camera device and a device directory relationship of each of the camera devices, so as to assign a device identifier to the camera device according to the device directory relationship; Bind the camera device to the account information of the connected lower-level platform and add it to the device tree; The protocol capability identifier of the lower-level platform is obtained. If the protocol capability identifier meets the preset identification judgment condition, the camera device is synchronized to the device relationship database, wherein the protocol capability identifier is used to indicate whether the lower-level platform has the ability to run the 1400 protocol.

3. The data push control method based on the 1400 protocol according to claim 1, characterized in that: The device capability set database configuration method includes: After the lower-level platform completes registration, a subscription instruction is sent to the lower-level platform, so that the lower-level platform responds to the subscription instruction and synchronizes the camera devices with 1400 capabilities of this platform to the preset device capability set database according to the logic of the GAT1400 protocol.

4. The data push control method based on the 1400 protocol according to claim 1, characterized in that: Also includes: When it is detected that the first database is updated, the updated device identification and account information are matched with the second database. If the device identification and account information exist in the second database, the device identification and account information are used to update the device information.

5. The data push control method based on the 1400 protocol according to claim 4, characterized in that: The first database is one of the device relationship database and the device capability set database, and the second database is another database corresponding to the first database.

6. A data push control device based on 1400 protocol, characterized in that: include: A message receiving unit, configured to receive a data push message, wherein the data push message includes: image data captured by a camera device, a device identifier of the camera device, and account information of a lower-level platform to which the camera device is connected; a device relationship matching unit, configured to match the device identification and the account information with a preset device relationship database to obtain a device relationship matching result; a device capability matching unit, configured to match the device identifier and the account information with a preset device capability set database to obtain a capability set matching result; The message push execution unit is configured to push the data push message to the upper-level platform when both the device relationship matching result and the capability set matching result are successful.

7. The data push control device based on 1400 protocol according to claim 6, characterized in that: Also includes: Device relational database building unit, used for: Obtaining, through a preset GB28181 protocol, a camera device and a device directory relationship of each of the camera devices, so as to assign a device identifier to the camera device according to the device directory relationship; Bind the camera device to the account information of the connected lower-level platform and add it to the device tree; The protocol capability identifier of the lower-level platform is obtained. If the protocol capability identifier meets the preset identification judgment condition, the camera device is synchronized to the device relationship database, wherein the protocol capability identifier is used to indicate whether the lower-level platform has the ability to run the 1400 protocol.

8. The data push control device based on 1400 protocol according to claim 6, characterized in that: Also includes: Device capability set database building unit, used for: After the lower-level platform completes registration, a subscription instruction is sent to the lower-level platform, so that the lower-level platform responds to the subscription instruction and synchronizes the camera devices with 1400 capabilities of this platform to the preset device capability set database according to the logic of the GAT1400 protocol.

9. A data push control terminal based on 1400 protocol, characterized in that: include: memory and processor; The memory is used to store program code, and the program code corresponds to the data push control method based on the 1400 protocol according to any one of claims 1 to 5; The processor is configured to read and execute the program code.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores program code, and the program code is used to be read and executed by a processor to implement a data push control method based on the 1400 protocol as described in any one of claims 1 to 5.

Images