Edge-side multi-protocol adaptive video device access method and apparatus

Abstract

This invention belongs to the field of multi-protocol access, and provides a method and apparatus for edge-side multi-protocol adaptive video device access. The method includes dynamically loading matching protocol plugins from a protocol plugin repository; dynamically adjusting the execution order of all protocol plugins in the repository based on the activity level, system resource utilization efficiency, and protocol importance of each network video device; registering the corresponding protocol plugins to a unified abstraction layer according to the dynamically adjusted execution order, and performing network video device query, authentication, and bitstream address acquisition operations for each registered protocol plugin; and re-determining the activity level, system resource utilization efficiency, and protocol importance of each network video device based on the execution results of each protocol plugin, and dynamically readjusting the execution order of all protocol plugins in the repository again. This enables pluggable, loosely coupled, and dynamically loadable multi-protocol adaptive access.

Description

Technical Field

[0001] This invention belongs to the field of multi-protocol access, and particularly relates to a method and apparatus for edge-side multi-protocol adaptive video device access. Background Technology

[0002] The statements in this section are merely background information related to the present invention and do not necessarily constitute prior art.

[0003] Existing power grid visualization and maintenance systems require access to network cameras, NVRs, and other devices from different manufacturers and models. Due to significant differences in proprietary protocols among manufacturers, the central platform often adopts a "one protocol, one set of adaptation services" approach, resulting in high development and maintenance costs; heavy load on the central platform; and difficulty in expansion. In edge-side scenarios (substations, distribution rooms) with limited computing resources (CPU < 1GHz, memory < 512MB), it is impossible to directly run multiple vendor SDKs. Existing multi-protocol adaptive access methods suffer from poor compatibility, leading to system instability, complex and inefficient management, and poor scalability, making it difficult to adapt to new protocols, especially in edge computing (such as substations, distribution rooms) and IoT scenarios. Summary of the Invention

[0004] To address the technical problems existing in the background art, the present invention provides an edge-side multi-protocol adaptive video device access method and apparatus, which can realize plug-in, loosely coupled, and dynamically loaded multi-protocol adaptive access.

[0005] To achieve the above objectives, the present invention adopts the following technical solution: The first aspect of the present invention provides a method for edge-side multi-protocol adaptive video device access.

[0006] A method for edge-side multi-protocol adaptive video device access, comprising: The first packet sent by each network video device upon going online is matched for features, and the protocol type of the corresponding network video device is automatically identified. Then, the matching protocol plugin is dynamically loaded from the protocol plugin repository. The execution order of all protocol plugins in the protocol plugin repository is dynamically adjusted based on the activity level of each network video device, system resource utilization efficiency, and protocol importance. According to the dynamically adjusted execution order of protocol plugins, the corresponding protocol plugins are registered to the unified abstraction layer and the network video device query, authentication and bitstream address acquisition operations of each registered protocol plugin are executed. The acquired bitstream information is reported to the central platform in a unified data format. At the same time, the activity level of each network video device, system resource utilization efficiency, and protocol importance are re-determined based on the execution results of each protocol plugin. The execution order of all protocol plugins in the protocol plugin repository is then dynamically adjusted.

[0007] As one implementation method, a protocol feature identifier is used to extract SIP header fields, SDK handshake features, and private message fingerprints from the first packet when each network video device comes online. Then, the protocol type of each network video device is determined by matching these first packet features.

[0008] As one implementation method, the activity level, system resource utilization efficiency, and protocol importance of each network video device are normalized, and then the current priority of each protocol plugin in the protocol plugin repository is calculated by weighted summation, thereby dynamically adjusting the execution order of all protocol plugins in the protocol plugin repository.

[0009] In one implementation, the activity level of a network video device is determined by its online status, data transmission frequency, and response time.

[0010] As one implementation method, system resource utilization efficiency is determined by CPU utilization, memory utilization, and network bandwidth utilization.

[0011] In one implementation, the importance of the protocol is determined by the protocol plugin tasks, which include emergency tasks, regular tasks, and background tasks, with their corresponding protocol importance decreasing in that order.

[0012] As one implementation method, if the execution of the protocol plugin fails, it will automatically retry and adjust the execution strategy according to the reason for the failure.

[0013] A second aspect of the present invention provides an edge-side multi-protocol adaptive video device access device.

[0014] An edge-side multi-protocol adaptive video device access device includes: The dynamic loading module is used to perform feature matching on the first packet when each network video device comes online, automatically identify the protocol type of the corresponding network video device, and then dynamically load the matching protocol plugin from the protocol plugin repository. The dynamic scheduling module is used to dynamically adjust the execution order of all protocol plugins in the protocol plugin repository based on the activity level of each network video device, system resource utilization efficiency, and protocol importance. The plugin execution module is used to register the corresponding protocol plugins to the unified abstraction layer according to the dynamically adjusted protocol plugin execution order, and to perform network video device query, authentication and bitstream address acquisition operations for each registered protocol plugin. The data reporting module is used to report the acquired bitstream information to the central platform in a unified data format. At the same time, it redetermines the activity level of each network video device, system resource utilization efficiency, and protocol importance based on the execution results of each protocol plugin, and dynamically adjusts the execution order of all protocol plugins in the protocol plugin repository.

[0015] A third aspect of the present invention provides a computer-readable storage medium.

[0016] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the edge-side multi-protocol adaptive video device access method as described above.

[0017] A fourth aspect of the present invention provides a computer device.

[0018] A computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the edge-side multi-protocol adaptive video device access method as described above.

[0019] Compared with the prior art, the beneficial effects of the present invention are: This invention automatically identifies the protocol type of the network video device based on the first packet received when the device comes online. It then dynamically loads matching protocol plugins from a protocol plugin repository. Furthermore, based on the activity level of each network video device, system resource utilization efficiency, and protocol importance, it dynamically adjusts the execution order of all protocol plugins in the repository. This process registers and executes the plugins, ensuring that in resource-constrained edge environments, the system can intelligently allocate resources and optimize execution efficiency while guaranteeing the real-time performance and stability of critical services. Through continuous monitoring, it also dynamically readjusts the execution order of all protocol plugins in the repository, achieving pluggable, loosely coupled, dynamically loadable multi-protocol adaptive access and maintaining high system efficiency under different workloads.

[0020] Advantages of additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0021] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an improper limitation of the invention.

[0022] Figure 1 This is a flowchart of the edge-side multi-protocol adaptive video device access method according to an embodiment of the present invention; Figure 2This is a schematic diagram of the edge-side multi-protocol adaptive video device access device according to an embodiment of the present invention; Figure 3 This is a schematic diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0023] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0024] It should be noted that the following detailed description is illustrative and intended to provide further explanation of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0025] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0026] Figure 1 A schematic diagram of the edge-side multi-protocol adaptive video device access method according to an embodiment of the present invention is provided. Figure 1 The edge-side multi-protocol adaptive video device access method of this embodiment may include the following steps S101 to S104.

[0027] The specific implementation process of steps S101 to S104 is as follows: Step S101: Perform feature matching on the first packet of each network video device when it comes online, automatically identify the protocol type of the corresponding network video device, and then dynamically load the matching protocol plugin in the protocol plugin repository.

[0028] In practice, the protocol signature identifier listens to network ports (UDP 5060, 8000, TCP 37777) and captures the first packet data when a network video device comes online.

[0029] By using a protocol signature identifier, SIP header fields, SDK handshake features, and private message fingerprints are extracted from the first packet sent when each network video device comes online. These first packet features are then used to match and determine the protocol type of each network video device (e.g., Hikvision proprietary V3.2, GB / T28181, etc.). This improves the accuracy of protocol type identification for network video devices.

[0030] Different network video devices are pre-configured with corresponding protocol types; Different protocol types have different first packet characteristics, such as SIP header fields, SDK handshake features, and private message fingerprints. Therefore, the protocol type of each network video device can be determined by matching the first packet characteristics such as SIP header fields, SDK handshake features, and private message fingerprints.

[0031] It should be noted here that the protocol feature recognizer can be implemented using an existing neural network architecture. Its training samples are the first packet data when the network video device with the labeled protocol type comes online. By extracting the data SIP header field, SDK handshake features and private message fingerprints from the first packet when the network video device comes online, the parameters of the protocol feature recognizer are trained, and the mapping relationship between the data SIP header field, SDK handshake features and private message fingerprints and the protocol type is constructed.

[0032] In other embodiments, those skilled in the art may also use feature similarity comparison to match and identify the protocol type of the corresponding network video device, which will not be described in detail here.

[0033] Based on the identified protocol type, the corresponding shared library (SO / DLL) is loaded from the protocol plugin repository. This repository stores lightweight protocol parsing plugins, achieving low resource consumption and high scalability through a dynamic loading mechanism. The protocol plugin repository solves the problems of high integration costs and heavy load on the central platform in existing methods, making it particularly suitable for resource-constrained scenarios such as substations and power distribution rooms.

[0034] The protocol plugin in this embodiment of the invention only implements three callback functions: "device discovery, authentication, and bitstream address acquisition," which reduces system memory usage.

[0035] Step S102: Dynamically adjust the execution order of all protocol plugins in the protocol plugin repository based on the activity level of each network video device, system resource utilization efficiency, and protocol importance.

[0036] In one or more embodiments, the activity level, system resource utilization efficiency, and protocol importance of each network video device are normalized, and then the current priority of each protocol plugin in the protocol plugin repository is calculated by weighted summation, thereby dynamically adjusting the execution order of all protocol plugins in the protocol plugin repository.

[0037] The activity level of network video devices is determined by their online status, data transmission frequency, and response time. The activity level of network video devices can be calculated using the following formula: ; in, Activity level; The value is 0 or 1, which indicates the online status. A value of 0 indicates offline and a value of 1 indicates online. For data transmission frequency; For response time; , and These are weighting coefficients; the sum of these three factors equals 1, and their values ​​can be determined based on the specific circumstances. For example... , , .

[0038] The weight of online status indicates that whether a device is online is a key factor in determining its activity level; the weight of data transmission frequency reflects the workload of the device; and the weight of response time measures the real-time performance of the device.

[0039] Plugins for high-activity devices (such as live surveillance cameras) are given higher priority to ensure timely processing of critical data; while plugins for low-activity devices (such as occasionally used storage devices) are given lower priority to reduce resource consumption.

[0040] It should be noted that in other embodiments, the model can also be trained using network video device operating status data (including online status, data transmission frequency, and response time) that marks the activity of network video devices, thereby constructing a mapping relationship between the activity of network video devices and the online status, data transmission frequency, and response time.

[0041] In one or more embodiments, system resource utilization efficiency is determined by CPU utilization, memory utilization, and network bandwidth utilization.

[0042] CPU utilization refers to the current percentage of CPU usage (e.g., 75%). Memory utilization rate refers to the percentage of total memory currently in use (e.g., 80%). Network bandwidth utilization refers to the percentage of current network throughput relative to the maximum available bandwidth (e.g., 60%).

[0043] System resource utilization efficiency can be calculated using the following formula: ; in, To improve system resource utilization efficiency; CPU utilization; Memory usage; Network bandwidth utilization; , and These are weighting coefficients; the sum of these three factors equals 1, and their values ​​can be determined based on the specific circumstances. For example... , , .

[0044] It should be noted that in other embodiments, the model can also be trained by using resource usage data (including CPU utilization, memory utilization, and network bandwidth utilization) that marks the system resource utilization efficiency, thereby constructing a mapping relationship between the system resource utilization efficiency and the CPU utilization, memory utilization, and network bandwidth utilization.

[0045] In some alternative embodiments, the importance of the protocol is determined by the protocol plugin tasks, which include emergency tasks, regular tasks, and background tasks, with their corresponding protocol importance decreasing in that order.

[0046] Urgent tasks: Operations that must be performed immediately, such as device authentication and connection establishment; Routine tasks: periodic tasks such as obtaining bitstream addresses and querying device status; Background tasks: Non-real-time tasks such as configuration updates and log reporting.

[0047] Protocol importance can be pre-configured based on the protocol plugin task's importance score. To represent, for example: When the protocol plugin task is an urgent task, the importance score corresponding to the protocol importance is 60; When the protocol plugin task is a regular task, the importance score corresponding to the protocol importance is 30; When the protocol plugin task is a background task, the importance score corresponding to the protocol importance is 10.

[0048] The activity level, system resource utilization efficiency, and protocol importance of each network video device are normalized, and their corresponding representation data are normalized to the range of 0 to 1. This unifies the data and improves the accuracy of current priority confirmation for protocol plugins.

[0049] The process of calculating the current priority of each protocol plugin in the protocol plugin repository using a weighted summation method is as follows: ; in, Total score; , and These are the weighting coefficients, and the sum of the three is 1. Their values ​​can be chosen according to the actual situation, for example, 40%, 30%, and 30% respectively.

[0050] Based on total score To determine the priority of protocol plugins; total score The larger the value, the higher the priority.

[0051] Step S103: According to the dynamically adjusted protocol plugin execution order, register the corresponding protocol plugins to the unified abstraction layer and perform network video device query, authentication and bitstream address acquisition operations for each registered protocol plugin.

[0052] The principle of the unified abstraction layer in this invention is to achieve protocol independence through standardized interfaces and unified data formats. Its working process includes plugin registration, data conversion, and unified reporting, solving the problems of heavy load on the central platform and high integration costs in existing methods. Combined with a lightweight plugin design, this unified abstraction layer API achieves efficient multi-protocol adaptive access in resource-constrained edge scenarios.

[0053] Step S104: The obtained bitstream information is reported to the central platform in a unified data format (such as JSON format). At the same time, the activity level, system resource utilization efficiency and protocol importance of each network video device are re-determined based on the execution results of each protocol plugin, and the execution order of all protocol plugins in the protocol plugin repository is dynamically adjusted.

[0054] In one or more embodiments, if the execution of the protocol plugin fails, it will be automatically retried, and the execution strategy will be adjusted according to the reason for the failure (e.g., delaying retry if there is a network problem).

[0055] This invention automatically identifies the protocol type of a network video device based on the first packet received when the device comes online. It then dynamically loads matching protocol plugins from a protocol plugin repository. Furthermore, based on the activity level of each network video device, system resource utilization efficiency, and protocol importance, it dynamically adjusts the execution order of all protocol plugins in the repository. This process registers and executes the plugins, ensuring that in resource-constrained edge environments, the system can intelligently allocate resources and optimize execution efficiency while guaranteeing the real-time performance and stability of critical services. Through continuous monitoring, the execution order of all protocol plugins in the repository is dynamically readjusted, achieving pluggable, loosely coupled, dynamically loadable multi-protocol adaptive access and maintaining high system efficiency under different workloads.

[0056] like Figure 2 As shown, the edge-side multi-protocol adaptive video device access device provided in this embodiment of the invention can be implemented in software. The edge-side multi-protocol adaptive video device access device includes the following software modules: dynamic loading module 201, dynamic scheduling module 202, plug-in execution module 203, and data reporting module 204.

[0057] The functions of each software module in the edge-side multi-protocol adaptive video device access device are described below: (1) Dynamic loading module 201, which is used to perform feature matching on the first packet when each network video device goes online, automatically identify the protocol type of the corresponding network video device, and then dynamically load the matching protocol plugin in the protocol plugin repository.

[0058] In practice, the protocol signature identifier listens to network ports (UDP 5060, 8000, TCP 37777) and captures the first packet data when a network video device comes online.

[0059] By using a protocol signature identifier, SIP header fields, SDK handshake features, and private message fingerprints are extracted from the first packet sent when each network video device comes online. These first packet features are then used to match and determine the protocol type of each network video device (e.g., Hikvision proprietary V3.2, GB / T28181, etc.). This improves the accuracy of protocol type identification for network video devices.

[0060] Different network video devices are pre-configured with corresponding protocol types; Different protocol types have different first packet characteristics, such as SIP header fields, SDK handshake features, and private message fingerprints. Therefore, the protocol type of each network video device can be determined by matching the first packet characteristics such as SIP header fields, SDK handshake features, and private message fingerprints.

[0061] It should be noted here that the protocol feature recognizer can be implemented using an existing neural network architecture. Its training samples are the first packet data when the network video device with the labeled protocol type comes online. By extracting the data SIP header field, SDK handshake features and private message fingerprints from the first packet when the network video device comes online, the parameters of the protocol feature recognizer are trained, and the mapping relationship between the data SIP header field, SDK handshake features and private message fingerprints and the protocol type is constructed.

[0062] In other embodiments, those skilled in the art may also use feature similarity comparison to match and identify the protocol type of the corresponding network video device, which will not be described in detail here.

[0063] Based on the identified protocol type, the corresponding shared library (SO / DLL) is loaded from the protocol plugin repository. This repository stores lightweight protocol parsing plugins, achieving low resource consumption and high scalability through a dynamic loading mechanism. The protocol plugin repository solves the problems of high integration costs and heavy load on the central platform in existing methods, making it particularly suitable for resource-constrained scenarios such as substations and power distribution rooms.

[0064] The protocol plugin in this embodiment of the invention only implements three callback functions: "device discovery, authentication, and bitstream address acquisition," which reduces system memory usage.

[0065] (2) Dynamic scheduling module 202, which is used to dynamically adjust the execution order of all protocol plugins in the protocol plugin repository according to the activity level of each network video device, the efficiency of system resource usage and the importance of the protocol.

[0066] In one or more embodiments, the activity level, system resource utilization efficiency, and protocol importance of each network video device are normalized, and then the current priority of each protocol plugin in the protocol plugin repository is calculated by weighted summation, thereby dynamically adjusting the execution order of all protocol plugins in the protocol plugin repository.

[0067] The activity level of network video devices is determined by their online status, data transmission frequency, and response time. The activity level of network video devices can be calculated using the following formula: ; in, Activity level; The value is 0 or 1, which indicates the online status. A value of 0 indicates offline and a value of 1 indicates online. For data transmission frequency; For response time; , and These are weighting coefficients; the sum of these three factors equals 1, and their values ​​can be determined based on the specific circumstances. For example... , , .

[0068] The weight of online status indicates that whether a device is online is a key factor in determining its activity level; the weight of data transmission frequency reflects the workload of the device; and the weight of response time measures the real-time performance of the device.

[0069] Plugins for high-activity devices (such as live surveillance cameras) are given higher priority to ensure timely processing of critical data; while plugins for low-activity devices (such as occasionally used storage devices) are given lower priority to reduce resource consumption.

[0070] It should be noted that in other embodiments, the model can also be trained using network video device operating status data (including online status, data transmission frequency, and response time) that marks the activity of network video devices, thereby constructing a mapping relationship between the activity of network video devices and the online status, data transmission frequency, and response time.

[0071] In one or more embodiments, system resource utilization efficiency is determined by CPU utilization, memory utilization, and network bandwidth utilization.

[0072] CPU utilization refers to the current percentage of CPU usage (e.g., 75%). Memory utilization rate refers to the percentage of total memory currently in use (e.g., 80%). Network bandwidth utilization refers to the percentage of current network throughput relative to the maximum available bandwidth (e.g., 60%).

[0073] System resource utilization efficiency can be calculated using the following formula: ; in, To improve system resource utilization efficiency; CPU utilization; Memory usage; Network bandwidth utilization; , and These are weighting coefficients; the sum of these three factors equals 1, and their values ​​can be determined based on the specific circumstances. For example... , , .

[0074] It should be noted that in other embodiments, the model can also be trained by using resource usage data (including CPU utilization, memory utilization, and network bandwidth utilization) that marks the system resource utilization efficiency, thereby constructing a mapping relationship between the system resource utilization efficiency and the CPU utilization, memory utilization, and network bandwidth utilization.

[0075] In some alternative embodiments, the importance of the protocol is determined by the protocol plugin tasks, which include emergency tasks, regular tasks, and background tasks, with their corresponding protocol importance decreasing in that order.

[0076] Urgent tasks: Operations that must be performed immediately, such as device authentication and connection establishment; Routine tasks: periodic tasks such as obtaining bitstream addresses and querying device status; Background tasks: Non-real-time tasks such as configuration updates and log reporting.

[0077] Protocol importance can be pre-configured based on the protocol plugin task's importance score. To represent, for example: When the protocol plugin task is an urgent task, the importance score corresponding to the protocol importance is 60; When the protocol plugin task is a regular task, the importance score corresponding to the protocol importance is 30; When the protocol plugin task is a background task, the importance score corresponding to the protocol importance is 10.

[0078] The activity level, system resource utilization efficiency, and protocol importance of each network video device are normalized, and their corresponding representation data are normalized to the range of 0 to 1. This unifies the data and improves the accuracy of current priority confirmation for protocol plugins.

[0079] The process of calculating the current priority of each protocol plugin in the protocol plugin repository using a weighted summation method is as follows: ; in, Total score; , and These are the weighting coefficients, and the sum of the three is 1. Their values ​​can be chosen according to the actual situation, for example, 40%, 30%, and 30% respectively.

[0080] Based on total score To determine the priority of protocol plugins; total score The larger the value, the higher the priority.

[0081] (3) Plugin execution module 203, which is used to register the corresponding protocol plugins to the unified abstraction layer according to the dynamically adjusted protocol plugin execution order and to perform network video device query, authentication and bitstream address acquisition operations for each registered protocol plugin.

[0082] The principle of the unified abstraction layer in this embodiment is to achieve protocol independence through standardized interfaces and unified data formats. Its working process includes plugin registration, data conversion, and unified reporting, which solves the problems of heavy load on the central platform and high integration costs in existing methods. Combined with a lightweight plugin design, this unified abstraction layer API achieves efficient multi-protocol adaptive access in resource-constrained edge scenarios.

[0083] (4) Data reporting module 204 is used to report the acquired bitstream information to the central platform in a unified data format. At the same time, it re-determines the activity level, system resource utilization efficiency and protocol importance of each network video device based on the execution results of each protocol plugin, and dynamically adjusts the execution order of all protocol plugins in the protocol plugin repository.

[0084] In one or more embodiments, if the execution of the protocol plugin fails, it will be automatically retried, and the execution strategy will be adjusted according to the reason for the failure (e.g., delaying retry if there is a network problem).

[0085] It should be noted that each module in the edge-side multi-protocol adaptive video device access device of this embodiment corresponds one-to-one with each step in the edge-side multi-protocol adaptive video device access method in the above embodiment, and their specific implementation processes are the same, so they will not be repeated here.

[0086] The structure of the electronic device according to an embodiment of the present invention will be described in detail below. Figure 3 This is a schematic diagram of the composition structure of an electronic device provided in an embodiment of the present invention. It can be understood that... Figure 3 The diagram shows only an exemplary structure of the electronic device, not the entire structure. Some or all of the structures shown may be implemented as needed.

[0087] The electronic device provided in this embodiment of the invention includes: at least one processor 301, a memory 302, a user interface 303, and at least one network interface 304. The various components in the edge-side multi-protocol adaptive video device access device are coupled together via a bus system 305. It can be understood that the bus system 305 is used to realize the connection and communication between these components. In addition to a data bus, the bus system 305 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 3 The general designated all buses as Bus System 305.

[0088] The user interface 303 may include a monitor, keyboard, mouse, trackball, click wheel, buttons, touchpad, or touch screen.

[0089] It is understood that memory 302 can be volatile memory or non-volatile memory, or both. In this embodiment of the invention, memory 302 is capable of storing data to support the operation of the terminal. Examples of this data include any computer programs used to operate on the terminal, such as operating systems and applications. The operating system includes various system programs, such as framework layers, core library layers, driver layers, etc., used to implement various basic services and handle hardware-based tasks. Applications can include various applications.

[0090] In some embodiments, the edge-side multi-protocol adaptive video device access device provided in this invention can be implemented using a combination of hardware and software. For example, the edge-side multi-protocol adaptive video device access device provided in this invention can be a processor in the form of a hardware decoding processor, programmed to execute the edge-side multi-protocol adaptive video device access method provided in this invention. For instance, the processor in the form of a hardware decoding processor can employ one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0091] As an example, processor 301 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., wherein the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0092] As an example of the hardware implementation of the edge-side multi-protocol adaptive video device access device provided in this embodiment of the invention, the device provided in this embodiment of the invention can be directly executed by a processor 301 in the form of a hardware decoding processor. For example, it can be executed by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components to implement the edge-side multi-protocol adaptive video device access method provided in this embodiment of the invention.

[0093] The memory 302 in this embodiment of the invention is used to store various types of data to support the operation of the edge-side multi-protocol adaptive video device access device, or to store data for execution. Figure 1The program code for the method shown. Examples of this data include: any executable instructions for operation on an edge-side multi-protocol adaptive video device access device, such as executable instructions that can be included in the executable instructions, implementing the edge-side multi-protocol adaptive video device access method of the embodiments of the present invention.

[0094] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including functions for executing... Figure 1 The program code for the method shown. In such an embodiment, the computer program can be downloaded and installed from a network via a communication component, and / or installed from a removable medium. When the computer program is executed by the central processing unit, it performs the various functions defined in the apparatus of this application.

[0095] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, as well as combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0096] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for edge-side multi-protocol adaptive video device access, characterized in that, include: The first packet sent by each network video device upon going online is matched for features, and the protocol type of the corresponding network video device is automatically identified. Then, the matching protocol plugin is dynamically loaded from the protocol plugin repository. The execution order of all protocol plugins in the protocol plugin repository is dynamically adjusted based on the activity level of each network video device, system resource utilization efficiency, and protocol importance. According to the dynamically adjusted execution order of protocol plugins, the corresponding protocol plugins are registered to the unified abstraction layer and the network video device query, authentication and bitstream address acquisition operations of each registered protocol plugin are executed. The acquired bitstream information is reported to the central platform in a unified data format. At the same time, the activity level of each network video device, system resource utilization efficiency, and protocol importance are re-determined based on the execution results of each protocol plugin. The execution order of all protocol plugins in the protocol plugin repository is then dynamically adjusted.

2. The edge-side multi-protocol adaptive video device access method as described in claim 1, characterized in that, The protocol feature identifier is used to extract SIP header fields, SDK handshake features and private message fingerprints from the first packet when each network video device comes online. Then, the protocol type of each network video device is determined by matching these first packet features.

3. The edge-side multi-protocol adaptive video device access method as described in claim 1, characterized in that, After normalizing the activity level, system resource utilization efficiency, and protocol importance of each network video device, the current priority of each protocol plugin in the protocol plugin repository is calculated by weighted summation, and then the execution order of all protocol plugins in the protocol plugin repository is dynamically adjusted.

4. The edge-side multi-protocol adaptive video device access method as described in claim 1 or 3, characterized in that, The activity level of network video devices is determined by their online status, data transmission frequency, and response time.

5. The edge-side multi-protocol adaptive video device access method as described in claim 1 or 3, characterized in that, System resource utilization efficiency is determined by CPU utilization, memory utilization, and network bandwidth utilization.

6. The edge-side multi-protocol adaptive video device access method as described in claim 1 or 3, characterized in that, The importance of a protocol is determined by the protocol plugin tasks, which include emergency tasks, regular tasks, and background tasks, with their respective protocol importance decreasing in that order.

7. The edge-side multi-protocol adaptive video device access method as described in claim 1, characterized in that, If the execution of the protocol plugin fails, it will automatically retry and adjust the execution strategy according to the reason for the failure.

8. An edge-side multi-protocol adaptive video device access system, characterized in that, The edge-side multi-protocol adaptive video device access method based on any one of claims 1-7 includes: The dynamic loading module is used to perform feature matching on the first packet when each network video device comes online, automatically identify the protocol type of the corresponding network video device, and then dynamically load the matching protocol plugin from the protocol plugin repository. The dynamic scheduling module is used to dynamically adjust the execution order of all protocol plugins in the protocol plugin repository based on the activity level of each network video device, system resource utilization efficiency, and protocol importance. The plugin execution module is used to register the corresponding protocol plugins to the unified abstraction layer according to the dynamically adjusted protocol plugin execution order, and to perform network video device query, authentication and bitstream address acquisition operations for each registered protocol plugin. The data reporting module is used to report the acquired bitstream information to the central platform in a unified data format. At the same time, it redetermines the activity level of each network video device, system resource utilization efficiency, and protocol importance based on the execution results of each protocol plugin, and dynamically adjusts the execution order of all protocol plugins in the protocol plugin repository.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps in the edge-side multi-protocol adaptive video device access method as described in any one of claims 1-7.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps in the edge-side multi-protocol adaptive video device access method as described in any one of claims 1-7.

Images