Interaction method and device of intelligent converged terminal and sensing device, equipment and medium

Abstract

The application provides an interaction method and device of a smart fusion terminal and a sensing device, equipment and a medium, and belongs to the technical field of intelligent device interaction. The method comprises the following steps: establishing a communication link with a target sensing device; obtaining target interaction data between the smart fusion terminal and the target sensing device based on an initial data security interaction strategy through the communication link; extracting device communication feature data and data types based on the target interaction data; determining a target time delay requirement based on the device communication feature data and the data types, determining a target data security interaction strategy based on the target time delay requirement and a target sensing device type of the target sensing device; processing initial transmission data to be transmitted based on the target data security interaction strategy to obtain target transmission data, and sending the target transmission data to the target sensing device through the communication link. The application can balance the interaction security and efficiency between the smart fusion terminal and the sensing device, and meet the security interaction requirement of the edge layer of power distribution Internet of Things.

Description

Technical Field

[0001] This application belongs to the field of intelligent device interaction technology, and more specifically, it relates to the interaction method, device, equipment and medium between intelligent fusion terminal and sensing device. Background Technology

[0002] The intelligent converged terminal is the core control unit of the distribution network edge layer. It is responsible for aggregating data from sensing devices and issuing control commands, and also has data processing and security protection functions. Sensing devices refer to the terminal devices in the distribution network used to collect operational data or execute control commands. They are the foundation for the digital monitoring and control of the distribution network.

[0003] With the advancement of digital transformation of power distribution networks, the interaction needs between intelligent integrated terminals and sensing devices are becoming increasingly frequent. It is necessary to achieve real-time data acquisition and control command issuance, while ensuring the security and reliability of the interaction process.

[0004] In existing technologies, the interaction between terminals and sensing devices often adopts a unified security strategy without dynamically adapting to the real-time communication requirements. This leads to an imbalance between security and efficiency, affecting the continuity of data acquisition in the power distribution network and the reliability of control commands, and failing to meet the security interaction requirements of the edge layer of the power distribution Internet of Things. Summary of the Invention

[0005] The purpose of this application is to provide a method, device, equipment, and medium for interaction between intelligent converged terminals and sensing devices, so as to balance the security and efficiency of interaction between intelligent converged terminals and sensing devices and meet the security interaction requirements of the edge layer of the power distribution Internet of Things.

[0006] A first aspect of this application provides an interaction method between an intelligent fusion terminal and a sensing device, applied to an intelligent fusion terminal, comprising:

[0007] In response to the detection of a device access signal from the distribution network equipment, the system determines whether the distribution network equipment is a target sensing device based on the device access signal. If the distribution network equipment is a target sensing device, a communication link is established with the target sensing device.

[0008] Through the communication link, target interaction data between the intelligent fusion terminal and the target sensing device is acquired within the first time period based on the initial data security interaction strategy; device communication feature data and data types are extracted based on the target interaction data.

[0009] The target latency requirement is determined based on the device communication characteristic data and data type. The target data security interaction strategy is determined based on the target latency requirement and the target sensing device type. The data transmission parameters corresponding to the target data security interaction strategy are different from the data transmission parameters corresponding to the initial data security interaction strategy.

[0010] Based on the target data security interaction strategy, the initial transmission data to be transmitted is processed to obtain the target transmission data, and then the target transmission data is sent to the target sensing device through the communication link.

[0011] A second aspect of this application provides an interaction device between an intelligent fusion terminal and a sensing device, applied to an intelligent fusion terminal, comprising:

[0012] The communication link establishment module is used to respond to the detection of a device access signal from the distribution network equipment, determine whether the distribution network equipment is a target sensing device based on the device access signal, and establish a communication link with the target sensing device if the distribution network equipment is a target sensing device.

[0013] The interactive data analysis module is used to acquire target interaction data between the intelligent fusion terminal and the target sensing device within the first time period through the communication link, based on the initial data security interaction strategy; and to extract device communication feature data and data types based on the target interaction data.

[0014] The interaction strategy analysis module is used to determine the target latency requirement based on device communication characteristic data and data type, and to determine the target data security interaction strategy based on the target latency requirement and the target sensing device type; the data transmission parameters corresponding to the target data security interaction strategy are different from the data transmission parameters corresponding to the initial data security interaction strategy.

[0015] The data transmission module is used to process the initial transmission data to be transmitted based on the target data security interaction strategy, obtain the target transmission data, and send the target transmission data to the target sensing device through the communication link.

[0016] A third aspect of this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement the steps of the above-described method for interaction between an intelligent fusion terminal and a sensing device.

[0017] In a fourth aspect of this application, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the steps of the above-described method for interaction between an intelligent fusion terminal and a sensing device.

[0018] The beneficial effects of the interaction method, apparatus, device, and medium between the intelligent fusion terminal and sensing device provided in this application embodiment are as follows:

[0019] This application embodiment first completes the pre-collection of target interaction data using an initial data security interaction strategy to ensure basic interaction security during the device access phase. Then, based on the device communication characteristic data and data type of the collected target interaction data, the target latency requirement is determined to ensure that the latency requirement fully matches the actual business and device capabilities. Furthermore, since the inherent functions of different types of devices determine their upper limit for adapting to security strategies, this application embodiment combines device type with the target data security interaction strategy to achieve on-demand adjustment.

[0020] In summary, the embodiments of this application improve the continuity and security of data acquisition in the distribution network by dynamically adjusting the security interaction strategy, ensuring that the interaction between the intelligent fusion terminal and the sensing device not only meets security requirements but also adapts to the diverse business scenarios of the distribution network, providing strong support for the stable operation of the edge layer of the distribution Internet of Things. Attached Figure Description

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

[0022] Figure 1 A flowchart illustrating the interaction method between an intelligent fusion terminal and a sensing device provided in an embodiment of this application;

[0023] Figure 2 A structural block diagram of an interaction device between an intelligent fusion terminal and a sensing device provided in an embodiment of this application;

[0024] Figure 3 This is a schematic block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0025] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0026] It is understood that in the embodiments of this application, if user information and other related data are involved, user permission or consent is required when the embodiments of this application are applied to specific products or technologies, and the collection, use and processing of related data must comply with relevant laws, regulations and standards.

[0027] It should be noted that the terms "first," "second," etc., used in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in sequences other than those illustrated or described herein.

[0028] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating an interaction method between an intelligent fusion terminal and a sensing device according to an embodiment of this application. The method can be applied to an intelligent fusion terminal. Specifically, the method may include steps S101 to S104.

[0029] S101: In response to detecting a device access signal from the distribution network equipment, determine whether the distribution network equipment is a target sensing device based on the device access signal. If the distribution network equipment is a target sensing device, establish a communication link with the target sensing device.

[0030] In this embodiment, the intelligent converged terminal (hereinafter referred to as the terminal) is the core control unit of the distribution network edge layer, responsible for aggregating data from distribution network equipment and issuing control commands. The intelligent converged terminal combines data processing, security protection, and multi-device collaborative management functions, serving as a crucial hub connecting distribution network equipment with the upper-level master station. Distribution network equipment refers to electrical equipment used in the distribution network system, specifically including devices for data acquisition, control, and monitoring. Examples include smart meters, smart circuit breakers, distribution substation monitoring gateways, distributed power supply access units, and transformer monitoring devices. Distribution network equipment is a fundamental component for the digital operation of the distribution network. Device access signals refer to physical signals representing the device's access intention sent through physical interfaces such as RS485 and LoRa when the distribution network equipment attempts to establish a connection with the intelligent converged terminal. Specifically, device access signals may include level changes and frequency band modulation signals.

[0031] Target sensing devices refer to power distribution network sensing devices pre-configured by the intelligent converged terminal that require data interaction and business collaboration. These target sensing devices are the objects with which the intelligent converged terminal interacts with data. The communication link refers to the logical connection channel established between the intelligent converged terminal and the target sensing devices for data transmission and command interaction. The communication link ensures the stability and security of data transmission and is the foundation for subsequent data interaction.

[0032] This embodiment ensures that the intelligent fusion terminal establishes communication links only with legitimate target sensing devices that require interaction, avoiding the access of illegal or irrelevant power distribution network devices that occupy system resources and reducing communication congestion and security risks caused by invalid links. At the same time, this embodiment ensures the security and targeting of subsequent interactions by first determining the legitimacy of the device before establishing the link, thereby improving the efficiency and reliability of power distribution network edge layer interactions.

[0033] For example, the intelligent converged terminal monitors the interface status in real time through its configured physical interface modules, such as RS485 interface modules and LoRa wireless modules. The wired interface can monitor interface level changes, and when a low-level signal lasting more than 100 milliseconds is detected, it is determined to be a potential device access signal; the wireless interface can monitor modulation signals in preset frequency bands such as the 470MHz band of LoRa, and when a signal waveform conforming to the communication protocol of the power distribution network equipment is captured, it is determined to be a potential device access signal.

[0034] The intelligent converged terminal matches the corresponding underlying communication protocol based on the detected device access signal type, such as RS485 corresponding to the DL / T645 protocol and LoRa corresponding to the LoRaWAN protocol, and simultaneously generates an access detection command. The access detection command may include information such as the terminal identifier and detection code. The intelligent converged terminal then transmits the device access signal to the power distribution network equipment through the physical interface that detected the device access signal.

[0035] The intelligent converged terminal can be preset with a time limit of 500 milliseconds. If a response confirmation frame is received from the distribution network equipment within this time limit, and the device identifier contained in the response confirmation frame conforms to the preset target sensing device identifier rules (such as including a specific area code or device type code), then the distribution network equipment is determined to be a target sensing device. If no response confirmation frame is received or the device identifier contained in the response confirmation frame does not conform to the preset target sensing device identifier rules, then it is determined to be a non-target sensing device, and no further operation is performed.

[0036] After confirming that the distribution network equipment is the target sensing device, the intelligent fusion terminal can read the initial root key corresponding to this type of target sensing device from its built-in security module and send a key negotiation request to the target sensing device through the physical interface. Upon receiving the request, the target sensing device decrypts it using its own pre-set root key and returns a negotiation response. The intelligent fusion terminal generates a temporary session key based on the random numbers exchanged between the two parties. Subsequently, the intelligent fusion terminal sends a link establishment confirmation command. The target sensing device receives and verifies the validity of the link establishment confirmation command and returns a confirmation response. At this point, the communication link between the intelligent fusion terminal and the target sensing device is established, and subsequent data interaction can be performed through this link.

[0037] S102: Obtain target interaction data between the intelligent fusion terminal and the target sensing device within the first time period through the communication link based on the initial data security interaction strategy; extract device communication feature data and data type based on the target interaction data.

[0038] In this embodiment, the initial data security interaction strategy refers to the security protection scheme adopted by the terminal and the target sensing device during the initial data acquisition phase. The initial data security interaction strategy may include mechanisms such as encryption and verification to ensure the security of the target interaction data. The first time period refers to the fixed collection duration set by the intelligent fusion terminal for acquiring the initial interaction data, ensuring that the amount of collected data is sufficient to support subsequent feature extraction. Target interaction data refers to all data exchanged and transmitted between the intelligent fusion terminal and the target sensing device within the first time period. Device communication feature data are parameters extracted from the target interaction data that reflect the communication patterns of the devices, such as data upload cycle and data frame length. Data type is the classification of the target interaction data according to its business attributes, such as control commands, monitoring data, and statistical data; the data type reflects the business purpose of the data.

[0039] This embodiment first ensures the security of initial data through an initial data security interaction strategy, then collects target interaction data during the first time period, and finally extracts the communication characteristics and data types of the target interaction data. This scheme can accurately grasp the device capabilities and business requirements, laying the foundation for subsequent determination of target latency requirements and strategy matching, and avoiding blind adjustments to the security interaction strategy without data support. This embodiment can obtain sufficient interaction data through the initial security strategy, providing a basis for subsequent accurate adaptation strategies.

[0040] For example, after the communication link is established, the intelligent fusion terminal can call the initial data security interaction policy from the built-in security policy library. This initial data security interaction policy may include a 128-bit standard AES encryption algorithm, a 32-bit timestamp anti-replay mechanism, and a complete MAC verification. The intelligent fusion terminal starts the first time period timing (e.g., set to 1 hour) and sends data acquisition instructions to the target sensing device at a preset acquisition frequency. The data acquisition instructions may include acquisition dimensions (such as current, voltage, and device status). The target sensing device transmits real-time operating data to the terminal through the communication link according to the data acquisition instructions. The terminal sorts the received data by timestamp and stores it in a local buffer.

[0041] After the first time period ends, the terminal reads all target interaction data from the local buffer and extracts device communication characteristic data. Specifically, the terminal can count the time intervals of continuous data transmission to calculate the average data upload cycle; the terminal can also count the payload bytes of each data item to calculate the average data frame length. Simultaneously, the terminal parses the data type identifier field in the data frame and, in conjunction with distribution network business rules, classifies the data into types such as control commands, monitoring data, and statistical data for subsequent determination of target latency requirements.

[0042] In this embodiment, the target interaction data includes multiple units of interaction data arranged in timestamp order; the multiple units of interaction data arranged in timestamp order include multiple data sent from the intelligent fusion terminal to the target sensing device and multiple data sent from the target sensing device to the intelligent fusion terminal; based on the target interaction data, device communication feature data and data types are extracted, specifically including:

[0043] Calculate the time difference between units of interactive data at every two adjacent timestamps in the target interactive data, and use the average of all time differences as the target data upload cycle;

[0044] Calculate the number of data bytes in each unit of interactive data in the target interactive data, and take the average number of data bytes in all units of interactive data as the target data frame length;

[0045] The target data upload period and target data frame length are used as device communication characteristic data.

[0046] Parse the business type identifiers of all unit interaction data in the target interaction data, and ensure a one-to-one correspondence between the business type identifiers and data types;

[0047] Based on the business type identifier of all unit interaction data, the number of unit interaction data corresponding to each data type is counted, and the data type with the most unit interaction data is taken as the data type of the target interaction data.

[0048] In this embodiment, unit interaction data refers to a single data unit in the first interaction data, divided by timestamp, containing independent data transmitted in a single transaction between the intelligent fusion terminal and the target sensing device. Time difference refers to the timestamp difference between two adjacent unit interaction data in the first interaction data, reflecting the interval between adjacent data transmissions. The target data upload cycle is obtained by averaging all time differences, reflecting the average interval of data transmission by the target sensing device. Data byte count refers to the storage byte length of a single unit interaction data, reflecting the size of a single data transmission. The target data frame length is obtained by averaging the data byte count of all unit interaction data, reflecting the average frame size of data transmitted by the device in normal operation. The service type identifier is a fixed field in the unit interaction data used to identify service attributes, and it has a one-to-one correspondence with the data type, serving as the basis for determining the data type of the first interaction data.

[0049] This embodiment calculates the average time difference to obtain the target data upload cycle, which can avoid the misleading effect of extreme intervals on the device's communication pattern and truly reflect the stable transmission rhythm of the device. This embodiment calculates the average number of data bytes as the target data frame length, which can smooth the byte fluctuation of individual data and reflect the normal data volume of the device. The combination of the two can characterize the device's communication capability.

[0050] Considering that the types of services primarily transmitted by the device during the first time period better reflect actual interaction needs, the most frequent data types are selected to avoid misjudgments caused by a few occasional data types. This majority-based selection logic ensures that data types match the device's core business scenarios, making subsequent determinations of target latency requirements and target data security interaction strategies more realistic and preventing a disconnect between strategy and scenario.

[0051] For example, taking the target sensing device as a low-voltage feeder monitoring unit (monitoring type) and the first time period as 1 hour (3600 seconds) as an example, the specific steps are as follows:

[0052] The intelligent fusion terminal retrieves the initial interaction data within one hour from the local cache, and splits it into 358 units of interaction data according to the timestamp. It is assumed that this includes 179 current acquisition commands issued by the terminal and 179 current monitoring data uploaded by the monitoring unit. The intelligent fusion terminal removes two units of interaction data with duplicate timestamps due to retransmission, retains 356 valid units of interaction data, and arranges them in order of timestamp.

[0053] The terminal sequentially extracts the timestamps of two adjacent valid unit interaction data, calculates the timestamp difference, sums all time differences to obtain 21610 seconds, divides by 355 to obtain an average of 60.87 seconds, and determines the target data upload cycle of this monitoring unit to be 60.87 seconds. The terminal parses the byte length of each valid unit interaction data, and counts the total number of bytes of 356 unit interaction data to be 15258 bytes, divides by 356 to obtain an average of 42.86 bytes, and determines the target data frame length to be 42.86 bytes.

[0054] Assume the service type identifiers include 0x01, 0x02, ..., 0x06, where 0x01, 0x02, 0x03, 0x04, 0x05, and 0x06 correspond to control commands, fault alarms, periodic monitoring data, status query responses, historical statistical data, and configuration responses, respectively. The terminal reads the service type identifier from each valid unit of interactive data, counts the number of unit interactive data corresponding to each service type identifier, sorts the number of unit interactive data corresponding to each service type identifier in descending order, selects the service type identifier with the largest number, and determines the type corresponding to this service type identifier as the data type of the first interactive data based on the correspondence between the service type identifier and the data type.

[0055] If two or more service type identifiers have the same number of identifiers and all are the maximum (i.e., tied for the highest number), then the service type identifier with the highest priority is selected as the dominant identifier according to the preset service priority rules. The priorities from highest to lowest are: fault alarms, control commands, periodic monitoring data, status query responses, configuration responses, and historical statistics.

[0056] S103: Determine the target latency requirement based on the device communication characteristic data and data type; determine the target data security interaction strategy based on the target latency requirement and the target sensing device type; the data transmission parameters corresponding to the target data security interaction strategy are different from the data transmission parameters corresponding to the initial data security interaction strategy.

[0057] In this embodiment, the target latency requirement refers to the time limit standard set for data transmission. The target data security interaction strategy refers to a security protection scheme customized for the target latency requirement and the target sensing device type. It can encompass updated encryption, anti-replay, and integrity verification mechanisms, used to ensure data security while adapting to device capabilities and real-time business requirements. The target data security interaction strategy is an optimized scheme distinct from the initial data security interaction strategy. Data transmission parameters refer to the specific technical indicators supporting the implementation of the security interaction strategy. These may include anti-replay priority, integrity verification range, non-repudiation configuration, encryption algorithm, upper limit of verification data percentage, upper limit of anti-replay time, and non-repudiation function enable threshold. Different security interaction strategies correspond to different data transmission parameters to achieve precise adaptation. The target sensing device type refers to the device category classified according to the core functions of the target sensing device. For example, it may include metering, monitoring, control, and access types. Different types of devices have different computing power levels and data processing requirements, affecting the selection of the target data security interaction strategy.

[0058] This embodiment addresses the security and efficiency imbalance caused by the adoption of a unified security strategy in existing technologies, achieving precise adaptation of the security strategy. First, it determines the target latency requirement based on device communication characteristic data and data type. This is because device communication characteristic data reflects the actual data processing and transmission capabilities of the device, while data type reflects the real-time requirements of the business. Combining these two factors avoids setting unreasonable latency standards that are detached from device capabilities and business scenarios. Next, this embodiment determines the target data security interaction strategy based on the target sensing device type. This is because different types of devices have different functional characteristics (e.g., control devices require rapid response, while metering devices require reliable data), necessitating a strategy that aligns with the device's functional positioning. This embodiment explicitly states that the data transmission parameters corresponding to the target data security interaction strategy differ from the initial data security interaction strategy. This is because the initial data security interaction strategy is only used for basic adaptation, while the target data security interaction strategy needs to be optimized for specific scenarios, ultimately ensuring that security protection matches interaction efficiency, device characteristics, and business requirements.

[0059] The beneficial effects of this embodiment are that it can avoid the problems of high real-time service timeout and low computing power device overload caused by the unified strategy, so that the target data security interaction strategy can not only adapt to the device communication capability and service latency requirements, but also fit the characteristics of the target sensing device type. Furthermore, the parameter differences from the initial data security interaction strategy ensure the accuracy of the strategy, improve the security and efficiency of the interaction between intelligent fusion terminals and sensing devices in the distribution network, and meet the operational needs of diverse business scenarios.

[0060] In this embodiment, the device communication characteristic data includes the target data upload period and the target data frame length; determining the target latency requirement based on the device communication characteristic data and data type specifically includes:

[0061] If the data type is a control command or a fault alarm, then the latency level is determined to be Level 1.

[0062] If the data type is periodic monitoring data or status query response, then the latency level is determined to be Level 2;

[0063] If the data type is historical statistics or configuration response, the latency level is determined to be the third level; the initial latency corresponding to the first level is less than the initial latency corresponding to the second level, and the initial latency corresponding to the second level is less than the initial latency corresponding to the third level.

[0064] The device's real-time processing capability coefficient is calculated based on the target data upload cycle and the target data frame length.

[0065] The target latency requirement is determined based on the initial latency corresponding to the latency level and the device's real-time processing capability coefficient.

[0066] In this embodiment, the first level refers to the latency level corresponding to data types such as control commands or fault alarms. It represents the highest real-time requirement among the three latency levels, suitable for emergency service scenarios in the distribution network requiring millisecond-level responses. The second level refers to the latency level corresponding to data types such as periodic monitoring data or status query responses. Its real-time requirement falls between the first and third levels, suitable for routine monitoring service scenarios in the distribution network requiring minute-level responses. The third level refers to the latency level corresponding to data types such as historical statistical data or configuration responses. It has the lowest real-time requirement, suitable for non-emergency service scenarios in the distribution network without real-time transmission needs. Initial latency refers to the pre-set base latency value for each latency level (first, second, and third levels). It serves as the benchmark for subsequently adjusting the target latency requirement based on the device's real-time processing capability coefficient, and satisfies the relationship: first-level initial latency < second-level initial latency < third-level initial latency. The device's real-time processing capability coefficient is a parameter that quantifies the data processing and transmission capabilities of the target sensing device. A larger device real-time processing capability coefficient value indicates stronger device processing capabilities, providing a quantitative basis for latency adjustment.

[0067] This embodiment ensures that the target latency requirement aligns with the real-time demands of power distribution network services while also adapting to the actual processing capabilities of the target sensing devices. Considering that the real-time requirements differ depending on the service value of different data types (e.g., control commands or fault alarms require millisecond-level emergency responses, while historical statistical data has no real-time transmission pressure), this embodiment categorizes latency levels according to data type, setting three levels with sequentially increasing initial latency. Considering that the target data upload cycle reflects the device's transmission rhythm and the target data frame length reflects the volume of data transmitted in a single transmission, this embodiment combines both to calculate the device's real-time processing capability coefficient, jointly quantifying the device's carrying capacity. This embodiment combines the initial latency with the device's real-time processing capability coefficient to determine the target latency, avoiding overloading the device by solely determining latency based on service requirements or deviating from service needs by solely determining latency based on device requirements, ensuring that the latency requirement is scientific and feasible.

[0068] In this embodiment, calculating the device's real-time processing capability coefficient based on the target data upload cycle and the target data frame length specifically includes: calculating the device's real-time processing capability coefficient using a first coefficient calculation formula based on the target data upload cycle and the target data frame length; the first coefficient calculation formula is:

[0069]

[0070] Where K is the real-time processing capacity coefficient of the equipment. and These are the weighting coefficients. , This represents the upper limit of the historical data upload cycle. This is the lower limit of the historical data upload cycle. For the target data upload cycle, This represents the upper limit of the historical data frame length. This is the lower limit of the historical data frame length. The target data frame length.

[0071] In this embodiment, the first coefficient calculation formula refers to the mathematical formula used to calculate the real-time processing capability coefficient of the device. It is calculated by combining the target data upload cycle, the target data frame length, and the upper and lower limits of historical data, and then adding a weighting coefficient to ensure that the coefficient objectively reflects the actual capability of the device. The weighting coefficient is used to adjust the influence weight of the target data upload cycle and the target data frame length in the calculation of the device's real-time processing capability coefficient, and can be preset according to the characteristics of the distribution network equipment and business needs. The upper limit of the historical data upload cycle refers to the maximum value of the target sensing device's data upload cycle obtained based on historical operating data statistics, reflecting the historical limit range of the device's upload cycle. The lower limit of the historical data upload cycle refers to the minimum value of the target sensing device's data upload cycle obtained based on historical operating data statistics. The upper limit of the historical data frame length refers to the maximum value of the target sensing device's data frame length obtained based on historical operating data statistics, reflecting the historical limit range of the device's data frame length. The lower limit of the historical data frame length refers to the minimum value of the target sensing device's data frame length obtained based on historical operating data statistics.

[0072] In this embodiment, the target latency requirement is determined based on the latency level and the device's real-time processing capability coefficient. Specifically, this includes: determining the initial latency and latency threshold range based on the latency level; and adjusting the initial latency based on the device's real-time processing capability coefficient and latency threshold range to obtain the target latency requirement.

[0073] In this embodiment, the latency threshold range refers to the range of initial latency that can be adjusted for each latency level. It is a constraint condition for adjusting the initial latency in combination with the device's real-time processing capability coefficient, ensuring that the adjusted target latency requirement is both compatible with the device's capabilities and does not deviate from the real-time requirements of the corresponding level.

[0074] This embodiment uses the target data upload cycle and target data frame length as core inputs, and combines the upper and lower limits of historical data upload cycles and historical data frame lengths to calculate the device's real-time processing capability coefficient through a first coefficient calculation formula. This transforms the device's data transmission rhythm and single data volume into quantifiable capability indicators. This embodiment determines the initial latency and latency threshold range based on the latency level corresponding to the business scenario, and dynamically adjusts the initial latency within the latency threshold range based on the device's real-time processing capability coefficient to finally obtain the target latency requirement.

[0075] This embodiment quantifies the real-time processing capability of the device through a first coefficient calculation formula and sets the initial latency according to the latency level to ensure that the requirements match the differences in business real-time performance. This embodiment also adds a latency threshold range to prevent excessive adjustment from deviating from the business positioning. The combination of the two ensures that the target latency requirement is both adapted to the actual carrying capacity of the device and does not deviate from the core business requirements, laying the foundation for subsequent matching of accurate target data security interaction strategies and avoiding an imbalance between security and efficiency.

[0076] In this embodiment, the first coefficient calculation formula is based on the target data upload period and the target data frame length. First, the standardized ratios of the two dimensions are calculated separately, and then they are weighted and summed to obtain the device's real-time processing capability coefficient. Specifically, regarding the target data upload period dimension, the target data upload period is subtracted from the upper limit of the historical data upload period, and the difference is divided by the difference between the upper and lower limits of the historical data upload period to obtain the standardized ratio for this dimension, mapping the target data upload period to the 0-1 range. Regarding the target data frame length dimension, the target data frame length is subtracted from the upper limit of the historical data frame length, and the difference is divided by the difference between the upper and lower limits of the historical data frame length to obtain another standardized ratio, similarly mapping the target data frame length to the 0-1 range. Finally, two weighted coefficients that sum to 1 are used to assign weights to the two standardized ratios, and the weighted ratios are summed to obtain the device's real-time processing capability coefficient.

[0077] This calculation logic aligns with the core influencing factors of a device's real-time processing capability. Specifically, the shorter the target data upload cycle, the higher the data transmission frequency and the stronger the response of the device per unit time. When the target data upload cycle is close to the historical lower limit (optimal transmission rhythm), the standardized ratio is close to 1, indicating strong capability in this dimension; when it is close to the historical upper limit (worst rhythm), the ratio is close to 0, indicating weak capability, and the capability in this dimension can be quantified. The shorter the target data frame length, the smaller the amount of data processed by the device per transaction and the lighter the pressure. When the target data frame length is close to the historical lower limit (optimal processing volume), the standardized ratio is close to 1, indicating strong capability; when it is close to the historical upper limit (worst volume), the ratio is close to 0, indicating weak capability, and the capability in this dimension can be quantified. The weighting coefficients are allocated according to the distribution network scenario. If transmission efficiency is emphasized, the target data upload cycle dimension is given greater weight. By integrating the contributions of the two dimensions, the final result can comprehensively reflect the device's real-time processing capability.

[0078] For example, taking three typical target sensing devices at the edge layer of the power distribution network (control type: smart circuit breaker, monitoring type: temperature and humidity gateway in the power distribution room, and metering type: smart energy meter) as an example, the implementation process of S103 may include:

[0079] (1) The intelligent fusion terminal performs first interactive data collection for 1 hour (first time period) on 3 types of devices through the established communication link, splits the collected first interactive data into unit interactive data according to the timestamp, and calculates the average value of data upload period and average value of data frame length based on the unit interactive data, and obtains the target data upload period and target data frame length respectively.

[0080] Assuming the calculation shows that the smart circuit breaker transmits control commands / status feedback once per second, the target data upload cycle is 1 second, a single frame contains the device ID and command code, and the target data frame length is 24 bytes; the temperature and humidity gateway in the substation uploads temperature and humidity data once every 2 minutes, the target data upload cycle is 120 seconds, a single frame contains the monitoring value and timestamp, and the target data frame length is 48 bytes; and the smart energy meter uploads electricity consumption data once per hour, the target data upload cycle is 3600 seconds, a single frame contains the metering value and statistical time period, and the target data frame length is 60 bytes.

[0081] This embodiment can parse the business type identifier of unit interaction data and count the most frequent type. Assuming the statistics show that "control commands" from smart circuit breakers account for 93%, making them the most frequent data type; "periodic monitoring data" from temperature and humidity gateways account for 90%, making them the most frequent data type; and "historical statistical data" from smart meters account for 96%, making them the most frequent data type.

[0082] (2) The intelligent fusion terminal calls the built-in "data type-latency level mapping table" configuration parameters:

[0083] Intelligent circuit breaker (data type: control command) → Latency level 1, initial latency 50 milliseconds (adapting to millisecond-level response), latency threshold range 40-60 milliseconds;

[0084] Temperature and humidity gateway (data type: periodic monitoring data) → Latency level 2, initial latency 300 milliseconds (adapted to minute-level response), latency threshold range 250-350 milliseconds;

[0085] Smart energy meter (data type: historical statistics) → Latency level 3, initial latency 5 seconds (adapting to non-real-time requirements), latency threshold range 4.5-5.5 seconds.

[0086] (3) The intelligent fusion terminal calls the first coefficient calculation formula, presets the upper limit of the historical data upload period to 12 hours (43200 seconds) and the lower limit to 0.5 seconds, the upper limit of the historical data frame length to 128 bytes and the lower limit to 16 bytes, and the weight coefficients α=0.6 (focusing on the upload period) and β=0.4 (focusing on the frame length). Substituting these values ​​into the calculation, we get: intelligent circuit breaker: K≈0.85, temperature and humidity gateway: K≈0.5, intelligent energy meter: K≈0.2.

[0087] (4) The intelligent fusion terminal adjusts the latency within the threshold range according to the rule of lowering the latency for high coefficients and raising the latency for low coefficients. Specifically, for the intelligent circuit breaker (K=0.85), the initial latency is reduced from 50 milliseconds to 45 milliseconds to compress the response time by utilizing high processing power; for the temperature and humidity gateway (K=0.5), the initial latency is increased from 300 milliseconds to 320 milliseconds to reserve processing redundancy; for the intelligent energy meter (K=0.2), the initial latency is increased from 5 seconds to 5.2 seconds to adapt to the low computing power rhythm.

[0088] (5) The intelligent fusion terminal, based on the target latency requirements and device type, calls the built-in policy library to create parameter differences with the initial data security interaction policy (assuming 10 rounds of AES encryption, full-frame verification, and ECC non-repudiation enabled). Specifically, for the intelligent circuit breaker (45 milliseconds, control type), the data transmission parameters of the matched target data security interaction policy are: 8 rounds of AES encryption, verification only of "device ID + instruction code", and ECC non-repudiation disabled. For the temperature and humidity gateway (320 milliseconds, monitoring type), the data transmission parameters of the matched target data security interaction policy are: 10 rounds of AES encryption, full-frame verification, and ECC non-repudiation disabled. For the smart energy meter (5.2 seconds, metering type), the data transmission parameters of the matched target data security interaction policy are: 10 rounds of AES encryption, full-frame verification, and ECC non-repudiation enabled, achieving precise adaptation.

[0089] S104: Based on the target data security interaction strategy, process the initial transmission data to be transmitted to obtain the target transmission data, and send the target transmission data to the target sensing device through the communication link.

[0090] In this embodiment, steps S101-S104 can be triggered and executed according to a preset fixed cycle. After determining the target data security interaction strategy based on the target latency requirements and the target sensing device type, the interaction method between the intelligent fusion terminal and the sensing device further includes: generating a data security interaction instruction based on the target data security interaction strategy, and sending the data security interaction instruction to the target sensing device; the data security interaction instruction is used to instruct the target sensing device on the method of receiving target transmission data and the method of sending the transmission data to be sent to the intelligent fusion terminal.

[0091] In this embodiment, the initial transmission data to be transmitted refers to the raw service data that the intelligent fusion terminal is about to send to the target sensing device. The target transmission data refers to the final transmittable data obtained after the initial transmission data has been processed by the target data security interaction strategy (such as encryption and verification). The data security interaction command refers to the command generated by the intelligent fusion terminal based on the target data security interaction strategy and used for synchronizing interaction rules.

[0092] The consideration behind this embodiment is to ensure that the interaction rules between the intelligent fusion terminal and the target sensing device are consistent, avoiding data transmission failures or security vulnerabilities caused by mismatched processing methods between the two parties. This embodiment first sends data security interaction instructions to synchronize rules, allowing the target sensing device to prepare for receiving and sending in advance; this embodiment then processes the initial transmission data to obtain the target transmission data and sends it, ensuring that data transmission complies with security policies, ultimately achieving efficient and secure interaction between the two parties.

[0093] For example, taking the target sensing device as a control-type intelligent circuit breaker, with the initial data security interaction strategy being 10 rounds of AES encryption, full-frame verification, and non-repudiation enabled, and the target data security interaction strategy being 8 rounds of AES encryption, verification only of device ID + control command code, and non-repudiation disabled, the specific implementation process of processing the initial transmission data to be transmitted based on the target data security interaction strategy to obtain the target transmission data and sending the target transmission data to the target sensing device through the communication link is as follows:

[0094] (1) The intelligent fusion terminal acquires the target transmission data for the intelligent circuit breaker, assuming it includes the device ID (001), control command code (opening), operation timestamp (2025XXXXXX) and operator number (OP001), with a total data length of 32 bytes.

[0095] (2) The intelligent fusion terminal retrieves the data transmission parameters of the target data security interaction policy from the policy library: the encryption algorithm is 8 rounds of AES, the integrity verification range is device ID + control command code (6 bytes in total), the anti-replay priority is 5, the anti-repudiation configuration is disabled, the upper limit of the verification data ratio is 60%, the upper limit of the anti-replay time is 2ms, and the anti-repudiation function enable threshold is none.

[0096] (3) The intelligent fusion terminal uses an 8-round AES algorithm to encrypt the 32-byte content of the target transmitted data and generate 32-byte encrypted data; it performs integrity verification, calculates CRC32 check value only for device ID (3 bytes) and control command code (3 bytes), and obtains 4-byte check code; it generates an anti-replay field, using a 16-bit hardware random number (takes 1.5ms, which does not exceed the upper limit) as an anti-replay identifier; because the anti-repudiation configuration is disabled, the ECC signature operation is not performed.

[0097] (4) The intelligent fusion terminal concatenates 32 bytes of encrypted data, 4 bytes of verification code and 2 bytes of anti-replay field in the format of “encrypted data + verification code + anti-replay field” to form target transmission data with a total length of 38 bytes.

[0098] (5) The intelligent fusion terminal confirms that the communication link is an RS485-1 port, and sends 38 bytes of target transmission data to the intelligent circuit breaker according to the 1-second transmission period in the target strategy. After receiving the data, the intelligent circuit breaker parses the data according to the target strategy, completes the encryption data decryption, check code verification and anti-replay check, and executes the corresponding control operation after confirming that the data is valid.

[0099] For example, taking the target sensing device as a control type intelligent circuit breaker, the specific implementation process of generating and sending data security interaction commands during the interaction between the intelligent fusion terminal and the device is as follows:

[0100] (1) The intelligent fusion terminal extracts the policy details corresponding to the intelligent circuit breaker of the control class from the built-in policy library and clarifies the key parameters used to generate instructions. Among them, the method parameters for receiving target transmission data may include the receiving port identifier (RS485-1), data parsing order (first check code → then encrypted data → finally anti-replay field), verification triggering time (initiate integrity verification within 10ms after receiving data), and abnormal data processing rules (discard and report error frames if verification fails); the method parameters for sending the interactive data to be sent to the terminal may include the sending period (1 second / time), data encapsulation format (device ID + service data + timestamp), sending baud rate (9600bps), and retransmission mechanism (retransmit after 300ms if no terminal confirmation frame is received, with a maximum of 2 retransmissions).

[0101] (2) The data security interaction command adopts a structured format design, which includes four parts: First, the command header (2 bytes), the first byte is the command type identifier, and the second byte is the command version; Second, the receiving mode configuration section (8 bytes), which is filled with the receiving port identifier (corresponding to RS485-1), the data parsing sequence code (corresponding to the preset parsing logic), the verification trigger delay (corresponding to 10ms), and the exception handling identifier (corresponding to "discard + feedback error"); Third, the sending mode configuration section (10 bytes), which is filled with the sending period (corresponding to 1 second), the encapsulation format code (corresponding to the preset encapsulation logic), the baud rate identifier (corresponding to 9600bps), the retransmission interval (corresponding to 300ms), and the maximum number of retransmissions (corresponding to 2 times); Fourth, the check section (2 bytes), which performs CRC16 calculation on all bytes of the command header, the receiving mode configuration section, and the sending mode configuration section to obtain the check code and ensure the integrity of the command transmission.

[0102] (3) The intelligent fusion terminal sends the generated data security interaction command to the control type intelligent circuit breaker through the established RS485 communication link; after receiving the command, the intelligent circuit breaker parses each field of the command, configures the segment parameters according to the receiving method to initialize the receiving module (bind RS485-1 port, set 10ms check delay), configures the segment parameters according to the sending method to initialize the sending module (set 1 second sending period, 9600bps baud rate), and generates a command receiving confirmation frame (including device ID and confirmation code) after completing the configuration, and sends it back to the terminal.

[0103] (4) After the intelligent fusion terminal receives the confirmation frame returned by the circuit breaker, it determines that the data security interaction instruction has been successfully sent. When the terminal sends the target transmission data, the circuit breaker completes the data verification and parsing according to the receiving method indicated by the instruction. When the circuit breaker returns the equipment status data, it sends it at regular intervals according to the sending method indicated by the instruction, so as to realize the unified interaction rules between the two parties.

[0104] As can be concluded from the above, in the device access phase, this embodiment determines whether the distribution network equipment is a target sensing device by using the device access signal. It establishes communication links only with legitimate target sensing devices, avoiding the access of illegal or irrelevant devices that occupy system resources, reducing communication congestion caused by invalid links, lowering security risks, and ensuring efficient utilization of resources at the distribution network edge layer. In the initial data acquisition phase, this embodiment ensures data security with an initial data security interaction strategy. Combined with the acquisition of sufficient target interaction data in the first time period, it accurately extracts device communication characteristic data and data types, providing reliable data support for subsequent determination of target latency requirements and strategy matching, avoiding unfounded and blind strategy adjustments.

[0105] When determining the target latency requirements, this embodiment classifies latency levels according to data type and adjusts them in conjunction with the real-time processing capability coefficient of the equipment. This ensures that the latency requirements not only match the differences in business real-time performance but also adapt to the actual processing capabilities of the equipment, avoiding timeouts for high-real-time services or overload of low-computing-power equipment. Based on the target latency requirements and equipment type, this embodiment determines the target data security interaction strategy, forming differentiated parameter adaptations with the initial strategy to balance security protection and interaction efficiency. Simultaneously, it synchronizes the interaction rules between the two parties through data security interaction commands, avoiding transmission failures caused by mismatched processing methods and ensuring smooth interaction. Ultimately, this achieves secure, accurate, and efficient interaction between the intelligent fusion terminal and the target sensing device, meeting the diverse operational needs of the power distribution network.

[0106] In one embodiment of this application, determining whether a power distribution network device is a target sensing device based on a device access signal includes:

[0107] If the device access signal is a wired signal, the physical channel and underlying communication protocol are determined based on the interface number corresponding to the device access signal, and an access detection command is generated.

[0108] If the device access signal is a wireless signal, the physical channel and underlying communication protocol are matched based on the physical characteristics of the device access signal, and an access detection command is generated.

[0109] Based on the underlying communication protocol, access probe commands are sent to the distribution network equipment through a physical channel; the access probe commands are used to instruct the distribution network equipment to return a response confirmation frame through the physical channel.

[0110] If a response confirmation frame is received within the first time limit, the distribution network equipment is identified as the target sensing device.

[0111] If no response confirmation frame is received within the first time limit, the access detection command is resent to the distribution network equipment after the first time interval; if a response confirmation frame is received within the second time limit, the distribution network equipment is identified as the target sensing device; if no response confirmation frame is received within the second time limit, the distribution network equipment is determined not to be the target sensing device.

[0112] In this embodiment, the device access signal refers to the signal generated when distribution network equipment accesses the smart converged terminal, used to trigger the target sensing device judgment process. Wired signal refers to the device access signal transmitted via physical cables. Wireless signal refers to the device access signal transmitted via wireless frequency bands. Interface number refers to the unique number identifying the physical interface during wired access. Physical channel refers to the physical link for data transmission. Underlying communication protocol refers to the basic communication rules for interaction between the device and the terminal. Access detection command is a command used to detect whether the device can interact normally. Response confirmation frame refers to the confirmation frame returned by the device after receiving the detection command. First time limit refers to the maximum time to wait for a response after the first detection command is sent. First time interval refers to the interval between resending the detection command after the first detection timeout. Second time limit refers to the maximum time to wait for a response after resending the detection command. Both the first and second time limits can be set based on actual needs based on experience.

[0113] In this embodiment, a differentiated strategy is adopted to determine the physical channel and underlying communication protocol based on the differences between wired and wireless access methods for distribution network equipment. This ensures the accuracy of channel and protocol matching and avoids detection failures due to confusion in access methods. This embodiment sets up access detection commands and response confirmation frames, which can verify the communication availability of the device through bidirectional interaction, rather than relying solely on signal presence, thus improving the reliability of target device identification. This embodiment sets a first time limit to avoid indefinite waiting affecting efficiency. Setting a first time interval and a second time limit is to eliminate misjudgments caused by single transmission interference (such as momentary signal loss), giving the device a second chance to respond. If there is still no response after the second time, it is determined to be a non-target device, balancing identification accuracy and efficiency, ensuring that only devices with normal communication are included in the target sensing device category, laying the foundation for subsequent data interaction.

[0114] For example, taking smart meters (wired access) and LoRa temperature and humidity sensors (wireless access) in a power distribution network as examples, the specific steps are as follows:

[0115] The intelligent fusion terminal detects the device access signal. If the signal is transmitted via an RS485 cable (wired signal), the interface number is read as RS485-01; if the signal is transmitted via the 470MHz LoRa band (wireless signal), the physical characteristics are extracted as LoRa modulation and signal strength -75dBm.

[0116] For wired signals (interface number RS485-01), the smart fusion terminal determines the physical channel as RS485-01 channel and the underlying communication protocol as Modbus-RTU. The smart fusion terminal generates access detection commands based on the Modbus-RTU protocol. The access detection commands may include command identifiers and check codes, and are sent to the smart energy meter through the RS485-01 channel.

[0117] For wireless signals (physical characteristics LoRa), the matching physical channel is the LoRa-03 channel, and the underlying communication protocol is LoRaWAN. The intelligent converged terminal generates access detection commands based on the LoRaWAN protocol and sends them to the temperature and humidity sensor through the LoRa-03 channel.

[0118] In this embodiment, a first time limit can be set to 1 second. If a response confirmation frame is received from the smart energy meter within 1 second, it is determined to be a target sensing device. If no response is received from the temperature and humidity sensor within 1 second, a second detection is initiated. After a first time interval of 2 seconds, the smart fusion terminal resends the access detection command to the temperature and humidity sensor, setting a second time limit of 2 seconds. If a response confirmation frame is received within 2 seconds, it is determined to be a target sensing device. If there is still no response after the second time, it is determined that the device is not a target sensing device.

[0119] This embodiment can accurately match channels and protocols for different access methods of distribution network equipment, avoiding detection errors caused by confusion in access methods. Through two detections and timely control, this embodiment reduces misjudgments caused by momentary interference, improving the accuracy of target sensing device identification. Simultaneously, it avoids infinite waiting, ensuring identification efficiency. Ultimately, only devices with normal communication are listed as target sensing devices, providing a reliable equipment foundation for subsequent secure data interaction and improving the stability of distribution network edge layer device management.

[0120] In one embodiment of this application, a target data security interaction strategy is determined based on the target latency requirements and the target sensing device type, including:

[0121] The anti-replay priority, integrity verification range, and non-repudiation configuration corresponding to the target sensing device type are determined from the mapping table between device type and data transmission parameters. The target sensing device type includes control, monitoring, metering, or access types. The mapping table between device type and data transmission parameters includes the anti-replay priority, integrity verification range, and non-repudiation configuration corresponding to each of the control, monitoring, metering, and access types.

[0122] Determine the encryption algorithm, verification data ratio limit, anti-replay time limit, and anti-repudiation function enable threshold corresponding to the target latency requirement from the mapping table between latency requirements and data transmission parameters.

[0123] The data security interaction strategy is determined based on the anti-replay priority, integrity verification range, anti-repudiation configuration, encryption algorithm, upper limit of verification data ratio, upper limit of anti-replay time consumption, and anti-repudiation function enable threshold.

[0124] In this embodiment, the mapping table between device type and data transmission parameters refers to a pre-stored association table built into the intelligent fusion terminal, which associates different target sensing device types with their corresponding core data transmission parameters. The table includes four device types: control, monitoring, metering, and access. Each type corresponds to a unique anti-replay priority, integrity verification range, and non-repudiation configuration. The mapping table between latency requirements and data transmission parameters refers to a pre-stored association table built into the intelligent fusion terminal, which associates different latency requirements with their corresponding core data transmission parameters. The table includes multiple latency requirement levels, each with different latency upper limit thresholds. Each latency requirement level corresponds to a unique encryption algorithm, upper limit for verification data percentage, upper limit for anti-replay time, and non-repudiation function enable threshold. The anti-replay priority refers to the importance level of the anti-replay mechanism set according to the target sensing device type. For example, it can be set to levels 1-5, with higher values ​​requiring stricter protection. The anti-replay priority reflects the necessity of resisting repeated instruction injection or data retransmission attacks in the device's business scenario. For example, control devices are prone to misoperation due to instruction replay, so the priority can be set to the highest.

[0125] The integrity verification range refers to the range of fields to be verified for interactive data. It is a core parameter to ensure that data is not tampered with. It can be determined in conjunction with the device type. For example, monitoring devices need to verify the entire data frame (including monitoring values ​​and timestamps) to avoid misjudgment of status, while control devices can verify only the core instruction fields to save time. The non-repudiation configuration refers to the setting for whether to enable the non-repudiation function based on the device type, determining whether the data has traceability. For example, metering devices need to enable it because it is related to electricity billing, while control devices can disable it due to high real-time requirements. The maximum percentage of verification data refers to the maximum proportion of verification data to the total data volume of a single frame, set based on the target latency requirements. This controls time consumption by limiting unnecessary verifications. The maximum anti-replay time limit refers to the maximum allowed processing time for anti-replay mechanisms (such as random number generation and timestamp verification) set based on the target latency requirements, ensuring that anti-replay operations do not consume latency budget. The non-repudiation function enable threshold refers to the maximum allowable processing time (including signature and verification) for enabling the non-repudiation function, which is set based on the target latency requirements. It is only enabled when the non-repudiation processing time is lower than this threshold.

[0126] For example, taking two typical target sensing devices in a power distribution network (control type: smart circuit breaker, target latency requirement ≤50ms; metering type: smart energy meter, target latency requirement ≤5s) as an example, the smart fusion terminal executes the data security interaction strategy determination process, and the specific steps are as follows:

[0127] (1) The terminal reads that the target sensing device type of the smart circuit breaker is control type, and retrieves the corresponding parameters from the mapping relationship table between device type and data transmission parameters: anti-replay priority is set to 5 (highest level, because replay of control commands can easily cause false tripping), integrity verification range is set to device ID + control command code (core field, to reduce verification time), and anti-repudiation configuration is set to disabled (to avoid ECC signature crowding out the latency budget).

[0128] The terminal reads that the target sensing device type of the smart energy meter is metering, and retrieves the corresponding parameters from the mapping table between device type and data transmission parameters: anti-replay priority is set to 2 (low level, low risk of replay of historical metering data), integrity verification range is set to the whole data frame (including metering value and statistical period to ensure data reliability), and anti-repudiation configuration is set to enabled (data source needs to be traced to avoid electricity bill disputes).

[0129] (2) For the target latency requirement of the smart circuit breaker ≤50ms, the terminal retrieves the corresponding parameters from the mapping table of latency requirement and data transmission parameters: the encryption algorithm is set to 128-bit simplified AES (8 rounds of iteration, adapted to millisecond-level response), the upper limit of the verification data ratio is set to 60% (not exceeding the range of core fields), the upper limit of anti-replay time is set to 2ms (using 16-bit hardware random number anti-replay), and the anti-repudiation function enable threshold is set to none (because anti-repudiation has been disabled).

[0130] For smart meters with a target latency requirement of ≤5s, the terminal retrieves the corresponding parameters from the mapping table between latency requirement and data transmission parameters: the encryption algorithm is set to 128-bit standard AES (10 rounds of iteration, 5s latency can be carried), the upper limit of the verification data ratio is set to 100% (full frame verification is stress-free), the upper limit of anti-replay time is set to 10ms (using 32-bit timestamps for anti-replay), and the anti-repudiation function enable threshold is set to 50ms (ECC signature + signature verification time ≤30ms, not exceeding the threshold).

[0131] (3) Disable the anti-replay priority 5, integrity verification range device ID + control command code, and anti-repudiation configuration corresponding to the intelligent circuit breaker, and integrate them with the 128-bit simplified AES encryption algorithm, the upper limit of verification data ratio of 60%, the upper limit of anti-replay time of 2ms, and the anti-repudiation function enable threshold to form a dedicated data security interaction strategy for control devices.

[0132] The anti-replay priority 2, integrity verification range of the entire data frame, and anti-repudiation configuration of the smart energy meter are integrated with the 128-bit standard AES encryption algorithm, the upper limit of verification data ratio of 100%, the upper limit of anti-replay time of 10ms, and the anti-repudiation function enable threshold of 50ms to form a dedicated data security interaction strategy for metering devices, and the strategy is determined.

[0133] This embodiment uses two mapping tables to match the parameters corresponding to the device type and latency requirements, which can quickly determine a complete data security interaction strategy that fits the device characteristics and business real-time requirements, avoiding blind parameter configuration; at the same time, it covers multiple types of devices such as control and monitoring devices and different latency requirements, ensuring strategy adaptability, effectively balancing data transmission security and efficiency, and ensuring the stable and reliable interaction of diverse devices in the power distribution network.

[0134] Corresponding to the interaction method between the intelligent fusion terminal and the sensing device in the above embodiment, Figure 2 This is a structural block diagram of an interaction device between an intelligent fusion terminal and a sensing device according to an embodiment of this application. For ease of explanation, only the parts relevant to the embodiment of this application are shown. (See also...) Figure 2 The interaction device 20 between the intelligent fusion terminal and the sensing device includes: a communication link establishment module 21, an interaction data analysis module 22, an interaction strategy analysis module 23, and a data transmission module 24.

[0135] The communication link establishment module 21 is used to respond to the detection of a device access signal from the distribution network equipment, determine whether the distribution network equipment is a target sensing device based on the device access signal, and establish a communication link with the target sensing device if the distribution network equipment is a target sensing device.

[0136] Interactive data analysis module 22 is used to acquire target interaction data between the intelligent fusion terminal and the target sensing device within the first time period through the communication link based on the initial data security interaction strategy; and to extract device communication feature data and data types based on the target interaction data.

[0137] The interaction strategy analysis module 23 is used to determine the target latency requirement based on the device communication characteristic data and data type, and to determine the target data security interaction strategy based on the target latency requirement and the target sensing device type; the data transmission parameters corresponding to the target data security interaction strategy are different from the data transmission parameters corresponding to the initial data security interaction strategy.

[0138] The data transmission module 24 is used to process the initial transmission data to be transmitted based on the target data security interaction strategy, obtain the target transmission data, and send the target transmission data to the target sensing device through the communication link.

[0139] In one embodiment of this application, when determining whether a power distribution network device is a target sensing device based on a device access signal, the communication link establishment module 21 is specifically used for:

[0140] If the device access signal is a wired signal, the physical channel and underlying communication protocol are determined based on the interface number corresponding to the device access signal, and an access detection command is generated.

[0141] If the device access signal is a wireless signal, the physical channel and underlying communication protocol are matched based on the physical characteristics of the device access signal, and an access detection command is generated.

[0142] Based on the underlying communication protocol, access probe commands are sent to the distribution network equipment through a physical channel; the access probe commands are used to instruct the distribution network equipment to return a response confirmation frame through the physical channel.

[0143] If a response confirmation frame is received within the first time limit, the distribution network equipment is identified as the target sensing device.

[0144] If no response confirmation frame is received within the first time limit, the access detection command is resent to the distribution network equipment after the first time interval; if a response confirmation frame is received within the second time limit, the distribution network equipment is identified as the target sensing device; if no response confirmation frame is received within the second time limit, the distribution network equipment is determined not to be the target sensing device.

[0145] In one embodiment of this application, the device communication characteristic data includes the target data upload period and the target data frame length; when determining the target latency requirement based on the device communication characteristic data and data type, the interaction strategy analysis module 23 is specifically used for:

[0146] If the data type is a control command or a fault alarm, then the latency level is determined to be Level 1.

[0147] If the data type is periodic monitoring data or status query response, then the latency level is determined to be Level 2;

[0148] If the data type is historical statistics or configuration response, the latency level is determined to be the third level; the initial latency corresponding to the first level is less than the initial latency corresponding to the second level, and the initial latency corresponding to the second level is less than the initial latency corresponding to the third level.

[0149] The device's real-time processing capability coefficient is calculated based on the target data upload cycle and the target data frame length.

[0150] The target latency requirement is determined based on the initial latency corresponding to the latency level and the device's real-time processing capability coefficient.

[0151] In one embodiment of this application, the interaction strategy analysis module 23, when calculating the device's real-time processing capability coefficient based on the target data upload cycle and the target data frame length, is specifically used for:

[0152] Based on the target data upload cycle and the target data frame length, the device's real-time processing capability coefficient is calculated using the first coefficient calculation formula.

[0153] The formula for calculating the first coefficient is:

[0154]

[0155] Where K is the real-time processing capacity coefficient of the equipment. and These are the weighting coefficients. , This represents the upper limit of the historical data upload cycle. This is the lower limit of the historical data upload cycle. For the target data upload cycle, This represents the upper limit of the historical data frame length. This is the lower limit of the historical data frame length. The target data frame length.

[0156] In one embodiment of this application, when determining the target latency requirement based on the latency level and the device's real-time processing capability coefficient, the interaction strategy analysis module 23 is specifically used to: determine the initial latency and latency threshold range based on the latency level; and adjust the initial latency based on the device's real-time processing capability coefficient and latency threshold range to obtain the target latency requirement.

[0157] In one embodiment of this application, when determining the target data security interaction strategy based on the target latency requirements and the target sensing device type of the target sensing device, the interaction strategy analysis module 23 is specifically used for:

[0158] The anti-replay priority, integrity verification range, and non-repudiation configuration corresponding to the target sensing device type are determined from the mapping table between device type and data transmission parameters. The target sensing device type includes control, monitoring, metering, or access types. The mapping table between device type and data transmission parameters includes the anti-replay priority, integrity verification range, and non-repudiation configuration corresponding to each of the control, monitoring, metering, and access types.

[0159] Determine the encryption algorithm, verification data ratio limit, anti-replay time limit, and anti-repudiation function enable threshold corresponding to the target latency requirement from the mapping table between latency requirements and data transmission parameters.

[0160] The data security interaction strategy is determined based on the anti-replay priority, integrity verification range, anti-repudiation configuration, encryption algorithm, upper limit of verification data ratio, upper limit of anti-replay time consumption, and anti-repudiation function enable threshold.

[0161] In one embodiment of this application, after determining the target data security interaction strategy based on the target latency requirements and the target sensing device type, the interaction device 20 between the intelligent fusion terminal and the sensing device further includes: an interaction instruction module, used to generate a data security interaction instruction based on the target data security interaction strategy and send the data security interaction instruction to the target sensing device; the data security interaction instruction is used to instruct the target sensing device on the method of receiving target transmission data and the method of sending the transmission data to be sent to the intelligent fusion terminal.

[0162] See Figure 3 , Figure 3 This is a schematic block diagram of an electronic device provided according to an embodiment of this application. Figure 3 The electronic device 300 in this embodiment may include one or more processors 301, one or more input devices 302, one or more output devices 303, and one or more memories 304. The processors 301, input devices 302, output devices 303, and memories 304 communicate with each other via a communication bus 305. The memories 304 store computer programs, including program instructions. The processors 301 execute the program instructions stored in the memories 304. Specifically, the processors 301 are configured to invoke the program instructions to perform the functions of the modules in the aforementioned device embodiments, for example... Figure 2The functions of the communication link establishment module 21, interactive data analysis module 22, interactive strategy analysis module 23, and data transmission module 24 are illustrated. In this embodiment, the electronic device 300 can be the intelligent fusion terminal shown above.

[0163] It should be understood that, in the embodiments of this application, the processor 301 may be a central processing unit (CPU), but it may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0164] Input device 302 may include a touchpad, a fingerprint sensor (for collecting the user's fingerprint information and fingerprint orientation information), a microphone, etc., and output device 303 may include a display (LCD, etc.), a speaker, etc.

[0165] The memory 304 may include read-only memory and random access memory, and provides instructions and data to the processor 301. A portion of the memory 304 may also include non-volatile random access memory. For example, the memory 304 may also store information about the type of sensing device.

[0166] In specific implementations, the processor 301, input device 302, and output device 303 described in the embodiments of this application can execute the implementation methods described in the embodiments of the interaction method between the intelligent fusion terminal and the sensing device provided in the embodiments of this application, or they can execute the implementation methods of the electronic device 300 described in the embodiments of this application, which will not be repeated here.

[0167] In another embodiment of this application, a computer-readable storage medium is provided. This computer-readable storage medium stores a computer program, which includes program instructions. When executed by a processor, the program instructions implement all or part of the processes in the methods described above. Alternatively, the computer program can instruct related hardware to complete the process. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include any entity or device capable of carrying computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0168] The computer-readable storage medium can be an internal storage unit of the electronic device in any of the foregoing embodiments, such as a hard disk or memory of the electronic device. The computer-readable storage medium can also be an external storage device of the electronic device, such as a plug-in hard disk, smart media card (SMC), secure digital card (SD), flash card, etc., provided on the electronic device. Furthermore, the computer-readable storage medium can include both internal and external storage units of the electronic device. The computer-readable storage medium is used to store computer programs and other programs and data required by the electronic device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0169] Those skilled in the art will recognize that the modules / units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0170] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the electronic devices and units described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0171] In the several embodiments provided in this application, it should be understood that the disclosed electronic devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For instance, the division of modules / units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules, units, or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces or modules / units, or it may be an electrical, mechanical, or other form of connection.

[0172] The modules / units described as separate components may or may not be physically separate. Similarly, the components shown as modules / units may or may not be physical modules / units; they may be located in one place or distributed across multiple network modules / units. Some or all of the modules / units can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0173] Furthermore, the functional modules / units in the various embodiments of this application can be integrated into one processing module / unit, or each module / unit can exist physically separately, or two or more modules / units can be integrated into one module / unit. The integrated modules / units described above can be implemented in hardware or in the form of software functional modules / units.

[0174] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for interaction between an intelligent fusion terminal and a sensing device, characterized in that, Applications in intelligent converged terminals, including: In response to the detection of a device access signal from a power distribution network device, the system determines whether the power distribution network device is a target sensing device based on the device access signal. If the power distribution network device is a target sensing device, a communication link is established with the target sensing device. Through the communication link, target interaction data between the intelligent fusion terminal and the target sensing device is obtained within a first time period based on an initial data security interaction strategy; device communication feature data and data type are extracted based on the target interaction data. The target latency requirement is determined based on the device communication characteristic data and the data type. The target data security interaction strategy is determined based on the target latency requirement and the target sensing device type. The data transmission parameters corresponding to the target data security interaction strategy are different from the data transmission parameters corresponding to the initial data security interaction strategy. Based on the target data security interaction strategy, the initial transmission data to be transmitted is processed to obtain the target transmission data, and the target transmission data is sent to the target sensing device through the communication link; The device communication characteristic data includes the target data upload period and the target data frame length; Determining the target latency requirement based on the device communication characteristic data and the data type includes: If the data type is a control command or a fault alarm, then the latency level is determined to be the first level; If the data type is periodic monitoring data or status query response, then the latency level is determined to be Level 2; If the data type is historical statistics or configuration response, then the latency level is determined to be the third level; the initial latency corresponding to the first level is less than the initial latency corresponding to the second level, and the initial latency corresponding to the second level is less than the initial latency corresponding to the third level; Based on the target data upload cycle and the target data frame length, the device's real-time processing capability coefficient is calculated using the first coefficient calculation formula. The formula for calculating the first coefficient is: Where K is the real-time processing capacity coefficient of the equipment. and These are the weighting coefficients. , This represents the upper limit of the historical data upload cycle. This is the lower limit of the historical data upload cycle. For the target data upload cycle, This represents the upper limit of the historical data frame length. This is the lower limit of the historical data frame length. The target data frame length; The target latency requirement is determined based on the initial latency corresponding to the latency level and the device's real-time processing capability coefficient.

2. The interaction method between the intelligent fusion terminal and the sensing device as described in claim 1, characterized in that, The step of determining whether the power distribution network equipment is a target sensing device based on the device access signal includes: If the device access signal is a wired signal, the physical channel and underlying communication protocol are determined based on the interface number corresponding to the device access signal, and an access detection command is generated. If the device access signal is a wireless signal, then the physical channel and underlying communication protocol are matched based on the physical characteristics of the device access signal, and an access detection command is generated. Based on the underlying communication protocol, the access probe command is sent to the power distribution network equipment through the physical channel; the access probe command is used to instruct the power distribution network equipment to return a response confirmation frame through the physical channel; If the response confirmation frame is received within the first time limit, the power distribution network equipment is identified as the target sensing device. If the response confirmation frame is not received within the first time limit, the access detection command is resent to the distribution network equipment after the first time interval; if the response confirmation frame is received within the second time limit, the distribution network equipment is identified as the target sensing device; if the response confirmation frame is not received within the second time limit, the distribution network equipment is determined not to be the target sensing device.

3. The interaction method between the intelligent fusion terminal and the sensing device as described in claim 1, characterized in that, The determination of the target latency requirement based on the latency level and the device's real-time processing capability coefficient includes: The initial latency and latency threshold range are determined based on the latency level; The initial latency is adjusted based on the device's real-time processing capability coefficient and the latency threshold range to obtain the target latency requirement.

4. The interaction method between the intelligent fusion terminal and the sensing device as described in claim 1, characterized in that, The step of determining the target data security interaction strategy based on the target latency requirements and the target sensing device type includes: The anti-replay priority, integrity verification range, and non-repudiation configuration corresponding to the target sensing device type are determined from the mapping table between device type and data transmission parameters; the target sensing device type includes control type, monitoring type, metering type, or access type; the mapping table between device type and data transmission parameters includes the anti-replay priority, integrity verification range, and non-repudiation configuration corresponding to each of the control type, monitoring type, metering type, and access type. Determine the encryption algorithm, verification data ratio limit, anti-replay time limit, and anti-repudiation function enable threshold corresponding to the target latency requirement from the mapping table between latency requirements and data transmission parameters. The data security interaction strategy is determined based on the anti-replay priority, integrity verification range, anti-repudiation configuration, encryption algorithm, upper limit of verification data ratio, upper limit of anti-replay time consumption, and anti-repudiation function enable threshold.

5. The interaction method between the intelligent fusion terminal and the sensing device as described in claim 1, characterized in that, After determining the target data security interaction strategy based on the target latency requirements and the target sensing device type, the method further includes: Data security interaction instructions are generated based on the target data security interaction strategy, and the data security interaction instructions are sent to the target sensing device. The data security interaction instructions are used to instruct the target sensing device on how to receive target transmission data and how to send the transmission data to be sent to the intelligent fusion terminal.

6. An interactive device for an intelligent fusion terminal and a sensing device, characterized in that, Applications in intelligent converged terminals, including: A communication link establishment module is used to respond to the detection of a device access signal from a power distribution network device, determine whether the power distribution network device is a target sensing device based on the device access signal, and establish a communication link with the target sensing device if the power distribution network device is a target sensing device. The interactive data analysis module is used to acquire target interaction data between the intelligent fusion terminal and the target sensing device within a first time period through the communication link, based on an initial data security interaction strategy; and to extract device communication feature data and data types based on the target interaction data. The interaction strategy analysis module is used to determine the target latency requirement based on the device communication characteristic data and the data type, and to determine the target data security interaction strategy based on the target latency requirement and the target sensing device type; the data transmission parameters corresponding to the target data security interaction strategy are different from the data transmission parameters corresponding to the initial data security interaction strategy. The device communication characteristic data includes the target data upload period and the target data frame length; The interactive strategy analysis module is specifically used to determine the latency level as the first level if the data type is a control command or fault alarm; to determine the latency level as the second level if the data type is periodic monitoring data or status query response; and to determine the latency level as the third level if the data type is historical statistical data or configuration response. The initial latency corresponding to the first level is less than the initial latency corresponding to the second level, and the initial latency corresponding to the second level is less than the initial latency corresponding to the third level. Based on the target data upload cycle and the target data frame length, the module calculates the device's real-time processing capability coefficient using a first coefficient calculation formula. The formula for calculating the first coefficient is: Where K is the real-time processing capacity coefficient of the equipment. and These are the weighting coefficients. , This represents the upper limit of the historical data upload cycle. This is the lower limit of the historical data upload cycle. For the target data upload cycle, This represents the upper limit of the historical data frame length. This is the lower limit of the historical data frame length. The target data frame length; The target latency requirement is determined based on the initial latency corresponding to the latency level and the real-time processing capability coefficient of the device. The data transmission module is used to process the initial transmission data to be transmitted based on the target data security interaction strategy to obtain the target transmission data, and send the target transmission data to the target sensing device through the communication link.

7. A smart fusion terminal, comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 5.

8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 5.

Images