A method for reading terminal equipment of energy controller
The method for energy controllers normalizes protocol tasks using a tag management system, addressing resource conflicts and enhancing efficiency by integrating new protocols without additional manual configuration.
Patent Information
- Application Number
- CN202211264787.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-10-17
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2042-10-17
AI Technical Summary
Energy controllers face challenges with multiple protocol tasks competing for resources on the same port, leading to complex management and inefficient use of system resources, with each new protocol requiring significant manpower and material resources.
A method involving a tag management task to extract and normalize tag quantities from different protocol tasks, creating a tag matrix library, and a reading task that adapts to this matrix for efficient data reading without requiring separate protocol tasks for each device.
This approach reduces resource conflicts and simplifies management by normalizing protocol tasks, allowing seamless integration of new protocols and improving operational efficiency.
Smart Images

Figure CN115643313B_ABST
Abstract
Description
Technical Field
[0001] The invention relates to the technical field of information processing, and in particular to a method for reading terminal equipment of an energy controller. Background Art
[0002] The electricity consumption information collection system is divided into three layers (cloud layer, edge layer and terminal layer). The energy controller is located in the edge layer. The upper layer (cloud layer) of the energy controller is the main station for consumption and collection, and the lower layer (terminal layer) is the terminal equipment such as electric energy meters, circuit breakers, and sensors. The energy controller collects load curves, events and other data of the terminal equipment at the bottom, connects to the main station system for consumption and collection, receives the main station command and returns the collected terminal equipment data.
[0003] The protocols of the terminal devices in the substation are varied due to the different types of equipment and purchase batches. The protocol information of each terminal device is sent to the energy controller by the user acquisition master station as part of the equipment file. When the energy controller reads the terminal device, it first assigns it to different collection task areas according to the physical port connected to the terminal device, and then designs a protocol task process for each protocol on the port. When reading a certain terminal device, it transfers to the corresponding protocol task execution according to its file information.
[0004] As the number of terminal device protocols continues to increase, energy controllers have begun to have the following drawbacks: multiple protocol tasks run simultaneously on the same physical port, and the tasks compete for communication resources, making task scheduling and management difficult; each protocol sets a protocol task, consuming a large amount of system resources; each new protocol requires a lot of manpower and material resources to develop, which is inefficient. Summary of the invention
[0005] The present invention proposes a method for energy controller to read terminal equipment, the purpose of which is to solve the problems of multiple protocol tasks occupying resources and complex management on the same port of the energy controller, so that the energy controller can read terminal equipment data concisely and efficiently.
[0006] The technical solution of the present invention is as follows:
[0007] A method for reading terminal equipment of an energy controller comprises the following steps:
[0008] S0: Create a tag management task and a reading task. The tag management task extracts the tag quantity from different parts of each protocol task of the energy controller and normalizes the tag quantity to obtain a tag matrix library. The reading task normalizes the remaining common parts of each protocol task except the tag quantity.
[0009] S1: The main station sends the terminal equipment file to the energy controller, the tag management task receives the file, and searches the tag matrix library according to the terminal equipment file, and selects a suitable tag matrix for binding;
[0010] S2: The main station sends a command to start the reading terminal device to the energy controller. The reading task applies to the tag management task according to the terminal device ID. The tag management task embeds the tag quantity in the binding tag matrix into the corresponding tag position of the reading task; the reading task automatically adapts the embedded tag matrix, executes the reading terminal device operation, and uploads the terminal device data to the main station;
[0011] S3: After completing the reading operation, the reading task deletes the marked quantity, uninstalls the protocol, and waits for the next reading command to arrive.
[0012] Furthermore, the tag management task performs update management on the tag matrix library. When there is a new protocol task, the tag quantity is extracted and normalized for the new protocol task to obtain a new tag matrix, which is added to the tag matrix library.
[0013] Furthermore, the method for extracting the marker quantity in step S0 is: defining the characteristic value of each reduction task as the marker quantity, and defining the position for extracting the marker quantity as the marker position.
[0014] Furthermore, the normalization operation of the labeled quantity in step S0 includes uniformly defining the data type and data format of the labeled quantity.
[0015] Furthermore, the tag quantity includes a hardware parameter tag quantity, and the hardware parameter tag quantity includes a port number, a baud rate, a data bit, a stop bit, and a check bit of a physical interface; the tag management task specifies a unified rule for the data type and the number of data bits of each hardware parameter tag quantity to obtain a hardware parameter group:
[0016] [H1, H2, H3, ..., H x ]
[0017] Here, x represents the number of hardware parameter markers.
[0018] Furthermore, the tag quantity also includes a sending control tag quantity, and the sending control tag quantity includes a sending buffer pool size, a sending idle time, a sending character interval, a sending message package, a physical interface write operation, a sending exception handling and a retransmission management;
[0019] The tag management task normalizes the sending control tag quantity and converts it into a sending control group:
[0020] [T1, T2, T3, ..., T y ]
[0021] Where y represents the number of control tags sent.
[0022] Furthermore, the tag quantity also includes a receiving control tag quantity, and the receiving control tag quantity includes a receiving buffer pool size, a receiving waiting time, a physical interface read operation, a frame header search, a frame format matching, an APDU parsing and a receiving exception handling;
[0023] The tag management task normalizes the receiving control tag quantity and converts it into a receiving control group:
[0024] [R1, R2, R3, ..., R z ]
[0025] Wherein, z represents the number of received control markers.
[0026] Furthermore, the tag management task combines the hardware parameter group, the sending control group and the receiving control group to obtain a normalized tag matrix p:
[0027]
[0028] Perform label extraction and normalization operations on n types of reduction tasks to obtain the label matrix library P:
[0029] P=[p1,p2,p3,...,p n ].
[0030] Furthermore, the internal logic of the remaining common parts of each reduction task described in step S0 except for the marking amount is completely the same.
[0031] Furthermore, the copying and reading task cannot be run independently, and the copying and reading operation can be performed after the marking quantity is embedded.
[0032] Compared with the prior art, the present invention has the following beneficial effects: by means of a tag management task, tag quantity extraction and normalization operations are performed on different parts of each protocol task of the energy controller to generate a tag matrix, and a reading task is used to normalize the remaining common parts of each protocol task, so that protocol normalization and protocol framework are realized, conflicts among multiple protocol tasks are avoided, the difficulty of scheduling management is reduced, and new protocols are added conveniently; when a reading command is received, the tag management task can execute the reading end device operation after embedding the corresponding tag matrix into the reading task, without setting a protocol task for each protocol, thereby avoiding the problems of multiple protocol tasks on the same port of the energy controller occupying resources and complex management, reducing system complexity and improving work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] Figure 1 It is a flow chart of the single-port multi-protocol processing method of the present invention;
[0034] Figure 2 It is a flow chart of the copy-reading end device method of the present invention; DETAILED DESCRIPTION
[0035] The technical solution of the present invention is described in detail below with reference to the accompanying drawings:
[0036] like Figure 1 and Figure 2 , a method for reading terminal equipment of an energy controller, comprising the following steps:
[0037] S0: Create a tag management task and a reading task. The tag management task extracts tag quantities from different parts of each protocol task of the energy controller, defines the characteristic value of each protocol task as a tag quantity, and defines the position of the extracted tag quantity as a tag bit.
[0038] The data type and data format of the labeled quantity are uniformly defined, that is, the labeled quantity is normalized to obtain the labeled matrix library P.
[0039] Preferably, the marking quantity includes three categories: hardware parameter marking quantity, sending control marking quantity and receiving control marking quantity.
[0040] The hardware interfaces of the energy controller include carrier, RS485, micro-power wireless, Bluetooth, etc. The characteristics of these physical interfaces are extracted to obtain hardware parameter tag quantities. The hardware parameter tag quantities include the port number, baud rate, data bit, stop bit and check bit of the physical interface. The tag management task specifies a unified rule for the data type and data bit number of each hardware parameter tag quantity. Each hardware parameter tag quantity is recorded as H i (i=1, 2, 3, ..., x), and get the hardware parameter set:
[0041] [H1, H2, H3, ..., H x ]
[0042] Here, x represents the number of hardware parameter markers.
[0043] The sending control tag quantity includes the sending buffer pool size, sending idle time, sending character interval, sending message grouping, physical interface write operation, sending exception processing and retransmission management, etc. The tag management task normalizes the sending control tag quantity and converts it into a sending control group:
[0044] [T1, T2, T3, ..., T y ]
[0045] Where y represents the number of control tags sent.
[0046] The receiving control tag quantity includes receiving buffer pool size, receiving waiting time, physical interface read operation, frame header search, frame format matching, APDU (Application Protocol Data Unit) parsing and receiving exception processing, etc. The tag management task normalizes the receiving control tag quantity and converts it into a receiving control group:
[0047] [R1, R2, R3, ..., R z ]
[0048] Wherein, z represents the number of received control markers.
[0049] The tag management task combines the hardware parameter group, the sending control group, and the receiving control group to obtain a normalized tag matrix p:
[0050]
[0051] For n types of reduction tasks, label quantity extraction and normalization are performed to obtain the label matrix library P:
[0052] P=[p1,p2,p3,…,p n ].
[0053] After constructing the marking matrix, the internal logic of the remaining common parts of each reduction task except the marking amount is exactly the same. The remaining common parts of each reduction task except the marking amount are normalized to generate a copying task. The copying task cannot run independently. When copying the terminal device, the corresponding marking matrix needs to be embedded before the copying operation can be performed.
[0054] S1: The main station sends the terminal equipment file to the energy controller, the tag management task receives the file, and searches in the tag matrix library according to the terminal equipment file, and selects a suitable tag matrix for binding.
[0055] S2: The main acquisition station sends a command to start the reading terminal device to the energy controller. The reading task applies to the tag management task according to the terminal device ID. The tag management task embeds the tag quantity in the binding tag matrix into the corresponding tag position of the reading task; the reading task automatically adapts the embedded tag matrix, executes the reading terminal device operation, and uploads the terminal device data to the main acquisition station.
[0056] S3: After completing the reading operation, the reading task deletes the marked quantity, uninstalls the protocol, and waits for the next reading command to arrive.
[0057] Preferably, the tag management task performs update management on the tag matrix library. When there is a new protocol task, the tag quantity is extracted and normalized for the new protocol task to obtain a new tag matrix, which is added to the tag matrix library P.
Claims
1. A method for reading terminal equipment of an energy controller, characterized in that: The steps include: S0: Create a tag management task and a reading task. The tag management task extracts the tag quantity from different parts of each protocol task of the energy controller and normalizes the tag quantity to obtain a tag matrix library. The reading task normalizes the remaining common parts of each protocol task except the tag quantity. S1: The main station sends the terminal equipment file to the energy controller, the tag management task receives the file, and searches the tag matrix library according to the terminal equipment file, and selects a suitable tag matrix for binding; S2: The main station sends a command to start the reading terminal device to the energy controller, and the reading task applies to the tag management task according to the terminal device ID. The tag management task embeds the tag quantity in the binding tag matrix into the tag position corresponding to the reading task; The reading task automatically adapts the embedded tag matrix, executes the reading end device operation, and uploads the end device data to the user acquisition master station; S3: After completing the reading operation, the reading task deletes the marked quantity, uninstalls the protocol, and waits for the next reading command to arrive; The tag quantity includes a hardware parameter tag quantity, and the hardware parameter tag quantity includes a port number, a baud rate, a data bit, a stop bit, and a check bit of a physical interface; the tag management task specifies a unified rule for the data type and the number of data bits of each hardware parameter tag quantity to obtain a hardware parameter group: ; Where x represents the number of hardware parameter markers; The tag quantity also includes a sending control tag quantity, and the sending control tag quantity includes a sending buffer pool size, a sending idle time, a sending character interval, a sending message package, a physical interface write operation, a sending exception processing and a retransmission management; The tag management task normalizes the sending control tag quantity and converts it into a sending control group: ; Among them, y represents the number of control markers sent; The tag quantity also includes a receiving control tag quantity, and the receiving control tag quantity includes a receiving buffer pool size, a receiving waiting time, a physical interface read operation, a frame header search, a frame format matching, an APDU analysis and a receiving exception processing; The tag management task normalizes the receiving control tag quantity and converts it into a receiving control group: ; Among them, z represents the number of received control markers; The tag management task combines the hardware parameter group, the sending control group, and the receiving control group to obtain a normalized tag matrix p: ; Perform label extraction and normalization operations on n types of reduction tasks to obtain the label matrix library P: 。 2. The method of energy controller reading terminal device according to claim 1, characterized in that: The tag management task updates and manages the tag matrix library. When there is a new specification task, the tag quantity is extracted and normalized for the new specification task to obtain a new tag matrix, which is added to the tag matrix library.
3. The method of energy controller reading terminal device as claimed in claim 1, characterized in that: The method for extracting the label quantity in step S0 is: defining the characteristic value of each reduction task as the label quantity, and defining the position where the label quantity is extracted as the label position.
4. The method of energy controller reading terminal device according to claim 1, characterized in that: The normalization operation of the labeled quantity in step S0 includes uniformly defining the data type and data format of the labeled quantity.
5. The method of energy controller reading terminal device as claimed in claim 1, characterized in that: The internal logic of the remaining common parts of each protocol task described in step S0, except for the marking amount, is exactly the same.
6. The method of the energy controller reading terminal device according to any one of claims 1 to 5, characterized in that: The copying and reading task cannot be run independently, and the copying and reading operation can be performed after the tag quantity is embedded.
Citation Information
Patent Citations
Power consumption information acquisition system, NB-IoT communication module and communication method thereof
CN111833578A
Multi-protocol intelligent acquisition gateway system for water and electricity meters and use method of multi-protocol intelligent acquisition gateway system
CN113194554A
Systems, methods, and devices for geolocation with deployable large scale arrays
US20170374572A1
Meter reading schema to enhance system functionality
US20180094948A1
Data collection server and lost data supplementation method
WO2018003053A1
