A power grid data scheduling method, device and system

Abstract

The application belongs to the technical field of electric power communication, and discloses a power grid data scheduling method, device and system. The scheduling method is applied to a wireless central coordinator and includes the following steps: in response to a scheduling instruction, remote control instructions or telemetry instructions are aggregated to obtain a first data frame and send the first data frame to each terminal device; a remote control scheduling request and a telemetry scheduling request corresponding to the first data frame are generated; corresponding uplink channel resources are allocated to each remote control scheduling request and each telemetry scheduling request, and the uplink channel resources are aggregated into a second data frame and sent to each terminal device; a third data frame is received and first message type information is extracted; if the first message type information is a preset response parameter, the third data frame is taken as a response data frame; and if the first message type information is a preset alarm parameter, the third data frame is taken as a remote signaling data frame. The application can avoid uplink conflict and collision of the third data frame of the terminal device without handshaking and without changing existing hardware devices.

Description

Technical Field

[0001] This application relates to the field of power communication technology, and in particular to a method, device and system for scheduling power grid data. Background Technology

[0002] In power grid applications such as smart water, electricity, and gas meters, business platforms often need to periodically call various terminals to obtain their metering data, such as daily / monthly freezes and real-time consumption records. However, in scenarios where downlink triggers multiple uplinks, collisions are extremely likely to occur. This is because when a large number of terminal modules are connected to the same gateway, they simultaneously receive the call and send uplink data at the same frequency. Several common methods can now resolve uplink collisions, such as CSMA-CA pre-transmission detection and pre-transmission request for RTS / CTS.

[0003] However, efficient implementation of CSMA-CA requires hardware support, such as fast signal detection and processing capabilities, to reduce latency within the contention window. Without hardware support, latency increases significantly. While the RTS / CTS mechanism can reduce collisions between hidden nodes, it introduces additional signaling overhead, requiring the transmission of two control frames (RTS and CTS) for each communication to perform a handshake, further increasing latency. Summary of the Invention

[0004] This application provides a method, device, and system for scheduling power grid data, which can avoid uplink collisions of third data frames from terminal devices without handshaking or changing existing hardware.

[0005] In a first aspect, embodiments of this application provide a method for scheduling power grid data, applied to a wireless central coordinator, comprising:

[0006] In response to the scheduling instruction, the remote control instructions in the remote control queue or the telemetry instructions in the telemetry queue are aggregated according to the maximum data length in the scheduling instruction to obtain the first data frame and send it to each terminal device.

[0007] The remote control scheduling request corresponding to each remote control command and the telemetry scheduling request corresponding to each telemetry command are generated in the first data frame; in the preset time slot after the first data frame is sent, the corresponding uplink channel resources are allocated to each remote control scheduling request and each telemetry scheduling request, and they are aggregated into a second data frame and sent to each terminal device.

[0008] The system receives the third data frame from the terminal device and extracts the first message type information from the third data frame. If the first message type information is a preset response parameter, the system sends the third data frame as a response data frame to the upper-level device. The system determines the corresponding remote control scheduling request or telemetry scheduling request based on the uplink channel resources used by the response data frame and deletes the corresponding telemetry scheduling request or remote control scheduling request. If the first message type information is a preset alarm parameter, the system sends the third data frame as a remote signaling data frame to the upper-level device.

[0009] Furthermore, the method also includes:

[0010] Receive downlink service data and extract the second message type information from the downlink service data;

[0011] If the second message type information is a preset control parameter, then extract the control type information from the downlink service data;

[0012] If the control type information is a preset telemetry parameter, then a telemetry command is generated based on the downlink service data and placed in the telemetry queue; otherwise, a remote control command is generated based on the downlink service data and placed in the remote control queue.

[0013] Furthermore, in response to the scheduling instruction, the remote control instructions in the remote control queue or the telemetry instructions in the telemetry queue are aggregated according to the maximum data length in the scheduling instruction to obtain a first data frame, which is then sent to each terminal device, including:

[0014] Remote control judgment steps: In response to the scheduling command, determine whether the remote control queue is empty;

[0015] If not empty, determine whether the difference between the maximum data length and the length of the queue to be aggregated is greater than or equal to the length of the first remote control instruction in the remote control queue; if yes, put the remote control instruction into the queue to be aggregated and return to the remote control judgment step; if no, generate the first data frame based on the queue to be aggregated.

[0016] If empty, then execute the telemetry judgment step: determine whether the telemetry queue is empty;

[0017] If not empty, determine whether the difference between the maximum data length and the length of the queue to be aggregated is greater than or equal to the length of the first telemetry instruction in the telemetry queue; if yes, put the telemetry instruction into the queue to be aggregated and return to the telemetry judgment step; if empty or no, generate the first data frame based on the queue to be aggregated.

[0018] Furthermore, in the preset time slot following the transmission of the first data frame, corresponding uplink channel resources are allocated to each remote control scheduling request and each telemetry scheduling request, and these are aggregated into a second data frame and sent to each terminal device, including:

[0019] Set the scheduling identifier information of each remote scheduling request to the first value and put it into the remote scheduling queue;

[0020] Set the scheduling identifier information of each telemetry scheduling request to the first value and put it into the telemetry scheduling queue;

[0021] Perform the following remote control scheduling judgment steps: Determine if the remote control scheduling queue is empty;

[0022] If not empty, then execute the uplink resource judgment step: determine whether the uplink resources are exhausted; if not exhausted, allocate uplink channel resources for the first remote scheduling request in the remote scheduling queue whose first scheduling identifier information is the first value, change the scheduling identifier information to the second value, and return to the remote scheduling judgment step.

[0023] If empty, then execute the telemetry scheduling judgment step: determine whether the telemetry scheduling queue is empty;

[0024] If not empty, then execute the uplink resource judgment step;

[0025] If not exhausted, allocate uplink channel resources to the telemetry scheduling request whose first scheduling identifier information in the telemetry scheduling queue is the first value, change the scheduling identifier information to the second value, and return to the telemetry scheduling judgment step.

[0026] If the uplink resources are empty or exhausted, a second data frame is generated based on the allocated uplink channel resources.

[0027] Furthermore, the method also includes:

[0028] Generate a current time slot channel information with a length of 1 byte based on the normal uplink resources and reserved uplink resources of the current time slot;

[0029] The channel configuration for the next time slot, with a length of 1 byte, is generated based on the normal uplink resources and reserved uplink resources of the next time slot.

[0030] Among them, the bit corresponding to the occupied channel in the normal uplink resources is the first preset value, and the bit corresponding to the idle channel in the normal uplink resources and each channel in the reserved uplink resources is the second preset value.

[0031] The fourth data frame is generated based on the current time slot channel conditions and the next time slot channel conditions, and then sent to each terminal device.

[0032] Furthermore, the method also includes:

[0033] Extract the rescheduling instruction information from the control field of the response data frame; if the rescheduling instruction information is equal to the preset fragmentation value, change the scheduling identifier information of the remote control scheduling request or telemetry scheduling request corresponding to the response data frame to the first value; otherwise, delete the remote control scheduling request or telemetry scheduling request corresponding to the response data frame.

[0034] Furthermore, the method also includes:

[0035] If the allocated uplink channel resources do not receive a third data frame or acknowledgment message, determine whether the number of retransmissions of the corresponding remote control scheduling request or telemetry scheduling request is less than the preset retransmission threshold. If yes, change the corresponding scheduling identifier information to the first value and increment the number of retransmissions by 1. If no, delete the corresponding remote control scheduling request or telemetry scheduling request.

[0036] In a preset time slot after sending the first data frame, corresponding uplink channel resources are allocated to each remote control scheduling request and each telemetry scheduling request, and these are aggregated into a second data frame and sent to each terminal device, including:

[0037] Perform the remote scheduling judgment step; if the remote scheduling queue is not empty, perform the uplink resource judgment step.

[0038] If not exhausted, determine if there is a remote scheduling request in the remote scheduling queue with a retransmission count not equal to 0 and a scheduling identifier information of the first value; if there is, allocate uplink channel resources to the remote scheduling request; if not, allocate uplink channel resources to the first remote scheduling request in the remote scheduling queue with a scheduling identifier information of the first value, change the scheduling identifier information to the second value, and return to the remote scheduling judgment step.

[0039] If the remote control scheduling queue is empty, then execute the telemetry scheduling judgment step;

[0040] If not empty, then execute the uplink resource judgment step;

[0041] If not exhausted, determine if there is a telemetry scheduling request in the telemetry scheduling queue with a retransmission count not equal to 0 and a scheduling identifier information of the first value; if there is, allocate uplink channel resources to the telemetry scheduling request; if not, allocate uplink channel resources to the first telemetry scheduling request in the telemetry scheduling queue with a scheduling identifier information of the first value, change the scheduling identifier information to the second value, and return to the telemetry scheduling judgment step.

[0042] If the uplink resources are empty or exhausted, a second data frame is generated based on the allocated uplink channel resources.

[0043] Furthermore, the method also includes:

[0044] After sending the second data frame, the uplink frequency point of the uplink channel resources allocated to each terminal device in the second data frame is used as the camping frequency point of the corresponding terminal device.

[0045] After receiving the response data frame, extract the frequency update instruction from the control field of the response data frame;

[0046] If the frequency update command is equal to the preset frequency update parameter, then update the camping frequency of the corresponding terminal device according to the uplink frequency of the response data frame; otherwise, keep the camping frequency of the terminal device unchanged.

[0047] The steps for allocating uplink channel resources for a remote control scheduling request or a telemetry scheduling request include:

[0048] Determine whether the number of requests in the remote control scheduling queue and the telemetry scheduling queue is equal to the number of channels minus 1;

[0049] If so, the priority allocation step for the stationary frequency point is executed: uplink channel resources are allocated according to the stationary frequency point of the terminal device corresponding to the remote control scheduling request or telemetry scheduling request and the idle ordinary uplink resources; if there is no stationary frequency point among the idle ordinary uplink resources, uplink channel resources are randomly allocated according to the preset principle.

[0050] If not, determine whether the difference between the maximum number of terminals and the minimum number of terminals in each channel is less than or equal to the preset number of terminals; if not, remove the channel corresponding to the maximum number of terminals; if yes or after removing the channel, execute the priority allocation step for the stationed frequency point; if there are no stationed frequency points in the idle ordinary uplink resources, randomly allocate uplink channel resources that meet the preset principle in order of the number of terminals in each channel from the smallest to the largest.

[0051] Furthermore, the preset principles include: randomly assigned frequency points and each stationary frequency point is different; the method also includes:

[0052] After randomly allocating uplink channel resources, the randomly allocated frequency points are used as the camping frequency points of the corresponding terminal devices, and it is determined whether the difference between the maximum number of camping terminals and the minimum number of camping terminals in each channel is less than or equal to the preset number of camping terminals; if so, uplink channel resources are randomly re-allocated according to the preset principle.

[0053] Furthermore, the first data frame includes a subframe number, control information, and multiple instruction frames; the subframe number is 1 byte long; the control information is between 1 and 11 bytes long; and the instruction frames are between 0 and 16 bytes long.

[0054] The instruction frame includes frame type information, frame length information, and instruction content; the frame type information and frame length information are both 4 bits in length, and the instruction content is between 0 and 15 bytes in length.

[0055] Furthermore, the preset response parameter is equal to 000 or 101; the preset alarm parameter is equal to 010; the preset telemetry parameter is equal to 2; the first preset value is 1, the second preset value is 0; the preset segment value is equal to 1; and the preset frequency update parameter is equal to 1.

[0056] Secondly, embodiments of this application provide a wireless central coordinator, including a module for executing a power grid data scheduling method as described in any of the above embodiments.

[0057] Thirdly, embodiments of this application provide a method for scheduling power grid data, applied to a terminal device, including:

[0058] After receiving the first data frame sent by the wireless central coordinator, determine whether there is a telemetry command or remote control command corresponding to the preset address based on the command content of each command frame in the first data frame.

[0059] If it exists, a third data frame is generated based on telemetry or remote control commands;

[0060] After receiving the second data frame from the wireless central coordinator, determine whether there is an uplink channel resource corresponding to the preset address based on the instruction content of each instruction frame in the second data frame.

[0061] If present, the third data frame is sent to the wireless central coordinator via uplink channel resources;

[0062] Upon receiving alarm data, a third data frame is generated based on the alarm data;

[0063] The remote signaling channel resources are determined based on the fourth data frame sent by the wireless central coordinator;

[0064] The third data frame is sent to the wireless central coordinator via the remote signaling channel resource.

[0065] Furthermore, the method also includes:

[0066] When the uplink time slot specified by the uplink channel resource arrives, determine whether the third data frame has been generated;

[0067] If not, an acknowledgment message is sent on the uplink channel resources; and after the third data frame is generated, the third data frame is sent to compete with the fourth data frame for the uplink channel resources according to the uplink frequency point specified by the uplink channel resources.

[0068] Furthermore, the above-mentioned transmission of the third data frame based on the uplink frequency point specified by the uplink channel resources and the competition for uplink channel resources with the fourth data frame includes:

[0069] Determine whether the fourth data frame contains the uplink frequency point specified by the uplink channel resource;

[0070] If so, the third data frame will be sent using the uplink frequency and the time slot resources obtained through contention.

[0071] If not, the third data frame is sent using the time slot and frequency resources obtained through competition, and before sending, the frequency update instruction in the control field of the third data frame is changed to the preset frequency update parameter.

[0072] Furthermore, the method also includes:

[0073] Determine whether the uplink channel resources are sufficient to transmit the complete third data frame; if so, send the third data frame; if not, fragment the third data frame based on the uplink channel resources to obtain multiple third data frames.

[0074] Set the rescheduling indication information of each third data frame except the last third data frame to the preset fragmentation value;

[0075] The third data frame is sent to the wireless central coordinator via uplink channel resources.

[0076] Furthermore, the method also includes:

[0077] When competing for uplink channel resources, determine whether the number of bits equal to the second preset value in the current time slot channel situation or the next time slot channel situation of the fourth data frame is greater than the preset reserved channel number.

[0078] If yes, then compete for normal uplink resources; if not, then make the third data frame wait for a preset time.

[0079] If, in the fourth data frame received after a preset duration, the number of bits equal to the second preset value in both the current time slot channel condition and the next time slot channel condition is equal to the preset reserved channel number, then the third data frame will be sent by competing for reserved uplink resources.

[0080] Furthermore, the aforementioned third data frame includes verification status information, frame type information, control field, frame length field, service information length field, and service information.

[0081] Fourthly, embodiments of this application provide a terminal device, including a module for executing a power grid data scheduling method as described in any of the above embodiments.

[0082] Fifthly, embodiments of this application provide a power grid data scheduling system, including a wireless central coordinator that executes the power grid data scheduling method as described in any of the above embodiments; and at least one terminal device disposed in the power grid that executes the power grid data scheduling method as described in any of the above embodiments.

[0083] In summary, compared with the prior art, the beneficial effects of the technical solution provided in this application include at least the following:

[0084] This application provides a method for scheduling power grid data. First, this application utilizes the mechanism that downlink in the power grid system inevitably triggers uplink data. After the wireless central coordinator sends a first data frame including remote control instructions or telemetry instructions, it allocates uplink channel resources to each terminal device according to the instructions in the first data frame. The allocated uplink channel resources are then placed into a second data frame and sent to the terminal devices. This allows each terminal device to send the third data frame according to the uplink channel resources in the second data frame after generating a third data frame based on the remote control instructions in the first data frame. This avoids uplink collisions in the third data frame without handshake or modification of existing hardware. Attached Figure Description

[0085] Figure 1 A flowchart of a power grid data scheduling method provided as an exemplary embodiment of this application.

[0086] Figure 2 A flowchart of a first data frame aggregation step provided for an exemplary embodiment of this application.

[0087] Figure 3 A schematic diagram of the frame structure of a first data frame provided for an exemplary embodiment of this application.

[0088] Figure 4 This is a schematic diagram of the frame structure of MacCtrl in a first data frame provided for an exemplary embodiment of this application.

[0089] Figure 5 This is a schematic diagram of the frame structure of the dispersedUnicast in a second data frame provided as an exemplary embodiment of this application.

[0090] Figure 6 This is a schematic diagram of the frame structure of the dispersedItem in a second data frame provided as an exemplary embodiment of this application.

[0091] Figure 7 A flowchart illustrating the steps of allocating channel resources for a scheduling request, provided in an exemplary embodiment of this application.

[0092] Figure 8 This is a schematic diagram of channel resource priority provided for an exemplary embodiment of this application. Detailed Implementation

[0093] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0094] Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0095] The scheduling method of this application is mainly applied to the power grid monitoring system. It is mainly used for the transmission of telemetry, telecontrol, and remote information between a wireless central coordinator (such as an edge smart gateway) and multiple terminal devices (such as sensors). The smart gateway can send downlink telemetry commands and remote control commands, and at the same time receive uplink information from the sensors (including remote signaling alarms, monitoring data reporting, remote control result feedback, etc.). Various sensor devices are used to receive downlink telemetry commands or remote control commands and send uplink information.

[0096] In power grid applications where periodic monitoring data is collected, the edge application smart gateway triggers telemetry commands and sends them to the sensor application. The sensor collects corresponding parameter data according to the received commands and uploads it to the smart gateway. For example, for telemetry commands, the sensor collects monitoring data and uploads it to the smart gateway, while for remote control commands, it executes the corresponding actions and provides feedback on the execution results. In alarm linkage scenarios, the sensor can also remotely transmit alarm information to the smart gateway.

[0097] Please see Figure 1 This application provides a method for scheduling power grid data, applied to a wireless central coordinator, which may specifically include the following steps:

[0098] Step S11: In response to the scheduling instruction, the remote control instructions in the remote control queue or the telemetry instructions in the telemetry queue are aggregated according to the maximum data length in the scheduling instruction to obtain the first data frame and send it to each terminal device.

[0099] The dispatch command can be manually input or triggered at a preset cycle. When using cycle triggering, the cycle can be set according to the type of terminal device; for example, the data of an electricity meter is typically retrieved every 30 minutes.

[0100] It is worth noting that after aggregating remote control or telemetry commands into the first data frame, the wireless central coordinator must delete them from the corresponding remote control or telemetry queue to avoid repeatedly performing the recall operation.

[0101] Step S12: Generate remote control scheduling requests corresponding to each remote control command and telemetry scheduling requests corresponding to each telemetry command in the first data frame; in the preset time slot after sending the first data frame, allocate corresponding uplink channel resources for each remote control scheduling request and each telemetry scheduling request, and aggregate them into a second data frame and send it to each terminal device.

[0102] Specifically, the preset time slot can be two time slots.

[0103] Specifically, the frame format of the second data frame is the same as that of the first data frame, but the instruction content is different. The first data frame records the content of remote control or telemetry instructions, such as the information to be monitored or the operation to be performed by the terminal device, while the second data frame records the uplink channel resources allocated to the corresponding terminal device, including time domain and frequency domain information.

[0104] Step S13: Receive the third data frame from the terminal device and extract the first message type information of the third data frame.

[0105] Step S14: If the first message type information is a preset response parameter, then the third data frame is sent to the upper-level device as a response data frame; the corresponding remote control scheduling request or telemetry scheduling request is determined according to the uplink channel resources used by the response data frame, and the corresponding telemetry scheduling request or remote control scheduling request is deleted. The preset response parameter is equal to 000 or 101.

[0106] The first message type information can be obtained from the service information in the third data frame.

[0107] Step S15: If the first message type information is a preset alarm parameter, then the third data frame is sent to the upper-level device as a remote signaling data frame. The preset alarm parameter is 010.

[0108] Specifically, when the first message type information is a preset alarm parameter, it means that the third data frame is not triggered by the terminal device responding to the call of the wireless central coordinator, but rather by the device itself actively uploading alarm information.

[0109] In addition to the above, the scheduling method of this application also includes:

[0110] Step S01: Generate a 1-byte current timeslot channel information based on the normal uplink resources and reserved uplink resources of the current timeslot. The normal uplink resources are the portion allocated by the wireless central coordinator when allocating uplink channel resources, and the reserved uplink resources are the portion reserved for sudden uplink requests from terminal devices.

[0111] For example, if there are a total of 3 uplink channels, with 2 channels being regular uplink resources and 1 channel being reserved uplink resources, the wireless central coordinator will only allocate the 2 channels of regular uplink resources when allocating uplink channel resources to generate the second data frame.

[0112] Step S02: Generate a 1-byte channel information for the next time slot based on the normal uplink resources and reserved uplink resources of the next time slot. Specifically, the fourth data frame is sent to each terminal device in each time slot. Considering the time consumed by downlink transmission and terminal device parsing contention, this application also synchronizes the channel information of the next time slot to the terminal devices in real time.

[0113] Step S03, wherein the bit corresponding to the occupied channel in the normal uplink resources is a first preset value, and the bit corresponding to the idle channel in the normal uplink resources and each channel in the reserved uplink resources is a second preset value.

[0114] The first preset value can be 1, and the second preset value can be 0.

[0115] Specifically, in the fourth data frame, each bit corresponds to a channel. If the channel is idle in the current or next time slot, the corresponding bit value is the second preset value; otherwise, it is the first preset value. The bit positions for different channels are not fixed, meaning that the channel type corresponding to each bit in each transmitted fourth data frame can be different.

[0116] Step S04: Generate a fourth data frame based on the current time slot channel conditions and the next time slot channel conditions, and send it to each terminal device. Specifically, when the frame length information FrameLen in the fourth data frame is 1, the fourth data frame only carries the current time slot channel conditions; when FrameLen is 2, the fourth data frame carries both the current time slot channel conditions and the next time slot channel conditions.

[0117] The reason why this application enables the wireless central coordinator to send the fourth data frame to each terminal device in real time to inform them of the real-time uplink channel status is mainly to deal with the situation where the terminal device suddenly needs to go uplink due to an alarm.

[0118] It is understandable that the downlink of the wireless central coordinator will trigger the uplink of the terminal devices, which is predictable. For example, in a multi-channel gateway, when collecting data from a large number of water meters, a multicast-like method can be used to aggregate data and simultaneously call terminal devices with an equal number of channels. Assigning different channels to terminal devices during the call can avoid collisions and speed up the call process. However, terminal devices still have a certain degree of randomness in their reporting, such as alarm event reporting. For such unpredictable transmissions, this application addresses this by synchronizing the idle and occupied states of channels in real time. This allows terminal devices to use idle channels for uplinking when an alarm occurs, further avoiding potential collisions from sudden uplinks.

[0119] Correspondingly, in the terminal device, embodiments of this application provide a method for scheduling power grid data, including:

[0120] Step S21: After receiving the first data frame sent by the wireless central coordinator, determine whether there is a telemetry command or remote control command corresponding to the preset address based on the command content of each command frame in the first data frame.

[0121] Specifically, the device address is written in the instruction content of each instruction frame in the first data frame. After receiving the first data frame, the terminal device determines whether the device address in the instruction content of any instruction frame matches its own preset address. If so, the corresponding instruction frame is the instruction sent to itself, and then the corresponding operation is executed according to the instruction frame to generate the third data frame.

[0122] Step S22: If it exists, generate a third data frame based on telemetry or remote control commands.

[0123] The third data frame generated here is the response data frame mentioned above, in which the first message type information is 000 or 101.

[0124] Step S23: After receiving the second data frame from the wireless central coordinator, determine whether there is an uplink channel resource corresponding to the preset address based on the instruction content of each instruction frame in the second data frame.

[0125] Specifically, the second data frame has the same frame format and the same parsing method as the first data frame.

[0126] Step S24: If it exists, the third data frame is sent to the wireless central coordinator through the uplink channel resources.

[0127] Step S25: Upon receiving alarm data, generate a third data frame based on the alarm data.

[0128] The third data frame generated here is the aforementioned remote signaling data frame, in which the first message type information is 010.

[0129] Step S26: Determine the remote signaling channel resources based on the fourth data frame sent by the wireless central coordinator.

[0130] Specifically, the remote signaling channel resource can be determined by the channel whose bit value is equal to the second preset value in the fourth data frame. Since the alarm data is very urgent, the nearest time slot is usually used for transmission.

[0131] Step S27: The third data frame is sent to the wireless central coordinator via the remote signaling channel resource.

[0132] The above embodiments provide a method for scheduling power grid data. First, this application utilizes the mechanism that downlink in the power grid system inevitably triggers uplink data. After the wireless central coordinator sends a first data frame including remote control instructions or telemetry instructions, it allocates uplink channel resources to each terminal device according to the instructions in the first data frame. The allocated uplink channel resources are then placed into a second data frame and sent to the terminal device. This allows each terminal device to send the third data frame according to the uplink channel resources in the second data frame after generating a third data frame based on the remote control instructions in the first data frame. This avoids uplink collisions of the third data frame without handshake or modification of existing hardware.

[0133] In some embodiments, the scheduling method in the wireless central coordinator further includes:

[0134] Step S001: Receive downlink service data and extract the second message type information from the downlink service data.

[0135] The downlink service data is sent from the upstream device of the wireless central coordinator to the wireless central coordinator. The second message type information in the downlink service data is generally in the 7th byte, with a length of 3 bits.

[0136] Step S002: If the second message type information is a preset control parameter, then extract the control type information from the downlink service data. The preset control parameter can be equal to 100. When the second message type information is equal to 100, further extract the 7-bit control type information from the downlink service data to obtain the instruction content.

[0137] Step S003: If the control type information is a preset telemetry parameter, then generate a telemetry command based on the downlink service data and put it into the telemetry queue; otherwise, generate a remote control command based on the downlink service data and put it into the remote control queue.

[0138] Specifically, when the control type information is equal to 2, the corresponding downlink service data is to query sensor monitoring data, and therefore serves as a telemetry command; otherwise, the downlink service data may be a remote control command such as sensor reset setting.

[0139] In some embodiments, the above-mentioned response to a scheduling instruction, aggregating remote control instructions in the remote control queue or telemetry instructions in the telemetry queue according to the maximum data length in the scheduling instruction to obtain a first data frame and sending it to each terminal device, includes:

[0140] Step S111, Remote control judgment step: In response to the scheduling command, determine whether the remote control queue is empty.

[0141] Step S112: If not empty, determine whether the difference between the maximum data length and the length of the queue to be aggregated is greater than or equal to the length of the first remote control instruction in the remote control queue; if yes, put the remote control instruction into the queue to be aggregated and return to the remote control judgment step; if no, generate the first data frame based on the queue to be aggregated.

[0142] The maximum data length is the maximum capacity that can be placed in the first data frame required by the scheduling instruction.

[0143] Step S113: If empty, then execute the telemetry judgment step: determine whether the telemetry queue is empty.

[0144] Step S114: If not empty, determine whether the difference between the maximum data length and the length of the queue to be aggregated is greater than or equal to the length of the first telemetry instruction in the telemetry queue; if yes, put the telemetry instruction into the queue to be aggregated and return to the telemetry judgment step; if empty or no, generate the first data frame based on the queue to be aggregated.

[0145] Please see Figure 2 In this application, remote control commands have a higher priority than telemetry commands. Therefore, when constructing the first data frame, this application prioritizes extracting remote control commands from the remote control queue and placing them into the first data frame. If the remote control queue is empty and there are still empty slots in the first data frame to continue placing commands, then it checks whether there are any telemetry commands that need to be sent.

[0146] Specifically, please see Figure 3 , Figure 3 This is the format of the first data frame used in this application. The first data frame consists of a subframe, a MacCtrl, and N (N equals FrameCnt in MacCtrl) MacFrames.

[0147] Here, `subframe` represents the subframe number, used for subframe synchronization between the terminal and the base station. It is 1 byte long and cycles through values ​​from 0 to 255. `MacCtrl` contains control information. `MacFrame` represents the command frame, and the number of command frames is determined by `FrameCnt` in `MacCtrl`. The number of `MacFrame` values ​​corresponds to the number of aggregated remote control or telemetry commands.

[0148] Please see Figure 4 In the instruction frame, FrameType is the frame type information, which indicates the type of frame content, and its length is 4 bits.

[0149] FrameLen is a 4-bit frame length information, representing the byte length of FramePayload. Generally, when the message of a remote control command or telemetry command is no more than 15 bytes, the aggregation condition is met. However, for command messages larger than 15 bytes, this application needs to activate the reserved frame type, in which case the length of the corresponding frame length information is 1 to 2 bytes.

[0150] FramePayload is the instruction content, the specific content of which depends on FrameType.

[0151] Please see Figure 5 When FrameType=8, it indicates that the entire data frame is the second data frame, and the instruction content in each instruction frame is distributedUnicast, such as... Figure 5 The diagram shows the uplink channel resources allocated to each terminal device, including time-domain and frequency-domain resources. The instruction content is known to be between 0 and 15 bytes long, and each uplink channel resource requires 3 bytes to represent. Therefore, a maximum of 5 uplink channel resources can be written into one instruction frame; that is, the number of terminals that can communicate in one second data frame is greater than the number of terminals that can communicate in one first data frame.

[0152] like Figure 6 As shown, dispersedItem represents an uplink channel resource; devAddr is the logical address (terminal address) of the UE corresponding to this uplink channel resource; sched# is the retransmission count, initially 0, incremented by 1 for each retransmission; ttiOffset is the offset value between the timing of the allocated resource and the current downlink TTI, i.e., time domain information; freqBitIdx is the frequency information of the allocated resource.

[0153] In some embodiments, the aforementioned allocation of corresponding uplink channel resources for each remote control scheduling request and each telemetry scheduling request in the preset time slot after the first data frame is sent, and aggregation into a second data frame for transmission to each terminal device, includes:

[0154] Step S121: Set the scheduling identifier information of each remote control scheduling request to the first value and put it into the remote control scheduling queue.

[0155] Step S122: Set the scheduling identifier information of each telemetry scheduling request to the first value and put it into the telemetry scheduling queue.

[0156] Specifically, any scheduling request can only be cancelled after receiving a response from the terminal device or after the number of retransmissions reaches a preset retransmission threshold. Therefore, this application uses scheduling identification information to mark whether each scheduling request in the queue is in a state of pending channel resource allocation or a state of awaiting terminal feedback. If the scheduling identification information is a first value, it indicates that the scheduling request is in a state of pending channel resource allocation, where the first value can be 1 and the preset retransmission threshold can be equal to 4.

[0157] Step S123, execute the remote control scheduling judgment step: determine whether the remote control scheduling queue is empty.

[0158] Step S124: If not empty, then execute the uplink resource judgment step: determine whether the uplink resources are exhausted.

[0159] Step S125: If not exhausted, allocate uplink channel resources to the remote scheduling request whose first scheduling identifier information in the remote scheduling queue is the first value, change the scheduling identifier information to the second value, and return to the remote scheduling judgment step.

[0160] Specifically, the second value can be 0. When the scheduling identifier information is the second value, it means that the corresponding scheduling request has been allocated channel resources and needs to wait for terminal feedback. At this time, there is no need to schedule channel resources.

[0161] Step S126: If empty, execute the telemetry scheduling judgment step: determine whether the telemetry scheduling queue is empty.

[0162] Step S127: If not empty, then execute the uplink resource judgment step.

[0163] Step S128: If not exhausted, allocate uplink channel resources to the telemetry scheduling request whose first scheduling identifier information in the telemetry scheduling queue is the first value, change the scheduling identifier information to the second value, and return to the telemetry scheduling judgment step.

[0164] Step S129: If the uplink resources are empty or exhausted, generate a second data frame based on the allocated uplink channel resources.

[0165] Please see Figure 7 and Figure 8 In allocating uplink channel resources, this application also prioritizes the remote control scheduling request corresponding to the remote control command. If the scheduling request cannot be satisfied, it is transferred to the next time sequence without changing the scheduling priority. Within the same priority, the FIFO principle is used for resource scheduling and allocation.

[0166] Specifically, the wireless central coordinator in this application uses a single-channel broadcast for downlink, and downlink data is multiplexed in the time domain. An uplink channel is reserved for remote signaling reporting by terminal devices. Therefore, during uplink scheduling, each timing sequence of one channel cannot be allocated to meet the real-time requirements of alarms.

[0167] In some embodiments, the scheduling method executed by the terminal device further includes:

[0168] Step S301: Determine whether the uplink channel resources are sufficient to transmit the complete third data frame; if so, send the third data frame; if not, fragment the third data frame based on the uplink channel resources to obtain multiple third data frames.

[0169] Note that the third data frame here needs to be sent using the allocated uplink channel resources; it is a response data frame.

[0170] The third data frame includes verification status information, frame type information, control fields, frame length fields, service information length fields, and service information. FrameType is the frame type information, used to indicate the type of frame content, and has a length of 3 bits.

[0171] LenInd is the frame length field, FrameLen is the service information length field, used to indicate the byte length of the FramePayload. FrameCtrl is a control field used to indicate whether the service information FramePayload contains the corresponding control field.

[0172] The FUR (Frequency Update Request) instruction, located in the control field, indicates that the UE requests an update to the uplink transmission frequency point. When FUR is set to 1, the uplink frequency point on which the radio central coordinator successfully decodes the uplink data from the terminal device is the designated frequency point; when FUR is set to 0, there is no need to update the UE's uplink frequency point.

[0173] SR is also located in the control field, which is the rescheduling indication information. When set to 1, it indicates that the UE has data to send and requests the base station to schedule it; when set to 0, it indicates that the UE currently has no additional data to send. By default, when SR=0, the radio central coordinator immediately clears the uplink scheduling request of the terminal device.

[0174] Step S302: Set the rescheduling indication information of each third data frame except the last third data frame to a preset fragmentation value; specifically, in practical applications, the amount of data that the terminal device needs to feed back each time is not fixed, so there may be a situation where the uplink channel resources scheduled by the wireless central coordinator cannot completely transmit the third data frame.

[0175] Therefore, in the terminal device, this application sets up a rescheduling mechanism, that is, when the terminal device needs additional uplink channel resources, it will change the value of the rescheduling indication information to 1, so as to inform the wireless central coordinator that the terminal device still has additional data and still needs to schedule uplink resources to send. This mechanism can avoid the terminal device using inappropriate channel resources to send excessive data, thereby occupying other channel resources that may have been allocated, thus causing collisions.

[0176] Step S303: Send a third data frame to the wireless central coordinator through uplink channel resources.

[0177] Correspondingly, the scheduling method of the wireless central coordinator also includes:

[0178] Step S311: Extract the rescheduling indication information from the control field of the response data frame.

[0179] The response data frame here refers to the third data frame in response to remote control or telemetry commands.

[0180] Step S312: If the rescheduling instruction information is equal to the preset fragmentation value, then change the scheduling identifier information of the remote control scheduling request or telemetry scheduling request corresponding to the response data frame to the first value.

[0181] Specifically, in the wireless central coordinator, if the preset fragment value in the response data frame is 1, it means that the terminal device still needs to request uplink channel resources. It is worth noting that the redundant data of the terminal device and the response data frame of this uplink both belong to the same remote control command or telemetry command. Therefore, there is no need to adjust the type and priority of the corresponding scheduling request. The scheduling identifier information can be directly modified again to the first value indicating "to be allocated".

[0182] Step S313: Otherwise, delete the remote control scheduling request or telemetry scheduling request corresponding to the response data frame.

[0183] The rescheduling mechanism described in the above embodiments can prevent terminal devices from insisting on transmitting data in one go when there is excessive data, which would cause collisions with other devices uplink, and further improve the reliability of uplink data transmission.

[0184] In some embodiments, the scheduling method for the terminal device further includes:

[0185] Step S401: When the uplink time slot specified by the uplink channel resource arrives, determine whether the third data frame has been generated.

[0186] Note that the third data frame here needs to be sent using the allocated uplink channel resources; it is a response data frame.

[0187] In step S402, if not, an acknowledgment message is sent on the uplink channel resources; and after generating the third data frame, the third data frame is sent to compete with the fourth data frame for the uplink channel resources according to the uplink frequency point specified by the uplink channel resources.

[0188] Specifically, if the time domain resources in the uplink channel resources allocated by the wireless central coordinator are too advanced, or the data volume is too large, the time required for sorting, preparation, and combination is too long. This may cause the terminal device to be unable to sort the third data frame when the corresponding time slot arrives. In this case, the terminal device first sends an acknowledgment message to inform the wireless gateway coordinator that it has received the corresponding remote control command or telemetry command. Then, it competes for uplink channel resources according to the idle time slots and channels described in the fourth data frame, thereby enabling the transmission of the third data frame without conflicting with the uplink of other terminals.

[0189] Correspondingly, the scheduling methods in the wireless gateway coordinator also include:

[0190] Step S410: If the allocated uplink channel resources do not receive a third data frame or acknowledgment message, determine whether the number of retransmissions of the corresponding remote control scheduling request or telemetry scheduling request is less than the preset retransmission threshold. If yes, change the corresponding scheduling identifier information to the first value and increment the retransmission count by 1. If no, delete the corresponding remote control scheduling request or telemetry scheduling request.

[0191] The preset retransmission threshold can be equal to 4.

[0192] It is understandable that although terminal devices can compete for channel resources, the fourth data frame acquired by a terminal device only has a maximum of two time slots of channel availability, and the success rate of competition is not 100%. Therefore, except in cases where the terminal device does not receive remote control or telemetry commands, this application still allocates uplink channel resources to the terminal device after receiving the uplink confirmation message. If a suitable uplink channel resource can be allocated to the terminal device before it competes for resources, then for the terminal device, the uplink channel resource obtained using the second data frame is necessarily superior to the channel resource obtained through competition. After all, for each terminal device, there may also be cases where alarm data remote signaling is transmitted uplink, which cannot be predicted in advance by the wireless central coordinator. If the terminal device competes for uplink remote signaling data frames from other terminal devices during resource competition, it may seriously affect the real-time performance of alarm data. Since the fourth data frame is also generated by the wireless central coordinator, the fourth data frame and the allocated channel resources will not conflict with each other. Therefore, transmitting using the allocated uplink channel resources will absolutely not conflict with any possible remote signaling data frames.

[0193] In the aforementioned preset time slot after sending the first data frame, corresponding uplink channel resources are allocated to each remote control scheduling request and each telemetry scheduling request, and these are aggregated into a second data frame and sent to each terminal device, including:

[0194] Step S411: Perform the remote control scheduling judgment step.

[0195] Step S412: If the remote control scheduling queue is not empty, execute the uplink resource judgment step; if it is not exhausted, determine whether there is a remote control scheduling request in the remote control scheduling queue with a retransmission count not equal to 0 and a scheduling identifier information of the first value.

[0196] Step S413: If applicable, allocate uplink channel resources for remote scheduling request.

[0197] Step S414: If none, allocate uplink channel resources for the remote scheduling request whose first scheduling identifier information in the remote scheduling queue is the first value, change the scheduling identifier information to the second value, and return to the remote scheduling judgment step.

[0198] Step S415: If the remote control scheduling queue is empty, then execute the telemetry scheduling judgment step.

[0199] Step S416: If not empty, execute the uplink resource judgment step; if not exhausted, determine whether there is a telemetry scheduling request in the telemetry scheduling queue with a retransmission count not equal to 0 and a scheduling identifier information of the first value.

[0200] Step S417: If applicable, allocate uplink channel resources for the telemetry scheduling request.

[0201] Step S418: If none, allocate uplink channel resources to the telemetry scheduling request whose first scheduling identifier information in the telemetry scheduling queue is the first value, change the scheduling identifier information to the second value, and return to the telemetry scheduling judgment step.

[0202] In step S419, if the uplink resources are empty or exhausted, a second data frame is generated based on the allocated uplink channel resources.

[0203] Specifically, after adding a retransmission mechanism, the priority of the retransmission scheduling request is greater than the priority of the scheduling request for the initial transmission of the same type of instruction, i.e., retransmission of remote control > initial transmission of remote control > retransmission of telemetry > initial transmission of telemetry.

[0204] The above embodiments prioritize retransmission scheduling requests, which can maximize the probability that terminal devices that allocate uplink channel resources faster than those that send acknowledgment messages compete for resources, and further reduce the possibility of collisions.

[0205] In some embodiments, in the terminal device, the above-mentioned transmission of the third data frame by competing for uplink channel resources with the fourth data frame based on the uplink frequency point specified by the uplink channel resources includes:

[0206] Step S4021: Determine whether there is an uplink frequency point specified by uplink channel resources in the fourth data frame.

[0207] Step S4022: If available, send the third data frame using the uplink frequency point and the time slot resources obtained through contention.

[0208] In step S4023, if none is available, the third data frame is sent using the time slot and frequency resources obtained through competition. Before sending, the frequency update instruction in the control field of the third data frame is changed to the preset frequency update parameter.

[0209] Specifically, it can be understood that the frequency points of the uplink channel resources allocated by the wireless central coordinator are the camping frequency points of the corresponding terminal devices. Therefore, the camping frequency points are given priority in the competition. If the channel resources cannot be obtained by using the camping frequency points, other frequency points can be tried to compete. However, if the resources obtained by the competition are different from the camping frequency points, the frequency point update command needs to be changed to the preset frequency point update parameter, such as 1, in the third data frame to inform the wireless central coordinator to update the camping frequency points.

[0210] Correspondingly, in the wireless central coordinator, this scheduling method also includes:

[0211] Step S51: After sending the second data frame, the uplink frequency point of the uplink channel resources allocated to each terminal device in the second data frame is used as the camping frequency point of the corresponding terminal device.

[0212] Step S52: After receiving the response data frame, extract the frequency update instruction from the control field of the response data frame.

[0213] Step S53: If the frequency update instruction is equal to the preset frequency update parameter, then update the camping frequency of the corresponding terminal device according to the uplink frequency of the response data frame; otherwise, keep the camping frequency of the terminal device unchanged.

[0214] The steps by which the wireless central coordinator allocates uplink channel resources for a remote control scheduling request or a telemetry scheduling request include:

[0215] Step S61: Determine whether the number of requests in the remote control scheduling queue and the telemetry scheduling queue is equal to the number of channels minus 1.

[0216] Step S62, if yes, then execute the priority allocation step of the stationary frequency point: allocate uplink channel resources according to the stationary frequency point of the terminal device corresponding to the remote control scheduling request or telemetry scheduling request and the idle ordinary uplink resources.

[0217] It can be assumed that when allocating uplink channel resources, it is necessary to ensure that the frequency points in the resources are consistent with the station frequency points of the terminal devices. If this requirement cannot be met (i.e., not all scheduling requests can be allocated to station frequency point resources), then according to the priority of the scheduling requests, the station frequency point with higher priority is selected first, and other frequencies are randomly selected for the rest.

[0218] In the embodiments of this application, the amount of channel resources reserved can be adjusted by parameters. This application can set parameters by command, and by default, at least 33% of the channel resources are reserved as contestable uplink resources.

[0219] Step S63: If there are no stationary frequency points in the idle ordinary uplink resources, then uplink channel resources are randomly allocated according to preset principles; wherein, the preset principles include: the randomly allocated frequency points and each stationary frequency point are different.

[0220] Step S64: If not, determine whether the difference between the maximum and minimum number of terminals on each channel is less than or equal to the preset number of terminals. The preset number of terminals can be 3. Specifically, this determination is to determine whether the number of terminals on each channel is balanced. If not, the channel with the highest load (i.e., the most terminals) is removed before allocation to avoid being assigned to the channel with the most terminals, which would cause excessive channel load.

[0221] Step S65: If not, then remove the channel corresponding to the maximum number of resident terminals.

[0222] Step S66: If the channel is removed or eliminated, perform the priority allocation step for the stationary frequency point.

[0223] Step S67: If there are no camping frequency points in the idle ordinary uplink resources, then uplink channel resources that meet the preset principle are randomly allocated in order of increasing number of camping terminals in each channel.

[0224] Specifically, the scheduling method of the wireless central coordinator also includes:

[0225] Step S68: After randomly allocating uplink channel resources, the randomly allocated frequency points are used as the camping frequency points of the corresponding terminal devices, and it is determined whether the difference between the maximum number of camping terminals and the minimum number of camping terminals in each channel is less than or equal to the preset number of camping terminals; if so, uplink channel resources are randomly re-allocated according to the preset principle.

[0226] The channel resource allocation mechanism described in the above embodiments can ensure a more balanced number of terminal devices on each uplink channel, further reducing the possibility of uplink collisions between terminal devices.

[0227] In some embodiments, the scheduling method in the terminal device further includes:

[0228] Step S81: When competing for uplink channel resources, determine whether the number of bits equal to the second preset value in the current time slot channel condition or the next time slot channel condition of the fourth data frame is greater than the preset reserved channel number.

[0229] In step S82, if yes, then compete for normal uplink resources; if no, then make the third data frame wait for a preset time.

[0230] The preset duration can be randomly generated according to the CSMA / CA rule (BE=[2,4]).

[0231] Specifically, if the number of bits equal to the second preset value is greater than the preset number of reserved channels, it means that there are ordinary uplink resources available in the current time slot or the next time slot, other than the reserved uplink resources. In this case, ordinary uplink resources can be contested to avoid potential conflicts with alarm data from other terminal devices caused by contesting reserved uplink resources.

[0232] Step S83: If, in the fourth data frame received after a preset duration, the number of bits equal to the second preset value in both the current time slot channel condition and the next time slot channel condition is equal to the preset reserved channel number, then the third data frame is sent to compete for the reserved uplink resources. This application enables the terminal device to perform time-domain backoff when competing for resources if there are no ordinary uplink resources, thereby further increasing the probability of receiving uplink channel resources allocated by the wireless central coordinator.

[0233] The various embodiments described in this application can be independent solutions or combinations thereof based on their inherent logic, and all such solutions fall within the protection scope of this application. It is understood that the methods and operations implemented by the terminal device in the above method embodiments can also be implemented by components (e.g., chips or circuits) that can be used in the terminal device, and the methods and operations implemented by the wireless central coordinator can also be implemented by components (e.g., chips or circuits) that can be used in the wireless central coordinator.

[0234] In the embodiments provided above, the methods provided by the embodiments of this application have been described from the perspective of interaction between various devices. To implement the functions of the methods provided in the embodiments of this application, the terminal device and the wireless central coordinator may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0235] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) containing computer-usable program code.

[0236] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0237] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for scheduling power grid data, characterized in that, Applications in wireless central coordinators include: In response to a scheduling instruction, the remote control instructions in the remote control queue or the telemetry instructions in the telemetry queue are aggregated according to the maximum data length in the scheduling instruction to obtain a first data frame and send it to each terminal device. Generate remote control scheduling requests corresponding to each of the remote control commands and telemetry scheduling requests corresponding to each of the telemetry commands in the first data frame; in a preset time slot after sending the first data frame, allocate corresponding uplink channel resources for each of the remote control scheduling requests and each of the telemetry scheduling requests, and aggregate them into a second data frame and send it to each of the terminal devices; Receive the third data frame from the terminal device and extract the first message type information of the third data frame; If the first message type information is a preset response parameter, the third data frame is sent to the upper-level device as a response data frame; the corresponding remote control scheduling request or telemetry scheduling request is determined according to the uplink channel resources used by the response data frame, and the corresponding telemetry scheduling request or remote control scheduling request is deleted; if the first message type information is a preset alarm parameter, the third data frame is sent to the upper-level device as a remote signaling data frame.

2. The power grid data scheduling method according to claim 1, characterized in that, Also includes: Receive downlink service data and extract the second message type information from the downlink service data; If the second message type information is a preset control parameter, then the control type information in the downlink service data is extracted; If the control type information is a preset telemetry parameter, then a telemetry command is generated based on the downlink service data and placed in the telemetry queue; otherwise, a remote control command is generated based on the downlink service data and placed in the remote control queue.

3. The power grid data scheduling method according to claim 1, characterized in that, The step of responding to a scheduling instruction by aggregating remote control instructions in the remote control queue or telemetry instructions in the telemetry queue according to the maximum data length in the scheduling instruction to obtain a first data frame and sending it to each terminal device includes: Remote control determination step: In response to the scheduling instruction, determine whether the remote control queue is empty; If not empty, determine whether the difference between the maximum data length and the length of the queue to be aggregated is greater than or equal to the length of the first remote control instruction in the remote control queue; if yes, put the remote control instruction into the queue to be aggregated and return to the remote control determination step; if no, generate the first data frame based on the queue to be aggregated. If empty, then execute the telemetry judgment step: determine whether the telemetry queue is empty; If not empty, determine whether the difference between the maximum data length and the length of the queue to be aggregated is greater than or equal to the length of the first telemetry instruction in the telemetry queue; if yes, put the telemetry instruction into the queue to be aggregated and return to the telemetry determination step; if empty or no, generate the first data frame based on the queue to be aggregated.

4. The power grid data scheduling method according to claim 2, characterized in that, The step of allocating corresponding uplink channel resources for each of the remote control scheduling requests and each of the telemetry scheduling requests in a preset time slot after sending the first data frame, and aggregating them into a second data frame and sending it to each of the terminal devices, includes: Set the scheduling identifier information of each of the aforementioned remote scheduling requests to a first value and place them in the remote scheduling queue; Set the scheduling identifier information of each telemetry scheduling request to a first value and put it into the telemetry scheduling queue; Perform the remote control scheduling judgment step: Determine whether the remote control scheduling queue is empty; If not empty, then execute the uplink resource judgment step: determine whether the uplink resources are exhausted; if not exhausted, allocate the uplink channel resources to the first remote scheduling request in the remote scheduling queue whose scheduling identifier information is the first value, change the scheduling identifier information to the second value, and return to the remote scheduling judgment step; If empty, then execute the telemetry scheduling judgment step: determine whether the telemetry scheduling queue is empty; If not empty, then execute the uplink resource judgment step; if not exhausted, then allocate the uplink channel resource to the first telemetry scheduling request in the telemetry scheduling queue whose scheduling identifier information is the first value, change the scheduling identifier information to the second value, and return to the telemetry scheduling judgment step. If the uplink resources are empty or exhausted, the second data frame is generated based on the allocated uplink channel resources.

5. The power grid data scheduling method according to claim 4, characterized in that, Also includes: Generate a 1-byte channel information for the current time slot based on the normal uplink resources and reserved uplink resources of the current time slot; generate a 1-byte channel information for the next time slot based on the normal uplink resources and reserved uplink resources of the next time slot; Among them, the bit corresponding to the occupied channel in the normal uplink resources is the first preset value, and the bit corresponding to the idle channel in the normal uplink resources and each channel in the reserved uplink resources is the second preset value. The fourth data frame is generated based on the current time slot channel conditions and the next time slot channel conditions, and then sent to each terminal device.

6. The power grid data scheduling method according to claim 5, characterized in that, Also includes: Extract the rescheduling indication information from the control field of the response data frame; If the rescheduling indication information is equal to the preset fragmentation value, then the scheduling identifier information of the remote scheduling request or telemetry scheduling request corresponding to the response data frame is changed to the first value; otherwise, the remote scheduling request or telemetry scheduling request corresponding to the response data frame is deleted.

7. The power grid data scheduling method according to claim 6, characterized in that, Also includes: If the allocated uplink channel resources do not receive the third data frame or acknowledgment message, then determine whether the number of retransmissions of the corresponding remote control scheduling request or telemetry scheduling request is less than the preset retransmission threshold. If yes, then change the corresponding scheduling identifier information to the first value and increment the number of retransmissions by 1. If no, then delete the corresponding remote control scheduling request or telemetry scheduling request. The step of allocating corresponding uplink channel resources for each of the remote control scheduling requests and each of the telemetry scheduling requests in a preset time slot after sending the first data frame, and aggregating them into a second data frame and sending it to each of the terminal devices, includes: Perform the remote control scheduling judgment step; if the remote control scheduling queue is not empty, perform the uplink resource judgment step. If not exhausted, determine whether there is a remote scheduling request in the remote scheduling queue with a retransmission count not equal to 0 and a scheduling identifier information of the first value; if there is, allocate the uplink channel resource to the remote scheduling request; if not, allocate the uplink channel resource to the first remote scheduling request in the remote scheduling queue with a scheduling identifier information of the first value, change the scheduling identifier information to the second value, and return to the remote scheduling determination step; If the remote control scheduling queue is empty, then the telemetry scheduling judgment step is executed; If it is not empty, then execute the uplink resource judgment step described above; If not exhausted, determine whether there is a telemetry scheduling request in the telemetry scheduling queue with a retransmission count not equal to 0 and a scheduling identifier information of the first value; if there is, allocate the uplink channel resource to the telemetry scheduling request; if not, allocate the uplink channel resource to the first telemetry scheduling request in the telemetry scheduling queue with a scheduling identifier information of the first value, change the scheduling identifier information to the second value, and return to the telemetry scheduling judgment step; If the uplink resources are empty or exhausted, the second data frame is generated based on the allocated uplink channel resources.

8. The power grid data scheduling method according to claim 6, characterized in that, Also includes: After sending the second data frame, the uplink frequency point of the uplink channel resources allocated to each of the terminal devices in the second data frame is used as the camping frequency point of the corresponding terminal device. After receiving the response data frame, extract the frequency point update instruction from the control field of the response data frame; If the frequency update instruction is equal to the preset frequency update parameter, then the camping frequency of the corresponding terminal device is updated according to the uplink frequency of the response data frame. Otherwise, the stationary frequency of the terminal device remains unchanged; The steps of allocating the uplink channel resources for the remote control scheduling request or the telemetry scheduling request include: Determine whether the number of requests in the remote control scheduling queue and the telemetry scheduling queue is equal to the number of channels minus 1; If so, the priority allocation step of the stationary frequency point is executed: the uplink channel resources are allocated according to the stationary frequency point of the terminal device corresponding to the remote control scheduling request or the telemetry scheduling request and the idle ordinary uplink resources; if there is no stationary frequency point among the idle ordinary uplink resources, the uplink channel resources are randomly allocated according to the preset principle. If not, determine whether the difference between the maximum number of terminals and the minimum number of terminals in each channel is less than or equal to the preset number of terminals; if not, remove the channel corresponding to the maximum number of terminals; if yes or after removing the channel, execute the priority allocation step for the stationing frequency; if there is no stationing frequency in the idle ordinary uplink resources, randomly allocate the uplink channel resources that satisfy the preset principle in order of the number of terminals in each channel from least to most.

9. The power grid data scheduling method according to claim 8, characterized in that, The preset principles include: the randomly assigned frequency points and each of the dwelling frequency points are different; and also include: After randomly allocating the uplink channel resources, the randomly allocated frequency points are used as the camping frequency points of the corresponding terminal devices, and it is determined whether the difference between the maximum number of camping terminals and the minimum number of camping terminals in each channel is less than or equal to the preset number of camping terminals; if so, the uplink channel resources are randomly re-allocated according to the preset principle.

10. The method for scheduling power grid data according to claim 1, characterized in that, The first data frame includes a subframe number, control information, and multiple instruction frames; the subframe number is 1 byte long; the control information is between 1 and 11 bytes long; and the instruction frames are between 0 and 16 bytes long. The instruction frame includes frame type information, frame length information, and instruction content; the frame type information and the frame length information are both 4 bits in length, and the instruction content is between 0 and 15 bytes in length.

11. The method for scheduling power grid data according to claim 8, characterized in that, The preset response parameter is equal to 000 or 101; the preset alarm parameter is equal to 010; the preset control parameter is equal to 100; The preset telemetry parameter is equal to 2; The first preset value is 1, and the second preset value is 0; The preset segment value is equal to 1; the preset frequency update parameter is equal to 1.

12. A method for scheduling power grid data, characterized in that, Applied to terminal devices, including: After receiving the first data frame sent by the wireless central coordinator, determine whether there is a telemetry command or a remote control command corresponding to the preset address based on the command content of each command frame in the first data frame. If it exists, a third data frame is generated based on the telemetry command or the remote control command; After receiving the second data frame from the wireless central coordinator, determine whether the uplink channel resource corresponding to the preset address exists based on the instruction content of each instruction frame in the second data frame. If present, the third data frame is sent to the wireless central coordinator via the uplink channel resource; Upon receiving alarm data, a third data frame is generated based on the alarm data; The remote signaling channel resources are determined based on the fourth data frame sent by the wireless central coordinator; The third data frame is sent to the wireless central coordinator through the remote signaling channel resource.

13. The method for scheduling power grid data according to claim 12, characterized in that, Also includes: When the uplink time slot specified by the uplink channel resource arrives, determine whether the third data frame has been generated; If not, an acknowledgment message is sent on the uplink channel resources; Furthermore, after generating the third data frame, the third data frame is transmitted by competing with the fourth data frame for uplink channel resources according to the uplink frequency point specified by the uplink channel resources.

14. The power grid data scheduling method according to claim 13, characterized in that, The step of competing with the fourth data frame for uplink channel resources based on the uplink frequency point specified by the uplink channel resources to transmit the third data frame includes: Determine whether the fourth data frame contains the uplink frequency point specified by the uplink channel resource; If so, the third data frame is transmitted using the uplink frequency and the time slot resources obtained through contention. If not, the third data frame is sent using the time slot and frequency resources obtained through competition, and before sending, the frequency update instruction in the control field of the third data frame is changed to a preset frequency update parameter.

15. The method for scheduling power grid data according to claim 12, characterized in that, Also includes: Determine whether the uplink channel resources are sufficient to transmit the complete third data frame; If possible, then send the third data frame; If not, the third data frame is fragmented based on the uplink channel resources to obtain multiple third data frames; Set the rescheduling indication information of each third data frame except the last third data frame to the preset fragmentation value; The third data frame is transmitted to the wireless central coordinator via the uplink channel resources.

16. The power grid data scheduling method according to claim 14, characterized in that, Also includes: When competing for the uplink channel resources, it is determined whether the number of bits equal to the second preset value in the current time slot channel situation or the next time slot channel situation of the fourth data frame is greater than the preset reserved channel number. If yes, then compete for normal uplink resources; if not, then the third data frame waits for a preset time. If, in the fourth data frame received after a preset duration, the number of bits equal to the second preset value in both the current time slot channel condition and the next time slot channel condition is equal to the preset reserved channel number, then the third data frame is sent by competing for reserved uplink resources.

17. The method for scheduling power grid data according to claim 12, characterized in that, The third data frame includes verification status information, frame type information, control field, frame length field, service information length field, and service information.

18. A wireless central coordinator, characterized in that, It includes a module for performing the power grid data scheduling method as described in any one of claims 1 to 11.

19. A terminal device, characterized in that, It includes a module for performing the power grid data scheduling method as described in any one of claims 12 to 17.

20. A power grid data dispatching system, characterized in that, The device includes a wireless central coordinator that performs the power grid data scheduling method as claimed in any one of claims 1 to 11; and at least one terminal device disposed in the power grid that performs the power grid data scheduling method as claimed in any one of claims 12 to 17.

Images