WO2023226989A9 - 一种基于plc的节点调度方法、设备及plc系统 - Google Patents

一种基于plc的节点调度方法、设备及plc系统 Download PDF

Info

Publication number
WO2023226989A9
WO2023226989A9 PCT/CN2023/095839 CN2023095839W WO2023226989A9 WO 2023226989 A9 WO2023226989 A9 WO 2023226989A9 CN 2023095839 W CN2023095839 W CN 2023095839W WO 2023226989 A9 WO2023226989 A9 WO 2023226989A9
Authority
WO
WIPO (PCT)
Prior art keywords
sleep
group
node
nodes
information
Prior art date
Application number
PCT/CN2023/095839
Other languages
English (en)
French (fr)
Other versions
WO2023226989A1 (zh
Inventor
茆意伟
曹倩
郑博文
林学森
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023226989A1 publication Critical patent/WO2023226989A1/zh
Publication of WO2023226989A9 publication Critical patent/WO2023226989A9/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B3/00—Line transmission systems
    • H04B3/54—Systems for transmission via power distribution lines
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation

Definitions

  • the embodiments of the present application relate to the field of communication technology, and in particular to a node scheduling method, equipment and PLC system based on power line communication (PLC).
  • PLC power line communication
  • PLC power line communication
  • PLC technology refers to a communication technology that uses power lines as communication media to transmit signals through carrier waves. Because PLC technology can utilize existing power lines with extensive coverage as transmission media, it does not require the deployment of new lines and can greatly reduce initial deployment costs. In addition, PLC technology does not require separate line maintenance, thus greatly reducing later maintenance costs. In addition, PLC technology is not affected by factors in the surrounding environment (such as electromagnetic interference, etc.).
  • This application provides a PLC-based node scheduling method, equipment and PLC system, which can reduce the power consumption of each node in the power line communication system while ensuring the PLC communication business requirements.
  • a PLC-based node scheduling method is provided.
  • the method is applied in a PLC system.
  • the PLC system includes a first node (also called a master node) and a plurality of second nodes (also called end nodes), wherein the plurality of The second nodes respectively belong to a plurality of groups, the plurality of second nodes include a third node, and the third node is connected to the first node through a power line.
  • the method includes: the first node determines that the group where the third node is located is the first group; the first node obtains the group service information of the first group; the first node sends group dormancy scheduling information to the third node according to the group service information of the first group. .
  • the packet service information is used to represent one or more of the following: service priority, bandwidth, delay, and packet size of the service corresponding to the first packet.
  • the group sleep scheduling information includes the group sleep policy, and the group sleep scheduling information is used by the third node to trigger the corresponding sleep wake-up mechanism.
  • the first node may directly send the group dormancy scheduling information to the third node based on the packet service information of the first group.
  • the first node may directly determine the sleep scheduling policy of the first group based on the packet service information of the first group, and the sleep scheduling policy may at least be used to characterize the group sleep policy of the first group.
  • the first node may comprehensively consider the available resource information and the packet service information to send the group dormancy scheduling information to the third node.
  • the first node can comprehensively determine the sleep scheduling policy of the first group by combining the available resource information and the group service information.
  • the sleep scheduling policy can at least be used to characterize the group sleep policy of the first group.
  • the main node and the end node can use the widely deployed power lines as the transmission medium, reducing the early deployment cost and later maintenance cost, and avoiding the impact of surrounding environment (such as electromagnetic interference, etc.) factors on communication.
  • the master node can group multiple end nodes according to the business association, and according to the group business-related information (such as business priority, bandwidth, delay, packet size, etc., quality of service (QoS)) Reasonably determine the sleep scheduling strategy, so that each end node in the group can fully sleep while ensuring the PLC communication business needs, so as to reduce the power consumption of each end node.
  • business-related information such as business priority, bandwidth, delay, packet size, etc., quality of service (QoS)
  • the nodes in the first group have a business association relationship. That is, multiple members of the same group "wake up and sleep together.” Through this method, each end node in the group can be fully dormant while ensuring the PLC communication service requirements. In addition, since members in different groups are used for different services, the time slots can overlap with each other. This can also reduce packet loss caused by competition.
  • the business association relationship between the nodes in the first group includes one or more of the following: a control relationship and a synchronization relationship.
  • This application does not limit the specific relationship between multiple end nodes in the same group.
  • multiple end nodes may have a controlling and controlled relationship, synchronization (such as synchronization status, synchronized execution operations, synchronization settings, etc.) )relation.
  • synchronization such as synchronization status, synchronized execution operations, synchronization settings, etc.
  • the above-mentioned first node determines that the group where the third node is located is the first group, including: the first node obtains business association information used to characterize business association relationships between multiple second nodes; A node determines the group in which multiple second nodes are located based on the service association information of multiple second nodes, wherein the determined group in which multiple second nodes are located includes the first group in which the third node is located.
  • the master node groups the end nodes according to the business association information used to characterize the business association relationship between the end nodes, so that the end nodes with the business association relationship adopt the same sleep scheduling policy. This solution can ensure that when multiple members in the same group trigger the sleep wake-up mechanism according to the same sleep scheduling policy, "waking up and sleeping together" will not affect the end node's business.
  • the first node can obtain the business association information of multiple second nodes based on one or more of the following: user settings or operations, information reported by the second node, address association table ( address association table, ATT).
  • address association table address association table
  • This application does not limit the ways in which the master node obtains end node business related information.
  • the business association information of the end node can be determined by the main node based on the settings of the operation and maintenance personnel, or determined by the main node based on one or more of the user's operations, downloads, or settings, or the main node can be determined based on the information reported by the end node.
  • information such as business information, function information, status information, connection information, etc.
  • ATT such as node information with business association indicated in the local ATT (such as node physical address, etc.)).
  • the nodes in the first group do not interfere with each other.
  • each end node in the group can be fully dormant while ensuring the PLC communication service requirements.
  • nodes in the same group do not interfere with each other, it is possible to avoid collisions between end nodes that interfere with each other when sending packets, resulting in mutual collision and packet loss.
  • the above-mentioned first node determines that the group where the third node is located is the first group, including: the first node obtains node topology information used to characterize whether the plurality of second nodes interfere with each other; A node determines the first group based on the node topology information of the plurality of second nodes.
  • the master node groups the end nodes according to the node topology information used to characterize whether the end nodes interfere with each other, so that the end nodes that interfere with each other do not wake up at the same time, thereby avoiding the collision of the end nodes that interfere with each other when sending packets. Collision packet loss.
  • the above group sleep policy is L1 type sleep (such as L1 type sleep described in the International Telecommunication Union (ITU) G.9961 standard), and the group sleep scheduling information also includes the group sleep type and short sleep bitmap; among them, the group sleep type includes scheduling once or periodic scheduling until modified.
  • the master node may instruct the end nodes in the first group to perform L1 type sleep based on actual conditions (such as specific business requirements corresponding to the first group). In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep policy is L3 type long sleep (as described in the ITU G.9961 standard L3 type long sleep).
  • the master node may instruct the end nodes in the first group to perform L3 type long sleep according to the actual situation (such as the specific service requirements corresponding to the first group). This allows each end node in the group to fully sleep when there is no business, thereby reducing the power consumption of each end node.
  • the above group sleep policy is L2 type long sleep (such as L2 type long sleep described in the ITU G.9961 standard).
  • the group sleep scheduling information also includes group sleep type, group sleep start time and group sleep time. Sleep duration; among them, the group sleep type includes scheduling once or periodically until modification.
  • the master node can instruct the end nodes in the first group to perform L2 type long sleep according to the actual situation (such as the specific service requirements corresponding to the first group). In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep type is periodic scheduling until modification, and the group sleep scheduling information also includes a sleep period.
  • the master node can instruct the end nodes in the first group to perform periodic L2 type long sleep according to the actual situation (such as the specific service requirements corresponding to the first group). In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep type is periodic scheduling until modification, and the group sleep scheduling information also includes the group wake-up duration.
  • the master node can instruct the end nodes in the first group to perform periodic L2 type long sleep according to the actual situation (such as the specific service requirements corresponding to the first group). In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above-mentioned first node sends the group sleep schedule information to the third node according to the group service information, including: the first node sends the group sleep schedule to the third node based on the group service information and the currently available resource information. information.
  • This application does not limit the specific basis for the master node to decide the sleep scheduling strategy.
  • the master node can also perform a sleep scheduling strategy based on the group service information and other relevant information, such as currently available resource information, to ensure that the obtained sleep scheduling strategy is more rational.
  • the above-mentioned first node sends group dormancy scheduling information to the third node according to the packet service information, including: the first node broadcasts the group dormancy to multiple second nodes including the third node according to the packet service information. Scheduling information. By broadcasting group sleep scheduling information, the synchronization and timeliness of the end node's execution of the sleep scheduling policy can be ensured.
  • the above-mentioned first node obtains the group service information of the first group, including: the first node obtains the group service information of the first group in one or more of the following ways: from multiple second nodes Obtained from one or more locations and determined based on the power line deployment topology.
  • This application does not limit the specific way in which the master node obtains group service information.
  • the master node may determine the group service information based on the information reported by the end nodes, or determine the group service information based on the power line deployment topology (such as the perception between end nodes, the connection relationship between end nodes, etc.).
  • the third node and the first node are directly connected through a power line; or the third node is indirectly connected to the first node through a fourth node, and the third node and the fourth node are connected through a power line.
  • the fourth node is connected to the first node through a power line, and the fourth node belongs to the plurality of second nodes.
  • This application does not limit the topology between the end node and the master node within the same group.
  • the end node may be directly connected to the master node.
  • the end node may also be indirectly connected to the master node, such as by transferring communication data to the master node through one or more other end nodes.
  • the fourth node belongs to the first group.
  • this application does not limit whether the forwarding node and the above-mentioned end node are in the same group.
  • the forwarding node and the above-mentioned end node may be in one group. Based on this, the method provided by this application can be applied to PLC systems with various topologies.
  • the fourth node does not belong to the first group.
  • this application does not limit whether the forwarding node and the above-mentioned end node are in the same group.
  • the forwarding node and the above-mentioned end node may not be in the same group. Based on this, the method provided by this application can be applied to PLC systems with various topologies.
  • the power line distance between the fourth node and the first node is greater than the power line distance between the third node and the first node. Reliable data transmission can be ensured by relaying communication data through end nodes that are closer to the power line of the main node.
  • the third node also belongs to the second group, and the group sleep scheduling information corresponding to the second group does not conflict with the group sleep scheduling information corresponding to the first group.
  • the end node can enter the sleep state when the sleep scheduling information corresponding to multiple groups indicates that the end node can enter the sleep state. In other words, if the sleep scheduling information corresponding to any group in which an end node belongs indicates that the end node needs to be in the awake state, the end node cannot enter the sleep state. Through this method, the normal operation of business can be guaranteed.
  • a PLC-based node scheduling method is provided, which method is applied to a PLC system, where the PLC system includes a first node and a plurality of second nodes, the plurality of second nodes respectively belong to multiple groups, and the plurality of second nodes
  • the two nodes include a third node belonging to the first group, and the third node is connected to the first node through a power line.
  • the method includes: a third node receives group sleep scheduling information from the first node, the group sleep scheduling information includes a group sleep policy, and the group sleep scheduling information is used by the third node to trigger a corresponding sleep wake-up mechanism; the third node responds to the group sleep scheduling The information triggers the corresponding sleep wake-up mechanism synchronously with other nodes in the first group.
  • the main node and the end node can use the widely deployed power lines as the transmission medium, reducing the early deployment cost and later maintenance cost, and avoiding the impact of surrounding environment (such as electromagnetic interference, etc.) factors on communication.
  • the end node can "wake up and sleep together" on a group basis according to the group-based sleep scheduling policy instructed by the master node. Through this method, each end node in the group can be fully dormant while ensuring the PLC communication service requirements.
  • the nodes in the first group have a business association relationship. That is, multiple members of the same group "wake up and sleep together.” Through this method, each end node in the group can be fully dormant while ensuring the PLC communication service requirements. In addition, since members in different groups are used for different services, the time slots can overlap with each other. This can also reduce packet loss caused by competition.
  • the business association relationship between the nodes in the first group includes one or more of the following: a control relationship and a synchronization relationship.
  • This application does not limit the specific relationship between multiple end nodes in the same group.
  • multiple end nodes may have a controlling and controlled relationship, synchronization (such as synchronization status, synchronized execution operations, synchronization settings, etc.) )relation.
  • the nodes in the first group do not interfere with each other.
  • each end node in the group can be fully dormant while ensuring the PLC communication service requirements.
  • nodes in the same group do not interfere with each other, it is possible to avoid collisions between end nodes that interfere with each other when sending packets, resulting in mutual collision and packet loss.
  • the above group sleep policy is L1 type sleep
  • the group sleep scheduling information also includes a group sleep type and a short sleep bitmap
  • the group sleep type is scheduled once
  • the above third node is based on the group sleep scheduling information and Other nodes in the first group synchronously trigger the corresponding sleep wake-up mechanism, including: the third node wakes up at the moment corresponding to the next media access control (media access control, MAC) cycle wake-up time slice according to the short sleep bitmap, and wakes up after sleeping Sleep at the moment corresponding to the time slice.
  • the end node can perform an L1 type hibernation synchronously with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep policy is L1 type sleep
  • the group sleep scheduling information also includes a group sleep type and a short sleep bitmap
  • the group sleep type is periodic scheduling until modified
  • the above third node is scheduled according to the group sleep schedule
  • the information triggers the corresponding sleep wake-up mechanism synchronously with other nodes in the first group, including: the third node wakes up at the moment corresponding to the wake-up time slice of each subsequent MAC cycle according to the short sleep bitmap, and sleeps at the moment corresponding to the sleep time slice .
  • the end node can periodically perform L1 type hibernation in synchronization with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above-mentioned group sleep policy is L3 type long sleep
  • the above-mentioned third node synchronizes with other nodes in the first group to trigger the corresponding sleep wake-up mechanism according to the group sleep scheduling information, including: the third node according to The L3 type long sleep indicated by the group sleep policy enters the sleep state until it wakes up on its own or is woken up.
  • the end node can perform L3 type long sleep synchronously with other end nodes in the same group according to the instructions of the master node. This allows each end node in the group to fully sleep when there is no business, thereby reducing the power consumption of each end node.
  • the above group sleep policy is L2 type long sleep
  • the group sleep scheduling information also includes group sleep type, group sleep start time and group sleep duration, the group sleep type is scheduled once; the above third node is based on The group sleep scheduling information triggers the corresponding sleep wake-up mechanism synchronously with other nodes in the first group, including: the third node sleeps at the moment corresponding to the above-mentioned sleep start time, and wakes up after the above-mentioned group sleep duration is met.
  • the end node can perform an L2 type long sleep synchronously with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep policy is L2 type long sleep.
  • the group sleep scheduling information also includes group sleep type, group sleep start time, group sleep duration and sleep cycle.
  • the group sleep type is periodic scheduling until modified;
  • the above-mentioned third node synchronizes with other nodes in the first group to trigger the corresponding sleep wake-up mechanism according to the group sleep scheduling information, including: the third node enters the sleep state at the moment corresponding to the above-mentioned sleep start time, and wakes up after the above-mentioned group sleep duration is met.
  • the third node When the above sleep cycle is met, the third node enters the sleep state until it wakes up after the above group sleep duration is met; when the above sleep cycle is met again, the third node enters the sleep state again until it wakes up after the above group sleep duration is met. And so on.
  • the end node can periodically perform L2 type long sleep in synchronization with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep policy is L2 type long sleep.
  • the group sleep scheduling information also includes group sleep type, group sleep start time, group sleep duration, and group wakeup duration.
  • the group sleep type is periodic scheduling until modified.
  • the above-mentioned third node synchronizes with other nodes in the first group to trigger the corresponding sleep wake-up mechanism according to the group sleep scheduling information, including: the third node enters the sleep state at the moment corresponding to the above-mentioned sleep start time, until the above-mentioned group sleep duration is met Wake up; when the above-mentioned group wake-up time is met, the third node enters the sleep state until the above-mentioned group sleep time is met; when the above-mentioned group wake-up time is met again, the third node enters the sleep state again until the above-mentioned group sleep time is met.
  • the end node can periodically perform L2 type long sleep in synchronization with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the third node and the first node are directly connected through a power line; or the third node is indirectly connected to the first node through a fourth node, and the third node and the fourth node are connected through a power line.
  • the fourth node is connected to the first node through a power line, and the fourth node belongs to the plurality of second nodes.
  • This application does not limit the topology between the end node and the master node within the same group.
  • the end node may be directly connected to the master node.
  • the end node may also be indirectly connected to the master node, such as by relaying communication data to the master node through one or more other end nodes.
  • the fourth node belongs to the first group.
  • this application does not limit whether the forwarding node and the above-mentioned end node are in the same group.
  • the forwarding node and the above-mentioned end node may be in one group. Based on this, the method provided by this application can be applied to PLC systems with various topologies.
  • the fourth node does not belong to the first group.
  • this application does not limit whether the forwarding node and the above-mentioned end node are in the same group.
  • the forwarding node and the above-mentioned end node may not be in the same group. Based on this, the method provided by this application can be applied to PLC systems with various topologies.
  • the power line distance between the fourth node and the first node is greater than the power line distance between the third node and the first node. Reliable data transmission can be ensured by relaying communication data through end nodes that are closer to the power line of the main node.
  • the third node also belongs to the second group, and the group sleep scheduling information corresponding to the second group does not conflict with the group sleep scheduling information corresponding to the first group.
  • the end node can enter the sleep state when the sleep scheduling information corresponding to multiple groups indicates that the end node can enter the sleep state. In other words, if the sleep scheduling information corresponding to any group in which an end node belongs indicates that the end node needs to be in the awake state, the end node cannot enter the sleep state. Through this method, the normal operation of business can be guaranteed.
  • a communication node is provided.
  • the communication node is a main node.
  • the main node is connected to a plurality of second nodes (ie, end nodes) through power lines.
  • the plurality of second nodes include a third node.
  • the main node includes :
  • the processing unit is used to determine that the group where the third node is located is the first group; the information acquisition unit is used to obtain the group service information of the first group; the communication unit is used to transmit data to the third group through the power line according to the group service information of the first group.
  • the node sends group sleep scheduling information.
  • the packet service information is used to represent one or more of the following: service priority, bandwidth, delay, and packet size of the service corresponding to the first packet.
  • the group sleep scheduling information includes the group sleep policy, and the group sleep scheduling information is used by the third node to trigger the corresponding sleep wake-up mechanism.
  • the main node and the end node can use the widely deployed power lines as the transmission medium, reducing the early deployment cost and later maintenance cost, and avoiding the impact of surrounding environment (such as electromagnetic interference, etc.) factors on communication.
  • the master node can group multiple end nodes according to the business association and reasonably determine the sleep scheduling strategy based on the group business-related information (such as business priority, bandwidth, delay, packet size and other business QoS), so that it can While ensuring the PLC communication business needs, each end node in the group is allowed to fully sleep to reduce the power consumption of each end node.
  • the nodes in the first group have a business association relationship. That is, multiple members of the same group "wake up and sleep together.” Based on this, each end node in the group can be fully dormant while ensuring the PLC communication service requirements. In addition, since members in different groups are used for different services, the time slots can overlap with each other. This can also reduce packet loss caused by competition.
  • the business association relationship between the nodes in the first group includes one or more of the following: a control relationship and a synchronization relationship.
  • This application does not limit the specific relationship between multiple end nodes in the same group.
  • multiple end nodes may have a controlling and controlled relationship, synchronization (such as synchronization status, synchronized execution operations, synchronization settings, etc.) )relation.
  • synchronization such as synchronization status, synchronized execution operations, synchronization settings, etc.
  • the above-mentioned processing unit is further configured to: obtain business association information used to characterize the business association relationship between multiple second nodes; the above-mentioned processing unit determines that the group where the third node is located is the first group, The method includes: the processing unit determines the group in which the plurality of second nodes are located according to the obtained business association information of the plurality of second nodes, wherein the determined group in which the plurality of second nodes are located includes the first group in which the above-mentioned third node is located.
  • the master node groups the end nodes according to the business association information used to characterize the business association relationship between the end nodes, so that the end nodes with the business association relationship adopt the same sleep scheduling policy. This solution can ensure that when multiple members in the same group trigger the sleep wake-up mechanism according to the same sleep scheduling policy, "waking up and sleeping together" will not affect the end node's business.
  • the above-mentioned processing unit may obtain the service-related information of multiple second nodes based on one or more of the following: user settings or operations, information reported by the second node, and ATT.
  • This application does not limit the ways in which the master node obtains end node business related information.
  • the business association information of the end node can be determined by the main node based on the settings of the operation and maintenance personnel, or determined by the main node based on one or more of the user's operations, downloads, or settings, or the main node can be determined based on the information reported by the end node.
  • information such as business information, function information, status information, connection information, etc.
  • ATT such as node information with business association indicated in the local ATT (such as node physical address, etc.)).
  • the nodes in the first group do not interfere with each other. Based on this, each end node in the group can be fully dormant while ensuring the PLC communication service requirements. In addition, since nodes in the same group do not interfere with each other, it is possible to avoid collisions between end nodes that interfere with each other when sending packets, resulting in mutual collision and packet loss.
  • the above-mentioned processing unit is further configured to: obtain node topology information used to characterize whether the plurality of second nodes interfere with each other; the above-mentioned processing unit determines that the group where the third node is located is the first group, It includes: the processing unit determines the first group according to the node topology information of the plurality of second nodes.
  • the master node groups the end nodes according to the node topology information used to characterize whether the end nodes interfere with each other, so that the end nodes that interfere with each other do not wake up at the same time, thereby avoiding the collision of the end nodes that interfere with each other when sending packets. Collision packet loss.
  • the above group sleep policy is L1 type sleep
  • the group sleep scheduling information also includes a group sleep type and a short sleep bitmap; where the group sleep type includes scheduling once or periodic scheduling until modified.
  • the master node may instruct the end nodes in the first group to perform L1 type sleep based on actual conditions (such as specific business requirements corresponding to the first group). In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep policy is L3 type long sleep.
  • the master node may instruct the end nodes in the first group to perform L3 type long sleep according to the actual situation (such as the specific service requirements corresponding to the first group). This allows each end node in the group to fully sleep when there is no business, thereby reducing the power consumption of each end node.
  • the above group sleep policy is L2 type long sleep
  • the group sleep scheduling information also includes group sleep type, group sleep start time, and group sleep duration; where the group sleep type includes scheduling once or periodic scheduling until Revise.
  • the master node can instruct the end nodes in the first group to perform L2 type long sleep according to the actual situation (such as the specific service requirements corresponding to the first group). In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep type is periodic scheduling until modification, and the group sleep scheduling information also includes a sleep period.
  • the master node can instruct the end nodes in the first group to perform periodic L2 type long sleep according to the actual situation (such as the specific service requirements corresponding to the first group). In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep type is periodic scheduling until modification, and the group sleep scheduling information also includes the group wake-up duration.
  • the master node can instruct the end nodes in the first group to perform periodic L2 type long sleep according to the actual situation (such as the specific service requirements corresponding to the first group). In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the communication unit sending group sleep scheduling information to the third node based on the packet service information includes: the communication unit sending the group sleep scheduling information to the third node based on the group service information and currently available resource information.
  • This application does not limit the specific basis for the master node to decide the sleep scheduling strategy.
  • the master node can also perform a sleep scheduling strategy based on the group service information and other relevant information, such as currently available resource information, to ensure that the obtained sleep scheduling strategy is more rational.
  • the communication unit sending group sleep scheduling information to a third node based on the packet service information includes: the communication unit broadcasting the group sleep scheduling information to a plurality of second nodes including the third node based on the group service information. .
  • group sleep scheduling information By broadcasting group sleep scheduling information, the synchronization and timeliness of the end node's execution of the sleep scheduling policy can be ensured.
  • the above processing unit obtains the packet service information of the first group, including: the processing unit obtains the group service information of the first group in one or more of the following ways: from the plurality of second nodes. Obtained from one or more locations and determined based on the powerline deployment topology.
  • This application does not limit the specific way in which the master node obtains group service information.
  • the master node may determine the group service information based on the information reported by the end nodes, or determine the group service information based on the power line deployment topology (such as the perception between end nodes, the connection relationship between end nodes, etc.).
  • the third node and the main node are directly connected through a power line; or the third node is indirectly connected to the main node through a fourth node, and the third node and the fourth node are connected through a power line.
  • the node is connected to the main node through a power line, and the fourth node belongs to the plurality of second nodes mentioned above.
  • This application does not limit the topology between the end node and the master node within the same group.
  • the end node may be directly connected to the master node.
  • the end node may also be indirectly connected to the master node, such as by relaying communication data to the master node through one or more other end nodes.
  • the fourth node belongs to the first group.
  • this application does not limit whether the forwarding node and the above-mentioned end node are in the same group.
  • the forwarding node and the above-mentioned end node may be in one group. Based on this, the solution provided by this application can be applied to PLC systems with various topologies.
  • the fourth node does not belong to the first group.
  • this application does not limit whether the forwarding node and the above-mentioned end node are in the same group.
  • the forwarding node and the above-mentioned end node may not be in the same group. Based on this, the solution provided by this application can be applied to PLC systems with various topologies.
  • the power line distance between the fourth node and the main node is greater than the power line distance between the third node and the main node. Reliable data transmission can be ensured by relaying communication data through end nodes that are closer to the power line of the main node.
  • the third node also belongs to the second group, and the group sleep scheduling information corresponding to the second group does not conflict with the group sleep scheduling information corresponding to the first group.
  • the end node can enter the sleep state when the sleep scheduling information corresponding to multiple groups indicates that the end node can enter the sleep state. In other words, if the sleep scheduling information corresponding to any group in which an end node belongs indicates that the end node needs to be in the awake state, the end node cannot enter the sleep state. Based on this, the normal operation of business can be guaranteed.
  • a communication node is provided.
  • the communication node is an end node, such as a third node, and the end node is connected to a main node (such as a first node) through a power line.
  • the end node includes: a communication unit, used to receive group sleep scheduling information from the first node, the group sleep scheduling information includes a group sleep policy, and the group sleep scheduling information is used by the third node to trigger the corresponding sleep wake-up mechanism; a processing unit, Triggering the corresponding sleep wake-up mechanism synchronously with other nodes in the first group according to the group sleep scheduling information.
  • the main node and the end node can use the widely deployed power lines as the transmission medium, reducing the early deployment cost and later maintenance cost, and avoiding the impact of surrounding environment (such as electromagnetic interference, etc.) factors on communication.
  • the end node can "wake up and sleep together" on a group basis according to the group-based sleep scheduling policy instructed by the master node. Based on this, each end node in the group can be fully dormant while ensuring the PLC communication service requirements.
  • the nodes in the first group have a business association relationship. That is, multiple members of the same group "wake up and sleep together.” Based on this, each end node in the group can be fully dormant while ensuring the PLC communication service requirements. In addition, since members in different groups are used for different services, the time slots can overlap with each other. This can also reduce packet loss caused by competition.
  • the business association relationship between the nodes in the first group includes one or more of the following: a control relationship and a synchronization relationship.
  • This application does not limit the specific relationship between multiple end nodes in the same group.
  • multiple end nodes may have a controlling and controlled relationship, synchronization (such as synchronization status, synchronized execution operations, synchronization settings, etc.) )relation.
  • the nodes in the first group do not interfere with each other. Based on this, each end node in the group can be fully dormant while ensuring the PLC communication service requirements. In addition, since nodes in the same group do not interfere with each other, it is possible to avoid collisions between end nodes that interfere with each other when sending packets, resulting in mutual collision and packet loss.
  • the above group sleep policy is L1 type sleep
  • the group sleep scheduling information also includes a group sleep type and a short sleep bitmap
  • the group sleep type is scheduled once
  • the above processing unit compares the group sleep scheduling information with the first Other nodes in a group synchronously trigger the corresponding sleep wake-up mechanism, including: the processing unit wakes up at the time corresponding to the next MAC cycle wake-up time slice according to the short sleep bitmap, and sleeps at the time corresponding to the sleep time slice.
  • the end node can perform an L1 type hibernation synchronously with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above-mentioned group sleep policy is L1 type sleep
  • the group sleep scheduling information also includes a group sleep type and a short sleep bitmap
  • the group sleep type is periodic scheduling until modified
  • the above processing unit is based on the group sleep scheduling information
  • the corresponding sleep wake-up mechanism is triggered synchronously with other nodes in the first group, including: the processing unit wakes up at the time corresponding to the wake-up time slice of each subsequent MAC cycle according to the short sleep bitmap, and sleeps at the time corresponding to the sleep time slice.
  • the end node can periodically perform L1 type hibernation in synchronization with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above-mentioned group sleep policy is L3 type long sleep
  • the above-mentioned processing unit synchronizes with other nodes in the first group to trigger the corresponding sleep wake-up mechanism according to the group sleep scheduling information, including: the processing unit according to the group sleep
  • the L3 type long sleep indicated by the policy enters the sleep state until it wakes up on its own or is woken up.
  • the end node can perform L3 type long sleep synchronously with other end nodes in the same group according to the instructions of the master node. This allows each end node in the group to fully sleep when there is no business, thereby reducing the power consumption of each end node.
  • the above group sleep policy is L2 type long sleep
  • the group sleep scheduling information also includes group sleep type, group sleep start time and group sleep duration, the group sleep type is scheduled once; the above processing unit is based on the group sleep time.
  • the sleep scheduling information triggers the corresponding sleep wake-up mechanism synchronously with other nodes in the first group, including: the processing unit sleeps at the moment corresponding to the above-mentioned sleep start time, and wakes up after the above-mentioned group sleep duration is met.
  • the end node can perform an L2 type long sleep synchronously with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep policy is L2 type long sleep.
  • the group sleep scheduling information also includes group sleep type, group sleep start time, group sleep duration and sleep cycle.
  • the group sleep type is periodic scheduling until modified;
  • the above-mentioned processing unit triggers the corresponding sleep wake-up mechanism synchronously with other nodes in the first group according to the group sleep scheduling information, including: the processing unit enters the sleep state at the moment corresponding to the above-mentioned sleep start time, and wakes up after the above-mentioned group sleep duration is met; When the above sleep cycle is met, the third node enters the sleep state until it wakes up after the above group sleep duration is met; when the above sleep cycle is met again, the third node enters the sleep state again until it wakes up after the above group sleep duration is met, and so on.
  • the end node can periodically perform L2 type long sleep in synchronization with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep policy is L2 type long sleep.
  • the group sleep scheduling information also includes group sleep type, group sleep start time, group sleep duration, and group wakeup duration.
  • the group sleep type is periodic scheduling until modified. ;
  • the above-mentioned processing unit triggers the corresponding sleep wake-up mechanism synchronously with other nodes in the first group according to the group sleep scheduling information, including: the processing unit enters the sleep state at the moment corresponding to the above-mentioned sleep start time, and wakes up after the above-mentioned group sleep duration is met; When the above-mentioned group wake-up duration is met, the third node enters the sleep state until it wakes up after the above-mentioned group sleep duration is met; when the above-mentioned group wake-up duration is met again, the third node enters the sleep state again until it wakes up after the above-mentioned group sleep duration is met.
  • the end node can periodically perform L2 type long sleep in synchronization with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the third node and the first node are directly connected through a power line; or the third node is indirectly connected to the first node through a fourth node, and the third node and the fourth node are connected through a power line.
  • the fourth node is connected to the first node through a power line, and the fourth node is another end node connected to the main node through a power line.
  • the end node may be directly connected to the master node.
  • the end node may also be indirectly connected to the master node, such as by relaying communication data to the master node through one or more other end nodes.
  • the fourth node belongs to the first group.
  • this application does not limit whether the forwarding node and the above-mentioned end node are in the same group.
  • the forwarding node and the above-mentioned end node may be in one group. Based on this, the solution provided by this application can be applied to PLC systems with various topologies.
  • the fourth node does not belong to the first group.
  • this application does not limit whether the forwarding node and the above-mentioned end node are in the same group.
  • the forwarding node and the above-mentioned end node may not be in the same group. Based on this, the solution provided by this application can be applied to PLC systems with various topologies.
  • the power line distance between the fourth node and the first node is greater than the power line distance between the third node and the first node. Reliable data transmission can be ensured by relaying communication data through end nodes that are closer to the power line of the main node.
  • the third node also belongs to the second group, and the group sleep scheduling information corresponding to the second group does not conflict with the group sleep scheduling information corresponding to the first group.
  • the end node can enter the sleep state when the sleep scheduling information corresponding to multiple groups indicates that the end node can enter the sleep state. In other words, if the sleep scheduling information corresponding to any group in which an end node belongs indicates that the end node needs to be in the awake state, the end node cannot enter the sleep state. Based on this, the normal operation of business can be guaranteed.
  • a communication node is provided.
  • the communication node is a main node.
  • the main node is connected to a plurality of second nodes (ie, end nodes) through power lines.
  • the plurality of second nodes include a third node.
  • the main node includes : Processor, used to determine that the group where the third node is located is the first group, and obtain the group service information of the first group; communication module, used to send group dormancy scheduling information to the third node through the power line according to the group service information of the first group .
  • the packet service information is used to represent one or more of the following: service priority, bandwidth, delay, and packet size of the service corresponding to the first packet.
  • the group sleep scheduling information includes the group sleep policy, and the group sleep scheduling information is used by the third node to trigger the corresponding sleep wake-up mechanism.
  • the main node and the end node can use the widely deployed power lines as the transmission medium, reducing the early deployment cost and later maintenance cost, and avoiding the impact of surrounding environment (such as electromagnetic interference, etc.) factors on communication.
  • the master node can group multiple end nodes according to the business association and reasonably determine the sleep scheduling strategy based on the group business-related information (such as business priority, bandwidth, delay, packet size and other business QoS), so that it can While ensuring the PLC communication business needs, each end node in the group is allowed to fully sleep to reduce the power consumption of each end node.
  • the nodes in the first group have a business association relationship. That is, multiple members of the same group "wake up and sleep together.” Based on this, each end node in the group can be fully dormant while ensuring the PLC communication service requirements. In addition, since members in different groups are used for different services, the time slots can overlap with each other. This can also reduce packet loss caused by competition.
  • the business association relationship between the nodes in the first group includes one or more of the following: a control relationship and a synchronization relationship.
  • This application does not limit the specific relationship between multiple end nodes in the same group.
  • multiple end nodes may have a controlling and controlled relationship, synchronization (such as synchronization status, synchronized execution operations, synchronization settings, etc.) )relation.
  • synchronization such as synchronization status, synchronized execution operations, synchronization settings, etc.
  • the above-mentioned processor is further configured to: obtain business association information representing the business association relationship between multiple second nodes; the above-mentioned processor determines that the group where the third node is located is the first group, The method includes: the processor determines the group in which the plurality of second nodes are located according to the obtained business association information of the plurality of second nodes, wherein the determined group in which the plurality of second nodes are located includes the first group in which the third node is located.
  • the master node groups the end nodes according to the business association information used to characterize the business association relationship between the end nodes, so that the end nodes with the business association relationship adopt the same sleep scheduling policy. This solution can ensure that when multiple members in the same group trigger the sleep wake-up mechanism according to the same sleep scheduling policy, "waking up and sleeping together" will not affect the end node's business.
  • the above-mentioned processor can obtain the service-related information of multiple second nodes according to one or more of the following: user settings or operations, information reported by the second node, and ATT.
  • This application does not limit the ways in which the master node obtains end node business related information.
  • the business association information of the end node can be determined by the main node based on the settings of the operation and maintenance personnel, or determined by the main node based on one or more of the user's operations, downloads, or settings, or the main node can be determined based on the information reported by the end node.
  • information such as business information, function information, status information, connection information, etc.
  • ATT such as node information with business association indicated in the local ATT (such as node physical address, etc.)).
  • the nodes in the first group do not interfere with each other. Based on this, each end node in the group can be fully dormant while ensuring the PLC communication service requirements. In addition, since nodes in the same group do not interfere with each other, it is possible to avoid collisions between end nodes that interfere with each other when sending packets, resulting in mutual collision and packet loss.
  • the above-mentioned processor is further configured to: obtain node topology information used to characterize whether the plurality of second nodes interfere with each other; the above-mentioned processor determines that the group where the third node is located is the first group,
  • the method includes: a processor determining the first group according to the node topology information of the plurality of second nodes.
  • the master node groups the end nodes according to the node topology information used to characterize whether the end nodes interfere with each other, so that the end nodes that interfere with each other do not wake up at the same time, thereby avoiding the collision of the end nodes that interfere with each other when sending packets. Collision packet loss.
  • the above group sleep policy is L1 type sleep
  • the group sleep scheduling information also includes a group sleep type and a short sleep bitmap; where the group sleep type includes scheduling once or periodic scheduling until modified.
  • the master node may instruct the end nodes in the first group to perform L1 type sleep based on actual conditions (such as specific business requirements corresponding to the first group). In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep policy is L3 type long sleep.
  • the master node may instruct the end nodes in the first group to perform L3 type long sleep according to the actual situation (such as the specific service requirements corresponding to the first group). This allows each end node in the group to fully sleep when there is no business, thereby reducing the power consumption of each end node.
  • the above group sleep policy is L2 type long sleep
  • the group sleep scheduling information also includes group sleep type, group sleep start time, and group sleep duration; where the group sleep type includes scheduling once or periodic scheduling until Revise.
  • the master node can instruct the end nodes in the first group to perform L2 type long sleep according to the actual situation (such as the specific service requirements corresponding to the first group). In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep type is periodic scheduling until modification, and the group sleep scheduling information also includes a sleep period.
  • the master node can instruct the end nodes in the first group to perform periodic L2 type long sleep according to the actual situation (such as the specific service requirements corresponding to the first group). In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep type is periodic scheduling until modification, and the group sleep scheduling information also includes the group wake-up duration.
  • the master node can instruct the end nodes in the first group to perform periodic L2 type long sleep according to the actual situation (such as the specific service requirements corresponding to the first group). In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above communication module sends group sleep scheduling information to the third node according to the packet service information, including: the communication module sends the group sleep scheduling information to the third node based on the group service information and currently available resource information.
  • This application does not limit the specific basis for the master node to decide the sleep scheduling strategy.
  • the master node can also perform a sleep scheduling strategy based on the group service information and other relevant information, such as currently available resource information, to ensure that the obtained sleep scheduling strategy is more rational.
  • the above communication module sends the group sleep scheduling information to the third node according to the packet service information, including: the communication module broadcasts the group sleep schedule information to a plurality of second nodes including the third node according to the group service information. .
  • the communication module broadcasts the group sleep schedule information to a plurality of second nodes including the third node according to the group service information.
  • the above processor obtains the packet service information of the first group, including: the processor obtains the packet service information of the first group in one or more of the following ways: from the plurality of second nodes. Obtained from one or more locations and determined based on the powerline deployment topology.
  • This application does not limit the specific way in which the master node obtains group service information.
  • the master node may determine the group service information based on the information reported by the end nodes, or determine the group service information based on the power line deployment topology (such as the perception between end nodes, the connection relationship between end nodes, etc.).
  • the third node and the main node are directly connected through a power line; or the third node is indirectly connected to the main node through a fourth node, and the third node and the fourth node are connected through a power line.
  • the node is connected to the main node through a power line, and the fourth node belongs to the plurality of second nodes mentioned above.
  • This application does not limit the topology between the end node and the master node within the same group.
  • the end node may be directly connected to the master node.
  • the end node may also be indirectly connected to the master node, such as by relaying communication data to the master node through one or more other end nodes.
  • the fourth node belongs to the first group.
  • this application does not limit whether the forwarding node and the above-mentioned end node are in the same group.
  • the forwarding node and the above-mentioned end node may be in one group. Based on this, the solution provided by this application can be applied to PLC systems with various topologies.
  • the fourth node does not belong to the first group.
  • this application does not limit whether the forwarding node and the above-mentioned end node are in the same group.
  • the forwarding node and the above-mentioned end node may not be in the same group. Based on this, the solution provided by this application can be applied to PLC systems with various topologies.
  • the power line distance between the fourth node and the main node is greater than the power line distance between the third node and the main node. Reliable data transmission can be ensured by relaying communication data through end nodes that are closer to the power line of the main node.
  • the third node also belongs to the second group, and the group sleep scheduling information corresponding to the second group does not conflict with the group sleep scheduling information corresponding to the first group.
  • the end node can enter the sleep state when the sleep scheduling information corresponding to multiple groups indicates that the end node can enter the sleep state. In other words, if the sleep scheduling information corresponding to any group in which an end node belongs indicates that the end node needs to be in the awake state, the end node cannot enter the sleep state. Based on this, the normal operation of business can be guaranteed.
  • a communication node is provided.
  • the communication node is an end node, such as a third node, and the end node is connected to a main node (such as a first node) through a power line.
  • the end node includes: a communication module, used to receive group sleep scheduling information from the first node, the group sleep scheduling information includes a group sleep policy, and the group sleep scheduling information is used by the third node to trigger the corresponding sleep wake-up mechanism; a processor, Triggering the corresponding sleep wake-up mechanism synchronously with other nodes in the first group according to the group sleep scheduling information.
  • the main node and the end node can use the widely deployed power lines as the transmission medium, reducing the early deployment cost and later maintenance cost, and avoiding the impact of surrounding environment (such as electromagnetic interference, etc.) factors on communication.
  • the end node can "wake up and sleep together" on a group basis according to the group-based sleep scheduling policy instructed by the master node. Based on this, each end node in the group can be fully dormant while ensuring the PLC communication service requirements.
  • the nodes in the first group have a business association relationship. That is, multiple members of the same group "wake up and sleep together.” Based on this, each end node in the group can be fully dormant while ensuring the PLC communication service requirements. In addition, since members in different groups are used for different services, the time slots can overlap with each other. This can also reduce packet loss caused by competition.
  • the business association relationship between the nodes in the first group includes one or more of the following: a control relationship and a synchronization relationship.
  • This application does not limit the specific relationship between multiple end nodes in the same group.
  • multiple end nodes may have a controlling and controlled relationship, synchronization (such as synchronization status, synchronized execution operations, synchronization settings, etc.) )relation.
  • the nodes in the first group do not interfere with each other. Based on this, each end node in the group can be fully dormant while ensuring the PLC communication service requirements. In addition, since nodes in the same group do not interfere with each other, it is possible to avoid collisions between end nodes that interfere with each other when sending packets, resulting in mutual collision and packet loss.
  • the above-mentioned group sleep policy is L1 type sleep
  • the group sleep scheduling information also includes a group sleep type and a short sleep bitmap
  • the group sleep type is scheduled once;
  • the above processor matches the group sleep scheduling information with the first Other nodes in a group synchronously trigger the corresponding sleep wake-up mechanism, including: the processor wakes up at the time corresponding to the next MAC cycle wake-up time slice according to the short sleep bitmap, and sleeps at the time corresponding to the sleep time slice.
  • the end node can perform an L1 type hibernation synchronously with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above-mentioned group sleep policy is L1 type sleep
  • the group sleep scheduling information also includes a group sleep type and a short sleep bitmap
  • the group sleep type is periodic scheduling until modified
  • the above processor is based on the group sleep scheduling information
  • the corresponding sleep wake-up mechanism is triggered synchronously with other nodes in the first group, including: the processor wakes up at the time corresponding to the wake-up time slice of each subsequent MAC cycle according to the short sleep bitmap, and sleeps at the time corresponding to the sleep time slice.
  • the end node can periodically perform L1 type hibernation in synchronization with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above-mentioned group sleep policy is L3 type long sleep
  • the above-mentioned processor synchronizes with other nodes in the first group to trigger the corresponding sleep wake-up mechanism according to the group sleep scheduling information, including: the processor according to the group sleep
  • the L3 type long sleep indicated by the policy enters the sleep state until it wakes up on its own or is woken up.
  • the end node can perform L3 type long sleep synchronously with other end nodes in the same group according to the instructions of the master node. This allows each end node in the group to fully sleep when there is no business, thereby reducing the power consumption of each end node.
  • the above group sleep policy is L2 type long sleep.
  • the group sleep scheduling information also includes group sleep type, group sleep start time and group sleep duration.
  • the group sleep type is scheduled once; the above processor is based on the group sleep time.
  • the sleep scheduling information triggers the corresponding sleep wake-up mechanism synchronously with other nodes in the first group, including: the processor sleeps at the moment corresponding to the above-mentioned sleep start time, and wakes up after the above-mentioned group sleep duration is met.
  • the end node can perform an L2 type long sleep synchronously with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep policy is L2 type long sleep.
  • the group sleep scheduling information also includes group sleep type, group sleep start time, group sleep duration and sleep cycle.
  • the group sleep type is periodic scheduling until modified;
  • the above-mentioned processor triggers the corresponding sleep wake-up mechanism synchronously with other nodes in the first group according to the group sleep scheduling information, including: the processor enters the sleep state at the moment corresponding to the above-mentioned sleep start time, and wakes up after the above-mentioned group sleep duration is met; When the above sleep cycle is met, the third node enters the sleep state until it wakes up after the above group sleep duration is met; when the above sleep cycle is met again, the third node enters the sleep state again until it wakes up after the above group sleep duration is met, and so on.
  • the end node can periodically perform L2 type long sleep in synchronization with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the above group sleep policy is L2 type long sleep.
  • the group sleep scheduling information also includes group sleep type, group sleep start time, group sleep duration, and group wakeup duration.
  • the group sleep type is periodic scheduling until modified. ;
  • the above-mentioned processor triggers the corresponding sleep wake-up mechanism synchronously with other nodes in the first group according to the group sleep scheduling information, including: the processor enters the sleep state at the moment corresponding to the above-mentioned sleep start time, and wakes up after the above-mentioned group sleep duration is met; When the above-mentioned group wake-up duration is met, the third node enters the sleep state until it wakes up after the above-mentioned group sleep duration is met; when the above-mentioned group wake-up duration is met again, the third node enters the sleep state again until it wakes up after the above-mentioned group sleep duration is met.
  • the end node can periodically perform L2 type long sleep in synchronization with other end nodes in the same group according to the instructions of the master node. In this way, while ensuring the PLC communication service requirements, each end node in the group can be fully asleep to reduce the power consumption of each end node.
  • the third node and the first node are directly connected through a power line; or the third node is indirectly connected to the first node through a fourth node, and the third node and the fourth node are connected through a power line.
  • the fourth node is connected to the first node through a power line, and the fourth node is another end node connected to the main node through a power line.
  • the end node may be directly connected to the master node.
  • the end node may also be indirectly connected to the master node, such as by relaying communication data to the master node through one or more other end nodes.
  • the fourth node belongs to the first group.
  • this application does not limit whether the forwarding node and the above-mentioned end node are in the same group.
  • the forwarding node and the above-mentioned end node may be in one group. Based on this, the solution provided by this application can be applied to PLC systems with various topologies.
  • the fourth node does not belong to the first group.
  • this application does not limit whether the forwarding node and the above-mentioned end node are in the same group.
  • the forwarding node and the above-mentioned end node may not be in the same group. Based on this, the solution provided by this application can be applied to PLC systems with various topologies.
  • the power line distance between the fourth node and the first node is greater than the power line distance between the third node and the first node. Reliable data transmission can be ensured by relaying communication data through end nodes that are closer to the power line of the main node.
  • the third node also belongs to the second group, and the group sleep scheduling information corresponding to the second group does not conflict with the group sleep scheduling information corresponding to the first group.
  • the end node can enter the sleep state when the sleep scheduling information corresponding to multiple groups indicates that the end node can enter the sleep state. In other words, if the sleep scheduling information corresponding to any group in which an end node belongs indicates that the end node needs to be in the awake state, the end node cannot enter the sleep state. Based on this, the normal operation of business can be guaranteed.
  • a seventh aspect provides a PLC system, which includes a master node as in any possible implementation of the third aspect, and an end node as in any possible implementation of the fourth aspect.
  • An eighth aspect provides a PLC system, which includes a master node as in any possible implementation of the fifth aspect, and an end node as in any possible implementation of the sixth aspect.
  • a computer-readable storage medium is provided.
  • Computer-executable instructions are stored on the computer-readable storage medium.
  • any of the possible methods of the first aspect or the second aspect can be implemented. Methods in the implementation.
  • a chip system in a tenth aspect, includes a processor and a memory, and instructions are stored in the memory; when the instructions are executed by the processor, any one of the possibilities in the first aspect or the second aspect is realized. method in the implementation.
  • the chip system can be composed of chips or include chips and other discrete devices.
  • An eleventh aspect provides a computer program product that, when run on a computer, implements the method in any possible implementation manner of the first aspect or the second aspect.
  • Figure 1 is a schematic diagram of the topology of a power line communication system provided by an embodiment of the present application
  • Figure 2 is a schematic diagram of a PLC-based node scheduling process provided by an embodiment of the present application
  • Figure 3 is a schematic diagram of a PLC-based node scheduling time slot provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of another PLC-based node scheduling process provided by the embodiment of the present application.
  • FIG. 5 is a schematic diagram of another PLC-based node scheduling time slot provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of the hardware structure of a PLC node provided by an embodiment of the present application.
  • Figure 7 is a schematic structural diagram of a PLC network protocol stack provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of another PLC network protocol stack provided by the embodiment of the present application.
  • FIG. 9 is a flowchart 1 of the PLC-based node scheduling method provided by the embodiment of the present application.
  • Figure 10 is a grouping schematic diagram 1 provided by the embodiment of the present application.
  • Figure 11A is a grouping diagram 2 provided by an embodiment of the present application.
  • Figure 11B is a schematic diagram 1 of the relationship between end nodes provided by the embodiment of the present application.
  • Figure 11C is a schematic diagram 2 of the relationship between end nodes provided by the embodiment of the present application.
  • Figure 12 is a schematic diagram 3 of the end-node relationship provided by the embodiment of the present application.
  • Figure 13 is a grouping diagram 3 provided by the embodiment of the present application.
  • Figure 14 is a flow chart 2 of the PLC-based node scheduling method provided by the embodiment of the present application.
  • FIG. 15 is a flowchart three of the PLC-based node scheduling method provided by the embodiment of the present application.
  • FIG 16 is a flowchart 4 of the PLC-based node scheduling method provided by the embodiment of the present application.
  • Figure 17A is a schematic diagram of mutual interference between nodes provided by an embodiment of the present application.
  • Figure 17B is a grouping diagram 4 provided by the embodiment of the present application.
  • Figure 17C is a grouping diagram 5 provided by the embodiment of the present application.
  • FIG 18 is a flowchart 5 of the PLC-based node scheduling method provided by the embodiment of the present application.
  • first and second are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features. Therefore, features defined as “first” and “second” may explicitly or implicitly include one or more of these features. In the description of this embodiment, unless otherwise specified, “plurality” means two or more.
  • embodiments of the present application provide a node scheduling method based on power line communication (PLC), which can When the node is idle, the power consumption of each node is reduced by controlling the node to enter the sleep state without affecting the PLC communication business requirements.
  • PLC power line communication
  • the PLC-based node scheduling method provided by the embodiment of the present application can be applied in a power line communication system or scenario where power lines are laid out.
  • the power line communication system includes multiple communication nodes (also called PLC equipment, PLC nodes or PLC stations (STAs)).
  • the multiple communication nodes may include one or more master nodes (domain master, DM) and one or more end nodes (end point, EP). Communication between the master node (DM) and the end node (EP) is through power lines.
  • a master node (DM) can be connected to one or more end nodes (EP) through power lines.
  • An end node (EP) can also be connected to one or more other end nodes (EP) through power lines.
  • the master node (DM) is mainly responsible for network management and air interface resource allocation of the entire power line communication system.
  • the master node (DM) can be used to be responsible for network access decisions of end nodes (EP), bandwidth application decisions of end nodes (EP), traffic application decisions of end nodes (EP), heartbeat management, routing and topology Management, end node (EP) time slot resource allocation, sleep management, application layer message aggregation and distribution scheduling, network maintenance, etc.
  • the master node can be a gateway.
  • the end node has a sleep function.
  • the end node supports switching from the working mode to the sleep mode, or from the sleep mode to the working mode; for another example, the end node supports switching from the working state (also called the wake-up state) to the sleep state, or from the sleep state to the working state. .
  • the working state also called the wake-up state
  • a node can serve as both an end node and a master node.
  • a node can have both EP and DM functions.
  • the DM function of the node is enabled.
  • the PLC-based node scheduling method provided by the embodiments of this application can be applied to, but is not limited to, narrowband PLC technology, mid-band PLC technology, and broadband PLC technology.
  • narrowband PLC technology is often used in scenarios such as medium and low-voltage distribution network automation and electric meter reading with low-speed connections.
  • Mid-band PLC technology is often used in high-reliability and real-time control IoT scenarios, such as smart meters, smart traffic light control, smart street lights, etc.
  • Broadband PLC technology is often used in home broadband access, interconnection and other scenarios.
  • power line communication systems may include, but are not limited to, smart home systems, remote meter reading systems, urban lighting systems, smart community systems, parking lot management systems, security and anti-theft systems, fire alarm systems and other systems with power lines laid out.
  • nodes in smart home systems such as gateways, light drivers, lights, switch panels, temperature control panels, sensors (such as touch sensors, temperature sensors, proximity light sensors, pressure sensors, magnetic sensors, air pressure sensors, distance sensors , fingerprint sensor, ambient light sensor, smoke sensor, etc.), fresh air device, electric curtains, etc.
  • the nodes in the remote meter reading system include electricity meters, water meters, gas meters, data collectors, meter reading servers, etc.
  • Nodes in the urban lighting system include road lighting devices, landscape lighting devices, emergency lighting devices, lighting control devices, etc.
  • the nodes in the smart community system include access control devices, doors, elevators, monitoring, lights, water stations, parking lot gates, automatic sprinkler equipment, central control centers, etc.
  • the nodes in the parking lot management system include consoles, parking lot turnstiles, etc.
  • the nodes in the security and anti-theft system include front-end detectors, alarms, alarm controllers, etc.
  • Nodes in the fire alarm system include smoke sensors, smoke alarms, fire control centers, gateways, etc.
  • FIG. 1 shows a schematic topological structure diagram of a power line communication system provided by an embodiment of the present application.
  • the power line communication system includes a main node, end node 1, end node 2, end node 3 and end node 4. Among them, power lines are deployed between the main node and end node 1, end node 2, end node 3 and end node 4, and power lines are also deployed between each end node and the main node and other end nodes.
  • the master node in order to reduce the power consumption of each node without affecting the PLC business requirements, can send sleep scheduling information to the end node according to the request of the end node to instruct the end node to adjust the power consumption of each node according to the received request.
  • Schedule information to sleep or wake up.
  • the above-mentioned sleep scheduling information carries information for specifying the end node's sleep time (ie, sleep start time) and wake-up time (ie, wake-up start time, also called wake-up time).
  • the end node can enter the sleep state at the specified sleep time according to the sleep scheduling information, and enter the working state at the specified wake-up time.
  • node scheduling can be performed based on the following scheme 1 or scheme 2, so as to reduce the power consumption of each node without affecting the PLC business requirements.
  • the master node can instruct the end node to enter the short sleep state according to the received scheduling information by sending scheduling information to the end node according to the request of the end node.
  • nodes in the short sleep state can be in the sleep state in some time slots of a media access control (media access control, MAC) cycle, and in the working state in other time slots.
  • media access control media access control, MAC
  • Figure 2 shows a schematic diagram of a PLC-based node scheduling process provided by an embodiment of the present application.
  • the end node sends an enter short sleep request to the master node to request to enter the short sleep state (as described in the International Telecommunication Union (ITU) G.9961 standard according to the short sleep bitmap in each L1 type sleep state that sleeps and wakes up during the MAC cycle).
  • the master node After receiving the request to enter short sleep from the end node, the master node sends a short sleep confirmation message to the end node.
  • ITU International Telecommunication Union
  • the short sleep confirmation message sent by the master node to the end node can be used to agree to the end node's request to enter the short sleep state. Further, the end node sleeps or wakes up according to the message that the master node agrees to the short sleep request.
  • the short sleep confirmation message carries the reason why the master node agrees to the short sleep request.
  • the master node agrees to the short sleep request of the end node, but requires the end node to sleep or wake up according to the sleep schedule information specified by the master node.
  • the short sleep confirmation message sent by the master node to the end node also carries the corresponding reason code.
  • the master node can also broadcast the sleep scheduling information to the end nodes in the form of broadcast.
  • the sleep scheduling information carries information for specifying the sleep time and wake-up time of the end node.
  • the end node can enter the sleep state according to the sleep time specified by the sleep scheduling information, and enter the working state at the specified wake-up time.
  • the master node can carry the above sleep schedule information through the auxiliary information field (such as the short sleep schedule field or the default sleep schedule field) of the medium access plan (MAP) frame.
  • MAP medium access plan
  • the master node After receiving the short sleep request from the end node, if the master node evaluates that the end node entering the short sleep state will have an impact on the current network topology and business, the master node sends the short sleep request to the end node.
  • the acknowledgment message can be used to reject a short sleep request from an end node.
  • the short sleep confirmation message carries the reason why the master node rejected the short sleep request.
  • the reasons why the master node rejects the short sleep request of the end node may include, but are not limited to, the sleep time is too short, the schedule has no solution, or the request is rejected without reason, etc.
  • the short sleep request sent by the end node to the master node shown in Figure 2 may include, but is not limited to, a short sleep type and a short sleep bitmap.
  • the short sleep type is used to indicate but is not limited to whether the short sleep type initiated by the current end node is periodic, aperiodic or canceling the sleep schedule.
  • the short sleep bitmap is used to characterize, but is not limited to, the time slots in which an end node wishes to wake up and sleep within a MAC cycle.
  • the message entering the short sleep request may also include reserved fields.
  • a MAC cycle can be divided into 16 time slices (ie, 16 shares).
  • a short sleep bitmap such as 0001 0000 0000 0000 means waking up in the time period corresponding to the fourth time slice and sleeping in the time period corresponding to other time slices.
  • the message frame format of the short sleep request sent by the end node to the master node shown in Figure 2 can be as shown in Table 1 below:
  • the short sleep confirmation message sent by the master node to the end node shown in Figure 2 may include but is not limited to a reason code for agreeing/rejecting the short sleep request.
  • the reason code for agreeing/rejecting a short sleep request is 0b0000 (rejection without reason), 0b0001 (rejection due to too long sleep time), 0b0010 (rejection due to short sleep time), 0b0011 (rejection due to scheduling failure).
  • the short sleep confirmation message may also include reserved fields.
  • the message frame format of the short sleep confirmation message sent by the master node to the end node shown in Figure 2 can be as shown in the following Table 2:
  • the short sleep scheduling field of the MAP frame described in the embodiment of the present application may include short sleep scheduling information for each end node in the power line communication system.
  • the short sleep scheduling information may include but is not limited to the identification of the short sleep end node. (identification, ID), short sleep end node sleep type and short sleep end node bitmap, etc.
  • the default sleep schedule field of the MAP frame may include sleep schedule information for each end node in the power line communication system, including short sleep schedule information and long sleep schedule information.
  • the short sleep schedule information may include but is not limited to the default short sleep schedule. Instructions etc.
  • the short sleep schedule field format described in the embodiment of this application may be as shown in Table 3 below, and the default sleep schedule field format may be as shown in Table 4 below.
  • M is the number of end nodes that are about to enter the short sleep state in the power line communication system (M is a positive integer, M>1).
  • M is a positive integer, M>1).
  • the end node determines the sleep wake-up time slot based on the short sleep scheduling field.
  • i is the number of end nodes that are about to leave L3 type long sleep in the power line communication system (i is a positive integer, i>1).
  • the sleep start MAC cycle, default sleep duration and default wake-up duration shown in Table 4 above are for L2 type long sleep nodes that periodically enter the sleep state as described in the ITU G.9961 standard.
  • the number of end nodes required to be awakened, the first end node ID,..., and the i-th end node ID shown in Table 4 above are for the L3 type that remains dormant until it wakes up on its own or is awakened as described in the ITU G.9961 standard Long-sleeping nodes.
  • the end node determines the sleep wake-up time slot based on the default sleep schedule field.
  • the master node can send scheduling information to the end node according to the request of the end node to instruct the end node to enter the long sleep state according to the received scheduling information.
  • the node in the long sleep state can sleep across the MAC cycle. That is to say, the sleep state of the node in the long sleep state can span the MAC cycle, for example, starting from a certain time slot of one MAC cycle and continuing to the next MAC cycle. a certain time slot.
  • FIG. 4 shows a schematic diagram of another PLC-based node scheduling process provided by an embodiment of the present application.
  • the end node sends a long sleep request to the master node to request to enter a long sleep state (such as the L2 type sleep state or the L3 type sleep state described in the ITU G.9961 standard).
  • a long sleep state such as the L2 type sleep state or the L3 type sleep state described in the ITU G.9961 standard.
  • the master node After receiving the request to enter long sleep from the end node, the master node sends a long sleep confirmation message to the end node.
  • the long sleep confirmation message sent by the master node to the end node can be used to agree to the end node's request to enter the long sleep state. Further, the end node sleeps or wakes up according to the message that the master node agrees to the long sleep request.
  • the long sleep confirmation message carries the reason why the master node agreed to the long sleep request.
  • the master node agrees to the long sleep request of the end node, but requires the end node to sleep or wake up according to the sleep schedule information specified by the master node.
  • the long sleep confirmation message sent by the master node to the end node also carries the corresponding reason code.
  • the master node can also broadcast sleep scheduling information, including long sleep scheduling information, to the end nodes in the form of broadcast.
  • the sleep scheduling information carries information for specifying the sleep time and wake-up time of the end node.
  • the end node can enter the sleep state according to the sleep time specified by the sleep scheduling information, and enter the working state at the specified wake-up time.
  • the master node can carry the above sleep scheduling information, such as the long sleep scheduling information, through the auxiliary information field of the MAP frame (such as the long sleep scheduling field or the default sleep scheduling field).
  • the master node After receiving the long sleep request from the end node, if the master node evaluates that the end node entering the long sleep state will have an impact on the current network topology and business, the master node sends the long sleep request to the end node.
  • the acknowledgment message can be used to reject the end node's long sleep request message.
  • the long sleep confirmation message carries the reason why the master node rejected the long sleep request.
  • the reasons why the master node rejects the long sleep request of the end node may include, but are not limited to, the sleep time is too short, the schedule has no solution, or the request is rejected without reason, etc.
  • the request to enter the long sleep sent by the end node to the master node shown in Figure 4 may include, but is not limited to, the long sleep type, the long sleep mode sleep duration, and the long sleep mode wake up duration.
  • the long sleep type is used to indicate but is not limited to whether the long sleep type initiated by the current end node is periodic, aperiodic or canceling the sleep schedule.
  • the long sleep mode sleep duration is used to characterize the length of time the end node sleeps in a sleep cycle.
  • the long sleep mode sleep duration is usually set based on 1/16 of the MAC cycle.
  • the long sleep mode sleep duration is 0xFFFF, it means that the sleep duration is not limited.
  • the long sleep mode is the L3 type of sleep state in the ITU G.9961 standard.
  • the long sleep mode wake-up duration is used to represent the duration of the node wake-up immediately after the sleep time point.
  • the long sleep mode wake-up duration is usually set based on 1/16 of the MAC cycle.
  • the long sleep mode wake-up time can be greater than or equal to one MAC cycle.
  • the long sleep mode wake-up duration can also be 0.
  • the message for entering long sleep request may also include reserved fields.
  • the message frame format of the long sleep request sent by the end node to the master node shown in Figure 4 can be as shown in Table 5 below:
  • the long sleep confirmation message sent by the master node to the end node shown in Figure 4 may include but is not limited to the reason code for agreeing/rejecting the long sleep request.
  • the reason code for agreeing/rejecting a long sleep request is 0b0000 (rejection without reason), 0b0001 (rejection due to too long sleep time), 0b0010 (rejection due to short sleep time), 0b0011 (rejection due to scheduling failure).
  • the long sleep confirmation message may also include reserved fields.
  • the message frame format of the long sleep confirmation message sent by the master node to the end node shown in Figure 4 can be as shown in the following Table 6:
  • the long sleep scheduling field of the MAP frame described in the embodiment of the present application may include long sleep scheduling information for each end node in the power line communication system.
  • the long sleep scheduling information may include but is not limited to long sleep end node ID, The sleep type of the long-sleep end node, the sleep duration of the long-sleep end node, and the wake-up duration of the long-sleep end node.
  • the long sleep scheduling field format described in the embodiment of this application may be as shown in Table 7 below.
  • N is the number of end nodes that are about to enter the long sleep state in the power line communication system (N is a positive integer, N>1). It should be noted that if the sleep duration of a long-sleep node is 0xFFFF, it represents unlimited sleep, such as L3 type sleep described in the ITU G.9961 standard.
  • the format of the default sleep schedule field carrying the long sleep schedule information described in the embodiment of this application may be as shown in Table 4 above.
  • the sleep start MAC cycle, default sleep duration and default wake-up duration shown in Table 4 are for L2 type long sleep nodes.
  • the number of end nodes required to be awakened, the first end node ID, ..., and the i-th end node ID shown in Table 4 above are for L3 type long-sleeping nodes.
  • the end node can directly send a request to enter L3 long sleep to the master node (for example, the long sleep mode sleep duration 0xFFFF is carried in the request to enter long sleep). , to request to enter the L3 long sleep state.
  • the master node evaluates that the end node entering the L3 long sleep state will have no impact on the current network topology and services, the master node sends an L3 long sleep confirmation message to the end node. Agree to the end node's request to enter L3 long sleep. Further, the end node enters the L3 sleep state according to the message that the master node agrees to the L3 long sleep request, until it wakes up on its own or is woken up.
  • the end node self-awakening means that the end node in the L3 dormant state can wake up by itself and enter the working state when there is a business need.
  • the end node being awakened means that the end node in the L3 sleep state can accept the awakening of other nodes through the wake-up field of the auxiliary information field of the MAP frame and enter the working state.
  • other end nodes can request to wake up one or more end nodes in the L3 sleep state by sending a wakeup request to the master node.
  • the wake-up request includes the number and end-node ID of the end nodes required to be woken up.
  • the message frame format of the wake-up request can be as shown in Table 8 below:
  • multiple end nodes do not need to sleep and wake up synchronously in each cycle, but they still need to sleep and wake up synchronously.
  • multiple end nodes entering the L2 long sleep state need to have at least one identical wake-up time slice within the maximum MAC sleep period.
  • multiple end nodes entering the L3 long sleep state need to synchronize MAP frames with the master node and successfully parse the MAP frame at least once within 4 MAC sleep cycles.
  • the sleep period of end node A and end node D is 2 MAC cycles
  • the sleep period of end node B is 4 MAC cycles
  • the sleep period of end node C is 8 MAC cycles. Since the sleep periods of end node A, end node B, end node C and end node D are integer multiples, it is guaranteed that end node A, end node B, end node C and end node D have at least one same wake-up time slice ( As shown in Figure 5, wake-up time slice A and wake-up time slice B).
  • the embodiment of the present application also provides a PLC-based node scheduling based on the grouping situation. method.
  • the master node can group multiple end nodes according to the business association of the end nodes and/or the perception situation between the end nodes, etc., and multiple end nodes in the same group can share time slot.
  • multiple end nodes within the same group have business relationships.
  • FIG. 6 shows a schematic diagram of the hardware structure of a PLC node provided by an embodiment of the present application.
  • a PLC node may include a processor 601 , a communication module 602 , a memory 603 , a sensor 604 and a power supply module 605 .
  • the sensor 604 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, etc.
  • the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the PLC node.
  • the PLC node may include more or less components than shown in the figure, or combine some components, or split some components, or arrange different components.
  • the components illustrated may be implemented in hardware, software, or a combination of software and hardware.
  • Processor 601 may include one or more processing units.
  • the processor 601 may include an application processor (application processor, AP), modem processor, graphics processing unit (GPU), image signal processor (image signal processor, ISP), flight controller, Video codec, digital signal processor (DSP) and/or neural-network processing unit (NPU), etc.
  • application processor application processor, AP
  • modem processor graphics processing unit
  • GPU graphics processing unit
  • image signal processor image signal processor
  • ISP image signal processor
  • flight controller flight controller
  • Video codec digital signal processor
  • DSP digital signal processor
  • NPU neural-network processing unit
  • different processing units can be independent devices or integrated in one or more processors.
  • the processor 601 may also be provided with a memory for storing instructions and data.
  • the memory in processor 601 is cache memory. This memory can hold instructions or data that have just been used by processor 601 or are used repeatedly. If the processor 601 needs to use the instruction or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 601 is reduced, thus improving the efficiency of the system.
  • the processor 601 can be used to cooperate with the sensor 604 to collect sensor data (such as touch sensor data, pressure sensor data, etc.).
  • the processor 601 may include one or more microcontrollers (micro control units, MCUs), which are responsible for uniformly scheduling other modules/timing/transactions, etc.
  • microcontrollers microcontrollers
  • processor 601 may include one or more interfaces.
  • Interfaces may include integrated circuit (inter-integrated circuit, I2C) interface, integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, pulse code modulation (PCM) interface, universal asynchronous receiver and transmitter (universal asynchronous receiver/transmitter (UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and /or universal serial bus (USB) interface, etc.
  • I2C integrated circuit
  • I2S integrated circuit built-in audio
  • PCM pulse code modulation
  • UART universal asynchronous receiver and transmitter
  • MIPI mobile industry processor interface
  • GPIO general-purpose input/output
  • SIM subscriber identity module
  • USB universal serial bus
  • the I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (derail clock line, SCL).
  • processor 601 may include multiple sets of I2C buses.
  • the processor 601 can separately couple the sensor 604, microphone, camera, etc. through different I2C bus interfaces.
  • the processor 601 can couple the sensor 604 through an I2C interface, so that the processor 601 and the sensor 604 communicate through the I2C bus interface to implement the touch function of the PLC node.
  • the communication function of the PLC node can be implemented through power lines, communication module 602, modem processor, etc.
  • Power lines are used to transmit and receive signals. Power lines can be used to cover single or multiple communication bands.
  • the communication module 602 may provide solutions for application communication on electronic devices.
  • the communication module 602 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc.
  • the communication module 602 can receive signals from the power line, perform filtering, amplification and other processing on the received signals, and transmit them to the modem processor for demodulation.
  • the communication module 602 can also amplify the signal modulated by the modem processor and transmit it to other devices through the power line.
  • at least part of the functional modules of the communication module 602 may be disposed in the processor 601.
  • at least part of the functional modules of the communication module 602 and at least part of the modules of the processor 601 may be provided in the same device.
  • a modem processor may include a modulator and a demodulator.
  • the modulator is used to modulate and encode the signal to be sent into the information that needs to be transmitted.
  • the demodulator is used to demodulate the original signal from the received signal.
  • the modem processor may be a stand-alone device. In other embodiments, the modem processor may be independent of the processor and may be provided in the same device as the communication module or other functional modules.
  • Memory 603 may be used to store executable program code for a computer program.
  • the computer program may include a PLC network protocol stack.
  • the executable program code includes instructions.
  • the processor 601 can be used to execute instructions specified by the PLC protocol stack.
  • the memory 603 may include a program storage area and a data storage area.
  • the stored program area can store the operating system, at least one application program required for the function, etc.
  • the storage data area can store data created during the use of the electronic device (such as application data, user data, etc.).
  • the memory 603 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.
  • the processor 601 executes the instructions stored in the memory 603 and/or the instructions stored in the memory provided in the processor, executes various functional applications and data processing of the PLC node, and implements the communication process involved in the PLC network protocol stack or Processing.
  • Sensor 604 may be used to collect environmental information and/or sense user operations.
  • the user's operations include touch operations, click operations, sliding operations, the user's proximity to the screen, etc.
  • a pressure sensor is used to sense pressure signals and convert the pressure signals into electrical signals.
  • pressure sensors such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc.
  • a capacitive pressure sensor may include at least two parallel plates of conductive material.
  • the PLC node determines the intensity of the pressure based on changes in capacitance.
  • touch operation is performed on the PLC node, the PLC node detects the intensity of the touch operation based on the pressure sensor.
  • the PLC node can also calculate the location of the touch based on the signal detected by the pressure sensor.
  • touch operations acting on the same touch location but with different touch operation intensities may correspond to different operation instructions.
  • touch operations acting on the same touch location but with different touch durations may also correspond to different operation instructions.
  • the fingerprint sensor is used to collect fingerprints.
  • Temperature sensor is used to detect temperature.
  • the PLC node uses the temperature detected by the temperature sensor to execute the temperature processing strategy. For example, when the temperature reported by the temperature sensor exceeds a threshold, the PLC node reduces the performance of the processor located near the temperature sensor in order to reduce power consumption and implement thermal protection.
  • Touch sensor also called “touch panel”.
  • the touch sensor is used to detect touch operations on or near it (such as long press, swipe up, left swipe, click, double click, etc.).
  • the touch sensor can pass the detected touch operation to the processor 601 to determine the touch event type.
  • Power module 605 may include battery and charge management modules. Among them, the charging management module is used to receive charging input from the charger.
  • the power module 605 may also include a power management module for connecting the battery, the charging management module and the processor 601 .
  • the power management module receives input from the battery and/or charging management module and supplies power to the processor 601, communication line 602, memory 603, etc.
  • the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the PLC node.
  • the PLC node may include more or less components than shown in the figure, or combine some components, or split some components, or arrange different components.
  • the components illustrated may be implemented in hardware, software, or a combination of software and hardware.
  • the PLC node may also include a display screen.
  • the display screen is used to display images, videos, etc.
  • the display screen includes a display panel.
  • the display panel can use a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix organic light emitting diode).
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • active matrix organic light emitting diode active-matrix organic light emitting diode
  • emitting diode AMOLED
  • flexible light-emitting diode FLED
  • Miniled MicroLed, Micro-oLed, quantum dot light emitting diode (QLED), etc.
  • the PLC node may also include a camera to implement the shooting function.
  • the PLC node may also include buttons (such as a power button, a volume button, etc.).
  • the keys may be mechanical keys. It can also be a touch button.
  • the PLC node can receive key input and generate key signal input related to the user settings and function control of the PLC node.
  • the PLC node may also include a motor.
  • Motors are used to generate vibration cues.
  • the motor can be used to vibrate for incoming calls or for touch vibration feedback.
  • the touch vibration feedback effect can also be customized.
  • the PLC node may also include an indicator.
  • the indicator can be an indicator light, which can be used to indicate charging status, power changes, etc.
  • the structure of the PLC network protocol stack can be shown in Figure 7.
  • the PLC network protocol stack can include an application layer (also called a business layer), a data link layer (DLL) and a physical layer.
  • application layer also called a business layer
  • DLL data link layer
  • the application layer is mainly used to realize business data interaction between communication modules and complete data transmission through the data link layer.
  • the data link layer is mainly used to implement PLC network networking, network maintenance, routing management, connection management, sleep management, and application layer message aggregation, distribution and scheduling.
  • the data link layer can directly provide transmission services to the application layer.
  • the physical layer is mainly used to encode and modulate the data transmission messages that need to be distributed by the data link layer into carrier signals and send them to the power lines. It is also responsible for receiving the carrier signals transmitted on the power lines, demodulating and decoding them and sending them to the data link layer for processing. transmission.
  • the data link layer may include a management entity responsible for management plane matters such as routing, networking, sleep, and connection of PLC nodes, as well as multiple sub-layers for implementing the above services.
  • the data link layer can include DLL management entity (management entity), application protocol convergence (APC) layer, logical link control (LLC) layer and media access control ( media access control (MAC) layer.
  • management entity management entity
  • API application protocol convergence
  • LLC logical link control
  • MAC media access control
  • the APC layer is mainly responsible for the upload and delivery of the application layer and LLC layer.
  • the APC layer can process the original application data (application data primitive, ADP) from the application layer.
  • the APC layer can transmit information from the LLC layer to the application layer in the form of ADP.
  • the APC layer can exchange information such as address association table (ATT), classification data (classification data), high-level management messages (high-level management messages) and other information with the DLL management entity.
  • ATT may include but is not limited to local ATT and remote ATT. Local ATT can be used to characterize node information with business association (such as node physical address, etc.).
  • Remote ATT can be used to characterize other end nodes in the network and the node information (such as node physical address, etc.) of end nodes that are associated with these other end nodes.
  • Classified data can be used to characterize business priorities.
  • High-level management information is used to assist in the establishment of business flows.
  • ATT such as local ATT
  • the classified data can be used to assist the master node in determining business association information or node topology information, so as to group end nodes according to the business association information.
  • the classified data can be used to assist the master node in determining the sleep scheduling strategy, such as long sleep or short sleep; if a long sleep strategy is adopted, the classified data can also be used to assist the master node in determining the sleep type, sleep duration, wake-up duration or sleep cycle; if Using the short sleep strategy, the classified data can also be used to assist the master node in determining the short sleep bitmap.
  • the APC layer can exchange information with the application layer through the A-interface.
  • the LLC layer is mainly responsible for packet fragmentation aggregation, encryption and decryption, retransmission, routing and forwarding, etc.
  • the LLC layer can interact with the DLL management entity to interact with link control data unit (LCDU) data and other data, and obtain business service quality (quality of service, QoS), etc. from the DLL management entity.
  • LCDU link control data unit
  • QoS quality of service
  • LCDU data is used to assist in management interactions, such as short/long sleep application and confirmation, etc.
  • Service QoS may include but is not limited to service parameters such as service priority, bandwidth, delay, and packet size.
  • the LLC layer can exchange information with the APC layer through the x1 reference point.
  • the LLC layer and the APC layer can exchange information in the form of APC protocol data unit (APC protocol data unit, APDU) commands.
  • APC protocol data unit APC protocol data unit
  • the MAC layer is mainly responsible for the scheduling and transmission of messages and the time slotization of media access control.
  • the management entity of the data link layer is responsible for the routing, networking, sleep, connection and other management plane affairs of PLC nodes.
  • the MAC layer can exchange MAC parameters (such as transmission mode, transmission modulation order, number of retransmissions, transmission bandwidth and other data) with the DLL management entity.
  • the MAC parameter can be used to assist the master node in deciding the sleep duration, wake-up duration and other parameters of the sleep schedule.
  • the MAC layer can exchange information with the LLC layer through an x2 reference point.
  • the MAC layer and the LLC layer can exchange information in the form of logical link layer protocol data unit (logical link control protocol data unit, LPDU) commands.
  • logical link layer protocol data unit logical link control protocol data unit, LPDU
  • the MAC layer can exchange information with the physical layer through the physical medium interface (PMI).
  • PMI physical medium interface
  • Information can be exchanged between the MAC layer and the physical layer in the form of MAC protocol data unit (MPDU) commands.
  • MPDU MAC protocol data unit
  • the master node can make sleep scheduling decisions for end nodes based on service association information.
  • the PLC-based node scheduling method provided by the embodiment of the present application may include the following S901-S905:
  • S901 The master node obtains business related information.
  • the business association information is used to represent the business association situations of multiple end nodes, such as business association relationships.
  • the multiple nodes have a business association relationship.
  • lights and switch panels have a controlling and controlled relationship.
  • the switch panel in response to the user's pressing, clicking, sliding and other operations on the switch panel to turn on the lights, the switch panel can control The lamp is on.
  • the lights have a business relationship with the switch panel.
  • the access control device can control the door to open automatically when it captures the facial features of a user with access permission through the camera.
  • the access control device has a business relationship with the door.
  • the front-end detector set on the door/window controls the alarm to sound when it detects that the door/window is touched.
  • the front-end detector has a business association with the alarm.
  • the lighting control device when the lighting control device receives an operation to turn on road lighting, it controls the road lighting device to light up automatically.
  • the lighting control device has a business association with the road lighting device.
  • synchronization relationships include synchronization status, synchronization execution operations, synchronization settings, etc.
  • multiple road lighting devices on the same road section usually need to be turned on and off simultaneously.
  • multiple road lighting devices on the same road section have business relationships.
  • the multiple speakers have business relationships.
  • this application does not limit the specific business association between the end nodes. For example, if there are other business-related associations between the end nodes, it can also be considered that the end nodes have a business association.
  • the master node can determine the business related information of the end node according to the settings of the operation and maintenance personnel. For example, operation and maintenance personnel can associate multiple end nodes with services during network operation and maintenance. For example, operation and maintenance personnel can set up a switch panel to control multiple lights during network operation and maintenance. Based on this, the master node can determine that the switch panel has a business relationship with the multiple lights.
  • the master node may determine the business association information of the end node based on one or more of the user's operations, downloads, or settings. For example, the user can perform business association with multiple end nodes on the user management end node interface (such as application interface, applet interface, functional interface, etc.). For example, the user can set on the smart home application interface to turn on the air conditioner when the indoor temperature is higher than 30°. Based on this, the master node can determine that the temperature control panel and the air conditioner have a business relationship.
  • the user management end node interface such as application interface, applet interface, functional interface, etc.
  • the master node can determine the business-related information of the end node based on the information reported by the end node, such as business information, function information, status information, connection information, etc. For example, a speaker can report to the master node the connection information for establishing a communication connection with another speaker. Based on this, the master node can predict that the two speakers may be playing music synchronously. Further, the master node can determine whether the two speakers are playing music synchronously. speakers have business relationships.
  • the master node can determine the business association information of the end node according to the address association table (ATT), such as the node information with business association (such as the node physical address, etc.) indicated in the local ATT.
  • ATT address association table
  • the master node can also determine the business-related information through other ways.
  • the master node can also comprehensively determine the business association of the end node by combining the settings of the operation and maintenance personnel, the user's operations/downloads/settings, the information reported by the end node, and the node information with business association indicated in the ATT. information.
  • the master node determines the grouping information of the end node based on the service association information.
  • the group information of the end node can be used to characterize but is not limited to the identification (ID) of the members in the group.
  • multiple end nodes in the same group have business association relationships.
  • end node 1, end node 2 and end node 5 have a business association relationship, such as they are all used for the first service; end node 3 and end node 4 have a business association relationship, such as they are all used for the first service.
  • Second business Therefore, as shown in Figure 10, end node 1, end node 2 and end node 5 are located in group A, and end node 3 and end node 4 are located in group B.
  • multiple end nodes in the same group may have a parallel relationship, a communication interaction relationship, or other relationships, which are not specifically limited in this application.
  • end node 1, end node 2 and end node 5 in group A directly communicate with the master node respectively
  • end node 3 and end node 4 in group B directly communicate with the master node respectively.
  • end node 1, end node 2 and end node 5 are in a parallel relationship
  • end node 3 and end node 4 are in a parallel relationship.
  • end node 3 and end node 4 in group B directly communicate with the master node respectively, where end node 3 and end node 4 are in a parallel relationship.
  • end node 5 within group A is used to forward information from end node 1 and end node 2 to the master node, and forward information from the master node to end node 1 and end node 2, where the end node 1 and end node 2 are in a parallel relationship, end node 1 and end node 5 are in a direct communication relationship, and end node 2 and end node 5 are in a direct communication relationship.
  • the end node when the end node is far away from the main node (such as the power line distance), the end node can forward information to the main node through other end nodes that are closer to the main node.
  • the main node communicates with the main node through End nodes that are closer together forward information to end nodes that are farther away from the master node.
  • the relationship between the end node and the end node after the next hop has an indirect communication relationship; similarly, The relationship between any of the plurality of end nodes and the end node after the next hop/before the previous hop has an indirect communication relationship.
  • end node 5 and end node 4 in the group are used to forward information from end node 1 and end node 2 to the master node, and forward information from the master node to end node 1 and end node 2.
  • end node 1 and end node 2 are in a parallel relationship
  • end node 1 and end node 4 are in a direct communication relationship
  • end node 1 and end node 5 are in an indirect communication relationship
  • end node 4 and end node 5 are in a direct communication relationship
  • end node 1 and end node 5 are in a direct communication relationship
  • end node 1 and end node 5 are in a direct communication relationship
  • Node 2 and end node 4 have a direct communication relationship
  • end node 2 and end node 5 have an indirect communication relationship.
  • multiple end nodes in different groups may also have communication interaction relationships.
  • end node 3 and end node 4 in group B can pass End node 5 in group A forwards information to the master node; correspondingly, the master node forwards information to end nodes 3 and 4 in group B through end node 5 in group A.
  • end node 3 and end node 4 are in a parallel relationship
  • end node 3 and end node 5 are in a direct communication relationship
  • end node 4 and end node 5 are in a direct communication relationship.
  • the communication interaction relationship between multiple end nodes in different groups can also be an indirect communication relationship, which is not limited in the embodiment of this application.
  • the same node can be in multiple groups at the same time.
  • end node 1, end node 2 and end node 5 have a business association relationship. For example, they are all used for the first service.
  • End node 3, end node 4 and end node 5 have a business association relationship. For example, they are all used for the first service.
  • Second business. The master node is used to provide network management and air interface resource allocation services regarding the first service for end node 1, end node 2 and end node 5, and is used to provide end node 3, end node 4 and end node 5 regarding the second service. Network management and air interface resource allocation services. Therefore, as shown in Figure 13, end node 1 and end node 2 are located in group A, end node 3 and end node 4 are located in group B; end node 5 is located in both group A and group B.
  • the master node determines the sleep scheduling policy of the group based on the group service information. Alternatively, the master node determines the dormancy scheduling policy of the group based on the available resource information and the group service information.
  • the group service information may include but is not limited to the service QoS of each end node in the group.
  • Service QoS may include but is not limited to service parameters such as service priority, bandwidth, delay, and packet size.
  • the master node can obtain the packet service information from the end node.
  • the master node can determine the group service information based on the power line deployment topology (such as the sensing situation between end nodes, the connection relationship between end nodes, etc.).
  • This application does not specifically limit the specific channels through which the master node obtains group service information.
  • the sleep scheduling policy may be used to characterize: a group sleep policy.
  • group sleep strategies include short sleep, long sleep, etc.
  • the short sleep is such as L1 type sleep that sleeps and wakes up in every MAC cycle according to the short sleep bitmap.
  • Long sleep is a sleep type that periodically enters the sleep state (such as L2 type long sleep) or a sleep type that remains in the sleep state until it wakes up on its own or is awakened (such as L3 type long sleep).
  • the master node determines that all end nodes in the group are idle based on the group service information, the master node tends to keep the members in the group in a dormant state until they wake up on their own or are awakened, such as by end nodes in other groups. Wake up or wake up by the master node.
  • the group sleep policy determined by the master node is L3 type long sleep.
  • the master node determines that the currently available resources are insufficient to support the services corresponding to a certain group, the master node tends to keep members in low-level groups (such as low-priority and/or low-traffic-volume groups) in the Sleep state until it wakes up on its own or is woken up, such as by an end node in another group or by a master node.
  • the group sleep policy determined by the master node is L3 type long sleep.
  • the sleep scheduling policy can be used to characterize not only the group sleep policy, but also the group sleep type and short sleep bitmap.
  • the sleep scheduling policy can be used to indicate that the group sleep policy is L1 type sleep, and the group sleep type is scheduled once or periodically until modified.
  • the short sleep bitmap is such as 0001 0000 0000 0000 (represented in Wake up in the time period corresponding to the fourth time slice, and sleep in the time period corresponding to other time slices).
  • the sleep scheduling policy can be used to characterize not only the group sleep policy, but also the group sleep type, group sleep start time, and group sleep duration.
  • the group sleep type is scheduled once.
  • the group sleep start time is used to indicate the moment when multiple members in the group enter the sleep state.
  • the group sleep duration is used to indicate how long multiple members in the group have been in sleep state continuously.
  • the sleep scheduling policy can be used to represent that the group sleep policy is L2 type long sleep, the group sleep type is scheduled once, the group sleep start time is the specified time t1, and the group sleep duration is specified Duration k1.
  • the sleep scheduling policy can be used to characterize the group sleep policy, group sleep type, group sleep start time and group sleep duration, and can also be used to characterize the sleep cycle.
  • the group sleep type is periodic scheduling until modified.
  • the sleep cycle is used to indicate the cycle in which multiple members in the group enter the sleep state.
  • the sleep scheduling policy can be used to indicate that the group sleep policy is L2 type long sleep, the group sleep type is periodic scheduling until modified, the group sleep start time is the specified time t1, and the group sleep duration is the specified duration k1, and the sleep period is T.
  • the sleep scheduling policy can be used to characterize the group sleep policy, group sleep type, group sleep start time, and group sleep duration, and can also be used to characterize the group wake-up duration.
  • the group sleep type is periodic scheduling until modified.
  • the group wakeup duration is used to indicate the duration that multiple members in the group are continuously awake.
  • the sleep scheduling policy can be used to indicate that the group sleep policy is L2 type long sleep, the group sleep type is periodic scheduling until modified, the group sleep start time is the specified time t1, and the group sleep duration The specified duration is k1, and the group wake-up duration is k2.
  • the sleep time to enter the sleep state and the wake-up time to leave the sleep state and enter the wake-up state in each cycle can be determined according to the group sleep start time, group sleep duration and sleep cycle.
  • the sleep time and wake-up time in each cycle can also be determined based on the group sleep start time, group sleep duration, and group wake-up duration. Therefore, the group sleep start time, group sleep duration, and sleep period represented by the above sleep scheduling policy have the same effect as the group sleep start time, group sleep duration, and group wakeup time represented by the sleep scheduling policy, and are only used as different Manifestations.
  • the master node can comprehensively determine the dormancy scheduling policy of the group by combining the available resource information and the group service information.
  • the master node can determine the group sleep policy based on the group service information, and comprehensively determine specific parameters such as group sleep type, group sleep duration, and group wake-up duration based on available resource information and group service information.
  • the master node can comprehensively determine the group sleep policy based on available resource information and group service information, and determine specific parameters such as group sleep type, group sleep duration, and group wakeup duration.
  • the master node can directly determine the dormancy scheduling policy of the group based on the group service information.
  • the master node can directly determine that the group sleep policy of the group is L1 type sleep, and the group sleep type is scheduled once Or periodic scheduling until modified, and the master node can determine the short sleep bitmap.
  • the master node can directly determine that the group sleep policy of the group is long sleep and the group sleep type is scheduled once.
  • the group sleep start time is the specified time t1, and the group sleep duration is the specified time k1; or directly determine the group sleep policy of the group to long sleep, the group sleep type is periodic scheduling until modified, the group sleep start time is the specified time t1, and the group sleep The duration is the specified duration k1, and the sleep period is T; or the group sleep policy of the group is directly determined to be long sleep, the group sleep type is periodic scheduling until modified, the group sleep start time is the specified time t1, the group sleep duration is the specified duration k1, and the group sleep time is the specified time t1.
  • the wake-up duration is k2.
  • the master node can directly determine that the group sleep policy of the packet is L3 type long sleep.
  • the master node can also combine the available resource information and packet service information with other relevant information, such as network topology, packet priority, device priority, detection period, packet forwarding path length and channel conditions, etc. One or more of them, comprehensively determine the sleep scheduling policy of the group.
  • the master node can determine that the first group remains awake, the group sleep policy of the second group is L1 type sleep, and the group sleep type is scheduled once or periodically scheduled until Modify, and the master node can determine the short sleep bitmap.
  • the master node can determine that the first group remains awake, the group sleep policy of the second group is L2 type long sleep, the group sleep type is scheduled once, the group sleep start time is the specified time t1, and the group sleep duration is the specified duration. k1.
  • the master node can determine that the first group remains awake, the group sleep policy of the second group is L2 type long sleep, the group sleep type is periodic scheduling until modified, the group sleep start time is the specified time t1, and the group sleep duration is Specify the duration k1, and the sleep period is T.
  • the master node can determine that the first group remains awake, the group sleep policy of the second group is L2 type long sleep, the group sleep type is periodic scheduling until modified, the group sleep start time is the specified time t1, and the group sleep duration is Specify the duration k1, and the group wake-up duration is k2.
  • the master node may determine that the first group remains awake and the group sleep policy of the second group is L3 type long sleep.
  • the master node determines the sleep scheduling policy, how to determine the specific values of the group sleep policy, group sleep type, group sleep start time, group sleep duration, sleep cycle, group wake-up duration and other parameters, and determine the above parameters
  • the basis for the specific value, etc. is not limited in this application.
  • the master node can also use the detection cycle of the end node, the length of the message forwarding path, channel conditions, MAC parameters (such as transmission mode, transmission modulation order, number of retransmissions, transmission bandwidth, etc.), packet service information , one or more service parameters such as service priority, bandwidth, delay, and packet size, determine the specific values of parameters corresponding to the dormancy scheduling policy of the group.
  • MAC parameters such as transmission mode, transmission modulation order, number of retransmissions, transmission bandwidth, etc.
  • packet service information such as service priority, bandwidth, delay, and packet size
  • the group wake-up duration may be related to the packet size, packet forwarding path length and channel conditions.
  • the group sleep period may be related to the detection period of the end node (eg). For example, if the group includes sensors (such as touch sensors, temperature sensors, proximity light sensors, pressure sensors, magnetic sensors, air pressure sensors, distance sensors, fingerprint sensors, ambient light sensors, smoke sensors, etc.), the master node can add the group to The sleep period of the internal node is set to the detection period of the sensor (such as 100ms).
  • the entrance sensor and entrance spotlight are members of group A.
  • the entrance sensor senses that someone is moving within the preset range, it sends a message to the entrance spotlight to notify the entrance spotlight to light up.
  • the bedside sensor and bedroom lighting are members of group B.
  • the bedside sensor senses that someone is moving within the preset range, it sends information to the bedroom lighting to notify the bedroom lighting to turn on.
  • the detection cycle of the entrance sensor and bedside sensor is 100ms.
  • the group sleep period of group A and group B determined by the master node is 100ms
  • the wake-up time is 10ms
  • the sleep time is 90ms.
  • the entrance sensor and entrance spotlight are members of group A.
  • the entrance sensor senses that someone is moving within the preset range, it sends a message to the entrance spotlight to notify the entrance spotlight to light up.
  • the scene panel and the scene-controlled device are members of group B.
  • the scene panel detects a trigger action, it sends information to the scene-controlled device to notify the scene-controlled device to perform the corresponding action.
  • the detection cycle of the entrance sensor is 100ms.
  • the delay requirement for scene control services is 20ms.
  • the group sleep period of group A determined by the master node is 100ms, the wake-up time is 10ms, and the sleep time is 90ms.
  • the group sleep period of Group B determined by the master node is 20ms, the wake-up time is 10ms, and the sleep time is 10ms.
  • S904 The master node sends the group sleep scheduling information to the end node.
  • the master node can send the group sleep scheduling information to multiple end nodes in the corresponding group, so that the members in the group can Multiple end nodes can enter the sleep state and leave the sleep state at the same time according to the set of sleep scheduling information.
  • the master node can send the group sleep scheduling information to the end node in the form of a broadcast management frame (such as a beacon frame).
  • the beacon frame includes multiple beacon parameters, and the multiple beacon parameters are used to represent group sleep scheduling information. This application does not limit the specific manner in which the master node sends the group dormancy scheduling information to the end node.
  • the group sleep scheduling information can be used to characterize but is not limited to group identification (ID), group service type, group service name, group sleep policy, group sleep type, group sleep start time, group sleep duration, group wake-up duration, etc. one or more.
  • the group ID is used to uniquely identify one or more of the group in which the end node is located, the business corresponding to the group, or the scenario corresponding to the group determined by the master node based on the business association information.
  • the group sleep scheduling information can represent multiple groups at the granularity of the group sleep policy, as well as the group service type, group service name, group sleep type, group sleep start time, group sleep duration, and group wakeup duration of the multiple groups. and other parameters.
  • the group sleep scheduling information may include groups whose group sleep types are L1 type sleep, L2 type long sleep, and L3 type long sleep, where each group includes a group ID corresponding to the sleep type, group service type, group service name, group Sleep type, group sleep start time, group sleep duration, group wake-up duration and other parameters.
  • the group sleep scheduling information can represent the group ID corresponding to the group, the group service type, the group service name, the group sleep policy, the group sleep type, the group sleep start time, the group sleep duration, and the group wakeup duration at the granularity of the group. and other parameters.
  • the group sleep scheduling information may include a group ID and a group sleep policy.
  • the group sleep policy is L3 type long sleep.
  • the group sleep scheduling information may include the group ID, group sleep policy, and short sleep bitmap.
  • the group sleep scheduling information may include the group ID, group sleep policy, and short sleep bitmap.
  • the group sleep scheduling information may include group ID, group sleep policy, group sleep type, group sleep start time, and group sleep duration.
  • the group sleep scheduling information may include the group sleep start time and group sleep duration. Among them, the group sleep start time is used to indicate the moment when multiple members in the group enter the sleep state. The group sleep duration is used to indicate how long multiple members in the group have been in sleep state continuously.
  • the group sleep scheduling information may include group ID, group sleep policy, group sleep type, group sleep start time, group sleep duration, and sleep period.
  • group sleep policy is L2 type long sleep and the group sleep type is periodic scheduling until modified
  • group sleep scheduling information may include the group sleep start time, group sleep duration, and sleep period.
  • the sleep cycle is used to represent the cycle in which multiple members in the group enter the sleep state.
  • the group sleep scheduling information may include group ID, group sleep policy, group sleep type, group sleep start time, group sleep duration, and group wake-up duration.
  • group sleep policy is L2 type long sleep and the group sleep type is periodic scheduling until modified
  • group sleep scheduling information may include the group sleep start time, group sleep duration, and group wakeup duration.
  • the group wake-up duration is used to indicate the duration that multiple members in the group are continuously awake.
  • S905 The end node triggers the sleep wake-up mechanism according to the group sleep scheduling information.
  • the end node may trigger the sleep wake-up mechanism according to the group sleep scheduling information.
  • the end node determines that the group ID included in the group sleep scheduling information is not the ID of the group where the end node is located, the end node ignores the group sleep scheduling information and keeps the current status unchanged.
  • an end node if an end node is located in multiple groups at the same time.
  • the end node can enter the sleep state when the sleep scheduling information corresponding to multiple groups indicates that the end node can enter the sleep state.
  • the sleep scheduling information corresponding to any group in which an end node belongs indicates that the end node needs to be in the awake state, the end node cannot enter the sleep state.
  • the end node triggering the sleep wake-up mechanism according to the group sleep scheduling information may specifically include: the end node enters the L3 type sleep state according to the group sleep scheduling information (such as entering immediately after receiving the group sleep scheduling information) until it wakes up on its own. Or be awakened.
  • the end node enters the L3 type sleep state according to the group sleep scheduling information until it wakes up on its own or is woken up.
  • the end node triggering the sleep wake-up mechanism according to the group sleep scheduling information may specifically include: the end node sleeps or wakes up according to the group sleep scheduling information in the next MAC cycle.
  • the group sleep scheduling information includes a group sleep policy and a short sleep bitmap
  • the group sleep policy is LI type sleep and the short sleep bitmap is 0001 0000 0000 0000
  • the end node will use the group sleep schedule information in the next MAC cycle.
  • the short sleep bitmap wakes up in the time period corresponding to the fourth time slice and sleeps in the time period corresponding to other time slices.
  • the end node triggering the sleep wake-up mechanism according to the group sleep scheduling information may specifically include: the end node enters the sleep state at a specified time according to the group sleep scheduling information, such as the L2 type sleep state, until the specified sleep duration is met.
  • group sleep scheduling information includes group sleep policy, group sleep type, group sleep start time, and group sleep duration.
  • the group sleep policy is L2 type long sleep
  • the long sleep group sleep type is scheduled once
  • the group sleep start time is t1
  • the group sleep duration is the specified time k1
  • the end node enters the L2 type at the specified time t1 according to the group sleep scheduling information.
  • the designated time may mean starting immediately after receiving the group sleep scheduling information, or may represent other times, which are not limited in the embodiments of this application.
  • the end node triggering the sleep wake-up mechanism according to the group sleep schedule information may specifically include: the end node enters the sleep state at a specified time according to the group sleep schedule information, such as the L2 type sleep state, and leaves when the specified sleep duration is met. Sleep state, enter wake-up state, until the specified wake-up time is met.
  • group sleep scheduling information includes group sleep policy, group sleep type, group sleep start time, group sleep duration, and group wake-up duration.
  • the group sleep policy is L2 type long sleep
  • the long sleep group sleep type is periodic scheduling until modified
  • the group sleep start time is t1
  • the group sleep duration is the specified duration k1
  • the group wake-up duration is the specified duration k2
  • the sleep scheduling information enters the L2 type long sleep state at the specified time t1, leaves the sleep state when the specified sleep duration k1 is met, and enters the wake-up state until the specified wake-up duration k2 is met.
  • the designated time may mean starting immediately after receiving the group sleep scheduling information, or may represent other times, which are not limited in the embodiments of this application.
  • the end node triggering the sleep wake-up mechanism according to the group sleep schedule information may specifically include: the end node enters the sleep state at a specified time (such as t1) according to the group sleep schedule information, such as the L2 type sleep state, and waits until the specified time is satisfied. It leaves the sleep state and enters the wake-up state when the sleep duration (such as k1) is reached, and enters the sleep state again when the specified sleep period T is met.
  • a specified time such as t1
  • the group sleep schedule information such as the L2 type sleep state
  • group sleep scheduling information includes group sleep policy, group sleep type, group sleep start time, group sleep duration, and sleep period.
  • the group sleep policy is L2 type long sleep
  • the long sleep group sleep type is periodic scheduling until modified
  • the group sleep start time is t1
  • the group sleep duration is the specified duration k1
  • the sleep period is the specified duration T (such as 100ms)
  • the terminal enters the L2 type long sleep state at the specified time t1 according to the group sleep scheduling information, leaves the sleep state and enters the wake-up state when the specified sleep duration k1 is met, and enters the sleep state again when the specified sleep period T is met.
  • the designated time may mean starting immediately after receiving the group sleep scheduling information, or may represent other times, which are not limited in the embodiments of this application.
  • multiple members in the same group adopt the same sleep scheduling policy. That is, multiple members of the same group "wake up and sleep together.”
  • the group sleep policy is L3 type long sleep
  • all end nodes in the group enter the L3 type sleep state until they wake up at the same time.
  • the sleep state For example, when one end node wakes up, other end nodes leave the sleep state simultaneously.
  • Another example is when one end node wakes up on its own, other end nodes leave the sleep state synchronously.
  • the PLC-based node scheduling method can not only use the widely deployed power lines as transmission media, reduce early deployment costs and later maintenance costs, and avoid the impact of surrounding environment (such as electromagnetic interference, etc.) factors on communication.
  • the impact can also be achieved by grouping multiple end nodes according to business association conditions, and reasonably determining sleep scheduling policies based on group business related information (such as business QoS), such as group sleep policy, group sleep type, group sleep start time, group sleep Sleep duration, sleep cycle, group wake-up duration and other parameters,
  • group business related information such as business QoS
  • group sleep policy group sleep type, group sleep start time, group sleep Sleep duration, sleep cycle, group wake-up duration and other parameters
  • members in different groups are used for different services, so they can overlap with each other in time slots. This can also reduce packet loss caused by competition.
  • the end node can also update the service information to the master node, so that the master node can timely update the group service information of the end node.
  • the PLC-based node scheduling method provided by the embodiment of this application may also include the following S1401-S1402:
  • the end node can update service information to the master node through management frames (such as beacon frames).
  • management frames such as beacon frames
  • changes in end node services may be due to changes in the end node topology, changes in end node configuration, changes in user requirements, changes in business requirements, etc.
  • the bandwidth requirement is usually large, so the bandwidth is usually set to a larger value; however, when the end node is successfully powered on and works stably, in order to avoid Waste of bandwidth resources, the bandwidth setting will usually lower the level, such as lowering the bandwidth setting.
  • the end node's business changes the end node updates its business information to the master node so that the master node can promptly update the end node's group service information. Furthermore, the master node can re-determine the sleep scheduling strategy based on the updated business information when necessary.
  • S1402 The master node updates the group service information.
  • the master node can re-determine the sleep scheduling strategy based on the updated business information when necessary. That is, as shown in Figure 14, the PLC-based node scheduling method provided by the embodiment of the present application may also include the following S1403-S1405:
  • S1403 The master node re-determines the dormancy scheduling policy of the group based on the updated group service information. Or, the master node re-determines the dormancy scheduling policy of the group based on the available resource information and the updated group service information.
  • the updated group service information may include but is not limited to the updated service QoS of each end node in the group, etc.
  • the updated service QoS may include but is not limited to service parameters such as service priority, bandwidth, delay, and packet size.
  • the master node can directly re-determine the dormancy scheduling policy of the group based on the updated group service information.
  • the master node can re-determine the dormancy scheduling policy of the group by combining the available resource information and the updated group service information.
  • the master node can also combine the available resource information and the updated packet service information with other relevant information, such as network topology, packet priority, device priority, detection period, packet forwarding path length and channel One or more of the conditions, etc., re-determine the sleep scheduling policy of the group.
  • S1404 The master node sends group sleep scheduling information to the end node.
  • the set of sleep scheduling information sent by the master node to the end node is related to the sleep scheduling policy re-determined by the master node in S1403.
  • the master node can send the group sleep scheduling information to multiple end nodes in the corresponding group, so that multiple end nodes in the group can schedule according to the group sleep schedule.
  • Information enters sleep state at the same time and leaves sleep state at the same time.
  • the group sleep scheduling information may include a group ID and a group sleep policy.
  • the group sleep policy is L3 type long sleep.
  • the group sleep scheduling information may include the group ID, group sleep policy, and short sleep bitmap.
  • the group sleep policy is short sleep (such as L1 type sleep).
  • the group sleep scheduling information may include group ID, group sleep policy, group sleep type, group sleep start time, and group sleep duration.
  • the group sleep policy is L2 type long sleep. Group sleep type is scheduled once.
  • the group sleep scheduling information may include group ID, group sleep policy, group sleep type, group sleep start time, group sleep duration, and sleep period.
  • the group sleep policy is L2 type long sleep
  • the group sleep type is periodic scheduling until modified.
  • the group sleep scheduling information may include group ID, group sleep policy, group sleep type, group sleep start time, group sleep duration, and group wakeup duration.
  • the group sleep policy is L2 type long sleep
  • the group sleep type is periodic scheduling until modified.
  • the master node can send the group sleep scheduling information to the end node in the form of a broadcast management frame (such as a beacon frame).
  • a broadcast management frame such as a beacon frame
  • S1405 The end node triggers the sleep wake-up mechanism based on the latest received group sleep scheduling information.
  • the end node may trigger the sleep wake-up mechanism according to the group sleep scheduling information.
  • the end node determines that the group ID included in the group sleep scheduling information is not the ID of the group where the end node is located, the end node ignores the group sleep scheduling information and keeps the current status unchanged.
  • the end node can promptly notify the master node when the service changes, so that the master node can timely update the group service information of the end node, so that the master node can When necessary, the sleep scheduling strategy will be re-decided based on the updated business information.
  • This method can avoid the impact on the end node business caused by the unreasonable sleep scheduling strategy determined when the subsequent decision-making of the sleep scheduling strategy is caused by the master node not updating the group service information in a timely manner, or the end node power consumption caused by not fully sleeping the end node. Big question.
  • the master node can also send grouping change information to the end node so that the end node can update the grouping information in a timely manner.
  • the PLC-based node scheduling method provided by the embodiment of this application may also include the following S1501-S1503:
  • S1501 The master node determines that the grouping has changed.
  • the embodiments of this application do not limit the specific reasons and specific circumstances for group changes.
  • the change in the grouping may be caused by a change in the node group in the network or a change in the network topology.
  • S1502 The master node sends group change information to the end node.
  • the group change information can be used to represent the changed group ID and the IDs of members within the group.
  • the master node can send the group change information to the end node in the form of a broadcast management frame (such as a beacon frame).
  • a broadcast management frame such as a beacon frame
  • S1503 The end node updates the grouping information of the end node according to the grouping change information.
  • the master node can promptly notify the end nodes when the grouping changes, such as when the node group in the network changes or the network topology changes, so that the end nodes can Update group information in a timely manner.
  • This method can avoid the impact on the end node business caused by unreasonable sleep scheduling policy decisions due to asynchronous grouping information between the master node side and the end node side, or the problem of high power consumption of the end node caused by not fully sleeping the end node.
  • the master node can make sleep scheduling decisions for end nodes based on node topology information.
  • the PLC-based node scheduling method provided by the embodiment of the present application may include the following S1601-S1605:
  • S1601 The master node obtains node topology information.
  • node topology information is used to characterize whether multiple end nodes can perceive each other.
  • Mutual awareness means that both end nodes can receive signals from each other.
  • the node topology information is used by the master node to determine whether there will be mutual interference during the transmission process between multiple end nodes.
  • mutual interference between end nodes refers to the collision of data packets from multiple end nodes during the packet sending process.
  • mutual interference between end nodes means that data messages between end nodes that transmit data through different frequency bands cannot be received correctly due to adjacent channel energy leakage during the transmission process.
  • the sending end 1 sends information to the receiving end 1, and the sending end 2 sends information to the receiving end 2.
  • sender 1 and sender 2 access the channel for transmission at the same time, collisions between data packets may result in packet loss.
  • the data packet sent by sender 1 to receiver 1 will be lost due to collision with the data packet sent by sender 2.
  • the data packet sent by sender 2 to receiver 2 will be lost due to collision with the data packet sent by sender 1.
  • sender 1 and sender 2 interfere with each other.
  • the master node can obtain node topology information from the end node.
  • the end node can proactively report node topology information to the master node.
  • the master node can actively query (such as periodic query) node topology information from the end node.
  • an end node may record the topology information of the end node during processing of a specific event.
  • the specific event is that the end node accesses the PLC network. Based on this, the end node can send its recorded topology information to the master node.
  • the end node may record the topology information of the end node during PLC management.
  • the end node can record a forwarding table (such as an ATT table) that can characterize the node topology during the routing process. Based on this, the end node can send its recorded forwarding table (such as ATT table) that can characterize the node topology to the master node.
  • a forwarding table such as an ATT table
  • the master node determines the grouping information of the end node based on the node topology information.
  • the group information of the end node can be used to characterize but is not limited to the ID of the member in the group.
  • multiple end nodes in the same group do not interfere with each other.
  • multiple end nodes within the same group cannot receive each other's signals.
  • the master node can divide sender 1 and sender 2 into different groups. Furthermore, since sender 1 and receiver 1 have related services, and sender 2 and receiver 2 have related services, the master node can group sender 1 and receiver 1 into one group, and group sender 2 and receiver 2 into one group. group for another. As shown in FIG. 17B , the transmitting end 1 and the receiving end 1 are located in the group A, and the transmitting end 2 and the receiving end 2 are located in the group B.
  • end node 1 and end node 5 there is a direct connection relationship between end node 1 and end node 5, end node 2 and end node 5, and end node 1 and the master node.
  • End node 1 and the main node, end node 2 and the main node are indirectly connected to other end nodes through power lines.
  • End node 1 and end node 2 are respectively connected to the same end node.
  • end node 1 and end node 2 interfere with each other
  • end node 2 and end node 3 interfere with each other
  • end node 3 and end node 4 interfere with each other.
  • nodes that interfere with each other access the channel for transmission at the same time, they may cause collisions and packet loss.
  • the master node can connect end node 1 and end node 1.
  • Node 3 is grouped into a group, such as group A; and end node 2 and end node 4 are grouped into a group, such as group B.
  • the same end node may be in multiple groups at the same time. Among them, the end node and the end nodes in multiple groups do not interfere with each other.
  • the master node determines the sleep scheduling policy of the group based on the group service information. Alternatively, the master node determines the dormancy scheduling policy of the group based on the available resource information and the group service information.
  • the group service information may include but is not limited to the service QoS of each end node in the group.
  • Service QoS may include but is not limited to service parameters such as service priority, bandwidth, delay, and packet size.
  • the master node can obtain the packet service information from the end node.
  • the master node can determine the group service information based on the power line deployment topology (such as the sensing situation between end nodes, the connection relationship between end nodes, etc.).
  • This application does not specifically limit the specific channels through which the master node obtains group service information.
  • the sleep scheduling policy may be used to characterize: a group sleep policy.
  • group sleep policies include short sleep, long sleep (such as L2 type long sleep or L3 type long sleep), etc.
  • the sleep scheduling policy can be used to characterize not only the group sleep policy, but also the group sleep type and short sleep bitmap.
  • the group sleep policy is short sleep (such as L1 type sleep), and the group sleep type is scheduled once or periodically until modified.
  • the sleep scheduling policy can be used to characterize not only the group sleep policy, but also the group sleep type, group sleep start time, and group sleep duration. Among them, the group sleep type is scheduled once.
  • the sleep scheduling policy can be used to characterize the group sleep policy, group sleep type, group sleep start time and group sleep duration, and can also be used to characterize the sleep cycle.
  • the group sleep type is periodic scheduling until modified.
  • the sleep scheduling policy can be used to characterize the group sleep policy, group sleep type, group sleep start time, and group sleep duration, and can also be used to characterize the group wake-up duration.
  • the group sleep type is periodic scheduling until modified.
  • the master node can comprehensively determine the dormancy scheduling policy of the group by combining the available resource information and the group service information.
  • the master node can directly determine the dormancy scheduling policy of the group based on the group service information.
  • the master node can also combine the available resource information and packet service information with other relevant information, such as network topology, packet priority, device priority, detection period, packet forwarding path length and channel conditions, etc. One or more of them, comprehensively determine the sleep scheduling policy of the group.
  • the master node determines the sleep scheduling policy, how to determine the specific values of the group sleep policy, group sleep type, group sleep start time, group sleep duration, sleep cycle, group wake-up duration and other parameters, and determine the above parameters
  • the basis for the specific value, etc. is not limited in this application.
  • the master node can divide a MAC cycle into 16 time slots, in which group A and group B respectively occupy 8 non-overlapping time slots to avoid collisions between end nodes in the group when sending packets.
  • the sleep wake-up time slot bitmap of group A is 0b101010101010
  • the sleep wake-up time slot bitmap of group B is 0b01010101010101.
  • the master node can also configure the time slot granularity and the time slot positions allocated to each group according to the actual business situation and network channel conditions.
  • S1604 The master node sends group sleep scheduling information to the end node.
  • the set of sleep scheduling information sent by the master node to the end node is related to the sleep scheduling policy determined by the master node in S1603.
  • the master node can send the group sleep scheduling information to multiple end nodes in the corresponding group, so that multiple end nodes in the group can schedule according to the group sleep schedule.
  • Information enters sleep state at the same time and leaves sleep state at the same time.
  • the group sleep scheduling information can represent multiple groups at the granularity of the group sleep policy, as well as the group service type, group service name, group sleep type, group sleep start time, group sleep duration, and group wakeup duration of the multiple groups. and other parameters.
  • the group sleep scheduling information can represent the group ID corresponding to the group, the group service type, the group service name, the group sleep policy, the group type, the group sleep start time, the group sleep duration, the group wake-up duration, etc. at the group granularity. parameter.
  • the group sleep scheduling information may include a group ID and a group sleep policy.
  • the group sleep policy is L3 type long sleep.
  • the group sleep scheduling information may include the group ID, group sleep policy, and short sleep bitmap.
  • the group sleep scheduling information may include the group ID, group sleep policy, and short sleep bitmap.
  • the group sleep scheduling information may include group ID, group sleep policy, group sleep type, group sleep start time, and group sleep duration.
  • group sleep scheduling information may include the group sleep start time and group sleep duration.
  • the group sleep scheduling information may include group ID, group sleep policy, group sleep type, group sleep start time, group sleep duration, and sleep period.
  • group sleep policy is L2 type long sleep and the group sleep type is periodic scheduling until modified
  • group sleep scheduling information may include the group sleep start time, group sleep duration, and sleep period.
  • the group sleep scheduling information may include group ID, group sleep policy, group sleep type, group sleep start time, group sleep duration, and group wake-up duration.
  • group sleep policy is L2 type long sleep and the group sleep type is periodic scheduling until modified
  • group sleep scheduling information may include the group sleep start time, group sleep duration, and group wakeup duration.
  • the master node can send the group sleep scheduling information to the end node in the form of a broadcast management frame (such as a beacon frame).
  • a broadcast management frame such as a beacon frame
  • S1605 The end node triggers the sleep wake-up mechanism according to the group sleep scheduling information.
  • the end node may trigger the sleep wake-up mechanism according to the group sleep scheduling information.
  • the end node determines that the group ID included in the group sleep scheduling information is not the ID of the group where the end node is located, the end node ignores the group sleep scheduling information and keeps the current status unchanged.
  • an end node if an end node is located in multiple groups at the same time.
  • the end node can enter the sleep state when the sleep scheduling information corresponding to multiple groups indicates that the end node can enter the sleep state.
  • the sleep scheduling information corresponding to any group in which an end node belongs indicates that the end node needs to be in the awake state, the end node cannot enter the sleep state.
  • the PLC-based node scheduling method can not only use the widely deployed power lines as transmission media, reduce early deployment costs and later maintenance costs, and avoid surrounding environment (such as electromagnetic interference, etc.) factors from affecting communication.
  • the impact can also be achieved by grouping multiple end nodes based on node topology information, and reasonably determining sleep scheduling policies based on group business-related information (such as business QoS), such as group sleep policy, group sleep type, group sleep start time, group sleep Parameters such as sleep duration, sleep cycle, group wake-up duration, etc. can ensure the PLC communication business needs while allowing each node in the power line communication system to fully sleep to reduce the power consumption of each node.
  • group business-related information such as business QoS
  • members in different groups are used for different services, so they can overlap with each other in time slots. This can also reduce packet loss caused by competition.
  • the master node can also send grouping change information to the end node so that the end node can update the grouping information in a timely manner.
  • the PLC-based node scheduling method provided by the embodiment of this application may also include the following S1801-S1803:
  • S1801 The master node determines that the grouping has changed.
  • grouping changes may be caused by changes in node groups in the network, changes in the network topology, or changes in the perception between end nodes.
  • S1802 The master node sends group change information to the end node.
  • the group change information can be used to represent the changed group ID and the IDs of members within the group.
  • the master node can send the group change information to the end node in the form of a broadcast management frame (such as a beacon frame).
  • a broadcast management frame such as a beacon frame
  • S1803 The end node updates the grouping information of the end node according to the grouping change information.
  • the master node can promptly notify the end nodes when the grouping changes, such as when the node group in the network changes or the network topology changes, so that the end nodes Update group information in a timely manner.
  • This method can avoid the impact on the end node business caused by unreasonable sleep scheduling policy decisions due to asynchronous grouping information between the master node side and the end node side, or the problem of high power consumption of the end node caused by not fully sleeping the end node.
  • the master node may also comprehensively consider business association information and node topology information when determining grouping information. Based on this, the master node can group multiple end nodes by comprehensively considering the business association information and node topology information, and reasonably determine the sleep scheduling strategy based on the group business related information (such as business QoS), such as group sleep policy, group sleep type, Group sleep start time, group sleep duration, sleep cycle, group wake-up duration and other parameters can ensure the PLC communication business needs while allowing each node in the power line communication system to fully sleep to reduce the power consumption of each node.
  • group business related information such as business QoS
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be implemented in this application.
  • the implementation of the examples does not constitute any limitations.
  • a communication node (such as a master node or an end node) includes a corresponding hardware structure and/or software module to perform each function.
  • a communication node such as a master node or an end node
  • a communication node includes a corresponding hardware structure and/or software module to perform each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.
  • Embodiments of the present application can divide communication nodes (such as master nodes or end nodes) into functional modules.
  • functional modules can be divided into corresponding functional modules, or two or more functions can be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods.
  • each module in the communication node can be implemented in the form of software and/or hardware, and there is no specific limitation on this.
  • smart skipping ropes/electronic devices are presented in the form of functional modules.
  • Module here may refer to an application specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above functions.
  • ASIC application specific integrated circuit
  • the computer program product includes one or more computer instructions.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available media that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the available media may be magnetic media, (such as floppy disks, hard disks, etc. , tape), optical media (such as digital video disk (DVD)), or semiconductor media (such as solid state disk (SSD)), etc.
  • the steps of the methods or algorithms described in conjunction with the embodiments of the present application can be implemented in hardware, or can be implemented in a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, and the software modules can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, mobile hard disks, CD-ROM or any other form of storage well known in the art. in the medium.
  • An exemplary storage medium is coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and storage media may be located in an ASIC. Additionally, the ASIC can be located in an electronic device.
  • the processor and the storage medium may also exist as discrete components in a communication node (such as a master node or an end node).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Power Engineering (AREA)
  • Small-Scale Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Cable Transmission Systems, Equalization Of Radio And Reduction Of Echo (AREA)

Abstract

本申请公开了一种基于电力线通信(power line communication，PLC)的节点调度方法、设备及PLC系统，涉及通信技术领域，可以在保证PLC通信业务需求的同时，降低电力线通信系统中各个节点的功耗。其中，主节点和端节点可以利用已经广泛部署的电力线作为传输媒介，降低前期部署成本和后期维护成本，避免周边环境(如电磁干扰等)因素对通信的影响。另外，主节点可以通过根据业务关联情况对多个端节点进行分组，以及根据组业务相关信息和/或节点拓扑信息合理确定休眠调度策略。

Description

一种基于PLC的节点调度方法、设备及PLC系统
本申请要求于2022年5月26日提交国家知识产权局、申请号为202210590310.8、申请名称为“一种基于PLC的节点调度方法、设备及PLC系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种基于电力线通信(power line communication，PLC)的节点调度方法、设备及PLC系统。
背景技术
目前，随着智能家居、远程抄表、城市照明、智慧小区、停车场管理、安全防盗及消防报警系统等使用普及度的提高，电力线部署的普及度也越来也高。基于此，电力线通信(PLC)技术的发展也越来越快。PLC技术是指利用电力线作为通信媒介，通过载波方式传输信号的一种通信技术。PLC技术由于其可以利用现有的覆盖广泛的电力线作为传输媒介，因此不需要部署新线路，可以极大地降低前期部署成本。以及，PLC技术也不需要单独进行线路维护，因此也极大地降低了后期维护成本。另外，PLC技术不受周边环境(如电磁干扰等)因素的影响。
在基于PLC进行通信的过程中，各个节点之间的通信需要耗费较高的电量。尤其是对于一些充电类节点来说，较高的功耗会导致节点续航时间过短、浪费电能，影响用户体验。因此，基于PLC进行通信时，如何在保证通信业务需求的同时降低功耗是急需解决的问题。
发明内容
本申请提供一种基于PLC的节点调度方法、设备及PLC系统，可以在保证PLC通信业务需求的同时，降低电力线通信系统中各个节点的功耗。
为达到上述目的，本申请实施例采用如下技术方案：
第一方面，提供一种基于PLC的节点调度方法，该方法应用于PLC系统中，该PLC系统包括第一节点(也称主节点)和多个第二节点(也称端节点)，其中多个第二节点分别属于多个分组，该多个第二节点包括第三节点，第三节点与第一节点通过电力线连接。该方法包括：第一节点确定第三节点所在分组为第一分组；第一节点获取第一分组的分组业务信息；第一节点根据第一分组的分组业务信息向第三节点发送组休眠调度信息。其中，分组业务信息用于表征以下中的一个或多个：第一分组对应业务的业务优先级、带宽、时延、报文大小。组休眠调度信息包括组休眠策略，组休眠调度信息用于第三节点触发对应的休眠唤醒机制。
作为一种示例，第一节点可以直接基于第一分组的分组业务信息向第三节点发送组休眠调度信息。例如，第一节点可以直接基于第一分组的分组业务信息确定第一分组的休眠调度策略，休眠调度策略至少可以用于表征第一分组的组休眠策略。
作为另一种示例，第一节点可以综合考虑可用资源信息和分组业务信息向第三节点发送组休眠调度信息。例如，第一节点可以结合可用资源信息和分组业务信息综合确定第一分组的休眠调度策略，休眠调度策略至少可以用于表征第一分组的组休眠策略。
上述第一方面提供的方案，主节点和端节点可以利用已经广泛部署的电力线作为传输媒介，降低前期部署成本和后期维护成本，避免周边环境(如电磁干扰等)因素对通信的影响。另外，主节点可以通过根据业务关联情况对多个端节点进行分组，以及根据组业务相关信息(如业务优先级、带宽、时延、报文大小等业务服务质量(quality of service，QoS))合理确定休眠调度策略，从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述第一分组内的节点具有业务关联关系。即，同一分组内的多个成员“同醒同睡”。通过该方法，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。另外，由于不同分组内的成员用于不同的业务，因此在时隙上可以相互交叠。这样也可以降低因竞争带来的丢包。
在一种可能的实现方式中，上述第一分组内的节点之间的业务关联关系包括以下中的一种或多种：控制关系、同步关系。本申请不限定同一分组内多个端节点之间的具体关系，示例性地，多个端节点之间可以具有控制与被控制的关系、具有同步(如同步状态、同步执行操作、同步设置等)关系。通过将具有上述控制关系或同步关系等具有业务关联关系的端节点归于一个分组，可以在后续进行休眠调度策略决策时，保证同一分组内的多个成员“同醒同睡”不会对端节点的业务造成影响。
在一种可能的实现方式中，上述第一节点确定第三节点所在分组为第一分组，包括：第一节点获取用于表征多个第二节点之间的业务关联关系的业务关联信息；第一节点根据多个第二节点的业务关联信息确定多个第二节点所在的分组，其中确定的多个第二节点所在的分组包括上述第三节点所在的第一分组。主节点通过根据用于表征端节点之间业务关联关系的业务关联信息对端节点进行分组，使得具有业务关联关系的端节点采用相同的休眠调度策略。该方案可以保证同一分组内的多个成员根据相同休眠调度策略触发休眠唤醒机制时进行“同醒同睡”不会对端节点的业务造成影响。
在一种可能的实现方式中，第一节点可以根据以下中的一种或多种获取多个第二节点的业务关联信息：用户的设置或操作、第二节点上报的信息、地址关联表(address association table，ATT)。本申请不限定主节点获取端节点业务关联信息的途径。示例性地，端节点的业务关联信息可以由主节点根据运维人员的设置确定，或者由主节点根据用户的操作、下载或者设置中的一个或多个确定，或者由主节点根据端节点上报的信息(如业务信息、功能信息、状态信息、连接信息等)确定，或者由主节点根据ATT(如本地ATT中指示的具有业务关联的节点信息(如节点物理地址等))确定。
在一种可能的实现方式中，上述第一分组内的节点相互不干扰。通过该方法，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。另外，由于同一分组内的节点相互不干扰，因此可以避免相互干扰的端节点在发包时产生碰撞导致相互间的碰撞丢包。
在一种可能的实现方式中，上述第一节点确定第三节点所在分组为第一分组，包括：第一节点获取用于表征上述多个第二节点之间是否相互干扰的节点拓扑信息；第一节点根据上述多个第二节点的节点拓扑信息确定上述第一分组。主节点通过根据用于表征端节点之间是否相互干扰的节点拓扑信息对端节点进行分组，使得相互干扰的端节点不会同时唤醒，从而避免相互干扰的端节点在发包时产生碰撞导致相互间的碰撞丢包。
在一种可能的实现方式中，上述组休眠策略为L1类型休眠(如国际电信联盟(international telecommunication union，ITU)G.9961标准中所述L1类型休眠)，组休眠调度信息还包括组休眠类型和短休眠位图；其中，组休眠类型包括调度一次或者周期调度直到修改。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行L1类型休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L3类型长休眠(如ITU G.9961标准中所述L3类型长休眠)。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行L3类型长休眠。从而可以在无业务时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L2类型长休眠(如ITU G.9961标准中所述L2类型长休眠)，组休眠调度信息还包括组休眠类型、组休眠开始时间和组休眠时长；其中，组休眠类型包括调度一次或者周期调度直到修改。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠类型为周期调度直到修改，组休眠调度信息还包括休眠周期。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行周期性L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠类型为周期调度直到修改，组休眠调度信息还包括组唤醒时长。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行周期性L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述第一节点根据分组业务信息向第三节点发送组休眠调度信息，包括：第一节点根据分组业务信息，基于当前可用资源信息向第三节点发送组休眠调度信息。本申请不限定主节点决策休眠调度策略时的具体依据。可选的，主节点还可以根据分组业务信息，结合其它相关信息，如当前可用资源信息进行休眠调度策略，以保证得到的休眠调度策略更加合理化。
在一种可能的实现方式中，上述第一节点根据分组业务信息向第三节点发送组休眠调度信息，包括：第一节点根据分组业务信息向包括第三节点的多个第二节点广播组休眠调度信息。通过广播组休眠调度信息，可以保证端节点执行休眠调度策略的同步性和及时性。
在一种可能的实现方式中，上述第一节点获取第一分组的分组业务信息，包括：第一节点通过以下一种或多种方式获取第一分组的分组业务信息：从多个第二节点中的一个或多个处获取、根据电力线部署拓扑结构确定。本申请不限定主节点获取分组业务信息的具体途径。示例性地，主节点可以根据端节点上报的信息确定分组业务信息，或者根据电力线部署拓扑结构(如端节点之间的感知情况，端节点之间的连接关系等)确定分组业务信息。
在一种可能的实现方式中，第三节点与第一节点通过电力线直接连接；或者，第三节点通过第四节点与第一节点间接连接，第三节点与第四节点之间通过电力线连接，第四节点与第一节点之间通过电力线连接，第四节点属于上述多个第二节点。本申请不限定同一分组内端节点与主节点之间的拓扑结构。示例性地，端节点可以与主节点直接连接。或者，端节点还可以与主节点间接连接，如通过其它一个或多个端节点向主节点中转通信数据。
在一种可能的实现方式中，上述第四节点属于第一分组。对于端节点通过其它一个或多个端节点向主节点中转通信数据的情况，本申请不限定转发节点与上述端节点是否在一个分组内。例如，转发节点与上述端节点可以在一个分组内。基于此，本申请提供的方法可以适用于各种拓扑结构的PLC系统。
在一种可能的实现方式中，上述第四节点不属于第一分组。对于端节点通过其它一个或多个端节点向主节点中转通信数据的情况，本申请不限定转发节点与上述端节点是否在一个分组内。例如，转发节点与上述端节点可以不在一个分组内。基于此，本申请提供的方法可以适用于各种拓扑结构的PLC系统。
在一种可能的实现方式中，上述第四节点与第一节点之间的电力线距离大于第三节点与第一节点之间的电力线距离。通过由距离主节点电力线距离更近的端节点进行通信数据中转，可以保证数据的可靠性传输。
在一种可能的实现方式中，上述第三节点还属于第二分组，第二分组对应的组休眠调度信息与第一分组所对应的组休眠调度信息不冲突。端节点可以在多个分组对应的休眠调度信息均表征该端节点可以进入休眠状态时，进入休眠状态。换句话说，若一个端节点所在的任意一个分组对应的休眠调度信息表征该端节点需要处于唤醒状态，该端节点则不能进入休眠状态。通过该方法，可以保证业务的正常进行。
第二方面，提供一种基于PLC的节点调度方法，该方法应用于PLC系统中，其中PLC系统包括第一节点和多个第二节点，多个第二节点分别属于多个分组，多个第二节点中包括属于第一分组的第三节点，第三节点与第一节点通过电力线连接。该方法包括：第三节点接收来自第一节点的组休眠调度信息，组休眠调度信息包括组休眠策略，组休眠调度信息用于第三节点触发对应的休眠唤醒机制；第三节点根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制。
上述第二方面提供的方案，主节点和端节点可以利用已经广泛部署的电力线作为传输媒介，降低前期部署成本和后期维护成本，避免周边环境(如电磁干扰等)因素对通信的影响。另外，端节点可以根据主节点指示的以分组为粒度的休眠调度策略，以组为单位“同醒同睡”。通过该方法，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。
在一种可能的实现方式中，上述第一分组内的节点具有业务关联关系。即，同一分组内的多个成员“同醒同睡”。通过该方法，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。另外，由于不同分组内的成员用于不同的业务，因此在时隙上可以相互交叠。这样也可以降低因竞争带来的丢包。
在一种可能的实现方式中，上述第一分组内的节点之间的业务关联关系包括以下中的一种或多种：控制关系、同步关系。本申请不限定同一分组内多个端节点之间的具体关系，示例性地，多个端节点之间可以具有控制与被控制的关系、具有同步(如同步状态、同步执行操作、同步设置等)关系。通过根据上述控制关系或同步关系等业务关联关系进行分组，可以在后续进行休眠调度策略决策时，保证同一分组内的多个成员“同醒同睡”不会对端节点的业务造成影响。
在一种可能的实现方式中，上述第一分组内的节点相互不干扰。通过该方法，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。另外，由于同一分组内的节点相互不干扰，因此可以避免相互干扰的端节点在发包时产生碰撞导致相互间的碰撞丢包。
在一种可能的实现方式中，上述组休眠策略为L1类型休眠，组休眠调度信息还包括组休眠类型和短休眠位图，组休眠类型为调度一次；上述第三节点根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：第三节点根据短休眠位图，在下一个媒介接入控制(media access control，MAC)周期唤醒时间片对应的时刻唤醒，在休眠时间片对应的时刻休眠。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步执行一次L1类型休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L1类型休眠，组休眠调度信息还包括组休眠类型和短休眠位图，组休眠类型为周期调度直到修改；上述第三节点根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：第三节点根据短休眠位图，在后面每一个MAC周期唤醒时间片对应的时刻唤醒，在休眠时间片对应的时刻休眠。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步周期性执行L1类型休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L3类型长休眠，上述第三节点根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：第三节点根据组休眠策略所指示的L3类型长休眠进入休眠状态，直至自行唤醒或者被唤醒。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步执行L3类型长休眠。从而可以在无业务时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L2类型长休眠，组休眠调度信息还包括组休眠类型、组休眠开始时间和组休眠时长，组休眠类型为调度一次；上述第三节点根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：第三节点在上述休眠开始时间对应的时刻休眠，直至满足上述组休眠时长后唤醒。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步执行一次L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L2类型长休眠，组休眠调度信息还包括组休眠类型、组休眠开始时间、组休眠时长和休眠周期，组休眠类型为周期调度直到修改；上述第三节点根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：第三节点在上述休眠开始时间对应的时刻进入休眠状态，直至满足上述组休眠时长后唤醒；在满足上述休眠周期时，第三节点进入休眠状态，直至满足上述组休眠时长后唤醒；在再次满足上述休眠周期时，第三节点再次进入休眠状态，直至满足上述组休眠时长后唤醒，以此类推。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步周期性执行L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L2类型长休眠，组休眠调度信息还包括组休眠类型、组休眠开始时间、组休眠时长和组唤醒时长，组休眠类型为周期调度直到修改；上述第三节点根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：第三节点在上述休眠开始时间对应的时刻进入休眠状态，直至满足上述组休眠时长后唤醒；在满足上述组唤醒时长时，第三节点进入休眠状态，直至满足上述组休眠时长后唤醒；在再次满足上述组唤醒时长时，第三节点再次进入休眠状态，直至满足上述组休眠时长后唤醒，以此类推。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步周期性执行L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，第三节点与第一节点通过电力线直接连接；或者，第三节点通过第四节点与第一节点间接连接，第三节点与第四节点之间通过电力线连接，第四节点与第一节点之间通过电力线连接，第四节点属于上述多个第二节点。本申请不限定同一分组内端节点与主节点之间的拓扑结构。示例性地，端节点可以与主节点直接连接。或者，端节点还可以与主节点间接连接，如通过其它一个或多个端节点向主节点中转通信数据。
在一种可能的实现方式中，上述第四节点属于第一分组。对于端节点通过其它一个或多个端节点向主节点中转通信数据的情况，本申请不限定转发节点与上述端节点是否在一个分组内。例如，转发节点与上述端节点可以在一个分组内。基于此，本申请提供的方法可以适用于各种拓扑结构的PLC系统。
在一种可能的实现方式中，上述第四节点不属于第一分组。对于端节点通过其它一个或多个端节点向主节点中转通信数据的情况，本申请不限定转发节点与上述端节点是否在一个分组内。例如，转发节点与上述端节点可以不在一个分组内。基于此，本申请提供的方法可以适用于各种拓扑结构的PLC系统。
在一种可能的实现方式中，上述第四节点与第一节点之间的电力线距离大于第三节点与第一节点之间的电力线距离。通过由距离主节点电力线距离更近的端节点进行通信数据中转，可以保证数据的可靠性传输。
在一种可能的实现方式中，上述第三节点还属于第二分组，第二分组对应的组休眠调度信息与第一分组所对应的组休眠调度信息不冲突。端节点可以在多个分组对应的休眠调度信息均表征该端节点可以进入休眠状态时，进入休眠状态。换句话说，若一个端节点所在的任意一个分组对应的休眠调度信息表征该端节点需要处于唤醒状态，该端节点则不能进入休眠状态。通过该方法，可以保证业务的正常进行。
第三方面，提供一种通信节点，该通信节点为主节点，该主节点与多个第二节点(即端节点)通过电力线连接，该多个第二节点包括第三节点，该主节点包括：处理单元，用于确定第三节点所在分组为第一分组；信息获取单元，用于获取第一分组的分组业务信息；通信单元，用于根据第一分组的分组业务信息通过电力线向第三节点发送组休眠调度信息。其中，分组业务信息用于表征以下中的一个或多个：第一分组对应业务的业务优先级、带宽、时延、报文大小。组休眠调度信息包括组休眠策略，组休眠调度信息用于第三节点触发对应的休眠唤醒机制。
上述第三方面提供的方案，主节点和端节点可以利用已经广泛部署的电力线作为传输媒介，降低前期部署成本和后期维护成本，避免周边环境(如电磁干扰等)因素对通信的影响。另外，主节点可以通过根据业务关联情况对多个端节点进行分组，以及根据组业务相关信息(如业务优先级、带宽、时延、报文大小等业务QoS)合理确定休眠调度策略，从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述第一分组内的节点具有业务关联关系。即，同一分组内的多个成员“同醒同睡”。基于此，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。另外，由于不同分组内的成员用于不同的业务，因此在时隙上可以相互交叠。这样也可以降低因竞争带来的丢包。
在一种可能的实现方式中，上述第一分组内的节点之间的业务关联关系包括以下中的一种或多种：控制关系、同步关系。本申请不限定同一分组内多个端节点之间的具体关系，示例性地，多个端节点之间可以具有控制与被控制的关系、具有同步(如同步状态、同步执行操作、同步设置等)关系。通过将具有上述控制关系或同步关系等具有业务关联关系的端节点归于一个分组，可以在后续进行休眠调度策略决策时，保证同一分组内的多个成员“同醒同睡”不会对端节点的业务造成影响。
在一种可能的实现方式中，上述处理单元还用于：获取用于表征多个第二节点之间的业务关联关系的业务关联信息；上述处理单元确定第三节点所在分组为第一分组，包括：处理单元根据获取的多个第二节点的业务关联信息确定多个第二节点所在的分组，其中确定的多个第二节点所在的分组包括上述第三节点所在的第一分组。主节点通过根据用于表征端节点之间业务关联关系的业务关联信息对端节点进行分组，使得具有业务关联关系的端节点采用相同的休眠调度策略。该方案可以保证同一分组内的多个成员根据相同休眠调度策略触发休眠唤醒机制时进行“同醒同睡”不会对端节点的业务造成影响。
在一种可能的实现方式中，上述处理单元可以根据以下中的一种或多种获取多个第二节点的业务关联信息：用户的设置或操作、第二节点上报的信息、ATT。本申请不限定主节点获取端节点业务关联信息的途径。示例性地，端节点的业务关联信息可以由主节点根据运维人员的设置确定，或者由主节点根据用户的操作、下载或者设置中的一个或多个确定，或者由主节点根据端节点上报的信息(如业务信息、功能信息、状态信息、连接信息等)确定，或者由主节点根据ATT(如本地ATT中指示的具有业务关联的节点信息(如节点物理地址等))确定。
在一种可能的实现方式中，上述第一分组内的节点相互不干扰。基于此，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。另外，由于同一分组内的节点相互不干扰，因此可以避免相互干扰的端节点在发包时产生碰撞导致相互间的碰撞丢包。
在一种可能的实现方式中，上述处理单元还用于：获取用于表征上述多个第二节点之间是否相互干扰的节点拓扑信息；上述处理单元确定第三节点所在分组为第一分组，包括：处理单元根据上述多个第二节点的节点拓扑信息确定上述第一分组。主节点通过根据用于表征端节点之间是否相互干扰的节点拓扑信息对端节点进行分组，使得相互干扰的端节点不会同时唤醒，从而避免相互干扰的端节点在发包时产生碰撞导致相互间的碰撞丢包。
在一种可能的实现方式中，上述组休眠策略为L1类型休眠，组休眠调度信息还包括组休眠类型和短休眠位图；其中，组休眠类型包括调度一次或者周期调度直到修改。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行L1类型休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L3类型长休眠。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行L3类型长休眠。从而可以在无业务时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L2类型长休眠，组休眠调度信息还包括组休眠类型、组休眠开始时间和组休眠时长；其中，组休眠类型包括调度一次或者周期调度直到修改。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠类型为周期调度直到修改，组休眠调度信息还包括休眠周期。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行周期性L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠类型为周期调度直到修改，组休眠调度信息还包括组唤醒时长。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行周期性L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述通信单元根据分组业务信息向第三节点发送组休眠调度信息，包括：通信单元根据分组业务信息，基于当前可用资源信息向第三节点发送组休眠调度信息。本申请不限定主节点决策休眠调度策略时的具体依据。可选的，主节点还可以根据分组业务信息，结合其它相关信息，如当前可用资源信息进行休眠调度策略，以保证得到的休眠调度策略更加合理化。
在一种可能的实现方式中，上述通信单元根据分组业务信息向第三节点发送组休眠调度信息，包括：通信单元根据分组业务信息向包括第三节点的多个第二节点广播组休眠调度信息。通过广播组休眠调度信息，可以保证端节点执行休眠调度策略的同步性和及时性。
在一种可能的实现方式中，上述处理单元获取第一分组的分组业务信息，包括：处理单元通过以下一种或多种方式获取第一分组的分组业务信息：从多个第二节点中的一个或多个处获取、根据电力线部署拓扑结构确定。本申请不限定主节点获取分组业务信息的具体途径。示例性地，主节点可以根据端节点上报的信息确定分组业务信息，或者根据电力线部署拓扑结构(如端节点之间的感知情况，端节点之间的连接关系等)确定分组业务信息。
在一种可能的实现方式中，第三节点与主节点通过电力线直接连接；或者，第三节点通过第四节点与主节点间接连接，第三节点与第四节点之间通过电力线连接，第四节点与主节点之间通过电力线连接，第四节点属于上述多个第二节点。本申请不限定同一分组内端节点与主节点之间的拓扑结构。示例性地，端节点可以与主节点直接连接。或者，端节点还可以与主节点间接连接，如通过其它一个或多个端节点向主节点中转通信数据。
在一种可能的实现方式中，上述第四节点属于第一分组。对于端节点通过其它一个或多个端节点向主节点中转通信数据的情况，本申请不限定转发节点与上述端节点是否在一个分组内。例如，转发节点与上述端节点可以在一个分组内。基于此，本申请提供的方案可以适用于各种拓扑结构的PLC系统。
在一种可能的实现方式中，上述第四节点不属于第一分组。对于端节点通过其它一个或多个端节点向主节点中转通信数据的情况，本申请不限定转发节点与上述端节点是否在一个分组内。例如，转发节点与上述端节点可以不在一个分组内。基于此，本申请提供的方案可以适用于各种拓扑结构的PLC系统。
在一种可能的实现方式中，上述第四节点与主节点之间的电力线距离大于第三节点与主节点之间的电力线距离。通过由距离主节点电力线距离更近的端节点进行通信数据中转，可以保证数据的可靠性传输。
在一种可能的实现方式中，上述第三节点还属于第二分组，第二分组对应的组休眠调度信息与第一分组所对应的组休眠调度信息不冲突。端节点可以在多个分组对应的休眠调度信息均表征该端节点可以进入休眠状态时，进入休眠状态。换句话说，若一个端节点所在的任意一个分组对应的休眠调度信息表征该端节点需要处于唤醒状态，该端节点则不能进入休眠状态。基于此，可以保证业务的正常进行。
第四方面，提供一种通信节点，该通信节点为端节点，如第三节点，该端节点与主节点(如第一节点)通过电力线连接。该端节点包括：通信单元，用于接收来自第一节点的组休眠调度信息，组休眠调度信息包括组休眠策略，组休眠调度信息用于第三节点触发对应的休眠唤醒机制；处理单元，用于根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制。
上述第四方面提供的方案，主节点和端节点可以利用已经广泛部署的电力线作为传输媒介，降低前期部署成本和后期维护成本，避免周边环境(如电磁干扰等)因素对通信的影响。另外，端节点可以根据主节点指示的以分组为粒度的休眠调度策略，以组为单位“同醒同睡”。基于此，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。
在一种可能的实现方式中，上述第一分组内的节点具有业务关联关系。即，同一分组内的多个成员“同醒同睡”。基于此，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。另外，由于不同分组内的成员用于不同的业务，因此在时隙上可以相互交叠。这样也可以降低因竞争带来的丢包。
在一种可能的实现方式中，上述第一分组内的节点之间的业务关联关系包括以下中的一种或多种：控制关系、同步关系。本申请不限定同一分组内多个端节点之间的具体关系，示例性地，多个端节点之间可以具有控制与被控制的关系、具有同步(如同步状态、同步执行操作、同步设置等)关系。通过根据上述控制关系或同步关系等业务关联关系进行分组，可以在后续进行休眠调度策略决策时，保证同一分组内的多个成员“同醒同睡”不会对端节点的业务造成影响。
在一种可能的实现方式中，上述第一分组内的节点相互不干扰。基于此，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。另外，由于同一分组内的节点相互不干扰，因此可以避免相互干扰的端节点在发包时产生碰撞导致相互间的碰撞丢包。
在一种可能的实现方式中，上述组休眠策略为L1类型休眠，组休眠调度信息还包括组休眠类型和短休眠位图，组休眠类型为调度一次；上述处理单元根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：处理单元根据短休眠位图，在下一个MAC周期唤醒时间片对应的时刻唤醒，在休眠时间片对应的时刻休眠。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步执行一次L1类型休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L1类型休眠，组休眠调度信息还包括组休眠类型和短休眠位图，组休眠类型为周期调度直到修改；上述处理单元根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：处理单元根据短休眠位图，在后面每一个MAC周期唤醒时间片对应的时刻唤醒，在休眠时间片对应的时刻休眠。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步周期性执行L1类型休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L3类型长休眠，上述处理单元根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：处理单元根据组休眠策略所指示的L3类型长休眠进入休眠状态，直至自行唤醒或者被唤醒。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步执行L3类型长休眠。从而可以在无业务时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L2类型长休眠，组休眠调度信息还包括组休眠类型、组休眠开始时间和组休眠时长，组休眠类型为调度一次；上述处理单元根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：处理单元在上述休眠开始时间对应的时刻休眠，直至满足上述组休眠时长后唤醒。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步执行一次L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L2类型长休眠，组休眠调度信息还包括组休眠类型、组休眠开始时间、组休眠时长和休眠周期，组休眠类型为周期调度直到修改；上述处理单元根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：处理单元在上述休眠开始时间对应的时刻进入休眠状态，直至满足上述组休眠时长后唤醒；在满足上述休眠周期时，第三节点进入休眠状态，直至满足上述组休眠时长后唤醒；在再次满足上述休眠周期时，第三节点再次进入休眠状态，直至满足上述组休眠时长后唤醒，以此类推。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步周期性执行L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L2类型长休眠，组休眠调度信息还包括组休眠类型、组休眠开始时间、组休眠时长和组唤醒时长，组休眠类型为周期调度直到修改；上述处理单元根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：处理单元在上述休眠开始时间对应的时刻进入休眠状态，直至满足上述组休眠时长后唤醒；在满足上述组唤醒时长时，第三节点进入休眠状态，直至满足上述组休眠时长后唤醒；在再次满足上述组唤醒时长时，第三节点再次进入休眠状态，直至满足上述组休眠时长后唤醒，以此类推。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步周期性执行L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，第三节点与第一节点通过电力线直接连接；或者，第三节点通过第四节点与第一节点间接连接，第三节点与第四节点之间通过电力线连接，第四节点与第一节点之间通过电力线连接，第四节点是与主节点通过电力线连接的其它端节点。本申请不限定同一分组内端节点与主节点之间的拓扑结构。示例性地，端节点可以与主节点直接连接。或者，端节点还可以与主节点间接连接，如通过其它一个或多个端节点向主节点中转通信数据。
在一种可能的实现方式中，上述第四节点属于第一分组。对于端节点通过其它一个或多个端节点向主节点中转通信数据的情况，本申请不限定转发节点与上述端节点是否在一个分组内。例如，转发节点与上述端节点可以在一个分组内。基于此，本申请提供的方案可以适用于各种拓扑结构的PLC系统。
在一种可能的实现方式中，上述第四节点不属于第一分组。对于端节点通过其它一个或多个端节点向主节点中转通信数据的情况，本申请不限定转发节点与上述端节点是否在一个分组内。例如，转发节点与上述端节点可以不在一个分组内。基于此，本申请提供的方案可以适用于各种拓扑结构的PLC系统。
在一种可能的实现方式中，上述第四节点与第一节点之间的电力线距离大于第三节点与第一节点之间的电力线距离。通过由距离主节点电力线距离更近的端节点进行通信数据中转，可以保证数据的可靠性传输。
在一种可能的实现方式中，上述第三节点还属于第二分组，第二分组对应的组休眠调度信息与第一分组所对应的组休眠调度信息不冲突。端节点可以在多个分组对应的休眠调度信息均表征该端节点可以进入休眠状态时，进入休眠状态。换句话说，若一个端节点所在的任意一个分组对应的休眠调度信息表征该端节点需要处于唤醒状态，该端节点则不能进入休眠状态。基于此，可以保证业务的正常进行。
第五方面，提供一种通信节点，该通信节点为主节点，该主节点与多个第二节点(即端节点)通过电力线连接，该多个第二节点包括第三节点，该主节点包括：处理器，用于确定第三节点所在分组为第一分组，获取第一分组的分组业务信息；通信模块，用于根据第一分组的分组业务信息通过电力线向第三节点发送组休眠调度信息。其中，分组业务信息用于表征以下中的一个或多个：第一分组对应业务的业务优先级、带宽、时延、报文大小。组休眠调度信息包括组休眠策略，组休眠调度信息用于第三节点触发对应的休眠唤醒机制。
上述第五方面提供的方案，主节点和端节点可以利用已经广泛部署的电力线作为传输媒介，降低前期部署成本和后期维护成本，避免周边环境(如电磁干扰等)因素对通信的影响。另外，主节点可以通过根据业务关联情况对多个端节点进行分组，以及根据组业务相关信息(如业务优先级、带宽、时延、报文大小等业务QoS)合理确定休眠调度策略，从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述第一分组内的节点具有业务关联关系。即，同一分组内的多个成员“同醒同睡”。基于此，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。另外，由于不同分组内的成员用于不同的业务，因此在时隙上可以相互交叠。这样也可以降低因竞争带来的丢包。
在一种可能的实现方式中，上述第一分组内的节点之间的业务关联关系包括以下中的一种或多种：控制关系、同步关系。本申请不限定同一分组内多个端节点之间的具体关系，示例性地，多个端节点之间可以具有控制与被控制的关系、具有同步(如同步状态、同步执行操作、同步设置等)关系。通过将具有上述控制关系或同步关系等具有业务关联关系的端节点归于一个分组，可以在后续进行休眠调度策略决策时，保证同一分组内的多个成员“同醒同睡”不会对端节点的业务造成影响。
在一种可能的实现方式中，上述处理器还用于：获取用于表征多个第二节点之间的业务关联关系的业务关联信息；上述处理器确定第三节点所在分组为第一分组，包括：处理器根据获取的多个第二节点的业务关联信息确定多个第二节点所在的分组，其中确定的多个第二节点所在的分组包括上述第三节点所在的第一分组。主节点通过根据用于表征端节点之间业务关联关系的业务关联信息对端节点进行分组，使得具有业务关联关系的端节点采用相同的休眠调度策略。该方案可以保证同一分组内的多个成员根据相同休眠调度策略触发休眠唤醒机制时进行“同醒同睡”不会对端节点的业务造成影响。
在一种可能的实现方式中，上述处理器可以根据以下中的一种或多种获取多个第二节点的业务关联信息：用户的设置或操作、第二节点上报的信息、ATT。本申请不限定主节点获取端节点业务关联信息的途径。示例性地，端节点的业务关联信息可以由主节点根据运维人员的设置确定，或者由主节点根据用户的操作、下载或者设置中的一个或多个确定，或者由主节点根据端节点上报的信息(如业务信息、功能信息、状态信息、连接信息等)确定，或者由主节点根据ATT(如本地ATT中指示的具有业务关联的节点信息(如节点物理地址等))确定。
在一种可能的实现方式中，上述第一分组内的节点相互不干扰。基于此，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。另外，由于同一分组内的节点相互不干扰，因此可以避免相互干扰的端节点在发包时产生碰撞导致相互间的碰撞丢包。
在一种可能的实现方式中，上述处理器还用于：获取用于表征上述多个第二节点之间是否相互干扰的节点拓扑信息；上述处理器确定第三节点所在分组为第一分组，包括：处理器根据上述多个第二节点的节点拓扑信息确定上述第一分组。主节点通过根据用于表征端节点之间是否相互干扰的节点拓扑信息对端节点进行分组，使得相互干扰的端节点不会同时唤醒，从而避免相互干扰的端节点在发包时产生碰撞导致相互间的碰撞丢包。
在一种可能的实现方式中，上述组休眠策略为L1类型休眠，组休眠调度信息还包括组休眠类型和短休眠位图；其中，组休眠类型包括调度一次或者周期调度直到修改。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行L1类型休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L3类型长休眠。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行L3类型长休眠。从而可以在无业务时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L2类型长休眠，组休眠调度信息还包括组休眠类型、组休眠开始时间和组休眠时长；其中，组休眠类型包括调度一次或者周期调度直到修改。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠类型为周期调度直到修改，组休眠调度信息还包括休眠周期。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行周期性L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠类型为周期调度直到修改，组休眠调度信息还包括组唤醒时长。作为一种可能，主节点可以根据实际情况(如第一分组对应的具体业务需求)指示第一分组内的端节点执行周期性L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述通信模块根据分组业务信息向第三节点发送组休眠调度信息，包括：通信模块根据分组业务信息，基于当前可用资源信息向第三节点发送组休眠调度信息。本申请不限定主节点决策休眠调度策略时的具体依据。可选的，主节点还可以根据分组业务信息，结合其它相关信息，如当前可用资源信息进行休眠调度策略，以保证得到的休眠调度策略更加合理化。
在一种可能的实现方式中，上述通信模块根据分组业务信息向第三节点发送组休眠调度信息，包括：通信模块根据分组业务信息向包括第三节点的多个第二节点广播组休眠调度信息。通过广播组休眠调度信息，可以保证端节点执行休眠调度策略的同步性和及时性。
在一种可能的实现方式中，上述处理器获取第一分组的分组业务信息，包括：处理器通过以下一种或多种方式获取第一分组的分组业务信息：从多个第二节点中的一个或多个处获取、根据电力线部署拓扑结构确定。本申请不限定主节点获取分组业务信息的具体途径。示例性地，主节点可以根据端节点上报的信息确定分组业务信息，或者根据电力线部署拓扑结构(如端节点之间的感知情况，端节点之间的连接关系等)确定分组业务信息。
在一种可能的实现方式中，第三节点与主节点通过电力线直接连接；或者，第三节点通过第四节点与主节点间接连接，第三节点与第四节点之间通过电力线连接，第四节点与主节点之间通过电力线连接，第四节点属于上述多个第二节点。本申请不限定同一分组内端节点与主节点之间的拓扑结构。示例性地，端节点可以与主节点直接连接。或者，端节点还可以与主节点间接连接，如通过其它一个或多个端节点向主节点中转通信数据。
在一种可能的实现方式中，上述第四节点属于第一分组。对于端节点通过其它一个或多个端节点向主节点中转通信数据的情况，本申请不限定转发节点与上述端节点是否在一个分组内。例如，转发节点与上述端节点可以在一个分组内。基于此，本申请提供的方案可以适用于各种拓扑结构的PLC系统。
在一种可能的实现方式中，上述第四节点不属于第一分组。对于端节点通过其它一个或多个端节点向主节点中转通信数据的情况，本申请不限定转发节点与上述端节点是否在一个分组内。例如，转发节点与上述端节点可以不在一个分组内。基于此，本申请提供的方案可以适用于各种拓扑结构的PLC系统。
在一种可能的实现方式中，上述第四节点与主节点之间的电力线距离大于第三节点与主节点之间的电力线距离。通过由距离主节点电力线距离更近的端节点进行通信数据中转，可以保证数据的可靠性传输。
在一种可能的实现方式中，上述第三节点还属于第二分组，第二分组对应的组休眠调度信息与第一分组所对应的组休眠调度信息不冲突。端节点可以在多个分组对应的休眠调度信息均表征该端节点可以进入休眠状态时，进入休眠状态。换句话说，若一个端节点所在的任意一个分组对应的休眠调度信息表征该端节点需要处于唤醒状态，该端节点则不能进入休眠状态。基于此，可以保证业务的正常进行。
第六方面，提供一种通信节点，该通信节点为端节点，如第三节点，该端节点与主节点(如第一节点)通过电力线连接。该端节点包括：通信模块，用于接收来自第一节点的组休眠调度信息，组休眠调度信息包括组休眠策略，组休眠调度信息用于第三节点触发对应的休眠唤醒机制；处理器，用于根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制。
上述第六方面提供的方案，主节点和端节点可以利用已经广泛部署的电力线作为传输媒介，降低前期部署成本和后期维护成本，避免周边环境(如电磁干扰等)因素对通信的影响。另外，端节点可以根据主节点指示的以分组为粒度的休眠调度策略，以组为单位“同醒同睡”。基于此，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。
在一种可能的实现方式中，上述第一分组内的节点具有业务关联关系。即，同一分组内的多个成员“同醒同睡”。基于此，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。另外，由于不同分组内的成员用于不同的业务，因此在时隙上可以相互交叠。这样也可以降低因竞争带来的丢包。
在一种可能的实现方式中，上述第一分组内的节点之间的业务关联关系包括以下中的一种或多种：控制关系、同步关系。本申请不限定同一分组内多个端节点之间的具体关系，示例性地，多个端节点之间可以具有控制与被控制的关系、具有同步(如同步状态、同步执行操作、同步设置等)关系。通过根据上述控制关系或同步关系等业务关联关系进行分组，可以在后续进行休眠调度策略决策时，保证同一分组内的多个成员“同醒同睡”不会对端节点的业务造成影响。
在一种可能的实现方式中，上述第一分组内的节点相互不干扰。基于此，可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠。另外，由于同一分组内的节点相互不干扰，因此可以避免相互干扰的端节点在发包时产生碰撞导致相互间的碰撞丢包。
在一种可能的实现方式中，上述组休眠策略为L1类型休眠，组休眠调度信息还包括组休眠类型和短休眠位图，组休眠类型为调度一次；上述处理器根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：处理器根据短休眠位图，在下一个MAC周期唤醒时间片对应的时刻唤醒，在休眠时间片对应的时刻休眠。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步执行一次L1类型休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L1类型休眠，组休眠调度信息还包括组休眠类型和短休眠位图，组休眠类型为周期调度直到修改；上述处理器根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：处理器根据短休眠位图，在后面每一个MAC周期唤醒时间片对应的时刻唤醒，在休眠时间片对应的时刻休眠。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步周期性执行L1类型休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L3类型长休眠，上述处理器根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：处理器根据组休眠策略所指示的L3类型长休眠进入休眠状态，直至自行唤醒或者被唤醒。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步执行L3类型长休眠。从而可以在无业务时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L2类型长休眠，组休眠调度信息还包括组休眠类型、组休眠开始时间和组休眠时长，组休眠类型为调度一次；上述处理器根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：处理器在上述休眠开始时间对应的时刻休眠，直至满足上述组休眠时长后唤醒。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步执行一次L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L2类型长休眠，组休眠调度信息还包括组休眠类型、组休眠开始时间、组休眠时长和休眠周期，组休眠类型为周期调度直到修改；上述处理器根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：处理器在上述休眠开始时间对应的时刻进入休眠状态，直至满足上述组休眠时长后唤醒；在满足上述休眠周期时，第三节点进入休眠状态，直至满足上述组休眠时长后唤醒；在再次满足上述休眠周期时，第三节点再次进入休眠状态，直至满足上述组休眠时长后唤醒，以此类推。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步周期性执行L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，上述组休眠策略为L2类型长休眠，组休眠调度信息还包括组休眠类型、组休眠开始时间、组休眠时长和组唤醒时长，组休眠类型为周期调度直到修改；上述处理器根据组休眠调度信息与第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：处理器在上述休眠开始时间对应的时刻进入休眠状态，直至满足上述组休眠时长后唤醒；在满足上述组唤醒时长时，第三节点进入休眠状态，直至满足上述组休眠时长后唤醒；在再次满足上述组唤醒时长时，第三节点再次进入休眠状态，直至满足上述组休眠时长后唤醒，以此类推。作为一种可能，端节点可以根据主节点的指示与同一分组内的其它端节点同步周期性执行L2类型长休眠。从而可以在保证PLC通信业务需求的同时，让该分组内各个端节点充分休眠，以降低各个端节点的功耗。
在一种可能的实现方式中，第三节点与第一节点通过电力线直接连接；或者，第三节点通过第四节点与第一节点间接连接，第三节点与第四节点之间通过电力线连接，第四节点与第一节点之间通过电力线连接，第四节点是与主节点通过电力线连接的其它端节点。本申请不限定同一分组内端节点与主节点之间的拓扑结构。示例性地，端节点可以与主节点直接连接。或者，端节点还可以与主节点间接连接，如通过其它一个或多个端节点向主节点中转通信数据。
在一种可能的实现方式中，上述第四节点属于第一分组。对于端节点通过其它一个或多个端节点向主节点中转通信数据的情况，本申请不限定转发节点与上述端节点是否在一个分组内。例如，转发节点与上述端节点可以在一个分组内。基于此，本申请提供的方案可以适用于各种拓扑结构的PLC系统。
在一种可能的实现方式中，上述第四节点不属于第一分组。对于端节点通过其它一个或多个端节点向主节点中转通信数据的情况，本申请不限定转发节点与上述端节点是否在一个分组内。例如，转发节点与上述端节点可以不在一个分组内。基于此，本申请提供的方案可以适用于各种拓扑结构的PLC系统。
在一种可能的实现方式中，上述第四节点与第一节点之间的电力线距离大于第三节点与第一节点之间的电力线距离。通过由距离主节点电力线距离更近的端节点进行通信数据中转，可以保证数据的可靠性传输。
在一种可能的实现方式中，上述第三节点还属于第二分组，第二分组对应的组休眠调度信息与第一分组所对应的组休眠调度信息不冲突。端节点可以在多个分组对应的休眠调度信息均表征该端节点可以进入休眠状态时，进入休眠状态。换句话说，若一个端节点所在的任意一个分组对应的休眠调度信息表征该端节点需要处于唤醒状态，该端节点则不能进入休眠状态。基于此，可以保证业务的正常进行。
第七方面，提供一种PLC系统，该PLC系统包括如第三方面任一种可能的实现方式中的主节点，以及如第四方面任一种可能的实现方式中的端节点。
第八方面，提供一种PLC系统，该PLC系统包括如第五方面任一种可能的实现方式中的主节点，以及如第六方面任一种可能的实现方式中的端节点。
第九方面，提供一种计算机可读存储介质，该计算机可读存储介质上存储有计算机执行指令，该计算机执行指令被处理器执行时实现如第一方面或第二方面中任一种可能的实现方式中的方法。
第十方面，提供一种芯片系统，该芯片系统包括处理器、存储器，存储器中存储有指令；所述指令被所述处理器执行时，实现如第一方面或第二方面中任一种可能的实现方式中的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第十一方面，提供一种计算机程序产品，当其在计算机上运行时，使得实现如第一方面或第二方面中任一种可能的实现方式中的方法。
附图说明
图1为本申请实施例提供的一种电力线通信系统拓扑结构示意图；
图2为本申请实施例提供的一种基于PLC的节点调度过程示意图；
图3为本申请实施例提供的一种基于PLC的节点调度时隙示意图；
图4为本申请实施例提供的另一种基于PLC的节点调度过程示意图；
图5为本申请实施例提供的另一种基于PLC的节点调度时隙示意图；
图6为本申请实施例提供的一种PLC节点的硬件结构示意图；
图7为本申请实施例提供的一种PLC网络协议栈的结构示意图；
图8为本申请实施例提供的另一种PLC网络协议栈的结构示意图；
图9为本申请实施例提供的基于PLC的节点调度方法流程图一；
图10为本申请实施例提供的分组示意图一；
图11A为本申请实施例提供的分组示意图二；
图11B为本申请实施例提供的端节点关系示意图一；
图11C为本申请实施例提供的端节点关系示意图二；
图12为本申请实施例提供的端节点关系示意图三；
图13为本申请实施例提供的分组示意图三；
图14为本申请实施例提供的基于PLC的节点调度方法流程图二；
图15为本申请实施例提供的基于PLC的节点调度方法流程图三；
图16为本申请实施例提供的基于PLC的节点调度方法流程图四；
图17A为本申请实施例提供的节点间相互干扰示意图；
图17B为本申请实施例提供的分组示意图四；
图17C为本申请实施例提供的分组示意图五；
图18为本申请实施例提供的基于PLC的节点调度方法流程图五。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请实施例的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，在本申请实施例的描述中，“多个”是指两个或多于两个。
以下，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征。在本实施例的描述中，除非另有说明，“多个”的含义是两个或两个以上。
为了在保证PLC通信业务需求的同时，降低电力线通信系统中各个节点的功耗，作为一种可能的实现方式，本申请实施例提供一种基于电力线通信(PLC)的节点调度方法，该方法可以在节点空闲时，通过控制节点进入休眠状态，在不影响PLC通信业务需求的前提下，降低各个节点的功耗。
示例性地，本申请实施例提供的基于PLC的节点调度方法可以应用于布局有电力线的电力线通信系统中或者场景中。
其中，电力线通信系统中包括多个通信节点(也称PLC设备、PLC节点或PLC站点(station，STA))。该多个通信节点可以包括一个或多个主节点(domain master，DM)和一个或多个端节点(end point，EP)。主节点(DM)与端节点(EP)之间通过电力线通信。一个主节点(DM)可以与一个或多个端节点(EP)通过电力线连接。一个端节点(EP)也可以与其它一个或多个端节点(EP)通过电力线连接。
主节点(DM)主要用于负责整个电力线通信系统的网络管理和空口资源分配等。示例性地，主节点(DM)可以用于负责端节点(EP)的网络接入决策、端节点(EP)的带宽申请决策、端节点(EP)的流量申请决策、心跳管理、路由和拓扑管理、端节点(EP)的时隙资源的分配、休眠管理、应用层报文的汇聚和分发调度、网络维护等。例如，主节点可以是网关。端节点具备休眠功能。例如，端节点支持由工作模式切换为休眠模式，或者由休眠模式切换为工作模式；又如，端节点支持由工作状态(也称唤醒状态)切换为休眠状态，或者由休眠状态切换为工作状态。
需要说明的是，在一些场景中，一个节点既可以作为端节点，也可以作为主节点。例如，一个节点可以同时具备EP和DM的功能。在节点作为主节点时，该节点的DM功能开启。
需要说明的是，本申请实施例不限定PLC技术的频段及传输速率等。
示例性地，本申请实施例提供的基于PLC的节点调度方法可以适用于但不限于窄带PLC技术、中频带PLC技术和宽带PLC技术。其中，窄带PLC技术常用于低速率连接的中低压配电网自动化、电表抄表等场景中。中频带PLC技术常用于高可靠和实时控制类物联网场景，如智能电表、智能交通灯控制、智慧路灯等场景中。宽带PLC技术常用于家庭宽带接入、互连等场景中。
作为一种示例，电力线通信系统可以包括但不限定于智能家居系统、远程抄表系统、城市照明系统、智慧小区系统、停车场管理系统、安全防盗系统及消防报警系统等布局有电力线的系统。
作为一种示例，智能家居系统中的节点如网关、灯光驱动、灯、开关面板、温控面板、传感器(如触摸传感器、温度传感器、接近光传感器、压力传感器、磁传感器、气压传感器、距离传感器、指纹传感器、环境光传感器、烟雾传感器等)、新风装置、电动窗帘等。远程抄表系统中的节点如电表、水表、燃气表、数据采集器、抄表服务器等。城市照明系统中的节点如道路照明装置、景观照明装置、应急照明装置、照明控制装置等。智慧小区系统中的节点如门禁装置、门、电梯、监控、灯、水站、停车场闸机、自动喷淋设备、中控中心等。停车场管理系统中的节点如控制台、停车场闸机等。安全防盗系统中的节点如前端探测器、报警器、报警控制器等。消防报警系统中的节点如烟雾传感器、烟雾报警器、消防控制中心、网关等。
请参考图1，图1示出了本申请实施例提供的一种电力线通信系统拓扑结构示意图。如图1所示，电力线通信系统包括主节点、端节点1、端节点2、端节点3和端节点4。其中，主节点与端节点1、端节点2、端节点3和端节点4之间均部署有电力线，每一个端节点与主节点和其它端节点之间也均部署有电力线。
在本申请实施例中，为了在不影响PLC业务需求的前提下，降低各个节点的功耗，主节点可以根据端节点的请求，通过向端节点发送休眠调度信息以指示端节点根据接收到的调度信息休眠或唤醒。其中，上述休眠调度信息中携带有用于规定端节点休眠时刻(即休眠开始时间)和唤醒时刻(即唤醒开始时间，也称唤醒时间)的信息。端节点可以根据该休眠调度信息在规定的休眠时刻进入休眠状态，以及在规定的唤醒时刻进入工作状态。
示例性地，在本申请实施例中，可以基于以下方案1或方案2进行节点调度，以在不影响PLC业务需求的前提下，降低各个节点的功耗。
方案1：
在方案1中，主节点可以根据端节点的请求，通过向端节点发送调度信息以指示端节点根据接收到的调度信息进入短休眠状态。
其中，处于短休眠状态的节点可以在一个媒介接入控制 (media access control，MAC) 周期的一些时隙处于休眠状态，以及在另一些时隙处于工作状态。
例如，请参考图2，图2示出了本申请实施例提供的一种基于PLC的节点调度过程示意图。如图2所示，端节点向主节点发送进入短休眠请求，以请求进入短休眠状态(如国际电信联盟 (international telecommunication union，ITU) G.9961标准中所述根据短休眠位图在每一个MAC周期内进行休眠和唤醒的L1类型休眠状态)。在接收到来自端节点的进入短休眠请求之后，主节点向端节点发送短休眠确认消息。示例性地，若主节点评估端节点进入短休眠状态后对当前网络拓扑和业务没有影响，主节点向端节点发送的短休眠确认消息可以用于同意端节点的进入短休眠请求。进一步的，端节点根据主节点同意短休眠请求的消息休眠或唤醒。短休眠确认消息中携带有主节点同意短休眠请求的原因。
可选的，若主节点同意端节点的短休眠请求，但是要求端节点以主节点规定的休眠调度信息进行休眠或唤醒。主节点向端节点发送的短休眠确认消息中还携带有对应原因码。
进一步的，主节点还可以以广播的形式向端节点广播休眠调度信息。休眠调度信息中携带有用于规定端节点休眠时刻和唤醒时刻的信息。端节点可以根据休眠调度信息所规定的休眠时刻进入休眠状态，以及在规定的唤醒时刻进入工作状态。作为一种示例，主节点可以通过媒质接入规划(medium access plan，MAP)帧的辅助信息字段(如短休眠调度字段或者默认休眠调度字段)携带上述休眠调度信息。
作为另一种可能的情况，在接收到来自端节点的进入短休眠请求之后，若主节点评估端节点进入短休眠状态后对当前网络拓扑和业务有影响，主节点向端节点发送的短休眠确认消息可以用于拒绝端节点的短休眠请求的消息。短休眠确认消息中携带有主节点拒绝短休眠请求的原因。示例性地，主节点拒绝端节点的短休眠请求的原因可以包括但不限于睡眠时间过短、调度无解或者无原因拒绝等。
示例性地，图2所示端节点向主节点发送的进入短休眠请求可以包括但不限于短休眠类型和短休眠位图。其中，短休眠类型用于表征但不限于当前端节点发起的短休眠类型是周期的、非周期的或者取消休眠调度。短休眠位图用于表征但不限于端节点在一个MAC周期内希望唤醒和休眠的时隙。可选的，进入短休眠请求的报文还可以包括预留字段。
示例性地，一个MAC周期可以被划分为16个时间片(即16份)。短休眠位图如0001 0000 0000 0000表示在第四个时间片对应的时间段唤醒，在其它时间片对应的时间段休眠。
作为一种示例，图2所示端节点向主节点发送的进入短休眠请求的报文帧格式可以如以下表1所示：
表1

示例性地，图2所示主节点向端节点发送的短休眠确认消息可以包括但不限于同意/拒绝短休眠请求的原因码。示例性地，同意/拒绝短休眠请求的原因码如0b0000(表示无原因拒绝)、0b0001(表示因睡眠时间过长拒绝)、0b0010(表示因睡眠时间过短拒绝)、0b0011(表示因调度无解拒绝)、0b0100(表示调度问题已解决可重新尝试)、0b01019b(表示无条件接受)、0b0110(表示接受但具体调度以MAP帧短休眠调度字段为准)、0b0111(表示接受但具体调度以MAP帧默认休眠调度字段为准)等。可选的，短休眠确认消息的报文还可以包括预留字段。作为一种示例，图2所示主节点向端节点发送的短休眠确认消息的报文帧格式可以如以下表2所示：
表2
其中，本申请实施例所述MAP帧的短休眠调度字段可以包括针对电力线通信系统中各个端节点的短休眠调度信息，示例性地，短休眠调度信息可以包括但不限于短休眠端节点的标识(identification，ID)、短休眠端节点休眠类型和短休眠端节点的位图等。MAP帧的默认休眠调度字段可以包括针对电力线通信系统中各个端节点的休眠调度信息，包括短休眠调度信息和长休眠调度信息，示例性地，短休眠调度信息可以包括但不限于默认短休眠调度指示等。
作为一种示例，本申请实施例所述短休眠调度字段格式可以如以下表3所示，默认休眠调度字段格式可以如以下表4所示。
表3

其中，M为电力线通信系统中即将进入短休眠状态的端节点的数量(M为正整数，M＞1)。作为一种示例，若短休眠确认消息中携带的同意/拒绝短休眠请求的原因码为0b0110，则端节点根据短休眠调度字段决策休眠唤醒时隙。
表4

其中，i为电力线通信系统中即将离开L3类型长休眠的端节点的数量(i为正整数，i＞1)。其中，上述表4所示休眠开始MAC周期、默认休眠时长和默认唤醒时长针对的是ITU G.9961标准中所述周期性进入休眠状态的L2类型长休眠的节点。上述表4所示要求唤醒的端节点数、第1端节点ID、……、第i端节点ID针对的是ITU G.9961标准中所述一直处于休眠状态直至自行唤醒或者被唤醒的L3类型长休眠的节点。
作为一种示例，若短休眠确认消息中携带的同意/拒绝短休眠请求的原因码为0b0111，则端节点根据默认休眠调度字段决策休眠唤醒时隙。
但是，基于上述方案1进行节点调度时，多个端节点之间需要同步休眠以及同步唤醒。因此，多个端节点之间需要共享时隙以进行同步。如图3所示，在端节点A和端节点B同步之后，端节点A和端节点B的MAC周期同步。并且，端节点A和端节点B根据主节点的指示在同一MAC周期的时刻1同步进入短休眠状态，以及在同一MAC周期的时刻1同步唤醒。并且，在每一个MAC周期内，端节点A和端节点B进入短休眠状态和唤醒的时隙相同。也就是说，基于上述方案1进行节点调度时，工作在短休眠模式的端节点需要在每一个MAC周期内拥有相同的休眠时隙和唤醒时隙。
可以理解，基于上述方案1进行节点调度时，多个端节点之间的业务可能没有相关性，但是该多个端节点之间仍然需要共享时隙以进行同步。多个端节点之间的同步会造成多个端节点不必要的能量消耗。
为了解决上述问题，在不影响PLC业务需求的前提下，降低各个节点的功耗，本申请实施例还提供了以下方案2：
方案2：
在方案2中，主节点可以根据端节点的请求，通过向端节点发送调度信息以指示端节点根据接收到的调度信息进入长休眠状态。
其中，处于长休眠状态的节点可以跨MAC周期休眠，也就是说，处于长休眠状态的节点所持续的休眠状态可以跨MAC周期，例如从一个MAC周期的某一时隙开始持续到下一个MAC周期的某一时隙。
例如，请参考图4，图4示出了本申请实施例提供的另一种基于PLC的节点调度过程示意图。如图4所示，端节点向主节点发送进入长休眠请求，以请求进入长休眠状态(如ITU G.9961标准中所述L2类型的休眠状态或者L3类型的休眠状态)。在接收到来自端节点的进入长休眠请求之后，主节点向端节点发送长休眠确认消息。示例性地，若主节点评估端节点进入长休眠状态后对当前网络拓扑和业务没有影响，主节点向端节点发送的长休眠确认消息可以用于同意端节点的进入长休眠请求。进一步的，端节点根据主节点同意长休眠请求的消息休眠或唤醒。长休眠确认消息中携带有主节点同意长休眠请求的原因。
可选的，若主节点同意端节点的长休眠请求，但是要求端节点以主节点规定的休眠调度信息进行休眠或唤醒。主节点向端节点发送的长休眠确认消息中还携带有对应原因码。
进一步的，主节点还可以以广播的形式向端节点广播休眠调度信息，包括长休眠调度信息。休眠调度信息中携带有用于规定端节点休眠时刻和唤醒时刻的信息。端节点可以根据休眠调度信息所规定的休眠时刻进入休眠状态，以及在规定的唤醒时刻进入工作状态。作为一种示例，主节点可以通过MAP帧的辅助信息字段(如长休眠调度字段或者默认休眠调度字段)携带上述休眠调度信息，如长休眠调度信息。
作为另一种可能的情况，在接收到来自端节点的进入长休眠请求之后，若主节点评估端节点进入长休眠状态后对当前网络拓扑和业务有影响，主节点向端节点发送的长休眠确认消息可以用于拒绝端节点的长休眠请求的消息。长休眠确认消息中携带有主节点拒绝长休眠请求的原因。示例性地，主节点拒绝端节点的长休眠请求的原因可以包括但不限于睡眠时间过短、调度无解或者无原因拒绝等。
示例性地，图4所示端节点向主节点发送的进入长休眠请求可以包括但不限于长休眠类型、长休眠模式休眠时长和长休眠模式唤醒时长。
其中，长休眠类型用于表征但不限于当前端节点发起的长休眠类型是周期的、非周期的或者取消休眠调度。
长休眠模式休眠时长用于表征端节点在一个休眠周期内休眠的时间长度。示例性地，通常以MAC周期的1/16为基数设置长休眠模式休眠时长。作为一种示例，若长休眠模式休眠时长为0xFFFF，则表示不限制休眠时长，在这种情况下，长休眠模式为ITU G.9961标准中的L3类型的休眠状态。
长休眠模式唤醒时长用于表征紧跟休眠时间点后、节点唤醒的时长。示例性地，长休眠模式唤醒时长通常以MAC周期的1/16为基数设置长休眠模式唤醒时长。长休眠模式唤醒时长可以大于或等于一个MAC周期。长休眠模式唤醒时长还可以为0。可选的，进入长休眠请求的报文还可以包括预留字段。作为一种示例，图4所示端节点向主节点发送的进入长休眠请求的报文帧格式可以如以下表5所示：
表5

示例性地，图4所示主节点向端节点发送的长休眠确认消息可以包括但不限于同意/拒绝长休眠请求的原因码。示例性地，同意/拒绝长休眠请求的原因码如0b0000(表示无原因拒绝)、0b0001(表示因睡眠时间过长拒绝)、0b0010(表示因睡眠时间过短拒绝)、0b0011(表示因调度无解拒绝)、0b0100(表示调度问题已解决可重新尝试)、0b0101(表示因拓扑问题无解拒绝)、0b0110(表示拓扑问题已解决可重新尝试)、0b0111(表示接受但具体调度以MAP帧长休眠调度字段为准)、0b1000(表示接受但具体调度以MAP帧默认休眠调度字段为准)。可选的，长休眠确认消息的报文还可以包括预留字段。作为一种示例，图4所示主节点向端节点发送的长休眠确认消息的报文帧格式可以如以下表6所示：
表6
其中，本申请实施例所述MAP帧的长休眠调度字段可以包括针对电力线通信系统中各个端节点的长休眠调度信息，示例性地，长休眠调度信息可以包括但不限于长休眠端节点ID、长休眠端节点的休眠类型、长休眠端节点的休眠时长、长休眠端节点的唤醒时长。
作为一种示例，本申请实施例所述长休眠调度字段格式可以如以下表7所示。
表7

其中，N为电力线通信系统中即将进入长休眠状态的端节点的数量(N为正整数，N＞1)。需要说明的是，若长休眠节点的休眠时长为0xFFFF代表无限制休眠，如ITU G.9961标准中所述L3类型的休眠。
作为一种示例，本申请实施例所述携带有长休眠调度信息的默认休眠调度字段格式可以如上文中表4所示。其中，表4所示休眠开始MAC周期、默认休眠时长和默认唤醒时长针对的是L2类型长休眠的节点。上述表4所示要求唤醒的端节点数、第1端节点ID、……、第i端节点ID针对的是L3类型长休眠的节点。
可以理解，作为一种可能的实现方式，若端节点空闲，例如无业务时，端节点可以直接向主节点发送进入L3长休眠请求(如在进入长休眠请求中携带长休眠模式休眠时长0xFFFF)，以请求进入L3长休眠状态。在接收到来自端节点的进入L3长休眠模式请求之后，若主节点评估端节点进入L3长休眠状态后对当前网络拓扑和业务没有影响，主节点向端节点发送L3长休眠确认消息，用于同意端节点的进入L3长休眠请求。进一步的，端节点根据主节点同意L3长休眠请求的消息进入L3休眠状态，直至自行唤醒或者被唤醒。
其中，端节点自行唤醒是指处于L3休眠状态的端节点可以在有业务需求时自行唤醒，进入工作状态。
端节点被唤醒是指处于L3休眠状态的端节点可以接受其它节点通过MAP帧的辅助信息字段的唤醒域的唤醒，进入工作状态。例如，其它端节点可以通过向主节点发送唤醒请求，以请求唤醒一个或多个处于L3休眠状态的端节点。其中，唤醒请求中包括要求唤醒的端节点数和端节点ID。作为一种示例，唤醒请求的报文帧格式可以如以下表8所示：
表8
可以理解，虽然上述方案2进行节点调度时，多个端节点无需在每一个周期内同步休眠和同步唤醒，但是仍然需要同步休眠以及同步唤醒。例如，根据ITU G.9961标准的规定，进入L2长休眠状态的多个端节点需要在最大MAC休眠周期内至少拥有一个相同的唤醒时间片。又如，根据ITU G.9961标准的规定，进入L3长休眠状态的多个端节点需要与主节点同步MAP帧，以及在4个MAC休眠周期内至少有一次成功解析MAP帧。
如图5所示，端节点A和端节点D的休眠周期为2个MAC周期，端节点B的休眠周期为4个MAC周期，端节点C的休眠周期为8个MAC周期。由于端节点A、端节点B、端节点C和端节点D的休眠周期成整数倍，因此可以保证端节点A、端节点B、端节点C和端节点D至少拥有一个相同的唤醒时间片(如图5所示唤醒时间片A和唤醒时间片B)。
因此，基于上述方案2进行节点调度时，多个端节点之间需要共享至少一个共有时隙来进行同步。对于没有业务相关性的端节点，该方法由于多个端节点之间的同步仍然会造成多个端节点不必要的能量消耗。
另外，基于上述方案2进行节点调度时，若其它端节点向主节点发送唤醒请求，以请求唤醒一个或多个处于L3休眠状态的端节点，处于L3休眠状态的端节点可能需要经过较长时间才能感知到MAP帧。以图5所示休眠调度示意图为例，假设其它端节点在时刻1通过MAP帧请求唤醒处于L3休眠状态的端节点，则端节点C在经过7个MAC周期才能感知到用于唤醒该端节点的MAP帧。因此，该方法时延较大。
为了在不影响PLC业务需求的前提下，降低各个节点的功耗，以及降低因端节点休眠带来的响应时延，本申请实施例还提供了一种根据分组情况实施的基于PLC的节点调度方法。其中，在本申请实施例中，主节点可以根据端节点的业务关联情况和/或端节点之间的感知情况等对多个端节点进行分组，同一分组内的多个端节点之间可以共享时隙。
作为一种示例，同一分组内的多个端节点存在业务关联。
作为另一种示例，同一分组内的多个端节点之间传输无干扰。
其中，请参考图6，图6示出了本申请实施例提供的一种PLC节点的硬件结构示意图。
如图6所示，PLC节点(也称PLC设备或PLC站点(STA))可以包括处理器601，通信模块602，存储器603，传感器604和电源模块605。其中，传感器604可以包括压力传感器，陀螺仪传感器，气压传感器，磁传感器，距离传感器，接近光传感器，指纹传感器，温度传感器，触摸传感器，环境光传感器等。
可以理解的是，本发明实施例示意的结构并不构成对PLC节点的具体限定。在本申请另一些实施例中，PLC节点可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器601可以包括一个或多个处理单元。例如：处理器601可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，飞行控制器，视频编解码器，数字信号处理器(digital signal processor，DSP)和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
处理器601中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器601中的存储器为高速缓冲存储器。该存储器可以保存处理器601刚用过或循环使用的指令或数据。如果处理器601需要再次使用该指令或数据，可从所述存储器中直接调用。避免了重复存取，减少了处理器601的等待时间，因而提高了系统的效率。
在本申请实施例中，处理器601可以用于协同传感器604采集传感器数据(如触摸传感器数据、压力传感器数据等)。
在本申请实施例中，处理器601可以包括一个或多个微控制器(micro control unit，MCU)，用于负责统一调度其它模块/时序/事务的协调调度等。
在一些实施例中，处理器601可以包括一个或多个接口。接口可以包括集成电路(inter-integrated circuit，I2C)接口，集成电路内置音频(inter-integrated circuit sound，I2S)接口，脉冲编码调制(pulse code modulation，PCM)接口，通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口，移动产业处理器接口(mobile industry processor interface，MIPI)，通用输入输出(general-purpose input/output，GPIO)接口，用户标识模块(subscriber identity module，SIM)接口，和/或通用串行总线(universal serial bus，USB)接口等。
I2C接口是一种双向同步串行总线，包括一根串行数据线(serial data line，SDA)和一根串行时钟线(derail clock line，SCL)。在一些实施例中，处理器601可以包含多组I2C总线。处理器601可以通过不同的I2C总线接口分别耦合传感器604，麦克风，摄像头等。例如，处理器601可以通过I2C接口耦合传感器604，使处理器601与传感器604通过I2C总线接口通信，实现PLC节点的触摸功能。
PLC节点的通信功能可以通过电力线，通信模块602，调制解调处理器等实现。
电力线用于发射和接收信号。电力线可用于覆盖单个或多个通信频段。
通信模块602可以提供应用在电子设备上通信的解决方案。通信模块602可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。通信模块602可以由电力线接收信号，并对接收的信号进行滤波，放大等处理，传送至调制解调处理器进行解调。通信模块602还可以对经调制解调处理器调制后的信号放大，经电力线传输给其它设备。在一些实施例中，通信模块602的至少部分功能模块可以被设置于处理器601中。在一些实施例中，通信模块602的至少部分功能模块可以与处理器601的至少部分模块被设置在同一个器件中。
调制解调处理器可以包括调制器和解调器。其中，调制器用于将待发送的信号调制编码为需要传输的信息。解调器用于从接收的信号中解调得到原始信号。在一些实施例中，调制解调处理器可以是独立的器件。在另一些实施例中，调制解调处理器可以独立于处理器，与通信模块或其它功能模块设置在同一个器件中。
存储器603可以用于存储计算机程序的可执行程序代码。示例性地，计算机程序可以包括PLC网络协议栈。其中，可执行程序代码包括指令。处理器601可以用于执行PLC协议栈规定的指令。
存储器603可以包括存储程序区和存储数据区。其中，存储程序区可存储操作系统，至少一个功能所需的应用程序等。存储数据区可存储电子设备使用过程中所创建的数据(比如应用数据，用户数据等)等。此外，存储器603可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件，闪存器件，通用闪存存储器(universal flash storage，UFS)等。处理器601通过运行存储在存储器603的指令，和/或存储在设置于处理器中的存储器的指令，执行PLC节点的各种功能应用以及数据处理，实现PLC网络协议栈所涉及的通信过程或处理过程。
传感器604可以用于采集环境信息和/或感知用户的操作。示例性地，用户的操作如触摸操作、点击操作、滑动操作、用户靠近屏幕等。
例如，压力传感器用于感受压力信号，可以将压力信号转换成电信号。压力传感器的种类很多，如电阻式压力传感器，电感式压力传感器，电容式压力传感器等。电容式压力传感器可以是包括至少两个具有导电材料的平行板。当有力作用于压力传感器，电极之间的电容改变。PLC节点根据电容的变化确定压力的强度。当有触摸操作作用于PLC节点上，PLC节点根据压力传感器检测所述触摸操作强度。PLC节点也可以根据压力传感器检测的信号计算触摸的位置。在一些实施例中，作用于相同触摸位置，但不同触摸操作强度的触摸操作，可以对应不同的操作指令。在另一些实施例中，作用于相同触摸位置，但不同触摸时长的触摸操作，也可以对应不同的操作指令。
指纹传感器用于采集指纹。
温度传感器用于检测温度。在一些实施例中，PLC节点利用温度传感器检测的温度，执行温度处理策略。例如，当温度传感器上报的温度超过阈值，PLC节点执行降低位于温度传感器附近的处理器的性能，以便降低功耗实施热保护。
触摸传感器，也称“触控面板”。触摸传感器用于检测作用于其上或附近的触摸操作(例如长按、上滑、左滑、单击、双击等)。触摸传感器可以将检测到的触摸操作传递给处理器601，以确定触摸事件类型。
电源模块605可以包括电池和充电管理模块。其中，充电管理模块用于从充电器接收充电输入。
在一些实施例中，电源模块605还可以包括电源管理模块，用于连接电池、充电管理模块与处理器601。电源管理模块接收电池和/或充电管理模块的输入，为处理器601、通信线路602、存储器603等供电。
可以理解的是，本申请实施例示意的结构并不构成对PLC节点的具体限定。在本申请另一些实施例中，PLC节点可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
例如，在一些实施例中，PLC节点还可以包括显示屏。显示屏用于显示图像，视频等。显示屏包括显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)，有机发光二极管(organic light-emitting diode，OLED)，有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting diode的，AMOLED)，柔性发光二极管(flex light-emitting diode，FLED)，Miniled，MicroLed，Micro-oLed，量子点发光二极管(quantum dot light emitting diodes，QLED)等。
又如，在一些实施例中，PLC节点还可以包括摄像头，用于实现拍摄功能。
又如，在一些实施例中，PLC节点还可以包括按键(如开机键、音量键等)。按键可以是机械按键。也可以是触摸式按键。PLC节点可以接收按键输入，产生与PLC节点的用户设置以及功能控制有关的键信号输入。
又如，在一些实施例中，PLC节点还可以包括马达。马达用于产生振动提示。马达可以用于来电振动提示，也可以用于触摸振动反馈。触摸振动反馈效果还可以支持自定义。
又如，在一些实施例中，PLC节点还可以包括指示器。指示器可以是指示灯，可以用于指示充电状态，电量变化等。
作为一种示例，PLC网络协议栈的结构可以如图7所示。如图7所示，PLC网络协议栈可以包括应用层(application layer)(也称业务层)、数据链路层(data link layer，DLL)和物理层(physical layer)。
其中，应用层主要用于实现通信模块之间的业务数据交互，通过数据链路层完成数据传输。
数据链路层主要用于实现PLC网络的组网、网络维护、路由管理、连接管理、休眠管理及应用层报文的汇聚和分发调度等。数据链路层可直接向应用层提供传输服务。
物理层主要用于将需要数据链路层分发的数据传输报文编码、调制为载波信号，发送到电力线上，同时负责接收电力线上传输的载波信号经解调、解码发送至数据链路层进行传输。
在一些实施例中，数据链路层可以包括用于负责PLC节点的路由、组网、休眠、连接等管理面事务的管理实体，以及用于实现上述服务的多个子层。如图8所示，数据链路层可以包括DLL管理实体(management entity)、应用协议汇聚(application protocol convergence，APC)层、逻辑链路控制(logical link control，LLC)层和媒体接入控制(media access control，MAC)层。
其中，APC层主要负责应用层和LLC层的上传下达。APC层可以处理来自应用层的原始应用数据(application data primitive，ADP)。同时，APC层可以将来自LLC层的信息以ADP的形式传输至应用层。以及，APC层可以与DLL管理实体交互地址关联表(address association table，ATT)、分类数据(classification data)、高级别管理信息(high-level management messages)等信息。其中，ATT可以包括但不限于本地ATT和远端ATT。本地ATT可以用于表征具有业务关联的节点信息(如节点物理地址等)。远端ATT可以用于表征网络中其他端节点以及跟这些其他端节点具有关联关系的端节点的节点信息(如节点物理地址等)。分类数据可以用于表征业务优先级。高级别管理信息用于辅助进行业务流的建立。
在本申请实施例中，ATT，如本地ATT可以用于辅助主节点确定业务关联信息或者节点拓扑信息，从而根据业务关联信息对端节点进行分组。分类数据可以用于辅助主节点确定休眠调度策略，如长休眠还是短休眠；若采用长休眠策略，分类数据还可以用于辅助主节点确定休眠类型、休眠时长、唤醒时长或者休眠周期等；若采用短休眠策略，分类数据还可以用于辅助主节点确定短休眠位图。作为一种示例，如图8所示，APC层可以通过A接口(A-interface)与应用层交互信息。
LLC层主要负责报文的分片聚合、加解密、重传、路由转发等。以及，LLC层可以与DLL管理实体交互链路控制数据单元(link control data unit，LCDU)数据等数据，从DLL管理实体获取业务服务质量(quality of service，QoS)等。其中，LCDU数据用于辅助进行管理交互，如进行短/长休眠申请和确认等。业务QoS可以包括但不限于业务优先级、带宽、时延以及报文大小等业务参数。
作为一种示例，如图8所示，LLC层可以通过x1参考点(x1 reference point)与APC层交互信息。
作为一种示例，如图8所示，LLC层与APC层之间可以以APC协议数据单元(APC protocol data unit，APDU)命令的形式交互信息。
MAC层主要负责报文的调度传输以及媒介接入控制的时隙化，数据链路层的管理实体负责PLC节点的路由、组网、休眠、连接等管理面事务。以及，MAC层可以与DLL管理实体交互MAC参数(如传输模式、传输调制阶数、重传次数、传输带宽等数据)。在本申请实施例中，MAC参数可以用于辅助主节点决策休眠调度的休眠时长、唤醒时长等参数。
作为一种示例，如图8所示，MAC层可以通过x2参考点(x2 reference point)与LLC层交互信息。作为一种示例，如图8所示，MAC层与LLC层之间可以以逻辑链路层协议数据单元(logical link control protocol data unit，LPDU)命令的形式交互信息。
作为一种示例，如图8所示，MAC层可以通过物理层媒介接口(physical medium interface，PMI)与物理层交互信息。MAC层与物理层之间可以以MAC协议数据单元(MAC protocol data unit，MPDU)命令的形式交互信息。
以下将结合附图，对本申请实施例提供的根据分组情况实施的基于PLC的节点调度方法进行具体介绍。
在一些实施例中，主节点可以基于业务关联信息进行端节点的休眠调度决策。
如图9所示，本申请实施例提供的基于PLC的节点调度方法可以包括以下S901-S905：
S901：主节点获取业务关联信息。
其中，业务关联信息用于表征多个端节点的业务关联情况，如业务关联关系。
作为一种示例，若多个端节点之间具有控制与被控制的关系，可以认为该多个节点具有业务关联关系。
例如，在智能家居系统中，灯与开关面板具有控制与被控制的关系，如响应于用户在开关面板上的按压操作、点击操作、滑动操作等用于打开灯的操作，开关面板可以控制灯点亮。对于这种场景，灯与开关面板具有业务关联关系。
又如，在智慧小区系统中，门禁装置在通过摄像头捕获到具有出入权限的用户的人脸特征时，可以控制门自动打开。对于这种场景，门禁装置与门具有业务关联关系。
又如，在安全防盗系统中，设置在门/窗户上的前端探测器在检测到门/窗户被触碰时，控制报警器报警。对于这种场景，前端探测器与报警器具有业务关联关系。
又如，在城市照明系统中，照明控制装置在接收到开启道路照明的操作时，控制道路照明装置自动点亮。对于这种场景，照明控制装置与道路照明装置具有业务关联关系。
作为另一种示例，若多个端节点之间具有同步关系，可以认为该多个节点具有业务关联关系。其中，同步关系如同步状态、同步执行操作、同步设置等。
例如，在城市照明系统中，同一路段的多个道路照明装置通常需要同步点亮以及同步熄灭。对于这种场景，同一路段的多个道路照明装置具有业务关联关系。
又如，在智能家居系统中，同步进行音乐播放的多个音箱需要同步参数(如音量等)设置以及同步播放进度。对于这种场景，该多个音箱具有业务关联关系。
需要说明的是，本申请不限定端节点之间的具体业务关联情况，例如，对于端节点之间具有其它与业务有关的关联关系的情况，也可以认为端节点之间具有业务关联关系。
作为一种可能的实现方式，主节点可以根据运维人员的设置确定端节点的业务关联信息。示例性地，运维人员可以在组网运维时将多个端节点进行业务关联。例如，运维人员可以在组网运维时设置通过一个开关面板控制多个灯，基于此，主节点可以确定该一个开关面板与该多个灯具有业务关联关系。
作为另一种可能的实现方式，主节点可以根据用户的操作、下载或者设置中的一个或多个确定端节点的业务关联信息。示例性地，用户可以在用户管理端节点的界面(如应用界面、小程序界面、功能界面等)上将多个端节点进行业务关联。例如，用户可以在智能家居应用界面上设置当室内温度高于30°时，将空调打开，基于此，主节点可以确定温控面板与空调具有业务关联关系。
作为另一种可能的实现方式，主节点可以根据端节点上报的信息，如业务信息、功能信息、状态信息、连接信息等确定端节点的业务关联信息。例如，音箱可以向主节点上报其与另一个音箱之间建立通信连接的连接信息，基于此，主节点可以预测这两个音箱之间可能在同步播放音乐，进一步的，主节点可以确定这两个音箱具有业务关联关系。
作为另一种可能的实现方式，主节点可以根据地址关联表(ATT)，如本地ATT中指示的具有业务关联的节点信息(如节点物理地址等)确定端节点的业务关联信息。需要说明的是，上述确定端节点的业务关联信息的方式仅作为几种示例，主节点还可以通过其它途径确定业务关联信息。或者，主节点还可以结合运维人员的设置、用户的操作/下载/设置、端节点上报的信息和ATT中指示的具有业务关联的节点信息中的任意多个，综合确定端节点的业务关联信息。
S902：主节点根据业务关联信息确定端节点的分组信息。
其中，端节点的分组信息可以用于表征但不限于该分组内成员的标识(identification，ID)。
在本申请实施例中，同一分组内的多个端节点具有业务关联关系。
示例性地，如图10所示，端节点1、端节点2和端节点5具有业务关联关系，如均用于第一业务；端节点3和端节点4具有业务关联关系，如均用于第二业务。因此，如图10所示，端节点1、端节点2和端节点5位于组A中，端节点3和端节点4位于组B中。
其中，在本申请实施例中，同一分组内的多个端节点之间可以是并列关系，也可以具有通信交互关系，或者具有其它关系，本申请不做具体限定。
如图11A所示，组A内的端节点1、端节点2和端节点5分别直接与主节点通信，组B内的端节点3和端节点4分别直接与主节点通信。其中，端节点1、端节点2和端节点5是并列关系；端节点3和端节点4是并列关系。又如图11B所示，组B内的端节点3和端节点4分别直接与主节点通信，其中，端节点3和端节点4是并列关系。
其中，端节点之间具有通信交互关系如端节点之间具有直接通信关系或者端节点间间接通信。
如图11B所示，组A内的端节点5用于将来自端节点1和端节点2的信息转发至主节点，以及将来自主节点的信息转发至端节点1和端节点2，其中端节点1和端节点2是并列关系，端节点1和端节点5是直接通信关系，端节点2和端节点5是直接通信关系。
可以理解，对于端节点与主节点距离(如电力线距离)较远的情况，端节点可以通过其它与主节点距离较近的端节点向主节点转发信息，对应的，主节点通过与该主节点距离较近的端节点向与该主节点距离较远的端节点转发信息。基于此，在本申请实施例中，一个端节点分别通过多个端节点向主节点转发信息时，该端节点与下一跳之后的端节点之间的关系即具有间接通信关系；同样地，该多个端节点中的任意端节点与下一跳之后/上一跳之前的端节点之间的关系即具有间接通信关系。
如图11C所示，组内的端节点5和端节点4用于将来自端节点1和端节点2的信息转发至主节点，以及将来自主节点的信息转发至端节点1和端节点2。其中，端节点1和端节点2是并列关系，端节点1和端节点4是直接通信关系，端节点1和端节点5是间接通信关系，端节点4和端节点5是直接通信关系，端节点2和端节点4是直接通信关系，端节点2和端节点5是间接通信关系。
在本申请实施例中，不同分组内的多个端节点之间也可以具有通信交互关系。
如图12所示，假设组B内的端节点3和端节点4距离主节点较远，组A内的端节点5距离主节点较近，组B内的端节点3和端节点4可以通过组A内的端节点5向主节点转发信息；对应地，主节点通过组A内的端节点5向组B内的端节点3和端节点4转发信息。其中，端节点3和端节点4是并列关系，端节点3与端节点5是直接通信关系，端节点4与端节点5是直接通信关系。
可选的，不同分组内的多个端节点之间的通信交互关系还可以是间接通信关系，本申请实施例不做限定。
在一些实施例中，同一节点可以同时位于多个分组中。
如图13所示，端节点1、端节点2和端节点5具有业务关联关系，如均用于第一业务；端节点3、端节点4和端节点5具有业务关联关系，如均用于第二业务。主节点用于为端节点1、端节点2和端节点5提供关于第一业务的网络管理和空口资源分配服务，以及用于为端节点3、端节点4和端节点5提供关于第二业务的网络管理和空口资源分配服务。因此，如图13所示，端节点1、端节点2位于组A中，端节点3和端节点4位于组B中；端节点5即位于组A中，也位于组B中。
S903：主节点根据分组业务信息确定该分组的休眠调度策略。或者，主节点根据可用资源信息和分组业务信息确定该分组的休眠调度策略。
其中，分组业务信息可以包括但不限于分组内各个端节点的业务QoS等。业务QoS可以包括但不限于业务优先级、带宽、时延以及报文大小等业务参数。
作为一种可能的实现方式，主节点可以从端节点获取分组业务信息。
作为另一种可能的实现方式，主节点可以根据电力线部署拓扑结构(如端节点之间的感知情况，端节点之间的连接关系等)确定分组业务信息。
关于主节点获取分组业务信息的具体渠道，本申请不做具体限定。
在一些实施例中，休眠调度策略可以用于表征：组休眠策略。其中，组休眠策略如短休眠、长休眠等。示例性地，短休眠如根据短休眠位图在每一个MAC周期内进行休眠和唤醒的L1类型休眠。长休眠如周期性进入休眠状态的休眠类型(如L2类型长休眠)或者一直处于休眠状态直至自行唤醒或者被唤醒的休眠类型(如L3类型长休眠)。
例如，若主节点根据分组业务信息确定该分组内的端节点均空闲，则主节点倾向于使该分组内的成员一直处于休眠状态，直至自行唤醒或者被唤醒，如被其它分组内的端节点唤醒或者由主节点唤醒。对于这种情况，主节点确定的组休眠策略为L3类型长休眠。
又如，若主节点确定当前可用资源不足以支持某一分组所对应的业务，则主节点倾向于使低级别的分组(如低优先级和/或低业务量的分组)内的成员一直处于休眠状态，直至自行唤醒或者被唤醒，如被其它分组内的端节点唤醒或者由主节点唤醒。对于这种情况，主节点确定的组休眠策略为L3类型长休眠。
在另一些实施例中，休眠调度策略既可以用于表征组休眠策略，还可以用于表征组休眠类型和短休眠位图。
例如，对于休眠策略为L1类型休眠情况，休眠调度策略可以用于表征组休眠策略为L1类型休眠，组休眠类型为调度一次或者周期调度直到修改，短休眠位图如0001 0000 0000 0000(表示在第四个时间片对应的时间段唤醒，在其它时间片对应的时间段休眠)。
在另一些实施例中，休眠调度策略既可以用于表征组休眠策略，还可以用于表征组休眠类型、组休眠开始时间和组休眠时长。其中，组休眠类型如调度一次。组休眠开始时间用于表示组内多个成员进入休眠状态的时刻。组休眠时长用于表示组内多个成员连续处于休眠状态的时长。
例如，对于休眠策略为L2类型长休眠的情况，休眠调度策略可以用于表征组休眠策略为L2类型长休眠，组休眠类型为调度一次，组休眠开始时间为指定时刻t1，组休眠时长为指定时长k1。
在另一些实施例中，休眠调度策略既可以用于表征组休眠策略、组休眠类型、组休眠开始时间和组休眠时长，还可以用于表征休眠周期。其中，组休眠类型如周期调度直到修改。休眠周期用于表示组内多个成员进入休眠状态的周期。
例如，对于休眠策略为L2类型长休眠的情况，休眠调度策略可以用于表征组休眠策略为L2类型长休眠，组休眠类型为周期调度直到修改，组休眠开始时间为指定时刻t1，组休眠时长为指定时长k1，休眠周期为T。
在另一些实施例中，休眠调度策略既可以用于表征组休眠策略、组休眠类型、组休眠开始时间和组休眠时长，还可以用于表征组唤醒时长。其中，组休眠类型如周期调度直到修改。组唤醒时长用于表示组内多个成员连续处于唤醒状态的时长。
例如，对于休眠策略为L2类型长休眠的情况，休眠调度策略可以用于表征组休眠策略为L2类型长休眠，组休眠类型为周期调度直到修改，组休眠开始时间为指定时刻t1，组休眠时长为指定时长k1，组唤醒时长为k2。
可以理解，根据组休眠开始时间、组休眠时长和休眠周期可以确定在每一个周期内进入休眠状态的休眠时刻和离开休眠状态进入唤醒状态的唤醒时刻。同样地，根据组休眠开始时间、组休眠时长和组唤醒时长也可以确定在每一个周期内的休眠时刻和唤醒时刻。因此，上述休眠调度策略所表征的组休眠开始时间、组休眠时长和休眠周期，与休眠调度策略所表征的组休眠开始时间、组休眠时长和组唤醒时长的作用是等同的，仅作为不同的表现形式。
作为一种可能的实现方式，主节点可以结合可用资源信息和分组业务信息综合确定分组的休眠调度策略。
示例性地，主节点可以根据分组业务信息确定组休眠策略，以及结合可用资源信息和分组业务信息综合确定组休眠类型、组休眠时长、组唤醒时长等具体参数。
又一示例性地，主节点可以结合可用资源信息和分组业务信息综合确定组休眠策略，以及确定组休眠类型、组休眠时长、组唤醒时长等具体参数。
作为另一种可能的实现方式，主节点可以根据分组业务信息直接确定分组的休眠调度策略。
例如，当分组业务信息表征业务优先级较低、业务对时延要求不高且业务报文小于预设阈值，主节点可以直接确定分组的组休眠策略为L1类型休眠，组休眠类型为调度一次或者周期调度直到修改，以及主节点可以确定短休眠位图。
又如，当分组业务信息表征业务优先级较低、业务对时延要求不高且业务报文小于预设阈值，主节点可以直接确定分组的组休眠策略为长休眠，组休眠类型为调度一次，组休眠开始时间为指定时刻t1，组休眠时长为指定时长k1；或者直接确定分组的组休眠策略为长休眠，组休眠类型为周期调度直到修改，组休眠开始时间为指定时刻t1，组休眠时长为指定时长k1，休眠周期为T；或者直接确定分组的组休眠策略为长休眠，组休眠类型为周期调度直到修改，组休眠开始时间为指定时刻t1，组休眠时长为指定时长k1，组唤醒时长为k2。
又如，当分组业务信息表征业务量为0(如无业务报文)，主节点可以直接确定分组的组休眠策略为L3类型长休眠。
在一些实施例中，主节点还可以根据可用资源信息和分组业务信息，结合其它相关信息，如网络拓扑结构、分组优先级、设备优先级、检测周期、报文转发路径长度和信道状况等中的一个或多个，综合确定分组的休眠调度策略。
例如，假设第一分组和第二分组均处于唤醒状态，且第一分组的优先级和业务优先级均高于第二分组，当可用资源信息表征当前可用资源不足以满足第一分组所对应的业务需求，但是可以满足第二分组所对应的业务需求，主节点可以确定第一分组保持唤醒状态不变，第二分组的组休眠策略为L1类型休眠，组休眠类型为调度一次或者周期调度直到修改，以及主节点可以确定短休眠位图。或者，主节点可以确定第一分组保持唤醒状态不变，第二分组的组休眠策略为L2类型长休眠，组休眠类型为调度一次，组休眠开始时间为指定时刻t1，组休眠时长为指定时长k1。或者，主节点可以确定第一分组保持唤醒状态不变，第二分组的组休眠策略为L2类型长休眠，组休眠类型为周期调度直到修改，组休眠开始时间为指定时刻t1，组休眠时长为指定时长k1，休眠周期为T。或者，主节点可以确定第一分组保持唤醒状态不变，第二分组的组休眠策略为L2类型长休眠，组休眠类型为周期调度直到修改，组休眠开始时间为指定时刻t1，组休眠时长为指定时长k1，组唤醒时长为k2。或者，主节点可以确定第一分组保持唤醒状态不变，第二分组的组休眠策略为L3类型长休眠。
需要说明的是，主节点在确定休眠调度策略时，具体如何确定组休眠策略、组休眠类型、组休眠开始时间、组休眠时长、休眠周期、组唤醒时长等参数的具体值，以及确定上述参数的具体值的依据等，本申请不做限定。
作为一种示例，主节点也可以根据端节点的检测周期、报文转发路径长度、信道状况、MAC参数(如传输模式、传输调制阶数、重传次数、传输带宽等等)、分组业务信息，如业务优先级、带宽、时延以及报文大小等一个或多个业务参数，确定分组的休眠调度策略对应的参数的具体值。
示例性地，组唤醒时长可能与报文大小、报文转发路径长度和信道状况有关。组休眠周期可能与端节点(如)的检测周期有关。例如，若组内包括传感器(如触摸传感器、温度传感器、接近光传感器、压力传感器、磁传感器、气压传感器、距离传感器、指纹传感器、环境光传感器、烟雾传感器等)，则主节点可以将该组内端节点的休眠周期设置为传感器的检测周期(如100ms)。
例如，假设玄关传感器和玄关射灯为组A中的成员，当玄关传感器感知到预设范围内有人移动时，向玄关射灯发送信息以通知玄关射灯点亮。类似地，床头传感器和卧室照明灯为组B中的成员，当床头传感器感知到预设范围内有人移动时，向卧室照明灯发送信息以通知卧室照明灯点亮。其中，玄关传感器和床头传感器的检测周期是100ms。主节点确定的组A和组B的组休眠周期为100ms，唤醒时长为10ms，休眠时长为90ms。
又如，假设玄关传感器和玄关射灯为组A中的成员，当玄关传感器感知到预设范围内有人移动时，向玄关射灯发送信息以通知玄关射灯点亮。场景面板和场景受控设备为组B中的成员，当场景面板检测到触发动作时，向场景受控设备发送信息以通知场景受控设备执行相应动作。其中，玄关传感器的检测周期是100ms。场景控制业务的时延需求是20ms。主节点确定的组A的组休眠周期为100ms，唤醒时长为10ms，休眠时长为90ms。但是，由于组B中场景面板是主控设备，对用户时延很敏感，因此主节点确定的组B的组休眠周期为20ms，唤醒时长为10ms，休眠时长为10ms。
S904：主节点向端节点发送组休眠调度信息。
可以理解，在本申请实施例中，由于同一分组内的多个成员采用相同的休眠调度策略，因此主节点可以将组休眠调度信息发送给对应分组内的多个端节点，以便该分组内的多个端节点可以根据该组休眠调度信息同时进入休眠状态以及同时离开休眠状态。
作为一种示例，主节点可以通过广播管理帧(如beacon帧)的形式将组休眠调度信息发送至端节点。其中，beacon帧中包括多个beacon参数，该多个beacon参数用于表示组休眠调度信息。关于主节点向端节点发送组休眠调度信息的具体方式，本申请不做限定。
其中，组休眠调度信息可以用于表征但不限于组标识(ID)、组业务类型、组业务名称、组休眠策略、组休眠类型、组休眠开始时间、组休眠时长、组唤醒时长等中的一个或多个。组ID用于唯一标识主节点根据业务关联信息确定的端节点所在的分组、该分组所对应的业务或者该分组所对应的场景中的一个或多个等。
需要说明的是，本申请实施例不限定组休眠调度信息中各个参数的具体表现形式。
作为一种示例，组休眠调度信息可以以组休眠策略为粒度表征多个组，以及多个组的组业务类型、组业务名称、组休眠类型、组休眠开始时间、组休眠时长、组唤醒时长等参数。例如，组休眠调度信息可以包括组休眠类型为L1类型休眠、L2类型长休眠和L3类型长休眠的组，其中每一个组内包括对应休眠类型的组ID以及组业务类型、组业务名称、组休眠类型、组休眠开始时间、组休眠时长、组唤醒时长等参数。
作为另一种示例，组休眠调度信息可以以分组为粒度表征分组对应的组ID以及组业务类型、组业务名称、组休眠策略、组休眠类型、组休眠开始时间、组休眠时长、组唤醒时长等参数。
在一些实施例中，组休眠调度信息中可以包括组ID和组休眠策略。其中，组休眠策略如L3类型长休眠。
在另一些实施例中，组休眠调度信息中可以包括组ID和组休眠策略和短休眠位图。例如，对于组休眠策略为短休眠(如L1类型休眠)的情况，组休眠调度信息中可以包括组ID和组休眠策略和短休眠位图。在另一些实施例中，组休眠调度信息中可以包括组ID、组休眠策略、组休眠类型、组休眠开始时间和组休眠时长。例如，对于组休眠策略为L2类型长休眠，组休眠类型为调度一次的情况，组休眠调度信息中可以包括组休眠开始时间和组休眠时长。其中，组休眠开始时间用于表示组内多个成员进入休眠状态的时刻。组休眠时长用于表示组内多个成员连续处于休眠状态的时长。
在另一些实施例中，组休眠调度信息中可以包括组ID、组休眠策略、组休眠类型、组休眠开始时间、组休眠时长和休眠周期。例如，对于组休眠策略为L2类型长休眠，组休眠类型为周期调度直到修改的情况，组休眠调度信息中可以包括组休眠开始时间、组休眠时长和休眠周期。其中，休眠周期用于表示组内多个成员进入休眠状态的周期。
在另一些实施例中，组休眠调度信息中可以包括组ID、组休眠策略、组休眠类型、组休眠开始时间、组休眠时长和组唤醒时长。例如，对于组休眠策略为L2类型长休眠，组休眠类型为周期调度直到修改的情况，组休眠调度信息中可以包括组休眠开始时间、组休眠时长和组唤醒时长。其中，组唤醒时长用于表示组内多个成员连续处于唤醒状态的时长。
S905：端节点根据组休眠调度信息触发休眠唤醒机制。
示例性地，端节点可以在确定组休眠调度信息中包括的组ID为端节点所在分组的ID时，根据组休眠调度信息触发休眠唤醒机制。对应的，若端节点确定组休眠调度信息中包括的组ID不是端节点所在分组的ID时，端节点忽略该组休眠调度信息，保持当前状态不变。
需要说明的是，在本申请实施例中，若一个端节点同时位于多个分组中。端节点可以在多个分组对应的休眠调度信息均表征该端节点可以进入休眠状态时，进入休眠状态。换句话说，若一个端节点所在的任意一个分组对应的休眠调度信息表征该端节点需要处于唤醒状态，该端节点则不能进入休眠状态。通过该方法，可以保证业务的正常进行。
在一些实施例中，端节点根据组休眠调度信息触发休眠唤醒机制具体可以包括：端节点根据组休眠调度信息进入(如在接收到组休眠调度信息后立即进入)L3类型休眠状态，直至自行唤醒或者被唤醒。
例如，假设组休眠调度信息包括组休眠策略，且组休眠策略为L3类型长休眠，则端节点根据组休眠调度信息进入L3类型休眠状态，直至自行唤醒或者被唤醒。
关于处于L3类型休眠状态的端节点自行唤醒或者被唤醒的具体介绍，可以参考上文中的说明。
在另一些实施例中，端节点根据组休眠调度信息触发休眠唤醒机制具体可以包括：端节点在下一个MAC周期根据组休眠调度信息休眠或唤醒。
例如，假设组休眠调度信息包括组休眠策略和短休眠位图，其中组休眠策略为LI类型休眠，短休眠位图为0001 0000 0000 0000，则端节点在下一个MAC周期，根据组休眠调度信息中的短休眠位图在第四个时间片对应的时间段唤醒，在其它时间片对应的时间段休眠。
在另一些实施例中，端节点根据组休眠调度信息触发休眠唤醒机制具体可以包括：端节点根据组休眠调度信息在指定时刻进入休眠状态，如L2类型休眠状态，直至满足指定休眠时长。
例如，假设组休眠调度信息包括组休眠策略、组休眠类型、组休眠开始时间和组休眠时长。其中，组休眠策略为L2类型长休眠，长休眠组休眠类型为调度一次，组休眠开始时间为t1，组休眠时长为指定时长k1，则端节点根据组休眠调度信息在指定时刻t1进入L2类型长休眠状态，直至满足指定休眠时长k1。其中，该指定时刻可以表示收到组休眠调度信息后立即开始，也可以表示其它时刻，本申请实施例不做限定。
在另一些实施例中，端节点根据组休眠调度信息触发休眠唤醒机制具体可以包括：端节点根据组休眠调度信息在指定时刻进入休眠状态，如L2类型休眠状态，并在满足指定休眠时长时离开休眠状态、进入唤醒状态，直至满足指定唤醒时长。
例如，假设组休眠调度信息包括组休眠策略、组休眠类型、组休眠开始时间、组休眠时长和组唤醒时长。其中，组休眠策略为L2类型长休眠，长休眠组休眠类型为周期调度直到修改，组休眠开始时间为t1，组休眠时长为指定时长k1，组唤醒时长为指定时长k2，则端节点根据组休眠调度信息在指定时刻t1进入L2类型长休眠状态，并在满足指定休眠时长k1时离开休眠状态、进入唤醒状态，直至满足指定唤醒时长k2。其中，该指定时刻可以表示收到组休眠调度信息后立即开始，也可以表示其它时刻，本申请实施例不做限定。
在另一些实施例中，端节点根据组休眠调度信息触发休眠唤醒机制具体可以包括：端节点根据组休眠调度信息在指定时刻(如t1)进入休眠状态，如L2类型休眠状态，并在满足指定休眠时长(如k1)时离开休眠状态、进入唤醒状态，直至满足指定休眠周期T时再次进入休眠状态。
例如，假设组休眠调度信息包括组休眠策略、组休眠类型、组休眠开始时间、组休眠时长和休眠周期。其中，组休眠策略为L2类型长休眠，长休眠组休眠类型为周期调度直到修改，组休眠开始时间为t1，组休眠时长为指定时长k1，休眠周期为指定时长T(如100ms)，则端节点根据组休眠调度信息在指定时刻t1进入L2类型长休眠状态，并在满足指定休眠时长k1时离开休眠状态、进入唤醒状态，直至满足指定休眠周期T时再次进入休眠状态。其中，该指定时刻可以表示收到组休眠调度信息后立即开始，也可以表示其它时刻，本申请实施例不做限定。
需要说明的是，在本申请实施例中，同一分组内的多个成员采用相同的休眠调度策略。即，同一分组内的多个成员“同醒同睡”。例如，当组休眠策略为L3类型长休眠时，该组内的所有端节点进入L3类型休眠状态，直至同时唤醒。例如在一个端节点被唤醒时，其它端节点同步离开休眠状态。又如在一个端节点自行唤醒时，其它端节点同步离开休眠状态。
可以理解，基于本申请实施例提供的基于PLC的节点调度方法，不仅可以利用已经广泛部署的电力线作为传输媒介，降低前期部署成本和后期维护成本，避免周边环境(如电磁干扰等)因素对通信的影响，还可以通过根据业务关联情况对多个端节点进行分组，以及根据组业务相关信息(如业务QoS)合理确定休眠调度策略，如组休眠策略、组休眠类型、组休眠开始时间、组休眠时长、休眠周期、组唤醒时长等参数， 从而可以在保证PLC通信业务需求的同时，让电力线通信系统中各个节点充分休眠，以降低各个节点的功耗。
另外，基于本申请实施例提供的基于PLC的节点调度方法，不同分组内的成员用于不同的业务，因此在时隙上可以相互交叠。这样也可以降低因竞争带来的丢包。
进一步的，在一些实施例中，若一个分组内的某一端节点的业务发生变更，该端节点还可以向主节点更新业务信息，以便主节点及时更新该端节点的分组业务信息。
示例性的，请参考图14，本申请实施例提供的基于PLC的节点调度方法还可以包括以下S1401-S1402：
S1401：端节点在业务发生变更时，向主节点更新业务信息。
作为一种可能的实现方式，端节点可以通过管理帧(如beacon帧)向主节点更新业务信息。
其中，本申请不限定端节点业务发生变更的具体原因。示例性地，端节点业务发生变更可能是由于端节点拓扑结构发生改变、端节点配置发生改变、用户需求发生改变、业务需求发生改变等。
例如，在端节点上电时，为了保证端节点上电时的通信需求，其带宽需求通常较大，因此带宽通常设置的较大；但是，当端节点成功上电并稳定工作时，为了避免带宽资源的浪费，其带宽设置通常会降低等级，如会降低带宽设置。基于此，在端节点成功上电之后，其业务发生变更。在端节点的业务发生变更时，端节点向主节点更新其业务信息，以便主节点及时更新该端节点的分组业务信息。进一步的，主节点可以在有需求时，根据更新后的业务信息重新决策休眠调度策略。
S1402：主节点更新分组业务信息。
可选的，主节点可以在有需求时，根据更新后的业务信息重新决策休眠调度策略。即如图14所示，本申请实施例提供的基于PLC的节点调度方法还可以包括以下S1403-S1405：
S1403：主节点根据更新后的分组业务信息重新确定该分组的休眠调度策略。或者，主节点根据可用资源信息和更新后的分组业务信息重新确定该分组的休眠调度策略。
其中，更新后的分组业务信息可以包括但不限于更新后的分组内各个端节点的业务QoS等。更新后的业务QoS可以包括但不限于业务优先级、带宽、时延以及报文大小等业务参数。
作为一种可能的实现方式，主节点可以根据更新后的分组业务信息直接重新确定分组的休眠调度策略。
作为另一种可能的实现方式，主节点可以结合可用资源信息和更新后的分组业务信息重新确定分组的休眠调度策略。
在一些实施例中，主节点还可以根据可用资源信息和更新后的分组业务信息，结合其它相关信息，如网络拓扑结构、分组优先级、设备优先级、检测周期、报文转发路径长度和信道状况等中的一个或多个，重新确定分组的休眠调度策略。
关于主节点确定休眠调度策略的具体过程和方法，可以参考上述实施例中的介绍。
S1404：主节点向端节点发送组休眠调度信息。
其中，主节点向端节点发送的该组休眠调度信息与主节点在S1403重新确定的休眠调度策略相关。
由于同一分组内的多个成员采用相同的休眠调度策略，因此主节点可以将组休眠调度信息发送给对应分组内的多个端节点，以便该分组内的多个端节点可以根据该组休眠调度信息同时进入休眠状态以及同时离开休眠状态。
在一些实施例中，组休眠调度信息中可以包括组ID和组休眠策略。其中，组休眠策略如L3类型长休眠。
在另一些实施例中，组休眠调度信息中可以包括组ID和组休眠策略和短休眠位图。其中，组休眠策略为短休眠(如L1类型休眠)。
在另一些实施例中，组休眠调度信息中可以包括组ID、组休眠策略、组休眠类型、组休眠开始时间和组休眠时长。其中，组休眠策略如L2类型长休眠。组休眠类型如调度一次。
在另一些实施例中，组休眠调度信息中可以包括组ID、组休眠策略、组休眠类型、组休眠开始时间、组休眠时长和休眠周期。其中，组休眠策略如L2类型长休眠，组休眠类型如周期调度直到修改。
在另一些实施例中，组休眠调度信息中可以包括组ID、组休眠策略、组休眠类型、组休眠开始时间、组休眠时长和组唤醒时长。其中，组休眠策略如L2类型长休眠，组休眠类型如周期调度直到修改。
作为一种示例，主节点可以通过广播管理帧(如beacon帧)的形式将组休眠调度信息发送至端节点。
关于组休眠调度信息中所包括的具体信息，可以参考上述实施例中的介绍。
S1405：端节点根据最新接收到的组休眠调度信息触发休眠唤醒机制。
示例性地，端节点可以在确定组休眠调度信息中包括的组ID为端节点所在分组的ID时，根据组休眠调度信息触发休眠唤醒机制。对应的，若端节点确定组休眠调度信息中包括的组ID不是端节点所在分组的ID时，端节点忽略该组休眠调度信息，保持当前状态不变。
关于端节点根据组休眠调度信息触发休眠唤醒机制的具体过程和可能的情况，可以参考上述实施例中的介绍。
可以理解，基于本申请实施例提供的基于PLC的节点调度方法，端节点可以在业务发生变更时，及时通知主节点，便于主节点可以及时更新该端节点的分组业务信息，以便主节点可以在有需求时，根据更新后的业务信息重新决策休眠调度策略。该方法可以避免由于主节点没有及时更新分组业务信息导致的后续决策休眠调度策略时确定的休眠调度策略不合理造成的对端节点业务的影响，或者没有使端节点充分休眠导致的端节点功耗大的问题。
进一步的，在一些实施例中，若主节点确定分组发生变更，主节点还可以向端节点发送分组变更信息，以便端节点及时更新分组信息。
示例性的，请参考图15，本申请实施例提供的基于PLC的节点调度方法还可以包括以下S1501-S1503：
S1501：主节点确定分组发生变更。
其中，本申请实施例不限定分组发生变更的具体原因和具体情况。示例性地，分组发生变更可能是由于网络中的节点组发生变更或者网络拓扑结构发生变更造成的。
S1502：主节点向端节点发送分组变更信息。
其中，分组变更信息可以用于表征变更后的分组ID和分组内成员的ID。
作为一种示例，主节点可以通过广播管理帧(如beacon帧)的形式将分组变更信息发送至端节点。
S1503：端节点根据分组变更信息更新端节点的分组信息。
可以理解，基于本申请实施例提供的基于PLC的节点调度方法，主节点可以在分组发生变更时，如网络中的节点组发生变更或者网络拓扑结构发生变更时，及时通知端节点，以便端节点及时更新分组信息。该方法可以避免由于主节点侧与端节点侧分组信息不同步导致的休眠调度策略决策不合理造成的对端节点业务的影响，或者没有使端节点充分休眠导致的端节点功耗大的问题。
在一些实施例中，主节点可以基于节点拓扑信息进行端节点的休眠调度决策。
如图16所示，本申请实施例提供的基于PLC的节点调度方法可以包括以下S1601-S1605：
S1601：主节点获取节点拓扑信息。
其中，节点拓扑信息用于表征多个端节点间是否能够相互感知。相互感知是指端节点之间均能够接收到来自对方的信号。在本申请实施例中，节点拓扑信息用于主节点判断多个端节点间传输过程当中是否会相互干扰。
在一些实施例中，端节点间相互干扰是指多个端节点在发包过程当中数据报文发生碰撞。或者，端节点间相互干扰是指通过不同频段进行数据传输的端节点间由于传输过程中邻频能量泄漏导致的数据报文不能被正确接收。
如图17A所示，发送端1向接收端1发送信息，发送端2向接收端2发送信息。若发送端1和发送端2同时接入信道进行传输，由于数据报文发生碰撞，可能会导致相互间的碰撞丢包。例如，发送端1发送至接收端1的数据包会由于与发送端2发出的数据包发生碰撞丢包。同样地，发送端2发送至接收端2的数据包会由于与发送端1发出的数据包发生碰撞丢包。对于这种情况，我们可以认为发送端1和发送端2相互干扰。
在本申请实施例中，主节点可以从端节点获取节点拓扑信息。例如，端节点可以主动向主节点上报节点拓扑信息。又如，主节点可以向端节点主动查询(如周期性查询)节点拓扑信息。
作为一种示例，端节点可以在处理特定事件的过程中记录该端节点的拓扑信息。示例性地，特定事件为端节点接入PLC网络。基于此，端节点可以将其记录的拓扑信息发送给主节点。
作为另一种示例，端节点可以在进行PLC管理的过程中记录该端节点的拓扑信息。示例性地，端节点可以在路由的过程中记录可以表征节点拓扑结构的转发表(如ATT表)。基于此，端节点可以将其记录的可以表征节点拓扑结构的转发表(如ATT表)发送给主节点。
S1602：主节点根据节点拓扑信息确定端节点的分组信息。
其中，端节点的分组信息可以用于表征但不限于该分组内成员的ID。
其中，在本申请实施例中，同一分组内的多个端节点之间相互不干扰。例如，同一分组内的多个端节点接收不到彼此的信号。
示例性地，如图17A所示，若发送端1和发送端1同时接入信道进行传输，由于数据报文发生碰撞，可能会导致相互间的碰撞丢包。即，发送端1和发送端2相互干扰。对于这种情况，为了避免后续相互干扰的端节点在发包时产生碰撞，主节点可以将发送端1和发送端2分至不同的分组。进一步的，由于发送端1和接收端1业务相关，发送端2和接收端2业务相关，因此主节点可以将发送端1和接收端1归为一个分组，将发送端2和接收端2归为另一个分组。如图17B所示，发送端1和接收端1位于组A中，发送端2和接收端2位于组B中。
又如图17C所示，端节点1与端节点5、端节点2与端节点5、端节点1与主节点之间是直接连接关系。端节点1与主节点、端节点2与主节点是通过电力线和其它端节点间接连接的关系。端节点1与端节点2是与同一端节点分别连接的关系。假设各个端节点之间业务无关，端节点1与端节点2相互干扰，端节点2与端节点3相互干扰，端节点3与端节点4相互干扰。对于这种情况，由于相互干扰的节点同时接入信道进行传输可能会导致相互间的碰撞丢包，因此为了避免后续相互干扰的端节点在发包时产生碰撞，主节点可以将端节点1和端节点3分为一组，如组A；以及将端节点2和端节点4分为一组，如组B。
在一些实施例中，同一端节点可以同时位于多个分组中。其中，该端节点与多个分组内的端节点均不相互干扰。
关于端节点的分组信息的具体介绍，可以参考上文实施例中的介绍。
S1603：主节点根据分组业务信息确定该分组的休眠调度策略。或者，主节点根据可用资源信息和分组业务信息确定该分组的休眠调度策略。
其中，分组业务信息可以包括但不限于分组内各个端节点的业务QoS等。业务QoS可以包括但不限于业务优先级、带宽、时延以及报文大小等业务参数。
作为一种可能的实现方式，主节点可以从端节点获取分组业务信息。
作为另一种可能的实现方式，主节点可以根据电力线部署拓扑结构(如端节点之间的感知情况，端节点之间的连接关系等)确定分组业务信息。
关于主节点获取分组业务信息的具体渠道，本申请不做具体限定。
在一些实施例中，休眠调度策略可以用于表征：组休眠策略。其中，组休眠策略如短休眠、长休眠(如L2类型长休眠或者L3类型长休眠)等。
在另一些实施例中，休眠调度策略既可以用于表征组休眠策略，还可以用于表征组休眠类型和短休眠位图。其中，组休眠策略如短休眠(如L1类型休眠)，组休眠类型如调度一次或者周期调度直到修改。
在另一些实施例中，休眠调度策略既可以用于表征组休眠策略，还可以用于表征组休眠类型、组休眠开始时间和组休眠时长。其中，组休眠类型如调度一次。
在另一些实施例中，休眠调度策略既可以用于表征组休眠策略、组休眠类型、组休眠开始时间和组休眠时长，还可以用于表征休眠周期。其中，组休眠类型如周期调度直到修改。
在另一些实施例中，休眠调度策略既可以用于表征组休眠策略、组休眠类型、组休眠开始时间和组休眠时长，还可以用于表征组唤醒时长。其中，组休眠类型如周期调度直到修改。
作为一种可能的实现方式，主节点可以结合可用资源信息和分组业务信息综合确定分组的休眠调度策略。
作为另一种可能的实现方式，主节点可以根据分组业务信息直接确定分组的休眠调度策略。
在一些实施例中，主节点还可以根据可用资源信息和分组业务信息，结合其它相关信息，如网络拓扑结构、分组优先级、设备优先级、检测周期、报文转发路径长度和信道状况等中的一个或多个，综合确定分组的休眠调度策略。
需要说明的是，主节点在确定休眠调度策略时，具体如何确定组休眠策略、组休眠类型、组休眠开始时间、组休眠时长、休眠周期、组唤醒时长等参数的具体值，以及确定上述参数的具体值的依据等，本申请不做限定。
以图17C所示分组为例，假设该组网场景的MAC周期为160ms各个端节点的时延需求均为20ms。对于这种情况，主节点可以将一个MAC周期划分为16个时隙，其中组A和组B分别占用其中不交叠的8个时隙，以避免组内的端节点在发包时产生碰撞。例如，组A的休眠唤醒时隙位图为0b1010101010101010，组B的休眠唤醒时隙位图为0b0101010101010101。可选的，主节点也可以根据实际业务情形和网络信道状况配置时隙粒度和分配给各个组的时隙位置。
关于主节点确定休眠调度策略的具体过程和方法，可以参考上述实施例中的介绍。
S1604：主节点向端节点发送组休眠调度信息。
其中，主节点向端节点发送的该组休眠调度信息与主节点在S1603确定的休眠调度策略相关。
由于同一分组内的多个成员采用相同的休眠调度策略，因此主节点可以将组休眠调度信息发送给对应分组内的多个端节点，以便该分组内的多个端节点可以根据该组休眠调度信息同时进入休眠状态以及同时离开休眠状态。
需要说明的是，本申请实施例不限定组休眠调度信息中各个参数的具体表现形式。
作为一种示例，组休眠调度信息可以以组休眠策略为粒度表征多个组，以及多个组的组业务类型、组业务名称、组休眠类型、组休眠开始时间、组休眠时长、组唤醒时长等参数。
作为另一种示例，组休眠调度信息可以以分组为粒度表征分组对应的组ID以及组业务类型、组业务名称、组休眠策略、组类型、组休眠开始时间、组休眠时长、组唤醒时长等参数。
在一些实施例中，组休眠调度信息中可以包括组ID和组休眠策略。其中，组休眠策略如L3类型长休眠。
在另一些实施例中，组休眠调度信息中可以包括组ID和组休眠策略和短休眠位图。例如，对于组休眠策略为短休眠(如L1类型休眠)的情况，组休眠调度信息中可以包括组ID和组休眠策略和短休眠位图。
在另一些实施例中，组休眠调度信息中可以包括组ID、组休眠策略、组休眠类型、组休眠开始时间和组休眠时长。例如，对于组休眠策略如L2类型长休眠，组休眠类型为调度一次的情况，组休眠调度信息中可以包括组休眠开始时间和组休眠时长。
在另一些实施例中，组休眠调度信息中可以包括组ID、组休眠策略、组休眠类型、组休眠开始时间、组休眠时长和休眠周期。例如，对于组休眠策略为L2类型长休眠，组休眠类型为周期调度直到修改的情况，组休眠调度信息中可以包括组休眠开始时间、组休眠时长和休眠周期。
在另一些实施例中，组休眠调度信息中可以包括组ID、组休眠策略、组休眠类型、组休眠开始时间、组休眠时长和组唤醒时长。例如，对于组休眠策略为L2类型长休眠，组休眠类型为周期调度直到修改的情况，组休眠调度信息中可以包括组休眠开始时间、组休眠时长和组唤醒时长。
作为一种示例，主节点可以通过广播管理帧(如beacon帧)的形式将组休眠调度信息发送至端节点。
关于组休眠调度信息中所包括的具体信息，可以参考上述实施例中的介绍。
S1605：端节点根据组休眠调度信息触发休眠唤醒机制。
示例性地，端节点可以在确定组休眠调度信息中包括的组ID为端节点所在分组的ID时，根据组休眠调度信息触发休眠唤醒机制。对应的，若端节点确定组休眠调度信息中包括的组ID不是端节点所在分组的ID时，端节点忽略该组休眠调度信息，保持当前状态不变。
需要说明的是，在本申请实施例中，若一个端节点同时位于多个分组中。端节点可以在多个分组对应的休眠调度信息均表征该端节点可以进入休眠状态时，进入休眠状态。换句话说，若一个端节点所在的任意一个分组对应的休眠调度信息表征该端节点需要处于唤醒状态，该端节点则不能进入休眠状态。通过该方法，可以保证业务的正常进行。
关于端节点根据组休眠调度信息触发休眠唤醒机制的具体过程和可能的情况，可以参考上述实施例中的介绍。
可以理解，基于本申请实施例提供的基于PLC的节点调度方法，不仅可以利用已经广泛部署的电力线作为传输媒介，降低前期部署成本和后期维护成本，避免周边环境(如电磁干扰等)因素对通信的影响，还可以通过根据节点拓扑信息对多个端节点进行分组，以及根据组业务相关信息(如业务QoS)合理确定休眠调度策略，如组休眠策略、组休眠类型、组休眠开始时间、组休眠时长、休眠周期、组唤醒时长等参数，从而可以在保证PLC通信业务需求的同时，让电力线通信系统中各个节点充分休眠，以降低各个节点的功耗。
另外，基于本申请实施例提供的基于PLC的节点调度方法，不同分组内的成员用于不同的业务，因此在时隙上可以相互交叠。这样也可以降低因竞争带来的丢包。
进一步的，在一些实施例中，若主节点确定分组发生变更，主节点还可以向端节点发送分组变更信息，以便端节点及时更新分组信息。
示例性的，请参考图18，本申请实施例提供的基于PLC的节点调度方法还可以包括以下S1801-S1803：
S1801：主节点确定分组发生变更。
其中，本申请实施例不限定分组发生变更的具体原因和具体情况。示例性地，分组发生变更可能是由于网络中的节点组发生变更，网络拓扑结构发生变更，或者端节点间的感知情况发生变化造成的。
S1802：主节点向端节点发送分组变更信息。
其中，分组变更信息可以用于表征变更后的分组ID和分组内成员的ID。
作为一种示例，主节点可以通过广播管理帧(如beacon帧)的形式将分组变更信息发送至端节点。
S1803：端节点根据分组变更信息更新端节点的分组信息。
可以理解，基于本申请实施例提供的基于PLC的节点调度方法，主节点可以在分组发生变更时，如网络中的节点组发生变更或者网络拓扑结构发生变更时，及时通知端节点，以便端节点及时更新分组信息。该方法可以避免由于主节点侧与端节点侧分组信息不同步导致的休眠调度策略决策不合理造成的对端节点业务的影响，或者没有使端节点充分休眠导致的端节点功耗大的问题。
可选的，在一些实施例中，主节点也可以在确定分组信息时，综合考虑业务关联信息和节点拓扑信息。基于此，主节点可以通过综合考虑业务关联信息和节点拓扑信息对多个端节点进行分组，以及根据组业务相关信息(如业务QoS)合理确定休眠调度策略，如组休眠策略、组休眠类型、组休眠开始时间、组休眠时长、休眠周期、组唤醒时长等参数，从而可以在保证PLC通信业务需求的同时，让电力线通信系统中各个节点充分休眠，以降低各个节点的功耗。
应理解，本申请实施例的各个方案可以进行合理的组合使用，并且实施例中出现的各个术语的解释或说明可以在各个实施例中互相参考或解释，对此不作限定。
还应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
可以理解的是，通信节点(如主节点或端节点)为了实现上述任一个实施例的功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以对通信节点(如主节点或端节点)进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
应理解，通信节点(如主节点或端节点)中的各个模块可以通过软件和/或硬件形式实现，对此不作具体限定。换言之，智能跳绳/电子设备是以功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路ASIC、电路、执行一个或多个软件或固件程序的处理器和存储器、集成逻辑电路，和/或其它可以提供上述功能的器件。
在一种可选的方式中，当使用软件实现数据传输时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地实现本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其它可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线((digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如软盘、硬盘、磁带)、光介质(例如数字化视频光盘(digital video disk，DVD))、或者半导体介质(例如固态硬盘solid state disk(SSD))等。
结合本申请实施例所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性地存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于电子设备中。当然，处理器和存储介质也可以作为分立组件存在于通信节点(如主节点或端节点)中。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。

Claims (38)

  1. 一种基于PLC的节点调度方法，其特征在于，所述方法应用于PLC系统中，所述PLC系统包括第一节点和多个第二节点，所述多个第二节点分别属于多个分组，所述方法包括：
    所述第一节点确定第三节点所在分组为第一分组，所述第三节点属于所述多个第二节点，所述第三节点与所述第一节点通过电力线连接；
    所述第一节点获取所述第一分组的分组业务信息，所述分组业务信息用于表征以下中的一个或多个：所述第一分组对应业务的业务优先级、带宽、时延、报文大小；
    所述第一节点根据所述分组业务信息向所述第三节点发送组休眠调度信息，所述组休眠调度信息包括组休眠策略，所述组休眠调度信息用于所述第三节点触发对应的休眠唤醒机制。
  2. 根据权利要求1所述的方法，其特征在于，所述第一分组内的节点具有业务关联关系。
  3. 根据权利要求2所述的方法，其特征在于，所述第一分组内的节点之间的业务关联关系包括以下中的一种或多种：控制关系、同步关系。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述第一节点确定所述第三节点所在分组为所述第一分组，包括：
    所述第一节点获取所述多个第二节点的业务关联信息，所述业务关联信息用于表征所述多个第二节点之间的业务关联关系；
    所述第一节点根据所述多个第二节点的业务关联信息确定所述多个第二节点所在的分组，所述多个第二节点所在的分组包括所述第三节点所在的所述第一分组。
  5. 根据权利要求4所述的方法，其特征在于，
    所述第一节点根据以下中的一种或多种获取所述多个第二节点的业务关联信息：用户的设置或操作、第二节点上报的信息、地址关联表ATT。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述第一分组内的节点相互不干扰。
  7. 根据权利要求6所述的方法，其特征在于，所述第一节点确定所述第三节点所在分组为所述第一分组，包括：
    所述第一节点获取所述多个第二节点的节点拓扑信息，所述节点拓扑信息用于表征所述多个第二节点之间是否相互干扰；
    所述第一节点根据多个第二节点的节点拓扑信息确定所述第一分组。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，所述组休眠策略为L1类型休眠，所述组休眠调度信息还包括组休眠类型和短休眠位图；其中，所述组休眠类型包括调度一次或者周期调度直到修改。
  9. 根据权利要求1-7中任一项所述的方法，其特征在于，所述组休眠策略为L3类型长休眠。
  10. 根据权利要求1-7中任一项所述的方法，其特征在于，所述组休眠策略为L2类型长休眠，所述组休眠调度信息还包括组休眠类型、组休眠开始时间和组休眠时长；其中，所述组休眠类型包括调度一次或者周期调度直到修改。
  11. 根据权利要求10所述的方法，其特征在于，所述组休眠类型为周期调度直到修改，所述组休眠调度信息还包括休眠周期或组唤醒时长。
  12. 根据权利要求1-11中任一项所述的方法，其特征在于，所述第一节点根据所述分组业务信息向所述第三节点发送组休眠调度信息，包括：
    所述第一节点根据所述分组业务信息，基于当前可用资源信息向所述第三节点发送组休眠调度信息。
  13. 根据权利要求1-12中任一项所述的方法，其特征在于，所述第一节点根据所述分组业务信息向所述第三节点发送组休眠调度信息，包括：
    所述第一节点根据所述分组业务信息向包括所述第三节点的所述多个第二节点广播所述组休眠调度信息。
  14. 根据权利要求1-13中任一项所述的方法，其特征在于，所述第一节点获取所述第一分组的分组业务信息，包括：
    所述第一节点通过以下一种或多种方式获取所述第一分组的分组业务信息：从所述多个第二节点中的一个或多个获取、根据电力线部署拓扑结构确定。
  15. 根据权利要求1-14中任一项所述的方法，其特征在于，
    所述第三节点与所述第一节点通过电力线直接连接；或者，
    所述第三节点通过第四节点与所述第一节点间接连接，所述第三节点与所述第四节点之间通过电力线连接，所述第四节点与所述第一节点之间通过电力线连接，所述第四节点属于所述多个第二节点。
  16. 根据权利要求15所述的方法，其特征在于，所述第四节点属于或不属于所述第一分组。
  17. 根据权利要求15或16所述的方法，其特征在于，所述第四节点与所述第一节点之间的电力线距离大于所述第三节点与所述第一节点之间的电力线距离。
  18. 根据权利要求1-17中任一项所述的方法，其特征在于，所述第三节点还属于第二分组，所述第二分组对应的组休眠调度信息与所述第一分组所对应的组休眠调度信息不冲突。
  19. 一种基于PLC的节点调度方法，其特征在于，所述方法应用于PLC系统中，所述PLC系统包括第一节点和多个第二节点，所述多个第二节点分别属于多个分组，所述多个第二节点中包括属于第一分组的第三节点，所述第三节点与所述第一节点通过电力线连接，所述方法包括：
    所述第三节点接收来自所述第一节点的组休眠调度信息，所述组休眠调度信息包括组休眠策略，所述组休眠调度信息用于所述第三节点触发对应的休眠唤醒机制；
    所述第三节点根据所述组休眠调度信息与所述第一分组内的其它节点同步触发对应的休眠唤醒机制。
  20. 根据权利要求19所述的方法，其特征在于，所述第一分组内的节点具有业务关联关系。
  21. 根据权利要求20所述的方法，其特征在于，所述第一分组内的节点之间的业务关联关系包括以下中的一种或多种：控制关系、同步关系。
  22. 根据权利要求19-21中任一项所述的方法，其特征在于，所述第一分组内的节点相互不干扰。
  23. 根据权利要求19-22中任一项所述的方法，其特征在于，所述组休眠策略为L1类型休眠，所述组休眠调度信息还包括组休眠类型和短休眠位图，所述组休眠类型为调度一次；所述第三节点根据所述组休眠调度信息与所述第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：
    所述第三节点根据所述短休眠位图，在下一个MAC周期唤醒时间片对应的时刻唤醒，在休眠时间片对应的时刻休眠。
  24. 根据权利要求19-22中任一项所述的方法，其特征在于，所述组休眠策略为L1类型休眠，所述组休眠调度信息还包括组休眠类型和短休眠位图，所述组休眠类型为周期调度直到修改；所述第三节点根据所述组休眠调度信息与所述第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：
    所述第三节点根据所述短休眠位图，在后面每一个MAC周期唤醒时间片对应的时刻唤醒，在休眠时间片对应的时刻休眠。
  25. 根据权利要求19-22中任一项所述的方法，其特征在于，所述组休眠策略为L3类型长休眠，所述第三节点根据所述组休眠调度信息与所述第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：
    所述第三节点根据所述组休眠策略进入休眠状态，直至自行唤醒或者被唤醒。
  26. 根据权利要求19-22中任一项所述的方法，其特征在于，所述组休眠策略为L2类型长休眠，所述组休眠调度信息还包括组休眠类型、组休眠开始时间和组休眠时长，所述组休眠类型为调度一次；所述第三节点根据所述组休眠调度信息与所述第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：
    所述第三节点在所述休眠开始时间对应的时刻休眠，直至满足所述组休眠时长后唤醒。
  27. 根据权利要求19-22中任一项所述的方法，其特征在于，所述组休眠策略为L2类型长休眠，所述组休眠调度信息还包括组休眠类型、组休眠开始时间、组休眠时长和休眠周期，所述组休眠类型为周期调度直到修改；所述第三节点根据所述组休眠调度信息与所述第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：
    所述第三节点在所述休眠开始时间对应的时刻进入休眠状态，直至满足所述组休眠时长后唤醒；
    在满足所述休眠周期时，所述第三节点进入休眠状态，直至满足所述组休眠时长后唤醒；
    在再次满足所述休眠周期时，所述第三节点再次进入休眠状态，直至满足所述组休眠时长后唤醒，以此类推。
  28. 根据权利要求19-22中任一项所述的方法，其特征在于，所述组休眠策略为L2类型长休眠，所述组休眠调度信息还包括组休眠类型、组休眠开始时间、组休眠时长和组唤醒时长，所述组休眠类型为周期调度直到修改；所述第三节点根据所述组休眠调度信息与所述第一分组内的其它节点同步触发对应的休眠唤醒机制，包括：
    所述第三节点在所述休眠开始时间对应的时刻进入休眠状态，直至满足所述组休眠时长后唤醒；
    在满足所述组唤醒时长时，所述第三节点进入休眠状态，直至满足所述组休眠时长后唤醒；
    在再次满足所述组唤醒时长时，所述第三节点再次进入休眠状态，直至满足所述组休眠时长后唤醒，以此类推。
  29. 根据权利要求19-28中任一项所述的方法，其特征在于，
    所述第三节点与所述第一节点通过电力线直接连接；或者，
    所述第三节点通过第四节点与所述第一节点间接连接，所述第三节点与所述第四节点之间通过电力线连接，所述第四节点与所述第一节点之间通过电力线连接，所述第四节点属于所述多个第二节点。
  30. 根据权利要求29所述的方法，其特征在于，所述第四节点属于或不属于所述第一分组。
  31. 根据权利要求29或30所述的方法，其特征在于，所述第四节点与所述第一节点之间的电力线距离大于所述第三节点与所述第一节点之间的电力线距离。
  32. 根据权利要求19-31中任一项所述的方法，其特征在于，所述第三节点还属于第二分组，所述第二分组对应的组休眠调度信息与所述第一分组所对应的组休眠调度信息不冲突。
  33. 一种通信节点，其特征在于，所述通信节点包括：
    通信接口，用于进行信号发送与接收；
    存储器，用于存储计算机程序指令；
    处理器，用于执行所述指令，使得所述通信节点执行如权利要求1-18任一项所述的方法。
  34. 一种通信节点，其特征在于，所述通信节点包括：
    通信接口，用于进行信号发送与接收；
    存储器，用于存储计算机程序指令；
    处理器，用于执行所述指令，使得所述通信节点执行如权利要求19-32中任一项所述的方法。
  35. 一种PLC系统，其特征在于，所述PLC系统包括权利要求33所述的通信节点和权利要求34所述的通信节点。
  36. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机执行指令，所述计算机执行指令被处理电路执行时实现如权利要求1-18或19-32中任一项所述的方法。
  37. 一种芯片系统，其特征在于，所述芯片系统包括处理电路、存储介质，所述存储介质中存储有指令；所述指令被所述处理电路执行时，实现如权利要求1-18或19-32中任一项所述的方法。
  38. 一种计算机程序产品，其特征在于，所述计算机程序产品包括程序指令，所述程序指令被执行时，以实现如权利要求1-18或19-32中任一项所述的方法。
PCT/CN2023/095839 2022-05-26 2023-05-23 一种基于plc的节点调度方法、设备及plc系统 WO2023226989A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210590310.8 2022-05-26
CN202210590310.8A CN117176200A (zh) 2022-05-26 2022-05-26 一种基于plc的节点调度方法、设备及plc系统

Publications (2)

Publication Number Publication Date
WO2023226989A1 WO2023226989A1 (zh) 2023-11-30
WO2023226989A9 true WO2023226989A9 (zh) 2024-01-11

Family

ID=88918555

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/095839 WO2023226989A1 (zh) 2022-05-26 2023-05-23 一种基于plc的节点调度方法、设备及plc系统

Country Status (2)

Country Link
CN (1) CN117176200A (zh)
WO (1) WO2023226989A1 (zh)

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070160027A1 (en) * 2005-12-27 2007-07-12 Muqattash Alaa H Dynamic power save modes
CN104950829B (zh) * 2014-03-31 2018-04-27 奇点新源国际技术开发(北京)有限公司 一种总线系统功耗控制方法及装置
CN104703296A (zh) * 2015-03-19 2015-06-10 江苏物联网研究发展中心 无线通信多跳网络链状及树状拓扑结构的链路休眠方法
CN107182027B (zh) * 2017-06-05 2019-12-10 北京交通大学 基于分组的m2m通信非连续传输方法
WO2022067692A1 (zh) * 2020-09-30 2022-04-07 Oppo广东移动通信有限公司 侧行链路的传输方法和终端

Also Published As

Publication number Publication date
WO2023226989A1 (zh) 2023-11-30
CN117176200A (zh) 2023-12-05

Similar Documents

Publication Publication Date Title
US10798548B2 (en) Method for controlling device by using Bluetooth technology, and apparatus
CN106792916B (zh) 一种混合型远距离无线传感器网络系统及其通信方法
US11082851B2 (en) Method and apparatus for processing audio signal by using Bluetooth technology
CN108377531B (zh) 一种数据通信方法及装置
US20170303076A1 (en) Method and apparatus for transmitting or receiving data using bluetooth in wireless communication system
US8626251B2 (en) Audio-visual system energy savings using a mesh network
US20170251469A1 (en) Method for transmitting and receiving audio data in wireless communication system supporting bluetooth communication and device therefor
US9235983B2 (en) Apparatus and methods for group-based reactive service discovery
CN105052209A (zh) 轮询信标
WO2015122576A1 (ko) 무선 통신 시스템에서 블루투스 저전력 에너지를 이용하여 객체 전송 서비스를 수행하기 위한 방법 및 장치
WO2016106730A1 (zh) 主从网络休眠及唤醒的方法、装置及主从网络省电系统
WO2008044885A2 (en) Methods for managing the power in a wireless network
CN110636478A (zh) 蓝牙Mesh网络系统及其通信方法、设备与存储介质
WO2021115193A1 (zh) 一种设备组网方法、电子设备及系统
EP4311314A1 (en) Sleep scheduling method and device
JP2023551375A (ja) 送変電設備のモノのインターネットにおけるノード設備の無線通信方法及びシステム
EP2795957A1 (en) Bandwidth management in a home network
US11706732B2 (en) Method and apparatus for controlling UE for cellular IoT service in 5G mobile communication system
WO2014176979A1 (zh) 无线电唤醒方法和无线电唤醒电路
US11595889B2 (en) Determining a duty schedule for a group of lighting devices providing a similar lighting service
US20230247572A1 (en) Wireless communication method and apparatus, relay device, remote device, and base station
WO2023226989A9 (zh) 一种基于plc的节点调度方法、设备及plc系统
CN106330641B (zh) 一种超低功耗can网络通讯方法
US10772041B2 (en) Beacon signal processing system
US11317347B2 (en) Method and apparatus for providing service by using Bluetooth low energy technology

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23811060

Country of ref document: EP

Kind code of ref document: A1