A national standard-based provincial dispatching system, method, device and storage medium

Abstract

The application discloses a province-based dispatching system and method based on a national standard, equipment and a storage medium, the system comprising 1400 equipment, a visual internet platform and a 1400 view library platform; the 1400 view library platform creates node information of each node after deploying the nodes; when the visual internet platform binds the 1400 equipment, the user is prompted to select an administrative region, and then the national standard code of the equipment is generated, and the equipment information and the acquisition configuration signaling are sent to the platform, so that the platform establishes the matching relationship between the equipment and the nodes according to the national standard code and the node information, and obtains the configuration information; the 1400 equipment registers on the corresponding nodes according to the configuration information acquired from the platform, and pushes the collected picture data to the nodes, thereby improving the technical problems that the existing technology has complicated configuration information input for equipment connection 1400 view library, the related information needs to be configured on the equipment setting page by the installation and maintenance personnel, the manual operation error rate is relatively high, and the equipment installation efficiency is relatively low.

Description

Technical Field

[0001] This application relates to the field of video network technology, and in particular to a provincial scheduling system, method, device and storage medium based on national standards. Background Technology

[0002] With the continuous development of China Telecom's video network equipment and services, public security bureaus in various cities now require the use of video image information from public areas. This information is captured by front-end cameras using a specific capture mechanism, including images of license plates, and then transmitted to the 1400 View Library platform. The platform stores and indexes the captured images, connecting them to the public security network. These images are then streamed to the public security information system for intelligent analysis and display.

[0003] The existing provincial architecture of the GA / T view library has drawbacks in actual implementation. The input of configuration information for connecting devices to the 1400 view library is cumbersome, requiring installation and maintenance personnel to configure relevant information on the device settings page. This results in a high error rate due to manual operation and low equipment installation efficiency. Summary of the Invention

[0004] This application provides a provincial scheduling system, method, device, and storage medium based on national standards to improve the technical problems of existing technologies, such as cumbersome input of equipment connection 1400 view library configuration information, the need for installation and maintenance personnel to configure relevant information on the equipment settings page, high error rate of manual operation, and low equipment installation efficiency.

[0005] In view of this, the first aspect of this application provides a provincial dispatch system based on national standards, including: 1400 equipment, a video network platform, and a 1400 view library platform;

[0006] The 1400 view library platform is used to create node information corresponding to each node after the nodes are deployed. The node information includes the node region, the node survival status, and the node domain name or node IP.

[0007] The video network platform is used to prompt the user to select an administrative region when binding a 1400 device, generate the national standard code of the 1400 device according to the selection result and the national standard generation rules, and send the device information and configuration acquisition signaling of the 1400 device to the 1400 view library platform.

[0008] The 1400 view library platform is also used to establish a matching relationship between the device and the node based on the national standard code in the device information of the 1400 device and the node information, to obtain the configuration information of the 1400 device, and to send a configuration acquisition signaling to the 1400 device.

[0009] The 1400 device is used to obtain corresponding configuration information from the 1400 view library platform, register on the corresponding matching node according to the configuration information, and push the collected image data to the corresponding node.

[0010] Optionally, the 1400 view library platform includes a central node and sub-nodes, with the sub-nodes including provincial sub-nodes, municipal sub-nodes, and district sub-nodes;

[0011] The central node is specifically used for:

[0012] Obtain the national standard code from the equipment information of the 1400 devices;

[0013] Based on the first 6 digits of the national standard code and the node information, it is determined whether a district-level sub-node can be matched. If a district-level sub-node can be matched, the 1400 device is scheduled to the district-level sub-node, and a matching relationship between the 1400 device and the district-level sub-node is established.

[0014] If a district-level sub-node cannot be matched, then the first four digits of the national standard code and the node information are used to determine whether a city-level sub-node can be matched. If a city-level sub-node can be matched, then the 1400 device is scheduled to the city-level sub-node, and a matching relationship between the 1400 device and the city-level sub-node is established.

[0015] If a municipal-level sub-node cannot be matched, then the first two digits of the national standard code and the node information are used to determine whether a provincial-level sub-node can be matched. If a provincial-level sub-node can be matched, then the 1400 device is scheduled to the provincial-level sub-node, and a matching relationship between the 1400 device and the provincial-level sub-node is established.

[0016] If a provincial sub-node cannot be matched, the 1400 device will be scheduled to the central node, and a matching relationship between the 1400 device and the central node will be established.

[0017] Optionally, the 1400 view library platform also includes a public security view library;

[0018] The central node and the branch nodes are respectively used to push the received image data to the public security view database;

[0019] The sub-nodes are also used to upload the push results to the superior node, wherein the superior node of the district-level sub-node is the city-level sub-node, the superior node of the city-level sub-node is the provincial-level sub-node, and the superior node of the provincial-level sub-node is the central node.

[0020] Optionally, the central node is further used for:

[0021] Real-time monitoring of each sub-node; if a fault is detected in the target sub-node, an automatic alarm mechanism is triggered and the operation and maintenance personnel are notified to handle the situation.

[0022] If the target sub-node still has a fault after the preset time period, then it is determined whether the target sub-node has a corresponding city-level sub-node.

[0023] If no corresponding city-level sub-node exists, then obtain the node information of the provincial-level sub-node corresponding to the target sub-node;

[0024] If a corresponding city-level sub-node exists, the node information of the city-level sub-node is obtained, and the status of the city-level sub-node is determined based on the node information. If it is normal, the target sub-node is scheduled to the city-level sub-node, and a matching relationship between the target sub-node and the city-level sub-node is established. If it is not normal, the node information of the provincial sub-node corresponding to the target sub-node is obtained.

[0025] After obtaining the node information of the provincial sub-node, the status of the provincial sub-node is determined based on the node information. If it is normal, the target sub-node is scheduled to the provincial sub-node, and a matching relationship between the target sub-node and the provincial sub-node is established. If it is not normal, the target sub-node is scheduled to the central node, and a matching relationship between the target sub-node and the central node is established.

[0026] Optionally, the real-time monitoring of each sub-node includes:

[0027] Real-time acquisition of the success rate of pushing the map at each sub-node;

[0028] When the success rate of pushing the target sub-node drops to a preset threshold and continues for a preset time, the target sub-node is determined to have failed.

[0029] Optionally, the video network platform is specifically used to respond to the device binding command, determine whether the device is a 1400 device, and if so, prompt the user to select an administrative region, generate the national standard code of the 1400 device according to the selection result and the national standard generation rules, and send the device information and configuration acquisition signaling of the 1400 device to the 1400 view library platform.

[0030] The second aspect of this application provides a provincial-level scheduling method based on national standards, applicable to any of the provincial-level scheduling systems based on national standards described in the first aspect, the method comprising:

[0031] Nodes are deployed through the 1400 View Library platform, and node information corresponding to each node is created. The node information includes the node region, node liveness status, and node domain name or node IP.

[0032] By binding the 1400 device to the video network platform, the user is prompted to select an administrative region. Based on the selection result and the national standard generation rules, the national standard code of the 1400 device is generated, and the device information and configuration acquisition signaling of the 1400 device are sent to the 1400 view library platform.

[0033] The 1400 view library platform establishes a matching relationship between the device and the node based on the national standard code in the device information of the 1400 device and the node information, obtains the configuration information of the 1400 device, and sends a configuration acquisition signaling to the 1400 device.

[0034] The 1400 device obtains the corresponding configuration information from the 1400 view library platform, registers on the corresponding matching node according to the configuration information, and pushes the collected image data to the corresponding node.

[0035] Optionally, the 1400 view library platform includes a central node and sub-nodes, with the sub-nodes including provincial sub-nodes, municipal sub-nodes, and district sub-nodes;

[0036] The step of establishing a matching relationship between devices and nodes through the 1400 view library platform based on the national standard code in the device information of the 1400 device and the node information includes:

[0037] The national standard code is obtained from the equipment information of 1400 devices through the central node;

[0038] Based on the first 6 digits of the national standard code and the node information, it is determined whether a district-level sub-node can be matched. If a district-level sub-node can be matched, the 1400 device is scheduled to the district-level sub-node, and a matching relationship between the 1400 device and the district-level sub-node is established.

[0039] If a district-level sub-node cannot be matched, then the first four digits of the national standard code and the node information are used to determine whether a city-level sub-node can be matched. If a city-level sub-node can be matched, then the 1400 device is scheduled to the city-level sub-node, and a matching relationship between the 1400 device and the city-level sub-node is established.

[0040] If a municipal-level sub-node cannot be matched, then the first two digits of the national standard code and the node information are used to determine whether a provincial-level sub-node can be matched. If a provincial-level sub-node can be matched, then the 1400 device is scheduled to the provincial-level sub-node, and a matching relationship between the 1400 device and the provincial-level sub-node is established.

[0041] If a provincial sub-node cannot be matched, the 1400 device will be scheduled to the central node, and a matching relationship between the 1400 device and the central node will be established.

[0042] A third aspect of this application provides a provincial scheduling device based on national standards, the device including a processor and a memory;

[0043] The memory is used to store program code and transmit the program code to the processor;

[0044] The processor is used to execute any of the provincial scheduling methods based on national standards described in the second aspect according to the instructions in the program code.

[0045] The fourth aspect of this application provides a computer-readable storage medium for storing program code, which, when executed by a processor, implements the provincial scheduling method based on national standards as described in any of the second aspects.

[0046] As can be seen from the above technical solutions, this application has the following advantages:

[0047] This application provides a provincial-level scheduling system based on national standards, comprising: a 1400 device, a video network platform, and a 1400 view library platform; the 1400 view library platform is used to create node information corresponding to each node after deployment, including node region, node liveness status, and node domain name or node IP; the video network platform is used to prompt the user to select an administrative region when binding the 1400 device, generate the national standard code of the 1400 device according to the selection result and national standard generation rules, and send the device information and configuration acquisition signaling of the 1400 device to the 1400 view library platform; the 1400 view library platform is also used to establish a matching relationship between the device and the node according to the national standard code and node information in the device information of the 1400 device, obtain the configuration information of the 1400 device, and send the configuration acquisition signaling to the 1400 device; the 1400 device is used to obtain the corresponding configuration information from the 1400 view library platform, register on the corresponding matched node according to the configuration information, and push the collected image data to the corresponding node.

[0048] In this application, after deploying nodes, the 1400 view library platform creates node information corresponding to each node. When binding the 1400 device, the video network platform generates the national standard code of the 1400 device and stores the device information of the 1400 device in the 1400 view library platform. The 1400 view library platform matches the national standard code of the 1400 device with the node information to create a matching relationship between the device and the node, thereby generating the configuration information of the 1400 device. The 1400 device obtains the corresponding configuration information from the 1400 view library platform and registers on the corresponding node so that it can subsequently push the collected image data to the relevant node. The corresponding nodes enable the scheduling of 1400 devices to their respective nodes. The 1400 view library platform automatically matches the corresponding nodes according to the national standard codes, eliminating the need for manual interface configuration for individual devices. This saves installation and maintenance personnel the workload of configuring view library node information and authentication parameters on the device settings page, avoiding errors caused by manual operation, and improving the installation and deployment efficiency of 1400 devices. This addresses the technical problems of existing technologies, such as cumbersome input of device connection configuration information to the 1400 view library, the need for installation and maintenance personnel to configure relevant information on the device settings page, high error rate of manual operation, and low equipment installation and deployment efficiency. Attached Figure Description

[0049] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0050] Figure 1 A schematic diagram of a provincial scheduling system based on national standards provided in this application embodiment;

[0051] Figure 2 A schematic diagram of the process of scheduling 1400 devices to nodes provided in an embodiment of this application;

[0052] Figure 3 A flowchart illustrating an automatic exception handling mechanism triggered when a node fails, as provided in an embodiment of this application.

[0053] Figure 4 A schematic diagram of the existing GA / T1400 view library provincial architecture provided for embodiments of this application;

[0054] Figure 5 This is a flowchart illustrating a provincial scheduling method based on national standards, provided as an embodiment of this application. Detailed Implementation

[0055] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0056] If such as Figure 4 The existing GA / T1400 view library deployment architecture shown in the diagram uses a provincial-level deployment architecture for equipment scheduling. However, this architecture suffers from excessively long deployment links. Only district-level view libraries connect to capture devices, and connecting devices to the view library requires installation and maintenance personnel to manually enter view library node information and authentication parameters on-site through the device's backend settings page. This results in slow deployment speeds, requires specialized training for installation and maintenance personnel, has a high error rate due to manual operation, low equipment deployment efficiency, and long debugging and testing times when problems arise, thus hindering the large-scale development of the video network image service.

[0057] To improve the above issues, please refer to Figure 1 This application provides a provincial dispatch system based on national standards, including: 1400 devices, a video network platform, and a 1400 view library platform;

[0058] The 1400 View Library platform is used to create node information for each node after deployment. The node information includes the node region, node liveness status, and node domain name or node IP.

[0059] The video network platform is used to prompt users to select an administrative region when binding a 1400 device, generate the national standard code of the 1400 device according to the selection result and national standard generation rules, and send the device information and configuration acquisition signaling of the 1400 device to the 1400 view library platform.

[0060] The 1400 view library platform is also used to establish a matching relationship between devices and nodes based on the national standard code and node information in the device information of the 1400 device, obtain the configuration information of the 1400 device, and send the configuration acquisition signaling to the 1400 device.

[0061] The 1400 device is used to obtain the corresponding configuration information from the 1400 view library platform, register on the corresponding matching node according to the configuration information, and push the collected image data to the corresponding node.

[0062] In this embodiment of the application, the 1400 view library platform is used to create node information corresponding to each node after the nodes are deployed. One of the fields is to select the province, city, or district where the node is located. The node information includes the node region, the node's liveness status, and the node's domain name or node IP.

[0063] After receiving a device binding instruction, the video network platform responds by determining whether the device is a 1400 device. If so, it prompts the user to select an administrative region (and may also prompt the user to select a police station). Based on the selection result and the national standard generation rules, it generates the national standard code (such as national standard ID) for the 1400 device and sends the device information (including national standard code, device model, etc.) and configuration acquisition signaling to the 1400 view library platform. The video network platform can send device information and configuration acquisition signaling to the 1400 view library platform through the signaling system.

[0064] After receiving device information and configuration information acquisition instructions from the video network platform, the 1400 View Library platform establishes a matching relationship between the device and the node based on the national standard code in the device information of the 1400 device and the node information stored in its own memory. It then obtains the configuration information of the 1400 device and sends a configuration acquisition signaling message to the 1400 device. Upon receiving the configuration signaling message, the 1400 device can obtain the corresponding configuration information (i.e., node information) from the 1400 View Library platform, register on the corresponding matching node according to the configuration information, and push the collected image data to the corresponding node.

[0065] In this embodiment, the 1400 view library platform includes a central node and several sub-nodes, including provincial, municipal, and district-level sub-nodes. The central node is specifically used for:

[0066] Obtain the national standard code from the equipment information of the 1400 devices;

[0067] Based on the first 6 digits of the national standard code (district / county administrative code) and node information (specifically, based on the node area in the node information), it is determined whether a district-level sub-node can be matched. If a district-level sub-node can be matched, the 1400 device is scheduled to the district-level sub-node, and a matching relationship between the 1400 device and the district-level sub-node is established.

[0068] If a district-level sub-node cannot be matched, the first four digits of the national standard code and the node information are used to determine whether a city-level sub-node can be matched. If a city-level sub-node can be matched, the 1400 device is scheduled to the city-level sub-node, and a matching relationship between the 1400 device and the city-level sub-node is established.

[0069] If a municipal-level sub-node cannot be matched, the first two digits of the national standard code and the node information are used to determine whether a provincial-level sub-node can be matched. If a provincial-level sub-node can be matched, the 1400 device is scheduled to the provincial-level sub-node, and a matching relationship between the 1400 device and the provincial-level sub-node is established.

[0070] If a provincial sub-node cannot be matched, the 1400 device will be scheduled to the central node, and a matching relationship between the 1400 device and the central node will be established.

[0071] Furthermore, the 1400 View Library platform also includes a public security view library;

[0072] The central node and the branch nodes are used to push the received image data to the public security view database, respectively.

[0073] Sub-nodes are also used to upload push results to higher-level nodes. The higher-level node of a district-level sub-node is a city-level sub-node, the higher-level node of a city-level sub-node is a provincial-level sub-node, and the higher-level node of a provincial-level sub-node is a central node.

[0074] Furthermore, the central node is also used for:

[0075] Real-time monitoring of each sub-node; if a fault is detected in the target sub-node, an automatic alarm mechanism is triggered and the operation and maintenance personnel are notified to handle the situation.

[0076] If the target sub-node still has a fault after the preset time period, then determine whether the target sub-node has a corresponding city-level sub-node.

[0077] If no corresponding municipal-level sub-node exists, obtain the node information of the provincial-level sub-node corresponding to the target sub-node;

[0078] If a corresponding city-level sub-node exists, obtain the node information of that city-level sub-node and determine whether the status of that city-level sub-node is normal based on the node information. If it is normal, schedule the target sub-node to that city-level sub-node and establish a matching relationship between the target sub-node and that city-level sub-node. If it is not normal, obtain the node information of the provincial sub-node corresponding to the target sub-node.

[0079] After obtaining the node information of the provincial sub-node, the status of the provincial sub-node is determined based on the node information. If it is normal, the target sub-node is scheduled to the provincial sub-node, and a matching relationship between the target sub-node and the provincial sub-node is established. If it is not normal, the target sub-node is scheduled to the central node, and a matching relationship between the target sub-node and the central node is established.

[0080] In this embodiment, the central node serves as a backup for all sub-nodes. The central node comprises two parts: a scheduling / management service and an image processing service. The scheduling / management service consists of a signaling module, a node scheduling module, a node management module, and a device management module, while the image processing service consists of an image receiving module and an image processing module. Each sub-node consists of an image receiving module and an image processing module.

[0081] The device management module is used to manage the information data of the 1400 devices, including Ape device information (including national standard codes, device models, etc.) and node information of the nodes where the devices are located;

[0082] The signaling module is used to interface with the signaling system, instruct the device to turn on the 1400 capability set switch when binding, and obtain the latest node information from the 1400 view library platform;

[0083] The node management module is used to manage node information, such as node region, node domain name or IP address, and node status. This information can be added, deleted, modified, and queried through the 1400 management backend. After node deployment, corresponding node information needs to be created in the 1400 management backend, with one field allowing selection of the node's province, city, and district.

[0084] The node scheduling module is used to match the 1400 device with the corresponding node based on the national standard code and node information, schedule the 1400 device to the corresponding node, and establish the matching relationship between the device and the node to generate the configuration information of the 1400 device. This implements a dynamic scheduling method based on the national standard. For details on the scheduling process, please refer to [reference needed]. Figure 2 If a sub-node subsequently fails, it will also be used to dynamically schedule equipment to the parent node corresponding to the failed sub-node. For details on the scheduling process of a failed district-level sub-node, please refer to [link / reference needed]. Figure 3 The scheduling process for other faulty sub-nodes is similar. It should be noted that when monitoring each sub-node, the central node obtains the real-time success rate of each sub-node's graph push. When the success rate of a target sub-node drops to a preset threshold and remains so for a preset time, the target sub-node is determined to be faulty. At this point, the central node will trigger an automatic alarm mechanism and notify operations personnel to handle the issue. If, after the preset time period, operations personnel have not handled the issue, meaning the target sub-node is still faulty, the central node will trigger... Figure 3 The automatic exception handling mechanism shown;

[0085] The image receiving module is used to receive image data pushed by 1400 devices and lower-level nodes;

[0086] The image push module is used to push received image data to the public security view database.

[0087] The provincial scheduling system based on national standards in this application embodiment can achieve the following effects:

[0088] Automatic scheduling: It allows the 1400 devices to be automatically matched to the corresponding nodes according to the national standard code, eliminating the need for interface configuration of individual devices. This not only saves a lot of installation and maintenance time, but also avoids the problem of human operation errors.

[0089] Elastic expansion: This system has the feature of elastic expansion. In the process of developing sub-nodes, only provincial sub-nodes can be built first to achieve rapid implementation in provinces. After the business scale reaches a certain level, the system can be expanded to build city-level or county (district) level view libraries. Finally, the equipment can be batch-scheduled down to each city or county (district) level view library, thereby reducing the bandwidth, server and other resource pressure on the upper-level view library.

[0090] Fault tolerance: When a lower-level node fails, the system can automatically schedule the upper-level node of the failed node, thereby improving the stability of the system.

[0091] In this embodiment, after deploying nodes, the 1400 view library platform creates node information corresponding to each node. When binding the 1400 device, the video network platform generates the national standard code of the 1400 device and stores the device information of the 1400 device in the 1400 view library platform. The 1400 view library platform matches the national standard code of the 1400 device with the node information to create a matching relationship between the device and the node, thereby generating the configuration information of the 1400 device. The 1400 device obtains the corresponding configuration information from the 1400 view library platform and registers on the corresponding node. Subsequently, it pushes the collected image data to the [node name missing]. The corresponding nodes enable the scheduling of 1400 devices to their respective nodes. The 1400 view library platform automatically matches the corresponding nodes according to the national standard codes, eliminating the need for manual interface configuration for individual devices. This saves installation and maintenance personnel the workload of configuring view library node information and authentication parameters on the device settings page, avoiding errors caused by manual operation, and improving the installation and deployment efficiency of 1400 devices. This addresses the technical problems of existing technologies, such as cumbersome input of device connection configuration information to the 1400 view library, the need for installation and maintenance personnel to configure relevant information on the device settings page, high error rate of manual operation, and low equipment installation and deployment efficiency.

[0092] The above is an embodiment of a provincial scheduling system based on national standards provided in this application. The following is an embodiment of a provincial scheduling method based on national standards provided in this application.

[0093] Please refer to Figure 5 This application provides a provincial-level scheduling method based on national standards, applied to the provincial-level scheduling system based on national standards in the aforementioned embodiments. The method includes:

[0094] Step 101: Deploy nodes through the 1400 View Library platform and create node information for each node. The node information includes the node region, node liveness status, and node domain name or node IP.

[0095] After deploying nodes, the 1400 View Library platform creates node information for each node. One of the fields is to select the province, city, or region where the node is located. The node information includes the node region, node liveness status, and node domain name or node IP.

[0096] Step 102: Bind the 1400 device through the video network platform, prompt the user to select an administrative region, generate the national standard code of the 1400 device according to the selection result and national standard generation rules, and send the device information and configuration acquisition signaling of the 1400 device to the 1400 view library platform.

[0097] After receiving a device binding instruction, the video network platform responds by determining whether the device is a 1400 device. If so, it prompts the user to select an administrative region (and may also prompt the user to select a police station). Based on the selection result and the national standard generation rules, it generates the national standard code (such as national standard ID) for the 1400 device and sends the device information (including national standard code, device model, etc.) and configuration acquisition signaling to the 1400 view library platform. The video network platform can send device information and configuration acquisition signaling to the 1400 view library platform through the signaling system.

[0098] Step 103: Establish a matching relationship between the device and the node through the 1400 view library platform based on the national standard code and node information in the device information of the 1400 device, obtain the configuration information of the 1400 device, and send the configuration acquisition signaling to the 1400 device.

[0099] After receiving the device information and configuration information acquisition instruction sent by the video network platform, the 1400 view library platform establishes a matching relationship between the device and the node based on the national standard code in the device information of the 1400 device and the node information stored in itself, obtains the configuration information of the 1400 device, and sends a configuration acquisition signaling to the 1400 device.

[0100] The 1400 View Library platform includes a central node and sub-nodes, with sub-nodes at the provincial, municipal, and district levels. The platform establishes a matching relationship between devices and nodes based on the national standard codes and node information within the equipment information of the 1400 devices. This includes:

[0101] The national standard code is obtained from the equipment information of 1400 devices through the central node;

[0102] Based on the first 6 digits of the national standard code and the node information, it is determined whether a district-level sub-node can be matched. If a district-level sub-node can be matched, the 1400 device is scheduled to the district-level sub-node, and a matching relationship between the 1400 device and the district-level sub-node is established.

[0103] If a district-level sub-node cannot be matched, the first four digits of the national standard code and the node information are used to determine whether a city-level sub-node can be matched. If a city-level sub-node can be matched, the 1400 device is scheduled to the city-level sub-node, and a matching relationship between the 1400 device and the city-level sub-node is established.

[0104] If a municipal-level sub-node cannot be matched, the first two digits of the national standard code and the node information are used to determine whether a provincial-level sub-node can be matched. If a provincial-level sub-node can be matched, the 1400 device is scheduled to the provincial-level sub-node, and a matching relationship between the 1400 device and the provincial-level sub-node is established.

[0105] If a provincial sub-node cannot be matched, the 1400 device will be scheduled to the central node, and a matching relationship between the 1400 device and the central node will be established.

[0106] Furthermore, the central node can monitor each sub-node in real time. When monitoring each sub-node, the central node can obtain the success rate of pushing the map of each sub-node in real time. When the success rate of pushing the map of a target sub-node drops to a preset threshold and continues for a preset time, it is determined that the target sub-node has failed and that the target sub-node is the failed node.

[0107] If a fault is detected in the target sub-node, an automatic alarm mechanism will be triggered, and the operation and maintenance personnel will be notified to handle it.

[0108] If the target sub-node still has a fault after the preset time period, then determine whether the target sub-node has a corresponding city-level sub-node.

[0109] If no corresponding municipal-level sub-node exists, obtain the node information of the provincial-level sub-node corresponding to the target sub-node;

[0110] If a corresponding city-level sub-node exists, obtain the node information of that city-level sub-node and determine whether the status of that city-level sub-node is normal based on the node information. If it is normal, schedule the target sub-node to that city-level sub-node and establish a matching relationship between the target sub-node and that city-level sub-node. If it is not normal, obtain the node information of the provincial sub-node corresponding to the target sub-node.

[0111] After obtaining the node information of the provincial sub-node, the status of the provincial sub-node is determined based on the node information. If it is normal, the target sub-node is scheduled to the provincial sub-node, and a matching relationship between the target sub-node and the provincial sub-node is established. If it is not normal, the target sub-node is scheduled to the central node, and a matching relationship between the target sub-node and the central node is established.

[0112] Step 104: Obtain the corresponding configuration information from the 1400 view library platform through the 1400 device, register on the corresponding matching node according to the configuration information, and push the collected image data to the corresponding node.

[0113] When the 1400 device receives the configuration signaling, it can obtain the corresponding configuration information (i.e., node information) from the 1400 view library platform, then register on the corresponding matching node according to the configuration information, and push the collected image data to the corresponding node.

[0114] In this embodiment, after deploying nodes, the 1400 view library platform creates node information corresponding to each node. When binding the 1400 device, the video network platform generates the national standard code of the 1400 device and stores the device information of the 1400 device in the 1400 view library platform. The 1400 view library platform matches the national standard code of the 1400 device with the node information to create a matching relationship between the device and the node, thereby generating the configuration information of the 1400 device. The 1400 device obtains the corresponding configuration information from the 1400 view library platform and registers on the corresponding node. Subsequently, it pushes the collected image data to the [node name missing]. The corresponding nodes enable the scheduling of 1400 devices to their respective nodes. The 1400 view library platform automatically matches the corresponding nodes according to the national standard codes, eliminating the need for manual interface configuration for individual devices. This saves installation and maintenance personnel the workload of configuring view library node information and authentication parameters on the device settings page, avoiding errors caused by manual operation, and improving the installation and deployment efficiency of 1400 devices. This addresses the technical problems of existing technologies, such as cumbersome input of device connection configuration information to the 1400 view library, the need for installation and maintenance personnel to configure relevant information on the device settings page, high error rate of manual operation, and low equipment installation and deployment efficiency.

[0115] This application also provides a provincial scheduling device based on national standards, the device including a processor and a memory;

[0116] The memory is used to store program code and transfer the program code to the processor;

[0117] The processor is used to execute the national standard-based provincial scheduling method in the aforementioned method embodiments according to the instructions in the program code.

[0118] This application also provides a computer-readable storage medium for storing program code, which, when executed by a processor, implements the national standard-based provincial scheduling method in the aforementioned method embodiments.

[0119] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises 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 processes, methods, products, or apparatus.

[0120] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

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

[0122] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0123] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0124] 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 this application, 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. This computer software product is stored in a storage medium and includes several instructions for executing all or part of the steps of the methods described in the various embodiments of this application through a computer device (which may be a personal computer, server, or network device, etc.). The aforementioned storage medium includes: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.

[0125] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A provincial-level scheduling system based on national standards, characterized in that, include: 1400 devices, video network platform, and 1400 view library platform; The 1400 view library platform is used to create node information corresponding to each node after the nodes are deployed. The node information includes the node region, the node survival status, and the node domain name or node IP. The video network platform is used to prompt the user to select an administrative region when binding a 1400 device, generate the national standard code of the 1400 device according to the selection result and the national standard generation rules, and send the device information and configuration acquisition signaling of the 1400 device to the 1400 view library platform. The 1400 view library platform is also used to establish a matching relationship between the device and the node based on the national standard code in the device information of the 1400 device and the node information, to obtain the configuration information of the 1400 device, and to send a configuration acquisition signaling to the 1400 device. The 1400 device is used to obtain corresponding configuration information from the 1400 view library platform, register on the corresponding matching node according to the configuration information, and push the collected image data to the corresponding node. The 1400 view library platform includes a central node and sub-nodes, with the sub-nodes including provincial sub-nodes, municipal sub-nodes, and district sub-nodes; The central node is specifically used for: Obtain the national standard code from the equipment information of the 1400 devices; Based on the first 6 digits of the national standard code and the node information, it is determined whether a district-level sub-node can be matched. If a district-level sub-node can be matched, the 1400 device is scheduled to the district-level sub-node, and a matching relationship between the 1400 device and the district-level sub-node is established. If a district-level sub-node cannot be matched, then the first four digits of the national standard code and the node information are used to determine whether a city-level sub-node can be matched. If a city-level sub-node can be matched, then the 1400 device is scheduled to the city-level sub-node, and a matching relationship between the 1400 device and the city-level sub-node is established. If a municipal-level sub-node cannot be matched, then the first two digits of the national standard code and the node information are used to determine whether a provincial-level sub-node can be matched. If a provincial-level sub-node can be matched, then the 1400 device is scheduled to the provincial-level sub-node, and a matching relationship between the 1400 device and the provincial-level sub-node is established. If a provincial-level sub-node cannot be matched, the 1400 device will be scheduled to the central node, and a matching relationship between the 1400 device and the central node will be established. The central node is also used for: Real-time acquisition of the success rate of pushing the map at each sub-node; When the success rate of pushing the target sub-node drops to a preset threshold and continues for a preset time, the target sub-node is determined to have failed. If a fault is detected in the target sub-node, an automatic alarm mechanism will be triggered, and the operation and maintenance personnel will be notified to handle it. If the target sub-node still has a fault after the preset time period, then it is determined whether the target sub-node has a corresponding city-level sub-node. If no corresponding city-level sub-node exists, then obtain the node information of the provincial-level sub-node corresponding to the target sub-node; If a corresponding city-level sub-node exists, the node information of the city-level sub-node is obtained, and the status of the city-level sub-node is determined based on the node information. If it is normal, the target sub-node is scheduled to the city-level sub-node, and a matching relationship between the target sub-node and the city-level sub-node is established. If it is not normal, the node information of the provincial sub-node corresponding to the target sub-node is obtained. After obtaining the node information of the provincial sub-node, the status of the provincial sub-node is determined based on the node information. If it is normal, the target sub-node is scheduled to the provincial sub-node, and a matching relationship between the target sub-node and the provincial sub-node is established. If it is not normal, the target sub-node is scheduled to the central node, and a matching relationship between the target sub-node and the central node is established.

2. The provincial dispatching system based on national standards according to claim 1, characterized in that, The 1400 view library platform also includes a public security view library; The central node and the branch nodes are respectively used to push the received image data to the public security view database; The sub-nodes are also used to upload the push results to the superior node, wherein the superior node of the district-level sub-node is the city-level sub-node, the superior node of the city-level sub-node is the provincial-level sub-node, and the superior node of the provincial-level sub-node is the central node.

3. The provincial dispatching system based on national standards according to claim 1, characterized in that, The video network platform is specifically used to respond to the device binding command, determine whether the device is a 1400 device, and if so, prompt the user to select an administrative region, generate the national standard code of the 1400 device according to the selection result and the national standard generation rules, and send the device information and configuration acquisition signaling of the 1400 device to the 1400 view library platform.

4. A provincial-level scheduling method based on national standards, characterized in that, The method, applied to the provincial-level scheduling system based on national standards as described in any one of claims 1-3, comprises: Nodes are deployed through the 1400 View Library platform, and node information corresponding to each node is created. The node information includes the node region, node liveness status, and node domain name or node IP. By binding the 1400 device to the video network platform, the user is prompted to select an administrative region. Based on the selection result and the national standard generation rules, the national standard code of the 1400 device is generated, and the device information and configuration acquisition signaling of the 1400 device are sent to the 1400 view library platform. The 1400 view library platform establishes a matching relationship between the device and the node based on the national standard code in the device information of the 1400 device and the node information, obtains the configuration information of the 1400 device, and sends a configuration acquisition signaling to the 1400 device. The 1400 device obtains the corresponding configuration information from the 1400 view library platform, registers on the corresponding matching node according to the configuration information, and pushes the collected image data to the corresponding node. The 1400 view library platform includes a central node and sub-nodes, with the sub-nodes including provincial sub-nodes, municipal sub-nodes, and district sub-nodes; The step of establishing a matching relationship between devices and nodes through the 1400 view library platform based on the national standard code in the device information of the 1400 device and the node information includes: The national standard code is obtained from the equipment information of the 1400 devices through the central node; Based on the first 6 digits of the national standard code and the node information, it is determined whether a district-level sub-node can be matched. If a district-level sub-node can be matched, the 1400 device is scheduled to the district-level sub-node, and a matching relationship between the 1400 device and the district-level sub-node is established. If a district-level sub-node cannot be matched, then the first four digits of the national standard code and the node information are used to determine whether a city-level sub-node can be matched. If a city-level sub-node can be matched, then the 1400 device is scheduled to the city-level sub-node, and a matching relationship between the 1400 device and the city-level sub-node is established. If a municipal-level sub-node cannot be matched, then the first two digits of the national standard code and the node information are used to determine whether a provincial-level sub-node can be matched. If a provincial-level sub-node can be matched, then the 1400 device is scheduled to the provincial-level sub-node, and a matching relationship between the 1400 device and the provincial-level sub-node is established. If a provincial-level sub-node cannot be matched, the 1400 device will be scheduled to the central node, and a matching relationship between the 1400 device and the central node will be established. The success rate of each sub-node in pushing the map is obtained in real time through the central node; When the success rate of pushing the target sub-node drops to a preset threshold and continues for a preset time, the target sub-node is determined to have failed. If a fault is detected in the target sub-node, an automatic alarm mechanism will be triggered, and the operation and maintenance personnel will be notified to handle it. If the target sub-node still has a fault after the preset time period, then it is determined whether the target sub-node has a corresponding city-level sub-node. If no corresponding city-level sub-node exists, then obtain the node information of the provincial-level sub-node corresponding to the target sub-node; If a corresponding city-level sub-node exists, the node information of the city-level sub-node is obtained, and the status of the city-level sub-node is determined based on the node information. If it is normal, the target sub-node is scheduled to the city-level sub-node, and a matching relationship between the target sub-node and the city-level sub-node is established. If it is not normal, the node information of the provincial sub-node corresponding to the target sub-node is obtained. After obtaining the node information of the provincial sub-node, the status of the provincial sub-node is determined based on the node information. If it is normal, the target sub-node is scheduled to the provincial sub-node, and a matching relationship between the target sub-node and the provincial sub-node is established. If it is not normal, the target sub-node is scheduled to the central node, and a matching relationship between the target sub-node and the central node is established.

5. A provincial dispatching device based on national standards, characterized in that, The device includes a processor and a memory; The memory is used to store program code and transmit the program code to the processor; The processor is used to execute the provincial scheduling method based on national standards as described in claim 4 according to the instructions in the program code.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store program code, which, when executed by a processor, implements the provincial scheduling method based on national standards as described in claim 4.

Images