Power data acquisition system and method, device, and computer-readable storage medium

Abstract

The present invention discloses a power data acquisition system and method, equipment, and computer-readable storage medium. The system builds a distributed ECU through an ECU pool and a user mobile phone App, realizes power data acquisition and control information distribution based on the distributed ECU, and can be used as a link backup for the existing power data acquisition system to ensure the normal collection of power data and the real-time distribution of control information when the power line carrier network fails. In addition, the user mobile phone App uses a local communication method to connect to the meter. Compared with the HPLC network, the local communication method has higher communication reliability, and its short-distance communication characteristics also bring it higher transmission security. The present invention is consistent with the existing security design of the power system, and on the basis of maintaining the existing security architecture, it realizes the security, convenience and real-time nature of information interaction.

Description

Technical Field

[0001] The present invention relates to the technical field of power data collection, and in particular, to a power data collection system and method, a device, and a computer-readable storage medium. Background Art

[0002] like Figure 1 As shown in the figure, the data collection of the power system (power consumption data and distribution network data, etc.) is implemented using a cloud, edge, and end architecture, including the power grid cloud platform (such as the power grid master station, etc., hereinafter referred to as the master station), edge-side collection equipment (such as energy controllers, fusion terminals, concentrators, etc., energy controllers are ECUs, and edge-side collection equipment is collectively referred to as ECUs) and end-side metering equipment (such as electric meters, etc., hereinafter referred to as electric meters). The entire communication link is divided into an uplink between the ECU and the master station and a local link between the ECU and the electric meter. The uplink is currently mainly based on the 4G wireless virtual private network provided by telecom operators, and the local link is mainly based on the power line carrier network. The entire link carries the collection of power data and the distribution of control information. However, in actual operation, the power line carrier network will be affected by various uncertain factors, and there may be a temporary failure of the carrier line. At this time, the master station cannot collect power data on the failed line, nor can it send control information to the electric meter on the failed line in time. These problems caused by the reliability of the carrier network have brought great inconvenience to the power grid company and users.

[0003] To solve the above-mentioned problems caused by carrier reliability, it is necessary to back up the carrier line. At present, a common idea is to add a wireless module to the meter and use wireless for link backup, but this will bring huge cost investment and waste of resources, so it is not adopted in actual applications. Another idea is to use mobile Internet to perform link backup when needed, but the secondary system of the power system is strictly security zoned. Production scheduling is in security zone 1, which has the highest security level, data acquisition (i.e., master station) is in security zone 2, office is in information management zone, and Internet-related services are in Internet zone. There is a forward and reverse isolation device between different zones, and there is also a dedicated horizontal isolation device between the internal and external networks. The high-security level area cannot be accessed from the low-security level area. This security design of the power system makes it very difficult to use mobile Internet to back up the Internet of Things, that is, the mobile Internet cannot access the master station. Therefore, finding a power data acquisition solution that not only conforms to the power grid security architecture, but also has the characteristics of real-time, convenient, and economical has become an urgent problem to be solved. Summary of the invention

[0004] The present invention provides a power data acquisition system and method, equipment, and computer-readable storage medium to solve the technical problem that the existing power system cannot realize data acquisition and control information distribution when the carrier network fails.

[0005] According to one aspect of the present invention, there is provided an electric power data acquisition system, comprising a master station, a distributed ECU architecture and an electric meter, wherein the distributed ECU architecture comprises an ECU pool and a user mobile phone App, wherein the ECU pool comprises an ECU server and a plurality of ECU units, wherein the ECU pool and the master station are deployed in an intranet of a power grid, wherein the plurality of ECU units are connected to the master station via a wireless virtual private network, wherein the ECU server is connected to the plurality of ECU units, wherein the ECU server is connected to the user mobile phone App via an operator's public network, wherein the user's mobile phone is connected to the electric meter via a local communication method, wherein the ECU server is used to allocate an ECU unit to each user mobile phone App, and to bind the relationship between the electric meter, the user mobile phone App and the ECU unit, so as to construct a two-way backup communication link from the electric meter to the master station through the user mobile phone App, the ECU server and the corresponding ECU unit in sequence, and wherein the two-way backup communication link is used to perform data acquisition and control information distribution through the two-way backup communication link when a link failure occurs in the power line carrier network.

[0006] Furthermore, the security strategy adopted by the distributed ECU architecture includes: completing two-way identity authentication between the ECU server and the user's mobile phone App, building a secure channel for data transmission between the ECU server and the user's mobile phone App, the ECU server performing application-layer security protection on the information interacted between the user's mobile phone App and the main station, and completing the binding after two-way verification between the main station and the electric meter through the binding request code and the binding reply code.

[0007] Furthermore, the binding request code is generated by the electric meter, and the binding reply code is generated by the master station. The binding request code and the binding reply code are both spliced ​​by an information domain and a verification domain. The information domain includes a nonce value that increases in a cumulative form. The verification domain includes a verification value. The verification value is a hash value calculated by splicing the nonce value with a hidden information domain and a shared key shared between the master station and the electric meter using a hash algorithm. The hidden information domain includes multiple types of information. The electric meter uses the same or different information for splicing calculation when generating the binding request code and the master station uses the same or different information when generating the binding reply code.

[0008] Furthermore, the hidden information field includes at least one of a code type, an electric meter ID, an ECU unit ID, and a current date.

[0009] Furthermore, when allocating an ECU unit to each user mobile phone App, the ECU server calculates the Hash value of the meter ID corresponding to the user mobile phone App, and uses the Hash value to perform a modulus operation on the number of ECU units in the ECU pool to obtain the ECU unit index to be bound.

[0010] In addition, the present invention also provides a power data collection method, which uses the power data collection system as described above and includes the following contents:

[0011] The user downloads the App provided by the power grid and completes the registration;

[0012] Start the master station and ECU pool. Several ECU units access the master station through a wireless virtual private network. The ECU server waits for the user's mobile phone App to access.

[0013] The user's mobile app establishes a connection with the ECU server through the operator's public network;

[0014] The ECU server allocates an ECU unit to the user's mobile app, binds the relationship between the meter, the user's mobile app, and the ECU unit, and builds a two-way backup communication link from the meter to the master station through the user's mobile app, the ECU server, the corresponding ECU unit, and the master station.

[0015] When a link failure occurs in the power line carrier network, data collection and control information delivery are performed via the bidirectional backup communication link.

[0016] Furthermore, the process of binding the relationship between the electric meter, the user mobile phone App, and the ECU unit includes the following contents:

[0017] The user triggers the meter to create a binding request code through the App, and sends it to the main station through the user's mobile phone App, ECU server, and corresponding ECU unit in sequence;

[0018] The master station verifies the binding request code, generates a binding reply code after successful verification, and sends the binding reply code to the ECU server through the ECU unit to notify the ECU server to perform binding;

[0019] The ECU server completes the relationship binding between the ECU unit, the user's mobile phone App, and the electric meter, and sends the binding reply code to the electric meter through the user's mobile phone App;

[0020] The electric meter verifies the binding reply code and accepts the binding after successful verification.

[0021] Furthermore, the process of the ECU server allocating an ECU unit to the user's mobile phone App includes the following:

[0022] The ECU server calculates the hash value of the meter ID, and uses the hash value to perform a modulus operation on the number of ECU units in the ECU pool to obtain the ECU unit index to be bound.

[0023] In addition, the present invention also provides a device, including a processor and a memory, wherein the memory stores a computer program, and the processor is used to execute the steps of the above method by calling the computer program stored in the memory.

[0024] In addition, the present invention also provides a computer-readable storage medium for storing a computer program for collecting power data, wherein the computer program executes the steps of the method described above when running on a computer.

[0025] The present invention has the following effects:

[0026] The power data acquisition system of the present invention builds a distributed ECU through an ECU pool and a user mobile phone App, realizes power data acquisition and control information distribution based on the distributed ECU, and can be used as a link backup for the existing power data acquisition system, ensuring the normal collection of power data and the real-time distribution of control information when the power line carrier network fails. In addition, the user mobile phone App uses a local communication method to connect to the electric meter. Compared with the HPLC network, the local communication method has higher communication reliability, and its short-distance communication characteristics also bring it higher transmission security. The present invention is consistent with the existing security design of the power system, and on the basis of maintaining the existing security architecture, it realizes the security, convenience and real-time nature of information interaction.

[0027] In addition, the power data collection method of the present invention also has the above advantages.

[0028] In addition to the above-described purposes, features and advantages, the present invention has other purposes, features and advantages. The present invention will be further described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The drawings constituting a part of this application are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0030] Figure 1 It is a schematic diagram of the network architecture of the existing power data acquisition system.

[0031] Figure 2 It is a schematic diagram of the network architecture of the power data acquisition system of the preferred embodiment of the present invention.

[0032] Figure 3 It is a flowchart of a power data collection method according to another embodiment of the present invention.

[0033] Figure 4 yes Figure 3 Schematic diagram of a sub-process of step S4 in FIG. DETAILED DESCRIPTION

[0034] The embodiments of the present invention are described in detail below with reference to the accompanying drawings. However, the present invention can be implemented in many different ways as defined and covered below.

[0035] like Figure 2 As shown, a preferred embodiment of the present invention provides an electric power data acquisition system, including a main station, a distributed ECU architecture and an electric meter, the distributed ECU architecture includes an ECU pool and a user mobile phone App, the ECU pool includes an ECU server and a plurality of ECU units, the ECU pool and the main station are deployed in the intranet of the power grid, the plurality of ECU units are connected to the main station through a wireless virtual private network, the ECU server is connected to the plurality of ECU units, the ECU server is connected to the user mobile phone App through the operator's public network, the user's mobile phone is connected to the electric meter through a local communication method, the ECU server is used to allocate an ECU unit to each user's mobile phone App, and bind the relationship between the electric meter, the user's mobile phone App, and the ECU unit to construct a two-way backup communication link from the electric meter through the user's mobile phone App, the ECU server, the corresponding ECU unit to the main station in sequence, which is used for data acquisition and control information issuance through the two-way backup communication link when a link failure occurs in the power line carrier network.

[0036] It can be understood that the secondary system of the power system is strictly divided into security zones. Production dispatch is in security zone 1, which has the highest security level. Data collection (i.e., the master station) is in security zone 2. Office is in the information management zone. Internet-related services are in the Internet zone. There is a forward and reverse isolation device between different zones, and there is also a dedicated horizontal isolation device between the internal and external networks. The high-security zone cannot be accessed from the low-security zone. Under this strict partition, although the existing users (mobile phone apps) interact with the master station through the public network, they are all realized through the power grid data exchange platform. There are multiple data scheduled ferrying time points every day. The data interaction platform packages the data to penetrate the firewall and isolate, thereby realizing the ferrying of data from the public network to the state grid master station system. This security design brings a problem, that is, users cannot interact with the master station in real time through the public network, that is, the data sent by the mobile phone app must be sent to the master station through the exchange platform at a fixed ferrying time point. This results in the inability to send power data to the master station in time through the public network, and the control information interaction between the master station and the meter cannot be completed in real time. This contradiction between security, convenience and real-time performance is also one of the main reasons why user applications cannot truly penetrate the power grid. It directly leads to the inability of users to actively participate in the power grid's production and operation activities such as demand response, and causes the power grid to have insufficient stickiness to users, and the value of the power grid cannot be further enhanced.

[0037] The power data acquisition system of this embodiment builds a distributed ECU architecture through the ECU pool and the user's mobile phone App, replaces the ECU entity of the existing acquisition system, builds the link between the master station, the distributed ECU architecture and the meter, and solves the contradiction between security, convenience and real-time in power data acquisition to a certain extent. Specifically, the master station and the ECU pool are deployed in the power grid intranet, but the master station is deployed in the second security zone of the intranet, and the ECU server needs to be deployed in the fourth security zone. Although they are in the same power grid intranet, the ECU server cannot directly access the master station. However, several ECU units in the ECU pool can directly access the master station in real time through the wireless virtual private network provided by the operator for the power grid, so that the ECU pool also has the ability to access the master station in real time. The user's mobile phone is connected to the electric meter through a local communication method, and the user's mobile phone App can be connected to the ECU server through the operator's public network. The ECU server allocates an ECU unit to each user's mobile phone App and binds the relationship between the electric meter, the user's mobile phone App, and the ECU unit. The bound user's mobile phone App, ECU server, and ECU unit are a distributed ECU relative to the electric meter, thereby constructing a two-way backup communication link from the electric meter to the main station through the user's mobile phone App, ECU server, and corresponding ECU unit in sequence. When the power line carrier network has a link failure, data collection and control information can be sent through the two-way backup communication link. Among them, the local communication method adopted between the user's mobile phone and the electric meter can be any one of Bluetooth, NFC, Wifi, and infrared, and the specific communication method is not specifically limited here. In addition, the number of ECU servers in the ECU pool can be one, two, or more, and centralized processing can be performed by configuring one ECU server, or parallel processing can be performed by at least two ECU servers.

[0038] It can be understood that the power data acquisition system of this embodiment builds a distributed ECU through the ECU pool and the user's mobile phone App, realizes power data acquisition and control information distribution based on the distributed ECU, and can be used as a link backup for the existing power data acquisition system to ensure the normal collection of power data and the real-time distribution of control information when the power line carrier network fails. In addition, the user's mobile phone App uses a local communication method to connect to the meter. Compared with the HPLC network, the local communication method has higher communication reliability, and its short-distance communication characteristics also bring it higher transmission security. The present invention is consistent with the existing security design of the power system, and on the basis of maintaining the existing security architecture, it realizes the security, convenience and real-time nature of information interaction.

[0039] It can be understood that the distributed ECU architecture consists of ECU units, ECU servers, and user mobile phone apps, where the user mobile phone apps are not grid assets, and the user mobile phone communicates with the ECU server through the public network, so the security of the distributed ECU architecture must be improved. The security of the data sent from the distributed ECU to the master station needs to be equal to or higher than the security of the ECU running on site in the existing solution, otherwise it will introduce security risks to the master station. As a preferred embodiment, the security strategy adopted by the distributed ECU architecture specifically includes:

[0040] 1) Complete two-way identity authentication between the ECU server and the user's mobile app. The user of the mobile app must be a user trusted by the power grid;

[0041] 2) A secure channel for data transmission is established between the ECU server and the user's mobile phone App to ensure the confidentiality and integrity of the data transmission;

[0042] 3) The ECU server performs application-layer security protection on the information exchanged between the user's mobile phone App and the main station. The ECU server itself is a security system that can perform application-layer security checks and protection on the protocol data exchanged between the App and the main station;

[0043] 4) The master station and the meter complete the binding after two-way verification through the binding request code and the binding reply code. The master station and the meter on the failed link communicate through the distributed ECU, and the two exchange the binding request code and the binding reply code. Both parties must verify the legitimacy of the source and purpose of the message. For the master station, the binding request code is sent by the meter on the failed link. For the meter, the binding reply code is sent by the master station and sent to itself.

[0044] The present invention uses mobile Internet to back up the power Internet of Things. After sufficient security detection, the mobile Internet data re-enters the power Internet of Things in the ECU pool. The present invention not only complies with the security architecture of the power grid, reuses the existing data interface, but also has the characteristics of real-time, convenience and economy.

[0045] It is understandable that the two-way identity authentication between the ECU server and the user's mobile phone App and the establishment of a secure channel between the two can be completed during the security negotiation between the two. As an option, the ECU server can use TLS one-way authentication server + SMS verification code authentication client to achieve security negotiation. The specific process is:

[0046] The ECU server certificate is pre-installed in the mobile app provided by the power grid to users. The app initiates a TLS connection to the ECU server. During the TLS handshake process, the app uses the pre-installed ECU server certificate to complete the identity authentication of the ECU server and establishes a TLS connection based on one-way authentication. In this process, the app completes the authentication of the ECU server and establishes an encrypted tunnel (TLS channel) between the mobile app and the ECU server. All subsequent data transmission between the mobile app and the ECU server is protected by this encrypted tunnel.

[0047] The mobile app collects user information, including the current mobile phone number, watch ID, etc., and sends it to the ECU server through the TLS channel.

[0048] The ECU server verifies the user information with the master station and confirms that the link where the meter is located is invalid. After confirmation, the ECU server generates a verification code and sends the verification code to the mobile phone App through the operator's SMS network.

[0049] After receiving the verification code, the mobile app sends the verification code back to the ECU server through the TLS channel, and the ECU server completes the authentication of the mobile app. At this point, the two-way authentication security channel between the app and the ECU server is successfully established.

[0050] As another option, the ECU server can also use a digital envelope to achieve security negotiation with the App. Specifically, the mobile App pre-sets the CA certificate and the ECU server certificate. After the user installs the mobile App, he registers with the power grid and obtains his own private key and certificate. During the authentication process, the mobile App and the ECU server exchange certificates and signatures to complete the authentication of their respective identities. The subsequent data interaction between the mobile App and the ECU server is encapsulated in a PKCS#7 digital envelope, and its confidentiality and integrity can be well guaranteed.

[0051] It can be understood that the ECU server completes the binding between the mobile app and the ECU unit, and is responsible for realizing the data interaction between the mobile app and the main station while isolating the mobile app and the main station. The ECU server will first disassemble the protocol data sent by the mobile app, reassemble it and send it to the main station through the ECU unit. At the same time, the ECU server will also disassemble the protocol data sent by the main station, reassemble it and send it to the mobile app.

[0052] At present, the common firewalls are all packet filtering firewalls, which only provide protection at the IP layer and transport layer level. The firewall will not understand the details of the session and cannot provide protection at the application layer. The ECU server in the present invention can grasp the details of the session during the process of protocol disassembly and assembly, and can implement application layer protection, thus solving the problem that the firewall cannot protect the application layer. In addition, the ECU server follows the principle of least privilege, only provides necessary services, discards unrecognized protocol data, disassembles the recognized protocol data, verifies its security and legality, and then reassembles it and forwards it to the main station and mobile phone App. At the same time, the ECU server can also set up black and white lists of users to prevent malicious users from accessing, and provide functions such as user access logs and audits.

[0053] It can be understood that before binding, the master station and the electric meter need to verify their respective identities, that is, the master station needs to confirm that the electric meter to be bound is indeed the electric meter corresponding to the user's mobile phone App, and at the same time, the electric meter needs to confirm that the binding instruction is indeed issued by the master station. The electric meter and the master station complete the identity confirmation between the two through the binding request code and the binding reply code. Among them, the binding process is: after the security negotiation between the mobile phone App and the ECU server is completed, the user operates the mobile phone App to trigger the electric meter to create a binding request code, and sends the binding request code, which reaches the master station via the mobile phone App, the ECU server, and the ECU unit. The master station verifies the request code. After the verification is successful, the master station generates a binding reply code, sends the binding reply code to the ECU server, and notifies the ECU server to bind. The ECU server completes the binding between the ECU unit and the mobile phone App and the electric meter, and sends the binding reply code to the electric meter through the mobile phone App. The electric meter verifies the binding reply code, and accepts the binding after success. When the master station completes the data collection and control information distribution of the electric meter of the failed link, the master station issues a control instruction to unbind, and the ECU server unbinds.

[0054] The binding request code is generated by the electric meter, the binding reply code is generated by the master station, and the binding request code and the binding reply code are both composed of an information domain and a verification domain. The information domain includes a nonce value that increases in an accumulated form, and the verification domain includes a verification value, which is a Hash value calculated by splicing the nonce value with the hidden information domain and the shared key shared between the master station and the electric meter using a Hash algorithm. The hidden information domain includes multiple information, and the electric meter generates the binding request code and the master station generates the binding reply code using the same or different information for splicing calculation. Specifically, the hidden information domain includes at least one of a code type, an electric meter ID, an ECU unit ID, and a current date. The hidden information domain is shared between the master station and the electric meter, and the hidden information domain does not appear in the binding request code, but is used for verification domain generation and verification on both sides, and the data in the information domain and the hidden information domain are protected by the verification domain. The Hash algorithm can also use algorithms such as SHA1, SHA256, and MD5, which are not specifically limited here. The nonce value is used to calculate the verification value of the verification domain of the binding request code, which is increased in a cumulative form, which can enhance the protection of the shared key between the master station and the meter, and at the same time realize the anti-replay function of the binding request code. The verification domain is similar to a lightweight digital signature, which completes the verification of the information domain and the hidden information domain. It concatenates the information domain, the hidden information domain and the shared key, and then calculates its hash value to obtain the verification value. For example, the verification value of the binding request code = MD5 (nonce | code type | table ID | current date | shared key), and the verification value of the binding reply code = MD5 (nonce | code type | ECU unit ID | current date | shared key).

[0055] As an exemplary illustration, the meter uses the code type, meter ID, and current date in the hidden information field for splicing calculation. Specifically, the meter generates a nonce value, which is the previous nonce value plus 1. For example, if the last time was 1234, then this time is 1235. The code type number corresponding to the binding request code is 1, the meter ID is 000000000100, and the current date is 210528, that is, May 28, 2021. The shared key between the meter and the master station is maintained uniformly by the master station and published to the meter. The keys of different meters are unique, such as the key of this meter is 12345678. The meter then concatenates the nonce value, meter ID, current date, and shared key, and calculates the verification value, verification value = MD5 ("1235100000000010021052812345678") = "166c2a3774e5164d4af1f5430a23b56e". Therefore, the binding request code is 1235166c2a3774e5164d4af1f5430a23b56e.

[0056] Then, the master station verifies the binding request code. The master station extracts the nonce value, i.e., 1235, from the binding request code. If the extracted nonce value is 0 and the last nonce value of the meter is 9999, the nonce value is a normal rotation value. If the nonce value is 1 greater than the last nonce value of the meter, the nonce value is a normal increment value. Otherwise, the nonce value is a replay value, and the master station abandons the binding request code. After the master station extracts the nonce value, it concatenates it with the code type, meter ID, current date, and shared key and calculates the verification value, verification value = MD5 ("1235100000000010021052812345678") = "166c2a3774e5164d4af1f5430a23b56e". Then, the master station compares the verification value calculated by it with the verification value in the binding request code to see if they are consistent. If they are consistent, the verification is successful, otherwise the verification fails. Obviously, when the information in the hidden information field on the master station side does not match that on the meter side, such as at least one of the following situations: code type mismatch, meter ID mismatch, current date mismatch, and shared key mismatch, at this time, due to the characteristics of the hash function, the verification values ​​on both sides must be different, and the binding request code verification fails.

[0057] Similarly, as an exemplary explanation, the master station uses the code type, ECU unit ID, and current date in the hidden information domain for splicing calculation. Specifically, the master station extracts the nonce value from the binding request code as the nonce value of this binding reply code, and then splices its code type, ECU unit ID, current date, and shared key. If the code type is a successful binding reply code, the number is 2, and if the code type is a failed binding reply code, the number is 3. The ECU unit ID is the ID of the ECU unit to which the meter is about to be bound, for example, 000000000005, and the current date is 210528. Then calculate the verification value = MD5 ("1235200000000000521052812345678") = "fc6039ba0c8218b7524a624cdba1df51". The binding reply code is 1235fc6039ba0c8218b7524a624cdba1df51.

[0058] Then, the electric meter verifies the binding reply code. The electric meter extracts the nonce value, i.e. 1235, from the binding reply code, and then verifies whether the nonce value is a replay value. If it is verified that the nonce value is not a replay value, the electric meter will splice the extracted nonce value with the code type, the bound ECU unit ID, the current date and the shared key, and calculate the verification value = MD5 ("1235200000000000521052812345678") = "fc6039ba0c8218b7524a624cdba1df51". Then, the electric meter compares the calculated verification value with the verification value contained in the binding reply code. If the two are consistent, the verification is successful, that is, the binding reply code is issued by the master station, and the meter splicing code type is a binding success reply code. In addition, if the verification fails, the code type is the binding failure reply code (i.e. 3), and the above calculation of the verification value is repeated. If the verification is successful, the binding reply code is issued by the master station, and the meter splicing code type is the binding failure reply code.

[0059] It is understandable that the electric meter may use only one or two types of information in the hidden information field for splicing calculation when generating the binding request code and the master station may use only one or two types of information in the hidden information field for splicing calculation when generating the binding reply code. However, the more types of information used, the higher the security.

[0060] It can be understood that the ECU server establishes a binding relationship between the meter, App and the ECU unit in the pool. The binding relationship must be fixed and have the characteristics of discretization. The role of the fixed binding relationship is to enable the master station to find the corresponding ECU unit in the ECU pool when the link where the meter is located fails. The role of the discretization is to enable the meter on the link to be evenly bound to different ECU units in the ECU pool when a link fails. As a preferred embodiment, when the ECU server allocates an ECU unit to each user's mobile phone App, it calculates the Hash value of the meter ID corresponding to the user's mobile phone App, and uses the Hash value to perform a modulus operation on the number of ECU units in the ECU pool to obtain the index of the ECU unit to be bound. For example, assuming that there are 100 ECU units in the ECU pool, the index index of the ECU unit bound to the meter ID 000000000100 is calculated as: index = MD5 ("000000000100") % 100 = 13, then the ECU unit bound to the meter by the ECU server is ECU unit No. 13.

[0061] It is understandable that Figure 3 As shown, another embodiment of the present invention further provides a power data collection method, preferably using the power data collection system as described above, the method comprising the following contents:

[0062] Step S1: The user downloads the App provided by the power grid and completes the registration;

[0063] Step S2: Start the main station and ECU pool, several ECU units access the main station through the wireless virtual private network, and the ECU server waits for the user's mobile phone App to access;

[0064] Step S3: The user's mobile phone App establishes a connection with the ECU server through the operator's public network;

[0065] Step S4: The ECU server allocates an ECU unit to the user mobile phone App, binds the relationship between the electric meter, the user mobile phone App, and the ECU unit, and builds a backup communication link from the electric meter through the user mobile phone App, the ECU server, the corresponding ECU unit to the main station in sequence;

[0066] Step S5: when a link failure occurs in the power line carrier network, data collection and control information delivery are performed via the backup communication link.

[0067] It can be understood that in step S2, after the master station is started, it will automatically maintain a table file for each meter, and the content of the table file includes information such as the meter ID, the shared key between each meter, and the corresponding user's mobile phone number. After the ECU pool is started, several ECU units access the master station through the wireless virtual private network provided by the operator for the power grid, and the ECU server is started and waits for the access of the mobile phone App.

[0068] In addition, in step S3, when establishing a connection between the App and the ECU server, a security negotiation is required to complete a two-way authentication and build an encrypted tunnel between the two. For details, please refer to the above system embodiment.

[0069] It can be understood that the power data collection method of this embodiment builds a distributed ECU through an ECU pool and a user mobile phone App, realizes power data collection and control information distribution based on the distributed ECU, and can be used as a link backup for the existing power data collection system to ensure the normal collection of power data and the real-time distribution of control information when the power line carrier network fails. In addition, the user mobile phone App uses a local communication method to connect to the meter. Compared with the HPLC network, the local communication method has higher communication reliability, and its short-distance communication characteristics also bring it higher transmission security. The present invention is consistent with the existing security design of the power system, and on the basis of maintaining the existing security architecture, it realizes the security, convenience and real-time nature of information interaction.

[0070] It is understandable that Figure 4 As shown, the process of binding the relationship between the electric meter, the user's mobile phone App, and the ECU unit in step S4 includes the following contents:

[0071] Step S41: The user triggers the meter to create a binding request code through the App, and sends it to the main station through the user's mobile phone App, ECU server, and corresponding ECU unit in sequence;

[0072] Step S42: the master station verifies the binding request code, generates a binding reply code after successful verification, and sends the binding reply code to the ECU server through the ECU unit to notify the ECU server to perform binding;

[0073] Step S43: The ECU server completes the relationship binding between the ECU unit, the user's mobile phone App, and the electric meter, and sends the binding reply code to the electric meter through the user's mobile phone App;

[0074] Step S44: The electric meter verifies the binding reply code and accepts the binding after successful verification.

[0075] In addition, the process of the ECU server allocating an ECU unit to the user's mobile phone App in step S4 includes the following:

[0076] The ECU server calculates the hash value of the meter ID, and uses the hash value to perform a modulus operation on the number of ECU units in the ECU pool to obtain the ECU unit index to be bound.

[0077] In addition, in another embodiment of the present invention, the power data collection method further includes the following contents:

[0078] Step S6: After completing the power data collection and control information delivery, the master station issues a control instruction to release the binding relationship. After receiving the control instruction, the ECU server releases the binding relationship between the electric meter, the user's mobile phone App, and the ECU unit.

[0079] It can be understood that the specific implementation process of each step in the embodiment of the method has been correspondingly described in the above-mentioned system embodiment, so it will not be repeated here.

[0080] It can be understood that another embodiment of the present invention further provides a device, including a processor and a memory, wherein the memory stores a computer program, and the processor executes the steps of the above method by calling the computer program stored in the memory.

[0081] It can be understood that another embodiment of the present invention further provides a computer-readable storage medium for storing a computer program for collecting power data, wherein the computer program executes the steps of the method described above when running on a computer.

[0082] The general form of computer readable media includes: floppy disk, flexible disk, hard disk, magnetic tape, any other magnetic media, CD-ROM, any other optical media, punch cards, paper tape, any other physical media with a pattern of holes, random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), flash erasable programmable read-only memory (FLASH-EPROM), any other memory chip or cartridge, or any other medium that can be read by a computer. The instructions can further be transmitted or received by a transmission medium. The term transmission medium can include any tangible or intangible medium that can be used to store, encode or carry instructions for execution by a machine, and includes digital or analog communication signals or other intangible media that facilitate the communication of the above instructions. Transmission media include coaxial cables, copper wire and optical fiber, which include the wires of a bus used to transmit a computer data signal.

[0083] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A power data acquisition system, characterized in that: It includes a main station, a distributed ECU architecture and an electric meter. The distributed ECU architecture includes an ECU pool and a user mobile phone App. The ECU pool includes an ECU server and several ECU units. The ECU pool and the main station are deployed in the intranet of the power grid. The several ECU units are connected to the main station through a wireless virtual private network. The ECU server is connected to the several ECU units. The ECU server is connected to the user mobile phone App through the operator's public network. The user mobile phone App is connected to the electric meter through a local communication method. The ECU server is used to allocate an ECU unit to each user mobile phone App, and bind the relationship between the electric meter, the user mobile phone App, and the ECU unit to build a two-way backup communication link from the electric meter to the main station through the user mobile phone App, the ECU server, the corresponding ECU unit in sequence, which is used for data collection and control information distribution through the two-way backup communication link when a link failure occurs in the power line carrier network. Among them, ECU represents an edge side collection device.

2. The power data acquisition system according to claim 1, characterized in that: The security strategy adopted by the distributed ECU architecture includes: completing two-way identity authentication between the ECU server and the user's mobile phone App, building a secure channel for data transmission between the ECU server and the user's mobile phone App, the ECU server performing application-layer security protection on the information exchanged between the user's mobile phone App and the main station, and completing the binding after the main station and the meter perform two-way verification through the binding request code and the binding reply code.

3. The power data acquisition system according to claim 2, characterized in that: The binding request code is generated by the electric meter, and the binding reply code is generated by the master station. Both the binding request code and the binding reply code are composed of an information field and a verification field. The information field includes a nonce value that increases in a cumulative form. The verification field includes a verification value. The verification value is a hash value calculated by using a hash algorithm by concatenating the nonce value with a hidden information field and a shared key shared between the master station and the electric meter. The hidden information field includes a variety of information. The electric meter uses the same or different information for concatenation calculation when generating the binding request code and the master station uses the same or different information when generating the binding reply code.

4. The power data acquisition system according to claim 3, characterized in that: The hidden information field includes at least one of a code type, an electric meter ID, an ECU unit ID, and a current date.

5. The power data acquisition system according to claim 1, characterized in that: When allocating an ECU unit to each user's mobile phone App, the ECU server calculates the Hash value of the meter ID corresponding to the user's mobile phone App, and uses the Hash value to perform a modulus operation on the number of ECU units in the ECU pool to obtain the ECU unit index to be bound.

6. A method for collecting power data, using the power data collection system according to any one of claims 1 to 5, characterized in that: Includes the following: The user downloads the App provided by the power grid and completes the registration; Start the master station and ECU pool. Several ECU units access the master station through a wireless virtual private network. The ECU server waits for the user's mobile phone App to access. The user's mobile app establishes a connection with the ECU server through the operator's public network; The ECU server allocates an ECU unit to the user's mobile app, binds the relationship between the meter, the user's mobile app, and the ECU unit, and builds a two-way backup communication link from the meter to the master station through the user's mobile app, the ECU server, the corresponding ECU unit, and the master station. When a link failure occurs in the power line carrier network, data collection and control information delivery are performed via the bidirectional backup communication link.

7. The power data collection method according to claim 6, characterized in that: The process of binding the relationship between the electric meter, the user's mobile phone App, and the ECU unit includes the following: The user triggers the meter to create a binding request code through the App, and sends it to the main station through the user's mobile phone App, ECU server, and corresponding ECU unit in sequence; The master station verifies the binding request code, generates a binding reply code after successful verification, and sends the binding reply code to the ECU server through the ECU unit to notify the ECU server to perform binding; The ECU server completes the relationship binding between the ECU unit, the user's mobile phone App, and the electric meter, and sends the binding reply code to the electric meter through the user's mobile phone App; The electric meter verifies the binding reply code and accepts the binding after successful verification.

8. The power data collection method according to claim 6, characterized in that: The process of the ECU server allocating an ECU unit to the user's mobile phone App includes the following: The ECU server calculates the hash value of the meter ID, and uses the hash value to perform a modulus operation on the number of ECU units in the ECU pool to obtain the ECU unit index to be bound.

9. A device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a computer program, and the processor executes the steps of the method according to any one of claims 6 to 8 by calling the computer program stored in the memory.

10. A computer-readable storage medium for storing a computer program for collecting power data, characterized in that: When the computer program is run on a computer, the steps of the method according to any one of claims 6 to 8 are executed.

Images