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

Abstract

The invention discloses a data push control method and device based on a 1400 protocol, a terminal and a medium, and the method comprises the steps: receiving a data push message pushed by a lower-level platform based on a GAT1400 protocol, the data push message comprises image data needing to be pushed, a device identifier used for recognizing the identity of a device, and account information; matching with an equipment relation database and an equipment capability set database according to the equipment identifier and the account information, respectively determining whether the equipment and the account are credible equipment / accounts with binding relation and have 1400 capability, if so, pushing the data push message to a superior platform, and if not, pushing the data push message to the superior platform. And the device without capability is prevented from being pushed to the superior 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 1400 protocol. Background Art

[0002] With the development of the video surveillance industry and the strengthening of national regulatory requirements, public security, food supervision bureaus, comprehensive management offices and other institutions will require that camera data in public areas or specific industries be pushed to their management platforms, i.e., 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 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 without capabilities 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 the incapable device to the upper platform in the scenario where the national standard device that does not currently have the 1400 capability is increased by the lower platform.

[0005] In order 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 identification of the camera device, and account information of a lower-level platform to which the camera device is connected;

[0007] According to the device identification and the account information, matching is performed with a preset device relationship database to obtain a device relationship matching result;

[0008] According to the device identification and the account information, matching is performed 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 the camera device and the device directory relationship of each of the camera devices through the preset GB28181 protocol, 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 them 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] When the subordinate platform completes registration, a subscription instruction is sent to the subordinate platform, so that the subordinate 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, a match is performed with the second database based on the updated device identification and account information. 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] The second aspect of the present application provides a data push control device based on the 1400 protocol, including:

[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 identification 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 identification 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 used to push the data push message to the upper-level platform when the device relationship matching result and the capability set matching result are both successful.

[0024] Preferably, it also includes: a device relationship database construction unit, which is used to:

[0025] Obtaining the camera device and the device directory relationship of each of the camera devices through the preset GB28181 protocol, 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 them 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, it also includes: a device capability set database construction unit, which is used to:

[0029] When the subordinate platform completes registration, a subscription instruction is sent to the subordinate platform, so that the subordinate 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] The third aspect of the present application provides a data push control terminal based on the 1400 protocol, including: a memory and a processor;

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

[0032] The processor is used for reading and executing the program code.

[0033] The fourth aspect of the present application provides a computer-readable storage medium, in which a 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 is first based on the GAT1400 protocol, and receives the data push message pushed by the lower-level platform, wherein the data push message contains the image data to be pushed, the device identifier and account information for identifying the device identity, and then matches with the device relationship database and the device capability set database according to the device identifier and the account information, and determines 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 drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. 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 creative labor.

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

[0038] Figure 2 A flowchart of an embodiment of a data push control method based on the 1400 protocol provided in this application.

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

[0040] Figure 4 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 A schematic diagram of the structure of an embodiment of a data push control device based on the 1400 protocol provided in this application.

[0042] Figure 6 A schematic diagram of the structure of a data push control terminal embodiment based on the 1400 protocol provided in this application. DETAILED DESCRIPTION

[0043] At present, there are mainly three types of cameras that meet the GAT1400 protocol: dedicated cameras that have the capability of this protocol and ordinary cameras that require protocol conversion. Ordinary cameras can be further divided into: 1) mounted under an AI box or NVR, which is converted to the 1400 protocol by intermediate hardware such as an AI box or NVR; 2) connected to a lower-level platform, which is converted to the 1400 protocol by the lower-level platform to interact with the centralized platform. In both cases, the mechanism of device relationship and capability set synchronization needs to be considered to ensure that the data pushed to the upper-level platform is correct. If the device relationship and device capability set are inaccurate, it may affect the timeliness of the centralized platform pushing snapshot information to the upper-level platform. Therefore, before the actual use of such cameras, the device relationship information and protocol capability set information of these devices must be configured one by one on the platform side. It is more likely to cause data push task errors due to human factors, resulting in the problem of pushing devices that do not have the corresponding capabilities to the upper-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 the incapable device to the upper platform in the scenario where the national standard device that does not currently have the 1400 capability 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 them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without 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 the present application is provided, as follows:

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

[0048] The system can be specifically divided into three main components: national standard cascade module, intensive business platform and 1400 platform. These three modules can be divided into three interconnected and integrated in a large terminal. Among them, the national standard cascade module is used to connect with the lower-level platform in accordance with the GB 28181 protocol, perform platform authentication and synchronize data such as equipment and directories, 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 device, which can configure different business capabilities based on the device, device capability set, device 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-level platform, and pushes the snapshots to one or more upper-level platforms according to the configuration.

[0049] like Figure 1 As shown, first, according to Figure 1 In 0.1~0.3, the installation and maintenance personnel obtain the platform access information of GB28181 and GAT 1400 respectively through the national standard cascading module, enter the corresponding account of the lower-level platform, and at the same time, configure the protocol capability identifier to declare whether the lower-level platform has (or partially has) 1400 capabilities. At this point, the basic configuration of the lower-level platform is completed.

[0050] Then, follow Figure 1 1.1~1.4 in the above, synchronize the equipment and catalog from the lower-level platform through the national standard cascading module according to the GB 28181 protocol and the platform cascading process through the retrieval and subscription instructions, and assign new national standard codes, i.e., equipment identifiers, to the synchronized equipment and catalog according to the rules of the centralized platform by the national standard cascading module; then synchronize the equipment to the centralized service platform, bind the corresponding account and put it on the equipment tree. If the lower-level platform is marked as "with 1400 capabilities", synchronize the equipment information to the 1400 platform to enter the equipment relationship data. If a device is added, the 1400 platform compares the newly entered equipment relationship database with the equipment capability set database with 1400 capabilities that has been synchronized from the lower-level platform. If it already exists, notify the centralized platform to update the equipment capability set.

[0051] according to Figure 12.1~2.5, the subordinate platform can register with the 1400 platform according to its configuration information. When the 1400 platform detects that a subordinate platform has completed registration, the 1400 platform sends a full device and image subscription instruction to the subordinate platform, so that the subordinate platform can respond to the instruction and synchronize the devices with 1400 capabilities to the 1400 platform through the retrieval and subscription process according to the GAT 1400 protocol standard process to enter the device capability set database. At this point, the device capability set database can be obtained. If a device is added, the 1400 platform compares the newly entered device capability set database with the devices that have been synchronized from the centralized service platform and entered into the device relationship database. If it already exists, the centralized platform is notified to add the device capability set; if the device is deleted, the centralized platform is notified to delete the device capability set.

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

[0053] Then, follow Figure 1 In 3.1~3.2, in the actual application stage, the camera device will push the stream to the lower-level platform, which will analyze the video stream frame by frame. If a picture that meets the capture conditions (face, motor vehicle, license plate, etc.) is found, it will be saved as a picture and converted to the 1400 protocol and pushed to the 1400 platform. The 1400 platform will query the device relationship (device relationship database) and capability set (device capability set database). If both exist, the data message will be pushed to the set upper-level platform according to 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 in the present application. The following is a detailed description of an embodiment of a data push control method based on the 1400 protocol provided in the present application.

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

[0056] Step 101: receiving a 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 of the lower-level platform. After receiving the data message pushed by the lower-level platform, the device identification and account information used to identify the device and user identity in the message are matched with the device relationship database and the device capability set database respectively, so as 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 referred to 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, so as to 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 capability to run the 1400 protocol.

[0067] It should be noted that steps 1001 to 1003 of this embodiment correspond to Figure 1 In 1.1~1.3, the national standard cascading module synchronizes devices and directories from the lower-level platform through retrieval 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, i.e., device identifiers, to the synchronized devices and directories according to the intensive platform rules; then synchronizes the devices to the intensive service platform, binds the corresponding account and puts them on the device tree. If the lower-level platform is marked as "with 1400 capabilities", the device information is synchronized to the 1400 platform to enter the device relationship data. At this point, the device relationship database can be 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, 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.

[0070] It should be noted that step 1004 of this embodiment corresponds to Figure 1 2.1~2.4, when the 1400 platform detects that a subordinate platform has completed registration, the 1400 platform sends a full device and image subscription instruction to the subordinate platform, so that the subordinate platform can respond to the instruction and synchronize the devices with 1400 capabilities to the 1400 platform through the retrieval and subscription process according to the GAT 1400 protocol standard 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, a match is performed with the second database based on the updated device identification and account information. 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 the device relationship or capability set is 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 the present application. The following is a detailed description of an embodiment of a data push control device based on the 1400 protocol provided by the present application.

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

[0077] The message receiving unit 201 is used to receive a data push message, wherein the data push message includes: image data captured by the camera device, a device identification 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 used 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.

[0081] Furthermore, it also includes: a device relationship database construction unit 2001, which is used 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, it also includes: a device capability set database construction unit 2002, which is used to:

[0086] When the subordinate platform completes the registration, it sends a subscription instruction to the subordinate platform, so that the subordinate 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 a data push control terminal embodiment based on the 1400 protocol and a computer-readable storage medium embodiment.

[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, and the program codes correspond to a data push control method based on the 1400 protocol as in the above embodiment;

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

[0091] The present application provides a computer-readable storage medium embodiment, 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 can 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 the present 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 only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, 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 interfaces, devices or units, which can be electrical, mechanical or other forms.

[0094] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can, for example, be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0095] It should be understood that in the present 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 objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single 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 separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0097] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0098] If the integrated unit is implemented in the form of 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, 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, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[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 aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned 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 identification of the camera device, and account information of a lower-level platform to which the camera device is connected; According to the device identification and the account information, matching is performed with a preset device relationship database to obtain a device relationship matching result; According to the device identification and the account information, matching is performed 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. According to the data push control method based on 1400 protocol according to claim 1, it is characterized in that: The configuration method of the device relationship database includes: Obtaining the camera device and the device directory relationship of each of the camera devices through the preset GB28181 protocol, 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 them 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. According to the data push control method based on 1400 protocol according to claim 1, it is characterized in that: The device capability set database configuration method comprises: When the subordinate platform completes registration, a subscription instruction is sent to the subordinate platform, so that the subordinate 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. According to the data push control method based on 1400 protocol according to claim 1, it is characterized in that: Also includes: When it is detected that the first database is updated, a match is performed with the second database based on the updated device identification and account information. 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. A data push control method based on 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 identification 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 identification and the account information with a preset device capability set database to obtain a capability set matching result; The message push execution unit is used to push the data push message to the upper-level platform when the device relationship matching result and the capability set matching result are both successful.

7. The data push control device based on 1400 protocol according to claim 6, characterized in that: Also includes: Device relational database building block for: Obtaining the camera device and the device directory relationship of each of the camera devices through the preset GB28181 protocol, 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 them 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: When the subordinate platform completes registration, a subscription instruction is sent to the subordinate platform, so that the subordinate 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 codes, and the program codes correspond to a data push control method based on 1400 protocol according to any one of claims 1 to 5; The processor is used for reading and executing 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