A video monitoring platform data transmission control method, system and device

Abstract

The present disclosure relates to a video monitoring platform data transmission control method, system and device, the method comprising: screening the resource directory version stamp of the monitoring platform in the superior and inferior domains, encapsulating the screened directory entries as directory synchronization difference packages; based on the link state parameters, splitting and sending the directory synchronization difference packages to the inferior domain, obtaining the reception confirmation fragments and recombining them into directory synchronization success signaling, and synchronizing the resource directory of the target monitoring point to the current platform; based on the device identifier, injecting a probe data package into the bearing network, capturing its time delay jitter value, continuous packet loss count and available bandwidth estimation value as real-time network quality parameters; based on the preset encoding strategy library, extracting the target encoding strategy from the continuous packet loss count, and sending the encoding parameters to the encoding device after re-negotiation to generate a new video stream adapted to the current network quality; the present application can improve the service stability of the monitoring platform in complex network environment.

Description

Technical Field

[0001] This invention relates to the field of data transmission technology, and in particular to a data transmission control method, system and device for a video surveillance platform. Background Technology

[0002] With the deepening of highway informatization, video surveillance platforms, as the core support for road network operation monitoring and emergency dispatch, are continuously expanding in scale. They typically adopt a multi-level network architecture, consisting of platforms at the provincial, municipal, and road section levels. Under this architecture, frequent synchronization of monitoring point directory information is required between upper and lower level platforms to ensure unified management and retrieval of network resources. Simultaneously, real-time video preview, as a fundamental service, requires the platform to dynamically adjust data transmission strategies based on network conditions to ensure the smoothness and clarity of the monitoring footage. In these scenarios, gateway devices, as the hub for cross-domain data interaction, directly determine the overall service capabilities of the platform through their transmission control mechanisms.

[0003] In existing technologies, cross-domain directory synchronization methods mostly employ timed full pushes or incremental updates based on simple heartbeat detection. These methods lack awareness and adaptive processing of real-time network link quality, making it difficult to cope with bandwidth fluctuations and packet loss interference in wide area network environments. This leads to inconsistencies in directory data between upper and lower level platforms, creating "information silos." Regarding real-time video transmission, existing methods typically use fixed bitrate transmission or manual switching based on local device caching. They cannot adjust encoding strategies in real-time based on dynamic latency jitter, continuous packet loss counts, and available bandwidth estimates of the carrying network. When network congestion occurs, video stuttering, pixelation, or even disconnection can easily occur, severely reducing the reliability of monitoring and the user experience. Therefore, there is an urgent need to develop a data transmission control method that can perceive link status in real time, achieve reliable cross-domain resource synchronization, and adaptively adjust video bitrates to solve the problems of poor real-time performance and insufficient network adaptability in cross-domain data synchronization, thereby improving the service stability and resource utilization of video surveillance platforms in complex network environments.

[0004] This disclosure provides a data transmission control method, system, and apparatus for a video surveillance platform.

[0005] Firstly, this disclosure provides a data transmission control method for a video surveillance platform, including: The resource directory version stamps of the directory synchronization request messages in the monitoring platform are filtered by upper and lower level domains to obtain the directory entries stored locally, and the directory entries are encapsulated into a directory synchronization difference package. Based on the link status parameters of the gateway link in the local storage, the directory synchronization difference packet is split and sent to the lower-level domain in the monitoring platform to obtain the reception confirmation fragment of the gateway link. The received confirmation fragments are reassembled into a directory synchronization success signaling, and based on the directory synchronization success signaling, the resource directory of the target monitoring point in the monitoring platform is synchronized to the local platform. Based on the device identifier of the target monitoring point in the platform, probe data is injected into the bearer network of the monitoring platform to obtain the probe data packet of the bearer network; The real-time network quality parameters of the probe data packets are captured, including latency jitter value, consecutive packet loss count, and available bandwidth estimate. Based on a preset encoding strategy library, the continuous packet loss count is subjected to strategy extraction to obtain the target encoding strategy of the encoding strategy library; Based on the target encoding strategy, the encoding parameters of the real-time network quality parameters are renegotiated and sent to the encoding device of the target monitoring point to generate a new video stream for the target monitoring point.

[0006] In a preferred embodiment, the step of filtering the resource directory version stamps of the directory synchronization request messages in the monitoring platform by upper and lower level domains to obtain locally stored directory entries, and encapsulating the directory entries into a directory synchronization difference packet, includes: Parse the directory synchronization request message sent by the lower-level domain in the monitoring platform, and extract the lower-level domain resource directory version stamp from the directory synchronization request message; The version stamp of the lower-level domain resource directory is compared byte by byte with the version stamp of the local upper-level domain resource directory in the monitoring platform according to a preset byte alignment method, and the abnormal byte position of the version stamp of the monitoring platform is marked based on the byte by byte comparison result. Based on the abnormal byte position of the version stamp, the version stamp traversal is performed on the parent domain resource directory tree of the local storage to obtain the delayed directory nodes and monitoring point entries of the local storage, and the delayed directory nodes and monitoring point entries are collected into a set of directory entries to be synchronized. The set of directory entries to be synchronized is serialized and encoded according to the hierarchical structure of the locally stored directory tree to generate a directory synchronization difference package.

[0007] In a preferred embodiment, the step of splitting the directory synchronization difference packet and sending it to the lower-level domain in the monitoring platform based on the link status parameters of the gateway link in the local storage, to obtain the reception acknowledgment fragment of the gateway link, includes: Based on the underlying socket interface of the gateway link in the lower domain, the remaining capacity of the send buffer and the size of the link congestion window of the gateway link are read, and the remaining capacity of the send buffer and the size of the link congestion window are used as the link status parameters of the gateway link in the local storage. When the remaining capacity of the sending buffer is greater than the preset minimum transmission threshold and the link congestion window size is greater than zero, the directory synchronization difference packet is cut into data slices. The data slices are encapsulated into data frames and pushed to the lower-level domain in the monitoring platform; The push data slices of the lower-level domain are aggregated to obtain the reception confirmation slices of the gateway link.

[0008] In a preferred embodiment, the step of reassembling the received confirmation fragments into a directory synchronization success signaling, and synchronizing the resource directory of the target monitoring point in the monitoring platform to the local platform based on the directory synchronization success signaling, includes: Extract the data slice sequence number and slice payload from the received confirmation slice, and concatenate the slice payloads sequentially to reassemble the directory synchronization success signaling. Parse the directory synchronization success signaling to obtain the hash verification value of the directory synchronization difference packet; The hash verification value is compared with the hash value of the directory synchronization difference packet calculated locally. When the comparison result is consistent, the resource directory information in the directory synchronization success signal is written into the resource directory database of the monitoring platform to complete the resource directory synchronization of the target monitoring point.

[0009] In a preferred embodiment, the step of injecting probe data into the bearer network of the monitoring platform based on the device identifier of the target monitoring point in the local platform to obtain probe data packets of the bearer network includes: Extract the device identifier of the target monitoring point from the real-time preview request of the monitoring platform, and query the device registry of the platform based on the device identifier; According to the device registry, obtain the IP address of the encoding device in the target monitoring point; Based on the encoding device, a probe data packet is constructed, the probe data packet containing a source IP address, a destination IP address, a protocol type flag, and a probe sequence number; The probe data packet is injected into the bearer network, and the response data packet returned by the encoding device is captured. The response data packet is used as the probe data packet, and the response data packet contains the probe sequence number and the return timestamp.

[0010] In a preferred embodiment, the real-time network quality parameters of the probe data packets are captured, including latency jitter, consecutive packet loss count, and available bandwidth estimate, among others: Extract the sending timestamp from the probe data packet, extract the receiving timestamp from the response data packet, and use the difference between the receiving timestamp and the sending timestamp as the latency jitter value; Within a preset time window, the total number of probe packets and the number of probe packets that did not receive a response are counted, and the ratio of the number of probe packets that did not receive a response to the total number of probe packets is used as the continuous packet loss count. Based on the time window, the total number of bytes of successfully received data payload of the response data packet is recorded, and the ratio of the total number of bytes of successfully received data payload to the length of the time window is used as an estimated value of available bandwidth. The latency jitter value, the consecutive packet loss count, and the available bandwidth estimate are encapsulated and integrated to obtain the real-time network quality parameters of the probe data packet.

[0011] In a preferred embodiment, the step of extracting strategies from the continuous packet loss count based on a preset coding strategy library to obtain the target coding strategy of the coding strategy library includes: Based on the continuous packet loss count, the latency jitter value, and the available bandwidth estimate, the network quality index of the gateway link is calculated; Based on a preset coding strategy library, the network quality index is numerically compared with the first quality threshold, the second quality threshold, and the third quality threshold of the coding strategy library; When the network quality index is greater than or equal to the first quality threshold, the first coding strategy is extracted from the coding strategy library; When the network quality index is less than the first quality threshold and greater than or equal to the second quality threshold, a second coding strategy is extracted from the coding strategy library. When the network quality index is less than the second quality threshold and greater than or equal to the third quality threshold, the third coding strategy is extracted from the coding strategy library; When the network quality index is less than the third quality threshold, a fourth coding strategy is extracted from the coding strategy library; The formula for calculating the network quality index is as follows:

[0012] in, This refers to the network quality index. This is the first adjustment coefficient for the network quality index. For the consecutive packet loss count, The estimated available bandwidth is... This is the preset maximum link bandwidth capacity. This is the second adjustment coefficient for the network quality index. The delay jitter value is... The preset latency jitter reference value, For the natural constant An exponential function with base 0.

[0013] In a preferred embodiment, the encoding parameters of the real-time network quality parameters are renegotiated based on the target encoding strategy and then sent to the encoding device at the target monitoring point to generate a new video stream for the target monitoring point. The first encoding strategy, the second encoding strategy, the third encoding strategy, and the fourth encoding strategy are integrated into the target encoding strategy; The target encoding strategy is parsed, and the resolution parameter, frame rate parameter, and bit rate parameter are extracted. The resolution parameter, frame rate parameter, and bit rate parameter are then encapsulated into an encoding parameter renegotiation request. The signaling channel of the monitoring platform sends the encoding parameter renegotiation request to the encoding device at the target monitoring point, triggering the re-initialization of the encoding device and obtaining the video frame sequence of the encoding device; The result of matching the bitstream format in the video frame sequence with the target encoding strategy is used as the new video bitstream of the target monitoring point.

[0014] Compared with the prior art, the present invention has the following beneficial effects: 1. This invention achieves efficient and accurate synchronization of cross-domain resource directories by introducing a link-state-aware fragmented reliable synchronization mechanism. The method first parses the directory synchronization request messages sent by the lower-level domain, extracts the resource directory version stamp, and compares it byte-by-byte with the version stamp of the local upper-level domain to filter out the directory entries that need to be synchronized and encapsulate them into a directory synchronization difference packet. Based on this, by monitoring the remaining capacity of the gateway link's sending buffer and the congestion window size, data fragments are pushed only when the link is idle and the queue is not full. Combined with fragmentation confirmation and reassembly mechanisms, the integrity and reliability of the directory synchronization process in a wide area network environment are ensured. This mechanism effectively avoids the bandwidth waste and data inconsistency problems caused by traditional timed full synchronization methods, significantly improves the real-time consistency of resources between multi-level platforms, reduces the failure rate of monitoring point retrieval due to directory asynchrony, and provides a reliable guarantee for the unified management and collaborative scheduling of large-scale video surveillance systems.

[0015] 2. This invention further constructs an adaptive video stream transmission control mechanism based on real-time network quality awareness. By injecting probe data packets into the bearer network, it captures latency jitter values, consecutive packet loss counts, and available bandwidth estimates in real time, and then fuses these multi-dimensional network parameters to calculate a network quality index. Based on the comparison results of this index with preset multi-level quality thresholds, it dynamically matches the corresponding level of encoding strategy from the encoding strategy library, and sends a parameter renegotiation request to the encoding device through the signaling channel, instructing it to interrupt the current encoding process, load the new strategy, and restart the encoding output. This mechanism enables the video bitstream to smoothly adapt to network fluctuations, automatically reducing the bitrate to avoid stuttering when network quality deteriorates, and increasing the bitrate to ensure image quality when network quality recovers. It fundamentally solves the problem of insufficient adaptability of traditional fixed bitrate transmission in complex network environments, significantly improving the smoothness, clarity, and overall user experience of real-time preview services. Attached Figure Description

[0016] The present disclosure will be described in more detail below based on embodiments and with reference to the accompanying drawings: Figure 1 The flowchart of a video surveillance platform data transmission control method according to Embodiment 1 of the present invention is shown. Figure 2 This diagram shows a functional block diagram of a video surveillance platform data transmission control system according to Embodiment 2 of the present invention. Figure 3 The diagram shows the composition of an electronic device that implements a data transmission control device for a video surveillance platform according to Embodiment 3 of the present invention. Detailed Implementation

[0017] To enable those skilled in the art to better understand the technical solutions of this disclosure, and to fully understand and implement the process of how this disclosure applies technical means to solve technical problems and achieve corresponding technical effects, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, not all embodiments. The embodiments of this disclosure and the various features within them can be combined with each other without conflict, and the resulting technical solutions are all within the protection scope of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort should fall within the protection scope of this disclosure.

[0018] It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0019] Example 1

[0020] Figure 1 This is a flowchart illustrating a data transmission control method for a video surveillance platform provided in an embodiment of this disclosure. Figure 1 As shown, a data transmission control method for a video surveillance platform includes: The resource directory version stamps of the directory synchronization request messages in the monitoring platform are filtered by upper and lower level domains to obtain the directory entries stored locally, and the directory entries are encapsulated into a directory synchronization difference package. In this embodiment of the invention, the step of filtering the resource directory version stamps of the directory synchronization request messages in the monitoring platform by upper and lower level domains to obtain locally stored directory entries, and encapsulating the directory entries into a directory synchronization difference packet, includes: Parse the directory synchronization request message sent by the lower-level domain in the monitoring platform, and extract the lower-level domain resource directory version stamp from the directory synchronization request message; The version stamp of the lower-level domain resource directory is compared byte by byte with the version stamp of the local upper-level domain resource directory in the monitoring platform according to a preset byte alignment method, and the abnormal byte position of the version stamp of the monitoring platform is marked based on the byte by byte comparison result. Based on the abnormal byte position of the version stamp, the version stamp traversal is performed on the parent domain resource directory tree of the local storage to obtain the delayed directory nodes and monitoring point entries of the local storage, and the delayed directory nodes and monitoring point entries are collected into a set of directory entries to be synchronized. The set of directory entries to be synchronized is serialized and encoded according to the hierarchical structure of the locally stored directory tree to generate a directory synchronization difference package.

[0021] The local platform within the monitoring platform receives directory synchronization request messages sent by lower-level domains. These request messages are signaling messages proactively initiated by the lower-level domain to obtain the latest resource directory information from the upper-level domain. The local platform parses these messages, accurately extracting the version stamp of the resource directory currently used by the lower-level domain from the message body. This version stamp is a data field identifying the update status of the lower-level domain's resource directory, typically composed of numbers or characters, reflecting the version number or last modification time of the domain's directory data. Through parsing and extraction, the local platform obtains the version status information of the lower-level domain's directory, providing a foundation for subsequent comparisons.

[0022] The platform at this level performs a byte-by-byte comparison between the extracted version stamps of the lower-level domain resource directories and the version stamps of the local upper-level domain resource directories. The version stamp of the local upper-level domain resource directory is a version identifier stored in the platform's database, representing the latest directory status of the upper-level domain. Before the comparison operation, the system aligns the two version stamp data according to a preset byte alignment method, ensuring that each byte position corresponds to the same semantic unit. Then, starting from the first byte, the processor compares the values ​​of each byte sequentially to see if they are the same, and marks the byte positions where the version stamp content is inconsistent based on the comparison results. These positions are recorded as version stamp abnormal byte positions. This marking is used to accurately locate the differences between the two version stamps, thereby determining the range of missing or lagging directory entries in the lower-level domain.

[0023] Based on the marked version stamp anomaly byte positions, the local platform traverses the local parent domain resource directory tree. The resource directory tree is a tree-like data structure that stores monitoring point information according to organizational hierarchy or geographical location. Each node represents a directory or group, and leaf nodes represent specific monitoring point entries. During traversal, the system uses the anomaly byte position as an index to quickly locate directory nodes in the directory tree whose version stamps are later than those of the lower-level domain, along with their subordinate monitoring point entries. These nodes and entries represent the "delayed" data that the lower-level domain has not yet synchronized. The system extracts these delayed directory nodes and monitoring point entries from the directory tree and aggregates them into a temporary dataset called the set of directory entries to be synchronized. This set contains all directory updates that need to be pushed to the lower-level domain.

[0024] This platform performs serialization encoding on the set of directory entries to be synchronized according to the original hierarchical structure of the local parent domain's resource directory tree. Serialization encoding refers to converting the directory tree structure data in memory into a byte stream format suitable for transmission over a network, such as XML, JSON, or a custom binary protocol. During encoding, the system retains detailed information about the parent-child relationships between directory nodes, node attributes, and monitoring points to ensure that the lower-level domain can correctly reconstruct the directory structure after receiving the data. After encoding, the system encapsulates the generated byte stream data into a complete directory synchronization difference packet, which is the final synchronization data unit prepared to be sent to the lower-level domain. Thus, through the above series of specific actions, including parsing and extraction, byte-by-byte comparison, anomaly marking, directory traversal, and aggregation encoding, this platform completes the processing of the directory synchronization request and generates a directory synchronization difference packet carrying incremental update content.

[0025] The beneficial effects are as follows: the above steps extract the version stamp of the lower-level domain resource directory by parsing the directory synchronization request message, and compare it byte by byte with the version stamp of the local upper-level domain resource directory to accurately mark the position of abnormal bytes in the version stamp, thereby achieving precise location of the differences. Based on the position of the abnormal bytes, the upper-level domain resource directory tree is traversed, and only delayed directory nodes and monitoring point entries with version stamps later than those of the lower-level domain are extracted and collected into a set of directory entries to be synchronized, avoiding redundant data transmission caused by full synchronization. Finally, the directory tree is serialized and encoded according to its original hierarchical structure to generate a directory synchronization difference packet, ensuring that the lower-level domain can completely restore the directory hierarchy after receiving it. This mechanism significantly improves the efficiency and accuracy of cross-domain directory synchronization through a differentiated and precise synchronization method, greatly reduces network bandwidth consumption, and effectively solves the directory inconsistency problem caused by traditional timed full synchronization or simple incremental updates, providing a reliable guarantee for unified resource management and real-time collaborative scheduling among multi-level video surveillance platforms.

[0026] Based on the link status parameters of the gateway link in the local storage, the directory synchronization difference packet is split and sent to the lower-level domain in the monitoring platform to obtain the reception confirmation fragment of the gateway link. In this embodiment of the invention, the step of splitting the directory synchronization difference packet and sending it to the lower-level domain in the monitoring platform based on the link status parameters of the gateway link in the local storage, to obtain the reception acknowledgment fragment of the gateway link, includes: Based on the underlying socket interface of the gateway link in the lower domain, the remaining capacity of the send buffer and the size of the link congestion window of the gateway link are read, and the remaining capacity of the send buffer and the size of the link congestion window are used as the link status parameters of the gateway link in the local storage. When the remaining capacity of the sending buffer is greater than the preset minimum transmission threshold and the link congestion window size is greater than zero, the directory synchronization difference packet is cut into data slices. The data slices are encapsulated into data frames and pushed to the lower-level domain in the monitoring platform; The push data slices of the lower-level domain are aggregated to obtain the reception confirmation slices of the gateway link.

[0027] The platform at this level invokes the underlying socket interface of the gateway link with the lower-level domain to perform a read operation. The underlying socket interface is a network programming interface provided by the operating system for directly accessing transport layer protocol control block information. Through this interface, the platform reads the remaining capacity of the gateway link's send buffer. The send buffer is a memory area in the kernel protocol stack used to temporarily store data to be sent; its remaining capacity reflects the amount of data that can be immediately written to the current link. Simultaneously, it reads the link congestion window size. The congestion window is a dynamic parameter used by the TCP protocol to control the sending rate; its size represents the amount of data allowed to be sent without acknowledgment under current network congestion conditions. The platform uses these two real-time values—the remaining capacity of the send buffer and the link congestion window size—as the link status parameters of the gateway link in its local storage.

[0028] The platform compares the remaining capacity of the send buffer with a preset minimum transmission threshold, and simultaneously checks if the link congestion window size is greater than zero. The preset minimum transmission threshold is an empirically configured value used to ensure that the send buffer has sufficient space to accommodate at least one data slice, preventing data fragmentation write failures due to insufficient buffer space. When the remaining capacity of the send buffer is greater than this minimum transmission threshold and the link congestion window size is greater than zero, it indicates that the current gateway link is in a state where it can send data, possessing sufficient buffer space and not being limited by network congestion. Under this condition, the platform performs a segmentation operation on the directory synchronization difference packet to be sent, dividing the difference packet into multiple data slices according to the maximum transmission unit size. The size of each data slice does not exceed the maximum transmission unit allowed by the network link, ensuring that IP fragmentation does not occur during transmission and improving transmission efficiency.

[0029] The platform performs data frame encapsulation on each data slice generated by the segmentation process. Data frame encapsulation involves adding a link-layer header, including the destination MAC address, source MAC address, and type / length fields, to the front of the data slice to form a complete data frame, enabling it to be transmitted over the physical link. After encapsulation, the platform writes the data frame to the transmission buffer via the network interface card (NIC) driver and triggers DMA transfer to push the data frame to the lower-level domain in the monitoring platform. During the push process, the platform records the transmission time and sequence number of each data slice for subsequent confirmation and tracking.

[0030] The platform performs an aggregation operation on the push confirmation information returned by the lower-level domain. After successfully receiving each data slice, the lower-level domain returns a receive confirmation fragment according to the protocol, which carries the sequence number of the confirmed data slice. The platform continuously monitors the gateway link, receives these returned receive confirmation fragments, and organizes and caches the confirmation fragments according to the sequence number. When all receive confirmation fragments corresponding to the sent data slices have been successfully received, the platform aggregates these confirmation fragments into a complete receive confirmation set, which serves as the receive confirmation fragment for the gateway link. This aggregation result signifies that all data slices of the directory synchronization difference packet have been reliably transmitted to the lower-level domain, providing a foundation for subsequent directory synchronization success signaling reassembly. Through the above series of specific actions, including reading link status parameters, conditional segmentation, data frame encapsulation and push, and confirmation fragment aggregation, this level of platform achieves reliable fragmented transmission of the directory synchronization difference packet.

[0031] The beneficial effects are as follows: By calling the underlying socket interface to read the remaining capacity of the gateway link's send buffer and the link congestion window size, accurate perception of the link's real-time transmission capability is achieved, and these two dynamic parameters are used as link status parameters for transmission decisions. By comparing the remaining capacity of the send buffer with a preset minimum transmission threshold and determining whether the congestion window size is greater than zero, data transmission is only initiated when the link has sufficient buffer space and is not congested, avoiding packet loss and retransmission caused by blindly pushing data when the link is congested or the buffer is insufficient. After the transmission conditions are met, the directory synchronization difference packet is divided into multiple data slices according to the maximum transmission unit size, ensuring that each slice does not experience IP fragmentation during transmission, thus improving link utilization. By encapsulating each data slice into data frames and pushing them sequentially to the next-level domain, combined with a fragmentation aggregation mechanism for receiving acknowledgments, reliable tracking of the transmission status of each data slice is achieved. This mechanism, through a series of specific technical means such as link status perception, conditional segmentation, and fragmentation acknowledgment tracking, significantly improves the transmission reliability and efficiency of cross-domain directory synchronization in a wide area network environment, effectively solving the problems of data loss and synchronization failure caused by network fluctuations.

[0032] The received confirmation fragments are reassembled into a directory synchronization success signaling, and based on the directory synchronization success signaling, the resource directory of the target monitoring point in the monitoring platform is synchronized to the local platform. In this embodiment of the invention, the step of reassembling the received confirmation fragments into a directory synchronization success signaling, and synchronizing the resource directory of the target monitoring point in the monitoring platform to the local platform based on the directory synchronization success signaling, includes: Extract the data slice sequence number and slice payload from the received confirmation slice, and concatenate the slice payloads sequentially to reassemble the directory synchronization success signaling. Parse the directory synchronization success signaling to obtain the hash verification value of the directory synchronization difference packet; The hash verification value is compared with the hash value of the directory synchronization difference packet calculated locally. When the comparison result is consistent, the resource directory information in the directory synchronization success signal is written into the resource directory database of the monitoring platform to complete the resource directory synchronization of the target monitoring point.

[0033] This platform performs extraction operations on all previously collected receive acknowledgment fragments. Each receive acknowledgment fragment is an acknowledgment message returned by the lower-level domain after successfully receiving a data slice. It contains the sequence number of the acknowledged data slice and the payload content of that slice. The platform extracts the data slice sequence number and corresponding slice payload from each receive acknowledgment fragment in ascending order of sequence number. The sequence number identifies the order of the data slice in the original directory synchronization difference packet, while the slice payload is the actual data content carried by that data slice. After extraction, the platform concatenates all slice payloads sequentially according to their sequence numbers, appending the end of the first slice's payload to the beginning of the second slice's payload, and so on, until all slice payloads are completely concatenated. This concatenation operation restores the complete data content successfully received by the lower-level domain, i.e., the original form of the directory synchronization difference packet, and reassembles it to obtain the directory synchronization success signaling. This signaling is essentially an acknowledgment message, indicating that the lower-level domain has completely received and verified the directory data synchronized this time.

[0034] This level of platform performs a parsing operation on the reconstructed directory synchronization success signaling. The payload of the directory synchronization success signaling carries a hash checksum of the directory synchronization difference packet calculated and written by the lower-level domain. The hash checksum is a fixed-length digest calculated from the original data using a hash function, used to verify whether the data has been tampered with or corrupted during transmission. The platform reads this hash checksum from a specific field position in the signaling payload to obtain the lower-level domain's integrity verification result for the received data.

[0035] The local platform compares the parsed hash checksum with the hash value of the locally calculated directory synchronization difference packet. Before sending the directory synchronization difference packet, the local platform had already calculated the hash value of the original difference packet using the same hash algorithm and saved it locally. Now, the platform compares the locally saved hash value with the hash checksum returned by the lower-level domain byte by byte to determine if they are completely identical. When the comparison result shows that the two hash values ​​are exactly the same, it means that the directory synchronization difference packet received by the lower-level domain is completely consistent with the original difference packet sent by the local platform, no data corruption or loss occurred during transmission, and the integrity of this directory synchronization is confirmed.

[0036] Assuming the comparison results are consistent, the local platform performs a write operation on the resource directory information carried in the directory synchronization success signaling. In addition to the hash checksum, the payload of the directory synchronization success signaling also includes the complete directory data content confirmed by the lower-level domain, i.e., the serialized data of the set of directory entries to be synchronized. The platform extracts this resource directory information from the signaling payload, including directory nodes, monitoring point entries, and their hierarchical relationships, and then writes this information into the local platform's resource directory database. The resource directory database is a persistent storage system stored on the local platform, used to maintain resource directory data shared by all lower-level domains. After the write operation is completed, the resource directory data for that lower-level domain in the local platform is updated, and the resource directory of the target monitoring point is officially synchronized to the local platform, available for subsequent real-time preview, video playback, and other business calls. Through the above series of specific actions, including extraction and splicing, parsing and reading, hash comparison, and database writing, the local platform completes the reassembly of the received confirmation fragments and the reliable synchronization of the target monitoring point's resource directory.

[0037] The beneficial effects are that the above mechanism, through a series of specific actions such as fragmentation and reassembly, hash verification, and database writing, achieves end-to-end reliability assurance for cross-domain directory synchronization, effectively solves the problem of directory inconsistency caused by data corruption or loss in traditional synchronization methods, and provides a solid data foundation for unified resource management and real-time business calls between multi-level video surveillance platforms.

[0038] Based on the device identifier of the target monitoring point in the platform, probe data is injected into the bearer network of the monitoring platform to obtain the probe data packet of the bearer network; In this embodiment of the invention, based on the device identifier of the target monitoring point in the platform, probe data is injected into the bearer network of the monitoring platform to obtain probe data packets of the bearer network, including: Extract the device identifier of the target monitoring point from the real-time preview request of the monitoring platform, and query the device registry of the platform based on the device identifier; According to the device registry, obtain the IP address of the encoding device in the target monitoring point; Based on the encoding device, a probe data packet is constructed, the probe data packet containing a source IP address, a destination IP address, a protocol type flag, and a probe sequence number; The probe data packet is injected into the bearer network, and the response data packet returned by the encoding device is captured. The response data packet is used as the probe data packet, and the response data packet contains the probe sequence number and the return timestamp.

[0039] This platform performs an extraction operation from the real-time preview request initiated by the superior monitoring platform. A real-time preview request is a signaling message sent by the superior monitoring platform to view the real-time video feed of a specific monitoring point. The message header or payload carries the device identifier of the target monitoring point. The device identifier is a unique identification code assigned to each monitoring point during platform registration, used to distinguish different monitoring resources. This platform parses the real-time preview request, reads and extracts the device identifier of the target monitoring point from the specified field location. After extraction, this platform performs a query operation on its device registry based on the device identifier. The device registry is a data table stored in the platform's database, recording detailed information about all connected coded devices, including device identifier, device name, device type, IP address, port number, access protocol, etc. The platform uses the device identifier as the index key to perform an exact match search in the device registry, locating the record entry corresponding to the target monitoring point.

[0040] This platform retrieves the data from the query results in the device registry. Within the located record, the IP address field stores the network layer address of the encoding device to which the target monitoring point belongs. The encoding device is a video acquisition device connected to the monitoring platform, such as a network camera or video encoder; its IP address is its unique identifier within the network. This platform reads the value of this IP address field from the record to obtain the encoding device's IP address, providing destination address information for constructing subsequent probe data packets.

[0041] This platform constructs probe packets based on the acquired encoding device IP address. A probe packet is a custom protocol message specifically designed for network quality measurement, with a pre-designed format and content. During construction, the platform first fills in its own network interface IP address in the source IP address field as the sender identifier; it fills in the acquired encoding device IP address in the destination IP address field as the target receiver; based on the preset probe protocol type, it fills in the corresponding protocol type field to identify the network layer protocol to which the probe packet belongs; and simultaneously generates a unique and incrementing probe sequence number within the current probe period, filling it in the probe sequence number field for subsequent matching requests and responses. After completing the above field filling, the probe packet construction is complete, containing complete routing information and a unique identifier from the source to the destination.

[0042] The platform at this level will perform an injection operation on the constructed probe data packet. Injection refers to sending the probe data packet through the network interface card (NIC) to the bearer network, causing it to be forwarded to the encoding device along the same transmission path as the real-time preview request. The bearer network is the physical or logical transmission link connecting the platform at this level and the encoding device, including network facilities such as switches, routers, and fiber optic cables. After the probe data packet is injected, it is transmitted to the encoding device along the path. Upon receiving the probe packet, the encoding device identifies it as a probe message based on the protocol type marker and immediately constructs a response data packet to return. The platform at this level continuously monitors the network interface and captures the response data packet returned by the encoding device. This response data packet carries the same probe sequence number as the request packet, as well as the return timestamp filled in by the encoding device in the response. The return timestamp records the time when the encoding device sent the response packet. The platform at this level takes the captured response data packet as the result of this probe, namely the probe data packet of the bearer network, which contains key time information and sequence identifiers of the round-trip transmission.

[0043] The beneficial effects are as follows: the above steps, by extracting device identifiers from real-time preview requests and querying the device registry, achieve precise location of the target encoding device's network position, avoiding the uncertainties and delays caused by manual configuration or broadcast discovery. By constructing probe packets containing source IP addresses, destination IP addresses, protocol type markers, and probe sequence numbers, each probe action is given a unique identifier, ensuring accurate correspondence between subsequent response packets and request packets. Injecting probe packets into the bearer network and capturing the response packets returned by the encoding device ensures that the probe path is completely consistent with the actual service flow path, truly reflecting the network link conditions experienced by the real-time preview request. The probe sequence number and return timestamp contained in the response packets provide accurate raw data for subsequent calculations of latency jitter, packet loss counts, and available bandwidth. This mechanism, through a series of specific actions such as device identifier location, probe packet construction, sequence number marking, and response capture, achieves proactive and accurate measurement of the bearer network link quality, effectively solving the problem that traditional passive monitoring cannot accurately reflect the network conditions of real-time service paths, and providing a reliable network awareness foundation for adaptive adjustment of video bitrates.

[0044] The real-time network quality parameters of the probe data packets are captured, including latency jitter value, consecutive packet loss count, and available bandwidth estimate. In this embodiment of the invention, the real-time network quality parameters of the probe data packets are captured. These real-time network quality parameters include latency jitter, consecutive packet loss count, and available bandwidth estimation. Extract the sending timestamp from the probe data packet, extract the receiving timestamp from the response data packet, and use the difference between the receiving timestamp and the sending timestamp as the latency jitter value; Within a preset time window, the total number of probe packets and the number of probe packets that did not receive a response are counted, and the ratio of the number of probe packets that did not receive a response to the total number of probe packets is used as the continuous packet loss count. Based on the time window, the total number of bytes of successfully received data payload of the response data packet is recorded, and the ratio of the total number of bytes of successfully received data payload to the length of the time window is used as an estimated value of available bandwidth. The latency jitter value, the consecutive packet loss count, and the available bandwidth estimate are encapsulated and integrated to obtain the real-time network quality parameters of the probe data packet.

[0045] This platform performs timestamp extraction on the probe and response data packets acquired during the probe process. When constructing the probe data packet, the platform writes a sending timestamp into its payload, recording the precise time the probe data packet was sent from the platform's network interface card (NIC). The response data packet is returned by the encoding device, and its payload includes a return timestamp filled in by the encoding device, recording the precise time the response data packet was sent from the encoding device's NIC. The platform reads the sending timestamp field from the probe data packet to obtain the sending time value; and reads the return timestamp field from the response data packet to obtain the receiving time value. Then, the platform performs a difference calculation operation, subtracting the sending timestamp value from the receiving timestamp value. The difference is the time taken for the data packet to travel round-trip between the platform and the encoding device, and this difference is used as the latency jitter value. The latency jitter value reflects the delay of data packet transmission in the network and is an important indicator of network stability.

[0046] This platform performs statistical operations within a preset time window. The time window is a pre-defined continuous period, such as a period of time measured in seconds, used to define the observation period for network quality parameters. Within this time window, the platform records the total number of probe packets sent out, i.e., the total number of probe packets; simultaneously, it records the number of probe packets that did not receive a corresponding response packet within a reasonable waiting time, i.e., the number of probe packets that did not receive a response. Failure to receive a response is usually due to network packet loss, congestion, or encoding equipment failure. After the time window ends, the platform performs a ratio calculation operation, dividing the number of probe packets that did not receive a response by the total number of probe packets. The quotient is used as the continuous packet loss count. The continuous packet loss count quantifies the reliability of network transmission numerically; a higher value indicates more severe packet loss and poorer network quality.

[0047] This platform performs data load statistics operations based on the same time window. For each response data packet successfully received within the time window, the platform records the length of its data load, i.e., the size of the successfully received data load. Data load refers to the number of effective data bytes actually carried in the response data packet after removing the network protocol header. The platform sums up the data load sizes of all successfully received response data packets to obtain the total number of bytes of successfully received data load. Subsequently, the platform performs a division operation, dividing the total number of bytes of successfully received data load by the length of the time window, and the quotient is used as the estimated available bandwidth. The estimated available bandwidth reflects the amount of effective data that can be successfully transmitted per unit time under current network conditions and is a key indicator for measuring network transmission capacity.

[0048] This platform performs encapsulation and integration operations on the calculated latency jitter value, consecutive packet loss count, and available bandwidth estimate. Encapsulation and integration refers to combining these three independent values ​​according to a predefined data structure to form a complete dataset. This dataset is used by the platform as a quantitative description of the bearer network quality within this probing period, i.e., the real-time network quality parameters of the probe data packets. This parameter set contains network state information in three dimensions: latency jitter value, consecutive packet loss count, and available bandwidth estimate, providing a comprehensive decision-making basis for subsequent coding strategy selection. Through a series of specific actions, including timestamp extraction, difference calculation, quantity statistics, ratio calculation, byte accumulation, division calculation, and encapsulation and integration, this platform completes the accurate measurement and parameterized expression of the real-time quality of the bearer network.

[0049] The beneficial effects are as follows: By extracting the sending and receiving timestamps from probe and response packets respectively and calculating their difference, accurate latency jitter values ​​are obtained, enabling real-time quantification of network transmission latency characteristics. By counting the total number of probe packets and the number of probe packets that did not receive a response within a preset time window and calculating the ratio, continuous packet loss counts are obtained, accurately reflecting the network's packet loss status and transmission reliability. By recording the total number of bytes of data payload in successfully received response packets and comparing it with the time window length, an estimated available bandwidth value is obtained, intuitively reflecting the network's remaining transmission capacity. The latency jitter value, continuous packet loss count, and available bandwidth estimate are encapsulated and integrated to form multi-dimensional real-time network quality parameters, providing a comprehensive and accurate network status awareness basis for subsequent adaptive adjustments to coding strategies. This mechanism, through a combination of active probing and real-time statistics, overcomes the shortcomings of traditional passive monitoring in quantifying network quality, achieving accurate characterization of the health status of the carrying network and providing reliable data support for dynamic adaptation of video streams.

[0050] Based on a preset encoding strategy library, the continuous packet loss count is subjected to strategy extraction to obtain the target encoding strategy of the encoding strategy library; In this embodiment of the invention, the step of extracting strategies from the continuous packet loss count based on a preset coding strategy library to obtain the target coding strategy of the coding strategy library includes: Based on the continuous packet loss count, the latency jitter value, and the available bandwidth estimate, the network quality index of the gateway link is calculated; Based on a preset coding strategy library, the network quality index is numerically compared with the first quality threshold, the second quality threshold, and the third quality threshold of the coding strategy library; When the network quality index is greater than or equal to the first quality threshold, the first coding strategy is extracted from the coding strategy library; When the network quality index is less than the first quality threshold and greater than or equal to the second quality threshold, a second coding strategy is extracted from the coding strategy library. When the network quality index is less than the second quality threshold and greater than or equal to the third quality threshold, the third coding strategy is extracted from the coding strategy library; When the network quality index is less than the third quality threshold, a fourth coding strategy is extracted from the coding strategy library; The formula for calculating the network quality index is as follows:

[0051] in, This refers to the network quality index. This is the first adjustment coefficient for the network quality index. For the consecutive packet loss count, The estimated available bandwidth is... This is the preset maximum link bandwidth capacity. This is the second adjustment coefficient for the network quality index. The delay jitter value is... The preset latency jitter reference value, For the natural constant An exponential function with base 0.

[0052] This platform uses the captured real-time network quality parameters, including continuous packet loss count, latency jitter, and estimated available bandwidth, as input data to perform a network quality index calculation. The network quality index is a comprehensive quantitative indicator used to integrate multi-dimensional network status parameters into a single value, comprehensively reflecting the overall transmission quality of the current gateway link. This platform calls a pre-configured network quality index calculation module, substituting the continuous packet loss count, latency jitter, and estimated available bandwidth into the index calculation formula. Through multiplication and exponentiation, a numerical result within a preset range is obtained, and this result is used as the network quality index of the gateway link. A larger index value indicates better link quality; a smaller index value indicates worse link quality.

[0053] This platform performs numerical comparison operations based on a pre-set coding strategy library. The coding strategy library is a dataset pre-stored within this platform, containing multiple coding strategy records corresponding to different network quality levels. Each strategy record is associated with a pre-set quality threshold range. The coding strategy library stores a first quality threshold, a second quality threshold, and a third quality threshold. These three thresholds are boundary values ​​arranged from largest to smallest, used to divide the network quality into four level intervals. This platform retrieves the calculated network quality index and first compares it with the first quality threshold to determine if the network quality index is greater than or equal to that threshold. If the network quality index is less than the first quality threshold, it continues to compare it with the second quality threshold; if the network quality index is less than the second quality threshold, it continues to compare it with the third quality threshold. Through this series of step-by-step comparisons, the quality level interval to which the network quality index belongs is determined.

[0054] This platform performs encoding strategy extraction based on the comparison results. When the network quality index is greater than or equal to the first quality threshold, it indicates that the current gateway link quality is at the optimal level. This platform locates the record corresponding to this level in the encoding strategy library and extracts the first encoding strategy stored therein. The first encoding strategy contains a set of encoding parameters suitable for high-quality network environments, such as higher resolution parameters, higher frame rate parameters, and higher bit rate parameters. When the network quality index is less than the first quality threshold but greater than or equal to the second quality threshold, it indicates that the link quality is at the suboptimal level. This platform extracts the second encoding strategy from the encoding strategy library, whose encoding parameters are lower than the first encoding strategy. When the network quality index is less than the second quality threshold but greater than or equal to the third quality threshold, it indicates that the link quality is at the lower-middle level. This platform extracts the third encoding strategy, whose parameters are further reduced to ensure smooth transmission. When the network quality index is less than the third quality threshold, it indicates that the link quality is at the worst level. This platform extracts the fourth encoding strategy, which uses the lowest encoding parameters supported by the encoding device to ensure that basic video transmission can still be maintained under the worst network conditions.

[0055] Finally, the platform extracts the first, second, third, or fourth encoding strategy as the result of this strategy extraction, i.e., the target encoding strategy in the encoding strategy library. This target encoding strategy contains a complete set of encoding parameter configurations that match the current network quality and will be used in subsequent encoding parameter renegotiation operations. Through a series of specific actions, including network quality index calculation, step-by-step threshold comparison, condition judgment, and strategy extraction, the platform completes adaptive selection of encoding strategies based on real-time network quality awareness, providing accurate decision-making basis for the dynamic adjustment of video bitstreams.

[0056] The beneficial effects are as follows: by integrating continuous packet loss counts, latency jitter values, and available bandwidth estimates into a single network quality index, a quantitative representation of the overall status of gateway links is achieved. This overcomes the limitation that a single indicator cannot comprehensively reflect network quality, providing a more accurate and comprehensive basis for the selection of coding strategies. By presetting a first, second, and third quality threshold and comparing the network quality index with these three thresholds step by step, network quality is divided into four levels from high to low, achieving a fine-grained classification of network conditions and avoiding frequent oscillations and misjudgments caused by switching a single threshold. Based on the comparison results, the first, second, third, and fourth coding strategies corresponding to each quality level are extracted from the coding strategy library, ensuring that the adjustment of coding parameters is precisely matched with real-time network quality. When network quality is excellent, a high bitrate and high resolution strategy is used to ensure image quality, while a smooth switch to a low bitrate strategy is made when network quality deteriorates to ensure smoothness. This mechanism, through a series of specific actions such as comprehensive index calculation, multi-level threshold comparison, and graded strategy extraction, achieves adaptive, fine-grained, and smooth adjustment of the video bitstream to network fluctuations. Based on the target encoding strategy, the encoding parameters of the real-time network quality parameters are renegotiated and sent to the encoding device of the target monitoring point to generate a new video stream for the target monitoring point.

[0057] In this embodiment of the invention, the encoding parameters of the real-time network quality parameters are renegotiated based on the target encoding strategy and then sent to the encoding device at the target monitoring point to generate a new video stream for the target monitoring point. The first encoding strategy, the second encoding strategy, the third encoding strategy, and the fourth encoding strategy are integrated into the target encoding strategy; The target encoding strategy is parsed, and the resolution parameter, frame rate parameter, and bit rate parameter are extracted. The resolution parameter, frame rate parameter, and bit rate parameter are then encapsulated into an encoding parameter renegotiation request. The signaling channel of the monitoring platform sends the encoding parameter renegotiation request to the encoding device at the target monitoring point, triggering the re-initialization of the encoding device and obtaining the video frame sequence of the encoding device; The result of matching the bitstream format in the video frame sequence with the target encoding strategy is used as the new video bitstream of the target monitoring point.

[0058] This platform integrates the first, second, third, and fourth encoding strategies previously extracted from the encoding strategy library. During the comparison between the network quality index and the quality threshold, only one encoding strategy is extracted at a time as the result matching the current network quality. Therefore, this integration operation essentially determines the single effective strategy obtained in this strategy extraction stage as the final target encoding strategy. This platform retrieves this strategy from the temporary storage area as the standard basis for subsequent processing, i.e., the target encoding strategy. This strategy contains a complete set of encoding parameter configurations that match the current gateway link quality.

[0059] This platform performs a parsing operation on the determined target encoding strategy. The target encoding strategy is stored in the encoding strategy library as structured data, containing multiple fields, each corresponding to different encoding parameters. The platform uses a parsing program to read and extract the resolution, frame rate, and bitrate parameters one by one from the strategy data structure. The resolution parameter specifies the width and height of the video image in pixels, determining the image's detail; the frame rate parameter specifies the number of video frames transmitted per second, determining the video's smoothness; and the bitrate parameter specifies the data rate of the video encoding output, determining the bandwidth used by the video. These three parameters are the core control parameters for the encoding device to perform video compression encoding, collectively determining the image quality and bandwidth usage of the output video stream.

[0060] This platform performs encapsulation operations on the extracted resolution, frame rate, and bitrate parameters. Encapsulation refers to combining these three parameters into a complete signaling message according to a protocol format that the encoding device can recognize and parse. This platform then fills these parameters into the predetermined field positions of the encoding parameter renegotiation request and adds necessary protocol identifiers and session control information to the message header, forming a complete encoding parameter renegotiation request. This request is specifically used to notify the encoding device to change its current encoding parameter configuration.

[0061] This platform sends the encapsulated encoding parameter renegotiation request via the signaling channel of the monitoring platform. The signaling channel is a pre-established logical link between the monitoring platform and the encoding device for transmitting control commands. It is independent of the media channel for video data and typically uses a reliable transmission protocol to ensure accurate delivery of control commands. This platform pushes the request to the encoding device at the target monitoring point via the signaling channel. Upon receiving the request, the encoding device performs a re-initialization operation. Re-initialization means that the encoding device temporarily interrupts the current video acquisition and encoding process, releases the occupied encoder resources, reconfigures the encoder registers according to the resolution, frame rate, and bit rate parameters carried in the request, and then restarts the video acquisition and encoding threads. During this process, the encoding device generates a series of consecutive video frames encoded according to the new parameters, forming the video frame sequence of the encoding device.

[0062] This platform receives video frame sequences output by the encoding device through the media channel and performs a matching judgment operation. Matching judgment involves comparing the bitstream format of the received video frame sequence with the parameters specified in the previously sent target encoding strategy to confirm whether the video frame resolution, frame rate, and bitrate meet expectations. Once the bitstream format is confirmed to match the target encoding strategy, this platform uses the video frame sequence as the new video bitstream for the target monitoring point. This new video bitstream, generated after network adaptive adjustment and adapted to the current gateway link quality, will be forwarded to the upper-level monitoring platform for decoding and playback.

[0063] The beneficial effects are as follows: By identifying the first to fourth encoding strategies that match the current network quality as the target encoding strategy, the above steps achieve precise and unique selection of encoding parameters, avoiding problems such as multi-strategy conflicts or ambiguous selections. By parsing the target encoding strategy and extracting resolution, frame rate, and bitrate parameters, the specific control dimensions that the encoding device needs to adjust are clarified, providing clear instructions for subsequent parameter renegotiation. Encapsulating these three core parameters into an encoding parameter renegotiation request and sending it to the encoding device through a signaling channel independent of media transmission ensures reliable transmission of control instructions and avoids instruction loss or delay caused by bandwidth competition with video data. By triggering the encoding device to perform a re-initialization operation, interrupting the current encoding process and restarting according to the new parameters, real-time, online adjustment of encoding parameters is achieved without device restart or manual intervention. Finally, the portion of the received video frame sequence that matches the target encoding strategy is used as the new video bitstream, ensuring that the quality of the output bitstream is accurately adapted to the network conditions.

[0064] Example 2

[0065] like Figure 2As shown in the figure, this embodiment also provides a functional block diagram of a video surveillance platform data transmission control system.

[0066] The video surveillance platform data transmission control system 100 described in this embodiment can be installed in an electronic device. Depending on the functions implemented, the video surveillance platform data transmission control system 100 may include a directory synchronization difference encapsulation module 101, a fragmented reliable transmission module 102, a directory synchronization confirmation and update module 103, a network detection data injection module 104, a network quality parameter capture module 105, a coding strategy hierarchical extraction module 106, and a coding parameter renegotiation and bitstream generation module 107. The module described in this invention can also be called a unit, which refers to a series of computer program segments that can be executed by the processor of an electronic device and can perform a fixed function, stored in the memory of the electronic device.

[0067] In this embodiment, the functions of each module / unit are as follows: The directory synchronization difference encapsulation module 101 is used to filter the resource directory version stamp of the directory synchronization request message in the monitoring platform by upper and lower level domains, obtain the directory entries stored locally, and encapsulate the directory entries into a directory synchronization difference package. The fragmented reliable transmission module 102 is used to split the directory synchronization difference packet and send it to the lower-level domain in the monitoring platform based on the link status parameters of the gateway link in the local storage, so as to obtain the reception confirmation fragment of the gateway link. The directory synchronization confirmation and update module 103 is used to reassemble the received confirmation fragments into a directory synchronization success signaling, and based on the directory synchronization success signaling, synchronize the resource directory of the target monitoring point in the monitoring platform to the local platform. The network detection data injection module 104 is used to inject detection data into the bearer network of the monitoring platform based on the device identifier of the target monitoring point in the local platform, so as to obtain the detection data packet of the bearer network. The network quality parameter capture module 105 is used to capture the real-time network quality parameters of the probe data packet. The real-time network quality parameters include latency jitter value, consecutive packet loss count and available bandwidth estimate. The encoding strategy hierarchical extraction module 106 is used to extract strategies from the continuous packet loss count based on a preset encoding strategy library to obtain the target encoding strategy of the encoding strategy library. The encoding parameter renegotiation and bitstream generation module 107 is used to renegotiate the encoding parameters of the real-time network quality parameters based on the target encoding strategy and send them to the encoding device of the target monitoring point to generate a new video bitstream for the target monitoring point.

[0068] In detail, each module in the video surveillance platform data transmission control system 100 described in this embodiment of the invention uses the same technical means as the video surveillance platform data transmission control method described in Embodiments 1 and 2, and can produce the same technical effects, which will not be repeated here.

[0069] Example 3

[0070] like Figure 3 As shown, this embodiment also provides a computer device. The electronic device may include a processor 10, a memory 11, a communication bus 12, and a communication interface 13. It may also include a computer program stored in the memory 11 and capable of running on the processor 10, such as a video surveillance platform data transmission control program.

[0071] In some embodiments, the processor 10 may be composed of integrated circuits, such as a single packaged integrated circuit or multiple integrated circuits with the same or different functions, including combinations of one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and various control chips. The processor 10 is the control unit of the electronic device, connecting various components of the entire electronic device through various interfaces and lines. It executes programs or modules stored in the memory 11 (e.g., executing data transmission control programs for video surveillance platforms) and calls data stored in the memory 11 to perform various functions of the electronic device and process data.

[0072] The memory 11 includes at least one type of medium, including flash memory, portable hard drive, multimedia card, card-type memory (e.g., SD or DX memory), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 11 can be an internal storage unit of an electronic device, such as a portable hard drive. In other embodiments, the memory 11 can be an external storage device of the electronic device, such as a plug-in portable hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc. Furthermore, the memory 11 can include both internal and external storage units of the electronic device. The memory 11 can be used not only to store application software and various types of data installed on the electronic device, such as the code of a video surveillance platform data transmission control program, but also to temporarily store data that has been output or will be output.

[0073] The communication bus 12 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into an address bus, a data bus, a control bus, etc. The bus is configured to enable communication between the memory 11 and at least one processor 10, etc.

[0074] The communication interface 13 is used for communication between the aforementioned electronic device and other electronic devices, including a network interface and a user interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a Wi-Fi interface, Bluetooth interface, etc.), typically used to establish communication connections between the electronic device and other electronic devices. The user interface may be a display, an input unit (such as a keyboard), or optionally, a standard wired or wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen, etc. The display may also be appropriately referred to as a screen or display unit, used to display information processed in the electronic device and to display a visual user interface.

[0075] The figure only shows an electronic device with components. Those skilled in the art will understand that the structure shown in the figure does not constitute a limitation on the electronic device and may include fewer or more components than shown, or combine certain components, or have different component arrangements.

[0076] For example, although not shown, the electronic device may also include a power supply (such as a battery) to power the various components. Preferably, the power supply can be logically connected to the at least one processor 10 through a power management device, thereby enabling functions such as charging management, discharging management, and power consumption management. The power supply may also include one or more DC or AC power supplies, recharging devices, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components. The electronic device may also include various sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be described in detail here.

[0077] It should be understood that the embodiments described are for illustrative purposes only and are not limited to this structure in the scope of the patent application.

[0078] The video surveillance platform data transmission control program stored in the memory 11 of the electronic device is a combination of multiple instructions. When run in the processor 10, it can achieve the following: The resource directory version stamps of the directory synchronization request messages in the monitoring platform are filtered by upper and lower level domains to obtain the directory entries stored locally, and the directory entries are encapsulated into a directory synchronization difference package. Based on the link status parameters of the gateway link in the local storage, the directory synchronization difference packet is split and sent to the lower-level domain in the monitoring platform to obtain the reception confirmation fragment of the gateway link. The received confirmation fragments are reassembled into a directory synchronization success signaling, and based on the directory synchronization success signaling, the resource directory of the target monitoring point in the monitoring platform is synchronized to the local platform. Based on the device identifier of the target monitoring point in the platform, probe data is injected into the bearer network of the monitoring platform to obtain the probe data packet of the bearer network; The real-time network quality parameters of the probe data packets are captured, including latency jitter value, consecutive packet loss count, and available bandwidth estimate. Based on a preset encoding strategy library, the continuous packet loss count is subjected to strategy extraction to obtain the target encoding strategy of the encoding strategy library; Based on the target encoding strategy, the encoding parameters of the real-time network quality parameters are renegotiated and sent to the encoding device of the target monitoring point to generate a new video stream for the target monitoring point.

[0079] Specifically, the specific implementation method of the processor 10 for the above instructions can be referred to the description of the relevant steps in the corresponding embodiment of the accompanying drawings, and will not be repeated here.

[0080] Furthermore, if the modules / units integrated into the electronic device are implemented as software functional units and sold or used as independent products, they can be stored in a medium. The medium can be volatile or non-volatile. For example, the medium may include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, or a read-only memory (ROM).

[0081] In the several embodiments provided by this invention, it should be understood that the disclosed electronic devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and other division methods may be used in actual implementation.

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

[0083] Furthermore, the functional modules in the various embodiments of the present invention 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 in the form of hardware plus software functional modules.

[0084] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0085] The embodiments of this application can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence (AI) refers to the theories, methods, technologies, and application systems that use digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0086] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A data transmission control method for a video surveillance platform, characterized in that, The method includes: The resource directory version stamps of the directory synchronization request messages in the monitoring platform are filtered by upper and lower level domains to obtain the directory entries stored locally, and the directory entries are encapsulated into a directory synchronization difference package. Based on the link status parameters of the gateway link in the local storage, the directory synchronization difference packet is split and sent to the lower-level domain in the monitoring platform to obtain the reception confirmation fragment of the gateway link. The received confirmation fragments are reassembled into a directory synchronization success signaling, and based on the directory synchronization success signaling, the resource directory of the target monitoring point in the monitoring platform is synchronized to the local platform. Based on the device identifier of the target monitoring point in the platform, probe data is injected into the bearer network of the monitoring platform to obtain the probe data packet of the bearer network; The real-time network quality parameters of the probe data packets are captured, including latency jitter value, consecutive packet loss count, and available bandwidth estimate. Based on a preset encoding strategy library, the continuous packet loss count is subjected to strategy extraction to obtain the target encoding strategy of the encoding strategy library; Based on the target encoding strategy, the encoding parameters of the real-time network quality parameters are renegotiated and sent to the encoding device of the target monitoring point to generate a new video stream for the target monitoring point.

2. The video surveillance platform data transmission control method as described in claim 1, characterized in that, The process involves filtering the resource directory version stamps of directory synchronization request messages in the monitoring platform by upper and lower level domains to obtain locally stored directory entries, and then encapsulating these directory entries into a directory synchronization difference packet, including: Parse the directory synchronization request message sent by the lower-level domain in the monitoring platform, and extract the lower-level domain resource directory version stamp from the directory synchronization request message; The version stamp of the lower-level domain resource directory is compared byte by byte with the version stamp of the local upper-level domain resource directory in the monitoring platform according to a preset byte alignment method, and the abnormal byte position of the version stamp of the monitoring platform is marked based on the byte by byte comparison result. Based on the abnormal byte position of the version stamp, the version stamp traversal is performed on the parent domain resource directory tree of the local storage to obtain the delayed directory nodes and monitoring point entries of the local storage, and the delayed directory nodes and monitoring point entries are collected into a set of directory entries to be synchronized. The set of directory entries to be synchronized is serialized and encoded according to the hierarchical structure of the locally stored directory tree to generate a directory synchronization difference package.

3. The video surveillance platform data transmission control method as described in claim 1, characterized in that, The step of splitting the directory synchronization difference packet based on the link status parameters of the gateway link in the local storage and sending it to the lower-level domain in the monitoring platform to obtain the reception acknowledgment fragment of the gateway link includes: Based on the underlying socket interface of the gateway link in the lower domain, the remaining capacity of the send buffer and the size of the link congestion window of the gateway link are read, and the remaining capacity of the send buffer and the size of the link congestion window are used as the link status parameters of the gateway link in the local storage. When the remaining capacity of the sending buffer is greater than the preset minimum transmission threshold and the link congestion window size is greater than zero, the directory synchronization difference packet is cut into data slices. The data slices are encapsulated into data frames and pushed to the lower-level domain in the monitoring platform; The push data slices of the lower-level domain are aggregated to obtain the reception confirmation slices of the gateway link.

4. The video surveillance platform data transmission control method as described in claim 1, characterized in that, The step of reassembling the received confirmation fragments into a directory synchronization success signaling, and synchronizing the resource directory of the target monitoring point in the monitoring platform to the local platform based on the directory synchronization success signaling, includes: Extract the data slice sequence number and slice payload from the received confirmation slice, and concatenate the slice payloads sequentially to reassemble the directory synchronization success signaling. Parse the directory synchronization success signaling to obtain the hash verification value of the directory synchronization difference packet; The hash verification value is compared with the hash value of the directory synchronization difference packet calculated locally. When the comparison result is consistent, the resource directory information in the directory synchronization success signal is written into the resource directory database of the monitoring platform to complete the resource directory synchronization of the target monitoring point.

5. The video surveillance platform data transmission control method as described in claim 1, characterized in that, The method involves injecting probe data into the bearer network of the monitoring platform based on the device identifier of the target monitoring point in the platform, thereby obtaining probe data packets for the bearer network, including: Extract the device identifier of the target monitoring point from the real-time preview request of the monitoring platform, and query the device registry of the platform based on the device identifier; According to the device registry, obtain the IP address of the encoding device in the target monitoring point; Based on the encoding device, a probe data packet is constructed, the probe data packet containing a source IP address, a destination IP address, a protocol type flag, and a probe sequence number; The probe data packet is injected into the bearer network, and the response data packet returned by the encoding device is captured. The response data packet is used as the probe data packet, and the response data packet contains the probe sequence number and the return timestamp.

6. The video surveillance platform data transmission control method as described in claim 5, characterized in that, The real-time network quality parameters of the captured probe data packets include latency jitter, consecutive packet loss count, and available bandwidth estimation, including: Extract the sending timestamp from the probe data packet, extract the receiving timestamp from the response data packet, and use the difference between the receiving timestamp and the sending timestamp as the latency jitter value; Within a preset time window, the total number of probe packets and the number of probe packets that did not receive a response are counted, and the ratio of the number of probe packets that did not receive a response to the total number of probe packets is used as the continuous packet loss count. Based on the time window, the total number of bytes of successfully received data payload of the response data packet is recorded, and the ratio of the total number of bytes of successfully received data payload to the length of the time window is used as an estimated value of available bandwidth. The latency jitter value, the consecutive packet loss count, and the available bandwidth estimate are encapsulated and integrated to obtain the real-time network quality parameters of the probe data packet.

7. The video surveillance platform data transmission control method as described in claim 1, characterized in that, The method involves extracting strategies from the continuous packet loss count based on a preset encoding strategy library to obtain the target encoding strategy of the encoding strategy library, including: Based on the continuous packet loss count, the latency jitter value, and the available bandwidth estimate, the network quality index of the gateway link is calculated; Based on a preset coding strategy library, the network quality index is numerically compared with the first quality threshold, the second quality threshold, and the third quality threshold of the coding strategy library; When the network quality index is greater than or equal to the first quality threshold, the first coding strategy is extracted from the coding strategy library; When the network quality index is less than the first quality threshold and greater than or equal to the second quality threshold, a second coding strategy is extracted from the coding strategy library; When the network quality index is less than the second quality threshold and greater than or equal to the third quality threshold, the third coding strategy is extracted from the coding strategy library; When the network quality index is less than the third quality threshold, a fourth coding strategy is extracted from the coding strategy library; The formula for calculating the network quality index is as follows: in, This refers to the network quality index. This is the first adjustment coefficient for the network quality index. For the consecutive packet loss count, The estimated available bandwidth is... This is the preset maximum link bandwidth capacity. This is the second adjustment coefficient for the network quality index. The delay jitter value is... The preset latency jitter reference value, For the natural constant An exponential function with base 0.

8. The video surveillance platform data transmission control method as described in claim 7, characterized in that, Based on the target encoding strategy, the encoding parameters of the real-time network quality parameters are renegotiated and then sent to the encoding device at the target monitoring point to generate a new video stream for the target monitoring point. The first encoding strategy, the second encoding strategy, the third encoding strategy, and the fourth encoding strategy are integrated into the target encoding strategy; The target encoding strategy is parsed, and the resolution parameter, frame rate parameter, and bit rate parameter are extracted. The resolution parameter, frame rate parameter, and bit rate parameter are then encapsulated into an encoding parameter renegotiation request. The signaling channel of the monitoring platform sends the encoding parameter renegotiation request to the encoding device at the target monitoring point, triggering the re-initialization of the encoding device and obtaining the video frame sequence of the encoding device; The result of matching the bitstream format in the video frame sequence with the target encoding strategy is used as the new video bitstream of the target monitoring point.

9. A data transmission control system for a video surveillance platform, characterized in that, The system for implementing the video surveillance platform data transmission control method according to claim 1 includes: The directory synchronization difference encapsulation module is used to filter the resource directory version stamps of the directory synchronization request messages in the monitoring platform by upper and lower level domains, obtain the directory entries stored locally, and encapsulate the directory entries into a directory synchronization difference package. The fragmented reliable transmission module is used to split the directory synchronization difference packet based on the link status parameters of the gateway link in the local storage and send it to the lower-level domain in the monitoring platform to obtain the reception confirmation fragment of the gateway link. The directory synchronization confirmation and update module is used to reassemble the received confirmation fragments into a directory synchronization success signal, and based on the directory synchronization success signal, synchronize the resource directory of the target monitoring point in the monitoring platform to the local platform. The network detection data injection module is used to inject detection data into the bearer network of the monitoring platform based on the device identifier of the target monitoring point in the platform, and obtain the detection data packet of the bearer network. The network quality parameter capture module is used to capture the real-time network quality parameters of the probe data packets. The real-time network quality parameters include latency jitter value, consecutive packet loss count, and available bandwidth estimate. The coding strategy hierarchical extraction module is used to extract the strategy from the continuous packet loss count based on a preset coding strategy library to obtain the target coding strategy of the coding strategy library. The encoding parameter renegotiation and bitstream generation module is used to renegotiate the encoding parameters of the real-time network quality parameters based on the target encoding strategy and send them to the encoding device of the target monitoring point to generate a new video bitstream for the target monitoring point.

10. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the method according to any one of claims 1 to 8.

Images