Power line carrier communication scheduling method and storage medium

Abstract

The application discloses a power line carrier communication scheduling method and a storage medium, and belongs to the technical field of power line communication. The power line carrier communication scheduling method comprises the following steps: a source node generates a scheduling frame; wherein the scheduling frame carries scheduling data and does not include a frame payload field; the source node sends the scheduling frame to a station, so as to instruct the station to generate a scheduling instruction based on the scheduling data, and output the scheduling instruction to a corresponding external mounting device. The application realizes the low-latency scheduling instruction issuing in the power line carrier communication.

Description

Technical Field

[0001] This application belongs to the field of power line communication technology, and in particular relates to a power line carrier communication scheduling method and storage medium. Background Technology

[0002] Power line communication (PLC) technology utilizes existing power lines as the communication medium to achieve data transmission and interaction, and has been widely used in scenarios such as electricity information collection, distribution automation, photovoltaic power generation control, electric vehicle charging management, and rail transit. In these applications, the communication network not only needs to carry periodic data collection services, but also needs to support the issuance of scheduling and control commands to achieve real-time control and coordination of terminal devices.

[0003] In traditional power line carrier communication systems, service messages are typically transmitted in the form of Start of Frame (SOF) frames at the data link layer, according to standards such as the "Technical Specification for Interoperability of High-Speed ​​Communication on Low-Voltage Power Lines". These SOF frames generally include frame control fields and frame payload fields, and are suitable for carrying data acquisition information, network management information, and application layer service data.

[0004] However, this frame structure was primarily designed for information acquisition and routine data transmission scenarios, resulting in a relatively long minimum frame payload length and corresponding time-domain occupancy. In actual operation, even short control commands need to be sent along with the frame payload field, thus preventing a reduction in the overall communication latency for command issuance. In high-time-sensitivity scheduling scenarios where the real-time requirements for scheduling control commands are as high as milliseconds, the above approach makes it difficult to meet the command issuance latency requirements. Summary of the Invention

[0005] This invention aims to at least solve one of the technical problems existing in the prior art. To this end, this invention proposes a power line carrier communication scheduling method and storage medium to achieve low-latency scheduling command issuance in power line carrier communication.

[0006] In a first aspect, this application provides a power line carrier communication scheduling method, the method comprising: The source node generates a scheduling frame; the scheduling frame carries scheduling data but does not include a frame payload field. The source node sends a scheduling frame to the station to instruct the station to generate scheduling instructions based on the scheduling data and output the scheduling instructions to the corresponding external mounted device.

[0007] According to one embodiment of this application, the scheduling frame adopts the control frame format of the data link layer, and the total length of the scheduling frame is a fixed length.

[0008] According to one embodiment of this application, the scheduling frame includes at least the following fields: The delimiter type field indicates that the current frame is a scheduling frame when the field value is a preset value; the network type field indicates the type of control system to which the scheduling data belongs; different network types correspond to different scheduling data encapsulation rules; the network identifier field is used to distinguish different power line carrier communication networks; the sequence number field is used to identify the transmission order of scheduling frames and is used by the station to filter repeatedly received scheduling frames; the data field is used to carry scheduling instructions; and the check field is used to verify the data integrity of the scheduling frame.

[0009] According to one embodiment of this application, the network type field is configured with at least one of the following field values: a first field value, used to indicate that the scheduling frame is transmitted in the electricity consumption information collection system; a second field value, used to indicate that the scheduling frame is transmitted in the photovoltaic power generation control system; a third field value, used to indicate that the scheduling frame is transmitted in the power distribution information control system; and a fourth field value, used to indicate that the scheduling frame is transmitted in the rail transit control system.

[0010] According to one embodiment of this application, the source node transmits scheduling frames in a power line carrier communication network in a broadcast manner.

[0011] According to one embodiment of this application, the source node receives scheduling request instructions from externally mounted devices via a serial port or Ethernet port, and determines scheduling data based on the scheduling request instructions; and / or, autonomously generates scheduling data.

[0012] According to one embodiment of this application, when a source node receives a scheduling request instruction, it identifies the instruction header of the scheduling request instruction and identifies the instruction tail according to the fixed length of the scheduling request instruction; it extracts multiple bytes of data before the first digit of the instruction tail as instruction data and extracts bytes of data before the second digit of the instruction tail as verification data; it compares the instruction data with the verification data to perform integrity verification, and if the integrity verification passes, it uses the instruction data as scheduling data.

[0013] Secondly, this application provides a power line carrier communication scheduling method, the method comprising: The station receives a scheduling frame sent by the source node; the scheduling frame carries scheduling data but does not include a frame payload field. The site generates scheduling instructions based on the scheduling data and outputs the scheduling instructions to the corresponding external mounted devices.

[0014] According to one embodiment of this application, the scheduling frame includes a delimiter type field. The station receives the scheduling frame sent by the source node, specifically including: monitoring the data frames broadcast in the power line carrier communication network and identifying the delimiter type field of the data frame; if the field value in the delimiter type field is a preset value, determining that the data frame is a scheduling frame, and extracting the scheduling data carried in the data field of the scheduling frame.

[0015] According to one embodiment of this application, the scheduling frame includes a network type field for indicating the type of control system to which the scheduling data belongs, and different network types correspond to different scheduling data encapsulation rules; the station generates scheduling instructions based on the scheduling data, specifically including: determining the target control system type to which the scheduling data belongs based on the field value in the network type field of the scheduling frame; determining the target scheduling data encapsulation rule corresponding to the target control system type, and encapsulating the scheduling data into scheduling instructions according to the target scheduling data encapsulation rule.

[0016] Thirdly, this application provides a power line carrier communication scheduling method, which includes: The source node generates a scheduling frame; the scheduling frame carries scheduling data but does not include a frame payload field. The source node sends a scheduling frame to the relay node to instruct the relay node to generate scheduling instructions based on the scheduling data and output the scheduling instructions to the corresponding external mounted devices.

[0017] According to one embodiment of this application, the source node sends a scheduling frame to the relay node, specifically including: the relay node forwards the scheduling frame to the station without modifying the scheduling frame, so as to instruct the station to generate a scheduling instruction based on the scheduling data, and outputs the scheduling instruction to the corresponding external mounted device.

[0018] Fourthly, this application provides a non-transitory computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the power line carrier communication scheduling method as described in the first, second, or third aspects above.

[0019] Fifthly, this application provides a power line carrier communication dispatching system, the system comprising: The source node is used to generate scheduling frames and send them to the stations. The station is used to generate scheduling instructions based on scheduling data and output the scheduling instructions to the corresponding external mounted devices.

[0020] In a sixth aspect, this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the power line carrier communication scheduling method as described in the first, second, or third aspects above.

[0021] In a seventh aspect, this application provides a chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the power line carrier communication scheduling method as described in the first, second, or third aspects.

[0022] Eighthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the power line carrier communication scheduling method as described in the first, second, or third aspects above.

[0023] The above-described one or more technical solutions in the embodiments of this application have at least one of the following technical effects: By generating scheduling frames through the source node and carrying scheduling data within these frames, and by eliminating the frame payload field, the frame structure is effectively simplified, reducing the inherent latency of traditional frame structure transmission and lowering communication latency at the data link layer. The source node sends scheduling frames to the stations to instruct them to generate scheduling instructions based on the scheduling data and output the instructions to the corresponding external mounted devices. This enables efficient transmission of scheduling data in the power line carrier communication network, achieving low-latency scheduling instruction issuance and providing an effective communication solution for high real-time control scenarios sensitive to communication latency.

[0024] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0025] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, in which: Figure 1 This is a flowchart illustrating the power line carrier communication scheduling method provided in some embodiments of this application; Figure 2 This is a schematic diagram of the process by which the source node processes scheduling request instructions and generates scheduling frames, provided in an embodiment of this application. Figure 3 This is a schematic diagram of the framework for generating a scheduling frame from a scheduling request instruction, provided in an embodiment of this application. Figure 4 This is a flowchart illustrating the power line carrier communication scheduling method provided in other embodiments of this application; Figure 5 This is a schematic diagram of the process for site identification and processing of scheduling frames provided in an embodiment of this application; Figure 6This is a flowchart illustrating the power line carrier communication scheduling method provided in some other embodiments of this application; Figure 7 This is a flowchart of the central coordinator and relay node processing scheduling frames provided in the embodiments of this application; Figure 8 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0026] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0027] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0028] With the rapid development of smart grid, distributed energy and industrial Internet of Things technologies, the end-to-end communication latency requirements for dispatching instructions are quite stringent in high real-time application scenarios such as rapid power regulation of centralized photovoltaic power plants, rapid fault isolation and recovery of distribution networks, and real-time synchronous control of rail transit signals.

[0029] Among them, high-speed power line communication (HPLC) based on orthogonal frequency division multiplexing (OFDM) modulation technology and its broadband dual-mode communication technology formed by combining with high-speed low-power radio frequency (HRF) have been widely used in power line communication-based systems due to their advantages of using existing power lines to achieve high-speed data transmission without the need for additional wiring.

[0030] In related technologies, service messages and control commands typically follow the "Technical Specification for Interoperability of High-Speed ​​Communication over Low-Voltage Power Lines," uniformly adopting the standard SOF frame structure for transmission over power lines or wireless links. This SOF frame consists of two parts: Frame Control (FC) and Payload Body (PB). The design of the SOF frame emphasizes reliable data acquisition and service message transmission. The FC serves as the carrier of control information such as source address, frame type, sequence number, and quality of service identifier, while the PB serves as the data carrier, carrying user service information (such as electricity consumption data, configuration parameters, or control command content). Furthermore, the length of the PB can be adjusted according to the transmitted content and application scenario to accommodate different service data volume requirements, ranging from tens of bytes to thousands of bytes.

[0031] However, the inventors realized through research and practice in real-time control scenarios that the command issuance mode based on standard SOF frames makes it difficult to differentiate between control commands and service messages. In other words, even when issuing extremely short control commands, the SOF frame carries the complete FC and PB. The "Technical Specification for Interoperability of High-Speed ​​Communication on Low-Voltage Power Lines" defines corresponding physical layer transmission parameters for different frequency bands (BAND). Within BAND1 to BAND4, the transmission length of the FC portion in the time domain is fixed at 711.4 microseconds. However, the PB, which carries the actual service data, taking the smallest PB of 72 bytes as an example, has a transmission delay of 2.2 to 10.4 milliseconds on the channel, exceeding the 2-millisecond threshold required by many real-time control scenarios (such as centralized photovoltaic power generation scenarios).

[0032] Furthermore, the inventors discovered that in real-time control scenarios, the data to be transmitted is relatively small, typically only a few to tens of bytes, but its timeliness requirements are high. The SOF frame structure, designed for general data transmission and containing a large capacity of PB, results in a waste of transmission time for this type of "small data, high timeliness" instruction transmission.

[0033] Therefore, from the perspective of data link layer frame format, a fast scheduling frame structure specifically designed for fast scheduling without carrying traditional PB can be designed, thereby reducing the latency of scheduling instruction transmission and improving scheduling speed.

[0034] In view of this, embodiments of this application provide a fast scheduling method and storage medium based on power line carrier communication, aiming to solve the problem of high delay in the issuance of scheduling instructions in power line carrier communication systems. By defining a scheduling frame without frame payload, the scheduling data of the scheduling instruction is carried by the frame control field, thereby realizing the issuance of low-latency scheduling instructions in the power line carrier communication system.

[0035] The power line carrier communication scheduling method and storage medium provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0036] The power line carrier communication scheduling method provided in this application can be applied to, but is not limited to, electricity information collection systems, photovoltaic power generation control systems, power distribution information control systems, or rail transit control systems.

[0037] Among them, the electricity consumption information collection system refers to a system in which the master station, as the source node, can issue scheduling instructions such as freezing and data retrieval to concentrators or smart meters deployed on-site as stations in scenarios such as residential or industrial and commercial electricity consumption information collection; the photovoltaic power generation control system refers to a system in which the centralized controller, as the source node, issues scheduling instructions such as rapid power adjustment and start-stop control to all photovoltaic inverters in the network, which are stations, in scenarios such as centralized or distributed photovoltaic power stations; the distribution information control system refers to a system in which the distribution master station or feeder terminal unit, as the source node, can issue scheduling instructions such as opening and closing, fault isolation and recovery to equipment such as smart switches and fault indicators on the line, which are stations, in scenarios such as distribution network automation; and the rail transit control system refers to a system in which the area controller, as the source node, can issue scheduling instructions such as interlocking, block, and speed codes in real time to turnout control units, signals, and train on-board equipment, which are stations, in rail transit signal and control systems.

[0038] In this embodiment of the application, a communication system architecture suitable for power line carrier communication is constructed to enable the rapid issuance of scheduling instructions in the power line carrier communication network. It should be noted that the communication system architecture described in this embodiment is used to illustrate the implementation environment of the scheduling method provided in this application and does not constitute a limitation on the scope of protection of this application.

[0039] In some embodiments, the communication system includes at least a source node and a station, the source node and the station communicating via a power line carrier communication link. The source node is a scheduling initiating node in the power line carrier communication network, used to generate and send scheduling frames; the station is a receiving node in the power line carrier communication network, used to receive scheduling frames and output the scheduling instructions carried therein to an external mounted device.

[0040] For example, the source node can be an access point in a power line carrier communication network (e.g., a central coordinator); in other implementations, a communication node with the ability to generate scheduling instructions can also serve as the source node.

[0041] In some embodiments, the communication system may further include a relay node located between the source node and the station, for forwarding the scheduling frame without changing the content of the scheduling frame, so as to extend the communication coverage.

[0042] Figure 1 This is a flowchart illustrating a power line carrier communication scheduling method provided in some embodiments of this application. For example... Figure 1 As shown, the power line carrier communication scheduling method includes steps 110 to 120.

[0043] Step 110: The source node generates a scheduling frame; wherein the scheduling frame carries scheduling data but does not include a frame payload field; Step 120: The source node sends a scheduling frame to the station to instruct the station to generate a scheduling instruction based on the scheduling data and output the scheduling instruction to the corresponding external mounted device.

[0044] In this embodiment, the source node can generate a scheduling frame based on its own scheduling needs or those generated by external devices it is connected to, and broadcast the scheduling frame to the power line carrier communication network. The station can listen to the data frames transmitted in the power line carrier communication network to receive the scheduling frame.

[0045] The source nodes mentioned in the embodiments of this application include, but are not limited to, a Central Coordinator (CCO). The Central Coordinator may be, for example, a centralized acquisition unit or photovoltaic controller deployed in a photovoltaic power generation control system, a distribution control unit or feeder terminal unit in a distribution network automation system, a rail transit sub-controller or area controller in a rail transit control system, a concentrator in an electricity consumption information acquisition system, an industrial control gateway or master station equipment that needs to centrally issue real-time control commands, or a power line carrier communication master control module or communication chip in the above-mentioned equipment.

[0046] A station (STA) is a functional entity in a power line carrier communication network that receives and parses scheduling frames and generates scheduling instructions based on the scheduling data within the scheduling frames, so that externally mounted execution devices can act according to the scheduling instructions.

[0047] A scheduling instruction is a complete data message that conforms to a specific application layer communication protocol format and can be recognized and executed by externally mounted devices.

[0048] External mounted equipment refers to the execution unit connected to the station and controlled by scheduling instructions.

[0049] For example, externally mounted devices may be inverters in photovoltaic scenarios, smart switches in power distribution scenarios, gate control units or signal machines in rail transit scenarios, etc.

[0050] It should be noted that the scheduling frames and the scheduling data they carry are designed specifically for high-speed, low-latency transmission within power line carrier communication networks. However, external devices (such as industrial controllers and inverters) typically follow their own fixed serial or Ethernet communication protocols (e.g., formats including specific headers, checksums, and trailers). Therefore, stations cannot directly send internal network scheduling data or frames to external devices. Instead, they need to repackage and assemble the received scheduling data into complete scheduling instructions according to the external devices' protocol rules, ensuring that the instructions can be correctly received and executed by the external devices.

[0051] Based on the scheduling data in the scheduling frame, the site generates corresponding scheduling instructions and outputs them to the external mounted device. Upon receiving a scheduling instruction from the site that conforms to its interface specification, the external mounted device parses the instruction and executes the required operations.

[0052] For example, externally mounted devices can adjust their output power, change their switching status, or report specified data according to scheduling instructions.

[0053] Among them, the scheduling frame refers to a dedicated Medium Access Control (MAC) layer protocol data unit (PDU) that is used to carry scheduling data for high real-time scheduling instructions after the frame format has been defined.

[0054] Unlike the service data transmission frames used in traditional power line carrier communication, this application does not achieve scheduling acceleration by shortening the length of service data or increasing the physical layer rate. Instead, it starts from the data link layer and specially designs and improves the frame structure used for scheduling command transmission.

[0055] When generating scheduling frames, the source node does not use the conventional service frame structure containing frame payload fields. Instead, it constructs a control frame structure for the rapid issuance of scheduling instructions. The scheduling frame retains only the necessary fields for frame identification and control, and sets a fixed-length data field to directly carry the scheduling instructions, thus avoiding the problem of service frame payload fields occupying a long transmission time in the time domain. In this way, scheduling instructions do not need to be encapsulated in the frame payload of the service data frame for transmission, significantly reducing the transmission latency of the scheduling frame on the power line carrier communication link. Specifically, the latency can be reduced from 2.2~10.4 milliseconds to 1.0~1.1 milliseconds.

[0056] In this embodiment, the data field length of the scheduling frame is a preset fixed length. When generating the scheduling frame, the source node directly maps the scheduling instruction to the data field. When the actual length of the scheduling instruction is less than the fixed length, the data field length can be padded. Since the overall frame structure of the scheduling frame does not change with the content of the scheduling instruction, the source node does not need to dynamically adjust the frame structure according to the amount of business data during the scheduling frame generation process, thereby further simplifying the generation and processing flow of the scheduling frame.

[0057] Specifically, a scheduling frame can be a specific type of MAC protocol data unit, namely a Medium Access Control Protocol Data Unit (MPDU), whose frame structure consists of a frame control field and does not contain a variable-length frame payload.

[0058] It should be noted that the Physical Layer (PHY) and MAC layer of the communication module can perform optimized pipelined processing and pre-scheduling for fixed-length scheduling frames. In the PHY layer's processing optimization, after detecting the start delimiter of the scheduling frame and completing time and frequency synchronization, the end boundary of the scheduling frame can be predetermined due to the known fixed length. In the MAC layer's processing optimization, the MAC layer does not need to process variable-length frames or dynamically determine frame boundaries by parsing the length field or searching for the frame end delimiter. Instead, it can trigger an interrupt and begin parsing and verifying the scheduling frame after receiving a preset fixed number of bytes, reducing the waiting time and computational overhead for scheduling frame boundary determination.

[0059] By limiting the scheduling frame to a fixed-length control frame format, the transmission time of the scheduling frame can be obtained under specific channel conditions, reducing the overhead of logical judgment and resource allocation, further compressing processing latency, facilitating rapid synchronization and detection at the site, and reducing the risk of scheduling frame parsing errors in complex noise environments.

[0060] It should be noted that in power line carrier communication systems, the data link layer frame structure is typically designed around the goal of "universal bearer," that is, by setting the PB field to adapt to data content of different lengths and types, thereby enabling compatibility with multiple services such as data acquisition, network management, and control commands within the same frame structure. This design has good applicability in conventional communication scenarios, but it also means that even short, semantically simple scheduling commands still need to be encapsulated and transmitted according to the complete service frame flow, making it difficult to further compress the frame's time domain footprint.

[0061] Against this backdrop, traditional solutions for optimizing scheduling command transmission latency often focus on adjusting physical layer parameters, scheduling priorities, or frame payload length, while rarely addressing the frame structure itself. From a protocol design perspective, the PB field is primarily used to provide variable-length data carrying capacity; not all types of information must rely on this universal carrying method. When the information to be transmitted has characteristics such as fixed length and well-defined parsing rules, continuing to use the universal PB structure is not the optimal choice. However, simplification of the frame structure without corresponding type differentiation and parsing constraint mechanisms may negatively impact frame identification, forwarding, and system interoperability. For example, if the frame structure lacks the PB field used to carry valid data, the receiver cannot rely on the payload length to determine data boundaries; simultaneously, in multi-node or relayed networks, short frames lacking clear semantic identification may be misjudged as abnormal or management frames, thus interfering with normal forwarding and parsing processes. Therefore, without systematic design, simply pruning the frame structure can easily disrupt the stability of the original power line carrier communication mechanism.

[0062] Based on the above understanding, this application does not regard the removal of frame payload fields as an isolated optimization method. Instead, it comprehensively reconstructs the transmission method by considering the characteristics of short length, fixed format, and clear semantics of scheduling instructions. While maintaining the overall compatibility of the power line carrier communication system, a dedicated scheduling frame structure without PB is defined to decouple scheduling instructions from the general service frame carrying mechanism. This allows them to be transmitted on the link in a more compact and deterministic frame format, thus laying the foundation for the rapid issuance of scheduling instructions. This improvement is not a simple reduction of the existing frame structure, but a targeted and systematic design of the data link layer frame structure based on the characteristics of scheduling services.

[0063] In some implementations, Table 1 is a field format table of the scheduling frame provided in some embodiments of this application. As shown in Table 1, the scheduling frame is an MPDU with a fixed total length of 16 bytes, which carries scheduling data through the frame control field and does not contain PB.

[0064] Table 1

[0065] The scheduling frame uses a fixed 16-byte structure. Specifically, the delimiter type field is located in bits 0 to 2 of byte 0, occupying 3 bits, and is used to identify the type of scheduling frame; the network type field is located in bits 3 to 7 of byte 0, occupying 5 bits, and is used to indicate the control system to which the scheduling command applies; the network identifier field occupies the first byte (bits 0 to 7 per byte), totaling 8 bits, and is used to distinguish different communication networks; the sequence number field is located between bytes 2 and 3 (bits 0 to 7 per byte), with a total length of 16 bits, and is used for the sequential identification and deduplication of scheduling frames; the data field is located from bytes 4 to 12 (bits 0 to 7 per byte), fixed at 72 bits (i.e., 9 bytes), and is used to carry the scheduling data of the scheduling command; the check sequence field is located in bytes 13 to 15 of the scheduling frame, with bits 0 to 7 per byte, totaling 24 bits, and is used to verify the integrity of the data transmission of the scheduling frame.

[0066] In the above embodiments, by constructing scheduling frames with fixed structure and length, the scheduling frames are quickly identified and processed using delimiter types. Through the network type field, the same physical network can serve multiple heterogeneous control systems, and the parsing of scheduling instructions does not interfere with each other, thus improving the versatility of the power line carrier communication scheduling method. Furthermore, the scheduling frames with fixed structure and length allow instruction data to be effectively encapsulated, ensuring the accuracy and completeness of instruction transmission.

[0067] In some embodiments, the scheduling frame includes at least a delimiter type field, a network type field, a network identifier field, a sequence number field, a data field, and a check field.

[0068] The delimiter type field is used to indicate that the current frame is a scheduling frame when the field value of the delimiter type field is a preset value, so that the station receiving the scheduling frame can distinguish the scheduling frame from beacon frames, SOF data frames, etc., and trigger the processing of scheduling instructions.

[0069] In some implementations, Table 2 is a delimiter type field value configuration table provided in some embodiments of this application. As shown in Table 2, the delimiter type field distinguishes different frames through different field values.

[0070] Table 2

[0071] It should be noted that in power line carrier communication technology, a beacon frame is a management frame periodically broadcast by a network coordinator (such as a CCO), mainly used to announce the existence of the network, synchronize network time, transmit network parameters, and notify service arrangements. The SOF frame is the basic data frame structure defined in the "Technical Specification for Interconnection and Interoperability of High-Speed ​​Communication on Low-Voltage Power Lines," consisting of two parts: FC and PB. It is the main frame type for carrying service data transmission. The Selective Acknowledgment frame is a control frame used for reliable data transmission. The receiver can selectively acknowledge a series of data frames that have been correctly received through this frame to improve retransmission efficiency. The inter-network coordination frame is a special type of control frame, mainly used for coordination and interaction between different central coordinators (CCOs) or networks, such as negotiating channel usage and resolving cross-network interference. In some implementations, the inter-network coordination frame can also refer to an MPDU frame format without a frame payload.

[0072] The network type field of the scheduling frame is used to indicate the type of control system to which the scheduling data belongs. Different network types correspond to different scheduling data encapsulation rules. By calling the corresponding data encapsulation rules, the scheduling data in the scheduling frame can be encapsulated into the corresponding scheduling instructions.

[0073] In some embodiments, the network type field is configured with at least one of the following field values: a first field value, used to indicate that the scheduling frame is transmitted in the electricity consumption information acquisition system; a second field value, used to indicate that the scheduling frame is transmitted in the photovoltaic power generation control system; a third field value, used to indicate that the scheduling frame is transmitted in the power distribution information control system; and a fourth field value, used to indicate that the scheduling frame is transmitted in the rail transit control system.

[0074] Table 3 is a configuration table of network type field values ​​provided in some embodiments of this application. As shown in Table 3, the network type field maps scheduling frames to industrial application systems through different field values. When the network type field value is 0, it indicates that the scheduling frame carries scheduling instructions from the electricity information acquisition system; when the network type field value is 1, it indicates that the scheduling frame carries scheduling instructions from the photovoltaic power generation control system; when the network type field value is 2, it indicates that the scheduling frame carries scheduling instructions from the power distribution information control system; when the network type field value is 3, it indicates that the scheduling frame carries scheduling instructions from the rail transit control system. Other network type field values ​​can be reserved for expanding support for other control systems.

[0075] Table 3

[0076] In the above embodiments, by defining the value of the network type field, parallel and non-interfering scheduling command channels are created for multiple different control systems on the same physical communication basis, which enhances the applicability and flexibility of the scheduling frame, enabling it to adapt to a variety of application scenarios and reducing the construction and maintenance costs of the power line carrier communication network.

[0077] The network identifier field of the scheduling frame is used to distinguish different power line carrier communication networks. The station can determine the current communication network system based on the field value of the network identifier field.

[0078] The Network Identification (NID) is a 24-bit field. Each independent broadband carrier communication network is assigned a globally unique NID value to ensure logical isolation and correct addressing between networks. However, the number of neighboring networks a network typically has is limited, generally no more than 8, and usually no more than 20. Therefore, a 1-byte (8-bit, representing 256 values ​​from 0 to 255) network identifier is used to distinguish the local network from its neighboring networks within the local environment.

[0079] Therefore, in some embodiments, for newly defined scheduling frames with a delimiter type value of a specific value (e.g., 4), the length of its network identifier field is reduced from 3 bytes as specified for general MPDU frames in the "Technical Specification for Interoperability of High-Speed ​​Communication on Low-Voltage Power Lines" to 1 byte.

[0080] In addition, to ensure normal communication and compatibility between network devices, when the network type field takes the value of 1 to 3 (corresponding to photovoltaic power generation control system, power distribution information control system, and rail transit control system), except for the scheduling frame, the network identifier field of the MPDU frame corresponding to other delimiter type values ​​(i.e., delimiter type values ​​0 to 3) also adopts a length of 1 byte. The two bytes of the high byte order of the original 3-byte network identifier field will be treated as a reserved field.

[0081] Furthermore, when the network type field is 0 (for the application of electrical information acquisition system), to maintain compatibility with traditional equipment, the length of the network identifier generated during network setup still follows the original rules, but its value usually does not exceed the range of 1 byte. When filling in the 3-byte network identifier field defined in the frame format, the 1-byte identifier value is filled into the first byte of the low byte order, while the two bytes of the high byte order are filled with 0.

[0082] By reducing the network identifier field from 3 bytes to 1 byte, 2 bytes of transmission load are reduced, further decreasing the transmission time and processing overhead of a single scheduling frame. Simultaneously, devices using the new scheduling frame format and those processing traditional frame formats can coexist and cooperate on the same network, improving the practicality and versatility of the communication scheduling method.

[0083] The sequence number field of the scheduling frame is used to identify the transmission order of the scheduling frames and is used by the station to filter repeatedly received scheduling frames to prevent the scheduling instructions from being executed repeatedly due to retransmission or reflection.

[0084] In addition, the data field of the scheduling frame is used to carry scheduling data.

[0085] Scheduling data refers to the instruction content that carries the specific operational data used to control externally mounted execution devices. It is represented as a fixed-length sequence of bytes, set within a specific field of a scheduling frame designed for fast instruction transmission. For example, scheduling data could be a byte sequence of 9 bytes.

[0086] For example, the scheduling data may include one or more of the following: power settings of externally mounted devices, on / off status commands, or operating mode codes.

[0087] The scheduling frame carries scheduling data but does not include a frame payload field. This means that the structure of the scheduling frame is different from that of the traditional SOF frame. It does not contain a frame payload part used to carry general service data. Instead, it integrates the scheduling data of the instructions to be issued into the frame control field, thereby reducing the latency caused by PB transmission, modulation and demodulation at the data link layer.

[0088] In some implementations, the length of the data field of the scheduling frame is fixed at 9 bytes. When generating a fast scheduling frame, if the length of the scheduling data is less than 9 bytes, zeros are padded at the end before encapsulating it into the data field until the entire 9-byte space is filled.

[0089] For example, if the actual effective scheduling data of a scheduling instruction is 5 bytes, the source node will append 4 bytes with a value of 0x00 to the 5 bytes of data to form a complete 9-byte data block, and then fill it into the data field of the scheduling frame. This method can fix the structure of the scheduling frame, keep the scheduling frame length at 16 bytes, and enable optimization measures such as buffer management and pipelined processing at the physical layer and MAC layer to be implemented stably.

[0090] The checksum field of a scheduling frame is used to verify the data integrity of the scheduling frame. For example, the verification method for the checksum field can be a Cyclic Redundancy Check (CRC) algorithm. Specifically, after generating the scheduling frame, the source node takes the remaining portion of the scheduling frame (excluding the checksum field) (or bytes within a specified bit range) as input data, calculates a fixed-length checksum using a predetermined CRC generator polynomial, and fills this value into the checksum field. Upon receiving the scheduling frame, the station first performs the same CRC calculation process to obtain a locally calculated checksum, and then compares it with the value carried in the checksum field of the received scheduling frame.

[0091] If the two match, the scheduling frame is considered to have been transmitted completely without any bit errors, and the station will continue with subsequent parsing and processing. If the two do not match, the scheduling frame is considered to have been corrupted during transmission, and the station will discard the frame to prevent erroneous or defective instructions from being issued and executed.

[0092] In some embodiments, the source node transmits scheduling frames in the power line carrier communication network in a broadcast manner. Here, broadcast means that the source node sets the target address of the scheduling frame to a broadcast address and transmits the signal carrying the scheduling frame throughout the entire power line carrier communication network via physical layer modulation.

[0093] Specifically, after the source node generates a scheduling frame, it sets its target address to the broadcast address at the MAC layer and modulates it onto a carrier through the physical layer before sending it to the target node in the network.

[0094] For example, a broadcast address could be a MAC address consisting entirely of 1s.

[0095] All stations and nodes within the network listen for and receive broadcast scheduling frames. Each receiving device determines whether a scheduling frame needs to be processed by parsing the delimiter type field in the scheduling frame, and then performs subsequent operations.

[0096] By using broadcast to send scheduling frames, the extra time overhead caused by repeatedly framing multiple targets and competing for channels is avoided, making scheduling instructions synchronous and providing a communication basis for realizing coordinated actions of device groups.

[0097] According to the power line carrier communication scheduling method provided in this application embodiment, a scheduling frame is generated by the source node, and the scheduling frame carries scheduling data. The scheduling frame does not include a frame payload field, which effectively simplifies the frame structure and shortens the inherent delay caused by the traditional frame structure transmission. The communication latency is reduced from the data link layer. The scheduling frame is sent to the station by the source node to instruct the station to generate scheduling instructions based on the scheduling data and output the scheduling instructions to the corresponding external mounted devices. This enables the scheduling data to be transmitted efficiently in the power line carrier communication network, realizes the issuance of low-latency scheduling instructions in the power line carrier communication network, and provides an effective communication solution for high real-time control scenarios that are sensitive to communication latency.

[0098] In some embodiments, the source node receives scheduling request instructions from externally mounted devices via a serial port or Ethernet port, and determines scheduling data based on the scheduling request instructions; and / or, autonomously generates scheduling data.

[0099] In some implementations, scheduling requirements originate from execution devices externally mounted to the source node. For example, the centralized data acquisition unit of a photovoltaic centralized power plant needs to issue power regulation commands to all inverters in the network, or the distribution control unit of the distribution network needs to issue tripping commands to smart switches. These externally mounted execution devices send scheduling commands containing complete application layer protocol formats to the source node through data interfaces such as serial ports and Ethernet.

[0100] In other implementations, scheduling requirements are generated by the source node itself. For example, the source node may periodically generate network status query commands based on its internal timer, or actively initiate device reset commands or execute pre-stored scripts or command sequences based on its internal logic.

[0101] In some embodiments, for instructions from externally mounted execution devices, the source node extracts the scheduling data carrying the actual scheduling instruction content through verification and parsing. For its own generated needs, the source node directly generates the scheduling data corresponding to the scheduling instruction, and then generates a scheduling frame based on the scheduling data. For example, the source node can encapsulate the scheduling data in a scheduling frame with a specific format that does not contain a frame payload.

[0102] However, scheduling requests cannot be directly sent as scheduling frames because their sources are diverse, and their original form is not designed for power line carrier network transmission. If unprocessed raw request data is directly encapsulated into a scheduling frame, not only may parsing fail due to data format incompatibility, but it will also be difficult to ensure the accuracy of the scheduling request on the transmission link.

[0103] Based on this, in some embodiments, when the source node receives a scheduling request instruction, it identifies the instruction header of the scheduling request instruction and identifies the instruction tail according to the fixed length of the scheduling request instruction; it extracts multiple bytes of data before the first digit of the instruction tail as instruction data and extracts bytes of data before the second digit of the instruction tail as verification data; it compares the instruction data with the verification data to perform integrity verification, and if the integrity verification passes, it uses the instruction data as scheduling data.

[0104] The scheduling request instruction refers to a complete control message generated by an externally mounted device (such as a centralized collector or master station) of the source node, conforming to a specific application layer protocol format, and containing information about the operation that needs to be performed by the externally mounted device of the site. The fixed length of the scheduling request instruction refers to the pre-defined total number of bytes in the external instruction message.

[0105] For example, the fixed length of the scheduling request instruction can be, for instance, 12 bytes, to facilitate the source node in quickly locating the end of the frame.

[0106] The instruction header and instruction tail are special bytes embedded in the scheduling request instruction, used to mark the beginning and end of the scheduling request instruction in the data stream.

[0107] For example, the instruction header can be 0xEF and the instruction tail can be 0x16.

[0108] When the source node identifies a byte with a value of 0xEF in the data stream, it can determine that this location is the header of a scheduling request instruction. Since scheduling request instructions have a predefined fixed length (e.g., 12 bytes), the source node can offset this fixed length from the header location to directly locate the expected instruction tail position. If the byte value at this location is 0x16, it matches the expectation and can initially confirm a complete instruction boundary; if the value does not match, it may mean that the data stream is misaligned or the scheduling request instruction is corrupted.

[0109] The first digit of the multi-byte data refers to the continuous sequence of bytes that carries the actual command content, starting after the instruction header and ending before the checksum data.

[0110] For example, in a 12-byte scheduling request instruction, the first digit of the multiple bytes of data can be, for example, the next 9 bytes following the first byte of the scheduling request instruction (in which case the instruction header is 0xEF).

[0111] The second byte of data refers to the bytes transmitted before the end of the instruction. These bytes are used to verify the integrity of the scheduling requirement instruction data and are also known as the checksum.

[0112] For example, Table 4 shows the scheduling request instruction format for serial port or Ethernet port transmission provided in the embodiments of this application. As shown in Table 4, the scheduling request instruction format adopts a fixed total length of 12 bytes.

[0113] Table 4

[0114] The instruction header field is located in byte 0 (bits 0-7), with a length of 8 bits, and is used as the start delimiter of the scheduling request instruction; the data field occupies bytes 1 to 9 (bits 0-7 per byte), with a total length of 72 bits (i.e., 9 bytes), and is used to carry the scheduling data of the scheduling request instruction; the check bit field is located in byte 10 (bits 0-7), with a length of 8 bits, and is used to perform integrity verification on the data field; the instruction tail field is located in byte 11 (bits 0-7), with a length of 8 bits, and serves as the end delimiter of the scheduling request instruction.

[0115] In some implementations, the source node calculates a checksum from the extracted first-digit bytes of data using a preset algorithm. This checksum is then compared with the extracted second-digit bytes of data. If they match, the checksum passes; otherwise, an error occurs during transmission, and the scheduling request is discarded.

[0116] For example, the preset algorithm may be a summation check, parity check, cyclic redundancy check, etc.

[0117] In some embodiments, the source node compares the instruction data with the check data to perform integrity verification, summing the multiple bytes of the first digit to obtain the check sum data; if the check sum data matches the check data, the integrity verification is determined to be successful.

[0118] After extracting the first digit from multiple bytes of data, the source node performs arithmetic summation on the values ​​of each byte in the data sequence. During the calculation, carry-over can be ignored (or only the lower 8 bits of the sum can be retained, etc.), ultimately resulting in a single-byte value, which is the checksum. Subsequently, the source node compares this calculated checksum bit by bit with the checksum extracted from the instruction. If the two match, the scheduling request instruction is deemed to have been transmitted completely and without error, and the check passes.

[0119] For example, suppose the fixed format of a scheduling request instruction is: 1-byte frame header (0xEF) + 9 bytes of instruction data + 1-byte checksum + 1-byte frame trailer (0x16). The first few bytes are the 9 bytes of instruction data plus the frame header, totaling 10 bytes. After extracting these 10 bytes, the source node performs a summation operation, adding the values ​​of these 10 bytes one by one to calculate a single-byte checksum (for example, the lower 8 bits of the sum can be used). Simultaneously, it retrieves the 1-byte checksum pre-calculated and filled in by the external device from the frame trailer. If the calculated checksum is exactly equal to the extracted checksum, the data is considered complete; otherwise, an error has occurred during transmission, and the instruction is discarded.

[0120] In the above embodiments, summation check is used as the integrity check method. Under the premise of meeting the basic error detection requirements, the check speed is optimized. The implementation is relatively simple and fast, and hardly introduces any additional processing delay, thereby improving the overall timeliness from scheduling requirement instructions to scheduling frames.

[0121] For example, Figure 2 This is a schematic diagram illustrating the process by which the source node processes scheduling request instructions and generates a scheduling frame, as provided in an embodiment of this application. Figure 2 As shown, taking the source node as CCO as an example, the frame header of the scheduling request instruction is 0xEF, the frame tail is 0x16, and the fixed length is 12 bytes. After CCO starts processing the scheduling request, CCO first receives data through a serial port or Ethernet interface. Then, CCO searches for the frame header 0xEF in the received data byte by byte. During this process, CCO needs to determine whether the data retrieval is complete. If the data retrieval is complete, the process terminates; if the data retrieval is not complete, CCO further determines whether the frame header 0xEF has been found. If not found, it returns to the step of searching for the frame header 0xEF byte by byte to continue execution; if the frame header 0xEF is found, the data reading position is shifted 10 bytes forward, and it is determined whether the identifier corresponding to this position is the frame tail 0x16. If not, it returns to the step of searching for the frame header 0xEF byte by byte to continue execution; if so, CCO extracts the value Z corresponding to the byte before the frame tail, and at the same time calculates the checksum Y corresponding to the 10 consecutive bytes of data starting from the current frame header, which is the second byte of data. Subsequently, the CCO checks the consistency of the values ​​of Z and Y. If they are inconsistent, it indicates that the current scheduling request instruction is unavailable, and execution returns to the step of searching for the frame header 0xEF byte by byte. If they are consistent, the CCO extracts the valid data X corresponding to bytes 1 to 9 after the current frame header. After data extraction, the CCO constructs a scheduling frame and writes the valid data X into the data field of the scheduling frame. Finally, the CCO sends the scheduling frame to the STA via a carrier communication link or a wireless communication link, ending the process of processing the scheduling request instruction and generating the scheduling frame.

[0122] Figure 3 This is a schematic diagram of the framework for generating a scheduling frame from a scheduling request instruction, provided in an embodiment of this application. For example... Figure 3 As shown, via link A1, the execution device external to the CCO (e.g., a centralized data acquisition unit) generates a scheduling request and sends the scheduling request instruction to the CCO via serial port or Ethernet. Subsequently, via link A2, the CCO performs operations such as verification, parsing, and protocol conversion on the scheduling request instruction, extracts the scheduling data, and encapsulates it into a scheduling frame without a frame payload, which is then sent to the target STA via the power line carrier link. Finally, via link A3, the STA receives and parses the scheduling frame, reassembles the scheduling data into a scheduling instruction recognizable by the external execution device (e.g., an inverter) according to its interface protocol, and sends it to the external execution device for execution via serial port or Ethernet.

[0123] In the above embodiments, by processing the scheduling request instructions of the externally mounted devices of the source node, verifying the external instructions and extracting the data, only complete and correct instruction content will be encapsulated into the scheduling frame. This isolates data transmission errors that may exist on external links or externally mounted devices from the high-speed carrier network, thereby improving the data integrity and execution reliability of the scheduling system.

[0124] Figure 4 This is a flowchart illustrating a power line carrier communication scheduling method provided in other embodiments of this application. For example... Figure 4 As shown, the power line carrier communication scheduling method includes steps 410 to 420.

[0125] Step 410: The station receives a scheduling frame sent by the source node; wherein the scheduling frame carries scheduling data but does not include the frame payload field.

[0126] Step 420: The site generates scheduling instructions based on the scheduling data and outputs the scheduling instructions to the corresponding external mounted devices.

[0127] The sites provided in this application include, but are not limited to, inverter communication control modules in photovoltaic power generation systems, smart switches or pole-mounted controllers in distribution networks, turnout control units, signal controllers, track status monitoring units, smart meters or terminal acquisition units in electricity information acquisition systems, or other industrial IoT terminals. The sites can also be conventional communication sites capable of receiving and responding to scheduling frames.

[0128] The site can be implemented by hardware or functional modules such as power line carrier communication modules, dedicated communication chips, or processors that execute corresponding program instructions integrated in the above-mentioned equipment.

[0129] External mounted equipment refers to the execution equipment connected to the station and controlled by scheduling instructions.

[0130] It should be noted that the scheduling frames and the scheduling data they carry are a simplified format designed specifically for high-speed, low-latency transmission within power line carrier communication networks. However, externally mounted devices (such as industrial controllers and inverters) typically follow their own fixed serial or Ethernet communication protocols (e.g., formats containing specific frame headers, checksums, and trailers). Therefore, the station, acting as a protocol adapter, needs to repackage and assemble the received scheduling data into a complete scheduling instruction format so that it can be correctly received and executed by external devices.

[0131] Specifically, after receiving and verifying the scheduling frame, the station extracts the scheduling data, which serves as the core of the instruction, from its data field. Subsequently, the station reassembles the scheduling data according to the communication protocol rules agreed upon by the externally mounted device.

[0132] In some embodiments, the scheduling frame includes a delimiter type field and a data field; the station receives the scheduling frame sent by the source node, monitors the data frames broadcast in the power line carrier communication network, and identifies the delimiter type field of the data frame; if the field value in the delimiter type field is a preset value, the station determines that the data frame is a scheduling frame and extracts the scheduling data carried in the data field field of the scheduling frame.

[0133] Specifically, the delimiter type field is located at a specific position in the scheduling frame (e.g., the first 3 bits of the frame control field). When a station begins receiving data frames broadcast in a power line carrier communication network, it first parses the delimiter type field of the data frame. When the station recognizes that the field value of the delimiter type field corresponds to a preset scheduling frame field value, it determines that the currently received data frame is a scheduling frame, thereby triggering scheduling frame processing. If the field value of the delimiter type field is other than a normal data frame or a management frame, the station can process it according to the normal procedure or ignore it directly.

[0134] By identifying the delimiter type field value corresponding to the scheduling frame, the site can concentrate processing resources on scheduling instructions, which can effectively improve the real-time performance of the site when processing mixed traffic.

[0135] In some embodiments, the scheduling frame includes a network type field for indicating the type of control system to which the scheduling data belongs, and different network types correspond to different preset scheduling data encapsulation rules; the station generates scheduling instructions based on the scheduling data, determines the target control system type to which the scheduling data belongs according to the field value in the network type field of the scheduling frame, determines the target scheduling data encapsulation rule corresponding to the target control system type, and encapsulates the scheduling data into scheduling instructions according to the target scheduling data encapsulation rule.

[0136] Among them, the preset scheduling data encapsulation rules refer to the predefined or configured protocol conversion specifications, which clearly stipulate how to encapsulate the scheduling data transmitted within the power line carrier communication network into scheduling instructions that can be correctly identified and executed by specific types of external mounted devices.

[0137] Specifically, the network type field carries network identification information in the scheduling frame. After successfully receiving and verifying a data frame, the station extracts the value of its network type field (e.g., field value 1 represents a photovoltaic power generation control system, value 2 represents a distribution information control system, etc.). The station internally stores or configures a mapping table of scheduling data encapsulation rules corresponding to each network type value. For example, for a photovoltaic power generation control system (field value 1), the encapsulation rule may require encapsulating the scheduling data as a Modbus Remote Terminal Unit (Modbus RTU) message with a specific function code; for a distribution information control system (field value 2), it may require encapsulation as an Application Service Data Unit (ASDU). The station can determine the specific encapsulation rule to be used by looking up the table.

[0138] By introducing a network type field and corresponding encapsulation rule selection, the same physical communication facility and the same scheduling frame format can logically isolate and serve multiple different control system scenarios. Sites automatically switch based on this field, preventing scheduling instructions from being incorrectly assembled into other scheduling instructions, thus reducing deployment complexity and maintenance costs when multiple systems coexist.

[0139] In some implementations, the station generates scheduling instructions based on scheduling data encapsulation rules and scheduling data, performs verification calculations on the scheduling data to obtain verification data, and encapsulates the scheduling data and verification data according to the scheduling data encapsulation rules to generate scheduling instructions.

[0140] After determining the scheduling data encapsulation rules, the site first performs verification operations on the scheduling data according to the requirements of the scheduling data encapsulation rules to obtain verification data.

[0141] In some implementations, the station performs a verification operation on the scheduling data extracted from the scheduling frame to obtain verification data. For example, if the scheduling data encapsulation rules require the generation of instructions in the format of "frame header + data + checksum + frame trailer", the station calculates the sum of all bytes of the scheduling data and takes the lower 8 bits as the verification data.

[0142] In some other implementations, the station performs a specified verification operation on the scheduling data extracted from the scheduling frame and the fixed frame header data to be added. For example, if the scheduling data encapsulation rules require the generation of an instruction in the format of "frame header + data + checksum + frame trailer", the station calculates the sum of all bytes of the scheduling data and the fixed frame header data to be added, and takes the lower 8 bits as the verification data.

[0143] Following this, the site assembles the fixed instruction header, scheduling data, calculated verification data, and fixed instruction tail sequentially according to the byte order and field structure defined by the encapsulation rules, generating a complete scheduling instruction.

[0144] Figure 5 This is a schematic diagram illustrating the process of site identification and processing of scheduling frames provided in an embodiment of this application. For example... Figure 5 As shown, after the source node begins transmitting a scheduling frame, the STA receives data frames from the local network via power line carrier or wireless radio frequency link and performs integrity verification on the data frames. The STA then determines whether the verification result is correct. If the verification fails, the data frame is discarded, and the process terminates. If the verification is correct, the STA further parses the delimiter type field of the data frame to determine if it is a scheduling frame identified by a preset value. If not, it proceeds to the regular processing flow for other types of messages (such as beacon frames or SOF data frames). If it is, the station extracts the scheduling data X carried in the data field of the scheduling frame from a fixed position. After data extraction, the STA adds a preset frame header (e.g., 0xEF) before the scheduling data X according to predetermined encapsulation rules and performs specified verification operations (e.g., summation) on the data after adding the header to generate verification data Y. Subsequently, the STA adds a preset frame trailer (e.g., 0x16) after the verification data Y, thereby reassembling a complete scheduling instruction conforming to the interface specification of the external mounted device. Then, the STA sends the reassembled scheduling instruction to the corresponding external mounted device via its serial port or Ethernet port. Finally, the externally mounted device receives and parses the scheduling instructions through this interface to execute the corresponding control operations, thus ending the process of issuing and responding to the scheduling instructions.

[0145] According to the power line carrier communication scheduling method provided in this application embodiment, the station receives scheduling frames issued by the source node. The scheduling frames carry scheduling data but do not include a frame payload field, realizing the reception and parsing of scheduling instructions in the internal network transmission format. This allows the station to extract scheduling data with low processing overhead. Subsequently, the station generates scheduling instructions based on the scheduling data and outputs the scheduling instructions to the corresponding external mounted devices. This achieves the adaptation between the internal network protocol and external industrial equipment, ensuring the accuracy and timeliness of scheduling instruction transmission, and providing a communication solution for industrial control scenarios such as centralized photovoltaic regulation and intelligent power distribution.

[0146] In this embodiment of the application, a communication system architecture suitable for power line carrier communication is constructed to enable the rapid issuance of scheduling instructions in the power line carrier communication network. It should be noted that the communication system architecture described in this embodiment is used to illustrate the implementation environment of the scheduling method provided in this application and does not constitute a limitation on the scope of protection of this application.

[0147] In some embodiments, the communication system includes a source node, a station, and a relay node located between the source node and the station. The relay node is used to forward scheduling frames without changing the content of the scheduling frames, thereby extending the communication coverage.

[0148] Figure 6 This is a flowchart illustrating a power line carrier communication scheduling method provided in some embodiments of this application. For example... Figure 6 As shown, the power line carrier communication scheduling method includes steps 610 to 620.

[0149] Step 610: The source node generates a scheduling frame; wherein the scheduling frame carries scheduling data but does not include the frame payload field.

[0150] Step 620: The source node sends a scheduling frame to the relay node to instruct the relay node to generate a scheduling instruction based on the scheduling data and output the scheduling instruction to the corresponding external mounted device.

[0151] The process of the source node generating the scheduling frame in this embodiment is the same as that in the above embodiment, and will not be repeated here to avoid repetition.

[0152] The relay node provided in this application embodiment may be, for example, a proxy coordinator (PCO). A relay node is an intermediate functional entity deployed in a power line carrier communication network, located between a source node (e.g., CCO) and one or more stations (STAs), used to receive, forward, and possibly respond to scheduling frames.

[0153] The main function of a relay node is to receive scheduling frames from source nodes or other relay nodes and forward them to downstream target sites without modification, thereby extending the physical coverage and topology flexibility of the network.

[0154] In some implementations, the source node sends a scheduling frame to the relay node, specifically including: the relay node forwards the scheduling frame to the station without modifying the scheduling frame, so as to instruct the station to generate a scheduling instruction based on the scheduling data and output the scheduling instruction to the corresponding external mounted device.

[0155] In this process, the relay node (e.g., the proxy coordinator PCO) performs transparent link-layer relay forwarding after receiving the scheduling frame issued by the source node (e.g., the CCO).

[0156] Specifically, relay nodes synchronize and receive complete scheduling frames through the physical layer. Since scheduling frames have a fixed frame structure and length (e.g., 16 bytes) and are identified as scheduling frames by a specific delimiter type field (e.g., a value of 4), relay nodes can identify the type of scheduling frame.

[0157] In other implementations, once the relay node confirms that the frame is a scheduled frame to be forwarded and passes basic link-layer verification (such as CRC check of the sequence number field), it can initiate the forwarding process without parsing, extracting, or modifying the content of its network identifier, sequence number, data field, or other fields.

[0158] The relay node simply forwards the received original scheduling frame directly and as is to one or more STAs within its downstream communication range. After receiving the forwarded scheduling frame, the STA performs the parsing and encapsulation process as described above, and finally outputs the generated scheduling command to its external mounted device.

[0159] Furthermore, relay nodes can also be connected to corresponding externally mounted execution devices. Therefore, relay nodes can not only forward scheduling frames, but also parse the scheduling data in the scheduling frames and control their own externally mounted execution devices accordingly.

[0160] In some other implementations, relay nodes can forward scheduling frames to one or more downstream stations (STAs) without modifying the core content of the scheduling frames, while parsing the scheduling data in the scheduling frames and controlling the execution devices attached to their own external devices accordingly.

[0161] For example, Figure 7 This is a flowchart illustrating the central coordinator and relay node processing of scheduling frames provided in an embodiment of this application. For example... Figure 7 As shown, taking the Central Coordinator Carrier Communication Module (CCO), Relay Node Agent Coordinator (PCO), and STA on the centralized acquisition unit as examples, when the CCO generates a scheduling request or receives a scheduling request from the externally mounted centralized acquisition unit, it sends a scheduling frame. After receiving the scheduling frame from the CCO, the relay node PCO quickly forwards the scheduling frame and, if it has a scheduling device mounted on it, parses the scheduling frame and sends scheduling instructions to its corresponding externally mounted device according to the scheduling frame. After receiving the scheduling frame, the STA parses the scheduling frame, converts the scheduling data carried in the scheduling frame into scheduling instructions that can be recognized by the externally mounted device, and sends scheduling instructions to its corresponding externally mounted device.

[0162] In some embodiments, the power line carrier communication scheduling method described above underwent a scheduling instruction issuance delay test. When the source node's serial port baud rate is configured to 460,800 bits per second, the time taken for the node to process and issue the scheduling instruction is 260 microseconds. At the same baud rate, the time taken for the station to receive and convert the instruction is also 260 microseconds. The time interval between the two serial port processing stages, i.e., the transmission and processing time of the scheduling frame in the power line carrier channel, was measured to be 1.008 milliseconds. This data indicates that the power line carrier communication scheduling method provided in this application achieves a scheduling instruction issuance delay at the millisecond level.

[0163] According to the power line carrier communication scheduling method provided in this application embodiment, a scheduling frame is generated by the source node, and the scheduling frame carries scheduling data. The scheduling frame does not include a frame payload field, which effectively simplifies the frame structure and shortens the inherent delay caused by the traditional frame structure transmission. The communication latency is reduced from the data link layer. The scheduling frame is sent from the source node to the relay node to instruct the relay node to generate scheduling instructions based on the scheduling data and output the scheduling instructions to the corresponding external mounted devices. This realizes the reliable extension of scheduling instructions in complex topology networks, improves the network coverage and deployment flexibility of scheduling instructions, and enables them to adapt to various networking scenarios. It provides a communication method with both low latency and good scalability for large-scale distributed real-time control systems.

[0164] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0165] In some embodiments, Figure 8 This is a schematic diagram of the structure of the electronic device provided in an embodiment of this application. For example... Figure 8 As shown, this application embodiment also provides an electronic device 800, including a processor 801, a memory 802, and a computer program stored in the memory 802 and executable on the processor 801. When the program is executed by the processor 801, it implements the various processes of the above-described power line carrier communication scheduling method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0166] This application provides a non-transitory computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described power line carrier communication scheduling method embodiment and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0167] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable media, such as computer read-only memory (ROM), random-access memory (RAM), magnetic disks, or optical disks.

[0168] The computer-readable storage medium may include: read-only memory (ROM), random-access memory (RAM), magnetic disk or optical disk, etc.

[0169] This application provides a computer program product, including a computer program that, when executed by a processor, implements the above-described power line carrier communication scheduling system method.

[0170] This application provides a chip that includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described power line carrier communication scheduling system method embodiments and achieve the same technical effects. To avoid repetition, it will not be described again here.

[0171] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0172] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0173] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the related technology, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0174] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

[0175] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0176] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.

Claims

1. A power line carrier communication scheduling method, characterized in that, The method includes: The source node generates a scheduling frame; wherein the scheduling frame carries scheduling data but does not include a frame payload field; The source node sends the scheduling frame to the station to instruct the station to generate a scheduling instruction based on the scheduling data and output the scheduling instruction to the corresponding external mounted device.

2. The power line carrier communication scheduling method according to claim 1, characterized in that, The scheduling frame adopts the control frame format of the data link layer, and the total length of the scheduling frame is a fixed length.

3. The power line carrier communication scheduling method according to claim 1, characterized in that, The scheduling frame includes at least the following fields: A delimiter type field is used to indicate that the current frame is a scheduling frame when the field value of the delimiter type field is a preset value. The network type field indicates the type of control system to which the scheduling data belongs; different network types correspond to different preset scheduling data encapsulation rules; The network identification field is used to distinguish different power line carrier communication networks; The sequence number field is used to identify the transmission order of the scheduling frames and to filter duplicate scheduling frames received by the station. The data field is used to carry the scheduling data; The verification field is used to verify the data integrity of the scheduling frame.

4. The power line carrier communication scheduling method according to claim 3, characterized in that, The network type field is configured with at least one of the following field values: The first field value is used to indicate the transmission of the scheduling frame in the electricity information collection system; The second field value is used to indicate the transmission of the scheduling frame in the photovoltaic power generation control system; The third field value is used to indicate the transmission of the scheduling frame in the power distribution information control system; The fourth field value is used to indicate the transmission of the scheduling frame in the rail transit control system.

5. The power line carrier communication scheduling method according to claim 1, characterized in that, The source node broadcasts scheduling frames in the power line carrier communication network.

6. The power line carrier communication scheduling method according to claim 1, characterized in that, The source node receives scheduling request instructions from externally mounted devices via a serial port or Ethernet port, and determines the scheduling data based on the scheduling request instructions; and / or, autonomously generates the scheduling data.

7. The power line carrier communication scheduling method according to claim 6, characterized in that, The method further includes: Upon receiving a scheduling request instruction, the source node identifies the instruction header of the scheduling request instruction and obtains the instruction tail according to the fixed length of the scheduling request instruction. Extract the first byte of data before the end of the instruction as instruction data, and extract the second byte of data before the end of the instruction as check data; The instruction data is compared with the verification data to perform an integrity check, and if the integrity check passes, the instruction data is used as the scheduling data.

8. A power line carrier communication scheduling method, characterized in that, The method includes: The station receives a scheduling frame sent by the source node; wherein the scheduling frame carries scheduling data but does not include a frame payload field; The station generates scheduling instructions based on the scheduling data and outputs the scheduling instructions to the corresponding external mounted devices.

9. The power line carrier communication scheduling method according to claim 8, characterized in that, The scheduling frame includes a delimiter type field and a data field; the station receives the scheduling frame sent by the source node, including: Monitor data frames broadcast in a power line carrier communication network and identify the delimiter type field of the data frames; If the field value in the delimiter type field is a preset value, the data frame is determined to be a scheduling frame, and the scheduling data carried in the data field field of the scheduling frame is extracted.

10. The power line carrier communication scheduling method according to claim 8, characterized in that, The scheduling frame includes a network type field indicating the type of control system to which the scheduling data belongs, and different network types correspond to different preset scheduling data encapsulation rules; the station generates scheduling instructions based on the scheduling data, including: The target control system type to which the scheduling data belongs is determined based on the field value in the network type field of the scheduling frame; Determine the target scheduling data encapsulation rules corresponding to the target control system type, and encapsulate the scheduling data into scheduling instructions according to the target scheduling data encapsulation rules.

11. A power line carrier communication scheduling method, characterized in that, The method includes: The source node generates a scheduling frame; wherein the scheduling frame carries scheduling data but does not include a frame payload field; The source node sends the scheduling frame to the relay node to instruct the relay node to generate a scheduling instruction based on the scheduling data and output the scheduling instruction to the corresponding external mounted device.

12. The power line carrier communication scheduling method according to claim 11, characterized in that, The source node sends the scheduling frame to the relay node, including: The relay node forwards the scheduling frame to the station without modifying the scheduling frame, so as to instruct the station to generate a scheduling instruction based on the scheduling data and output the scheduling instruction to the corresponding external mounted device.

13. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the power line carrier communication scheduling method as described in any one of claims 1-12.

Images