WO2022183510A1 - 用于物联网的电力线通信的方法、装置和系统 - Google Patents

用于物联网的电力线通信的方法、装置和系统 Download PDF

Info

Publication number
WO2022183510A1
WO2022183510A1 PCT/CN2021/079407 CN2021079407W WO2022183510A1 WO 2022183510 A1 WO2022183510 A1 WO 2022183510A1 CN 2021079407 W CN2021079407 W CN 2021079407W WO 2022183510 A1 WO2022183510 A1 WO 2022183510A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
iot
receiving
power line
sending
Prior art date
Application number
PCT/CN2021/079407
Other languages
English (en)
French (fr)
Inventor
潘稻
林泽锋
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21928591.3A priority Critical patent/EP4300836A4/en
Priority to PCT/CN2021/079407 priority patent/WO2022183510A1/zh
Priority to CN202180094881.6A priority patent/CN116888897A/zh
Publication of WO2022183510A1 publication Critical patent/WO2022183510A1/zh
Priority to US18/460,819 priority patent/US20230412210A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B3/00—Line transmission systems
    • H04B3/54—Systems for transmission via power distribution lines
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B3/00—Line transmission systems
    • H04B3/02—Details
    • H04B3/04—Control of transmission; Equalising
    • H04B3/10—Control of transmission; Equalising by pilot signal

Definitions

  • the present application relates to the field of Power Line Communication (PLC, Power Line Communication), and in particular to a method, device and system for power line communication for the Internet of Things (IoT, Internet of Things).
  • PLC Power Line Communication
  • IoT Internet of Things
  • PLC refers to the use of power lines to transmit data or information by digital signal processing.
  • PLC broadband technology uses low frequency power lines to send broadband data. Because it basically does not need to re-lay network lines and covers a much larger area than other types of carrier lines, PLC broadband technology has been widely used in various networks such as home networks and industrial networks. With the recent development of IoT technology, PLC IoT technology is also widely used in applications such as industrial networks such as smart grids. PLC IoT technology refers to the use of power lines to realize communication between IoT nodes. Recently, attempts have been made to apply PLC IoT to smart home applications, so the integration of PLC broadband network and PLC IoT network has gradually become a rigid requirement. In this converged network, PLC broadband communication and PLC IoT communication work in the same powerline network, and use the same medium and share physical layer transmission resources.
  • 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).
  • IoT nodes have less data traffic per node, the number of nodes is large, resulting in a large total cost of IoT applications.
  • due to the low rate achievable by IoT technology many resources are occupied, which squeezes the number of communication resources that can be used by broadband nodes, and greatly reduces the rate achievable by broadband nodes.
  • the bandwidth requirements of IoT nodes are also 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.
  • Embodiments of the present disclosure provide a power line communication solution for the Internet of Things, which can improve the communication performance of each node in such a converged network.
  • a method for power line communication for the Internet of Things includes: a sending device receiving a first request from a receiving device, the first request requesting to perform channel assessment for a first time window in a power line communication cycle; in response to the first request, the sending device to The receiving device transmits a sounding signal required to perform the channel evaluation; the transmitting device receives modulation parameters from the receiving device, the modulation parameters determined by performing the channel evaluation based on the sounding signal ; and the transmitting device performs data transmission with the receiving device on the first time window based on the modulation parameter.
  • a method of power line communication for the Internet of Things includes: a receiving device sending a first request to a sending device, the first request being used to request to perform channel evaluation for a first time window in a power line communication cycle; the receiving device receiving a response from the sending device to the first time window a request to send a sounding signal needed to perform the channel evaluation; the receiving device sends modulation parameters to the transmitting device, the modulation parameters determined by performing the channel evaluation based on the sounding signal ; and the receiving device and the sending device perform data transmission based on the modulation parameter on the first time window.
  • a method for power line communication for the Internet of Things includes the control device receiving a third request for resource allocation of the sounding signal from the transmitting device, the third request including information about a first time window in a power line communication cycle, the third request being made by the is sent by the sending device in response to a first request from a receiving device, the first request is for requesting to perform channel evaluation for the first time window; and the control device sends information about the resource to the sending device assigned information.
  • a communication device for power line communication of the Internet of Things includes: a processor; and a power line communication interface coupled to the processor.
  • the processor is configured to: receive, over the power line communication interface, a first request from a receiving device, the first request requesting to perform a channel evaluation for a first time window in a power line communication cycle; in response to the first request a request to send a probe signal needed to perform the channel evaluation to the receiving device through the power line communication interface; and to receive modulation parameters from the receiving device through the power line communication interface, the modulation parameters being The probe signal is determined by performing the channel evaluation; and based on the modulation parameter and over the first time window, data transmission is performed with the receiving device through the power line communication interface.
  • a communication device for power line communication of the Internet of Things includes: a processor; and a power line communication interface coupled to the processor.
  • the processor is configured to: send a first request to a sending device over the power line communication interface, the first request requesting to perform a channel evaluation for a first time window in a power line communication cycle; over the power line communication interface receiving a probe signal sent by the sending device in response to the first request for performing the channel evaluation; sending modulation parameters to the sending device through the power line communication interface, the modulation parameters are The probe signal is determined by performing the channel evaluation; and data transmission is performed with the transmitting device over the first time window based on the modulation parameter through the power line communication interface.
  • a control device for power line communication of the Internet of Things.
  • the control device includes: a processor; and a power line communication interface coupled to the processor.
  • the processor is configured to receive, over 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 is sent by the sending device in response to a first request from a receiving device, the first request requesting to perform a channel evaluation for the first time window; and through the power line communication interface Information about the resource allocation is sent to the sending device.
  • an apparatus for power line communication of the Internet of Things includes: a first request receiving unit, configured for a sending device to receive a first request from a receiving device, the first request being used to request to perform channel evaluation for a first time window in a power line communication cycle; sounding signal sending a unit configured for, in response to the first request, the sending device to send a sounding signal required for performing the channel evaluation to the receiving device; a modulation parameter receiving unit configured for the sending device receiving a modulation parameter from the receiving device, the modulation parameter being determined by performing the channel evaluation based on the sounding signal; and a first data transmission unit configured for the sending device to, based on the modulation parameter, performing data transmission with the receiving device over the first time window.
  • an apparatus for power line communication of the Internet of Things includes: a first request sending unit configured for the receiving device to send a first request to the sending device, the first request being used for requesting to perform channel evaluation for a first time window in a power line communication cycle; a sounding signal receiving unit , configured for the receiving device to receive the sounding signal required for performing the channel evaluation sent by the sending device in response to the first request; a modulation parameter sending unit, configured for the receiving device sending modulation parameters to the sending device, the modulation parameters determined by performing the channel assessment based on the sounding signal; and a second data transmission unit configured for the receiving device to communicate with the sending device Data transmission is performed on the first time window based on the modulation parameter.
  • an apparatus for power line communication of the Internet of Things includes: a third request receiving unit configured for the control device to receive a third request for resource allocation of the sounding signal from the transmitting device, the third request including a request for a first time window in the power line communication cycle information, the third request is sent by the sending device in response to a first request from a receiving device, the first request requesting to perform channel evaluation for the first time window; and a resource allocation unit, is configured for the control device to send information about the resource allocation to the sending device.
  • a system for power line communication of the Internet of Things includes the communication device of the aforementioned fourth and fifth aspects and the control device of the aforementioned sixth aspect.
  • a chip including a processor and a front-end circuit, the processor and the front-end circuit operating together to perform the method in the aforementioned first aspect, second aspect or third aspect.
  • a computer-readable storage medium comprises machine-executable instructions that, when executed by an apparatus, cause the apparatus to perform a method according to the first, second or third aspects.
  • the computer program product comprises computer program code which, when executed by an apparatus, causes the apparatus to perform the method according to the first aspect, the second aspect or the third aspect.
  • the rate performance and resource utilization efficiency of both the PLC IoT service and the PLC broadband service can be greatly improved with limited complexity improvement.
  • FIG. 1 shows a schematic diagram of an example PLC network in which embodiments of the present disclosure may be implemented
  • FIG. 2A shows a schematic diagram of selecting a time window in a rate boost mode (RBM, Rate Boost Mode) according to an embodiment of the present disclosure
  • TXOP Transmission Opportunity allocation under non-RBM according to an embodiment of the present disclosure
  • FIG. 2C shows a schematic diagram of TXOP allocation under RBM according to an embodiment of the present disclosure
  • FIG. 3 shows a schematic diagram of a process of entering an RBM in a downlink direction according to an embodiment of the present disclosure
  • FIG. 4 shows a schematic diagram of a process of entering an RBM in an uplink direction according to an embodiment of the present disclosure
  • FIG. 5 shows a schematic diagram of a process of exiting an RBM according to an embodiment of the present disclosure
  • FIG. 6 shows a schematic diagram of another process of entering an RBM in a downlink direction according to an embodiment of the present disclosure
  • FIG. 7 shows a flowchart of a method for PLC for IoT implemented at a sending device according to an embodiment of the present disclosure
  • FIG. 8 shows a flowchart of a method for PLC for IoT implemented at a receiving device according to an embodiment of the present disclosure
  • FIG. 9 shows a flowchart of a method for controlling a PLC for IoT implemented at a device according to an embodiment of the present disclosure
  • FIG. 10 shows a schematic block diagram of an apparatus for PLC for IoT implemented at a sending device according to an embodiment of the present disclosure
  • FIG. 11 shows a schematic block diagram of an apparatus for PLC for IoT implemented at a receiving device according to an embodiment of the present disclosure
  • FIG. 12 shows a schematic block diagram of an apparatus for PLC for IoT implemented at a control device according to an embodiment of the present disclosure.
  • FIG. 13 shows a simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure.
  • the term “including” and variations thereof are open inclusive, ie “including but not limited to”.
  • the term “based on” is “based at least in part on.”
  • the term “one embodiment” means “at least one embodiment”; the term “another embodiment” means “at least one additional embodiment”. Relevant definitions of other terms will be given in the description below.
  • circuit refers to one or more of the following:
  • a combination of hardware circuits and software such as (if applicable): (i) a combination of analog and/or digital hardware circuits and software/firmware, and (ii) any portion of a hardware processor and software (including working together to digital signal processors, software, and memory that enable devices, such as optical line terminals (OLTs) or other computing devices, to perform various functions); and
  • Hardware circuits and/or processors such as a microprocessor or portion of a microprocessor, that require software (eg, firmware) for operation, but may be absent when software is not required for operation.
  • software eg, firmware
  • circuitry as used herein also covers an implementation of only a hardware circuit or processor (or processors), or a portion of a hardware circuit or processor, or its accompanying software or firmware.
  • circuitry also covers a baseband integrated circuit or a processor integrated circuit or similar integrated circuit in an OLT or other computing device.
  • PLC network refers to any network that utilizes power lines to transmit data or information in digital signal processing methods.
  • the network can be used in conjunction with wired networks such as Digital Subscriber Line technology (DSL) using telephone lines and Cable Modem (CM, Cable Modem) using coaxial cable lines using cable television, or with cable networks such as Wi-Fi, Bluetooth and other wireless networks are used in combination.
  • DSL Digital Subscriber Line technology
  • CM Cable Modem
  • Wi-Fi Wireless Fidelity
  • Bluetooth wireless networks
  • PLC network master node (DM, Domain Master) refers to the master node in the PLC network, which is responsible for access, authentication, and resource time slot scheduling and allocation of other nodes in the PLC network.
  • PLC broadband node refers to any terminal device capable of broadband communication through a PLC.
  • the terminal device may have wireless or wired communication capabilities.
  • end devices include, but are limited to, Customer Premise Equipment (CPE), User Equipment (UE), Personal Computers, Desktop Computers, Mobile Phones, Cell Phones, Smartphones, Personal Digital Assistants (PDAs), Portable Computers, Tablets, Wearables devices, Internet of Things (IoT) devices, Machine Type Communication (MTC) devices, in-vehicle devices for V2X (X means pedestrian, vehicle or infrastructure/network) communication, or image capture devices such as digital cameras, games devices, music storage and playback devices, or Internet devices capable of wireless or wired Internet access and browsing, etc.
  • CPE Customer Premise Equipment
  • UE User Equipment
  • PDAs Personal Digital Assistants
  • IoT Internet of Things
  • MTC Machine Type Communication
  • V2X means pedestrian, vehicle or infrastructure/network
  • image capture devices such as digital cameras, games devices, music storage and playback devices
  • Internet devices capable
  • IoT sub-domain refers to a sub-network of IoT nodes in a PLC network.
  • IoT-Subdomain Master (IoT-SDM, IoT-Subdomain Master) refers to a node that manages or coordinates data transfer in an IoT subdomain.
  • IoT node or “IoT end node” may be an IoT end device with PLC capabilities, such as smart home appliances, smart meters, wearable devices, and the like.
  • IoT relay node refers to the repeater in the above-mentioned IoT sub-domain, which is connected with IoT-SDM to extend the distance of network transmission.
  • FIG. 1 shows a schematic diagram of an example PLC network 100 in which embodiments of the present disclosure may be implemented.
  • 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 end nodes 101, 102, and 103 may communicate with IoT-SDM 121 via IoT relay node 111, and IoT-SDM 121 communicates with a remote server (not shown) external to PLC network 100 via DM 122.
  • IoT end nodes 101, 102 and 103 need to communicate with DM 122 via IoT-SDM 121.
  • the PLC broadband nodes 104 and 105 may communicate with the DM 122 over power line channels to access networks such as the Internet, local area networks, metropolitan area networks, etc. via the DM 122.
  • IoT-SDM 121 and DM 122 may be implemented as separate physical entities.
  • IoT-SDM 121 and DM 122 may be implemented on the same physical entity, as shown at 120 in the figure.
  • IoT relay node 111 is shown in FIG. 1 , in some embodiments PLC network 100 may not include IoT relay node 111 . In this case, IoT end nodes 101 , 102 and 103 can communicate with IoT-SDM 121 directly. Furthermore, it should be understood that the numbers of IoT terminal nodes, PLC broadband nodes and IoT relay nodes are not limited to the example shown in FIG. 1 , but may include any other suitable greater or lesser numbers.
  • the functions of IoT-SDM 121 can be implemented centrally or distributed on any node in the IoT sub-domain, and the functions of DM 122 can be implemented centrally or distributed on any node in the PLC network.
  • the PLC network 100 may include more additional components not shown or some components shown may be omitted, which is not limited by the embodiment of the present disclosure. Implementation of the PLC network 100 is also not limited to the specific examples described above, but may be implemented in any suitable manner.
  • the physical layer technology adopts highly robust communication technologies, such as the Homeplug Green PHY standard and the robust orthogonal frequency used in IEEE 1901.1.
  • Division Multiplexing ROBO, Robust Orthogonal Frequency Division Multiplexing
  • RCM Robust Communication Mode
  • ROBO/RCM mode low-order bit modulation is fixed and repetition coding is used. Thereby, the reliability of transmission can be enhanced for supporting data rates of 4Mbps to 10Mbps.
  • Table 1 below shows examples of parameters in several ROBO modes.
  • PLC wideband technology carrier-based adaptive modulation characteristics are used.
  • the modulation order can be as high as 4096QAM, the rate is high, but the complexity is high, resulting in a small number of supported nodes.
  • Table 2 below shows an example of parameter comparison between PLC broadband technology and PLC IoT technology.
  • the same medium needs to support several broadband nodes and hundreds of IoT nodes.
  • IoT nodes have less data traffic per node, the number of nodes is large, resulting in a large total cost of IoT applications.
  • due to the low rate that the IoT technology can achieve in the above ROBO mode many resources are occupied. As a result, the number of communication resources available to the broadband node is squeezed, and the rate achievable by the broadband node is greatly reduced.
  • the bandwidth requirements of IoT applications are constantly increasing, not just simple control requirements and intermittent reporting requirements.
  • sensors have ongoing fixed bandwidth requirements, such as 150Kbps per sensor.
  • 40 sensors require a bandwidth of 6 Mbps, which is much larger than the communication bandwidth requirements of a traditional smart grid.
  • an embodiment of the present disclosure proposes an improved PLC solution for IoT.
  • a Rate Boost Mode (RBM, Rate Boost Mode) is introduced.
  • RBM is also referred to herein as the first mode.
  • IoT nodes perform data transmission based on at least one time window in the power line communication cycle. Specifically, by selecting one of the at least one time window, and performing channel evaluation for the selected time window, modulation parameters are determined for data transmission within the selected time window.
  • MAC Medium Access Control
  • the transmission performance per unit resource is greatly improved, and the physical layer time slot position is locked for data stream transmission.
  • MAC Medium Access Control
  • FIG. 2A shows a schematic diagram 200A of selecting a time window under an RBM according to an embodiment of the present disclosure.
  • the power line channel also changes in real time due to the real-time changes in load and noise.
  • the real-time change of the power line channel has the characteristics of an alternating current (AC, Alternate Current) cycle, as shown by 210 in FIG. 2A .
  • the windowing may be performed based on the AC cycle of the power line channel, eg, into 8 time windows 201-208. It should be understood that the number of time windows is not so limited, and any suitable number may be employed.
  • a single time window may be selected for channel evaluation and physical layer transmission parameters for the single time window may be output.
  • the physical layer transmission parameters are also referred to as Bit Allocation Table (BAT, Bit Allocation Table), and each time window is also referred to as a BAT area.
  • BAT Bit Allocation Table
  • a time window 205 may be selected for rate adaptation operation under RBM.
  • BAT In PLC broadband communication, BAT is usually maintained separately for each time window. Since BAT is a carrier level, it takes up a lot of storage space. In addition, the signaling overhead required by the receiving and sending parties to synchronize the BAT is also very large. Therefore, the maintenance of multiple time windows results in double the overhead. In contrast, under the RBM of the embodiment of the present disclosure, since the channel evaluation is performed only for a single time window, the storage and signaling overhead is only a fraction (in this example, 1/8) of the PLC broadband communication. .
  • RBM can greatly improve the communication efficiency under unit resources.
  • Table 3 shows an example of performance comparison of RBM and ROBO modes. where the same bandwidth is assumed.
  • FIG. 2B shows a schematic diagram 200B of TXOP allocation under non-RBM according to an embodiment of the present disclosure.
  • DM under non-RBM, DM usually allocates contention-free time slot (CFTS, Contention-free Time Slot) to IoT nodes from Shared Transmission Opportunity (STXOP, Shared Transmission Opportunity).
  • CFTS contention-free time slot
  • STXOP Shared Transmission Opportunity
  • FIG. 2C shows a schematic diagram 200C of TXOP allocation under RBM according to an embodiment of the present disclosure. As shown in Figure 2C, when entering the RBM, after determining the time window 231 for the IoT node, the DM MAC needs to allocate TXOP resources 232 for the window position.
  • the TXOP resource 232 may be a CFTXOP allocated to the IoT node. In some alternative embodiments, the TXOP resource 232 may be an STXOP, and the IoT node is assigned the highest priority CFTS in the STXOP. In some embodiments, one MAC cycle includes two AC cycles, in which case it may be determined to allocate one or two CFTXOPs or STXOPs to the IoT node according to the bit rate requirement.
  • RBM and ROBO modes may be combined for communication of IoT nodes. For example, in a high-rate scenario (eg, when the transmission rate is higher than a predetermined threshold rate) or under the control of an upper layer, the RBM is entered, and the ROBO mode is used at other times.
  • a sink node is a node that communicates with multiple nodes simultaneously in an IoT tree or star network. For ease of understanding, a more detailed description will be given below with reference to FIGS. 3 to 6 .
  • FIG. 3 shows a schematic diagram of a process 300 for entering an RBM in the downstream direction according to an embodiment of the present disclosure.
  • the downstream direction refers to data transmission from IoT-SDM 121 to IoT end node 101.
  • the IoT-SDM 121 is the transmitting device
  • the IoT terminal node 101 is the receiving device
  • the DM 122 is the controlling device.
  • the process of FIG. 3 may also be applicable to data transfer from IoT-SDM 121 to other IoT end nodes in network 100.
  • the process of FIG. 3 may include other additional processes not shown, or that some of the processes shown may be omitted. The scope of the present disclosure is not limited in this regard.
  • the process 300 of FIG. 3 may include a process 310 of negotiating entry into the RBM, a process 320 of channel assessment, and a process 330 of data transmission (which may also be referred to as a process 330 of resource allocation).
  • IoT-SDM 121 may initiate a process 310 of negotiating entry into the RBM. As shown in FIG. 3, IoT-SDM 121 may send 311 a request for entering the RBM (also referred to herein as a second request for convenience) to DM 122. For example, IoT-SDM 121 may send an RBM_enter.req message to DM 122.
  • RBM_enter.req message may be any other suitable form.
  • IoT-SDM 121 may monitor the rate of data transmission and send the request when the rate of data transmission is greater than a predetermined threshold rate.
  • the predetermined threshold rate may be dynamically configured as desired.
  • the threshold predetermined threshold rate may be pre-configured.
  • IoT-SDM 121 may 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 traffic type indicates high rate data transmission.
  • IoT-SDM 121 may send the request in response to receiving an instruction to enter the RBM (also referred to herein as the first instruction for convenience).
  • the instruction may come from upper layer controls such as the MAC layer, the application layer, or the like. It should be understood that the IoT-SDM 121 may send the request under any other suitable triggering conditions, and is not limited to the above example.
  • the DM 122 may send a negative response to the request (not shown) to the IoT-SDM 121.
  • DM 122 may send an RBM_enter.dec message to IoT-SDM 121.
  • RBM_enter.dec message to IoT-SDM 121.
  • the DM 122 may send 312 a positive response to the request to the IoT-SDM 121.
  • DM 122 may send an RBM_enter.cnf message to IoT-SDM 121.
  • IoT-SDM 121 may send 313 a notification (also referred to herein as a first notification for convenience) of entering the RBM to IoT end node 101 .
  • IoT-SDM 121 may send an RBM_enter.cnf message to IoT end node 101.
  • RBM_enter.cnf message may be sent to IoT end node 101.
  • the embodiment of the present disclosure does not impose any limitation on the form of the message, and may adopt any other suitable form. So far, the process 310 of negotiating to enter the RBM is completed, and the RBM is entered.
  • the IoT end node 101 may initiate a process 320 of channel evaluation. As shown in Figure 3, IoT end node 101 sends 321 a request to IoT-SDM 121 to perform a channel assessment for a single time window (also referred to herein as the first time window for convenience) in the power line communication cycle (For convenience, also referred to herein as the first request). For example, the IoT end node 101 may select a BAT area (ie, a time window) and include information of the selected BAT area (eg, ID, Identity, or the like) in the request. For example, IoT end node 101 may send a CE_Initiation.req message to IoT-SDM 121 as the request. Of course, any other suitable message form can also be used.
  • IoT-SDM 121 may send 322 a request for resource allocation for sounding signals (also referred to herein as a third request for convenience) to DM 122, the request including information about the selected Information on the BAT area.
  • IoT-SDM 121 may send a CE_ProbeSlotAssign.req message to DM 122 as the request.
  • any other suitable message form can also be used.
  • DM 122 may send 323 information about resource allocation to IoT-SDM 121. That is, the DM 122 allocates resources for the sounding signal to the IoT-SDM 121. For example, DM 122 may send a CE_ProbeSlotAssign.cnf message to IoT-SDM 121 to allocate the resource. Of course, any other suitable message form can also be used.
  • IoT-SDM 121 may send 324 a positive response to the first request to IoT end node 101.
  • IoT-SDM 121 may send a CE_Initiation.cnf message to IoT end node 101.
  • any other suitable message form can also be used.
  • IoT end node 101 may send 325 a request to IoT-SDM 121 for sending a probe signal (also referred to herein as a fourth request for convenience).
  • IoT end node 101 may send a CE_ProbeRequest.ind message to IoT-SDM 121 to request the transmission of probe signals.
  • the sounding signal may be a sounding frame (PROBE frame) or a channel training sequence.
  • the detection signal is not limited to this, but can take any other suitable form.
  • IoT-SDM 121 may send 326 a probe to IoT end node 101.
  • the IoT end node 101 can perform channel evaluation to determine modulation parameters.
  • the channel assessment may be implemented in any suitable manner known in the art or developed in the future, without limitation. It should be understood that the IoT end node 101 may require multiple sounding signals to complete the channel assessment. In this case, the process of requesting and sending the probe signal (ie, the processes shown at 325 and 326 ) may need to be performed multiple times.
  • IoT terminal node 101 sends 327 the determined modulation parameters to IoT-SDM 121 for data transmission within the selected time window.
  • the process 320 of channel evaluation is completed.
  • the process 330 of data transmission is entered.
  • DM 122 may send 331 information to IoT-SDM 121 about a transmission opportunity that covers the first time window. For example, DM 122 may generate a new TXOP allocation based on the information of the first time window, and send a MAP message to IoT-SDM 121 that includes the new TXOP allocation.
  • the IoT end node 101 may be assigned the highest priority CFTS at this STXOP.
  • the embodiment of the present disclosure is not limited to this, and any other suitable TXOP allocation manner may also be adopted.
  • the following description takes CFTXOP as an example.
  • IoT-SDM 121 may send 332 the information on transmission occasions to IoT end node 101.
  • IoT-SDM 121 may send an IoT-MAP message to IoT end node 101, the IoT-MAP message including the CFTXOP allocation for IoT-SDM 121.
  • IoT-SDM 121 may use the CFTXOP to perform downlink IoT data transmission 333 with IoT terminal node 101 based on the received modulation parameters.
  • FIG. 4 shows a schematic diagram of a process 400 for entering an RBM in the uplink direction according to an embodiment of the present disclosure.
  • the upstream direction refers to data transmission from IoT terminal node 101 to IoT-SDM 121.
  • the IoT terminal node 101 is the sending device
  • the IoT-SDM 121 is the receiving device
  • the DM 122 is the controlling device.
  • the process of FIG. 4 may also be applicable to data transmission from other IoT end nodes in the network 100 to the IoT-SDM 121.
  • the process of FIG. 4 may include other additional processes not shown, or that some of the processes shown may be omitted. The scope of the present disclosure is not limited in this regard.
  • the process 400 of FIG. 4 may include a process 410 of negotiating entry into the RBM, a process 420 of channel assessment, and a process 430 of data transmission (which may also be referred to as a process 430 of resource allocation).
  • the IoT end node 101 may initiate a process 410 of negotiating entry into the RBM.
  • IoT end node 101 may send a request (also referred to herein as a second request for convenience) to DM 122 via IoT-SDM 121 to enter the RBM.
  • the IoT terminal node 101 may send 411 a request for entering the RBM to the IoT-SDM 121 , and the IoT-SDM 121 forwards 412 the request to the DM 122 .
  • IoT end node 101 may send an RBM_enter.req message to IoT-SDM 121, which forwards the message to DM 122.
  • the embodiment of the present disclosure does not impose any limitation on the form of the message, and may adopt any other suitable form.
  • IoT end node 101 may monitor the rate of data transmission and send the request when the rate of data transmission is greater than a predetermined threshold rate.
  • the predetermined threshold rate may be dynamically configured as desired.
  • the threshold predetermined threshold rate may be pre-configured.
  • the IoT end node 101 may 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 traffic type indicates high rate data transmission.
  • the IoT end node 101 may send the request in response to receiving an instruction to enter the RBM (also referred to herein as the first instruction for convenience).
  • the instruction may come from upper layer controls such as the MAC layer, the application layer, or the like. It should be understood that the IoT terminal node 101 may send the request under any other suitable triggering conditions, and is not limited to the above example.
  • the DM 122 may send a negative response to the request (not shown) to the IoT-SDM 121.
  • DM 122 may send an RBM_enter.dec message to IoT-SDM 121.
  • RBM_enter.dec message to IoT-SDM 121.
  • DM 122 may send 413 a positive response to the request to IoT-SDM 121.
  • DM 122 may send an RBM_enter.cnf message to IoT-SDM 121.
  • RBM_enter.cnf message may be sent to IoT-SDM 121.
  • IoT-SDM 121 in response to receiving the positive response, determines to enter the RBM, and may initiate a process 420 of channel evaluation.
  • IoT-SDM 121 sends 421 a request to IoT end node 101 to perform channel evaluation for a single time window (also referred to herein as the first time window for convenience) in the power line communication cycle (For convenience, also referred to herein as the first request).
  • IoT-SDM 121 may select a BAT area (ie, a time window) and include information of the selected BAT area (eg, a BAT area ID or the like) in the request.
  • IoT-SDM 121 may send a CE_Initiation.req message to IoT end node 101 as the request.
  • any other suitable message form can also be used.
  • IoT end node 101 may send a request for resource allocation for sounding signals (also referred to herein as a third request for convenience) to DM 122 via IoT-SDM 121, the request including Information about the selected BAT region.
  • IoT end node 101 may send 422 CE_ProbeSlotAssign.req message to IoT-SDM 121 as the request and IoT-SDM 121 forwards 423 the message to DM 122.
  • any other suitable message form can also be used.
  • DM 122 may send information regarding resource allocation to IoT end node 101 via IoT-SDM 121. For example, DM 122 sends 424 information about resource allocation to IoT-SDM 121, and IoT-SDM 121 forwards 425 the information to IoT end node 101. That is, DM 122 allocates resources for probing signals to IoT terminal node 101. For example, DM 122 may allocate the resource by sending a CE_ProbeSlotAssign.cnf message to IoT-SDM 121 and IoT-SDM 121 forwarding the message to IoT end node 101. Of course, any other suitable message form can also be used.
  • IoT end node 101 may send 426 a positive response to the first request to IoT-SDM 121.
  • IoT end node 101 may send a CE_Initiation.cnf message to IoT-SDM 121.
  • any other suitable message form can also be used.
  • IoT-SDM 121 may send 427 a request (also referred to herein as a fourth request for convenience) to send a probe to IoT end node 101 .
  • IoT-SDM 121 may send a CE_ProbeRequest.ind message to IoT end node 101 to request the transmission of probe signals.
  • the sounding signal may be a sounding frame (PROBE frame) or a channel training sequence.
  • the detection signal is not limited to this, but can take any other suitable form.
  • IoT end node 101 may send 428 a probe to IoT-SDM 121.
  • IoT-SDM 121 can perform channel evaluation and thus determine modulation parameters.
  • the channel assessment may be performed in any suitable manner known in the art or developed in the future, without limitation. It should be understood that IoT-SDM 121 may require multiple probe signals to complete channel assessment. In this case, the process of requesting and sending the probe signal (ie, the processes shown at 427 and 428 ) may need to be performed multiple times.
  • IoT-SDM 121 sends 429 the determined modulation parameters to IoT terminal node 101 for data transmission within the selected time window.
  • the process 420 of channel evaluation is completed.
  • the process 430 of data transmission is entered.
  • DM 122 may send 431 information to IoT-SDM 121 about a transmission opportunity that covers the first time window. For example, DM 122 may generate a new TXOP allocation based on the information of the first time window, and send a MAP message to IoT-SDM 121 that includes the new TXOP allocation.
  • the IoT end node 101 may be assigned the highest priority CFTS at this STXOP.
  • the embodiment of the present disclosure is not limited to this, and any other suitable TXOP allocation manner may also be adopted.
  • the following description takes CFTXOP as an example.
  • IoT-SDM 121 may send 432 the information on transmission occasions to IoT end node 101.
  • IoT-SDM 121 may send an IoT-MAP message to IoT end node 101, the IoT-MAP message including the CFTXOP allocation for IoT-SDM 121.
  • the IoT terminal node 101 can use the CFTXOP to perform uplink IoT data transmission 433 with the IoT-SDM 121 based on the received modulation parameters.
  • FIG. 5 shows a schematic diagram of a process 500 of exiting an RBM according to an embodiment of the present disclosure.
  • FIG. 5 will be described below in conjunction with the example of FIG. 1 .
  • Process 500 in this example applies to any uplink or downlink scenario of exit from RBM. It should be understood that the process of FIG. 5 may include other additional processes not shown, or some of the processes shown may be omitted. The scope of the present disclosure is not limited in this regard.
  • the process 510 of FIG. 5 is a process of exiting the RBM in the case of uplink data transmission.
  • the IoT terminal node 101 is the sending device
  • the IoT-SDM 121 is the receiving device
  • the DM 122 is the controlling device.
  • the process 510 may be initiated by the IoT terminal node 101 .
  • IoT end node 101 may send a request (also referred to herein as a fifth request for convenience) to DM 122 via IoT-SDM 121 to exit the RBM.
  • IoT end node 101 may send 511 the request to IoT-SDM 121, and IoT-SDM 121 forwards 512 the request to DM 122.
  • IoT end node 101 may send an RBM_exit.req message to IoT-SDM 121 and IoT-SDM 121 forwards the message to DM 122.
  • any other suitable message form can also be used.
  • the DM 122 may send a positive response to the request to the IoT end node 101 via the IoT-SDM 121.
  • DM 122 may send 513 the request to IoT-SDM 121, and IoT-SDM 121 forwards 514 the request to IoT endpoint 101.
  • DM 122 may send an RBM_exit.cnf message to IoT-SDM 121 and IoT-SDM 121 forwards the message to IoT end node 101.
  • any other suitable message form can also be used.
  • IoT-SDM 121 when IoT-SDM 121 receives the positive response, IoT-SDM 121 may release the modulation parameters for the first time window, ie, the BAT for the selected BAT region. In some embodiments, when the IoT end node 101 receives the positive response, the IoT end node 101 may release the modulation parameters for the first time window, ie, the BAT for the selected BAT region.
  • process 520 is the process of exiting RBM in the case of downlink data transmission.
  • the IoT-SDM 121 is the sending device
  • the IoT end node 101 is the receiving device
  • the DM 122 is the controlling device.
  • this process 520 may be initiated by IoT-SDM 121.
  • IoT-SDM 121 may send 521 a request to DM 122 for exiting the RBM (also referred to herein as a fifth request for convenience).
  • IoT-SDM 121 may send an RBM_exit.req message to DM 122.
  • RBM_exit.req message may be used.
  • any other suitable message form can also be used.
  • DM 122 may send 522 a positive response to the request to IoT-SDM 121.
  • DM 122 may send an RBM_exit.cnf message to IoT-SDM 121.
  • RBM_exit.cnf message form
  • any other suitable message form can also be used.
  • IoT-SDM 121 may send 523 a notification to IoT end node 101 to exit RBM (also referred to herein as a second notification for convenience).
  • RBM also referred to herein as a second notification for convenience.
  • DM 122 may forward the RBM_exit.cnf message to IoT-SDM 121.
  • any other suitable message form can also be used.
  • IoT-SDM 121 when IoT-SDM 121 receives the positive response, IoT-SDM 121 may release the modulation parameters for the first time window, ie, the BAT for the selected BAT region. In some embodiments, when the IoT end node 101 receives the notification, the IoT end node 101 may release the modulation parameters for the first time window, ie, the BAT for the selected BAT region.
  • the embodiments described above in conjunction with FIGS. 3 to 5 are described by taking the communication between the IoT-SDM 121 and the IoT terminal node 101 as an example.
  • the communication between IoT-SDM 121 and IoT terminal node 101 in the above process may also be accomplished via one or more IoT relay nodes.
  • the communication between IoT relay nodes and IoT terminal nodes may also employ RBM. For ease of understanding, this will be described in more detail below with reference to FIG. 6 .
  • FIG. 6 shows a schematic diagram of another process 600 for entering an RBM in the downstream direction according to an embodiment of the present disclosure.
  • the downstream direction refers to data transmission from the IoT relay node 111 to the IoT terminal node 101 .
  • the IoT relay node 111 is the sending device
  • the IoT terminal node 101 is the receiving device
  • the DM 122 is the control device.
  • the process of FIG. 6 may include other additional processes not shown, or some of the processes shown may be omitted. The scope of the present disclosure is not limited in this regard.
  • the process 600 of FIG. 6 may include a process 610 of negotiating entry into an RBM, a process 620 of channel assessment, and a process 630 of data transmission (which may also be referred to as a process 630 of resource allocation).
  • the IoT relay node 111 may initiate a process 610 of negotiating into the RBM.
  • IoT relay node 111 may send a request (also referred to herein as a second request for convenience) to DM 122 via IoT-SDM 121 to enter the RBM.
  • the IoT relay node 111 may send 611 the request to the IoT-SDM 121 , and the IoT-SDM 121 may forward 612 the request to the DM 122 .
  • IoT relay node 111 may send a RBM_enter.req message to IoT-SDM 121 and IoT-SDM 121 forwards the message to DM 122.
  • the embodiment of the present disclosure does not impose any limitation on the form of the message, and may adopt any other suitable form.
  • IoT relay node 111 may monitor the rate of data transmission and send the request when the rate of data transmission is greater than a predetermined threshold rate.
  • the predetermined threshold rate may be dynamically configured as desired.
  • the threshold predetermined threshold rate may be pre-configured.
  • the IoT relay node 111 may 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 traffic type indicates high rate data transmission.
  • IoT relay node 111 may send the request in response to receiving an instruction to enter the RBM (also referred to herein as a first instruction for convenience).
  • the instruction may come from upper layer controls such as the MAC layer, the application layer, or the like. It should be understood that the IoT relay node 111 may send the request under any other suitable triggering conditions, and is not limited to the above example.
  • the DM 122 may send a negative response to the request (not shown) to the IoT-SDM 121.
  • DM 122 may send an RBM_enter.dec message to IoT-SDM 121.
  • RBM_enter.dec message to IoT-SDM 121.
  • the DM 122 may send 613 a positive response to the request to the IoT-SDM 121, and the IoT-SDM 121 forwards 614 the positive response to the IoT relay node 111.
  • DM 122 may send a RBM_enter.cnf message to IoT-SDM 121, and IoT-SDM 121 forwards the message to IoT relay node 111.
  • RBM_enter.cnf message to IoT-SDM 121
  • IoT-SDM 121 forwards the message to IoT relay node 111.
  • the IoT relay node 111 may send 615 a notification (also referred to herein as a first notification for convenience) of entering the RBM to the IoT end node 101 .
  • IoT relay node 111 may send an RBM_enter.cnf message to IoT terminal node 101 .
  • RBM_enter.cnf message may be sent to IoT terminal node 101 .
  • the embodiment of the present disclosure does not impose any limitation on the form of the message, and may adopt any other suitable form. So far, the process 610 of negotiating to enter the RBM is completed, and the RBM is entered.
  • the IoT end node 101 may initiate a process 620 of channel evaluation.
  • IoT end node 101 sends 621 to IoT relay node 111 a request to perform channel evaluation for a single time window (also referred to herein as the first time window for convenience) in the power line communication cycle request (also referred to herein as the first request for convenience).
  • IoT end node 101 may select a BAT area (ie, a time window) and include information on the selected BAT area (eg, a BAT area ID or similar information) in the request.
  • IoT terminal node 101 may send a CE_Initiation.req message to IoT relay node 111 as the request.
  • any other suitable message form can also be used.
  • IoT relay node 111 may send a request for resource allocation for sounding signals (also referred to herein as a third request for convenience) to DM 122 via IoT-SDM 121, the request Include information about the selected BAT region.
  • IoT relay node 111 may send 622 the resource allocation request to IoT-SDM 121, and IoT-SDM 121 may forward 623 the resource allocation request to DM 122.
  • IoT relay node 111 may send a CE_ProbeSlotAssign.req message to IoT-SDM 121, and IoT-SDM 121 forwards the message to DM 122.
  • any other suitable message form can also be used.
  • DM 122 may send information regarding resource allocation to IoT relay node 111 via IoT-SDM 121. That is, the DM 122 allocates the IoT relay node 111 resources for transmitting the probe signal. In some embodiments, DM 122 may send information about resource allocation to IoT-SDM 121, and IoT-SDM 121 forwards the 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 forwards the message to IoT relay node 111, thereby allocating resources. Of course, any other suitable message form can also be used.
  • IoT relay node 111 may send 626 a positive response to the first request to IoT end node 101 .
  • IoT relay node 111 may send a CE_Initiation.cnf message to IoT terminal node 101 .
  • any other suitable message form can also be used.
  • IoT end node 101 may send 627 a request (also referred to herein as a fourth request for convenience) to send probe signals to IoT relay node 111 .
  • IoT end node 101 may send a CE_ProbeRequest.ind message to IoT relay node 111 to request the transmission of a probe signal.
  • the sounding signal may be a sounding frame (PROBE frame) or a channel training sequence.
  • the detection signal is not limited to this, but can take any other suitable form.
  • IoT relay node 111 may send 628 a probe to IoT end node 101 .
  • the IoT end node 101 can perform channel evaluation to determine modulation parameters.
  • the channel assessment may be implemented in any suitable manner known in the art or developed in the future, without limitation. It should be understood that the IoT end node 101 may require multiple sounding signals to complete the channel assessment. In this case, the process of requesting and sending the probe signal (ie, the processes shown at 627 and 628 ) may need to be performed multiple times.
  • the IoT terminal node 101 then sends 629 the determined modulation parameters to the IoT terminal node 101 for data transmission within the selected time window.
  • the channel estimation process 620 is completed.
  • the process 630 of data transmission is entered.
  • DM 122 may send 631 information to IoT-SDM 121 about a transmission opportunity that covers the first time window. For example, DM 122 may generate a new TXOP allocation based on the information of the first time window, and send a MAP message to IoT-SDM 121 that includes the new TXOP allocation.
  • the IoT end node 101 may be assigned the highest priority CFTS at this STXOP.
  • the embodiment of the present disclosure is not limited to this, and any other suitable TXOP allocation manner may also be adopted.
  • the following description takes CFTXOP as an example.
  • IoT-SDM 121 may send 632 information on transmission timing to IoT relay node 111.
  • IoT-SDM 121 may send an IoT-MAP message to IoT relay node 111, the IoT-MAP message including the CFTXOP allocation for IoT relay node 111.
  • the IoT relay node 111 may send 633 the information on the transmission occasion to the IoT terminal node 101 .
  • IoT relay node 111 may send an IoT-MAP message to IoT end node 101 , the IoT-MAP message including the CFTXOP allocation for IoT relay node 111 .
  • the IoT relay node 111 may use the CFTXOP to perform downlink IoT data transmission 634 with the IoT terminal node 101 based on the received modulation parameters. It should be understood that the processes described above in conjunction with FIG. 3 to FIG. 6 are only examples, and the embodiments of the present disclosure are not limited thereto, and the RBM may be implemented in any suitable manner.
  • the ability to train for a single time window to approach the channel limit can be retained outside the ROBO mode.
  • the RBM mode is turned off in the low-traffic state, and the RBM is activated through historical traffic or upper-layer triggering to obtain the benefits of rate improvement.
  • the complexity of IoT chips can be maintained.
  • the corresponding time slots are fixedly scheduled for IoT nodes based on the selected time window scheduling. Therefore, high rate performance and resource utilization efficiency can be achieved with a small amount of resources with limited complexity improvement.
  • FIG. 7 shows a flowchart of a method 700 of PLC for IoT implemented at a transmitting device according to an embodiment of the present disclosure.
  • the method 700 may be implemented at a sending device (eg, IoT-SDM 121, IoT relay node 111, or IoT end node 101) in a PLC IoT network.
  • a sending device eg, IoT-SDM 121, IoT relay node 111, or IoT end node 101
  • FIG. 7 will be described here in conjunction with the example of FIG. 1 . It should be understood that the method of FIG. 7 may include other additional steps not shown, or that some of the steps shown may be omitted.
  • the scope of the present disclosure is not limited in this regard.
  • the transmitting device receives a first request from the receiving device to perform a channel evaluation for a first time window in a power line communication cycle.
  • the sending device may be IoT-SDM 121, and the receiving device may be IoT terminal node 101.
  • the sending device may be IoT terminal node 101, and the receiving device may be IoT-SDM 121.
  • the sending device may be the IoT relay node 111, and the receiving device may be the IoT terminal node 101.
  • the sending device may be the IoT terminal node 101 , and the receiving device may be the IoT relay node 111 .
  • a sending device may send a first notification to a receiving device to enter a first mode in which the sending device and the receiving device are based on at least one time window in the power line communication cycle for data transfer.
  • the sending device may receive the first request sent by the receiving device in response to the first notification.
  • the first mode is RBM.
  • the sending device in response to the rate of data transmission being greater than a predetermined threshold rate, may send a second request to the controlling device (eg, DM 122) to enter the first mode. In response to receiving a positive response to the second request from DM 122, the sending device may send the first notification to the receiving device. In some alternative embodiments, the sending device may send a second request to enter the first mode to the DM 122 in response to receiving the first instruction to enter the first mode. In response to receiving a positive response to the second request from DM 122, the sending device may send the first notification to the receiving device.
  • the controlling device eg, DM 122
  • the transmitting device transmits to the receiving device a sounding signal needed to perform channel evaluation.
  • the sending device may send a third request for resource allocation of sounding signals to DM 122, the third request including information about the first time window.
  • the sending device may send an affirmative response to the first request to the receiving device.
  • the transmitting device may transmit the probe signal to the receiving device based on the information about the resource allocation.
  • the transmitting device receives modulation parameters from the receiving device, the modulation parameters determined by the receiving device by performing channel evaluation based on the sounding signal.
  • the transmitting device performs data transmission with the receiving device over a first time window based on the modulation parameters.
  • the sending device receives information from the DM 122 about a transmission opportunity that covers the first time window. Then, the sending device can use the modulation parameter to send data to the receiving device at the transmission opportunity. In some embodiments, the sending device may send the information about the transmission opportunity to the receiving device so that the receiving device can receive the data.
  • the sending device may send a second notification to the receiving device to exit the first mode.
  • the sending device may send a fifth request to DM 122 to exit the first mode in response to the rate of data transmission being less than the predetermined threshold rate, and in response to receiving an affirmation from DM 122 for the fifth request
  • a second notification is sent to the receiving device.
  • the sending device may send a fifth request to DM 122 to exit the first mode in response to receiving the second instruction to exit the first mode, and in response to receiving a request from DM 122
  • the positive response to the fifth request sends a second notification to the receiving device.
  • the sending device in response to receiving a positive response to the fifth request from DM 122, the sending device may release the modulation parameters. Thereby saving the maintenance cost of modulation parameters.
  • FIG. 8 shows a flowchart of a method 800 of PLC for IoT implemented at a receiving device according to an embodiment of the present disclosure.
  • the method 800 may be implemented at a receiving device (eg, IoT-SDM 121, IoT relay node 111, or IoT end node 101) in a PLC IoT network.
  • a receiving device eg, IoT-SDM 121, IoT relay node 111, or IoT end node 101
  • FIG. 8 will be described here in conjunction with the example of FIG. 1 . It should be understood that the method of FIG. 8 may include other additional steps not shown, or that some of the steps shown may be omitted.
  • the scope of the present disclosure is not limited in this regard.
  • the receiving device sends a first request to the sending device, the first request requesting to perform a channel evaluation for a first time window in a power line communication cycle.
  • the sending device may be IoT-SDM 121, and the receiving device may be IoT terminal node 101.
  • the sending device may be IoT terminal node 101, and the receiving device may be IoT-SDM 121.
  • the sending device may be the IoT relay node 111
  • the receiving device may be the IoT terminal node 101 .
  • the sending device may be the IoT terminal node 101 , and the receiving device may be the IoT relay node 111 .
  • the receiving device may receive a first notification from the transmitting device to enter a first mode in which the transmitting device and the receiving device transmit data based on at least one time window in a power line communication cycle. In response to the first notification, the receiving device may send the first request to the sending device.
  • the first mode is RBM.
  • the receiving device receives a sounding signal sent by the transmitting device in response to the first request needed to perform channel evaluation.
  • the receiving device may receive a positive response to the first request from the sending device.
  • the receiving device may transmit a fourth request for transmitting the probe signal to the transmitting device, and receive the probe signal transmitted by the transmitting device in response to the fourth request.
  • the receiving device transmits modulation parameters to the transmitting device, the modulation parameters being determined by the receiving device by performing a channel evaluation based on the sounding signal.
  • the receiving device and the transmitting device perform data transmission based on the modulation parameters over the first time window.
  • the receiving device receives information from the sending device about a transmission opportunity, the transmission opportunity covering the first time window.
  • the receiving device can receive data from the sending device based on the transmission opportunity.
  • the receiving device may receive a second notification from the sending 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 modulation parameters.
  • embodiments of the present disclosure also provide a method of PLC for IoT implemented at a control device.
  • 9 shows a flowchart of a method 900 of controlling a PLC for IoT implemented at a device according to an embodiment of the present disclosure.
  • the method 900 may be implemented at a control device (eg, DM 122) in a PLC IoT network.
  • a control device eg, DM 122
  • FIG. 9 will be described here in conjunction with the example of FIG. 1 . It should be understood that the method of FIG. 9 may include other additional steps not shown, or that some of the steps shown may be omitted.
  • the scope of the present disclosure is not limited in this regard.
  • the controlling device receives a third request from the transmitting device for resource allocation of the probing signal, the third request including for the first time in the power line communication cycle window information.
  • the third request is sent by the sending device in response to a first request from the receiving device requesting that channel evaluation be performed for the first time window.
  • the sending device may be IoT-SDM 121, and the receiving device may be IoT terminal node 101.
  • the sending device may be IoT terminal node 101, and the receiving device may be IoT-SDM 121.
  • the sending device may be the IoT relay node 111
  • the receiving device may be the IoT terminal node 101
  • the sending device may be the IoT terminal node 101
  • the receiving device may be the IoT relay node 111 .
  • the DM 122 may receive a second request from the transmitting device to enter a first mode in which the transmitting device and the receiving device are based on at least one of a power line communication cycle time window for data transfer.
  • the DM 122 can send an affirmative response to the second request to the sending device so that the sending device can send a first notification to the receiving device to enter the first mode.
  • the first mode is RBM.
  • the DM 122 sends information about the resource allocation to the sending device.
  • the sending device can send a sounding signal to the receiving device based on the information, so that the receiving device can complete the channel evaluation based on the sounding signal, and then determine the modulation parameter and send it to the sending device.
  • the DM 122 may send information to the transmitting device about the transmission opportunity, the transmission opportunity covering the first time window. In some embodiments, DM 122 may receive a fifth request from the sending device to exit the first mode. In some embodiments, DM 122 may send a positive response to the fifth request to the sending device.
  • an RBM is introduced for IoT data transmission, and under the RBM, the transmitting device and the receiving device perform data transmission based on at least one time window in the power line communication cycle.
  • a small amount of resources are used to achieve high rate performance, approaching the resource utilization efficiency of broadband nodes in communication.
  • the rate performance and resource utilization efficiency of each node in the PLC broadband and PLC IoT converged network are improved.
  • FIG. 10 shows a schematic block diagram of an apparatus 1000 for PLC for IoT implemented at a sending device according to an embodiment of the present disclosure.
  • the apparatus 1000 may be implemented at a sending device (eg, IoT-SDM 121, IoT terminal node 101, or IoT relay node 111 of FIG. 1) in a PLC IoT network.
  • a sending device eg, IoT-SDM 121, IoT terminal node 101, or IoT relay node 111 of FIG. 1
  • FIG. 10 will be described below in conjunction with the example of FIG. 1 .
  • the apparatus 1000 may be a part of the sending device, or may be the sending device itself. It should be understood that the apparatus 1000 may include more additional components than those shown or omit some of the components shown therein, which is not limited by the embodiments of the present disclosure.
  • the apparatus 1000 includes a first request receiving unit 1010 , a sounding signal sending unit 1020 , a modulation parameter receiving unit 1030 and a first data transmitting unit 1040 .
  • the first request receiving unit 1010 is configured to receive a first request from a receiving device for requesting to perform channel evaluation for a first time window in a power line communication cycle.
  • the sounding signal sending unit 1020 is configured to send, in response to the first request, a sounding signal required for performing channel evaluation to the receiving device.
  • 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 sounding signal.
  • the first data transmission unit 1040 is configured to perform data transmission with the receiving device over the first time window based on the modulation parameter.
  • 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 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 the 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.
  • the first mode is RBM.
  • the notification sending unit may be configured to send a second request to the control device to enter the first mode in response to a rate of data transmission being greater than a predetermined threshold rate, and in response to receiving a request from the control device for A positive response to the second request sends the first notification to the receiving device.
  • the notification sending unit may be configured to send a second request for entering the first mode to the control device in response to receiving the first instruction to enter the first mode, and in response to receiving the first instruction to enter the first mode A positive response of the control device to the second request sends the first notification to the receiving device.
  • the sounding signal sending unit 1020 may include a first sending unit, a second sending unit and a third sending unit.
  • the first sending unit may be configured to send a third request for resource allocation of the sounding signal to the control device, the third request including information on the first time window.
  • the second sending unit may be configured to send a positive response to the first request to the receiving device in response to receiving the information about the resource allocation from the controlling device.
  • the third sending unit is configured to send the sounding signal to the receiving device based on the information about the resource allocation in response to receiving the fourth request from the receiving device to send the sounding signal.
  • the first data transmission unit 1040 may include a transmission opportunity reception unit and a data transmission unit.
  • the transmission occasion receiving unit may be configured to receive information about a transmission occasion from the control device, the transmission occasion covering the first time window.
  • the data transmission unit may be configured to use the modulation parameter for data transmission with the receiving device at the transmission occasion.
  • the first data transmission unit 1040 may further include a transmission occasion sending unit configured to send information about the transmission occasion to the receiving device.
  • the apparatus 1000 may further include a second notification sending unit configured to send a second notification of exiting the first mode to the receiving device.
  • the second notification sending unit may be configured to send a fifth request to the control device for exiting the first mode in response to the rate of data transmission being less than the predetermined threshold rate, and in response to receiving a request from the control device The second notification is sent to the receiving device by a positive response to the fifth request.
  • the second notification sending unit may be configured to send a fifth request for exiting the first mode to the control device in response to receiving the second instruction for exiting the first mode, and in response to receiving the second instruction for exiting the first mode A second notification is sent to the receiving device upon receipt of a positive response to the fifth request from the controlling device.
  • the apparatus 1000 may further include a modulation parameter release unit configured to release the modulation parameter in response to receiving an affirmative response to the fifth request from the control device.
  • FIG. 11 shows a schematic block diagram of an apparatus 1100 for PLC for IoT implemented at a receiving device according to an embodiment of the present disclosure.
  • the apparatus 1100 may be implemented at a receiving device (eg, IoT-SDM 121, IoT terminal node 101, or IoT relay node 111 of FIG. 1) in a PLC IoT network.
  • a receiving device eg, IoT-SDM 121, IoT terminal node 101, or IoT relay node 111 of FIG. 1
  • FIG. 11 is described below in conjunction with the example of FIG. 1 .
  • the apparatus 1100 may be a part of the receiving device, or may be the receiving device itself. It should be understood that the apparatus 1100 may include more additional components than those shown or omit some of the components shown therein, which is not limited by the embodiments of the present disclosure.
  • the apparatus 1100 includes a first request sending unit 1110 , a sounding 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 the sending device, the first request for requesting to perform channel evaluation for a first time window in the power line communication cycle.
  • the sounding signal receiving unit 1120 is configured to receive a sounding signal required for performing channel evaluation, which is sent by the transmitting device in response to the first request.
  • the modulation parameter transmission unit 1130 is configured to transmit modulation parameters to the transmission device, the modulation parameters being determined by performing channel evaluation based on the sounding signal.
  • the second data transmission unit 1140 is configured to perform data transmission with the transmitting device based on the modulation parameter over the first time window.
  • 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 the sending device 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 the power line communication cycle.
  • the request sending unit may be configured to send the first request to the sending device in response to the first notification.
  • the first mode is RBM.
  • the sounding 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 to the first request from the sending device.
  • the sending unit may be configured to send a fourth request for sending the probe signal to the sending device in response to the positive response.
  • the second receiving unit may be configured to receive the probe signal sent by the sending device in response to the fourth request.
  • the second data transmission unit 1140 may include a transmission occasion reception unit and a data transmission unit.
  • the transmission opportunity receiving unit may be configured to receive information about a transmission opportunity from the sending device, the transmission opportunity covering the first time window.
  • the data transmission unit may be configured to perform data transmission based on the transmission opportunity.
  • the apparatus 1100 may further include a second notification receiving unit and a modulation parameter releasing unit.
  • the second notification receiving unit may be configured to receive a second notification from the sending device of exiting the first mode.
  • the modulation parameter release unit may be configured to release the modulation parameter in response to the second notification.
  • FIG. 12 shows a schematic block diagram of an apparatus 1200 for PLC for IoT implemented at a control device according to an embodiment of the present disclosure.
  • the apparatus 1200 may be implemented at a control device (eg, DM 122 of FIG. 1 ) in a PLC IoT network.
  • a control device eg, DM 122 of FIG. 1
  • FIG. 12 is described below in conjunction with the example of FIG. 1 .
  • Device 1200 may be part of DM 122 or may be DM 122 itself. It should be understood that the apparatus 1200 may include more additional components than those shown or omit some of the components shown therein, which is not limited by the embodiments of the present disclosure.
  • 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 for resource allocation of the sounding signal from the transmitting device, the third request including information about the first time window in the power line communication cycle.
  • the third request is sent by the sending device in response to a first request from a receiving device requesting to perform channel evaluation for the first time window.
  • the resource allocation unit 1220 is configured to send information about the resource allocation to the sending device.
  • 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 to enter a first mode in which the transmitting device and the receiving device are based on a At least one time window for data transfer.
  • the response sending unit may be configured to send a positive response to the second request to the sending device in order to send a first notification of entering the first mode to the receiving device.
  • the first mode is RBM.
  • the apparatus 1200 may further include a transmission opportunity sending unit configured to send information about the transmission opportunity to the sending device, the transmission opportunity covering the first time window.
  • 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 for exiting the first mode from the sending device.
  • the second response sending unit may be configured to send a positive response to the fifth request.
  • Device 1300 is a simplified block diagram of a device 1300 suitable for implementing embodiments of the present disclosure.
  • Device 1300 may be provided to implement a PLC IoT communication device (transmitting device or receiving device) or control device, such as any of IoT-SDM 121, DM 122, IoT terminal node 101 and IoT relay node 111 shown in FIG. 1 .
  • device 1300 includes at least one processor 1310 and at least one PLC interface 1320 coupled to at least one processor 1310 .
  • the PLC interface 1320 may include a power plug interface 1321 , an analog front end (AFE, Analog Front End) 1322 and a digital front end (DFE, Digital Front End) 1323 .
  • AFE analog front end
  • DFE Digital Front End
  • the power plug interface 1321 may be coupled to an external power plug.
  • the power plug interface can represent any interface required by the PLC.
  • AFE 1322 may include analog signal processing elements, and DFE 1323 may include digital signal processing elements.
  • Processor 1310 may be of any type suitable for a local technology network, and may include, by way of limiting example, one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors, and multi-core processor-based architectures processor.
  • Device 1300 may have multiple processors, such as application specific integrated circuit chips, that are temporally slaved to a clock synchronized with the main processor.
  • the processor 1310 may be operable to implement embodiments of the present disclosure through the PLC interface 1320 such that the device 1300 performs the processes of the present disclosure as discussed with reference to FIGS. 3-12 .
  • the apparatus 1300 may correspond to the above-mentioned apparatus 1000 , apparatus 1100 or apparatus 1200 , and each functional module in the apparatus 1000 , apparatus 1100 or apparatus 1200 may be implemented by the processor 1310 combined with the PLC interface 1320 .
  • Embodiments of the present disclosure may also be implemented by software or by a combination of software and hardware.
  • device 1300 may also include memory (not shown).
  • the memory may include one or more non-volatile memories and one or more volatile memories.
  • Examples of non-volatile memory include, but are not limited to, read only memory (ROM), electrically programmable read only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic storage and/or Optical storage device.
  • Examples of volatile memory include, but are not limited to, random access memory (RAM) and other volatile memory that do not persist for the duration of a power outage.
  • the computer programs include computer-executable instructions that are executed by the associated processor 1310 . Programs can be stored in memory.
  • the processor 1310 may perform any suitable actions and processes by loading programs into memory.
  • the various example embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Certain aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor or other computing device. While aspects of the embodiments of the present disclosure are illustrated or described as block diagrams, flowcharts, or using some other graphical representation, it is to be understood that the blocks, apparatus, systems, techniques, or methods described herein may be taken as non-limiting Examples are implemented in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controllers or other computing devices, or some combination thereof.
  • FPGAs Field Programmable Gate Arrays
  • ASICs Application Specific Integrated Circuits
  • ASSPs Application Specific Standard Products
  • SOCs Systems on Chips
  • CPLD Complex Programmable Logic device
  • embodiments of the present disclosure may be described in the context of machine-executable instructions, such as included in program modules executed in a device on a target's real or virtual processor.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data structures.
  • the functionality of the program modules may be combined or divided among the described program modules.
  • Machine-executable instructions for program modules may be executed within local or distributed devices. In a distributed facility, program modules may be located in both local and remote storage media.
  • Computer program code for implementing the methods of the present disclosure may be written in one or more programming languages. Such computer program code may be provided to a processor of a general purpose computer, special purpose computer or other programmable data processing apparatus such that the program code, when executed by the computer or other programmable data processing apparatus, causes the flowchart and/or block diagrams The functions/operations specified in are implemented.
  • the program code may execute entirely on the computer, partly on the computer, as a stand-alone software package, partly on the computer and partly on a remote computer or entirely on the remote computer or server.
  • computer program code or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform the various processes and operations described above.
  • suitable carriers include signals, computer-readable media, and the like.
  • Examples of signals may include electrical, optical, radio, acoustic, or other forms of propagated signals, such as carrier waves, infrared signals, and the like.
  • a machine-readable medium may be any tangible medium that contains or stores a program for or in connection with an instruction execution system, apparatus, or device.
  • the machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium.
  • Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, 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.

Landscapes

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

Abstract

本申请涉及用于物联网(IoT)的电力线通信(PLC)的方法、装置和系统。该方法包括发送设备接收来自接收设备的第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估；响应于第一请求，发送设备向接收设备发送用于执行所述信道评估所需的探测信号；发送设备从接收设备接收调制参数，所述调制参数是通过基于所述探测信号执行所述信道评估而确定的；以及发送设备基于所述调制参数，与接收设备在所述第一时间窗上进行数据传输。根据在此提出的技术方案，可以在有限的复杂度提升的情况下，大幅提升PLC宽带和PLC IoT融合场景中宽带业务和IoT业务二者的速率性能以及资源利用效率。

Description

用于物联网的电力线通信的方法、装置和系统 技术领域
本申请涉及电力线通信(PLC，Power Line Communication)领域，特别是涉及用于物联网(IoT，Internet of Things)的电力线通信的方法、装置和系统。
背景技术
PLC是指利用电力线将数据或信息以数字信号处理方法进行传输。PLC宽带技术使用低频的电力线发送宽带数据。由于其基本上不需要另外重新铺设网络线路并且涵盖的地区范围远大于其他种类载体的线路，PLC宽带技术已被广泛应用于诸如家庭网络、行业网络等各种网络中。近来随着IoT技术的发展，PLC IoT技术也被广泛应用于诸如行业网络如智能电网等应用中。PLC IoT技术是指利用电力线实现IoT节点之间的通信。近来尝试将PLC IoT应用于智能家庭应用中，于是PLC宽带网络与PLC IoT网络的融合逐渐成为一个刚性需求。在这种融合网络中，PLC宽带通信和PLC IoT通信工作在同一个电力线网络中，并且使用同一介质和共享物理层传输资源。
通常，在这种融合网络中，同一介质需要支持数个PLC宽带节点(也简称为宽带节点)和数以百计的PLC IoT节点(也简称为IoT节点或窄带节点)。IoT节点虽然每节点的数据流量较少，但节点数多，导致IoT应用的总开销较大。另外，由于IoT技术可实现的速率低，导致占用的资源多，从而挤占宽带节点可使用的通信资源数量，并且导致宽带节点可实现的速率大幅降低。此外，IoT节点的带宽需求也在不断提升。因此，期望提供改进的方案来提升这种融合网络中宽带节点和IoT节点二者的通信性能。
发明内容
本公开的实施例提供一种用于物联网的电力线通信的方案，能够改善这种融合网络中的各节点的通信性能。
根据本公开实施例的第一方面，提供一种用于物联网的电力线通信的方法。该方法包括：发送设备接收来自接收设备的第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估；响应于所述第一请求，所述发送设备向所述接收设备发送用于执行所述信道评估所需的探测信号；所述发送设备从所述接收设备接收调制参数，所述调制参数是通过基于所述探测信号执行所述信道评估而确定的；以及所述发送设备基于所述调制参数，与所述接收设备在所述第一时间窗上进行数据传输。
根据本公开实施例的第二方面，提供一种用于物联网的电力线通信的方法。该方法包括：接收设备向发送设备发送第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估；所述接收设备接收所述发送设备响应于所述第一请求所发送的用于执行所述信道评估所需的探测信号；所述接收设备向所述发送设备发送调制参数，所述调制参数是通过基于所述探测信号执行所述信道评估而确定的；以及所述接收设备与所述发送设备在所述第一时间窗上基于所述调制参数进行数据传输。
根据本公开实施例的第三方面，提供一种用于物联网的电力线通信的方法。该方法包括：控制设备接收来自发送设备的用于探测信号的资源分配的第三请求，所述第三请求包括关于 电力线通信周期中的第一时间窗的信息，所述第三请求是由所述发送设备响应于来自接收设备的第一请求而发送的，所述第一请求用于请求针对所述第一时间窗执行信道评估；以及所述控制设备向所述发送设备发送关于所述资源分配的信息。
根据本公开实施例的第四方面，提供一种用于物联网的电力线通信的通信装置。该通信装置包括：处理器；以及耦合至所述处理器的电力线通信接口。所述处理器被配置为：通过所述电力线通信接口接收来自接收设备的第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估；响应于所述第一请求，通过所述电力线通信接口向所述接收设备发送用于执行所述信道评估所需的探测信号；通过所述电力线通信接口从所述接收设备接收调制参数，所述调制参数是通过基于所述探测信号执行所述信道评估而确定的；以及基于所述调制参数并且在所述第一时间窗上，通过所述电力线通信接口与所述接收设备进行数据传输。
根据本公开实施例的第五方面，提供一种用于物联网的电力线通信的通信装置。该通信装置包括：处理器；以及耦合至所述处理器的电力线通信接口。所述处理器被配置为：通过所述电力线通信接口向发送设备发送第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估；通过所述电力线通信接口接收所述发送设备响应于所述第一请求所发送的用于执行所述信道评估所需的探测信号；通过所述电力线通信接口向所述发送设备发送调制参数，所述调制参数是通过基于所述探测信号执行所述信道评估而确定的；以及通过所述电力线通信接口与所述发送设备在所述第一时间窗上基于所述调制参数进行数据传输。
根据本公开实施例的第六方面，提供一种用于物联网的电力线通信的控制设备。该控制设备包括：处理器；以及耦合至所述处理器的电力线通信接口。所述处理器被配置为：通过所述电力线通信接口接收来自发送设备的用于探测信号的资源分配的第三请求，所述第三请求包括关于电力线通信周期中的第一时间窗的信息，所述第三请求是由所述发送设备响应于来自接收设备的第一请求而发送的，所述第一请求用于请求针对所述第一时间窗执行信道评估；以及通过所述电力线通信接口向所述发送设备发送关于所述资源分配的信息。
根据本公开实施例的第七方面，提供一种用于物联网的电力线通信的装置。该装置包括：第一请求接收单元，被配置用于发送设备接收来自接收设备的第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估；探测信号发送单元，被配置用于响应于所述第一请求，所述发送设备向所述接收设备发送用于执行所述信道评估所需的探测信号；调制参数接收单元，被配置用于所述发送设备从所述接收设备接收调制参数，所述调制参数是通过基于所述探测信号执行所述信道评估而确定的；以及第一数据传输单元，被配置用于所述发送设备基于所述调制参数，与所述接收设备在所述第一时间窗上进行数据传输。
根据本公开实施例的第八方面，提供一种用于物联网的电力线通信的装置。该装置包括：第一请求发送单元，被配置用于接收设备向发送设备发送第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估；探测信号接收单元，被配置用于所述接收设备接收所述发送设备响应于所述第一请求所发送的用于执行所述信道评估所需的探测信号；调制参数发送单元，被配置用于所述接收设备向所述发送设备发送调制参数，所述调制参数是通过基于所述探测信号执行所述信道评估而确定的；以及第二数据传输单元，被配置用于所述接收设备与所述发送设备在所述第一时间窗上基于所述调制参数进行数据传输。
根据本公开实施例的第九方面，提供一种用于物联网的电力线通信的装置。该装置包括： 第三请求接收单元，被配置用于控制设备接收来自发送设备的用于探测信号的资源分配的第三请求，所述第三请求包括关于电力线通信周期中的第一时间窗的信息，所述第三请求是由所述发送设备响应于来自接收设备的第一请求而发送的，所述第一请求用于请求针对所述第一时间窗执行信道评估；以及资源分配单元，被配置用于所述控制设备向所述发送设备发送关于所述资源分配的信息。
根据本公开实施例的第十方面，提供一种用于物联网的电力线通信的系统。该系统包括前述第四和第五方面中的通信装置以及前述第六方面中的控制设备。
根据本公开实施例的第十一方面，提供一种芯片，包括处理器和前端电路，处理器和前端电路一起操作用于执行前述第一方面、第二方面或第三方面中的方法。
根据本公开实施例的第十二方面，提供一种计算机可读存储介质。该计算机可读存储介质包括机器可执行指令，所述机器可执行指令在由设备执行时促使该设备执行根据第一方面、第二方面或第三方面的方法。
根据本公开实施例的第十三方面，提供一种计算机程序产品。该计算机程序产品包括计算机程序代码，所述计算机程序代码在由设备执行时促使该设备执行根据第一方面、第二方面或第三方面的方法。
通过下文对示例实施例的描述将会理解，根据在此提出的技术方案，可以在有限的复杂度提升的情况下，大幅提升PLC IoT业务和PLC宽带业务二者的速率性能以及资源利用效率。
应当理解，发明内容部分中所描述的内容并非旨在限定本公开实施例的关键或重要特征，亦非用于限制本公开的范围。本公开的其它特征将通过以下的描述变得容易理解。
附图说明
结合附图并参考以下详细说明，本公开各实施例的上述和其他特征、优点及方面将变得更加明显。在附图中，相同或相似的附图标记表示相同或相似的元素，其中：
图1示出了本公开实施例可在其中实施的示例PLC网络的示意图；
图2A示出了根据本公开实施例的速率提升模式(RBM，Rate Boost Mode)下选择时间窗的示意图；
图2B示出了根据本公开实施例的非RBM下的传输时机(TXOP，Transmission Opportunity)分配的示意图；
图2C示出了根据本公开实施例的RBM下的TXOP分配的示意图；
图3示出了根据本公开实施例的在下行方向上进入RBM的过程的示意图；
图4示出了根据本公开实施例的在上行方向上进入RBM的过程的示意图；
图5示出了根据本公开实施例的退出RBM的过程的示意图；
图6示出了根据本公开实施例的在下行方向上进入RBM的另一过程的示意图；
图7示出了根据本公开实施例的发送设备处实施的用于IoT的PLC的方法的流程图；
图8示出了根据本公开实施例的接收设备处实施的用于IoT的PLC的方法的流程图；
图9示出了根据本公开实施例的控制设备处实施的用于IoT的PLC的方法的流程图；
图10示出了根据本公开实施例的发送设备处实施的用于IoT的PLC的装置的示意框图；
图11示出了根据本公开实施例的接收设备处实施的用于IoT的PLC的装置的示意框图；
图12示出了根据本公开实施例的控制设备处实施的用于IoT的PLC的装置的示意框图；以及
图13示出了适合于实现本公开实施例的设备的简化框图。
具体实施方式
下面将参照附图更详细地描述本公开的实施例。虽然附图中示出了本公开的一些实施例，然而应当理解的是，本公开可以通过各种形式来实现，而且不应该被解释为限于这里阐述的实施例，相反提供这些实施例是为了更加透彻和完整地理解本公开。应当理解的是，本公开的附图及实施例仅用于示例性作用，并非用于限制本公开的保护范围。
在此使用的术语“包括”及其变形是开放性包括，即“包括但不限于”。术语“基于”是“至少部分地基于”。术语“一个实施例”表示“至少一个实施例”；术语“另一实施例”表示“至少一个另外的实施例”。其他术语的相关定义将在下文描述中给出。
应理解，尽管本文可以使用术语“第一”和“第二”等来描述各种元件，但这些元件不应受到这些术语的限制。这些术语仅用于区分一个元件和另一个元件。例如，第一元件可以称为第二元件，同样，第二元件可以称为第一元件，而不脱离实施例的范围。如本文所用，术语“和/或”包括一个或多个所列术语的任何和所有组合。
在此使用的术语“电路”是指以下的一项或多项：
(a)仅硬件电路实现方式(诸如仅模拟和/或数字电路的实现方式)；以及
(b)硬件电路和软件的组合，诸如(如果适用)：(i)模拟和/或数字硬件电路与软件/固件的组合，以及(ii)硬件处理器的任意部分与软件(包括一起工作以使得诸如光线路终端(OLT)或其他计算设备等装置执行各种功能的数字信号处理器、软件和存储器)；以及
(c)硬件电路和/或处理器，诸如微处理器或者微处理器的一部分，其要求软件(例如固件)用于操作，但是在不需要软件用于操作时可以没有软件。
电路的定义适用于此术语在本申请中(包括任意权利要求中)的所有使用场景。作为另一示例，在此使用的术语“电路”也覆盖仅硬件电路或处理器(或多个处理器)、或者硬件电路或处理器的一部分、或者其随附软件或固件的实现方式。例如，如果适用于特定权利要求元素，术语“电路”还覆盖基带集成电路或处理器集成电路或者OLT或其他计算设备中的类似的集成电路。
如本文所用，术语“PLC网络”是指利用电力线将数据或信息以数字信号处理方法进行传输的任何网络。该网络可以与诸如使用电话线路的数字用户线路技术(DSL，Digital Subscriber Line)以及使用有线电视的同轴电缆线路的电缆调制解调器(CM，Cable Modem)之类的有线网络结合使用，也可以与诸如WiFi、蓝牙等无线网络结合使用。当然，该网络也可以与当前已有的以及未来开发的其它任何合适网络结合使用。
如本文所用，术语“PLC网络主节点(DM，Domain Master)”是指PLC网络中的主节点，负责PLC网络中其它节点的接入、认证以及资源时隙的调度分配。
如本文所用，术语“PLC宽带节点”是指任意能够通过PLC进行宽带通信的终端设备。该终端设备可以具有无线或有线通信能力。该终端设备的示例包括但限于客户终端设备(CPE)、用户设备(UE)、个人计算机、台式计算机、移动电话、蜂窝电话、智能电话、个人数字助理(PDA)、便携式计算机、平板、可穿戴设备、物联网(IoT)设备、机器类型通信(MTC)设备、用于V2X(X是指行人、车辆或基础设施/网络)通信的车载设备、或者诸如数字相机之类的图像捕获设备、游戏设备、音乐存储和回放设备或能够进行无线或有线因特网访问和浏览的因特网设备等等。
如本文所用，术语“IoT子域”是指在PLC网络中的IoT节点所构成的子网络。术语“IoT子域节点(IoT-SDM，IoT-Subdomain Master)”是指管理或协调IoT子域中的数据传输的节点。术语“IoT节点”或“IoT终端节点”可以是具有PLC能力的IoT终端设备，诸如智能家电、智能电表、可穿戴设备等。术语“IoT中继节点”是指上述IoT子域中的中继器，与IoT-SDM相连接，以扩大网络传输的距离。
图1示出了本公开实施例可在其中实施的示例PLC网络100的示意图。如图1所示，该PLC网络100可以包括IoT终端节点101、102和103、PLC宽带节点104和105、IoT中继节点111、IoT-SDM 121和DM 122。IoT终端节点101、102和103可以经由IoT中继节点111来与IoT-SDM 121通信，并且IoT-SDM 121经由DM 122而与在PLC网络100外部的远程服务器(未示出)通信。换言之，IoT终端节点101、102和103需要经由IoT-SDM 121来与DM 122通信。PLC宽带节点104和105可以通过电力线信道与DM 122通信，以便经由DM 122接入诸如因特网、局域网、城域网等的网络。在一些实施例中，IoT-SDM 121和DM 122可以实现为分离的物理实体。在一些实施例中，IoT-SDM 121和DM 122可以实现在同一物理实体上，如图中120所示。
尽管在图1中示出了IoT中继节点111，但在一些实施例中，PLC网络100可以不包括IoT中继节点111。在这种情况下，IoT终端节点101、102和103可以直接与IoT-SDM 121通信。此外，应理解到，IoT终端节点、PLC宽带节点和IoT中继节点的数目并不限于图1所示的示例，而是可以包括其它任意合适的更多或更少的数目。IoT-SDM 121的功能可以在IoT子域中的任意节点上集中或分布地实施，并且DM 122的功能可以在PLC网络中的任意节点上集中或分布地实施。此外，PLC网络100可以包括更多未示出的附加组件或者可以省略所示出的某些组件，本公开实施例对此并不做限制。PLC网络100的实施也不限于上述具体示例，而是可以以任意合适的方式实施。
在现有PLC IoT技术中，为了实现低成本、低功耗和高可靠性，物理层技术上均采用高鲁棒性通信技术，如Homeplug Green PHY标准及IEEE 1901.1中采用的鲁棒正交频分复用(ROBO，Robust Orthogonal Frequency Division Multiplexing)模式；同时ITU-T G.hn协议中也定义了鲁棒通信模式(RCM，Robust Communication Mode)。在ROBO/RCM模式中，固定使用低阶比特调制，同时采用重复编码。从而可以增强传输的可靠性，用于支持4Mbps至10Mbps的数据速率。下表1示出了几种ROBO模式下的参数示例。
表1 ROBO模式的参数示例
模式 物理层速率 调制阶数 FEC码率 重复拷贝次数
小型ROBO 3.8Mbps QPSK 1/2 5
标准ROBO 4.9Mbps QPSK 1/2 4
高速ROBO 9.8Mbps QPSK 1/2 2
可见，通过物理层上采用ROBO模式，通信方案简单，支持节点数多，可靠性高，但速率较低。
而在PLC宽带技术中，使用基于载波的自适应调制特性。调制阶数可高达4096QAM，速率高，但复杂度高，导致支持的节点数少。下表2示出了PLC宽带技术和PLC IoT技术的参数比较示例。
表2 PLC宽带技术和PLC IoT技术的参数比较示例
Figure PCTCN2021079407-appb-000001
这样，在PLC宽带和PLC IoT融合场景中，同一介质需要支持数个宽带节点和数以百计的IoT节点。IoT节点虽然每节点的数据流量较少，但节点数多，导致IoT应用的总开销较大。另外，由于IoT技术在上述ROBO模式中可实现的速率低，导致占用的资源多。从而挤占宽带节点可使用的通信资源数量，并且导致宽带节点可实现的速率大幅降低。
同时，IoT应用的带宽需求不断提升，而不再是只有简单的控制需求和间歇的上报需求。例如，传感器存在持续的固定带宽需求，如每传感器需要150Kbps。在这种情况下，40个传感器需要6Mbps的带宽，远大于传统智能电网的通信带宽需求。
鉴于此，本公开的实施例提出了一种针对IoT的PLC改进方案。根据在此提出的方案，引入了一种速率提升模式(RBM，Rate Boost Mode)。为方便起见，RBM在本文中也称为第一模式。在该RBM中，IoT节点基于电力线通信周期中的至少一个时间窗来进行数据传输。具体而言，通过选定该至少一个时间窗中的一个时间窗，并针对该选定的时间窗执行信道评估以确定调制参数用于该选定的时间窗内的数据传输。通过物理层和介质访问控制(MAC，Medium Access Control)层协作，大幅提升单位资源上的传输性能，锁定物理层时隙位置进行数据流传输。由此，使用少量的资源实现高的速率性能，逼近宽带节点在通信中的资源利用效率。为便于理解，下面结合图2A至图2C对此进行详细描述。
图2A示出了根据本公开实施例的RBM下选择时间窗的示意图200A。如所知，由于受到负载和噪声实时变化的影响，电力线信道也是实时变化的。但电力线信道的实时变化具备交流(AC，Alternate Current)周期的特性，如图2A中的210所示。如图2A所示，可以基于电力线信道的AC周期进行分窗，例如划分成8个时间窗201-208。应理解到，时间窗的数目并不限于此，而是可以采用任意合适数目。
根据本公开的实施例，在RBM下，可以选择单个时间窗进行信道评估并输出针对该单个时间窗的物理层传输参数。在本文中，物理层传输参数也称为比特分配表(BAT，Bit Allocation Table)，并且各时间窗也称为BAT区域。如图2A所示，在RBM下可以选择时间窗205进行速率自适应操作。
在PLC宽带通信中，通常针对每个时间窗都要单独维护BAT。由于BAT是载波级别，所以占用很大的存储空间。另外，收发双方同步BAT所需的信令开销也很大。因此，多个时间窗的维护导致开销加倍。相比之下，在本公开实施例的RBM下，由于仅针对单个时间窗进行信道评估，所以存储及信令开销只有PLC宽带通信中的几分之一(在本例中，1/8)。
另外，与其中固定使用低阶比特调制和采用重复编码的ROBO模式相比，RBM可以大幅提升单位资源下的通信效率。下表3示出了RBM和ROBO模式的性能比较示例。其中假设频宽相同。
表3 RBM和ROBO/RCM模式的性能比较示例
Figure PCTCN2021079407-appb-000002
可见，相同频宽的情况下，1/8资源占用即可提供更高的速率性能。
对于MAC层，DM需要为IoT节点分配通信资源。图2B示出了根据本公开实施例的非RBM下的TXOP分配的示意图200B。如图2B所示，在非RBM下，DM通常会从共享传输时机(STXOP，Shared Transmission Opportunity)中为IoT节点分配免竞争传输时隙(CFTS，Contention-free Time Slot)。
根据本公开的实施例，在RBM下，IoT节点将使用并且只使用特定的窗口传输数据。因此对于MAC层，DM需要为该IoT节点分配该窗口位置上的资源。例如，进入RBM时，需要为IoT节点分配特定的TXOP。DM需要更改TXOP分配以适配新需求。图2C示出了根据本公开实施例的RBM下的TXOP分配的示意图200C。如图2C所示，当进入RBM时，在针对IoT节点确定了时间窗231后，DM MAC需要为该窗口位置分配TXOP资源232。在一些实施例中，该TXOP资源232可以为CFTXOP，该CFTXOP被分配给该IoT节点。在一些备选实施例中，该TXOP资源232可以为STXOP，并为该IoT节点在该STXOP中分配最高优先级的CFTS。在一些实施例中，一个MAC周期包括两个AC周期，在这种情况下，可以根据比特率需求确定为IoT节点分配一个或两个CFTXOP或STXOP。
根据本公开的实施例，当在PLC网络中存在数百个IoT节点时，并非所有IoT节点都具有持续的高比特速率需求，而是大多数IoT节点在大多数时间上都是低速率的。因此，不需要为所有IoT节点都维护BAT，而可以只在必要时使少数IoT节点工作在RBM下。在本公开的一些实施例中，可以将RBM和ROBO模式结合用于IoT节点的通信。例如，在高速率场景(例如传输速率高于预定阈值速率时)中或在上层控制下进入RBM，其它时间使用ROBO模式。因此，由于RBM只在有需求的情况下进入，所以更加大幅地降低了汇聚节点的开销。汇聚节点是指在IoT树形网络或星型网络中同时与多个节点进行通信的节点。为了便于理解，下面结合图3至图6进行更详细的说明。
图3示出了根据本公开实施例的在下行方向上进入RBM的过程300的示意图。为方便起见，下面结合图1的示例对图3进行说明。在本例中，下行方向是指从IoT-SDM 121向IoT终端节点101的数据传输。在这种情况下，IoT-SDM 121为发送设备，IoT终端节点101为接收设备，DM 122为控制设备。应理解到，图3的过程也可以适用于从IoT-SDM 121向网络100中的其它IoT终端节点的数据传输。还应理解到，图3的过程可以包括其它未示出的附加过程，或者可以省略所示出的一些过程。本公开的范围并不受限于此。
在本实施例中，图3的过程300可以包括协商进入RBM的过程310、信道评估的过程320和数据传输的过程330(也可以称为资源分配的过程330)。
IoT-SDM 121可以发起协商进入RBM的过程310。如图3所示，IoT-SDM 121可以向DM 122发送311用于进入RBM的请求(为方便起见，在本文中也称为第二请求)。例如，IoT-SDM 121可以向DM 122发送RBM_enter.req消息。当然，本公开实施例并不对消息的形 式作任何限制，而是可以采用其他任意合适形式。
在一些实施例中，IoT-SDM 121可以监测数据传输的速率，并且当数据传输的速率大于预定阈值速率时发送该请求。在一些实施例中，该预定阈值速率可以根据需要动态配置。在一些实施例中，该阈值预定阈值速率可以是预先配置的。在一些备选实施例中，IoT-SDM 121可以监测数据传输的业务类型，并且当业务类型为预定业务类型时发送该请求。例如，预定业务类型指示高速率数据传输。在一些备选实施例中，IoT-SDM 121可以响应于接收到进入RBM的指令(为方便起见，在本文中也称为第一指令)而发送该请求。在一些实施例中，该指令可以来自例如MAC层、应用层等上层控制。应理解到，IoT-SDM 121可以在其他任意合适的触发条件下发送该请求，而不限于上述示例。
如果DM 122拒绝该请求，则DM 122可以向IoT-SDM 121发送针对该请求的否定响应(未示出)。例如，DM 122可以向IoT-SDM 121发送RBM_enter.dec消息。当然，本公开实施例并不对该消息的形式作任何限制，而是可以采用其他任意合适形式。至此该过程300将结束。
如果DM 122接受该请求，则DM 122可以向IoT-SDM 121发送312针对该请求的肯定响应。例如，DM 122可以向IoT-SDM 121发送RBM_enter.cnf消息。当然，本公开实施例并不对该消息的形式作任何限制，而是可以采用其他任意合适形式。
IoT-SDM 121响应于接收到该肯定响应，可以向IoT终端节点101发送313进入RBM的通知(为方便起见，在本文中也称为第一通知)。例如，IoT-SDM 121可以向IoT终端节点101发送RBM_enter.cnf消息。当然，本公开实施例并不对该消息的形式作任何限制，而是可以采用其他任意合适形式。至此，完成了协商进入RBM的过程310，并进入RBM。
在RBM下，IoT终端节点101可以发起信道评估的过程320。如图3所示，IoT终端节点101向IoT-SDM 121发送321用于请求针对电力线通信周期中的单个时间窗(为方便起见，在本文中也称为第一时间窗)执行信道评估的请求(为方便起见，在本文中也称为第一请求)。例如，IoT终端节点101可以选择一个BAT区域(即，时间窗)，并且将所选择的BAT区域的信息(例如标识(ID，Identity)或类似信息)包括在该请求中。例如，IoT终端节点101可以向IoT-SDM 121发送CE_Initiation.req消息作为该请求。当然，也可以采用其他任意合适的消息形式。
响应于该信道评估的请求，IoT-SDM 121可以向DM 122发送322用于探测信号的资源分配的请求(为方便起见，在本文中也称为第三请求)，该请求包括关于所选择的BAT区域的信息。例如，IoT-SDM 121可以向DM 122发送CE_ProbeSlotAssign.req消息作为该请求。当然，也可以采用其他任意合适的消息形式。
响应于该资源分配的请求，DM 122可以向IoT-SDM 121发送323关于资源分配的信息。也就是，DM 122为IoT-SDM 121分配用于探测信号的资源。例如，DM 122可以向IoT-SDM 121发送CE_ProbeSlotAssign.cnf消息以分配该资源。当然，也可以采用其他任意合适的消息形式。
继而，IoT-SDM 121可以向IoT终端节点101发送324针对第一请求的肯定响应。例如，IoT-SDM 121可以向IoT终端节点101发送CE_Initiation.cnf消息。当然，也可以采用其他任意合适的消息形式。
响应于该肯定响应，IoT终端节点101可以向IoT-SDM 121发送325用于发送探测信号的请求(为方便起见，在本文中也称为第四请求)。例如，IoT终端节点101可以向IoT-SDM  121发送CE_ProbeRequest.ind消息以便请求探测信号的发送。在一些实施例中，探测信号可以为探测帧(PROBE帧)或信道训练序列。当然，探测信号并不限于此，而是可以采用其他任意合适形式。
响应于该探测信号的请求，IoT-SDM 121可以向IoT终端节点101发送326探测信号。利用该探测信号，IoT终端节点101可以进行信道评估，从而确定调制参数。该信道评估可以采用本领域已知或未来开发的任意合适方式来实施，这里不作限制。应理解到，IoT终端节点101可能需要多个探测信号来完成信道评估。在这种情况下，探测信号的请求和发送过程(即325和326所示的过程)可能需要多次执行。
继而，IoT终端节点101将所确定的调制参数发送327给IoT-SDM 121，以便用于所选择的时间窗内的数据传输。至此，完成了信道评估的过程320。接下来进入数据传输的过程330。
参考图3，DM 122可以向IoT-SDM 121发送331关于传输时机的信息，该传输时机覆盖第一时间窗。例如，DM 122可以基于第一时间窗的信息，生成新TXOP分配，并且向IoT-SDM 121发送包括新TXOP分配的MAP消息。在一些实施例中，新TXOP分配中可以存在CFTXOP，该CFTXOP覆盖针对IoT终端节点101所选择的BAT区域的位置。例如，该CFTXOP可以与BAT_ID＝x对应。在一些备选实施例中，新TXOP分配中可以存在STXOP，该STXOP覆盖针对IoT终端节点101所选择的BAT区域的位置。在该STXOP可以为IoT终端节点101分配最高优先级的CFTS。当然，本公开的实施例并不限于此，也可以采用其他任意合适的TXOP分配方式。下面以CFTXOP为例进行描述。
IoT-SDM 121可以向IoT终端节点101发送332所述关于传输时机的信息。例如，IoT-SDM 121可以向IoT终端节点101发送IoT-MAP消息，该IoT-MAP消息包括针对IoT-SDM 121的该CFTXOP分配。
继而，IoT-SDM 121可以使用该CFTXOP、基于接收到的调制参数来与IoT终端节点101进行下行IoT数据传输333。
图4示出了根据本公开实施例的在上行方向上进入RBM的过程400的示意图。为方便起见，下面结合图1的示例对图4进行说明。在本例中，上行方向是指从IoT终端节点101向IoT-SDM 121的数据传输。在这种情况下，IoT终端节点101为发送设备，IoT-SDM 121为接收设备，DM 122为控制设备。应理解到，图4的过程也可以适用于从网络100中的其它IoT终端节点向IoT-SDM 121的数据传输。还应理解到，图4的过程可以包括其它未示出的附加过程，或者可以省略所示出的一些过程。本公开的范围并不受限于此。
在本实施例中，图4的过程400可以包括协商进入RBM的过程410、信道评估的过程420和数据传输的过程430(也可以称为资源分配的过程430)。
IoT终端节点101可以发起协商进入RBM的过程410。IoT终端节点101可以经由IoT-SDM 121向DM 122发送用于进入RBM的请求(为方便起见，在本文中也称为第二请求)。如图4所示，IoT终端节点101可以向IoT-SDM 121发送411用于进入RBM的请求，IoT-SDM 121将该请求转发412给DM 122。例如，IoT终端节点101可以向IoT-SDM 121发送RBM_enter.req消息，IoT-SDM 121将该消息转发给DM 122。当然，本公开实施例并不对消息的形式作任何限制，而是可以采用其他任意合适形式。
在一些实施例中，IoT终端节点101可以监测数据传输的速率，并且当数据传输的速率大于预定阈值速率时发送该请求。在一些实施例中，该预定阈值速率可以根据需要动态配置。在一些实施例中，该阈值预定阈值速率可以是预先配置的。在一些备选实施例中，IoT终端 节点101可以监测数据传输的业务类型，并且当业务类型为预定业务类型时发送该请求。例如，预定业务类型指示高速率数据传输。在一些备选实施例中，IoT终端节点101可以响应于接收到进入RBM的指令(为方便起见，在本文中也称为第一指令)而发送该请求。在一些实施例中，该指令可以来自例如MAC层、应用层等上层控制。应理解到，IoT终端节点101可以在其他任意合适的触发条件下发送该请求，而不限于上述示例。
如果DM 122拒绝该请求，则DM 122可以向IoT-SDM 121发送针对该请求的否定响应(未示出)。例如，DM 122可以向IoT-SDM 121发送RBM_enter.dec消息。当然，本公开实施例并不对该消息的形式作任何限制，而是可以采用其他任意合适形式。至此该过程400将结束。
如果DM 122接受该请求，则DM 122可以向IoT-SDM 121发送413针对该请求的肯定响应。例如，DM 122可以向IoT-SDM 121发送RBM_enter.cnf消息。当然，本公开实施例并不对该消息的形式作任何限制，而是可以采用其他任意合适形式。
IoT-SDM 121响应于接收到该肯定响应，确定进入RBM，并且可以发起信道评估的过程420。如图4所示，IoT-SDM 121向IoT终端节点101发送421用于请求针对电力线通信周期中的单个时间窗(为方便起见，在本文中也称为第一时间窗)执行信道评估的请求(为方便起见，在本文中也称为第一请求)。例如，IoT-SDM 121可以选择一个BAT区域(即，时间窗)，并且将所选择的BAT区域的信息(例如BAT区域ID或类似信息)包括在该请求中。例如，IoT-SDM 121可以向IoT终端节点101发送CE_Initiation.req消息作为该请求。当然，也可以采用其他任意合适的消息形式。
响应于该信道评估的请求，IoT终端节点101可以经由IoT-SDM 121向DM 122发送用于探测信号的资源分配的请求(为方便起见，在本文中也称为第三请求)，该请求包括关于所选择的BAT区域的信息。例如，IoT终端节点101可以向IoT-SDM 121发送422CE_ProbeSlotAssign.req消息作为该请求并且IoT-SDM 121将该消息转发423给DM 122。当然，也可以采用其他任意合适的消息形式。
响应于该资源分配的请求，DM 122可以经由IoT-SDM 121向IoT终端节点101发送关于资源分配的信息。例如，DM 122向IoT-SDM 121发送424关于资源分配的信息，并且IoT-SDM 121向IoT终端节点101转发425该信息。也就是，DM 122为IoT终端节点101分配用于探测信号的资源。例如，DM 122可以向IoT-SDM 121发送CE_ProbeSlotAssign.cnf消息并由IoT-SDM 121将该消息转发给IoT终端节点101，从而分配该资源。当然，也可以采用其他任意合适的消息形式。
继而，IoT终端节点101可以向IoT-SDM 121发送426针对第一请求的肯定响应。例如，IoT终端节点101可以向IoT-SDM 121发送CE_Initiation.cnf消息。当然，也可以采用其他任意合适的消息形式。
响应于该肯定响应，IoT-SDM 121可以向IoT终端节点101发送427用于发送探测信号的请求(为方便起见，在本文中也称为第四请求)。例如，IoT-SDM 121可以向IoT终端节点101发送CE_ProbeRequest.ind消息以便请求探测信号的发送。在一些实施例中，探测信号可以为探测帧(PROBE帧)或信道训练序列。当然，探测信号并不限于此，而是可以采用其他任意合适形式。
响应于该探测信号的请求，IoT终端节点101可以向IoT-SDM 121发送428探测信号。利用该探测信号，IoT-SDM 121可以进行信道评估，从而确定调制参数。该信道评估可以采 用本领域已知或未来开发的任意合适方式来实施，这里不作限制。应理解到，IoT-SDM 121可能需要多个探测信号来完成信道评估。在这种情况下，探测信号的请求和发送过程(即427和428所示的过程)可能需要多次执行。
继而，IoT-SDM 121将所确定的调制参数发送429给IoT终端节点101，以便用于所选择的时间窗内的数据传输。至此，完成了信道评估的过程420。接下来进入数据传输的过程430。
参考图4，DM 122可以向IoT-SDM 121发送431关于传输时机的信息，该传输时机覆盖第一时间窗。例如，DM 122可以基于第一时间窗的信息，生成新TXOP分配，并且向IoT-SDM 121发送包括新TXOP分配的MAP消息。在一些实施例中，新TXOP分配中可以存在CFTXOP，该CFTXOP覆盖针对IoT终端节点101所选择的BAT区域的位置。例如，该CFTXOP可以与BAT_ID＝x对应。在一些备选实施例中，新TXOP分配中可以存在STXOP，该STXOP覆盖针对IoT终端节点101所选择的BAT区域的位置。在该STXOP可以为IoT终端节点101分配最高优先级的CFTS。当然，本公开的实施例并不限于此，也可以采用其他任意合适的TXOP分配方式。下面以CFTXOP为例进行描述。
IoT-SDM 121可以向IoT终端节点101发送432所述关于传输时机的信息。例如，IoT-SDM 121可以向IoT终端节点101发送IoT-MAP消息，该IoT-MAP消息包括针对IoT-SDM 121的该CFTXOP分配。
继而，IoT终端节点101可以使用该CFTXOP、基于接收到的调制参数来与IoT-SDM 121进行上行IoT数据传输433。
图5示出了根据本公开实施例的退出RBM的过程500的示意图。为方便起见，下面结合图1的示例对图5进行说明。本例中的过程500适用于从RBM退出的任何上行或下行情形。应理解到，图5的过程可以包括其它未示出的附加过程，或者可以省略所示出的一些过程。本公开的范围并不受限于此。
在本实施例中，图5的过程510是在上行数据传输情形下退出RBM的过程。在这种情况下，IoT终端节点101为发送设备，IoT-SDM 121为接收设备，DM 122为控制设备。在上行数据传输情形下，该过程510可以由IoT终端节点101发起。
如图5所示，IoT终端节点101可以经由IoT-SDM 121向DM 122发送用于退出RBM的请求(为方便起见，在本文中也称为第五请求)。例如，IoT终端节点101可以向IoT-SDM 121发送511该请求，并且IoT-SDM 121向DM 122转发512该请求。例如，IoT终端节点101可以向IoT-SDM 121发送RBM_exit.req消息并由IoT-SDM 121将该消息转发给DM 122。当然，也可以采用其他任意合适的消息形式。
如果DM 122接受该请求，则DM 122可以经由IoT-SDM 121向IoT终端节点101发送针对该请求的肯定响应。例如，DM 122可以向IoT-SDM 121发送513该请求，并且IoT-SDM 121向IoT终端节点101转发514该请求。例如，DM 122可以向IoT-SDM 121发送RBM_exit.cnf消息并由IoT-SDM 121将该消息转发给IoT终端节点101。当然，也可以采用其他任意合适的消息形式。
在一些实施例中，当IoT-SDM 121接收到该肯定响应时，IoT-SDM 121可以释放针对第一时间窗的调制参数，即，针对所选择的BAT区域的BAT。在一些实施例中，当IoT终端节点101接收到该肯定响应时，IoT终端节点101可以释放针对第一时间窗的调制参数，即，针对所选择的BAT区域的BAT。
继续参考图5，过程520是在下行数据传输情形下退出RBM的过程。在这种情况下， IoT-SDM 121为发送设备，IoT终端节点101为接收设备，DM 122为控制设备。在下行数据传输情形下，该过程520可以由IoT-SDM 121发起。
如图5所示，IoT-SDM 121可以向DM 122发送521用于退出RBM的请求(为方便起见，在本文中也称为第五请求)。例如，IoT-SDM 121可以向DM 122发送RBM_exit.req消息。当然，也可以采用其他任意合适的消息形式。
如果DM 122接受该请求，则DM 122可以向IoT-SDM 121发送522针对该请求的肯定响应。例如，DM 122可以向IoT-SDM 121发送RBM_exit.cnf消息。当然，也可以采用其他任意合适的消息形式。
响应于接收到该肯定响应，IoT-SDM 121可以向IoT终端节点101发送523退出RBM的通知(为方便起见，在本文中也称为第二通知)。例如，DM 122可以向IoT-SDM 121转发RBM_exit.cnf消息。当然，也可以采用其他任意合适的消息形式。
在一些实施例中，当IoT-SDM 121接收到该肯定响应时，IoT-SDM 121可以释放针对第一时间窗的调制参数，即，针对所选择的BAT区域的BAT。在一些实施例中，当IoT终端节点101接收到该通知时，IoT终端节点101可以释放针对第一时间窗的调制参数，即，针对所选择的BAT区域的BAT。
上面结合图3至图5描述的实施例是以IoT-SDM 121与IoT终端节点101之间的通信为例进行描述的。然而，在一些实施例中，上述过程中IoT-SDM 121与IoT终端节点101之间的通信也可以经由一个或多个IoT中继节点来完成。此外，在一些实施例中，在IoT中继节点与IoT终端节点之间的通信也可以采用RBM。为了方便理解，下面结合图6对此进行更详细说明。
图6示出了根据本公开实施例的在下行方向上进入RBM的另一过程600的示意图。为方便起见，下面结合图1的示例对图6进行说明。在本例中，下行方向是指从IoT中继节点111向IoT终端节点101的数据传输。在这种情况下，IoT中继节点111为发送设备，IoT终端节点101为接收设备，DM 122为控制设备。应理解到，图6的过程可以包括其它未示出的附加过程，或者可以省略所示出的一些过程。本公开的范围并不受限于此。
在本实施例中，图6的过程600可以包括协商进入RBM的过程610、信道评估的过程620和数据传输的过程630(也可以称为资源分配的过程630)。
IoT中继节点111可以发起协商进入RBM的过程610。在一些实施例中，IoT中继节点111可以经由IoT-SDM 121向DM 122发送用于进入RBM的请求(为方便起见，在本文中也称为第二请求)。如图6所示，IoT中继节点111可以向IoT-SDM 121发送611该请求，IoT-SDM 121可以将该请求转发612给DM 122。例如，IoT中继节点111可以向IoT-SDM 121发送RBM_enter.req消息并由IoT-SDM 121将该消息转发给DM 122。当然，本公开实施例并不对消息的形式作任何限制，而是可以采用其他任意合适形式。
在一些实施例中，IoT中继节点111可以监测数据传输的速率，并且当数据传输的速率大于预定阈值速率时发送该请求。在一些实施例中，该预定阈值速率可以根据需要动态配置。在一些实施例中，该阈值预定阈值速率可以是预先配置的。在一些备选实施例中，IoT中继节点111可以监测数据传输的业务类型，并且当业务类型为预定业务类型时发送该请求。例如，预定业务类型指示高速率数据传输。在一些备选实施例中，IoT中继节点111可以响应于接收到进入RBM的指令(为方便起见，在本文中也称为第一指令)而发送该请求。在一些实施例中，该指令可以来自例如MAC层、应用层等上层控制。应理解到，IoT中继节点111 可以在其他任意合适的触发条件下发送该请求，而不限于上述示例。
如果DM 122拒绝该请求，则DM 122可以向IoT-SDM 121发送针对该请求的否定响应(未示出)。例如，DM 122可以向IoT-SDM 121发送RBM_enter.dec消息。当然，本公开实施例并不对该消息的形式作任何限制，而是可以采用其他任意合适形式。至此该过程600将结束。
如果DM 122接受该请求，则DM 122可以向IoT-SDM 121发送613针对该请求的肯定响应，并且IoT-SDM 121将该肯定响应转发614给IoT中继节点111。例如，DM 122可以向IoT-SDM 121发送RBM_enter.cnf消息，并且由IoT-SDM 121将该消息转发给IoT中继节点111。当然，本公开实施例并不对该消息的形式作任何限制，而是可以采用其他任意合适形式。
IoT中继节点111响应于接收到该肯定响应，可以向IoT终端节点101发送615进入RBM的通知(为方便起见，在本文中也称为第一通知)。例如，IoT中继节点111可以向IoT终端节点101发送RBM_enter.cnf消息。当然，本公开实施例并不对该消息的形式作任何限制，而是可以采用其他任意合适形式。至此，完成了协商进入RBM的过程610，并进入RBM。
在RBM下，IoT终端节点101可以发起信道评估的过程620。如图6所示，IoT终端节点101向IoT中继节点111发送621用于请求针对电力线通信周期中的单个时间窗(为方便起见，在本文中也称为第一时间窗)执行信道评估的请求(为方便起见，在本文中也称为第一请求)。例如，IoT终端节点101可以选择一个BAT区域(即，时间窗)，并且将所选择的BAT区域的信息(例如BAT区域ID或类似信息)包括在该请求中。例如，IoT终端节点101可以向IoT中继节点111发送CE_Initiation.req消息作为该请求。当然，也可以采用其他任意合适的消息形式。
响应于该信道评估的请求，IoT中继节点111可以经由IoT-SDM 121向DM 122发送用于探测信号的资源分配的请求(为方便起见，在本文中也称为第三请求)，该请求包括关于所选择的BAT区域的信息。在一些实施例中，IoT中继节点111可以向IoT-SDM 121发送622该资源分配请求，并且IoT-SDM 121可以向DM 122转发623该资源分配请求。例如，IoT中继节点111可以向IoT-SDM 121发送CE_ProbeSlotAssign.req消息，并且由IoT-SDM 121向DM 122转发该消息。当然，也可以采用其他任意合适的消息形式。
响应于该资源分配的请求，DM 122可以经由IoT-SDM 121向IoT中继节点111发送关于资源分配的信息。也就是，DM 122为IoT中继节点111分配用于发送探测信号的资源。在一些实施例中，DM 122可以向IoT-SDM 121发送关于资源分配的信息，并且IoT-SDM 121向IoT中继节点111转发该信息。例如，DM 122可以向IoT-SDM 121发送CE_ProbeSlotAssign.cnf消息，并由IoT-SDM 121向IoT中继节点111转发该消息，从而分配资源。当然，也可以采用其他任意合适的消息形式。
响应于接收到关于资源分配的信息，IoT中继节点111可以向IoT终端节点101发送626针对第一请求的肯定响应。例如，IoT中继节点111可以向IoT终端节点101发送CE_Initiation.cnf消息。当然，也可以采用其他任意合适的消息形式。
响应于该肯定响应，IoT终端节点101可以向IoT中继节点111发送627用于发送探测信号的请求(为方便起见，在本文中也称为第四请求)。例如，IoT终端节点101可以向IoT中继节点111发送CE_ProbeRequest.ind消息以便请求探测信号的发送。在一些实施例中，探测信号可以为探测帧(PROBE帧)或信道训练序列。当然，探测信号并不限于此，而是可以采用其他任意合适形式。
响应于该探测信号的请求，IoT中继节点111可以向IoT终端节点101发送628探测信号。利用该探测信号，IoT终端节点101可以进行信道评估，从而确定调制参数。该信道评估可以采用本领域已知或未来开发的任意合适方式来实施，这里不作限制。应理解到，IoT终端节点101可能需要多个探测信号来完成信道评估。在这种情况下，探测信号的请求和发送过程(即627和628所示的过程)可能需要多次执行。
继而，IoT终端节点101将所确定的调制参数发送629给IoT终端节点101，以便用于所选择的时间窗内的数据传输。至此，完成了信道评估的过程620。接下来进入数据传输的过程630。
参考图6，DM 122可以向IoT-SDM 121发送631关于传输时机的信息，该传输时机覆盖第一时间窗。例如，DM 122可以基于第一时间窗的信息，生成新TXOP分配，并且向IoT-SDM 121发送包括新TXOP分配的MAP消息。在一些实施例中，新TXOP分配中可以存在CFTXOP，该CFTXOP覆盖针对IoT终端节点101所选择的BAT区域的位置。例如，该CFTXOP可以与BAT_ID＝x对应。在一些备选实施例中，新TXOP分配中可以存在STXOP，该STXOP覆盖针对IoT终端节点101所选择的BAT区域的位置。在该STXOP可以为IoT终端节点101分配最高优先级的CFTS。当然，本公开的实施例并不限于此，也可以采用其他任意合适的TXOP分配方式。下面以CFTXOP为例进行描述。
IoT-SDM 121可以将关于传输时机的信息发送632给IoT中继节点111。例如，IoT-SDM 121可以向IoT中继节点111发送IoT-MAP消息，该IoT-MAP消息包括针对IoT中继节点111的该CFTXOP分配。IoT中继节点111可以向IoT终端节点101发送633所述关于传输时机的信息。例如，IoT中继节点111可以向IoT终端节点101发送IoT-MAP消息，该IoT-MAP消息包括针对IoT中继节点111的该CFTXOP分配。
继而，IoT中继节点111可以使用该CFTXOP、基于接收到的调制参数来与IoT终端节点101进行下行IoT数据传输634。应理解到，上述结合图3至图6描述的过程仅为示例，本公开实施例并不限于此，而是可以通过任意合适的方式来实施RBM。
根据本公开实施例提出的方案，可以在ROBO模式之外，保留针对单个时间窗进行训练以逼近信道极限的能力。平时小流量状态下RBM模式关闭，通过历史流量或上层触发来启动RBM以获得速率提升的收益。由此，可以保持IoT芯片的复杂度。此外，通过物理层和MAC层的协同配合，基于选定时间窗调度来对IoT节点固定调度相应时隙。因此，可以在有限的复杂度提升的情况下，使用少量的资源实现高的速率性能以及资源利用效率。
与上述RBM过程相对应，本公开实施例提供了在发送设备处实施的用于IoT的PLC的方法、在接收设备处实施的用于IoT的PLC的方法以及在控制设备处实施的用于IoT的PLC的方法。图7示出了根据本公开实施例的发送设备处实施的用于IoT的PLC的方法700的流程图。该方法700可以在PLC IoT网络中的发送设备(例如IoT-SDM 121、IoT中继节点111或IoT终端节点101)处实施。为了方便起见，这里将结合图1的示例对图7进行说明。应理解到，图7的方法可以包括其它未示出的附加步骤，或者可以省略示出的一些步骤。本公开的范围并不受限于此。
如图7所示，在框710处，发送设备接收来自接收设备的第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估。在一些实施例中，发送设备可以为IoT-SDM 121，接收设备可以为IoT终端节点101。在一些实施例中，发送设备可以为IoT终端节点101，接收设备可以为IoT-SDM 121。在一些实施例中，发送设备可以为IoT中继节点 111，接收设备可以为IoT终端节点101。在一些实施例中，发送设备可以为IoT终端节点101，接收设备可以为IoT中继节点111。
在一些实施例中，发送设备可以向接收设备发送进入第一模式的第一通知，在所述第一模式中所述发送设备和所述接收设备基于所述电力线通信周期中的至少一个时间窗来进行数据传输。继而，发送设备可以接收由接收设备响应于该第一通知而发送的第一请求。在一些实施例中，第一模式为RBM。
在一些实施例中，响应于数据传输的速率大于预定阈值速率，发送设备可以向控制设备(例如DM 122)发送用于进入第一模式的第二请求。响应于接收到来自DM 122的针对第二请求的肯定响应，发送设备可以向接收设备发送第一通知。在一些备选实施例中，发送设备可以响应于接收到进入第一模式的第一指令，向DM 122发送用于进入第一模式的第二请求。响应于接收到来自DM 122的针对第二请求的肯定响应，发送设备可以向接收设备发送第一通知。
在框720处，响应于第一请求，发送设备向接收设备发送用于执行信道评估所需的探测信号。在一些实施例中，发送设备可以向DM 122发送用于探测信号的资源分配的第三请求，所述第三请求包括关于所述第一时间窗的信息。响应于接收到来自DM 122的关于资源分配的信息，发送设备可以向接收设备发送针对第一请求的肯定响应。响应于接收到来自接收设备的用于发送探测信号的第四请求，发送设备可以基于关于资源分配的信息向接收设备发送探测信号。
在框730处，发送设备从接收设备接收调制参数，该调制参数是由接收设备通过基于探测信号执行信道评估而确定的。
在框740处，发送设备基于调制参数，与接收设备在第一时间窗上进行数据传输。在一些实施例中，发送设备接收来自DM 122的关于传输时机的信息，该传输时机覆盖第一时间窗。继而，发送设备可以在传输时机上、利用调制参数来向接收设备发送数据。在一些实施例中，发送设备可以向接收设备发送该关于传输时机的信息，以便接收设备接收数据。
在一些实施例中，发送设备可以向接收设备发送退出第一模式的第二通知。在一些实施例中，发送设备可以响应于数据传输的速率小于预定阈值速率而向DM 122发送用于退出第一模式的第五请求，并且响应于接收到来自DM 122的针对第五请求的肯定响应，向接收设备发送第二通知。在一些备选实施例中，发送设备可以响应于接收到用于退出第一模式的第二指令，来向DM 122发送用于退出第一模式的第五请求，并且响应于接收到来自DM 122的针对第五请求的肯定响应，向接收设备发送第二通知。在一些实施例中，响应于接收到来自DM 122的针对第五请求的肯定响应，发送设备可以释放调制参数。从而节省调制参数的维护成本。
以上关于图7描述的处理与图3至图6中的相应操作对应，其它细节可参照图3至图6的相关描述，这里不再赘述。根据图7的方法，可以完成PLC IoT网络节点在RBM下发送数据的操作。与ROBO模式相比，发送数据的效率大幅提升。
相应地，本公开实施例还提供在接收设备处实施的用于IoT的PLC的方法。图8示出了根据本公开实施例的接收设备处实施的用于IoT的PLC的方法800的流程图。该方法800可以在PLC IoT网络中的接收设备(例如IoT-SDM 121、IoT中继节点111或IoT终端节点101)处实施。为了方便起见，这里将结合图1的示例对图8进行说明。应理解到，图8的方法可以包括其它未示出的附加步骤，或者可以省略示出的一些步骤。本公开的范围并不受限于此。
如图8所示，在框810处，接收设备向发送设备发送第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估。在一些实施例中，发送设备可以为IoT-SDM 121，接收设备可以为IoT终端节点101。在一些实施例中，发送设备可以为IoT终端节点101，接收设备可以为IoT-SDM 121。在一些实施例中，发送设备可以为IoT中继节点111，接收设备可以为IoT终端节点101。在一些实施例中，发送设备可以为IoT终端节点101，接收设备可以为IoT中继节点111。
在一些实施例中，接收设备可以接收来自发送设备的进入第一模式的第一通知，在第一模式中发送设备和接收设备基于电力线通信周期中的至少一个时间窗来进行数据传输。响应于第一通知，接收设备可以向发送设备发送该第一请求。在一些实施例中，第一模式为RBM。
在框820处，接收设备接收发送设备响应于第一请求所发送的用于执行信道评估所需的探测信号。在一些实施例中，接收设备可以从发送设备接收针对第一请求的肯定响应。响应于该肯定响应，接收设备可以向发送设备发送用于发送探测信号的第四请求，并且接收由发送设备响应于第四请求而发送的探测信号。
在框830处，接收设备向发送设备发送调制参数，调制参数是由接收设备通过基于探测信号执行信道评估而确定的。
在框840处，接收设备与发送设备在第一时间窗上基于调制参数进行数据传输。在一些实施例中，接收设备接收来自发送设备的关于传输时机的信息，所述传输时机覆盖所述第一时间窗。继而，接收设备可以基于该传输时机来接收来自发送设备的数据。
在一些实施例中，接收设备可以接收来自发送设备的退出第一模式的第二通知。在一些实施例中，响应于接收到该第二通知，接收设备可以释放上述调制参数。从而节省调制参数的维护成本。
以上关于图8描述的处理与图3至图6中的相应操作对应，其它细节可参照图3至图6的相关描述，这里不再赘述。根据图8的方法，可以完成PLC IoT网络节点在RBM下接收数据的操作。与ROBO模式相比，接收数据的效率大幅提升。
相应地，本公开实施例还提供在控制设备处实施的用于IoT的PLC的方法。图9示出了根据本公开实施例的控制设备处实施的用于IoT的PLC的方法900的流程图。该方法900可以在PLC IoT网络中的控制设备(例如DM 122)处实施。为了方便起见，这里将结合图1的示例对图9进行说明。应理解到，图9的方法可以包括其它未示出的附加步骤，或者可以省略示出的一些步骤。本公开的范围并不受限于此。
如图9所示，在框910处，控制设备(例如DM 122)接收来自发送设备的用于探测信号的资源分配的第三请求，所述第三请求包括关于电力线通信周期中的第一时间窗的信息。第三请求是由发送设备响应于来自接收设备的第一请求而发送的，所述第一请求用于请求针对第一时间窗执行信道评估。在一些实施例中，发送设备可以为IoT-SDM 121，接收设备可以为IoT终端节点101。在一些实施例中，发送设备可以为IoT终端节点101，接收设备可以为IoT-SDM 121。在一些实施例中，发送设备可以为IoT中继节点111，接收设备可以为IoT终端节点101。在一些实施例中，发送设备可以为IoT终端节点101，接收设备可以为IoT中继节点111。
在一些实施例中，在接收第三请求之前，DM 122可以接收来自发送设备的用于进入第一模式的第二请求，在第一模式中发送设备和接收设备基于电力线通信周期中的至少一个时间窗来进行数据传输。DM 122可以向发送设备发送针对第二请求的肯定响应，以便发送设可以 向接收设备发送进入第一模式的第一通知。在一些实施例中，第一模式为RBM。
在框920处，DM 122向发送设备发送关于资源分配的信息。由此，发送设备可以基于该信息向接收设备发送探测信号，以便接收设备可以基于探测信号完成信道评估，进而确定调制参数并发送给发送设备。
在一些实施例中，DM 122可以向发送设备发送关于传输时机的信息，该传输时机覆盖第一时间窗。在一些实施例中，DM 122可以接收来自发送设备的用于退出第一模式的第五请求。在一些实施例中，DM 122可以向发送设备发送针对第五请求的肯定响应。
以上关于图9描述的处理与图3至图6中的相应操作对应，其它细节可参照图3至图6的相关描述，这里不再赘述。根据图9的方法，可以完成PLC IoT网络节点在RBM下控制数据传输的操作。与ROBO模式相比，通过物理层和MAC层协作，大幅提升单位资源上的传输性能，锁定物理层时隙位置进行数据流传输。
总体而言，根据本公开实施例的方案，针对IoT数据传输引入RBM，在RBM下发送设备和接收设备基于电力线通信周期中的至少一个时间窗来进行数据传输。由此，使用少量的资源实现高的速率性能，逼近宽带节点在通信中的资源利用效率。从而实现PLC宽带和PLC IoT融合网络中各节点的速率性能的提升和资源利用效率的提升。
与上述方法相对应，本公开实施例还提供用于IoT的PLC的装置和设备，下面结合图10至图13对此进行描述。图10示出了根据本公开实施例的在发送设备处实施的用于IoT的PLC的装置1000的示意框图。装置1000可以在PLC IoT网络中的发送设备(例如图1的IoT-SDM 121、IoT终端节点101或IoT中继节点111)处实施。为方便起见，下面结合图1的示例对图10进行描述。装置1000可以是该发送设备的一部分，也可以是发送设备本身。应理解到，装置1000可以包括比所示组件更多的附加组件或者省略其中所示的一部分组件，本公开实施例对此并不进行限制。
如图10所示，装置1000包括第一请求接收单元1010、探测信号发送单元1020、调制参数接收单元1030和第一数据传输单元1040。第一请求接收单元1010被配置用于接收来自接收设备的第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估。探测信号发送单元1020被配置用于响应于第一请求来向接收设备发送用于执行信道评估所需的探测信号。调制参数接收单元1030被配置用于从接收设备接收调制参数，所述调制参数是通过基于探测信号执行信道评估而确定的。第一数据传输单元1040被配置用于基于调制参数来与接收设备在第一时间窗上进行数据传输。
在一些实施例中，第一请求接收单元1010可以包括第一通知发送单元和请求接收单元。通知发送单元可以被配置用于向接收设备发送进入第一模式的第一通知，在第一模式中发送设备和接收设备基于电力线通信周期中的至少一个时间窗来进行数据传输。请求接收单元可以被配置用于接收由接收设备响应于第一通知而发送的第一请求。在一些实施例中，第一模式为RBM。
在一些实施例中，通知发送单元可以被配置用于响应于数据传输的速率大于预定阈值速率来向控制设备发送用于进入第一模式的第二请求，并且响应于接收到来自控制设备的针对第二请求的肯定响应来向接收设备发送第一通知。在一些备选实施例中，通知发送单元可以被配置用于响应于接收到进入第一模式的第一指令来向控制设备发送用于进入第一模式的第二请求，并且响应于接收到来自控制设备的针对第二请求的肯定响应来向接收设备发送第一通知。
在一些实施例中，探测信号发送单元1020可以包括第一发送单元、第二发送单元和第三发送单元。第一发送单元可以被配置用于向控制设备发送用于探测信号的资源分配的第三请求，所述第三请求包括关于所述第一时间窗的信息。第二发送单元可以被配置用于响应于接收到来自控制设备的关于资源分配的信息，向接收设备发送针对第一请求的肯定响应。第三发送单元被配置用于响应于接收到来自接收设备的用于发送探测信号的第四请求，基于关于资源分配的信息向接收设备发送探测信号。
在一些实施例中，第一数据传输单元1040可以包括传输时机接收单元和数据传输单元。传输时机接收单元可以被配置用于接收来自控制设备的关于传输时机的信息，所述传输时机覆盖所述第一时间窗。数据传输单元可以被配置用于在所述传输时机上、利用所述调制参数来与接收设备进行数据传输。在一些实施例中，第一数据传输单元1040还可以包括传输时机发送单元，被配置用于向接收设备发送关于传输时机的信息。
在一些实施例中，装置1000还可以包括第二通知发送单元，被配置用于向接收设备发送退出第一模式的第二通知。在一些实施例中，第二通知发送单元可以被配置用于响应于数据传输的速率小于预定阈值速率来向控制设备发送用于退出第一模式的第五请求，并且响应于接收到来自控制设备的针对第五请求的肯定响应来向接收设备发送第二通知。在一些备选实施例中，第二通知发送单元可以被配置用于响应于接收到用于退出第一模式的第二指令来向控制设备发送用于退出第一模式的第五请求，并且响应于接收到来自控制设备的针对第五请求的肯定响应来向接收设备发送第二通知。
在一些实施例中，装置1000还可以包括调制参数释放单元，被配置用于响应于接收到来自控制设备的针对第五请求的肯定响应来释放调制参数。
图11示出了根据本公开实施例的在接收设备处实施的用于IoT的PLC的装置1100的示意框图。装置1100可以在PLC IoT网络中的接收设备(例如图1的IoT-SDM 121、IoT终端节点101或IoT中继节点111)处实施。为方便起见，下面结合图1的示例对图11进行描述。装置1100可以是接收设备的一部分，也可以是接收设备本身。应理解到，装置1100可以包括比所示组件更多的附加组件或者省略其中所示的一部分组件，本公开实施例对此并不进行限制。
如图11所示，装置1100包括第一请求发送单元1110、探测信号接收单元1120、调制参数发送单元1130和第二数据传输单元1140。第一请求发送单元1110被配置用于向发送设备发送第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估。探测信号接收单元1120被配置用于接收由发送设备响应于第一请求所发送的用于执行信道评估所需的探测信号。调制参数发送单元1130被配置用于向发送设备发送调制参数，所述调制参数是通过基于探测信号执行信道评估而确定的。第二数据传输单元1140被配置用于与发送设备在第一时间窗上基于调制参数进行数据传输。
在一些实施例中，第一请求发送单元1110可以包括通知接收单元和请求发送单元。通知接收单元可以被配置用于接收来自发送设备的进入第一模式的第一通知，在第一模式中发送设备和接收设备基于电力线通信周期中的至少一个时间窗来进行数据传输。请求发送单元可以被配置用于响应于第一通知来向发送设备发送第一请求。在一些实施例中，第一模式为RBM。
在一些实施例中，探测信号接收单元1120可以包括第一接收单元、发送单元和第二接收单元。第一接收单元可以被配置用于从发送设备接收针对第一请求的肯定响应。发送单元可 以被配置用于响应于肯定响应而向发送设备发送用于发送探测信号的第四请求。第二接收单元可以被配置用于接收由发送设备响应于第四请求而发送的探测信号。
在一些实施例中，第二数据传输单元1140可以包括传输时机接收单元和数据传输单元。传输时机接收单元可以被配置用于接收来自发送设备的关于传输时机的信息，该传输时机覆盖第一时间窗。数据传输单元可以被配置用于基于该传输时机来进行数据传输。
在一些实施例中，装置1100还可以包括第二通知接收单元和调制参数释放单元。第二通知接收单元可以被配置用于接收来自发送设备的退出第一模式的第二通知。调制参数释放单元可以被配置用于响应于第二通知来释放调制参数。
图12示出了根据本公开实施例的在控制设备处实施的用于IoT的PLC的装置1200的示意框图。装置1200可以在PLC IoT网络中的控制设备(例如图1的DM 122)处实施。为方便起见，下面结合图1的示例对图12进行描述。装置1200可以是DM 122的一部分，也可以是DM 122本身。应理解到，装置1200可以包括比所示组件更多的附加组件或者省略其中所示的一部分组件，本公开实施例对此并不进行限制。
如图12所示，装置1200包括第三请求接收单元1210和资源分配单元1220。第三请求接收单元1210被配置用于接收来自发送设备的用于探测信号的资源分配的第三请求，所述第三请求包括关于电力线通信周期中的第一时间窗的信息。所述第三请求是由所述发送设备响应于来自接收设备的第一请求而发送的，所述第一请求用于请求针对所述第一时间窗执行信道评估。资源分配单元1220被配置用于向发送设备发送关于所述资源分配的信息。
在一些实施例中，装置1200还可以包括第二请求接收单元和第一响应发送单元。第二请求接收单元可以被配置用于接收来自发送设备的用于进入第一模式的第二请求，在所述第一模式中所述发送设备和所述接收设备基于所述电力线通信周期中的至少一个时间窗来进行数据传输。响应发送单元可以被配置用于向发送设备发送针对第二请求的肯定响应，以便向接收设备发送进入第一模式的第一通知。在一些实施例中，第一模式为RBM。
在一些实施例中，装置1200还可以包括传输时机发送单元，被配置用于向发送设备发送关于传输时机的信息，所述传输时机覆盖所述第一时间窗。在一些实施例中，装置1200还可以包括第五请求接收单元和第二响应发送单元。第五请求接收单元可以被配置用于接收来自发送设备的用于退出第一模式的第五请求。第二响应发送单元可以被配置用于发送针对第五请求的肯定响应。
图13是适合于实现本公开的实施例的设备1300的简化框图。可以提供设备1300以实现PLC IoT通信装置(发送设备或接收设备)或控制设备，例如图1所示的IoT-SDM 121、DM 122、IoT终端节点101和IoT中继节点111中的任一个设备。如图所示，设备1300包括至少一个处理器1310以及耦合到至少一个处理器1310的至少一个PLC接口1320。PLC接口1320可以包括电源插头接口1321、模拟前端(AFE，Analog Front End)1322和数字前端(DFE，Digital Front End)1323。
电源插头接口1321可以耦接至外部电源插头。该电源插头接口可以表示PLC所需的任何接口。AFE 1322可以包括模拟信号处理元件，并且DFE 1323可以包括数字信号处理元件。
处理器1310可以是适合于本地技术网络的任何类型，并且作为限制性示例，可以包括以下中的一个或多个：通用计算机、专用计算机、微处理器、数字信号处理器和基于多核处理器架构的处理器。设备1300可以具有多个处理器，例如专用集成电路芯片，其在时间上从属于与主处理器同步的时钟。
处理器1310可以被操作用于通过PLC接口1320来实现本公开的实施例，使得设备1300执行如参考图3至图12所讨论的本公开的处理。设备1300可以对应于上述装置1000、装置1100或装置1200，装置1000、装置1100或装置1200中的每个功能模块可以通过处理器1310结合PLC接口1320来实现。本公开的实施例还可以通过软件或通过软件和硬件的组合来实现。
在一些实施例中，设备1300还可以包括存储器(未示出)。存储器可以包括一个或多个非易失性存储器和一个或多个易失性存储器。非易失性存储器的示例包括但不限于只读存储器(ROM)、电可编程只读存储器(EPROM)、闪存、硬盘、光盘(CD)、数字视频盘(DVD)和其他磁存储和/或光存储装置。易失性存储器的示例包括但不限于随机存取存储器(RAM)和不会在断电持续时间中持续的其他易失性存储器。计算机程序包括由关联的处理器1310执行的计算机可执行指令。程序可以存储在存储器中。处理器1310可以通过将程序加载到存储器中来执行任何合适的动作和处理。
一般而言，本公开的各种示例实施例可以在硬件或专用电路、软件、逻辑，或其任何组合中实施。某些方面可以在硬件中实施，而其他方面可以在可以由控制器、微处理器或其他计算设备执行的固件或软件中实施。当本公开的实施例的各方面被图示或描述为框图、流程图或使用某些其他图形表示时，将理解此处描述的方框、装置、系统、技术或方法可以作为非限制性的示例在硬件、软件、固件、专用电路或逻辑、通用硬件或控制器或其他计算设备，或其某些组合中实施。可用来实现本公开实施例的硬件器件的示例包括但不限于：现场可编程门阵列(FPGA)、专用集成电路(ASIC)、专用标准产品(ASSP)、片上系统(SOC)、复杂可编程逻辑器件(CPLD)，等等。
作为示例，本公开的实施例可以在机器可执行指令的上下文中被描述，机器可执行指令诸如包括在目标的真实或者虚拟处理器上的器件中执行的程序模块中。一般而言，程序模块包括例程、程序、库、对象、类、组件、数据结构等，其执行特定的任务或者实现特定的抽象数据结构。在各实施例中，程序模块的功能可以在所描述的程序模块之间合并或者分割。用于程序模块的机器可执行指令可以在本地或者分布式设备内执行。在分布式设备中，程序模块可以位于本地和远程存储介质二者中。
用于实现本公开的方法的计算机程序代码可以用一种或多种编程语言编写。这些计算机程序代码可以提供给通用计算机、专用计算机或其他可编程的数据处理装置的处理器，使得程序代码在被计算机或其他可编程的数据处理装置执行的时候，引起在流程图和/或框图中规定的功能/操作被实施。程序代码可以完全在计算机上、部分在计算机上、作为独立的软件包、部分在计算机上且部分在远程计算机上或完全在远程计算机或服务器上执行。
在本公开的上下文中，计算机程序代码或者相关数据可以由任意适当载体承载，以使得设备、装置或者处理器能够执行上文描述的各种处理和操作。载体的示例包括信号、计算机可读介质等等。
信号的示例可以包括电、光、无线电、声音或其它形式的传播信号，诸如载波、红外信号等。
机器可读介质可以是包含或存储用于或有关于指令执行系统、装置或设备的程序的任何有形介质。机器可读介质可以是机器可读信号介质或机器可读存储介质。机器可读介质可以包括但不限于电子的、磁的、光学的、电磁的、红外的或半导体系统、装置或设备，或其任意合适的组合。机器可读存储介质的更详细示例包括带有一根或多根导线的电气连接、便携 式计算机磁盘、硬盘、随机存储存取器(RAM)、只读存储器(ROM)、可擦除可编程只读存储器(EPROM或闪存)、光存储设备、磁存储设备，或其任意合适的组合。
另外，尽管操作以特定顺序被描绘，但这并不应该理解为要求此类操作以示出的特定顺序或以相继顺序完成，或者执行所有图示的操作以获取期望结果。在某些情况下，多任务或并行处理会是有益的。同样地，尽管上述讨论包含了某些特定的实施细节，但这并不应解释为限制任何发明或权利要求的范围，而应解释为对可以针对特定发明的特定实施例的描述。本说明书中在分开的实施例的上下文中描述的某些特征也可以整合实施在单个实施例中。反之，在单个实施例的上下文中描述的各种特征也可以分离地在多个实施例或在任意合适的子组合中实施。
尽管已经以特定于结构特征和/或方法动作的语言描述了主题，但是应当理解，所附权利要求中限定的主题并不限于上文描述的特定特征或动作。相反，上文描述的特定特征和动作是作为实现权利要求的示例形式而被公开的。

Claims (46)

  1. 一种用于物联网的电力线通信的方法，其特征在于，包括：
    发送设备接收来自接收设备的第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估；
    响应于所述第一请求，所述发送设备向所述接收设备发送用于执行所述信道评估所需的探测信号；
    所述发送设备从所述接收设备接收调制参数，所述调制参数是通过基于所述探测信号执行所述信道评估而确定的；以及
    所述发送设备基于所述调制参数，与所述接收设备在所述第一时间窗上进行数据传输。
  2. 根据权利要求1所述的方法，其特征在于，接收所述第一请求包括：
    所述发送设备向所述接收设备发送进入第一模式的第一通知，在所述第一模式中所述发送设备和所述接收设备基于所述电力线通信周期中的至少一个时间窗来进行数据传输；以及
    所述发送设备接收所述接收设备响应于所述第一通知而发送的所述第一请求。
  3. 根据权利要求2所述的方法，其特征在于，所述第一模式为速率提升模式RBM。
  4. 根据权利要求2所述的方法，其特征在于，发送所述第一通知包括：
    响应于所述数据传输的速率大于预定阈值速率，所述发送设备向控制设备发送用于进入所述第一模式的第二请求；以及
    响应于接收到来自所述控制设备的针对所述第二请求的肯定响应，所述发送设备向所述接收设备发送所述第一通知。
  5. 根据权利要求2所述的方法，其特征在于，发送所述第一通知包括：
    响应于接收到进入所述第一模式的第一指令，所述发送设备向控制设备发送用于进入所述第一模式的第二请求；以及
    响应于接收到来自所述控制设备的针对所述第二请求的肯定响应，所述发送设备向所述接收设备发送所述第一通知。
  6. 根据权利要求1所述的方法，其特征在于，发送所述探测信号包括：
    所述发送设备向控制设备发送用于探测信号的资源分配的第三请求，所述第三请求包括关于所述第一时间窗的信息；
    响应于接收到来自所述控制设备的关于所述资源分配的信息，所述发送设备向所述接收设备发送针对所述第一请求的肯定响应；以及
    响应于接收到来自所述接收设备的用于发送探测信号的第四请求，所述发送设备基于所述关于所述资源分配的信息向所述接收设备发送所述探测信号。
  7. 根据权利要求1所述的方法，其特征在于，进行所述数据传输包括：
    所述发送设备接收来自控制设备的关于传输时机的信息，所述传输时机覆盖所述第一时间窗；以及
    所述发送设备在所述传输时机上、利用所述调制参数来与所述接收设备进行所述数据传输。
  8. 根据权利要求7所述的方法，其特征在于，还包括：
    所述发送设备向所述接收设备发送所述关于传输时机的信息。
  9. 根据权利要求2所述的方法，其特征在于，还包括：
    所述发送设备向所述接收设备发送退出所述第一模式的第二通知。
  10. 根据权利要求9所述的方法，其特征在于，发送所述第二通知包括：
    响应于所述数据传输的速率小于预定阈值速率，所述发送设备向控制设备发送用于退出所述第一模式的第五请求；以及
    响应于接收到来自所述控制设备的针对所述第五请求的肯定响应，所述发送设备向所述接收设备发送所述第二通知。
  11. 根据权利要求9所述的方法，其特征在于，发送所述第二通知包括：
    响应于接收到用于退出所述第一模式的第二指令，所述发送设备向控制设备发送用于退出所述第一模式的第五请求；以及
    响应于接收到来自所述控制设备的针对所述第五请求的肯定响应，所述发送设备向所述接收设备发送所述第二通知。
  12. 根据权利要求10或11所述的方法，其特征在于，还包括：
    响应于接收到来自所述控制设备的针对所述第五请求的肯定响应，所述发送设备释放所述调制参数。
  13. 根据权利要求4所述的方法，其特征在于，所述发送设备为物联网子域节点，所述接收设备为物联网终端节点，并且所述控制设备为电力线通信网络主节点。
  14. 根据权利要求4所述的方法，其特征在于，所述发送设备为物联网终端设备，所述接收设备为物联网子域节点，并且所述控制设备为电力线通信网络主节点。
  15. 一种用于物联网的电力线通信的方法，其特征在于，包括：
    接收设备向发送设备发送第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估；
    所述接收设备接收所述发送设备响应于所述第一请求所发送的用于执行所述信道评估所需的探测信号；
    所述接收设备向所述发送设备发送调制参数，所述调制参数是通过基于所述探测信号执行所述信道评估而确定的；以及
    所述接收设备与所述发送设备在所述第一时间窗上基于所述调制参数进行数据传输。
  16. 根据权利要求15所述的方法，其特征在于，发送所述第一请求包括：
    所述接收设备接收来自所述发送设备的进入第一模式的第一通知，在所述第一模式中所述发送设备和所述接收设备基于所述电力线通信周期中的至少一个时间窗来进行数据传输；以及
    响应于所述第一通知，所述接收设备向所述发送设备发送所述第一请求。
  17. 根据权利要求16所述的方法，其特征在于，所述第一模式为速率提升模式RBM。
  18. 根据权利要求15所述的方法，其特征在于，接收所述探测信号包括：
    所述接收设备从所述发送设备接收针对所述第一请求的肯定响应；
    响应于所述肯定响应，所述接收设备向所述发送设备发送用于发送探测信号的第四请求；以及
    所述接收设备接收由所述发送设备响应于所述第四请求而发送的所述探测信号。
  19. 根据权利要求15所述的方法，其特征在于，进行所述数据传输包括：
    所述接收设备接收来自所述发送设备的关于传输时机的信息，所述传输时机覆盖所述第一时间窗；以及
    所述接收设备基于所述传输时机来进行所述数据传输。
  20. 根据权利要求15所述的方法，其特征在于，还包括：
    所述接收设备接收来自所述发送设备的退出所述第一模式的第二通知；以及
    响应于所述第二通知，所述接收设备释放所述调制参数。
  21. 根据权利要求15所述的方法，其特征在于，所述发送设备为物联网网关，并且所述接收设备为物联网终端节点。
  22. 根据权利要求15所述的方法，其特征在于，所述发送设备为物联网终端设备，并且所述接收设备为物联网子域节点。
  23. 一种用于物联网的电力线通信的方法，其特征在于，包括：
    控制设备接收来自发送设备的用于探测信号的资源分配的第三请求，所述第三请求包括关于电力线通信周期中的第一时间窗的信息，所述第三请求是由所述发送设备响应于来自接收设备的第一请求而发送的，所述第一请求用于请求针对所述第一时间窗执行信道评估；以及
    所述控制设备向所述发送设备发送关于所述资源分配的信息。
  24. 根据权利要求23所述的方法，其特征在于，在接收所述第三请求之前，还包括：
    所述控制设备接收来自所述发送设备的用于进入第一模式的第二请求，在所述第一模式中所述发送设备和所述接收设备基于所述电力线通信周期中的至少一个时间窗来进行数据传输；以及
    所述控制设备向所述发送设备发送针对所述第二请求的肯定响应，以便所述发送设备向所述接收设备发送进入所述第一模式的第一通知。
  25. 根据权利要求24所述的方法，其特征在于，所述第一模式为速率提升模式RBM。
  26. 根据权利要求23所述的方法，其特征在于，还包括：
    所述控制设备向所述发送设备发送关于传输时机的信息，所述传输时机覆盖所述第一时间窗。
  27. 根据权利要求24所述的方法，其特征在于，还包括：
    所述控制设备接收来自所述发送设备的用于退出所述第一模式的第五请求；以及
    所述控制设备向所述发送设备发送针对所述第五请求的肯定响应。
  28. 根据权利要求23所述的方法，其特征在于，所述发送设备为物联网网关，所述接收设备为物联网终端设备，并且所述控制设备为电力线通信网络主节点。
  29. 根据权利要求23所述的方法，其特征在于，所述发送设备为物联网终端设备，所述接收设备为物联网网关，并且所述控制设备为电力线通信网络主节点。
  30. 一种用于物联网的电力线通信的通信装置，其特征在于，包括：
    处理器；以及
    耦合至所述处理器的电力线通信接口，
    其中，所述处理器被配置为：
    通过所述电力线通信接口接收来自接收设备的第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估；
    响应于所述第一请求，通过所述电力线通信接口向所述接收设备发送用于执行所述信道评估所需的探测信号；
    通过所述电力线通信接口从所述接收设备接收调制参数，所述调制参数是通过基于 所述探测信号执行所述信道评估而确定的；以及
    基于所述调制参数并且在所述第一时间窗上，通过所述电力线通信接口与所述接收设备进行数据传输。
  31. 根据权利要求30所述的通信装置，其特征在于，所述处理器被配置为通过以下操作来接收所述第一请求：
    通过所述电力线通信接口向所述接收设备发送进入第一模式的第一通知，在所述第一模式中所述通信装置和所述接收设备基于所述电力线通信周期中的至少一个时间窗来进行数据传输；以及
    通过所述电力线通信接口接收所述接收设备响应于所述第一通知而发送的所述第一请求。
  32. 根据权利要求31所述的通信装置，其特征在于，所述处理器还被配置为：
    通过所述电力线通信接口向所述接收设备发送退出所述第一模式的第二通知。
  33. 根据权利要求30所述的通信装置，其特征在于，所述通信装置为物联网子域节点，并且所述接收设备为物联网终端节点。
  34. 根据权利要求30所述的通信装置，其特征在于，所述通信装置为物联网终端节点，并且所述接收设备为物联网子域节点。
  35. 一种用于物联网的电力线通信的通信装置，其特征在于，包括：
    处理器；以及
    耦合至所述处理器的电力线通信接口，
    其中，所述处理器被配置为：
    通过所述电力线通信接口向发送设备发送第一请求，所述第一请求用于请求针对电力线通信周期中的第一时间窗执行信道评估；
    通过所述电力线通信接口接收所述发送设备响应于所述第一请求所发送的用于执行所述信道评估所需的探测信号；
    通过所述电力线通信接口向所述发送设备发送调制参数，所述调制参数是通过基于所述探测信号执行所述信道评估而确定的；以及
    通过所述电力线通信接口与所述发送设备在所述第一时间窗上基于所述调制参数进行数据传输。
  36. 根据权利要求35所述的通信装置，其特征在于，所述处理器被配置为通过以下操作来发送所述第一请求：
    通过所述电力线通信接口接收来自所述发送设备的进入第一模式的第一通知，在所述第一模式中所述发送设备和所述通信装置基于所述电力线通信周期中的至少一个时间窗来进行数据传输；以及
    响应于所述第一通知，通过电力线通信接口向所述发送设备发送所述第一请求。
  37. 根据权利要求36所述的通信装置，其特征在于，所述处理器还被配置为：
    通过所述电力线通信接口接收来自所述发送设备的退出所述第一模式的第二通知；以及
    响应于所述第二通知，释放所述调制参数。
  38. 根据权利要求35所述的通信装置，其特征在于，所述发送设备为物联网子域节点，并且所述通信装置为物联网终端节点。
  39. 根据权利要求35所述的通信装置，其特征在于，所述发送设备为物联网终端节点， 并且所述通信装置为物联网子域节点。
  40. 一种用于物联网的电力线通信的控制设备，其特征在于，包括：
    处理器；以及
    耦合至所述处理器的电力线通信接口，
    其中，所述处理器被配置为：
    通过所述电力线通信接口接收来自发送设备的用于探测信号的资源分配的第三请求，所述第三请求包括关于电力线通信周期中的第一时间窗的信息，所述第三请求是由所述发送设备响应于来自接收设备的第一请求而发送的，所述第一请求用于请求针对所述第一时间窗执行信道评估；以及
    通过所述电力线通信接口向所述发送设备发送关于所述资源分配的信息。
  41. 根据权利要求40所述的控制设备，其特征在于，在接收所述第三请求之前，所述处理器还被配置为：
    通过所述电力线通信接口接收来自所述发送设备的用于进入第一模式的第二请求，在所述第一模式中所述发送设备和所述接收设备基于所述电力线通信周期中的至少一个时间窗来进行数据传输；以及
    通过所述电力线通信接口向所述发送设备发送针对所述第二请求的肯定响应，以便所述发送设备向所述接收设备发送进入所述第一模式的第一通知。
  42. 根据权利要求41所述的控制设备，其特征在于，所述处理器还被配置为：
    通过所述电力线通信接口接收来自所述发送设备的用于退出所述第一模式的第五请求；以及
    通过所述电力线通信接口向所述发送设备发送针对所述第五请求的肯定响应。
  43. 根据权利要求40所述的控制设备，其特征在于，所述发送设备为物联网子域节点，所述接收设备为物联网终端节点，并且所述控制设备为电力线通信网络主节点。
  44. 根据权利要求40所述的控制设备，其特征在于，所述发送设备为物联网终端节点，所述接收设备为物联网子域节点，并且所述控制设备为电力线通信网络主节点。
  45. 一种用于物联网的电力线通信的系统，其特征在于，包括：
    根据权利要求30至34中任一项所述的通信装置；
    根据权利要求35至39中任一项所述的通信装置；以及
    根据权利要求40至44中任一项所述的控制设备。
  46. 一种计算机可读存储介质，其特征在于，包括机器可执行指令，所述机器可执行指令在由设备执行时促使所述设备执行如权利要求1-29中任一项所述的方法。
PCT/CN2021/079407 2021-03-05 2021-03-05 用于物联网的电力线通信的方法、装置和系统 WO2022183510A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP21928591.3A EP4300836A4 (en) 2021-03-05 2021-03-05 METHOD, APPARATUS AND SYSTEM FOR POWER LINE COMMUNICATION FOR INTERNET OF THINGS
PCT/CN2021/079407 WO2022183510A1 (zh) 2021-03-05 2021-03-05 用于物联网的电力线通信的方法、装置和系统
CN202180094881.6A CN116888897A (zh) 2021-03-05 2021-03-05 用于物联网的电力线通信的方法、装置和系统
US18/460,819 US20230412210A1 (en) 2021-03-05 2023-09-05 Method, apparatus, and system of power line communication for internet of things

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/079407 WO2022183510A1 (zh) 2021-03-05 2021-03-05 用于物联网的电力线通信的方法、装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/460,819 Continuation US20230412210A1 (en) 2021-03-05 2023-09-05 Method, apparatus, and system of power line communication for internet of things

Publications (1)

Publication Number Publication Date
WO2022183510A1 true WO2022183510A1 (zh) 2022-09-09

Family

ID=83154874

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/079407 WO2022183510A1 (zh) 2021-03-05 2021-03-05 用于物联网的电力线通信的方法、装置和系统

Country Status (4)

Country Link
US (1) US20230412210A1 (zh)
EP (1) EP4300836A4 (zh)
CN (1) CN116888897A (zh)
WO (1) WO2022183510A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110278008A (zh) * 2018-03-16 2019-09-24 华为技术有限公司 一种电力线通信方法及装置
CN110350948A (zh) * 2018-04-03 2019-10-18 华为技术有限公司 Plc系统的中继传输配置方法、中继传输方法及装置
US20190363754A1 (en) * 2015-03-16 2019-11-28 Texas Instruments Incorporated Optimized PHY Frame Structure for OFDM Based Narrowband PLC

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114175827B (zh) * 2019-08-29 2023-12-29 华为技术有限公司 通信方法、通信装置及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190363754A1 (en) * 2015-03-16 2019-11-28 Texas Instruments Incorporated Optimized PHY Frame Structure for OFDM Based Narrowband PLC
CN110278008A (zh) * 2018-03-16 2019-09-24 华为技术有限公司 一种电力线通信方法及装置
CN110350948A (zh) * 2018-04-03 2019-10-18 华为技术有限公司 Plc系统的中继传输配置方法、中继传输方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4300836A4 *

Also Published As

Publication number Publication date
CN116888897A (zh) 2023-10-13
US20230412210A1 (en) 2023-12-21
EP4300836A4 (en) 2024-04-24
EP4300836A1 (en) 2024-01-03

Similar Documents

Publication Publication Date Title
JP5955987B2 (ja) ＷｉＦｉネットワークの差別化関連付けサービス提供のためのシステム及び方法
CN107211323B (zh) 用于在无线lan多用户传输机会中传输数据的系统和方法
JP5876584B2 (ja) 光無線アクセスシステム
WO2017020777A1 (zh) 一种进行数据传输的方法和设备
JP5237442B2 (ja) ボイスオーバーインターネットプロトコル通信中に省電力モードを使用する方法およびシステム
CN103929823A (zh) 基于业务分类的电力无线专网信道接入控制方法
KR20110014654A (ko) 마스터―슬래이브 시스템에서의 매체 접근 제어 방법 및 시스템
TW200904070A (en) Removal of ambiguities in forming new piconet controller (PNC) when the current PNC is suddenly unavailable
WO2022042489A1 (zh) 资源指示、资源选择方法及装置
WO2019174011A1 (zh) 一种数据传输方法及装置、计算机存储介质
US20170359819A1 (en) Neighborhood Awareness Network and Multi-Channel Operation over OFDMA
WO2017185259A1 (zh) 光无线通信网络中传输信息的方法、协调器和终端节点
WO2018171374A1 (zh) 信道接入的指示方法和设备
WO2022183510A1 (zh) 用于物联网的电力线通信的方法、装置和系统
WO2015168908A1 (zh) 资源调度方法、装置及系统
WO2019051654A1 (zh) 一种逻辑信道的资源确定方法及装置、计算机存储介质
US10299313B2 (en) DOCSIS to support coordinated multi-point in 5G small cells
CN105873230A (zh) 一种电力线宽带载波广播通信同步方法
WO2022151912A1 (zh) 传输机会的使用权恢复方法及相关装置
WO2019136655A1 (zh) 数据复制传输功能的配置方法及相关产品
Liu et al. Throughput improvement for power line communication by adaptive MAC protocol
WO2014121679A1 (zh) 一种设备到设备通信数据传输方法、系统和用户设备
CN104661317B (zh) 基于双连接的上行调度请求传输方法、装置及系统
WO2017031645A1 (zh) 一种退避方法、传输消息方法及装置
WO2022193282A1 (zh) 资源选取方法、装置、设备及存储介质

Legal Events

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

Ref document number: 21928591

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180094881.6

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2021928591

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021928591

Country of ref document: EP

Effective date: 20230926

NENP Non-entry into the national phase

Ref country code: DE