Interface parameter acquisition method and device, electronic equipment and storage medium

By matching and reusing the interface parameters of already connected devices using interface parameter feature information when front-end monitoring devices are connected, the problem of large amounts of network interaction data is solved, network load is reduced, and data transmission efficiency is improved.

CN119496866BActive Publication Date: 2026-06-30ZHEJIANG UNIVIEW TECH CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
ZHEJIANG UNIVIEW TECH CO LTD
Filing Date
2023-08-14
Publication Date
2026-06-30

Smart Images

  • Figure CN119496866B_ABST
    Figure CN119496866B_ABST
Patent Text Reader

Abstract

The application provides an interface parameter acquisition method and device, electronic equipment and a storage medium, and relates to the technical field of monitoring. The method comprises the following steps: in the case that a front-end accesses a first monitoring device is detected, first interface parameter characteristic information of the first monitoring device is acquired; in the case that it is determined that first target characteristic information matching second interface parameter characteristic information of a second monitoring device which has been accessed exists in the first interface parameter characteristic information, target interface parameters of a target data interaction interface in the second monitoring device are copied, and the copied target interface parameters are determined as interface parameters of a first data interaction interface corresponding to the first target characteristic information in the first monitoring device; wherein, the target data interaction interface is a data interaction interface matching the first data interaction interface. The technical scheme provided by the application can effectively reduce the network interaction data amount between the front-end monitoring device and the back-end electronic equipment, and reduce the network load.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of monitoring technology, and in particular to a method, apparatus, electronic device, and storage medium for acquiring interface parameters. Background Technology

[0002] In the field of surveillance, front-end monitoring devices can be uniformly managed through back-end electronic devices. For example, a back-end electronic device can be a network video recorder (NVR), which can manage multiple network cameras (IP cameras, IPCs) at the front end and interact with them for data. Alternatively, a back-end electronic device can be a server, which can manage front-end monitoring devices such as cameras and interact with them for data.

[0003] The interaction between front-end monitoring devices and back-end electronic devices relies on numerous interfaces to enable the back-end electronic devices to obtain complete device functionality and configuration information from the front-end monitoring devices. This device functionality and configuration information can be characterized through interface parameters. Currently, the back-end electronic devices need to obtain interface parameters from each interface of each front-end monitoring device separately. This results in a large volume of network interaction data, especially when a large number of monitoring devices are connected to the front end, leading to very high network load and impacting network data transmission efficiency. Summary of the Invention

[0004] This invention provides a method, apparatus, electronic device, and storage medium for obtaining interface parameters, in order to solve the problem of high network load caused by large amounts of network interaction data between front-end monitoring devices and back-end electronic devices in the prior art.

[0005] This invention provides a method for obtaining interface parameters, including:

[0006] Upon detecting that the front end is connected to the first monitoring device, the first interface parameter feature information of the first monitoring device is obtained;

[0007] Determine whether there is a first target feature information in the first interface parameter feature information that matches the second interface parameter feature information of the connected second monitoring device;

[0008] If the first target feature information exists in the first interface parameter feature information, copy the target interface parameter of the target data interaction interface in the second monitoring device, and determine the copied target interface parameter as the interface parameter of the first data interaction interface corresponding to the first target feature information in the first monitoring device; wherein, the target data interaction interface is a data interaction interface that matches the first data interaction interface.

[0009] According to the interface parameter acquisition method provided by the present invention, the first interface parameter feature information includes a list of feature values ​​corresponding to each second data interaction interface in the first monitoring device; determining whether there is first target feature information in the first interface parameter feature information that matches the second interface parameter feature information of the connected second monitoring device includes:

[0010] Determine whether there is a first feature value in the second interface parameter feature information that matches the feature value list;

[0011] If the first feature value exists in the second interface parameter feature information, it is determined that there is a first target feature information in the first interface parameter feature information that matches the second interface parameter feature information; wherein, the first target feature information is the list of feature values ​​that match the first feature value; and the target data interaction interface is the second data interaction interface corresponding to the matching feature value list.

[0012] According to an interface parameter acquisition method provided by the present invention, the first interface parameter feature information further includes a first feature vector table of the first monitoring device and a first module feature value list corresponding to each interface module of the first monitoring device. The interface module includes at least one second data interaction interface of the same interface type. The first module feature value list is determined based on the feature value list of each second data interaction interface in the interface module. Determining whether there is a first feature value in the second interface parameter feature information that matches the feature value list includes:

[0013] Determine whether the first feature vector table is the same as the second feature vector table in the second interface parameter feature information;

[0014] If the first feature vector table is different from the second feature vector table, for each interface module, it is determined whether there is a second feature value in the second feature vector table that matches the first module feature value list of the interface module;

[0015] If the second feature value exists in the second feature vector table, it is determined that there is a first feature value in the second interface parameter feature information that matches the feature value list, wherein the first feature value is the second feature value, and the first data interaction interface is all the second data interaction interfaces included in the interface module.

[0016] The interface parameter acquisition method provided by the present invention further includes:

[0017] If there is no second feature value in the second feature vector table that matches the first module feature value list of the interface module, for each third data interaction interface in the interface module, it is determined whether there is a third feature value in the second feature vector table that matches the feature value list corresponding to the third data interaction interface;

[0018] If the third feature value exists in the second feature vector table, it is determined that there is a first feature value in the second interface parameter feature information that matches the feature value list, and the third data interaction interface is determined as the first data interaction interface, wherein the first feature value is the third feature value.

[0019] According to an interface parameter acquisition method provided by the present invention, the first module feature value list corresponding to each interface module of the first monitoring device is obtained by concatenating the feature value lists of each second data interaction interface in the interface module and performing a hash transformation.

[0020] The first feature vector table is generated by storing the feature values ​​from each of the feature value lists and the feature values ​​from each of the first module feature value lists into a vector table.

[0021] The interface parameter acquisition method provided by the present invention further includes:

[0022] For second target feature information in the first interface parameter feature information that does not match the second interface parameter feature information, obtain the interface parameters of the data interaction interface corresponding to the second target feature information from the first monitoring device.

[0023] According to an interface parameter acquisition method provided by the present invention, after determining the copied target interface parameter as the interface parameter of the first data interaction interface corresponding to the first target feature information in the first monitoring device, the method further includes:

[0024] For the second interface module in the second monitoring device, the feature value list of each data interaction interface in the second interface module is concatenated, and timestamp information is added to the concatenated feature value list to obtain the first feature value list to be processed; wherein, the interface parameters of each data interaction interface in the second interface module are copied by the first interface module in the first monitoring device.

[0025] The first list of feature values ​​to be processed is hashed to obtain the second module feature value list corresponding to the second interface module.

[0026] If the feature value list of the second module is inconsistent with the feature value list of the third module, the interface parameters corresponding to each data interaction interface in the first interface module are re-obtained from the first monitoring device; wherein, the feature value list of the third module is obtained by the first monitoring device by concatenating the feature value lists of each data interaction interface in the first interface module, adding the timestamp information to the concatenated feature value list, and performing a hash transformation on the second feature value list to be processed obtained after adding the timestamp information.

[0027] The present invention also provides an interface parameter acquisition device, comprising:

[0028] The information acquisition module is used to acquire the first interface parameter feature information of the first monitoring device when the front end is detected to be connected to the first monitoring device.

[0029] The feature matching module is used to determine whether there is a first target feature information in the first interface parameter feature information that matches the second interface parameter feature information of the connected second monitoring device;

[0030] The parameter copying module is used to copy the target interface parameters of the target data interaction interface in the second monitoring device when the first target feature information exists in the first interface parameter feature information, and to determine the copied target interface parameters as the interface parameters of the first data interaction interface corresponding to the first target feature information in the first monitoring device; wherein, the target data interaction interface is a data interaction interface that matches the first data interaction interface.

[0031] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the interface parameter acquisition method as described above.

[0032] The present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the interface parameter acquisition method as described above.

[0033] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the interface parameter acquisition method as described above.

[0034] The interface parameter acquisition method, apparatus, electronic device, and storage medium provided by this invention, when detecting that a front-end has connected to a first monitoring device, acquires the first interface parameter feature information of the first monitoring device. Then, it compares this first interface parameter feature information with the second interface parameter feature information of an already connected second monitoring device. If the first interface parameter feature information contains first target feature information that matches the second interface parameter feature information, it indicates that the interface parameters of the already connected second monitoring device contain interface parameters identical to the first data interaction interface corresponding to the first target feature information in the first monitoring device. In this case, the target interface parameter of the target data interaction interface matching the first data interaction interface in the second monitoring device is copied, and the copied target interface parameter is determined as the interface parameter of the first data interaction interface corresponding to the first target feature information in the first monitoring device. In this way, when a front-end connects to the first monitoring device, interface parameters that are duplicated with those of the first monitoring device can be filtered from the already connected second monitoring device and directly reused, without having to obtain them from the first monitoring device. This effectively reduces the amount of network interaction data between the front-end monitoring device and the back-end electronic device, and reduces network load. Attached Figure Description

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

[0036] Figure 1 This is one of the flowcharts illustrating the interface parameter acquisition method provided in this embodiment of the invention;

[0037] Figure 2 This is a schematic diagram illustrating an application scenario of the interface parameter acquisition method provided in this embodiment of the invention;

[0038] Figure 3 This is a second flowchart illustrating the interface parameter acquisition method provided in this embodiment of the invention.

[0039] Figure 4 This is a schematic diagram of the interface parameter acquisition device provided in an embodiment of the present invention;

[0040] Figure 5 This is a schematic diagram of the structure of the electronic device provided in an embodiment of the present invention. Detailed Implementation

[0041] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0042] It should be noted that the serial numbers assigned to the objects described in this invention, such as "first" and "second", are only used to distinguish the objects being described and do not have any sequential or technical meaning.

[0043] In the field of surveillance, the interaction between front-end and back-end devices is very frequent. Taking NVR and IPC as an example, the NVR, as a back-end device, needs to manage a large number of front-end IPCs and interact with them on data. The data interaction between NVR and IPC is based on data interaction protocol standards, such as the Simple Object Access Protocol (SOAP). However, data interaction protocols usually carry a large amount of data and have high performance consumption for parsing.

[0044] In real-world applications, the interaction data between IPCs and NVRs in the same batch is essentially identical, leading to a large amount of repetitive interaction. This significantly impacts the performance of both the NVR and IPCs, as well as the network load. Interaction between the NVR and IPCs relies on numerous interfaces to obtain complete device capabilities and configuration information. When connecting a large number of IPCs, such as hundreds, the frequency of interface interactions increases rapidly. As device functionality continues to improve and access specifications expand, this places a significant burden on the NVR's network load and performance, resulting in slow IPC deployment. Furthermore, network instability may cause some IPCs with similar functions to have incomplete capability or configuration information.

[0045] Based on this, embodiments of the present invention provide an interface parameter acquisition method. When accessing a front-end monitoring device, the method utilizes the interface parameter feature information of the newly accessed front-end monitoring device to quickly filter and reuse duplicate data in the interface parameters already acquired by the back-end device, while re-acquiring non-duplicate data. This effectively reduces the amount of network interaction data between the front-end monitoring device and the back-end device, thereby reducing network load.

[0046] The following is combined Figures 1-3The interface parameter acquisition method of the present invention is described below. This interface parameter acquisition method can be applied to electronic devices such as terminal devices or servers that are communicatively connected to monitoring equipment. The terminal devices may include mobile phones, computers, in-vehicle devices, tablet computers, wearable devices, etc.; the servers may include standalone servers, cluster servers, or cloud servers, etc. This interface parameter acquisition method can also be applied to an interface parameter acquisition device installed in the terminal device or server, which can be implemented through software, hardware, or a combination of both.

[0047] Figure 1 An exemplary schematic diagram of one of the interface parameter acquisition methods provided in an embodiment of the present invention is shown below. Figure 1 As shown, the method for obtaining interface parameters may include the following steps 110 to 130.

[0048] Step 110: When the front end is detected to be connected to the first monitoring device, obtain the first interface parameter feature information of the first monitoring device.

[0049] The first interface parameter feature information can be obtained by hashing the interface parameters of the first monitoring device. The interface parameters represent the capability information of the data interaction interface in the first monitoring device and the configuration information of the capability represented by that capability. The capability represents the functions possessed by the monitoring device.

[0050] For example, the first interface parameter feature information may include at least one of a feature value list, a first module feature value list, and a first feature vector table. The feature value list consists of feature values ​​of the data interaction interface, which can be obtained by hashing the interface parameters of each data interaction interface in the first monitoring device. The first module feature value list consists of feature values ​​of the interface module. An interface module includes at least one data interaction interface of the same interface type, and this first module feature value list can be obtained by concatenating the feature value lists of all its included data interaction interfaces and then hashing them. The first feature vector table can be generated by storing the feature values ​​of each data interaction interface and / or each interface module in the first monitoring device into a vector table.

[0051] For example, a vector table of length m can be preset, and n hash functions can be preset. For the nth hash function, the hash transformation process of the hash function is as follows: the American Standard Code for Information Interchange (ASCII) of each character in the string of the input hash function is shifted left by 10n bits to obtain a hash value, and the remainder obtained by taking the hash value modulo m is used as the feature value corresponding to the nth hash function.

[0052] Based on this, during the initialization of the first monitoring device, for each data interaction interface involved in the interaction between the first monitoring device and the backend electronic equipment, the interface parameters of the data interaction interface can be converted into strings and then input into n hash functions respectively to obtain a feature value output by each hash function. Thus, the interface parameters of a data interaction interface correspond to n feature values, and the feature value list formed by these n feature values ​​is used as the feature value list corresponding to that data interaction interface. For each interface module obtained by classifying these data interaction interfaces according to their functions, the feature value lists corresponding to each data interaction interface belonging to that interface module can be concatenated and then input into the n hash functions for hash conversion, similarly obtaining n feature values. The feature value list formed by these n feature values ​​is used as the first module feature value list corresponding to that interface module. Then, the feature values ​​of each data interaction interface and / or the feature values ​​of each interface module are stored in a vector table, i.e., a position is set in the vector table, which generates the first feature vector table corresponding to the first monitoring device. The string feature data is stored in the vector table.

[0053] For example, during the generation of the feature value list, the string input to the hash function can be the body content of the SOAP after serialization from the data interaction interface.

[0054] By using a hash function, the interface parameters of the data interaction interface are converted into feature values, which are then used to characterize the interface parameters. Compared to transmitting interface parameters, transmitting feature values ​​can compress the amount of data transmitted to a certain extent.

[0055] Step 120: Determine whether there is a first target feature information in the first interface parameter feature information that matches the second interface parameter feature information of the connected second monitoring device.

[0056] Similar to the first interface parameter feature information, the second interface parameter feature information may include at least one of the following: a feature value list corresponding to the second monitoring device, a module feature value list, and a second feature vector table. The second interface parameter feature information can be obtained by hashing the interface parameters of the second monitoring device during initialization. After the second monitoring device connects to the backend electronic device, the electronic device can obtain the second interface parameter feature information.

[0057] For each second monitoring device that has been connected to the electronic device, the electronic device has obtained the interface parameters of all data interaction interfaces involved in the interaction between the second monitoring device and the electronic device. By comparing the first interface parameter feature information of the first monitoring device with the second interface parameter feature information of the second monitoring device, it can be determined whether there is reusable data of the first monitoring device in the interface parameter data obtained by the electronic device.

[0058] For example, the list of first feature values ​​corresponding to each data interaction interface in the first interface parameter feature information can be compared with the second feature vector table or the second feature value list in the second interface parameter feature information. If the feature values ​​in the first feature value list exist in the second feature value list or the second feature vector table, it is determined that there is a first target feature information in the first interface parameter feature information that matches the second interface parameter feature information. The first feature value list is the first target feature information.

[0059] Alternatively, for each interface module in the first interface parameter feature information, the list of first module feature values ​​corresponding to that interface module can be compared with the second feature vector table in the second interface parameter feature information or the list of fourth module feature values ​​corresponding to each interface module. If the feature values ​​of the first module feature value list exist in the second feature vector table or a certain fourth module feature value list, then it is determined that there is first target feature information in the first interface parameter feature information that matches the second interface parameter feature information, and the list of first module feature values ​​is the first target feature information. Otherwise, for each data interaction interface in that interface module, it is determined whether the feature values ​​of the first feature value list of that data interaction interface exist in the second feature value list or the second feature vector table. If they exist, then it is determined that there is first target feature information in the first interface parameter feature information that matches the second interface parameter feature information, and the list of first feature values ​​of that data interaction interface is the first target feature information.

[0060] Alternatively, the first feature vector table in the first interface parameter feature information can be compared with the second feature vector table in the second interface parameter feature information. If they are the same, it is determined that there is a first target feature information in the first interface parameter feature information that matches the second interface parameter feature information. At this time, the feature values ​​of the interface parameters of all interactive interfaces represented by the first interface parameter feature information are the first target feature information. If they are different, for each interface module in the first interface parameter feature information, the first module feature value list corresponding to that interface module is compared with the second feature vector table. If the feature values ​​of the first module feature value list exist in the second feature vector table, the match is successful, and the first module feature value list is the successfully matched first target feature information. If the feature values ​​of the first module feature value list do not exist in the second feature vector table, it is further determined whether the feature values ​​of the first feature value list of each data interaction interface in that interface module exist in the second feature vector table. If they exist, the match is successful, and the first feature value list of that data interaction interface is the matched first target feature information.

[0061] Step 130: If the first target feature information exists in the first interface parameter feature information, copy the target interface parameter of the target data interaction interface in the second monitoring device, and determine the copied target interface parameter as the interface parameter of the first data interaction interface corresponding to the first target feature information in the first monitoring device.

[0062] The target data interaction interface is the data interaction interface that matches the first data interaction interface.

[0063] For example, for second target feature information in the first interface parameter feature information that does not match the second interface parameter feature information, the interface parameters of the data interaction interface corresponding to the second target feature information can be obtained from the first monitoring device.

[0064] For example, Figure 2 An exemplary illustration shows an application scenario diagram of the interface parameter acquisition method provided in an embodiment of the present invention. (Refer to...) Figure 2 As shown, taking an NVR as the backend electronic device and an IPC as the frontend monitoring device as an example, the NVR can manage and interact with multiple frontend IPCs. When IPC 21, IPC 22, and IPC 23 are initialized, a feature value list, a module feature value list, and a feature vector table corresponding to each IPC can be generated. Assuming that when IPC 23 is added to NVR 20, and IPC 21 and IPC 22 are already connected to NVR 20, then NVR 20 has already stored the feature value lists, module feature value lists, feature vector tables, and interface parameters of each data interaction interface for IPC 21 and IPC 22. Assuming the data interaction interfaces involved in the interaction between IPC 23 and NVR 20 include data interaction interface A3 and data interaction interface B3, and the feature values ​​of the first feature value list of data interaction interface A3 determined according to step 120 exist in the feature vector table of IPC 22 already stored in NVR 20, this indicates that there are interface parameters in IPC 22 that can be reused by data interaction interface A3. Therefore, data interaction interface A3 is the first data interaction interface corresponding to the first target feature information. At this time, based on the identification information of data interaction interface A3, a target data interaction interface matching this identification information can be determined from all data interaction interfaces of IPC 22, such as data interaction interface A2. Then, NVR 20 copies the interface parameters of data interaction interface A2 and uses these interface parameters as the interface parameters of data interaction interface A3 of IPC 23, without needing to obtain the interface parameters of data interaction interface A3 from IPC 23, thus reducing the amount of data interaction between IPC 23 and NVR 20. For data interaction interface B3 that fails to match, NVR 20 can directly obtain the interface parameters of data interaction interface B3 from IPC 23.

[0065] The interface parameter acquisition method provided in this embodiment of the invention, when detecting that a front-end has accessed a first monitoring device, acquires the first interface parameter feature information of the first monitoring device, and then compares the first interface parameter feature information with the second interface parameter feature information of an already accessed second monitoring device. If the first interface parameter feature information contains first target feature information that matches the second interface parameter feature information, it indicates that the interface parameters of the already accessed second monitoring device contain interface parameters identical to the first data interaction interface corresponding to the first target feature information in the first monitoring device. In this case, the target interface parameter of the target data interaction interface matching the first data interaction interface in the second monitoring device is copied, and the copied target interface parameter is determined as the interface parameter of the first data interaction interface corresponding to the first target feature information in the first monitoring device. In this way, when the front-end has accessed the first monitoring device, interface parameters that are duplicated with the first monitoring device can be filtered from the already accessed second monitoring device and reused directly, without having to obtain them from the first monitoring device. This effectively reduces the amount of network interaction data between the front-end monitoring device and the back-end electronic device, and reduces network load.

[0066] based on Figure 1 In an optional implementation of the interface parameter acquisition method corresponding to the embodiment, the first feature vector table can be generated by the electronic device storing the feature values ​​from the feature value list obtained from the first monitoring device and / or the feature values ​​from the feature value list of the first module into the vector table, or it can be updated by the electronic device based on the feature values ​​of the copied interface parameters of the second monitoring device. Specifically, after the electronic device copies the target interface parameters of the target data interaction interface in the second monitoring device and determines the copied target interface parameters as the interface parameters of the first data interaction interface corresponding to the first target feature information in the first monitoring device, it can generate or update the first feature vector table of the first monitoring device based on the copied target interface parameters; or after obtaining the interface parameters of the data interaction interface corresponding to the second target feature information from the first monitoring device, it can update or generate the first feature vector table of the first monitoring device based on the obtained interface parameters. In this way, the transmission of feature vector tables can be reduced, further reducing the amount of network interaction data between the front-end monitoring device and the back-end electronic device.

[0067] based on Figure 1In one example embodiment of the interface parameter acquisition method corresponding to the embodiment, the first interface parameter feature information includes a list of feature values ​​corresponding to each second data interaction interface in the first monitoring device. Accordingly, determining whether there is first target feature information in the first interface parameter feature information that matches the second interface parameter feature information of the connected second monitoring device may include: determining whether there is a first feature value in the second interface parameter feature information that matches the feature value list; if there is a first feature value in the second interface parameter feature information, determining that there is first target feature information in the first interface parameter feature information that matches the second interface parameter feature information; wherein, the first target feature information is a list of feature values ​​that match the first feature value; and the target data interaction interface is the second data interaction interface corresponding to the matching feature value list.

[0068] For example, the first interface parameter feature information may include a feature value list of each data interaction interface of the first monitoring device. For each second data interaction interface in the first monitoring device, the feature value list of the second data interaction interface can be compared with all feature value lists in the second interface parameter feature information. If there is a feature value list in the second interface parameter feature information that is the same as the feature value list of the second data interaction interface, then it is determined that there is a first feature value in the second interface parameter feature information that matches the feature value list. At this time, it is considered that there is an interface parameter in the interface parameters of the data interaction interface of the second monitoring device that can be reused by the first data interaction interface. The data interaction interface corresponding to the matching feature value list in the second monitoring device can be determined as the target data interaction interface, and then the interface parameters of the target data interaction interface are copied as the interface parameters of the first data interaction interface.

[0069] For example, with Figure 2 Taking an application scenario as an example, for a newly connected IPC 23, assuming it includes data interaction interfaces A3 and B3, the feature value list of data interaction interface A3 can be compared with the feature value lists of each data interaction interface of IPC 21 and IPC 22 already connected to NVR 20. Assuming that the feature value list of data interaction interface A1 is found to be the same as that of data interaction interface A3 in the feature value list of IPC 21, then NVR 20 can copy interface parameter 1 of data interaction interface A1 and use it as the interface parameter of data interaction interface A3, without needing to obtain it from IPC 23.

[0070] For example, all data interaction interfaces of the first monitoring device can be classified according to function to obtain at least one interface module. The first interface parameter feature information may include a feature value list of each data interaction interface of the first monitoring device and a first module feature value list of each interface module. Correspondingly, for each interface module in the first interface parameter feature information, it can be determined whether the feature values ​​of the first module feature value list of the interface module are all in the second feature vector table of the second interface parameter feature information. If so, it is determined that there is a first feature value in the second interface parameter feature information that matches the feature value list. This first feature value is the feature value of the first module feature value list. At this time, it is considered that there are interface parameters in the second monitoring device that can be reused by the interface module. The corresponding target data interaction interface can be matched from the second monitoring device according to each second data interaction interface in the interface module, and then the interface parameters of the target data interaction interface are copied as the interface parameters of the corresponding second data interaction interface in the interface module. If not, for each second data interaction interface in the interface module, determine whether all feature values ​​in the feature value list of the second data interaction interface exist in the second feature vector table. If so, match the corresponding target data interaction interface from the second monitoring device and copy the interface parameters of the target data interaction interface as the interface parameters of the second data interaction interface. Otherwise, obtain the interface parameters of the second data interaction interface from the first monitoring device.

[0071] For example, with Figure 2Taking an application scenario as an example, for a newly connected IPC 23, assuming its data interaction interfaces with NVR 20 include data interaction interface A3, data interaction interface B3, and data interaction interface C3, classifying each data interaction interface according to its function yields interface module 1 (including data interaction interfaces A3 and C3) and interface module 2 (including data interaction interface B3). The first module feature value lists of interface module 1 and interface module 2 can be compared with the feature vector tables of IPCs 21 and 22 already connected to NVR 20. Assuming that not all feature values ​​in the first module feature value list of interface module 1 exist in the feature vector tables of IPCs 21 and 22, then it is necessary to determine whether all feature values ​​in the feature value lists of data interaction interfaces A3 and C3 exist in their respective feature vector tables. Assuming all feature values ​​in the feature value list of data interaction interface A3 exist in the feature vector table of IPC 22, then the target data interaction interface (let's say data interaction interface A2) can be matched from the data interaction interfaces of IPC 22. NVR 20 can then copy interface parameter 2 of data interaction interface A2 and use it as the interface parameter of data interaction interface A3, without needing to obtain it from IPC 23. Conversely, assuming not all feature values ​​in the feature value list of data interaction interface C3 exist in the feature vector tables of IPC 21 and IPC 22, then NVR 20 can obtain the interface parameters of data interaction interface C3 from IPC 23.

[0072] For example, the first interface parameter feature information may include a first feature vector table of the first monitoring device, a first module feature value list corresponding to each interface module of the first monitoring device, and a feature value list for each data interaction interface of the first monitoring device. The interface module includes at least one second data interaction interface of the same interface type; the first module feature value list can be determined based on the feature value lists of each second data interaction interface in the interface module. Correspondingly, determining whether a first feature value matching the feature value list exists in the second interface parameter feature information may include: determining whether the first feature vector table is the same as the second feature vector table in the second interface parameter feature information; if the first feature vector table and the second feature vector table are different, for each interface module, determining whether a second feature value matching the first module feature value list of the interface module exists in the second feature vector table; if a second feature value exists in the second feature vector table, determining that a first feature value matching the feature value list exists in the second interface parameter feature information, wherein the first feature value is the second feature value, and the first data interaction interface is all the second data interaction interfaces included in the interface module.

[0073] Furthermore, if there is no second feature value in the second feature vector table that matches the first module feature value list of the interface module, for each third data interaction interface in the interface module, it is determined whether there is a third feature value in the second feature vector table that matches the feature value list corresponding to the third data interaction interface; if there is a third feature value in the second feature vector table, it is determined that there is a first feature value in the second interface parameter feature information that matches the feature value list, and the third data interaction interface is determined as the first data interaction interface, wherein the first feature value is the third feature value.

[0074] Among them, the first module feature value list corresponding to each interface module of the first monitoring device is obtained by concatenating the feature value lists of each second data interaction interface in the interface module and performing hash conversion; the first feature vector table is generated by storing the feature values ​​in each feature value list and the feature values ​​in each first module feature value list into the vector table.

[0075] For example, with Figure 2 Taking an application scenario as an example, for a newly connected IPC 23, assuming its data interaction interfaces with NVR 20 include data interaction interface A3, data interaction interface B3, data interaction interface C3, and data interaction interface D3, these data interaction interfaces can be classified according to their functions to obtain interface module 1 (including data interaction interface A3 and data interaction interface C3) and interface module 2 (including data interaction interface B3 and data interaction interface D3). NVR 20 can first compare the feature vector table a of IPC 23 with the feature vector table b of IPC 21 and the feature vector table c of IPC 22 that have already been connected to NVR 20. If feature vector table a is found to be the same as feature vector table b, then NVR 20 can match the target data interaction interface corresponding to the data interaction interface of IPC 23 from IPC 21, assuming it is data interaction interface A1, data interaction interface B1, data interaction interface C1 and data interaction interface D1. Then, it copies the interface parameters of these data interaction interfaces as the interface parameters of the data interaction interface of IPC 23, without having to obtain them from IPC 23.

[0076] If feature vector table a is different from both feature vector tables b and c, then NVR 20 compares the first module feature value lists of interface module 1 and interface module 2 with feature vector tables b and c, respectively. If all feature values ​​of the first module feature value list of interface module 1 are found in feature vector table b, it indicates that there are interface parameters in the interface parameters of IPC 21 that can be reused by interface module 1. Then, NVR 20 matches the target data interaction interface corresponding to interface module 1 from the data interaction interface of IPC 21, assuming it is data interaction interface A1 and data interaction interface C1. NVR 20 copies the interface parameters of data interaction interface A1 as the interface parameters of data interaction interface A3 in interface module 1, and copies the interface parameters of data interaction interface C1 as the interface parameters of data interaction interface C3, without having to obtain them from IPC 23.

[0077] If the feature values ​​of the first module feature value list of interface module 2 are not all present in feature vector table b or feature vector table c, then NVR 20 determines whether the feature values ​​of the feature value lists of data interaction interface B3 and data interaction interface D3 are all present in feature vector table b or feature vector table c, respectively. Assuming that the feature values ​​of the feature value list of data interaction interface B3 are all present in feature vector table b, then the target data interaction interface B1 is matched from the data interaction interfaces of IPC 21. NVR 20 can copy the interface parameters of data interaction interface B1 and use these interface parameters as the interface parameters of data interaction interface B3, without needing to obtain them from IPC 23. Assuming that the feature values ​​of the feature value list of data interaction interface D3 are not all present in feature vector table b or feature vector table c, then NVR 20 can obtain the interface parameters of data interaction interface D3 from IPC 23.

[0078] In this way, by first matching the feature vector table, and then matching the feature value list of the first module of the interface module if the matching fails, and then matching the feature value list of the data interaction interface in the interface module if the matching still fails, the efficiency of feature matching can be improved, thereby increasing the speed of data reuse filtering.

[0079] Based on the interface parameter acquisition methods of the above embodiments, since the interface parameters of some or all data interaction interfaces of the first monitoring device can be obtained by reusing the interface parameters of other monitoring devices that have been connected to the backend electronic equipment, misjudgment may occur during the reuse judgment process. Specifically, in one case, since the reuse of interface parameters is judged by feature value matching, there is a possibility of feature value misjudgment. The misjudgment rate depends on the number of hash functions and the range of feature values. For example, in an extreme case, assuming that a string generates only one feature value, and the value is between 0 and 1, then no matter what string is input, the generated feature value can only be 0 or 1. That is, strings with a conversion result of 0 are not necessarily the same string, which will lead to misjudgment. This misjudgment can be reduced by setting an appropriate number of hash functions and feature value range. The larger the number of hash functions and the larger the feature value range, the closer the probability of such misjudgment can be to infinitesimal.

[0080] In another scenario, the feature vector table for each monitoring device is generated by storing the feature values ​​from the feature value list and the feature values ​​from the module feature value list into a vector table. Misjudgments may occur during the feature value mapping and storage process. The probability of a misjudgment depends on the number of hash functions and the size of the feature vector table. For example, taking two interface modules of IPC1 as an example, assuming the feature value list of interface module 1 has the feature value {1, 3, 5} and the feature value list of interface module 2 has the feature value {2, 3, 5}, mapping to the corresponding positions in the vector table yields the feature vector table of IPC1 as {1, 2, 3, 4, 5}. Suppose there is another interface module 3 of IPC2, whose feature value list has the feature value {1, 2, 5}. Since 1, 2, and 5 can be found in the feature vector table {1, 2, 3, 4, 5}, it will be assumed that the interface parameters of interface module 3 already exist in IPC1, leading to a misjudgment.

[0081] Based on this, in one example embodiment of the present invention, a mechanism for dynamically detecting and correcting data misjudgments can be introduced. The consistency of the interface parameters of the front-end monitoring device is determined by keep-alive detection, and the misjudgment rate is gradually reduced through multiple rounds of detection and correction.

[0082] Specifically, Figure 3 This is an exemplary second flowchart illustrating the interface parameter acquisition method provided in an embodiment of the present invention. (Refer to...) Figure 3 As shown, after determining the target interface parameter to be copied as the interface parameter of the first data interaction interface corresponding to the first target feature information in the first monitoring device, the interface parameter acquisition method may further include the following steps 310 to 330.

[0083] Step 310: For the second interface module in the second monitoring device, concatenate the feature value list of each data interaction interface in the second interface module, and add timestamp information to the concatenated feature value list to obtain the first feature value list to be processed.

[0084] In this process, the interface parameters of each data interaction interface in the second interface module are copied by the first interface module in the first monitoring device. That is, the first interface module in the first monitoring device reuses the interface parameters of each data interaction interface in the second interface module. The second interface module is the interface module whose interface parameters are reused by the first monitoring device.

[0085] Step 320: Perform a hash transformation on the first list of feature values ​​to be processed to obtain the second module feature value list corresponding to the second interface module.

[0086] Specifically, the same hash conversion process as in step 110 above can be used to perform hash conversion on the first list of feature values ​​to be processed.

[0087] Step 330: If the feature value list of the second module is inconsistent with the feature value list of the third module, retrieve the interface parameters corresponding to each data interaction interface in the first interface module from the first monitoring device.

[0088] The third module feature value list is obtained by the first monitoring device concatenating the feature value lists of each data interaction interface in the first interface module, adding timestamp information to the concatenated feature value list, and performing a hash transformation on the second feature value list to be processed after adding timestamp information.

[0089] If the feature value list of the second module is inconsistent with the feature value list of the third module, it indicates that there is a misjudgment of the interface parameters of the first interface module in the feature vector table of the front-end monitoring device currently managed by the back-end electronic device. In this case, the interface parameters corresponding to each data interaction interface in the first interface module can be retrieved from the first monitoring device to correct the interface parameters corresponding to each data interaction interface in the first interface module. Otherwise, wait for the next detection.

[0090] For example, with Figure 2Taking an application scenario as an example, assuming that the data interaction interfaces between IPC 23 and NVR 20 include data interaction interface A3, data interaction interface B3, and data interaction interface C3, classifying each data interaction interface according to its function yields interface module 1 (including data interaction interfaces A3 and C3) and interface module 2 (including data interaction interface B3). During the process of IPC 23 accessing NVR 20, interface module 1 reuses the interface parameters of interface module 3 in IPC 21, which is already connected to NVR 20. In a keep-alive detection process, for interface module 1 of IPC 23, IPC 23 concatenates the feature value list L1 of its data interaction interface A3 and the feature value list L2 of its data interaction interface C3 and adds timestamp information t1 to obtain a second feature value list T2 to be processed. Then, this second feature value list T2 is converted into a string and input into n hash functions to obtain a feature value output by each hash function. The n feature values ​​obtained form the third module feature value list M3 corresponding to interface module 1. Meanwhile, NVR 20 concatenates the feature value list L3 of data interaction interface A1 and the feature value list L4 of data interaction interface C1 of interface module 3 and adds timestamp information t1 to obtain the first feature value list T1 to be processed. Then, the first feature value list T1 to be processed is converted into a string and input into n hash functions to obtain a feature value output by each hash function. The n feature values ​​obtained are used to form the second module feature value list M2 corresponding to interface module 3. Then, NVR 20 compares the feature value list M2 of the second module with the feature value list M3 of the third module. If they match, it means that the feature vector table of the IPC managed by NVR 20 can accurately determine whether the interface module 1 has corresponding reused data, and its interface parameters will not be misjudged. Then it waits to enter the next detection. If the feature value list M2 of the second module and the feature value list M3 of the third module do not match, it means that the feature value of the interface module 1 in the feature vector table of the IPC managed by NVR 20 will be misjudged, resulting in misjudged interface parameters. At this time, NVR 20 can re-obtain the interface parameters of each data interaction interface in interface module 1 from IPC 23 to correct the misjudged interface parameters.

[0091] In this way, through multiple rounds of keep-alive detection, the probability of misjudging interface parameters due to possible misjudgment of feature values ​​is accumulated to near infinitesimal until the possible misjudged interface parameters are corrected.

[0092] According to the misjudgment correction method in this example embodiment, taking an interface limit of 1000 data interaction interfaces for a single IPC, a preset vector table length m of 9586 bits, and 7 hash functions n as an example, the misjudgment rate is 0.01. After performing f rounds of keep-alive detection, the misjudgment rate changes to 0.01^f, that is, as f continues to increase, the misjudgment rate will decrease exponentially, thereby ensuring that misjudgments of interface parameters can be corrected in a timely manner.

[0093] The interface parameter acquisition method provided in this invention, on the one hand, uses a hash function to convert relevant interface parameters of the front-end monitoring device into feature values ​​and stores these feature values ​​in a feature vector table. It then uses feature value comparison to quickly filter and reuse duplicate interface parameters of the connected monitoring devices, and re-acquires non-duplicate data. This effectively reduces the amount of network interaction data between the back-end electronic devices and the front-end monitoring devices, improving the stability of the monitoring devices and the overall performance of the system. On the other hand, by introducing a dynamic keep-alive detection and misjudged data correction mechanism, it effectively ensures the correctness of data interaction, guaranteeing the correct and stable operation of the entire monitoring system even under high-voltage network environments. While effectively reducing the amount of network interaction data between the front-end monitoring devices and the back-end electronic devices, it also improves the stability of data interaction, reduces network load, and increases data transmission efficiency.

[0094] The interface parameter acquisition device provided by the present invention is described below. The interface parameter acquisition device described below and the interface parameter acquisition method described above can be referred to in correspondence.

[0095] Figure 4 An exemplary schematic diagram of the interface parameter acquisition device provided in an embodiment of the present invention is shown, with reference to... Figure 4 As shown, the interface parameter acquisition device may include: an information acquisition module 410, used to acquire the first interface parameter feature information of the first monitoring device when the first monitoring device is detected to be connected to the front end; a feature matching module 420, used to determine whether there is a first target feature information in the first interface parameter feature information that matches the second interface parameter feature information of the connected second monitoring device; and a parameter copying module 430, used to copy the target interface parameter of the target data interaction interface in the second monitoring device when the first target feature information exists in the first interface parameter feature information, and to determine the copied target interface parameter as the interface parameter of the first data interaction interface corresponding to the first target feature information in the first monitoring device; wherein, the target data interaction interface is a data interaction interface that matches the first data interaction interface.

[0096] In one example embodiment, the first interface parameter feature information includes a list of feature values ​​corresponding to each second data interaction interface in the first monitoring device; correspondingly, the feature matching module 420 may include: a first determining unit, configured to determine whether there is a first feature value in the second interface parameter feature information that matches the feature value list; and a second determining unit, configured to determine, if there is a first feature value in the second interface parameter feature information, that there is first target feature information in the first interface parameter feature information that matches the second interface parameter feature information; wherein, the first target feature information is a list of feature values ​​that matches the first feature value; and the target data interaction interface is the second data interaction interface corresponding to the matching feature value list.

[0097] In one example embodiment, the first interface parameter feature information further includes a first feature vector table of the first monitoring device and a first module feature value list corresponding to each interface module of the first monitoring device. The interface module includes at least one second data interaction interface of the same interface type. The first module feature value list is determined based on the feature value list of each second data interaction interface in the interface module. Correspondingly, the first determining unit includes: a first determining subunit, used to determine whether the first feature vector table is the same as the second feature vector table in the second interface parameter feature information; a second determining subunit, used to determine, for each interface module, whether there is a second feature value in the second feature vector table that matches the first module feature value list of the interface module if the first feature vector table is different from the second feature vector table; and a third determining subunit, used to determine that there is a first feature value in the second interface parameter feature information that matches the feature value list if the second feature value exists in the second feature vector table, wherein the first feature value is the second feature value, and the first data interaction interface is all the second data interaction interfaces included in the interface module.

[0098] In one example embodiment, the first determining unit further includes: a fourth determining subunit, configured to, in the case that no second feature value in the second feature vector table matches the feature value list of the first module of the interface module, determine whether there is a third feature value in the second feature vector table that matches the feature value list corresponding to the third data interaction interface for each third data interaction interface in the interface module; and a fifth determining subunit, configured to, in the case that a third feature value exists in the second feature vector table, determine that a first feature value in the second interface parameter feature information matches the feature value list, and determine the third data interaction interface as the first data interaction interface, wherein the first feature value is the third feature value.

[0099] In one example embodiment, the first module feature value list corresponding to each interface module of the first monitoring device is obtained by concatenating the feature value lists of each second data interaction interface in the interface module and performing a hash transformation; the first feature vector table is generated by storing the feature values ​​in each feature value list and the feature values ​​in each first module feature value list into a vector table.

[0100] In one example embodiment, the interface parameter acquisition device further includes: a parameter acquisition module, used to acquire interface parameters of the data interaction interface corresponding to the second target feature information from the first monitoring device for the second target feature information that does not match the second interface parameter feature information in the first interface parameter feature information.

[0101] In one example embodiment, the interface parameter acquisition device further includes a detection module, which is configured to: after determining that the target interface parameter to be copied is the interface parameter of the first data interaction interface corresponding to the first target feature information in the first monitoring device, for the second interface module in the second monitoring device, concatenate the feature value list of each data interaction interface in the second interface module, and add timestamp information to the concatenated feature value list to obtain a first feature value list to be processed; wherein, the interface parameters of each data interaction interface in the second interface module are copied by the first interface module in the first monitoring device; perform a hash transformation on the first feature value list to be processed to obtain a second module feature value list corresponding to the second interface module; if the second module feature value list is inconsistent with the third module feature value list, re-acquire the interface parameters corresponding to each data interaction interface in the first interface module from the first monitoring device; wherein, the third module feature value list is obtained by the first monitoring device concatenating the feature value lists of each data interaction interface in the first interface module, adding timestamp information to the concatenated feature value list, and performing a hash transformation on the second feature value list to be processed obtained after adding timestamp information.

[0102] Figure 5 An example is a schematic diagram of the structure of an electronic device, such as... Figure 5 As shown, the electronic device may include a processor 510, a communication interface 520, a memory 530, and a communication bus 540, wherein the processor 510, the communication interface 520, and the memory 530 communicate with each other through the communication bus 540. The processor 510 may call logical instructions in the memory 530 to execute the interface parameter acquisition method provided in any of the above method embodiments.

[0103] For example, processor 510 may include a central processing unit (CPU), a microprocessor, a network processor (NP), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0104] For example, the communication bus 540 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc.

[0105] Furthermore, the logical instructions in the aforementioned memory 530 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0106] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the interface parameter acquisition method provided in any of the above method embodiments.

[0107] In another aspect, the present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to perform the interface parameter acquisition method provided in any of the above method embodiments.

[0108] For example, computer-readable storage media include non-transitory computer-readable storage media.

[0109] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0110] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0111] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. An interface parameter acquisition method, characterized by, include: Upon detecting that the front end is connected to the first monitoring device, the first interface parameter feature information of the first monitoring device is obtained; Determine whether there is a first target feature information in the first interface parameter feature information that matches the second interface parameter feature information of the connected second monitoring device; If the first target feature information exists in the first interface parameter feature information, copy the target interface parameter of the target data interaction interface in the second monitoring device, and determine the copied target interface parameter as the interface parameter of the first data interaction interface corresponding to the first target feature information in the first monitoring device; wherein, the target data interaction interface is a data interaction interface that matches the first data interaction interface; Wherein, the first interface parameter feature information includes a list of feature values ​​corresponding to each second data interaction interface in the first monitoring device; determining whether there is first target feature information in the first interface parameter feature information that matches the second interface parameter feature information of the connected second monitoring device includes: Determine whether there is a first feature value in the second interface parameter feature information that matches the feature value list; If the first feature value exists in the second interface parameter feature information, it is determined that there is a first target feature information in the first interface parameter feature information that matches the second interface parameter feature information; wherein, the first target feature information is the list of feature values ​​that match the first feature value; and the target data interaction interface is the second data interaction interface corresponding to the matching feature value list.

2. The interface parameter acquisition method of claim 1, wherein, The first interface parameter feature information also includes a first feature vector table of the first monitoring device and a first module feature value list corresponding to each interface module of the first monitoring device. The interface module includes at least one second data interaction interface of the same interface type. The first module feature value list is determined based on the feature value list of each second data interaction interface in the interface module. Determining whether there is a first feature value in the second interface parameter feature information that matches the feature value list includes: Determine whether the first feature vector table is the same as the second feature vector table in the second interface parameter feature information; If the first feature vector table is different from the second feature vector table, for each interface module, it is determined whether there is a second feature value in the second feature vector table that matches the first module feature value list of the interface module; If the second feature value exists in the second feature vector table, it is determined that there is a first feature value in the second interface parameter feature information that matches the feature value list, wherein the first feature value is the second feature value, and the first data interaction interface is all the second data interaction interfaces included in the interface module.

3. The interface parameter acquisition method according to claim 2, characterized in that, Also includes: If there is no second feature value in the second feature vector table that matches the first module feature value list of the interface module, for each third data interaction interface in the interface module, it is determined whether there is a third feature value in the second feature vector table that matches the feature value list corresponding to the third data interaction interface; If the third feature value exists in the second feature vector table, it is determined that there is a first feature value in the second interface parameter feature information that matches the feature value list, and the third data interaction interface is determined as the first data interaction interface, wherein the first feature value is the third feature value.

4. The interface parameter acquisition method according to claim 2, characterized in that, The first module feature value list corresponding to each interface module of the first monitoring device is obtained by concatenating the feature value lists of each second data interaction interface in the interface module and then performing a hash transformation. The first feature vector table is generated by storing the feature values ​​from each of the feature value lists and the feature values ​​from each of the first module feature value lists into a vector table.

5. The interface parameter acquisition method according to claim 1, characterized in that, Also includes: For second target feature information in the first interface parameter feature information that does not match the second interface parameter feature information, obtain the interface parameters of the data interaction interface corresponding to the second target feature information from the first monitoring device.

6. The interface parameter acquisition method according to any one of claims 1 to 5, characterized in that, After determining the copied target interface parameters as the interface parameters of the first data interaction interface corresponding to the first target feature information in the first monitoring device, the method further includes: For the second interface module in the second monitoring device, the feature value list of each data interaction interface in the second interface module is concatenated, and timestamp information is added to the concatenated feature value list to obtain the first feature value list to be processed; wherein, the interface parameters of each data interaction interface in the second interface module are copied by the first interface module in the first monitoring device. The first list of feature values ​​to be processed is hashed to obtain the second module feature value list corresponding to the second interface module. If the feature value list of the second module is inconsistent with the feature value list of the third module, the interface parameters corresponding to each data interaction interface in the first interface module are re-obtained from the first monitoring device; wherein, the feature value list of the third module is obtained by the first monitoring device by concatenating the feature value lists of each data interaction interface in the first interface module, adding the timestamp information to the concatenated feature value list, and performing a hash transformation on the second feature value list to be processed obtained after adding the timestamp information.

7. An interface parameter acquisition device, characterized in that, include: The information acquisition module is used to acquire the first interface parameter feature information of the first monitoring device when the front end is detected to be connected to the first monitoring device. The feature matching module is used to determine whether there is a first target feature information in the first interface parameter feature information that matches the second interface parameter feature information of the connected second monitoring device; The parameter copying module is used to copy the target interface parameters of the target data interaction interface in the second monitoring device when the first target feature information exists in the first interface parameter feature information, and to determine the copied target interface parameters as the interface parameters of the first data interaction interface corresponding to the first target feature information in the first monitoring device; wherein, the target data interaction interface is a data interaction interface that matches the first data interaction interface; The first interface parameter feature information includes a list of feature values ​​corresponding to each second data interaction interface in the first monitoring device; the feature matching module is specifically used for: Determine whether there is a first feature value in the second interface parameter feature information that matches the feature value list; if the first feature value exists in the second interface parameter feature information, determine whether there is a first target feature information in the first interface parameter feature information that matches the second interface parameter feature information; wherein, the first target feature information is the feature value list that matches the first feature value; the target data interaction interface is the second data interaction interface corresponding to the matching feature value list.

8. 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 computer program, it implements the interface parameter acquisition method as described in any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the interface parameter acquisition method as described in any one of claims 1 to 6.