Method, apparatus, and system for power line communication for internet of things

Abstract

This application relates to methods, apparatus, and systems for power line communication (PLC) for the Internet of Things (IoT). The method includes a transmitting device receiving a first request from a receiving device, the first request requesting channel evaluation to be performed for a first time window within a power line communication cycle; in response to the first request, the transmitting device sending a probe signal to the receiving device required for performing the channel evaluation; the transmitting device receiving modulation parameters from the receiving device, the modulation parameters being determined by performing the channel evaluation based on the probe signal; and the transmitting device transmitting data with the receiving device within the first time window based on the modulation parameters. According to the proposed technical solution, the rate performance and resource utilization efficiency of both broadband services and IoT services in PLC broadband and PLC IoT converged scenarios can be significantly improved with limited increase in complexity.

Description

Technical Field

[0001] This application relates to the field of power line communication (PLC), and in particular to methods, apparatus and systems for power line communication for the Internet of Things (IoT). Background Technology

[0002] PLC (Power Line Communication) refers to the transmission of data or information using digital signal processing methods over power lines. PLC broadband technology uses low-frequency power lines to transmit broadband data. Because it requires virtually no additional network cabling and covers a much wider area than other types of cables, PLC broadband technology has been widely used in various networks, such as home networks and industrial networks. Recently, with the development of IoT (Internet of Things) technology, PLC IoT technology has also been widely applied in applications such as smart grids in industrial networks. PLC IoT technology refers to the use of power lines to achieve communication between IoT nodes. Recently, there have been attempts to apply PLC IoT to smart home applications, making the integration of PLC broadband networks and PLC IoT networks a growing necessity. In this integrated network, PLC broadband communication and PLC IoT communication operate on the same power line network, using the same medium and sharing physical layer transmission resources.

[0003] Typically, in such converged networks, the same medium needs to support several PLC broadband nodes (also referred to as broadband nodes) and hundreds of PLC IoT nodes (also referred to as IoT nodes or narrowband nodes). Although each IoT node has a smaller data traffic, the large number of nodes results in a high overall overhead for IoT applications. Furthermore, the low achievable data rates of IoT technology lead to higher resource consumption, thus limiting the communication resources available to broadband nodes and significantly reducing their achievable data rates. In addition, the bandwidth requirements of IoT nodes are constantly increasing. Therefore, it is desirable to provide improved solutions to enhance the communication performance of both broadband nodes and IoT nodes in such converged networks. Summary of the Invention

[0004] Embodiments of this disclosure provide a power line communication scheme for the Internet of Things (IoT) that can improve the communication performance of nodes in such a converged network.

[0005] According to a first aspect of this disclosure, a method for power line communication for an Internet of Things (IoT) is provided. The method includes: a transmitting device receiving a first request from a receiving device, the first request requesting channel evaluation to be performed for a first time window in a power line communication cycle; in response to the first request, the transmitting device sending a probe signal to the receiving device for performing the channel evaluation; the transmitting device receiving modulation parameters from the receiving device, the modulation parameters being determined by performing the channel evaluation based on the probe signal; and the transmitting device transmitting data with the receiving device within the first time window based on the modulation parameters.

[0006] According to a second aspect of this disclosure, a method for power line communication for an Internet of Things (IoT) is provided. The method includes: a receiving device sending a first request to a transmitting device, the first request requesting channel evaluation to be performed for a first time window in a power line communication cycle; the receiving device receiving a probe signal sent by the transmitting device in response to the first request for performing the channel evaluation; the receiving device sending modulation parameters to the transmitting device, the modulation parameters being determined by performing the channel evaluation based on the probe signal; and the receiving device and the transmitting device transmitting data based on the modulation parameters within the first time window.

[0007] According to a third aspect of this disclosure, a method for power line communication for an Internet of Things (IoT) is provided. The method includes: a control device receiving a third request from a transmitting device for resource allocation of a probe signal, the third request including information about a first time window in a power line communication cycle, the third request being sent by the transmitting device in response to a first request from a receiving device, the first request being for requesting channel evaluation to be performed for the first time window; and the control device sending the resource allocation information to the transmitting device.

[0008] According to a fourth aspect of this disclosure, a communication apparatus for power line communication in the Internet of Things (IoT) is provided. The communication apparatus includes: a processor; and a power line communication interface coupled to the processor. The processor is configured to: receive, via the power line communication interface, a first request from a receiving device, the first request requesting channel evaluation to be performed for a first time window in a power line communication cycle; in response to the first request, send, via the power line communication interface, a probe signal required for performing the channel evaluation to the receiving device; receive, via the power line communication interface, modulation parameters from the receiving device, the modulation parameters being determined by performing the channel evaluation based on the probe signal; and, based on the modulation parameters and within the first time window, transmit data with the receiving device via the power line communication interface.

[0009] According to a fifth aspect of this disclosure, a communication apparatus for power line communication in the Internet of Things (IoT) is provided. The communication apparatus includes: a processor; and a power line communication interface coupled to the processor. The processor is configured to: send a first request to a transmitting device via the power line communication interface, the first request requesting channel evaluation to be performed for a first time window in a power line communication cycle; receive, via the power line communication interface, a probe signal sent by the transmitting device in response to the first request for performing the channel evaluation; send modulation parameters to the transmitting device via the power line communication interface, the modulation parameters being determined by performing the channel evaluation based on the probe signal; and perform data transmission with the transmitting device via the power line communication interface based on the modulation parameters within the first time window.

[0010] According to a sixth aspect of this disclosure, a control device for power line communication in the Internet of Things (IoT) is provided. The control device includes: a processor; and a power line communication interface coupled to the processor. The processor is configured to: receive, via the power line communication interface, a third request from a transmitting device for resource allocation of a probe signal, the third request including information about a first time window in a power line communication cycle, the third request being sent by the transmitting device in response to a first request from a receiving device, the first request being for requesting channel evaluation for the first time window; and send, via the power line communication interface, information about the resource allocation to the transmitting device.

[0011] According to a seventh aspect of this disclosure, an apparatus for power line communication in the Internet of Things (IoT) is provided. The apparatus includes: a first request receiving unit configured to receive a first request from a receiving device, the first request requesting channel evaluation to be performed for a first time window in a power line communication cycle; a probe signal transmitting unit configured to, in response to the first request, transmit a probe signal to the receiving device required for performing the channel evaluation; a modulation parameter receiving unit configured to receive modulation parameters from the receiving device, the modulation parameters being determined by performing the channel evaluation based on the probe signal; and a first data transmission unit configured to transmit data between the transmitting device and the receiving device within the first time window based on the modulation parameters.

[0012] According to an eighth aspect of this disclosure, an apparatus for power line communication in the Internet of Things (IoT) is provided. The apparatus includes: a first request sending unit configured for a receiving device to send a first request to a transmitting device, the first request requesting channel evaluation to be performed for a first time window in a power line communication cycle; a probe signal receiving unit configured for the receiving device to receive a probe signal sent by the transmitting device in response to the first request, required for performing the channel evaluation; a modulation parameter sending unit configured for the receiving device to send modulation parameters to the transmitting device, the modulation parameters being determined by performing the channel evaluation based on the probe signal; and a second data transmission unit configured for the receiving device and the transmitting device to perform data transmission based on the modulation parameters within the first time window.

[0013] According to a ninth aspect of this disclosure, an apparatus for power line communication in the Internet of Things (IoT) is provided. The apparatus includes: a third request receiving unit configured to control a device to receive a third request from a transmitting device for resource allocation of a probe signal, the third request including information about a first time window in a power line communication cycle, the third request being sent by the transmitting device in response to a first request from a receiving device, the first request being for requesting channel evaluation to be performed for the first time window; and a resource allocation unit configured for the control device to send information about the resource allocation to the transmitting device.

[0014] According to a tenth aspect of this disclosure, a system for power line communication in the Internet of Things (IoT) is provided. The system includes the communication devices described in the fourth and fifth aspects above, and the control device described in the sixth aspect above.

[0015] According to an eleventh aspect of the present disclosure, a chip is provided, including a processor and a front-end circuit, the processor and the front-end circuit operating together to perform the methods of the first, second or third aspects described above.

[0016] According to a twelfth aspect of the present disclosure, a computer-readable storage medium is provided. The computer-readable storage medium includes machine-executable instructions that, when executed by a device, cause the device to perform a method according to the first, second, or third aspect.

[0017] According to a thirteenth aspect of the present disclosure, a computer program product is provided. The computer program product includes computer program code that, when executed by a device, causes the device to perform a method according to the first, second, or third aspect.

[0018] As will be understood from the following description of the exemplary embodiments, the technical solutions presented herein can significantly improve the rate performance and resource utilization efficiency of both PLC IoT services and PLC broadband services with limited increase in complexity.

[0019] It should be understood that the description in the Summary of the Invention is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0020] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0021] Figure 1 A schematic diagram of an example PLC network in which embodiments of the present disclosure may be implemented is shown;

[0022] Figure 2A A schematic diagram of selecting a time window in Rate Boost Mode (RBM) according to an embodiment of the present disclosure is shown;

[0023] Figure 2B A schematic diagram of transmission opportunity allocation (TXOP) under non-RBM according to an embodiment of the present disclosure is shown;

[0024] Figure 2C A schematic diagram of TXOP allocation under RBM according to an embodiment of the present disclosure is shown;

[0025] Figure 3 A schematic diagram illustrating the process of entering the RBM in the downlink direction according to an embodiment of the present disclosure is shown;

[0026] Figure 4 A schematic diagram illustrating the process of entering the RBM in the up direction according to an embodiment of the present disclosure is shown;

[0027] Figure 5 A schematic diagram illustrating the process of exiting RBM according to an embodiment of the present disclosure is shown;

[0028] Figure 6 A schematic diagram of another process of entering the RBM in the downlink direction according to an embodiment of the present disclosure is shown;

[0029] Figure 7 A flowchart is shown of a method for using a PLC for IoT implemented at a transmitting device according to an embodiment of this disclosure;

[0030] Figure 8 A flowchart is shown of a method for using a PLC for IoT implemented at a receiving device according to an embodiment of this disclosure;

[0031] Figure 9 A flowchart is shown of a method for using a PLC for IoT implemented at a control device according to an embodiment of the present disclosure;

[0032] Figure 10 A schematic block diagram of an apparatus for a PLC for IoT implemented at a transmitting device according to an embodiment of the present disclosure is shown;

[0033] Figure 11 A schematic block diagram of an apparatus for a PLC for IoT implemented at a receiving device according to an embodiment of the present disclosure is shown;

[0034] Figure 12 A schematic block diagram of a device for an IoT PLC implemented at a control device according to an embodiment of the present disclosure is shown; and

[0035] Figure 13 A simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure is shown. Detailed Implementation

[0036] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0037] The term "comprising" and its variations as used herein are open-ended inclusion, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment". Relevant definitions for other terms will be given in the description below.

[0038] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0039] As used herein, the term "circuit" refers to one or more of the following:

[0040] (a) Hardware-only implementations (such as implementations using only analog and / or digital circuits); and

[0041] (b) Combinations of hardware circuitry and software, such as (if applicable): (i) combinations of analog and / or digital hardware circuitry with software / firmware, and (ii) any part of a hardware processor with software (including digital signal processors, software, and memory that work together to enable devices such as optical line terminals (OLTs) or other computing devices to perform various functions); and

[0042] (c) Hardware circuitry and / or processors, such as microprocessors or a portion thereof, that require software (e.g. firmware) for operation, but may be without software when it is not required for operation.

[0043] The definition of "circuit" applies to all uses of this term in this application (including any claim). As another example, the term "circuit" as used herein also covers a hardware circuit or processor (or processors), or a portion of a hardware circuit or processor, or an implementation thereof with accompanying software or firmware. For example, if applicable to a particular claim element, the term "circuit" also covers a baseband integrated circuit or processor integrated circuit, or a similar integrated circuit in an OLT or other computing device.

[0044] As used herein, the term "PLC network" refers to any network that uses power lines to transmit data or information using digital signal processing methods. This network can be used in conjunction with wired networks such as Digital Subscriber Line (DSL) technology using telephone lines and Cable Modems (CM) using coaxial cable lines for cable television, as well as with wireless networks such as WiFi and Bluetooth. Of course, it can also be used with any other suitable networks that are currently existing or will be developed in the future.

[0045] As used in this article, the term "PLC Network Master (DM)" refers to the master node in a PLC network, which is responsible for the access, authentication, and resource time slot scheduling and allocation of other nodes in the PLC network.

[0046] As used herein, the term "PLC broadband node" refers to any terminal device capable of broadband communication via a PLC. This terminal device may have wireless or wired communication capabilities. Examples of such terminal devices include, but are not limited to, customer premises equipment (CPE), user equipment (UE), personal computers, desktop computers, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, machine-type communication (MTC) devices, in-vehicle devices for V2X (where X refers to pedestrian, vehicle, or infrastructure / network) communication, or image capture devices such as digital cameras, gaming devices, music storage and playback devices, or Internet devices capable of wireless or wired Internet access and browsing, etc.

[0047] As used herein, the term "IoT subdomain" refers to a subnetwork comprised of IoT nodes within a PLC network. The term "IoT subdomain node (IoT-SDM, IoT-Subdomain Master)" refers to a node that manages or coordinates data transmission within an IoT subdomain. The terms "IoT node" or "IoT terminal node" can refer to IoT terminal devices with PLC capabilities, such as smart appliances, smart meters, and wearable devices. The term "IoT relay node" refers to a repeater within the aforementioned IoT subdomain, connected to the IoT-SDM to extend the network transmission distance.

[0048] Figure 1 A schematic diagram of an example PLC network 100 in which embodiments of this disclosure may be implemented is shown. Figure 1 As shown, the PLC network 100 may include IoT terminal nodes 101, 102, and 103, PLC broadband nodes 104 and 105, IoT relay node 111, IoT-SDM 121, and DM 122. IoT terminal nodes 101, 102, and 103 can communicate with IoT-SDM 121 via IoT relay node 111, and IoT-SDM 121 communicates with a remote server (not shown) outside the PLC network 100 via DM 122. In other words, IoT terminal nodes 101, 102, and 103 need to communicate with DM 122 via IoT-SDM 121. PLC broadband nodes 104 and 105 can communicate with DM 122 via power line channels to access networks such as the Internet, local area networks, metropolitan area networks, etc. In some embodiments, IoT-SDM 121 and DM 122 can be implemented as separate physical entities. In some embodiments, IoT-SDM 121 and DM 122 can be implemented on the same physical entity, as shown in Figure 120.

[0049] Despite Figure 1The diagram shows IoT relay node 111, but in some embodiments, the PLC network 100 may not include IoT relay node 111. In this case, IoT terminal nodes 101, 102, and 103 can communicate directly with IoT-SDM 121. Furthermore, it should be understood that the number of IoT terminal nodes, PLC broadband nodes, and IoT relay nodes is not limited. Figure 1 The example shown may include any other suitable number of more or fewer components. The functionality of IoT-SDM 121 can be implemented centrally or distributedly on any node in the IoT subdomain, and the functionality of DM 122 can be implemented centrally or distributedly on any node in the PLC network. Furthermore, PLC network 100 may include additional components not shown, or some components shown may be omitted; this disclosure does not limit the scope of the embodiments. Implementation of PLC network 100 is not limited to the specific example described above, but can be implemented in any suitable manner.

[0050] In existing PLC IoT technologies, to achieve low cost, low power consumption, and high reliability, robust communication technologies are employed at the physical layer, such as the Homeplug Green PHY standard and the Robust Orthogonal Frequency Division Multiplexing (ROBO) mode used in IEEE 1901.1. The ITU-T G.hn protocol also defines a Robust Communication Mode (RCM). In ROBO / RCM mode, low-order bit modulation is consistently used, along with repetitive coding. This enhances transmission reliability and supports data rates from 4 Mbps to 10 Mbps. Table 1 below shows parameter examples for several ROBO modes.

[0051] Table 1. Parameter Examples for ROBO Mode

[0052] model Physical layer rate Modulation order FEC bitrate Number of repeated copies Small ROBO 3.8Mbps QPSK 1 / 2 5 Standard ROBO 4.9Mbps QPSK 1 / 2 4 High-speed ROBO 9.8Mbps QPSK 1 / 2 2

[0053] It is evident that by adopting the ROBO mode at the physical layer, the communication scheme is simple, supports a large number of nodes, and has high reliability, but the speed is relatively low.

[0054] In PLC broadband technology, carrier-based adaptive modulation is used. The modulation order can reach up to 4096QAM, offering high speed, but also high complexity, resulting in a limited number of supported nodes. Table 2 below shows a parameter comparison example of PLC broadband technology and PLC IoT technology.

[0055] Table 2. Parameter Comparison Examples of PLC Broadband Technology and PLC IoT Technology

[0056]

[0057] Thus, in PLC broadband and PLC IoT convergence scenarios, the same medium needs to support several broadband nodes and hundreds of IoT nodes. Although each IoT node has relatively low data traffic, the large number of nodes results in a high overall overhead for IoT applications. Furthermore, the low achievable speed of IoT technology in the aforementioned ROBO mode leads to high resource consumption. This further restricts the communication resources available to broadband nodes and significantly reduces the achievable speed of broadband nodes.

[0058] Meanwhile, the bandwidth requirements of IoT applications are constantly increasing, no longer limited to simple control needs and intermittent reporting. For example, sensors have continuous fixed bandwidth requirements, such as 150Kbps per sensor. In this case, 40 sensors would require 6Mbps of bandwidth, far exceeding the communication bandwidth requirements of traditional smart grids.

[0059] In view of this, embodiments of this disclosure propose an improved PLC scheme for IoT. According to the proposed scheme, a Rate Boost Mode (RBM) is introduced. For convenience, RBM is also referred to herein as the first mode. In this RBM, the IoT node performs data transmission based on at least one time window within the power line communication cycle. Specifically, one of the at least one time windows is selected, and channel evaluation is performed for the selected time window to determine modulation parameters for data transmission within that selected time window. Through cooperation between the physical layer and the Medium Access Control (MAC) layer, transmission performance per unit resource is significantly improved, locking the physical layer time slot location for data stream transmission. Thus, high rate performance is achieved using a small amount of resources, approaching the resource utilization efficiency of broadband nodes in communication. For ease of understanding, the following describes... Figures 2A to 2C This will be described in detail.

[0060] Figure 2A A schematic diagram 200A illustrating the selection of a time window under RBM according to an embodiment of the present disclosure is shown. As is known, the power line channel also changes in real time due to the influence of real-time changes in load and noise. However, the real-time changes in the power line channel exhibit the characteristics of an alternating current (AC) cycle, such as... Figure 2A As shown in 210. Figure 2A As shown, windowing can be performed based on the AC cycle of the power line channel, for example, dividing it into 8 time windows 201-208. It should be understood that the number of time windows is not limited to this, but any suitable number can be used.

[0061] According to embodiments of this disclosure, under RBM, a single time window can be selected for channel evaluation and output physical layer transmission parameters for that single time window. In this document, the physical layer transmission parameters are also referred to as a bit allocation table (BAT), and each time window is also referred to as a BAT region. Figure 2A As shown, under RBM, a time window of 205 can be selected for rate adaptive operation.

[0062] In PLC broadband communication, a separate BAT (Band Advisory Unit) is typically maintained for each time window. Since the BAT is at the carrier level, it consumes a significant amount of storage space. Furthermore, the signaling overhead required for synchronizing the BAT between the transmitting and receiving parties is substantial. Therefore, maintaining multiple time windows doubles the overhead. In contrast, under the RBM (Rack and Module Management) of this disclosure embodiment, since channel evaluation is performed only for a single time window, the storage and signaling overhead is only a fraction of that in PLC broadband communication (1 / 8 in this example).

[0063] Furthermore, compared to the ROBO mode, which uses fixed low-order bit modulation and repetitive coding, RBM can significantly improve communication efficiency per unit of resources. Table 3 below shows a performance comparison example of RBM and ROBO modes, assuming the same bandwidth.

[0064] Table 3. Performance Comparison Examples of RBM and ROBO / RCM Modes

[0065]

[0066] It is evident that, with the same bandwidth, 1 / 8 of the resource usage can provide higher speed performance.

[0067] For the MAC layer, DM needs to allocate communication resources for IoT nodes. Figure 2B A schematic diagram 200B illustrating TXOP allocation under a non-RBM configuration according to an embodiment of this disclosure is shown. Figure 2B As shown, in non-RBM, DM typically allocates contention-free time slots (CFTS) to IoT nodes from the shared transmission opportunity (STXOP).

[0068] According to embodiments of this disclosure, under RBM, IoT nodes will use and only use specific windows to transmit data. Therefore, for the MAC layer, DM needs to allocate resources at that window location for the IoT node. For example, upon entering RBM, a specific TXOP needs to be allocated for the IoT node. DM needs to modify the TXOP allocation to adapt to the new requirements. Figure 2CA schematic diagram 200C illustrating TXOP allocation under RBM according to an embodiment of this disclosure is shown. For example... Figure 2C As shown, upon entering the RBM, after determining the time window 231 for the IoT node, the DM MAC needs to allocate TXOP resources 232 for that window location. In some embodiments, the TXOP resource 232 can be a CFTXOP, which is allocated to the IoT node. In some alternative embodiments, the TXOP resource 232 can be an STXOP, and the IoT node is allocated the highest priority CFTS within that STXOP. In some embodiments, a MAC cycle includes two AC cycles, in which case one or two CFTXOPs or STXOPs can be allocated to the IoT node based on bit rate requirements.

[0069] According to embodiments of this disclosure, when there are hundreds of IoT nodes in a PLC network, not all IoT nodes have a continuous high bit rate requirement; rather, most IoT nodes operate at low rates most of the time. Therefore, it is not necessary to maintain a BAT (Bit Rate Acquisition) for all IoT nodes, but rather a few IoT nodes can operate in RBM (Rich Bandwidth Mode) only when necessary. In some embodiments of this disclosure, RBM and ROBO (Robo-Based Mode) can be combined for IoT node communication. For example, RBM can be used in high-rate scenarios (e.g., when the transmission rate exceeds a predetermined threshold rate) or under upper-level control, while ROBO mode is used at other times. Therefore, since RBM is only used when needed, the overhead of the aggregation node is significantly reduced. An aggregation node refers to a node that communicates with multiple nodes simultaneously in an IoT tree or star network. For ease of understanding, the following describes... Figures 3 to 6 To provide a more detailed explanation.

[0070] Figure 3 A schematic diagram of a process 300 entering the RBM in the downlink direction according to an embodiment of the present disclosure is shown. For convenience, the following is combined with... Figure 1 Example pair Figure 3 This will be explained further. In this example, downlink refers to data transmission from IoT-SDM 121 to IoT terminal node 101. In this case, IoT-SDM 121 is the transmitting device, IoT terminal node 101 is the receiving device, and DM 122 is the control device. It should be understood that... Figure 3 This process can also be applied to data transmission from IoT-SDM 121 to other IoT terminal nodes in network 100. It should also be understood that... Figure 3 The process may include other additional processes not shown, or some of the processes shown may be omitted. The scope of this disclosure is not limited thereto.

[0071] In this embodiment, Figure 3The process 300 may include the process of negotiating entry into the RBM 310, the process of channel assessment 320, and the process of data transmission 330 (also known as the process of resource allocation 330).

[0072] IoT-SDM 121 can initiate the negotiation process 310 to enter the RBM. For example... Figure 3 As shown, IoT-SDM 121 can send a request 311 to DM 122 for entering the RBM (also referred to herein as a second request for convenience). For example, IoT-SDM 121 can send an RBM_enter.req message to DM 122. Of course, this disclosure does not limit the form of the message, but any other suitable form can be used.

[0073] In some embodiments, the IoT-SDM 121 can monitor the data transmission rate and send the request when the data transmission rate exceeds a predetermined threshold rate. In some embodiments, the predetermined threshold rate can be dynamically configured as needed. In some embodiments, the predetermined threshold rate can be pre-configured. In some alternative embodiments, the IoT-SDM 121 can monitor the service type of the data transmission and send the request when the service type is a predetermined service type. For example, the predetermined service type indicates high-speed data transmission. In some alternative embodiments, the IoT-SDM 121 can send the request in response to receiving an instruction to enter the RBM (also referred to herein as a first instruction for convenience). In some embodiments, the instruction can originate from upper-layer control, such as the MAC layer or application layer. It should be understood that the IoT-SDM 121 can send the request under any other suitable triggering conditions, and is not limited to the examples described above.

[0074] If DM 122 rejects the request, DM 122 may send a negative response (not shown) to IoT-SDM 121. For example, DM 122 may send an RBM_enter.dec message to IoT-SDM 121. Of course, this disclosure does not limit the form of the message, but any other suitable form may be used. At this point, process 300 will end.

[0075] If DM 122 accepts the request, DM 122 can send a positive response 312 to IoT-SDM 121 in response to the request. For example, DM 122 can send an RBM_enter.cnf message to IoT-SDM 121. Of course, this disclosure does not limit the form of the message, but any other suitable form can be used.

[0076] In response to receiving the affirmative response, IoT-SDM 121 can send a notification (referred to herein as the first notification) to IoT terminal node 101, indicating entry into the RBM. For example, IoT-SDM 121 can send an RBM_enter.cnf message to IoT terminal node 101. Of course, this embodiment does not limit the form of the message, and any other suitable form can be used. This completes the negotiation process 310 for entering the RBM, and entry into the RBM is achieved.

[0077] Under RBM, IoT terminal node 101 can initiate channel evaluation process 320. For example... Figure 3 As shown, IoT terminal node 101 sends a 321 message to IoT-SDM 121 requesting channel evaluation to be performed for a single time window (also referred to herein as the first time window) within the power line communication cycle (for convenience, this is also referred to herein as the first request). For example, IoT terminal node 101 may select a BAT region (i.e., the time window) and include information about the selected BAT region (e.g., an identifier (ID) or similar information) in the request. For example, IoT terminal node 101 may send a CE_Initiation.req message to IoT-SDM 121 as this request. Of course, any other suitable message format may also be used.

[0078] In response to the channel assessment request, IoT-SDM 121 can send a 322 request for resource allocation for probe signals (also referred to herein as a third request for convenience) to DM 122. This request includes information about the selected BAT area. For example, IoT-SDM 121 can send a CE_ProbeSlotAssign.req message to DM 122 as this request. Of course, any other suitable message format can also be used.

[0079] In response to this resource allocation request, DM 122 can send 323 information about the resource allocation to IoT-SDM 121. That is, DM 122 allocates resources for IoT-SDM 121 to detect signals. For example, DM 122 can send a CE_ProbeSlotAssign.cnf message to IoT-SDM 121 to allocate the resource. Of course, any other suitable message format can also be used.

[0080] Subsequently, IoT-SDM 121 can send a positive response (324) to IoT terminal node 101 in response to the first request. For example, IoT-SDM 121 can send a CE_Initiation.cnf message to IoT terminal node 101. Of course, any other suitable message format can also be used.

[0081] In response to this affirmative response, IoT terminal node 101 may send a 325 request to IoT-SDM 121 for transmitting a probe signal (also referred to herein as a fourth request for convenience). For example, IoT terminal node 101 may send a CE_ProbeRequest.ind message to IoT-SDM 121 to request the transmission of a probe signal. In some embodiments, the probe signal may be a probe frame (PROBE frame) or a channel training sequence. Of course, the probe signal is not limited to these and may take any other suitable form.

[0082] In response to the request for the probe signal, IoT-SDM 121 may send probe signal 326 to IoT terminal node 101. Using this probe signal, IoT terminal node 101 can perform channel evaluation to determine modulation parameters. This channel evaluation can be implemented in any suitable manner known in the art or developed in the future, without limitation herein. It should be understood that IoT terminal node 101 may require multiple probe signals to complete the channel evaluation. In this case, the request and transmission process of the probe signal (i.e., the processes shown in 325 and 326) may need to be performed multiple times.

[0083] Subsequently, IoT terminal node 101 sends the determined modulation parameters 327 to IoT-SDM 121 for data transmission within the selected time window. This completes the channel evaluation process 320. The data transmission process then begins 330.

[0084] refer to Figure 3DM 122 can send 331 information about the transmission timing to IoT-SDM 121, which covers a first time window. For example, DM 122 can generate a new TXOP allocation based on the information of the first time window and send a MAP message including the new TXOP allocation to IoT-SDM 121. In some embodiments, the new TXOP allocation may include a CFTXOP, which covers the location of the BAT region selected for IoT terminal node 101. For example, the CFTXOP may correspond to BAT_ID = x. In some alternative embodiments, the new TXOP allocation may include an STXOP, which covers the location of the BAT region selected for IoT terminal node 101. The highest priority CFTS can be allocated to IoT terminal node 101 in the STXOP. Of course, the embodiments of this disclosure are not limited to this, and any other suitable TXOP allocation method can be used. The following description uses CFTXOP as an example.

[0085] IoT-SDM 121 can send the information about transmission timing described in 332 to IoT terminal node 101. For example, IoT-SDM 121 can send an IoT-MAP message to IoT terminal node 101, which includes the CFTXOP allocation for IoT-SDM 121.

[0086] Subsequently, IoT-SDM 121 can use the CFTXOP to perform downlink IoT data transmission 333 with IoT terminal node 101 based on the received modulation parameters.

[0087] Figure 4 A schematic diagram of a process 400 entering the RBM in the up direction according to an embodiment of the present disclosure is shown. For convenience, the following is combined with... Figure 1 Example pair Figure 4 This will be explained further. In this example, the uplink direction refers to data transmission from IoT terminal node 101 to IoT-SDM 121. In this case, IoT terminal node 101 is the transmitting device, IoT-SDM 121 is the receiving device, and DM 122 is the control device. It should be understood that... Figure 4 This process can also be applied to data transmission from other IoT terminal nodes in network 100 to IoT-SDM 121. It should also be understood that... Figure 4 The process may include other additional processes not shown, or some of the processes shown may be omitted. The scope of this disclosure is not limited thereto.

[0088] In this embodiment, Figure 4The process 400 may include the process 410 of negotiating entry into the RBM, the process 420 of channel assessment, and the process 430 of data transmission (also known as the process 430 of resource allocation).

[0089] IoT terminal node 101 can initiate a negotiation process 410 to enter the RBM. IoT terminal node 101 can send a request to DM 122 for entering the RBM via IoT-SDM 121 (hereinafter referred to as a second request for convenience). Figure 4 As shown, IoT terminal node 101 can send a request 411 to IoT-SDM 121 for entering RBM, and IoT-SDM 121 forwards the request 412 to DM 122. For example, IoT terminal node 101 can send an RBM_enter.req message to IoT-SDM 121, and IoT-SDM 121 forwards the message to DM 122. Of course, this embodiment does not impose any limitation on the form of the message, but any other suitable form can be used.

[0090] In some embodiments, the IoT terminal node 101 can monitor the data transmission rate and send the request when the data transmission rate exceeds a predetermined threshold rate. In some embodiments, the predetermined threshold rate can be dynamically configured as needed. In some embodiments, the predetermined threshold rate can be pre-configured. In some alternative embodiments, the IoT terminal node 101 can monitor the service type of the data transmission and send the request when the service type is a predetermined service type. For example, the predetermined service type indicates high-speed data transmission. In some alternative embodiments, the IoT terminal node 101 can send the request in response to receiving an instruction to enter the RBM (also referred to herein as a first instruction for convenience). In some embodiments, the instruction can originate from upper-layer control, such as the MAC layer or application layer. It should be understood that the IoT terminal node 101 can send the request under any other suitable triggering conditions, and is not limited to the examples described above.

[0091] If DM 122 rejects the request, DM 122 may send a negative response (not shown) to IoT-SDM 121. For example, DM 122 may send an RBM_enter.dec message to IoT-SDM 121. Of course, this disclosure does not limit the form of the message, but any other suitable form may be used. At this point, process 400 will end.

[0092] If DM 122 accepts the request, it can send a positive response (413) to IoT-SDM 121. For example, DM 122 can send an RBM_enter.cnf message to IoT-SDM 121. Of course, this disclosure does not limit the form of the message; any other suitable form may be used.

[0093] Upon receiving the positive response, IoT-SDM 121 determines to enter the RBM and can initiate the channel assessment process 420. For example... Figure 4 As shown, IoT-SDM 121 sends a 421 message to IoT terminal node 101 requesting channel evaluation to be performed for a single time window (also referred to herein as the first time window) within the power line communication cycle (for convenience, this is also referred to herein as the first request). For example, IoT-SDM 121 can select a BAT region (i.e., the time window) and include information about the selected BAT region (e.g., BAT region ID or similar information) in the request. For example, IoT-SDM 121 can send a CE_Initiation.req message to IoT terminal node 101 as this request. Of course, any other suitable message format can also be used.

[0094] In response to the channel assessment request, IoT terminal node 101 may send a request for resource allocation for probe signals (referred to herein as a third request for convenience) to DM 122 via IoT-SDM 121. This request includes information about the selected BAT area. For example, IoT terminal node 101 may send a 422CE_ProbeSlotAssign.req message to IoT-SDM 121 as this request, and IoT-SDM 121 may forward this message 423 to DM 122. Of course, any other suitable message format may also be used.

[0095] In response to the resource allocation request, DM 122 can send information about the resource allocation to IoT terminal node 101 via IoT-SDM 121. For example, DM 122 sends information about the resource allocation (424) to IoT-SDM 121, and IoT-SDM 121 forwards this information (425) to IoT terminal node 101. That is, DM 122 allocates resources for signal detection to IoT terminal node 101. For example, DM 122 can send a CE_ProbeSlotAssign.cnf message to IoT-SDM 121, and IoT-SDM 121 can forward this message to IoT terminal node 101, thereby allocating the resource. Of course, any other suitable message format can also be used.

[0096] Subsequently, IoT terminal node 101 can send a 426 positive response to the first request to IoT-SDM 121. For example, IoT terminal node 101 can send a CE_Initiation.cnf message to IoT-SDM 121. Of course, any other suitable message format can also be used.

[0097] In response to this affirmative response, IoT-SDM 121 may send a 427 request to IoT terminal node 101 for transmitting a probe signal (also referred to herein as a fourth request for convenience). For example, IoT-SDM 121 may send a CE_ProbeRequest.ind message to IoT terminal node 101 to request the transmission of a probe signal. In some embodiments, the probe signal may be a probe frame (PROBE frame) or a channel training sequence. Of course, the probe signal is not limited to these and may take any other suitable form.

[0098] In response to the request for the probe signal, IoT terminal node 101 may send probe signal 428 to IoT-SDM 121. Using this probe signal, IoT-SDM 121 can perform channel evaluation to determine modulation parameters. This channel evaluation can be implemented in any suitable manner known in the art or developed in the future, without limitation herein. It should be understood that IoT-SDM 121 may require multiple probe signals to complete the channel evaluation. In this case, the request and transmission process of the probe signal (i.e., the processes shown in 427 and 428) may need to be performed multiple times.

[0099] Subsequently, IoT-SDM 121 sends the determined modulation parameters 429 to IoT terminal node 101 for data transmission within the selected time window. This completes the channel evaluation process 420. The data transmission process then begins 430.

[0100] refer to Figure 4DM 122 can send 431 information about the transmission timing to IoT-SDM 121, which covers a first time window. For example, DM 122 can generate a new TXOP allocation based on the information of the first time window and send a MAP message including the new TXOP allocation to IoT-SDM 121. In some embodiments, the new TXOP allocation may include a CFTXOP, which covers the location of the BAT region selected for IoT terminal node 101. For example, the CFTXOP may correspond to BAT_ID = x. In some alternative embodiments, the new TXOP allocation may include an STXOP, which covers the location of the BAT region selected for IoT terminal node 101. The highest priority CFTS can be allocated to IoT terminal node 101 in the STXOP. Of course, the embodiments of this disclosure are not limited to this, and any other suitable TXOP allocation method can be used. The following description uses CFTXOP as an example.

[0101] IoT-SDM 121 can send the information about transmission timing described in 432 to IoT terminal node 101. For example, IoT-SDM 121 can send an IoT-MAP message to IoT terminal node 101, which includes the CFTXOP allocation for IoT-SDM 121.

[0102] Subsequently, IoT terminal node 101 can use the CFTXOP to perform uplink IoT data transmission 433 with IoT-SDM 121 based on the received modulation parameters.

[0103] Figure 5 A schematic diagram of the process 500 for exiting RBM according to an embodiment of the present disclosure is shown. For convenience, the following is in conjunction with... Figure 1 Example pair Figure 5 This is an explanation. Procedure 500 in this example applies to any uplink or downlink scenario exiting the RBM. It should be understood that... Figure 5 The process may include other additional processes not shown, or some of the processes shown may be omitted. The scope of this disclosure is not limited thereto.

[0104] In this embodiment, Figure 5 Process 510 is the process of exiting the RBM during uplink data transmission. In this case, IoT terminal node 101 is the transmitting device, IoT-SDM 121 is the receiving device, and DM 122 is the control device. During uplink data transmission, this process 510 can be initiated by IoT terminal node 101.

[0105] like Figure 5As shown, IoT terminal node 101 can send a request to DM 122 to exit RBM (also referred to herein as the fifth request for convenience). For example, IoT terminal node 101 can send the request to IoT-SDM 121, and IoT-SDM 121 forwards the request to DM 122. For example, IoT terminal node 101 can send an RBM_exit.req message to IoT-SDM 121, which will then forward the message to DM 122. Of course, any other suitable message format can also be used.

[0106] If DM 122 accepts the request, it can send a positive response to the request to IoT terminal node 101 via IoT-SDM 121. For example, DM 122 can send the request to IoT-SDM 121, and IoT-SDM 121 can forward the request to IoT terminal node 101. Alternatively, DM 122 can send an RBM_exit.cnf message to IoT-SDM 121, which will then forward the message to IoT terminal node 101. Of course, any other suitable message format can also be used.

[0107] In some embodiments, when IoT-SDM 121 receives the affirmative response, IoT-SDM 121 can release the modulation parameters for the first time window, i.e., the BAT for the selected BAT region. In some embodiments, when IoT terminal node 101 receives the affirmative response, IoT terminal node 101 can release the modulation parameters for the first time window, i.e., the BAT for the selected BAT region.

[0108] Continue to refer to Figure 5 Process 520 is the process of exiting the RBM during downlink data transmission. In this case, IoT-SDM 121 is the transmitting device, IoT terminal node 101 is the receiving device, and DM 122 is the control device. During downlink data transmission, this process 520 can be initiated by IoT-SDM 121.

[0109] like Figure 5 As shown, IoT-SDM 121 can send a 521 request to DM 122 to exit the RBM (also referred to as the fifth request in this document for convenience). For example, IoT-SDM 121 can send an RBM_exit.req message to DM 122. Of course, any other suitable message format can also be used.

[0110] If DM 122 accepts the request, it can send a positive response (522) to IoT-SDM 121. For example, DM 122 can send an RBM_exit.cnf message to IoT-SDM 121. Of course, any other suitable message format can also be used.

[0111] Upon receiving this affirmative response, IoT-SDM 121 can send a notification to IoT terminal node 101, 523, to exit RBM (also referred to herein as a second notification for convenience). For example, DM 122 can forward the RBM_exit.cnf message to IoT-SDM 121. Of course, any other suitable message format can also be used.

[0112] In some embodiments, when IoT-SDM 121 receives the affirmative response, IoT-SDM 121 may release the modulation parameters for the first time window, i.e., the BAT for the selected BAT region. In some embodiments, when IoT terminal node 101 receives the notification, IoT terminal node 101 may release the modulation parameters for the first time window, i.e., the BAT for the selected BAT region.

[0113] The above combination Figures 3 to 5 The described embodiment uses communication between IoT-SDM 121 and IoT terminal node 101 as an example. However, in some embodiments, the communication between IoT-SDM 121 and IoT terminal node 101 in the above process can also be accomplished via one or more IoT relay nodes. Furthermore, in some embodiments, communication between IoT relay nodes and IoT terminal nodes can also employ RBM. For ease of understanding, the following description... Figure 6 This will be explained in more detail.

[0114] Figure 6 A schematic diagram of another process 600 entering the RBM in the downlink direction according to an embodiment of the present disclosure is shown. For convenience, the following is combined with... Figure 1 Example pair Figure 6 This will be explained further. In this example, the downlink direction refers to data transmission from IoT relay node 111 to IoT terminal node 101. In this case, IoT relay node 111 is the transmitting device, IoT terminal node 101 is the receiving device, and DM 122 is the control device. It should be understood that... Figure 6 The process may include other additional processes not shown, or some of the processes shown may be omitted. The scope of this disclosure is not limited thereto.

[0115] In this embodiment, Figure 6The process 600 may include the process of negotiating entry into the RBM 610, the process of channel assessment 620, and the process of data transmission 630 (also known as the process of resource allocation 630).

[0116] IoT relay node 111 can initiate a negotiation process 610 to enter the RBM. In some embodiments, IoT relay node 111 can send a request for entering the RBM to DM 122 via IoT-SDM 121 (also referred to herein as a second request for convenience). Figure 6 As shown, IoT relay node 111 can send the request to IoT-SDM 121, and IoT-SDM 121 can forward the request to DM 122. For example, IoT relay node 111 can send an RBM_enter.req message to IoT-SDM 121, and IoT-SDM 121 can forward the message to DM 122. Of course, this embodiment does not limit the form of the message, but any other suitable form can be used.

[0117] In some embodiments, the IoT relay node 111 can monitor the data transmission rate and send the request when the data transmission rate exceeds a predetermined threshold rate. In some embodiments, the predetermined threshold rate can be dynamically configured as needed. In some embodiments, the predetermined threshold rate can be pre-configured. In some alternative embodiments, the IoT relay node 111 can monitor the service type of the data transmission and send the request when the service type is a predetermined service type. For example, the predetermined service type indicates high-speed data transmission. In some alternative embodiments, the IoT relay node 111 can send the request in response to receiving an instruction to enter the RBM (also referred to herein as a first instruction for convenience). In some embodiments, the instruction can come from upper-layer control, such as the MAC layer or application layer. It should be understood that the IoT relay node 111 can send the request under any other suitable triggering conditions, and is not limited to the examples described above.

[0118] If DM 122 rejects the request, DM 122 may send a negative response (not shown) to IoT-SDM 121. For example, DM 122 may send an RBM_enter.dec message to IoT-SDM 121. Of course, this disclosure does not limit the form of the message, but any other suitable form may be used. At this point, process 600 will end.

[0119] If DM 122 accepts the request, DM 122 can send a positive response (613) to IoT-SDM 121 in response to the request, and IoT-SDM 121 forwards the positive response (614) to IoT relay node 111. For example, DM 122 can send an RBM_enter.cnf message to IoT-SDM 121, and IoT-SDM 121 can forward the message to IoT relay node 111. Of course, this disclosure does not limit the form of the message, but any other suitable form can be used.

[0120] In response to receiving the affirmative response, IoT relay node 111 can send a notification (referred to herein as a first notification) to IoT terminal node 101, indicating entry into the RBM. For example, IoT relay node 111 can send an RBM_enter.cnf message to IoT terminal node 101. Of course, this embodiment does not limit the form of the message, and any other suitable form can be used. This completes the negotiation process 610 for entering the RBM, and entry into the RBM is achieved.

[0121] Under RBM, IoT terminal node 101 can initiate channel evaluation process 620. For example... Figure 6 As shown, IoT terminal node 101 sends a 621 message to IoT relay node 111 requesting channel evaluation to be performed for a single time window (also referred to herein as the first time window) within the power line communication cycle (for convenience, also referred to herein as the first request). For example, IoT terminal node 101 may select a BAT region (i.e., the time window) and include information about the selected BAT region (e.g., BAT region ID or similar information) in the request. For example, IoT terminal node 101 may send a CE_Initiation.req message to IoT relay node 111 as this request. Of course, any other suitable message format may also be used.

[0122] In response to the channel assessment request, IoT relay node 111 may send a resource allocation request for probe signals (also referred to herein as a third request for convenience) to DM 122 via IoT-SDM 121. This request includes information about the selected BAT area. In some embodiments, IoT relay node 111 may send the resource allocation request to IoT-SDM 121, and IoT-SDM 121 may forward the resource allocation request to DM 122. For example, IoT relay node 111 may send a CE_ProbeSlotAssign.req message to IoT-SDM 121, and IoT-SDM 121 may forward this message to DM 122. Of course, any other suitable message format may also be used.

[0123] In response to the resource allocation request, DM 122 can send information about the resource allocation to IoT relay node 111 via IoT-SDM 121. That is, DM 122 allocates resources for transmitting probe signals to IoT relay node 111. In some embodiments, DM 122 can send information about the resource allocation to IoT-SDM 121, and IoT-SDM 121 forwards this information to IoT relay node 111. For example, DM 122 can send a CE_ProbeSlotAssign.cnf message to IoT-SDM 121, and IoT-SDM 121 can forward this message to IoT relay node 111, thereby allocating resources. Of course, any other suitable message format can also be used.

[0124] In response to receiving information about resource allocation, IoT relay node 111 can send a positive response (626) to IoT terminal node 101 in response to the first request. For example, IoT relay node 111 can send a CE_Initiation.cnf message to IoT terminal node 101. Of course, any other suitable message format can also be used.

[0125] In response to this affirmative response, IoT terminal node 101 may send a request (also referred to herein as a fourth request) 627 to IoT relay node 111 for transmitting a probe signal. For example, IoT terminal node 101 may send a CE_ProbeRequest.ind message to IoT relay node 111 to request the transmission of a probe signal. In some embodiments, the probe signal may be a probe frame (PROBE frame) or a channel training sequence. Of course, the probe signal is not limited to these and may take any other suitable form.

[0126] In response to the request for the probe signal, the IoT relay node 111 may send probe signal 628 to the IoT terminal node 101. Using this probe signal, the IoT terminal node 101 can perform channel evaluation to determine modulation parameters. This channel evaluation can be implemented in any suitable manner known in the art or developed in the future, without limitation herein. It should be understood that the IoT terminal node 101 may require multiple probe signals to complete the channel evaluation. In this case, the request and transmission process of the probe signal (i.e., the processes shown in 627 and 628) may need to be performed multiple times.

[0127] Subsequently, IoT terminal node 101 sends the determined modulation parameters to IoT terminal node 101 for use in data transmission within the selected time window. This completes the channel evaluation process 620. Next, the data transmission process 630 begins.

[0128] refer to Figure 6 DM 122 can send 631 information about the transmission timing to IoT-SDM 121, which covers a first time window. For example, DM 122 can generate a new TXOP allocation based on the information of the first time window and send a MAP message including the new TXOP allocation to IoT-SDM 121. In some embodiments, the new TXOP allocation may include a CFTXOP, which covers the location of the BAT region selected for IoT terminal node 101. For example, the CFTXOP may correspond to BAT_ID = x. In some alternative embodiments, the new TXOP allocation may include an STXOP, which covers the location of the BAT region selected for IoT terminal node 101. The highest priority CFTS can be allocated to IoT terminal node 101 in the STXOP. Of course, the embodiments of this disclosure are not limited to this, and any other suitable TXOP allocation method can be used. The following description uses CFTXOP as an example.

[0129] IoT-SDM 121 can send information about the timing of transmission (632) to IoT relay node 111. For example, IoT-SDM 121 can send an IoT-MAP message to IoT relay node 111, which includes the CFTXOP allocation for IoT relay node 111. IoT relay node 111 can send the aforementioned information about the timing of transmission (633) to IoT terminal node 101. For example, IoT relay node 111 can send an IoT-MAP message to IoT terminal node 101, which includes the CFTXOP allocation for IoT relay node 111.

[0130] Subsequently, the IoT relay node 111 can use the CFTXOP, based on the received modulation parameters, to perform downlink IoT data transmission 634 with the IoT terminal node 101. It should be understood that the above combination... Figures 3 to 6 The described process is merely an example, and the embodiments disclosed herein are not limited thereto, but can be implemented in any suitable manner.

[0131] According to the scheme proposed in this disclosure, the ability to train for a single time window to approach the channel limit can be retained outside of the ROBO mode. Under normal low-traffic conditions, the RBM mode is disabled, and RBM is activated through historical traffic or upper-layer triggering to achieve the benefit of increased speed. This maintains the complexity of the IoT chip. Furthermore, through the coordinated operation of the physical layer and MAC layer, IoT nodes are scheduled for specific time slots based on selected time windows. Therefore, high speed performance and resource utilization efficiency can be achieved with limited complexity and minimal resources.

[0132] Corresponding to the RBM process described above, embodiments of this disclosure provide a method for a PLC for IoT implemented at a transmitting device, a method for a PLC for IoT implemented at a receiving device, and a method for a PLC for IoT implemented at a control device. Figure 7 A flowchart of a method 700 for a PLC used in IoT, implemented at a transmitting device according to an embodiment of this disclosure, is shown. Method 700 can be implemented at a transmitting device (e.g., IoT-SDM 121, IoT relay node 111, or IoT terminal node 101) in a PLC IoT network. For convenience, it will be referred to herein in conjunction with... Figure 1 Example pair Figure 7 This needs to be explained. It should be understood that... Figure 7 The method may include other additional steps not shown, or some steps shown may be omitted. The scope of this disclosure is not limited thereto.

[0133] like Figure 7 As shown, at block 710, the transmitting device receives a first request from the receiving device, the first request being for requesting channel evaluation to be performed for a first time window in a power line communication cycle. In some embodiments, the transmitting device may be an IoT-SDM 121, and the receiving device may be an IoT terminal node 101. In some embodiments, the transmitting device may be an IoT terminal node 101, and the receiving device may be an IoT-SDM 121. In some embodiments, the transmitting device may be an IoT relay node 111, and the receiving device may be an IoT terminal node 101. In some embodiments, the transmitting device may be an IoT terminal node 101, and the receiving device may be an IoT relay node 111.

[0134] In some embodiments, the transmitting device may send a first notification to the receiving device to enter a first mode, in which the transmitting device and the receiving device perform data transmission based on at least one time window within the power line communication cycle. The transmitting device may then receive a first request sent by the receiving device in response to the first notification. In some embodiments, the first mode is RBM (Remote Power Line Communication).

[0135] In some embodiments, in response to a data transmission rate exceeding a predetermined threshold rate, the transmitting device may send a second request to a control device (e.g., DM 122) to enter a first mode. In response to receiving an affirmative response from DM 122 to the second request, the transmitting device may send a first notification to the receiving device. In some alternative embodiments, the transmitting device may send a second request to DM 122 to enter the first mode in response to receiving a first instruction to enter the first mode. In response to receiving an affirmative response from DM 122 to the second request, the transmitting device may send a first notification to the receiving device.

[0136] At block 720, in response to the first request, the transmitting device sends a probe signal to the receiving device for performing channel assessment. In some embodiments, the transmitting device may send a third request to DM 122 for resource allocation of the probe signal, the third request including information about the first time window. In response to receiving the resource allocation information from DM 122, the transmitting device may send an affirmative response to the first request to the receiving device. In response to receiving a fourth request from the receiving device for transmitting the probe signal, the transmitting device may transmit the probe signal to the receiving device based on the information about the resource allocation.

[0137] At box 730, the transmitting device receives modulation parameters from the receiving device, which are determined by the receiving device through channel evaluation based on the probe signal.

[0138] At block 740, the transmitting device transmits data with the receiving device within a first time window based on modulation parameters. In some embodiments, the transmitting device receives information from DM 122 regarding the timing of transmission, which covers the first time window. The transmitting device can then transmit data to the receiving device using the modulation parameters at the specified transmission timing. In some embodiments, the transmitting device can send this information regarding the timing of transmission to the receiving device so that the receiving device can receive the data.

[0139] In some embodiments, the transmitting device may send a second notification to the receiving device to exit the first mode. In some embodiments, the transmitting device may send a fifth request to DM 122 to exit the first mode in response to a data transmission rate less than a predetermined threshold rate, and send a second notification to the receiving device in response to receiving a positive response from DM 122 to the fifth request. In some alternative embodiments, the transmitting device may send a fifth request to DM 122 to exit the first mode in response to receiving a second instruction to exit the first mode, and send a second notification to the receiving device in response to receiving a positive response from DM 122 to the fifth request. In some embodiments, in response to receiving a positive response from DM 122 to the fifth request, the transmitting device may release modulation parameters, thereby saving the maintenance cost of modulation parameters.

[0140] The above is about Figure 7 The description of processing and Figures 3 to 6 The corresponding operations are described in the documentation; other details can be found in the documentation. Figures 3 to 6 The relevant descriptions will not be repeated here. According to Figure 7 This method enables PLC IoT network nodes to send data under RBM. Compared to ROBO mode, the efficiency of data transmission is significantly improved.

[0141] Accordingly, embodiments of this disclosure also provide a method for using a PLC for IoT implemented at a receiving device. Figure 8 A flowchart of a method 800 for a PLC used in IoT, implemented at a receiving device according to an embodiment of the present disclosure, is shown. This method 800 can be implemented at a receiving device (e.g., IoT-SDM 121, IoT relay node 111, or IoT terminal node 101) in a PLC IoT network. For convenience, it will be referred to herein in conjunction with... Figure 1 Example pair Figure 8 This needs to be explained. It should be understood that... Figure 8 The method may include other additional steps not shown, or some steps shown may be omitted. The scope of this disclosure is not limited thereto.

[0142] like Figure 8As shown, at block 810, the receiving device sends a first request to the transmitting device, the first request being used to request channel evaluation to be performed for a first time window in the power line communication cycle. In some embodiments, the transmitting device may be an IoT-SDM 121, and the receiving device may be an IoT terminal node 101. In some embodiments, the transmitting device may be an IoT terminal node 101, and the receiving device may be an IoT-SDM 121. In some embodiments, the transmitting device may be an IoT relay node 111, and the receiving device may be an IoT terminal node 101. In some embodiments, the transmitting device may be an IoT terminal node 101, and the receiving device may be an IoT relay node 111.

[0143] In some embodiments, the receiving device may receive a first notification from the transmitting device to enter a first mode, in which the transmitting and receiving devices perform data transmission based on at least one time window within a power line communication cycle. In response to the first notification, the receiving device may send the first request to the transmitting device. In some embodiments, the first mode is RBM (Remote Power Line Communication).

[0144] At block 820, the receiving device receives a probe signal sent by the transmitting device in response to a first request, which is required for performing channel assessment. In some embodiments, the receiving device may receive a positive response from the transmitting device to the first request. In response to the positive response, the receiving device may send a fourth request to the transmitting device for transmitting the probe signal, and receive the probe signal sent by the transmitting device in response to the fourth request.

[0145] At box 830, the receiving device sends modulation parameters to the transmitting device, which are determined by the receiving device through channel evaluation based on the probe signal.

[0146] At block 840, the receiving device and the transmitting device transmit data based on modulation parameters within a first time window. In some embodiments, the receiving device receives information from the transmitting device regarding the timing of the transmission, which covers the first time window. The receiving device can then receive data from the transmitting device based on this transmission timing.

[0147] In some embodiments, the receiving device may receive a second notification from the transmitting device to exit the first mode. In some embodiments, in response to receiving the second notification, the receiving device may release the aforementioned modulation parameters, thereby saving the maintenance cost of the modulation parameters.

[0148] The above is about Figure 8 The description of processing and Figures 3 to 6 The corresponding operations are described in the documentation; other details can be found in the documentation. Figures 3 to 6 The relevant descriptions will not be repeated here. According to Figure 8This method enables PLC IoT network nodes to receive data under RBM. Compared to ROBO mode, the efficiency of data reception is significantly improved.

[0149] Accordingly, embodiments of this disclosure also provide a method for implementing a PLC for IoT at a control device. Figure 9 A flowchart of a method 900 for a PLC used in an IoT network, implemented at a control device according to an embodiment of this disclosure, is shown. This method 900 can be implemented at a control device (e.g., DM 122) in a PLC IoT network. For convenience, it will be referred to herein in conjunction with... Figure 1 Example pair Figure 9 This needs to be explained. It should be understood that... Figure 9 The method may include other additional steps not shown, or some steps shown may be omitted. The scope of this disclosure is not limited thereto.

[0150] like Figure 9 As shown, at block 910, a control device (e.g., DM 122) receives a third request from a transmitting device for resource allocation for probing signals. This third request includes information about a first time window within a power line communication cycle. The third request is sent by the transmitting device in response to a first request from a receiving device requesting channel evaluation for the first time window. In some embodiments, the transmitting device may be IoT-SDM 121, and the receiving device may be IoT terminal node 101. In some embodiments, the transmitting device may be IoT terminal node 101, and the receiving device may be IoT-SDM 121. In some embodiments, the transmitting device may be IoT relay node 111, and the receiving device may be IoT terminal node 101. In some embodiments, the transmitting device may be IoT terminal node 101, and the receiving device may be IoT relay node 111.

[0151] In some embodiments, before receiving a third request, DM 122 may receive a second request from the transmitting device for entering a first mode, in which the transmitting and receiving devices perform data transmission based on at least one time window within a power line communication cycle. DM 122 may send an affirmative response to the second request to the transmitting device, so that the transmitting device may send a first notification of entering the first mode to the receiving device. In some embodiments, the first mode is RBM.

[0152] At box 920, DM 122 sends information about resource allocation to the transmitting device. Based on this information, the transmitting device can send a probe signal to the receiving device, enabling the receiving device to perform channel assessment, determine modulation parameters, and send them to the transmitting device.

[0153] In some embodiments, DM 122 may send information to the transmitting device regarding the timing of a transmission that covers a first time window. In some embodiments, DM 122 may receive a fifth request from the transmitting device to exit the first mode. In some embodiments, DM 122 may send an affirmative response to the fifth request to the transmitting device.

[0154] The above is about Figure 9 The description of processing and Figures 3 to 6 The corresponding operations are described in the documentation; other details can be found in the documentation. Figures 3 to 6 The relevant descriptions will not be repeated here. According to Figure 9 This method enables PLC IoT network nodes to control data transmission under RBM. Compared to the ROBO mode, it significantly improves transmission performance per unit resource through collaboration between the physical layer and MAC layer, locking the physical layer time slot for data stream transmission.

[0155] In summary, the scheme according to the embodiments of this disclosure introduces RBM for IoT data transmission. Under RBM, the transmitting and receiving devices perform data transmission based on at least one time window within the power line communication cycle. This achieves high rate performance with minimal resources, approaching the resource utilization efficiency of broadband nodes in communication. Consequently, it improves the rate performance and resource utilization efficiency of each node in the PLC broadband and PLC IoT converged network.

[0156] Corresponding to the methods described above, embodiments of this disclosure also provide apparatus and devices for PLCs used in IoT, which are described below in conjunction with... Figures 10 to 13 This will be described. Figure 10 A schematic block diagram of a PLC for IoT implemented at a transmitting device according to an embodiment of the present disclosure is shown. The device 1000 can be located at a transmitting device (e.g., in a PLC IoT network) in a transmitting device... Figure 1 This is implemented at IoT-SDM 121, IoT terminal node 101, or IoT relay node 111. For convenience, the following description combines... Figure 1 Example pair Figure 10 The following description is provided. Device 1000 may be part of the transmitting device or the transmitting device itself. It should be understood that device 1000 may include more additional components than those shown, or may omit some of the components shown; this disclosure does not limit the scope of the invention.

[0157] like Figure 10As shown, the apparatus 1000 includes a first request receiving unit 1010, a probe signal transmitting unit 1020, a modulation parameter receiving unit 1030, and a first data transmission unit 1040. The first request receiving unit 1010 is configured to receive a first request from a receiving device, the first request requesting channel evaluation to be performed for a first time window in a power line communication cycle. The probe signal transmitting unit 1020 is configured to transmit a probe signal required for performing channel evaluation to the receiving device in response to the first request. The modulation parameter receiving unit 1030 is configured to receive modulation parameters from the receiving device, the modulation parameters being determined by performing channel evaluation based on the probe signal. The first data transmission unit 1040 is configured to transmit data with the receiving device within the first time window based on the modulation parameters.

[0158] In some embodiments, the first request receiving unit 1010 may include a first notification sending unit and a request receiving unit. The notification sending unit may be configured to send a first notification to the receiving device indicating entry into a first mode, in which the sending device and the receiving device perform data transmission based on at least one time window within a power line communication cycle. The request receiving unit may be configured to receive a first request sent by the receiving device in response to the first notification. In some embodiments, the first mode is RBM (Remote Power Line Communication).

[0159] In some embodiments, the notification sending unit may be configured to send a second request to the control device for entering a first mode in response to a data transmission rate exceeding a predetermined threshold rate, and to send a first notification to the receiving device in response to receiving a positive response from the control device for the second request. In some alternative embodiments, the notification sending unit may be configured to send a second request to the control device for entering a first mode in response to receiving a first instruction to enter the first mode, and to send a first notification to the receiving device in response to receiving a positive response from the control device for the second request.

[0160] In some embodiments, the probe signal transmitting unit 1020 may include a first transmitting unit, a second transmitting unit, and a third transmitting unit. The first transmitting unit may be configured to send a third request to a control device for resource allocation of the probe signal, the third request including information about the first time window. The second transmitting unit may be configured to send an affirmative response to the first request to a receiving device in response to receiving information about resource allocation from the control device. The third transmitting unit is configured to send the probe signal to the receiving device based on the information about resource allocation in response to receiving a fourth request from the receiving device for transmitting the probe signal.

[0161] In some embodiments, the first data transmission unit 1040 may include a transmission timing receiving unit and a data transmission unit. The transmission timing receiving unit may be configured to receive information about the transmission timing from a control device, the transmission timing covering the first time window. The data transmission unit may be configured to transmit data with a receiving device using the modulation parameters during the transmission timing. In some embodiments, the first data transmission unit 1040 may further include a transmission timing sending unit configured to send information about the transmission timing to the receiving device.

[0162] In some embodiments, the apparatus 1000 may further include a second notification sending unit configured to send a second notification to the receiving device to exit the first mode. In some embodiments, the second notification sending unit may be configured to send a fifth request to the control device to exit the first mode in response to a data transmission rate less than a predetermined threshold rate, and to send a second notification to the receiving device in response to receiving a positive response from the control device to the fifth request. In some alternative embodiments, the second notification sending unit may be configured to send a fifth request to the control device to exit the first mode in response to receiving a second instruction to exit the first mode, and to send a second notification to the receiving device in response to receiving a positive response from the control device to the fifth request.

[0163] In some embodiments, the apparatus 1000 may further include a modulation parameter release unit configured to release modulation parameters in response to receiving an affirmative response from a control device to a fifth request.

[0164] Figure 11 A schematic block diagram of a PLC for IoT implemented at a receiving device according to an embodiment of the present disclosure is shown. The device 1100 can be implemented at a receiving device (e.g., in a PLC IoT network) in a receiving device... Figure 1 This is implemented at IoT-SDM 121, IoT terminal node 101, or IoT relay node 111. For convenience, the following description combines... Figure 1 Example pair Figure 11 The following description is provided. Device 1100 may be part of a receiving device or the receiving device itself. It should be understood that device 1100 may include more additional components than those shown, or may omit some of the components shown; this disclosure does not limit the scope of the invention.

[0165] like Figure 11As shown, the apparatus 1100 includes a first request sending unit 1110, a probe signal receiving unit 1120, a modulation parameter sending unit 1130, and a second data transmission unit 1140. The first request sending unit 1110 is configured to send a first request to a transmitting device, the first request requesting channel evaluation to be performed for a first time window in a power line communication cycle. The probe signal receiving unit 1120 is configured to receive a probe signal sent by the transmitting device in response to the first request, required for performing channel evaluation. The modulation parameter sending unit 1130 is configured to send modulation parameters to the transmitting device, the modulation parameters being determined by performing channel evaluation based on the probe signal. The second data transmission unit 1140 is configured to perform data transmission with the transmitting device based on the modulation parameters within the first time window.

[0166] In some embodiments, the first request sending unit 1110 may include a notification receiving unit and a request sending unit. The notification receiving unit may be configured to receive a first notification from a transmitting device indicating entry into a first mode, in which the transmitting device and the receiving device perform data transmission based on at least one time window within a power line communication cycle. The request sending unit may be configured to send a first request to the transmitting device in response to the first notification. In some embodiments, the first mode is RBM.

[0167] In some embodiments, the probe signal receiving unit 1120 may include a first receiving unit, a transmitting unit, and a second receiving unit. The first receiving unit may be configured to receive a positive response from the transmitting device in response to a first request. The transmitting unit may be configured to send a fourth request to the transmitting device for transmitting a probe signal in response to the positive response. The second receiving unit may be configured to receive the probe signal sent by the transmitting device in response to the fourth request.

[0168] In some embodiments, the second data transmission unit 1140 may include a transmission timing receiving unit and a data transmission unit. The transmission timing receiving unit may be configured to receive information from the transmitting device regarding the transmission timing, which covers a first time window. The data transmission unit may be configured to perform data transmission based on the transmission timing.

[0169] In some embodiments, the apparatus 1100 may further include a second notification receiving unit and a modulation parameter release unit. The second notification receiving unit may be configured to receive a second notification from the transmitting device to exit the first mode. The modulation parameter release unit may be configured to release modulation parameters in response to the second notification.

[0170] Figure 12A schematic block diagram of a PLC for IoT implemented at a control device according to an embodiment of the present disclosure is shown. The device 1200 can be used in a PLC IoT network to control devices (e.g.,...). Figure 1 Implemented at DM 122). For convenience, the following is combined with... Figure 1 Example pair Figure 12 The following description is provided. Device 1200 may be part of DM 122 or DM 122 itself. It should be understood that device 1200 may include more additional components than those shown or omit some of the components shown, and this disclosure does not limit the scope of the invention.

[0171] like Figure 12 As shown, the apparatus 1200 includes a third request receiving unit 1210 and a resource allocation unit 1220. The third request receiving unit 1210 is configured to receive a third request from a transmitting device for resource allocation of a probe signal, the third request including information about a first time window in a power line communication cycle. The third request is sent by the transmitting device in response to a first request from a receiving device, the first request requesting channel evaluation for the first time window. The resource allocation unit 1220 is configured to send information about the resource allocation to the transmitting device.

[0172] In some embodiments, the apparatus 1200 may further include a second request receiving unit and a first response sending unit. The second request receiving unit may be configured to receive a second request from a transmitting device for entering a first mode, in which the transmitting device and the receiving device perform data transmission based on at least one time window within the power line communication cycle. The response sending unit may be configured to send an affirmative response to the second request to the transmitting device, thereby sending a first notification of entering the first mode to the receiving device. In some embodiments, the first mode is RBM.

[0173] In some embodiments, the apparatus 1200 may further include a transmission timing sending unit configured to send information about transmission timing to the transmitting device, the transmission timing covering the first time window. In some embodiments, the apparatus 1200 may further include a fifth request receiving unit and a second response sending unit. The fifth request receiving unit may be configured to receive a fifth request from the transmitting device for exiting the first mode. The second response sending unit may be configured to send an affirmative response to the fifth request.

[0174] Figure 13 This is a simplified block diagram of a device 1300 suitable for implementing embodiments of the present disclosure. The device 1300 can be provided to implement a PLC IoT communication device (transmitting or receiving device) or a control device, such as... Figure 1 Any one of the following devices shown: IoT-SDM 121, DM122, IoT terminal node 101, and IoT relay node 111. As shown, device 1300 includes at least one processor 1310 and at least one PLC interface 1320 coupled to the at least one processor 1310. PLC interface 1320 may include a power plug interface 1321, an analog front end (AFE) 1322, and a digital front end (DFE) 1323.

[0175] The power plug interface 1321 can be coupled to an external power plug. This power plug interface can represent any interface required by the PLC. The AFE 1322 may include analog signal processing elements, and the DFE 1323 may include digital signal processing elements.

[0176] Processor 1310 can be of any type suitable for a local technology network, and by way of limiting examples, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor, and processor based on a multi-core processor architecture. Device 1300 can have multiple processors, such as application-specific integrated circuit chips, which are time-subordinate to a clock synchronized with the main processor.

[0177] The processor 1310 can be operated to implement embodiments of the present disclosure via the PLC interface 1320, causing the device 1300 to perform as described in the reference. Figures 3 to 12 The processing discussed in this disclosure. Device 1300 may correspond to the aforementioned apparatus 1000, apparatus 1100, or apparatus 1200, and each functional module in apparatus 1000, apparatus 1100, or apparatus 1200 may be implemented by processor 1310 in conjunction with PLC interface 1320. Embodiments of this disclosure may also be implemented by software or by a combination of software and hardware.

[0178] In some embodiments, device 1300 may further include memory (not shown). Memory may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM), electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) and other volatile memories that do not persist during power-off periods. The computer program includes computer-executable instructions that are executed by the associated processor 1310. The program may be stored in memory. Processor 1310 can perform any suitable actions and processes by loading the program into memory.

[0179] In general, the various exemplary embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. When aspects of embodiments of this disclosure are illustrated or described as block diagrams, flowcharts, or using some other graphical representation, it will be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented as non-limiting examples in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof. Examples of hardware devices that can be used to implement embodiments of this disclosure include, but are not limited to, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0180] As an example, embodiments of this disclosure can be described in the context of machine-executable instructions, such as program modules that execute on a device running on a real or virtual processor of the target. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc., which perform a specific task or implement a specific abstract data structure. In various embodiments, the functionality of program modules may be combined or divided among the described program modules. The machine-executable instructions for a program module may execute within a local or distributed device. In a distributed device, the program module may reside on both local and remote storage media.

[0181] Computer program code used to implement the methods of this disclosure may be written in one or more programming languages. This computer program code may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, such that when executed by the computer or other programmable data processing apparatus, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be performed. The program code may be executed entirely on a computer, partially on a computer, as a stand-alone software package, partially on a computer and partially on a remote computer, or entirely on a remote computer or server.

[0182] In the context of this disclosure, computer program code or related data may be carried on any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, and the like.

[0183] Examples of signals may include electrical, optical, radio, sound, or other forms of propagation signals, such as carrier waves, infrared signals, etc.

[0184] A machine-readable medium can be any tangible medium that contains or stores programs for or relating to an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More detailed examples of machine-readable storage media include electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0185] Furthermore, although the operations are depicted in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or in a sequential order, or to execute all illustrated operations to obtain the desired result. In some cases, multitasking or parallel processing may be beneficial. Similarly, although the foregoing discussion includes certain specific implementation details, this should not be construed as limiting the scope of any invention or claim, but rather as a description of specific embodiments that may be implemented with respect to a particular invention. Certain features described in this specification in the context of separate embodiments may also be implemented in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination.

[0186] Although the subject matter has been described in language specific to structural features and / or methodological actions, it should be understood that the subject matter defined in the appended claims is not limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A method for power line communication for Internet of Things, characterized in that, comprising: a transmitting device sending a first notification to a receiving device to enter a first mode in which the transmitting device and the receiving device perform data transmission based on at least one time window in a power line communication period; and the transmitting device receiving a first request sent by the receiving device in response to the first notification, the first request being for requesting to perform a channel assessment for a first time window in the power line communication period; in response to the first request, the transmitting device sending a probe signal to the receiving device for performing the channel assessment; the transmitting device receiving a modulation parameter from the receiving device, the modulation parameter being determined by performing the channel assessment based on the probe signal; and the transmitting device performing the data transmission with the receiving device on the first time window based on the modulation parameter. the first mode is a rate boost mode (RBM).

2. The method of claim 1, wherein, sending the first notification comprises:

3. The method of claim 1, wherein, in response to a rate of the data transmission being greater than a predetermined threshold rate, the transmitting device sending a second request to a control device for entering the first mode; and in response to receiving a positive response from the control device for the second request, the transmitting device sending the first notification to the receiving device. sending the first notification comprises:

4. The method of claim 1, wherein, in response to receiving a first instruction to enter the first mode, the transmitting device sending a second request to a control device for entering the first mode; and in response to receiving a positive response from the control device for the second request, the transmitting device sending the first notification to the receiving device. sending the probe signal comprises:

5. The method of claim 1, wherein, the transmitting device sending a third request to a control device for resource allocation of a probe signal, the third request including information about the first time window; in response to receiving information about the resource allocation from the control device, the transmitting device sending a positive response to the receiving device for the first request; and in response to receiving a fourth request from the receiving device for sending a probe signal, the transmitting device sending the probe signal to the receiving device based on the information about the resource allocation. performing the data transmission comprises:

6. The method of claim 1, wherein, the transmitting device receiving information about a transmission opportunity from a control device, the transmission opportunity covering the first time window; and the transmitting device performing the data transmission with the receiving device on the transmission opportunity using the modulation parameter. further comprising:

7. The method of claim 6, wherein, the transmitting device sending the information about the transmission opportunity to the receiving device. further comprising:

8. The method of claim 1, wherein, the transmitting device sending a second notification to the receiving device to exit the first mode. sending the second notification comprises:

9. The method of claim 8, wherein, in response to a rate of the data transmission being less than a predetermined threshold rate, the transmitting device sending a fifth request to a control device for exiting the first mode; and in response to receiving a positive response from the control device for the fifth request, the transmitting device sending the second notification to the receiving device. sending the second notification comprises:

10. The method of claim 8, wherein, ​ in response to receiving a second instruction for exiting the first mode, the sending device sends to a control device a fifth request for exiting the first mode; and in response to receiving a positive response from the control device to the fifth request, the sending device sends to the receiving device the second notification.

11. The method according to claim 9 or 10, characterized in that, Further comprising: in response to receiving a positive response from the control device to the fifth request, the sending device releases the modulation parameters.

12. The method of claim 3, wherein, The sending device is an Internet of Things sub-domain node, the receiving device is an Internet of Things terminal node, and the control device is a power line communication network master node.

13. The method of claim 3, wherein, The sending device is an Internet of Things terminal device, the receiving device is an Internet of Things sub-domain node, and the control device is a power line communication network master node.

14. A method for power line communication for Internet of Things, characterized in that, Comprising: a receiving device receives from a sending device a first notification to enter a first mode in which the sending device and the receiving device perform data transmission based on at least one time window in a power line communication cycle; in response to the first notification, the receiving device sends to the sending device a first request for requesting to perform a channel assessment for a first time window in the power line communication cycle; the receiving device receives a probe signal required for performing the channel assessment sent by the sending device in response to the first request; the receiving device sends to the sending device modulation parameters determined by performing the channel assessment based on the probe signal; and the receiving device and the sending device perform data transmission based on the modulation parameters on the first time window.

15. The method of claim 14, wherein, The first mode is a rate boost mode (RBM).

16. The method of claim 14, wherein, Receiving the probe signal comprises: the receiving device receives from the sending device a positive response to the first request; in response to the positive response, the receiving device sends to the sending device a fourth request for sending a probe signal; and the receiving device receives the probe signal sent by the sending device in response to the fourth request.

17. The method of claim 14, wherein, Performing the data transmission comprises: the receiving device receives from the sending device information about a transmission opportunity, the transmission opportunity covering the first time window; and the receiving device performs the data transmission based on the transmission opportunity.

18. The method of claim 14, wherein, Further comprising: the receiving device receives from the sending device a second notification to exit the first mode; and in response to the second notification, the receiving device releases the modulation parameters.

19. The method of claim 14, wherein, The sending device is an Internet of Things gateway, and the receiving device is an Internet of Things terminal node.

20. The method of claim 14, wherein, The sending device is an Internet of Things terminal device, and the receiving device is an Internet of Things sub-domain node.

21. A method for power line communication for Internet of Things, characterized in that, Comprising: a control device receives from a sending device a second request for entering a first mode in which the sending device and a receiving device perform data transmission based on at least one time window in a power line communication cycle; the control device sends to the sending device a positive response to the second request so that the sending device sends to the receiving device a first notification to enter the first mode; The control device receives a third request for resource allocation of a probe signal from the transmitting device, the third request comprising information about a first time window in the power line communication cycle, the third request being sent by the transmitting device in response to a first request from the receiving device, the first request being for requesting performing channel assessment for the first time window; and The control device sends information about the resource allocation to the transmitting device.

22. The method of claim 21, wherein, The first mode is a rate boost mode, RBM.

23. The method of claim 21, wherein, Further comprising: The control device sends information about a transmission occasion to the transmitting device, the transmission occasion covering the first time window.

24. The method of claim 21, wherein, Further comprising: The control device receives a fifth request from the transmitting device for exiting the first mode; and The control device sends a positive response to the fifth request to the transmitting device.

25. The method of claim 21, wherein, The transmitting device is an Internet of Things gateway, the receiving device is an Internet of Things terminal device, and the control device is a power line communication network master node.

26. The method of claim 21, wherein, The transmitting device is an Internet of Things terminal device, the receiving device is an Internet of Things gateway, and the control device is a power line communication network master node.

27. A communication apparatus for power line communication of Internet of Things, characterized in that, Comprising: a processor; and a power line communication interface coupled to the processor, wherein the processor is configured to: send, to a receiving device via a power line communication interface, a first notification to enter a first mode in which the communication apparatus and the receiving device perform data transmission based on at least one time window in a power line communication cycle; receive, via the power line communication interface, a first request sent by the receiving device in response to the first notification, the first request being for requesting performing channel assessment for a first time window in the power line communication cycle; in response to the first request, send, to the receiving device via the power line communication interface, a probe signal required for performing the channel assessment; receive, from the receiving device via the power line communication interface, a modulation parameter determined by performing the channel assessment based on the probe signal; and perform data transmission with the receiving device based on the modulation parameter and on the first time window via the power line communication interface. The processor is further configured to:

28. The communication apparatus according to claim 27, wherein send, to the receiving device via the power line communication interface, a second notification to exit the first mode. The communication apparatus is an Internet of Things sub-domain node, and the receiving device is an Internet of Things terminal node.

29. The communication apparatus according to claim 27, wherein The communication apparatus is an Internet of Things terminal node, and the receiving device is an Internet of Things sub-domain node.

30. The communication apparatus of claim 27, wherein Comprising:

31. A communication apparatus for power line communication of Internet of Things, characterized in that, a processor; and a power line communication interface coupled to the processor, wherein the processor is configured to: receive, from a transmitting device via a power line communication interface, a first notification to enter a first mode in which the transmitting device and the communication apparatus perform data transmission based on at least one time window in a power line communication cycle; ​ ​ in response to the first notification, sending, by the power line communication interface, a first request to the transmitting device, the first request being for requesting performing channel assessment for a first time window in the power line communication cycle; receiving, by the power line communication interface, a probe signal transmitted by the transmitting device in response to the first request, the probe signal being required for performing the channel assessment; sending, by the power line communication interface, modulation parameters to the transmitting device, the modulation parameters being determined by performing the channel assessment based on the probe signal; and performing, by the power line communication interface, data transmission with the transmitting device based on the modulation parameters on the first time window.

32. The communication apparatus of claim 31, wherein the processor is configured to send the first request by: receiving, by the power line communication interface, a first notification from the transmitting device to enter a first mode in which the transmitting device and the communication apparatus perform data transmission based on at least one time window in the power line communication cycle; and in response to the first notification, sending, by the power line communication interface, the first request to the transmitting device. the processor is further configured to:

33. The communication apparatus of claim 32, wherein receive, by the power line communication interface, a second notification from the transmitting device to exit the first mode; and in response to the second notification, release the modulation parameters. the transmitting device is an Internet of Things sub-domain node, and the communication apparatus is an Internet of Things terminal node.

34. The communication apparatus of claim 31, wherein the transmitting device is an Internet of Things terminal node, and the communication apparatus is an Internet of Things sub-domain node.

35. The communication apparatus of claim 31, wherein comprise:

36. A control device for power line communication of an Internet of Things, characterized in that, a processor; and a power line communication interface coupled to the processor, wherein the processor is configured to: receive, by the power line communication interface, a second request from the transmitting device to enter a first mode in which the transmitting device and the receiving device perform data transmission based on at least one time window in a power line communication cycle; send, by the power line communication interface, a positive response to the second request to the transmitting device so that the transmitting device sends a first notification to the receiving device to enter the first mode; receive, by the power line communication interface, a third request from the transmitting device for resource allocation of a probe signal, the third request including information about a first time window in the power line communication cycle, the third request being sent by the transmitting device in response to a first request from the receiving device, the first request being for requesting performing channel assessment for the first time window; and send, by the power line communication interface, information about the resource allocation to the transmitting device. the processor is further configured to: receive, by the power line communication interface, a fifth request from the transmitting device to exit the first mode; and 37. The control device of claim 36, wherein, send, by the power line communication interface, a positive response to the fifth request to the transmitting device. the transmitting device is an Internet of Things sub-domain node, the receiving device is an Internet of Things terminal node, and the control device is a master node of a power line communication network. ​ 38. The control device of claim 36, wherein, ​ 39. The control device of claim 36, wherein, The sending device is an Internet of Things terminal node, the receiving device is an Internet of Things sub-domain node, and the control device is a power line communication network master node.

40. A system for power line communication for Internet of Things, characterized by, Comprising: The communication device according to any one of claims 27 to 30; The communication device according to any one of claims 31 to 35; And The control device according to any one of claims 36 to 39.

41. A computer-readable storage medium, comprising: Machine executable instructions comprising, which when executed by a device, cause the device to perform the method of any one of claims 1-26.

Images