WO2017036246A1 - 一种物联网通信方法、网络侧设备及物联网终端 - Google Patents

一种物联网通信方法、网络侧设备及物联网终端 Download PDF

Info

Publication number
WO2017036246A1
WO2017036246A1 PCT/CN2016/088231 CN2016088231W WO2017036246A1 WO 2017036246 A1 WO2017036246 A1 WO 2017036246A1 CN 2016088231 W CN2016088231 W CN 2016088231W WO 2017036246 A1 WO2017036246 A1 WO 2017036246A1
Authority
WO
WIPO (PCT)
Prior art keywords
iot
downlink
uplink
frame
network side
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2016/088231
Other languages
English (en)
French (fr)
Inventor
刘晟
罗毅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to KR1020187008343A priority Critical patent/KR102175875B1/ko
Priority to EP16840675.9A priority patent/EP3337096B1/en
Priority to RU2018111215A priority patent/RU2693293C1/ru
Priority to JP2018511197A priority patent/JP6556336B2/ja
Publication of WO2017036246A1 publication Critical patent/WO2017036246A1/zh
Priority to US15/909,771 priority patent/US10616026B2/en
Anticipated expiration legal-status Critical
Priority to US16/839,520 priority patent/US11388035B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/04—Scheduled access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2647—Arrangements specific to the receiver only
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
    • H04L1/0003—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate by switching between different modulation schemes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00—Baseband systems
    • H04L25/02—Details ; arrangements for supplying electrical power along data transmission lines
    • H04L25/0202—Channel estimation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/0008—Modulated-carrier systems arrangements for allowing a transmitter or receiver to use more than one type of modulation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/2603—Signal structure ensuring backward compatibility with legacy system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2647—Arrangements specific to the receiver only
    • H04L27/2655—Synchronisation arrangements
    • H04L27/2657—Carrier synchronisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00—Arrangements for synchronising receiver with transmitter
    • H04L7/04—Speed or phase control by synchronisation signals
    • H04L7/06—Speed or phase control by synchronisation signals the synchronisation signals differing from the information signals in amplitude, polarity or frequency or length
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/2605—Symbol extensions, e.g. Zero Tail, Unique Word [UW]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to an Internet of Things communication method, a network side device, and an Internet of Things terminal.
  • IoT Internet of Thing
  • IoT In IoT, in order to obtain information about the physical world or to control objects in the physical world, a large number of IoT terminals need to be deployed.
  • the IoT terminals are various devices with certain capabilities of sensing, computing, execution, and communication, and thus are implemented through a network. Information transmission, coordination and processing.
  • the channel bandwidth used for IoT terminal communication is usually only 1 to 2 MHz, which is much smaller than the channel bandwidth used by wireless local area network (WLAN) devices such as stations (STAs).
  • WLAN wireless local area network
  • the WLAN standard consists of gradual evolution of 802.11a, 802.11n, 802.11ac, etc.
  • IEEE 802.11 standards organization has launched a new generation WLAN standard called High Efficiency WLAN (HEW), namely 802.11ax. Standardization work, the WLAN device supporting 802.11ax uses a channel bandwidth of at least 20 MHz.
  • HEW High Efficiency WLAN
  • an IoT terminal cannot directly receive and transmit signals in a WLAN, that is, IoT communication is not subject to an access point (AP).
  • AP access point
  • the embodiment of the invention provides an IoT communication method, a network side device and an IoT terminal, so that the IoT terminal can accept the scheduling of the network side device during the IoT communication process, and reduce the risk of conflict in the IoT communication transmission process.
  • an Internet of Things IoT communication method including:
  • the network side device determines a terminal device that performs downlink data transmission, where the terminal device includes an IoT terminal;
  • the network side device sends a downlink data frame
  • the downlink data frame includes a traditional preamble, a high efficiency wireless local area network HEW preamble and a data field;
  • the subcarrier resource corresponding to the data field in the frequency domain includes at least one resource unit RU;
  • the RU is configured to send a downlink IoT frame to the IoT terminal, where the downlink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the downlink IoT frame, where the IoT data is used.
  • the field is used to transmit downlink data between the network side device and the IoT terminal.
  • the terminal device further includes a station STA;
  • the subcarrier resource corresponding to the data field in the frequency domain further includes at least one other RU different from the RU;
  • the at least one other RU is configured to transmit downlink data between the network side device and the STA.
  • the network side device is configured to send a downlink IoT frame to the IoT terminal by using the RU:
  • the carrier transmits a downlink IoT frame to the IoT terminal.
  • the data field included in the downlink data frame is specifically generated as follows:
  • the network side device performs code modulation on downlink data between the network side device and the STA, obtains a wireless local area network WLAN downlink modulation symbol, and maps the WLAN downlink modulation symbol to the at least one other RU.
  • code modulation on downlink data between the network side device and the STA, obtains a wireless local area network WLAN downlink modulation symbol, and maps the WLAN downlink modulation symbol to the at least one other RU.
  • the network side device performs inverse Fourier transform (IFFT) on the frequency domain signal including the at least one RU corresponding subcarrier and the at least one other RU corresponding subcarrier, and adds a cyclic prefix to generate a downlink baseband for mixing the IoT and the WLAN. signal.
  • IFFT inverse Fourier transform
  • the network side device is configured to send a downlink IoT frame to the IoT terminal by using the RU:
  • the data field included in the downlink data frame is specifically generated as follows:
  • the network side device performs code modulation on downlink data between the network side device and the STA, obtains a wireless local area network WLAN downlink modulation symbol, and maps the WLAN downlink modulation symbol to the at least one other RU.
  • code modulation on downlink data between the network side device and the STA, obtains a wireless local area network WLAN downlink modulation symbol, and maps the WLAN downlink modulation symbol to the at least one other RU.
  • the network side device performs inverse Fourier transform IFFT on the frequency domain signal including the at least one other RU corresponding subcarrier, and adds a cyclic prefix CP to generate a WLAN downlink baseband signal;
  • the network side device performs coding and modulation on downlink data between the network side device and the IoT terminal, and adds a CP to generate an IoT downlink single carrier symbol;
  • the network side device performs waveform shaping filtering on the IoT downlink single carrier symbol to obtain an IoT downlink baseband signal
  • the network side device performs frequency conversion on the IoT downlink baseband signal to obtain an IoT downlink bandpass signal, where a center frequency of the IoT downlink bandpass signal is fr , where fr is used for transmitting a downlink IoT frame.
  • the network side device adds the IoT downlink bandpass signal and the WLAN downlink baseband signal to obtain a downlink baseband signal that is mixed and transmitted by the IoT and the WLAN.
  • the IoT downlink single carrier symbol and the OFDM symbol of the WLAN downlink baseband signal adopt a CP of the same length, and the IoT downlink single carrier symbol The length is the same as the length of the OFDM symbol of the WLAN downlink baseband signal.
  • T 1 is the period of each modulation symbol
  • T 0 is the length of the OFDM symbol of the WLAN downlink baseband signal.
  • the RU for sending a downlink IoT frame includes at least one basic RU, the method further includes:
  • the network side device sends channel indication information on the basic RU
  • the channel indication information is used to indicate that the IoT terminal is switched by the basic RU to other RUs for transmitting downlink IoT frames except the basic RU.
  • the physical layer control information of the downlink IoT frame of the IoT preamble transmission includes one or any combination of the following sequences:
  • the IoT data field includes at least one subframe
  • the IoT data field includes downlink data of at least two IoT terminals
  • the downlink data of each IoT terminal occupies at least one subframe; or
  • the downlink data of each IoT terminal occupies at least one time slot of at least one subframe
  • the downlink data of each IoT terminal occupies at least one subframe and at least one slot of at least one subframe.
  • an Internet of Things IoT communication method including:
  • the IoT terminal acquires a downlink IoT frame from the downlink received signal, where the downlink received signal includes a downlink data frame sent by the network side device;
  • the downlink data frame includes a traditional preamble, a high efficiency WLAN HEW preamble and a data field, where the corresponding subcarrier resources in the frequency domain include at least one resource unit RU, and the at least one RU is used to send a downlink IoT frame.
  • the downlink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the downlink IoT frame, and the IoT data field is used to transmit the network side device and the IoT terminal. Downstream data between;
  • the IoT terminal processes the downlink IoT frame to obtain downlink data between the network side device and the IoT terminal.
  • a bandwidth of a receiving channel of the IoT terminal does not exceed a bandwidth of the RU
  • the receiving channel of the IoT terminal adopts a carrier frequency of f 0 +f r , where f 0 is a carrier frequency of the downlink IoT frame, and f r is a frequency difference of a center frequency point of the RU with respect to a zero frequency.
  • the IoT terminal processes the downlink IoT frame to obtain a relationship between the network side device and the IoT terminal.
  • Downstream data including:
  • each orthogonal frequency division multiplexing OFDM symbol of the downlink IoT frame removing a cyclic prefix CP, and performing upsampling and Fourier transform FFT to obtain IoT modulation mapped to subcarriers included in the RU Signal
  • the IoT terminal demodulates and decodes the IoT modulated signal to obtain downlink data between the network side device and the IoT terminal.
  • the IoT terminal processes the downlink IoT frame to obtain a relationship between the network side device and the IoT terminal.
  • Downstream data including:
  • the IoT terminal removes the cyclic prefix CP from each single carrier symbol of the downlink IoT frame, and performs frequency domain equalization to obtain an IoT modulated signal mapped to a frequency band corresponding to the RU;
  • the IoT terminal demodulates and decodes the IoT modulated signal to obtain downlink data between the network side device and the IoT terminal.
  • the physical layer control information of the downlink IoT frame of the IoT preamble transmission includes one or any combination of the following sequences:
  • an Internet of Things IoT communication method including:
  • the IoT terminal receives an uplink transmission scheduling request sent by the network side device;
  • the uplink transmission scheduling request is used to schedule the IoT terminal to send an uplink IoT frame
  • the uplink IoT frame is located in a data field of the uplink data frame, and the data field of the uplink data frame includes at least one resource unit RU corresponding to the subcarrier resource in the frequency domain, and the at least one RU is used to send the uplink IoT frame. ;
  • the uplink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the uplink IoT frame, where the IoT data field is used to transmit the network side device and the IoT terminal.
  • Upstream data is used to transmit physical layer control information of the uplink IoT frame.
  • the IoT terminal sends the uplink IoT frame in the following manner:
  • the IoT terminal is configured to send the uplink IoT frame by using the RU, including:
  • the IoT terminal performs inverse Fourier transform IFFT and downsampling on the frequency domain signal including the RU corresponding subcarrier, and adds a cyclic prefix to obtain a first IoT uplink baseband signal;
  • the carrier frequency of the uplink transmission channel is f 0 +f r , where f 0 is the carrier frequency of the channel of the uplink data frame in which the RU is transmitted, and f r is the center frequency of the second RU relative to the zero frequency Frequency difference.
  • the IoT terminal specifically sends the uplink IoT frame in the following manner:
  • the IoT terminal sends the uplink IoT frame in a single carrier manner, as follows:
  • the IoT terminal performs coding and modulation on uplink data between the network side device and the IoT terminal, and adds a cyclic prefix CP to generate an IoT uplink single carrier symbol;
  • the IoT terminal performs waveform shaping filtering on the IoT uplink single carrier symbol to obtain a second IoT uplink baseband signal;
  • the IoT terminal sends the second IoT uplink baseband signal through an uplink transmission channel
  • the carrier frequency of the uplink transmission channel is f 0 +f r , where f 0 is the carrier frequency of the channel of the uplink data frame in which the RU is transmitted, and f r is the frequency difference of the center frequency point of the RU relative to the zero frequency .
  • the IoT uplink single carrier symbol and the OFDM symbol of the WLAN uplink baseband signal sent by the STA adopt a CP of the same length
  • the IoT uplink The single carrier symbol is the same length as the OFDM symbol of the WLAN uplink baseband signal transmitted by the STA.
  • T 1 is a period of each modulation symbol
  • T 0 is a length of an OFDM symbol of the WLAN uplink baseband signal transmitted by the STA.
  • the physical layer control information of the uplink IoT frame of the IoT preamble transmission includes one or any combination of the following sequences:
  • the uplink IoT frame includes an uplink IoT subframe that is sent by at least two IoT terminals;
  • the uplink IoT subframe sent by each IoT terminal includes an IoT preamble and an IoT data field.
  • the uplink transmission scheduling request is sent by using a downlink data frame sent by the network side device;
  • the downlink data frame includes a traditional preamble, a high efficiency wireless local area network HEW preamble and a data field, and the downlink data frame includes a data field, and the corresponding subcarrier resource in the frequency domain includes at least one used to send the uplink transmission scheduling request. RU.
  • an Internet of Things IoT communication method including:
  • the network side device sends an uplink transmission scheduling request to the IoT terminal, where the uplink transmission scheduling request is used to schedule the IoT terminal to send an uplink IoT frame;
  • the uplink IoT frame is located in a data field of the uplink data frame, and the data field of the uplink data frame includes at least one resource unit RU corresponding to the subcarrier resource in the frequency domain, where the at least one RU is used to send the uplink.
  • IoT frame ;
  • the uplink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the uplink IoT frame, where the IoT data field is used to transmit the network side device and the IoT terminal.
  • Upstream data is used to transmit physical layer control information of the uplink IoT frame.
  • the network side device receives an uplink IoT frame that is sent by the IoT terminal according to the uplink transmission scheduling request, and includes:
  • the network side device acquires an uplink receiving signal, where the uplink receiving signal includes an uplink IoT frame sent by the IoT terminal;
  • the network side device removes the cyclic prefix CP from the uplink received signal, and performs a Fourier transform FFT to obtain a frequency domain received signal.
  • the network side device performs frequency domain equalization, inverse Fourier transform (IFFT), and demodulation and decoding processing on the IoT frequency domain signal to obtain uplink data between the network side device and the IoT terminal.
  • IFFT inverse Fourier transform
  • the network side device sends an uplink transmission scheduling request to the IoT terminal, including:
  • the downlink data frame includes a traditional preamble, a high efficiency wireless local area network HEW preamble and a data field, and the downlink data frame includes a data field, and the corresponding subcarrier resource in the frequency domain includes at least one used to send the uplink transmission scheduling request. RU.
  • the physical layer control information of the uplink IoT frame that is transmitted by the IoT preamble includes one or any combination of the following sequences:
  • a network side device includes:
  • a determining unit configured to determine a terminal device that performs downlink data transmission, where the terminal device includes an IoT terminal;
  • a sending unit configured to send a downlink data frame
  • the downlink data frame includes a traditional preamble, a high efficiency wireless local area network HEW preamble and a data field;
  • the subcarrier resource corresponding to the data field in the frequency domain includes at least one resource unit RU;
  • the RU is configured to send a downlink IoT frame to the IoT terminal, where the downlink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the downlink IoT frame, where the IoT data is used.
  • the field is used to transmit downlink data between the network side device and the IoT terminal.
  • the terminal device further includes a station STA;
  • the subcarrier resource corresponding to the data field in the frequency domain further includes at least one other RU different from the RU;
  • the at least one other RU is configured to transmit downlink data between the network side device and the STA.
  • the sending unit is configured to send a downlink IoT frame to the IoT terminal by using the RU:
  • a downlink IoT frame is transmitted to the IoT terminal by using other subcarriers included in the RU other than the protection subcarrier and the DC subcarrier.
  • the sending unit Specifically, the data field included in the downlink data frame is generated in the following manner:
  • the sending unit is configured to send, by using the RU, a downlink IoT frame to the IoT terminal by using the RU:
  • the sending unit specifically generates the data field included in the downlink data frame by using the following manner:
  • the IoT downlink single carrier symbol and the OFDM symbol of the WLAN downlink baseband signal adopt a CP of the same length, and the IoT downlink single carrier symbol The length is the same as the length of the OFDM symbol of the WLAN downlink baseband signal.
  • T 1 is the period of each modulation symbol
  • T 0 is the length of the OFDM symbol of the WLAN downlink baseband signal.
  • the RU for transmitting a downlink IoT frame includes at least one basic RU;
  • the sending unit is further configured to send channel indication information on the basic RU;
  • the channel indication information is used to indicate that the IoT terminal is switched by the basic RU to other RUs for transmitting downlink IoT frames except the basic RU.
  • the physical layer control information of the downlink IoT frame of the IoT preamble transmission includes one or any combination of the following sequences:
  • the IoT data field includes at least one subframe
  • the IoT data field includes downlink data of at least two IoT terminals
  • the downlink data of each IoT terminal occupies at least one subframe; or
  • the downlink data of each IoT terminal occupies at least one time slot of at least one subframe
  • the downlink data of each IoT terminal occupies at least one subframe and at least one slot of at least one subframe.
  • an IoT terminal including:
  • An acquiring unit configured to obtain a downlink IoT frame from a downlink receiving signal, where the downlink receiving signal includes a downlink data frame sent by a network side device;
  • the downlink data frame includes a traditional preamble, a high efficiency WLAN HEW preamble and a data field, where the corresponding subcarrier resources in the frequency domain include at least one resource unit RU, and the at least one RU is used to send a downlink IoT frame.
  • the downlink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the downlink IoT frame, and the IoT data field is used to transmit the network side device and the IoT terminal. Downstream data between;
  • a processing unit configured to process the downlink IoT frame acquired by the acquiring unit, to obtain downlink data between the network side device and the IoT terminal.
  • a bandwidth of a receiving channel of the IoT terminal does not exceed a bandwidth of the RU
  • the receiving channel of the IoT terminal adopts a carrier frequency of f 0 +f r , where f 0 is a carrier frequency of the downlink IoT frame, and f r is a frequency difference of a center frequency point of the RU with respect to a zero frequency.
  • the processing unit is configured to process the downlink IoT frame in the following manner, to obtain the network side device and Downlink data between the IoT terminals:
  • Demodulating and decoding the IoT modulated signal to obtain downlink data between the network side device and the IoT terminal.
  • the processing unit is configured to process the downlink IoT frame in the following manner to obtain downlink data between the network side device and the IoT terminal:
  • Demodulating and decoding the IoT modulated signal to obtain downlink data between the network side device and the IoT terminal.
  • the physical layer control information of the downlink IoT frame that is transmitted by the IoT preamble includes one or any combination of the following sequences:
  • an IoT terminal including:
  • a receiving unit configured to receive an uplink transmission scheduling request sent by the network side device, where the uplink transmission scheduling request is used to schedule the IoT terminal to send an uplink IoT frame, where the uplink IoT frame is located in a data field of an uplink data frame, where the uplink is
  • the data field of the data frame corresponding to the subcarrier resource in the frequency domain includes at least one resource unit RU, and the at least one RU is used to send the uplink IoT frame;
  • a sending unit configured to send the uplink IoT frame according to an uplink transmission scheduling request received by the receiving unit
  • the uplink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the uplink IoT frame, where the IoT data field is used to transmit the network side device and the IoT terminal.
  • Upstream data is used to transmit physical layer control information of the uplink IoT frame.
  • the sending unit sends the uplink IoT frame in the following manner:
  • the sending unit is configured to send the uplink IoT frame by using the RU:
  • the carrier frequency of the uplink transmission channel is f 0 +f r , where f 0 is the carrier frequency of the channel of the uplink data frame in which the RU is transmitted, and f r is the center frequency of the second RU relative to the zero frequency Frequency difference.
  • the sending unit sends the uplink IoT frame in the following manner:
  • the sending unit specifically sends the uplink IoT frame in a single carrier manner as follows:
  • the carrier frequency of the uplink transmission channel is f 0 +f r , where f 0 is the carrier frequency of the channel of the uplink data frame in which the RU is transmitted, and f r is the frequency difference of the center frequency point of the RU relative to the zero frequency .
  • the IoT uplink single carrier symbol and the OFDM symbol of the WLAN uplink baseband signal sent by the STA adopt a CP of the same length
  • the IoT uplink The single carrier symbol is the same length as the OFDM symbol of the WLAN uplink baseband signal transmitted by the STA.
  • T 1 is a period of each modulation symbol
  • T 0 is a length of an OFDM symbol of the WLAN uplink baseband signal transmitted by the STA.
  • the physical layer control information of the uplink IoT frame that is transmitted by the IoT preamble includes one or any combination of the following sequences:
  • the uplink IoT frame includes an uplink IoT subframe that is sent by at least two IoT terminals;
  • the uplink IoT subframe sent by each IoT terminal includes an IoT preamble and an IoT data field.
  • the uplink transmission scheduling request is sent by using a downlink data frame sent by the network side device;
  • the downlink data frame includes a traditional preamble, a high efficiency wireless local area network HEW preamble and a data field, and the downlink data frame includes a data field, and the corresponding subcarrier resource in the frequency domain includes at least one used to send the uplink transmission scheduling request. RU.
  • the eighth aspect provides a network side device, including:
  • a sending unit configured to send an uplink transmission scheduling request to the IoT terminal, where the uplink transmission scheduling request is used to schedule the IoT terminal to send an uplink IoT frame;
  • An acquiring unit configured to acquire an uplink IoT frame that is sent by the IoT terminal according to an uplink transmission scheduling request sent by the sending unit;
  • the uplink IoT frame is located in a data field of the uplink data frame, and the data field of the uplink data frame includes at least one resource unit RU corresponding to the subcarrier resource in the frequency domain, and the at least one The RUs are used to send the uplink IoT frame;
  • the uplink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the uplink IoT frame, where the IoT data field is used to transmit the network side device and the IoT terminal.
  • Upstream data is used to transmit physical layer control information of the uplink IoT frame.
  • the acquiring unit is configured to obtain, by using the following manner, an uplink IoT frame that is sent by the IoT terminal according to the uplink transmission scheduling request, and includes:
  • the uplink received signal includes an uplink IoT frame sent by the IoT terminal;
  • the sending unit sends an uplink transmission scheduling request to the IoT terminal in the following manner:
  • the downlink data frame includes a traditional preamble, a high efficiency wireless local area network HEW preamble and a data field, and the downlink data frame includes a data field, and the corresponding subcarrier resource in the frequency domain includes at least one used to send the uplink transmission scheduling request. RU.
  • the physical layer control information of the uplink IoT frame that is transmitted by the IoT preamble includes one or any combination of the following sequences:
  • the sub-carrier resource corresponding to the data field in the frequency domain includes an RU for transmitting downlink data or uplink data between the network side device and the IoT terminal, and is used for transmitting downlink data between the network side device and the STA or The RU of the uplink data, so that the data frame in the WLAN network can be shared or received between the IoT terminal and the STA, so that the network side device of the WLAN can schedule the IoT terminal, thereby reducing the risk of conflict in the IoT communication process.
  • FIG. 1 is a schematic diagram of a WLAN network architecture
  • 2 is a packet structure of an 802.11ax physical layer data frame
  • FIG. 3 is a schematic diagram of partitioning of subcarrier resources corresponding to a data field of an 802.11ax data frame in a frequency domain;
  • FIG. 4 is a schematic structural diagram of a data frame according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of implementing a first IoT communication method according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a downlink data frame according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of determining a subcarrier for transmitting IoT data according to an embodiment of the present invention.
  • FIG. 8 is a method for generating a data field based on an OFDM method according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a process for acquiring downlink data by an OFDM-based IoT terminal according to an embodiment of the present disclosure.
  • FIG. 10 is a method for generating a data field based on a single carrier manner according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of a process for acquiring downlink data by an IoT terminal according to a single carrier manner according to an embodiment of the present disclosure
  • FIG. 12 is a schematic structural diagram of time division multiplexing of a downlink IoT frame according to an embodiment of the present invention.
  • FIG. 13 is a flowchart of implementing a second IoT communication method according to an embodiment of the present invention.
  • FIG. 14 is a flowchart of implementing a third IoT communication method according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of an uplink data frame according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic diagram of another structure of an uplink data frame according to an embodiment of the present invention.
  • FIG. 17 is a schematic structural diagram of a physical layer frame of uplink data transmission according to an embodiment of the present disclosure.
  • FIG. 18 is a schematic structural diagram of another physical layer frame of uplink data transmission according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic diagram of a process for transmitting an uplink IoT frame based on an OFDM method according to an embodiment of the present disclosure
  • FIG. 20 is a schematic diagram of a process for transmitting an uplink IoT frame based on a single carrier manner according to an embodiment of the present disclosure
  • FIG. 21 is a schematic diagram showing the same length of an uplink single carrier symbol and an OFDM symbol of 802.11ax according to an embodiment of the present invention.
  • FIG. 22 is a schematic structural diagram of time division multiplexing of an uplink IoT frame according to an embodiment of the present invention.
  • FIG. 23 is a flowchart of implementing a fourth IoT communication method according to an embodiment of the present invention.
  • FIG. 24 is a schematic diagram of a process of receiving an uplink data frame by a network side device according to an embodiment of the present disclosure
  • FIG. 25 is a schematic diagram of a process of receiving uplink data by a network side device according to an embodiment of the present disclosure
  • FIG. 26 is a schematic structural diagram of an OFDM-based IoT frame according to an embodiment of the present disclosure.
  • FIG. 27 is a schematic structural diagram of a single carrier-based IoT frame according to an embodiment of the present disclosure.
  • FIG. 28 is a schematic structural diagram of a first network side device according to an embodiment of the present disclosure.
  • FIG. 29 is another schematic structural diagram of a first network side device according to an embodiment of the present disclosure.
  • FIG. 30 is a schematic structural diagram of a first IoT terminal according to an embodiment of the present disclosure.
  • FIG. 31 is another schematic structural diagram of a first IoT terminal according to an embodiment of the present disclosure.
  • FIG. 32 is a schematic structural diagram of a second IoT terminal according to an embodiment of the present disclosure.
  • FIG. 33 is another schematic structural diagram of a second IoT terminal according to an embodiment of the present invention.
  • FIG. 34 is a schematic structural diagram of a second network side device according to an embodiment of the present disclosure.
  • FIG. 35 is a schematic diagram of another structure of a second network side device according to an embodiment of the present disclosure.
  • FIG. 36 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • the IoT communication method provided by the embodiment of the present invention can be applied to the wireless local area network shown in FIG. (Wireless local Access Network, WLAN) in the network architecture.
  • a WLAN network device such as an access point (AP) in FIG. 1 is responsible for two-way communication with a WLAN device such as a station (STA), that is, the AP can send downlink data to the STA, as shown in FIG. STA1 and STA2 send downlink data; the AP can also receive uplink data from the STA. As shown in FIG. 1, the AP can receive uplink data sent by STA3.
  • the WLAN supports the 802.11a, 802.11n, 802.11ac, and 802.11ax standards proposed by the IEEE 802.11 standards organization.
  • the 802.11ax which is referred to in the following embodiments of the present invention, refers to a WLAN.
  • 802.11ax supports Orthogonal Frequency-Division Multiplexing (OFDM) technology. OFDMA divides the wideband channel into multiple orthogonal subcarriers in the frequency domain and allocates different subcarriers to different users. Achieve orthogonal multiplexing transmission of multiple users.
  • OFDM Orthogonal Frequency-Division Multiplexing
  • the IoT terminal and the STA can frequency-multiplex the sub-carrier resources corresponding to the 802.11ax physical layer data frame in the frequency domain to implement the IoT support in the 802.11ax.
  • FIG 2 shows the packet structure of the 802.11ax physical layer data frame.
  • the 802.11ax physical layer data frame includes a legacy preamble, an HEW preamble, and a data segment.
  • the first part of the 802.11ax physical layer data frame is the traditional preamble, and finally the data field.
  • the traditional preamble and data field are the 802.11ax protocol-specific preamble, that is, the HEW preamble.
  • the traditional preamble includes a field consisting of a Legacy Short Training Field (L-STF), a Legacy Long Training Field (L-LTF), and a Legacy Signal Field (L-SIG).
  • L-STF Legacy Short Training Field
  • L-LTF Legacy Long Training Field
  • L-SIG Legacy Signal Field
  • the HEW preamble includes a Repeated Legacy Signal Field (RL-SIG), a High Efficiency Signal-A field (HE-SIG-A), and a High Efficiency Signaling B field (High).
  • Efficiency Signal-B field, HE-SIG-B High Efficiency Short Training Field (HE-STF) and High Efficiency Long Training Field (HE-LTF).
  • the data field is used for data transmission; the fields such as L-SIG, RL-SIG, HE-SIG-A, and HE-SIG-B are used to transmit different types of physical layer signaling; L-STF, L-LTF, Fields such as HE-STF and HE-LTF are mainly used for timing and frequency synchronization and automatic Gain control and channel estimation, etc.
  • the data layer included in the physical layer data frame of 802.11ax is divided into at least one resource unit (RU) in the frequency domain corresponding subcarrier resources.
  • RU resource unit
  • a 20 MHz channel corresponds to 256 subcarrier resources in the frequency domain.
  • 256 subcarrier resources are numbered -128, -127, ..., 126, 127, respectively, where the intermediate position is located.
  • the carriers, that is, the subcarriers numbered -1, 0, and 1, are called DC subcarriers. Since these three subcarriers are susceptible to the DC offset of the transceiver system, they are not used for data transmission.
  • the subcarriers located at two edge positions that is, 6 subcarriers numbered from -128 to -123 on the left and 5 subcarriers numbered from 123 to 127 on the right are called guard subcarriers.
  • the guard subcarrier is used to reduce the out-of-band leakage of the transmitted signal, avoiding interference to adjacent channels, and therefore is not used for data transmission.
  • the subcarriers available for data transmission in the 20 MHz channel are subcarriers numbered -122 to -2, and subcarriers numbered 2 to 122, for a total of 242 subcarriers.
  • the 242 subcarriers that can be used for data transmission are further divided into RUs containing different numbers of subcarriers, for example, RUs including 26, 52, 106, and 242 subcarriers. Therefore, up to 9 of the 20 MHz channels can include 26 sub-carriers.
  • the RU of the carrier four RUs of 52 subcarriers, two RUs of 106 subcarriers, and one RU of 242 subcarriers, as shown in FIG.
  • RU of subcarriers Up to 37 RUs with 26 subcarriers, 16 RUs with 52 subcarriers, 8 RUs with 106 subcarriers, 4 RUs with 242 subcarriers, and 2 RUs with 484 subcarriers in an 80 MHz channel And 1 RU with 996 subcarriers.
  • the IoT terminal and the STA frequency division multiplexing the subcarrier resources corresponding to the data field of the 802.11ax physical layer data frame in the frequency domain.
  • the data field of the 802.11ax physical layer data frame corresponds to the IoT-RU and the non-IoT-RU, and the IoT-RU is used to transmit the network side device and the IoT terminal.
  • Downlink data or uplink data; the non-IoT-RU is used to transmit downlink data or uplink data between the network side device and the STA.
  • the physical layer data frame of 802.11ax includes a traditional preamble and The HEW preamble is not frequency division multiplexed with the IoT communication, that is, the legacy preamble and the HEW preamble are still used for communication between the network side device and the STA.
  • FIG. 4 is a schematic structural diagram of a data frame for performing data transmission by using an IoT terminal and a STA to multiplex a subcarrier resource corresponding to an 802.11ax physical layer data frame data field in a frequency domain according to an embodiment of the present invention.
  • the IoT-RU is used to transmit downlink data or uplink data between an AP and the IoT terminal; and the non-IoT-RU is used to transmit downlink data or uplink data between an AP and the STA.
  • the embodiment of the present invention uses the data frame structure described in FIG. 4 to perform IoT communication, which can support communication between the IoT terminal and the network side device in the 802.11ax, that is, the scheduling and coordination of the IoT communication by the network side device can be realized, thereby avoiding the IoT.
  • the following describes how to implement communication between the IoT terminal and the network side device in 802.11ax.
  • FIG. 5 is a flowchart of a method for implementing a first IoT communication method according to an embodiment of the present invention.
  • the execution body of the method shown in FIG. 5 is a network side device, and the network side device may be, for example, an AP. .
  • a flowchart for implementing a first IoT communication method according to an embodiment of the present invention includes:
  • the network side device determines a terminal device that performs downlink data transmission.
  • the network side device determines that the STA supporting the 802.11ax is the terminal device that performs the downlink data transmission, and the network side device may determine the IoT terminal terminal to perform the downlink data transmission in the embodiment of the present invention.
  • the terminal device that is, the terminal device that performs the downlink data transmission determined by the network side device, may be an 802.11ax-enabled STA, or may be an IoT terminal.
  • the terminal device for performing downlink data transmission determined in the embodiment of the present invention may include supporting 802.11.
  • the STA and IoT terminals of ax may also include only IoT terminals.
  • the downlink data transmission in the embodiment of the present invention may refer to a communication process in which downlink data is sent by the network side device and downlink data is received by the terminal device.
  • S102 The network side device sends a downlink data frame.
  • the network side device in the embodiment of the present invention determines the terminal device that performs downlink data transmission. After that, a downlink data frame can be transmitted.
  • FIG. 6 is a schematic structural diagram of a downlink data frame according to an embodiment of the present invention.
  • the downlink data frame shown in FIG. 6 includes a legacy preamble, an HEW preamble, and a data field.
  • the conventional preamble shown in FIG. 6 includes fields such as L-STF, L-LTF, and L-SIG as shown in FIG. 2.
  • the HEW preamble shown in FIG. 6 includes the RL-SIG as shown in FIG.
  • Fields such as HE-SIG-A, HE-SIG-B, HE-STF, and HE-LTF, that is, the conventional preamble and HEW preamble included in the downlink data frame and the conventional preamble and HEW preamble in 802.11ax are involved in the embodiments of the present invention.
  • the functions and structures are the same, and are used for communication between the network side device and the STA.
  • the data field included in the downlink data frame shown in FIG. 6 is different from the data field in the data frame structure in the 802.11ax shown in FIG. 2, and the foregoing is involved in the downlink data frame shown in FIG. 6 in the embodiment of the present invention.
  • the subcarrier resource corresponding to the data field in the frequency domain includes at least one RU for transmitting a downlink IoT frame to the IoT terminal.
  • the downlink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the downlink IoT frame, where the IoT data field is used to transmit the network side device and Downlink data between the IoT terminals.
  • the subcarrier resource corresponding to the data field in the frequency domain further includes at least one different from the RU for transmitting the IoT downlink data frame.
  • the at least one other RU is used to transmit downlink data between the network side device and the STA.
  • the RU for transmitting the IoT downlink data frame is referred to as a first RU, and the RU for transmitting downlink data between the network side device and the STA is referred to as a first.
  • Two RU In the embodiment of the present invention, the first RU, which is equivalent to the IoT-RU in FIG. 4, is used to send a downlink IoT frame to the IoT terminal.
  • the second RU is equivalent to the non-IoT-RU in FIG. 4, and is used to send downlink data between the network side device and the STA to the STA.
  • the downlink IoT frame sent by the first RU shown in FIG. 6 of the embodiment of the present invention includes an IoT preamble and an IoT data field, where the IoT preamble includes physical layer control information for transmitting the downlink IoT frame, and the IoT data field And configured to transmit downlink data between the network side device and the IoT terminal.
  • the physical layer control information of the downlink IoT frame transmitted by the IoT preamble includes one or any combination of the following sequences:
  • the downlink IoT frame is sent in the first RU of the data field, so that the IoT terminal can parse the preamble part in the downlink IoT frame, and obtain information about timing synchronization, frequency synchronization, and channel estimation of the IoT terminal, without
  • the preamble of 802.11ax is analyzed.
  • the IoT terminal does not need to support large bandwidths such as 20/40/80MHz, and effectively supports bandwidth-limited narrow-band IoT terminals, ensuring low complexity and low power consumption of IoT devices.
  • the network side device determines that the terminal device that performs data transmission includes an IoT terminal, that is, the network side device can send downlink data to the IoT terminal, and implements scheduling and coordination of the IoT terminal by the network side device.
  • the traditional preamble and the HEW preamble in the downlink data frame sent by the network side have the same structure as the preamble in the 802.11ax, so that the STA can receive the downlink data frame sent by the network side in the embodiment of the present invention.
  • the traditional preamble and the HEW preamble accept the scheduling and coordination of the STAs by the network side devices, so they do not compete with the IoT terminals for channels, and avoid conflicts between the WLAN devices such as STAs and the IoT terminals.
  • the data field in the downlink data frame sent by the network side is frequency-division multiplexed by the IoT terminal and the STA, so that the STA and the IoT terminal can share the WLAN channel resources during downlink transmission, and do not interfere with each other.
  • the implementation process of the downlink IoT frame sent by the first RU to the IoT terminal by the first RU is specifically described below.
  • the first implementation manner is: the network side device sends a downlink IoT frame to the IoT terminal by using the first RU according to an OFDM mode.
  • the IoT device cannot directly receive the downlink receiving signal of 20MHz and other bandwidths in 802.11ax, but filters out the 802.11ax signal in the first RU band of the downlink receiving signal through the analog filter of the receiving channel, that is, only receives the The IoT signal in the first RU band. Therefore, in the embodiment of the present invention, to avoid interference of the 802.11ax signal outside the first RU band to the IoT signal in the first RU band, a set number of subcarriers at two edge positions of the first RU are used as protection subcarriers, and a set number of subcarriers at the intermediate position of the first RU are used as DC subcarriers, and the protection subcarriers and the DC subcarriers are used.
  • the data transmission is not used for the downlink IoT frame, and the downlink IoT frame is sent to the IoT terminal by using other subcarriers included in the first RU except the protection subcarrier and the DC subcarrier.
  • the first RU when an RU including 26 subcarriers is used as the first RU, only 16 of the subcarriers are used for IoT data transmission, as shown in FIG. 7, if the subcarrier of the first RU including 26 subcarriers is left to the left
  • the subcarriers numbered -13, -12, -11, -10, and the subcarriers numbered 10, 11, and 12 can be used as protection subcarriers by pressing the -13, -12...11, and 12 numbers in sequence.
  • the subcarriers numbered -1, 0, and 1 are used as DC subcarriers.
  • an RU including 52 subcarriers when used as the IoT-RU, only 38 of them can be used for IoT data transmission, and if subcarriers of the RU including 52 subcarriers are pressed -26 from left to right, -25...24, 25 number, then 6 subcarriers numbered -26 to-21, and 5 subcarriers numbered 21 to 25 can be used as IoT protection subcarriers, and children numbered -1, 0, 1
  • the carrier acts as an IoT DC subcarrier.
  • the data field included in the downlink data frame may be generated by using the method shown in FIG. 8.
  • the network side device between the network side device and the IoT terminal The downlink data, which is described in FIG. 8 as IoT downlink data, is code modulated to obtain an IoT downlink modulation symbol.
  • the IoT downlink modulation symbol is mapped to the subcarrier included in the first RU, that is, the transmission position of the IoT downlink modulation symbol in the data field is located in the first RU The location of the carrier.
  • the network side device performs downlink data between the network side device and the STA, and shows 802.11ax downlink data in FIG.
  • the network side device performs inverse Fourier transform (IFFT) on the frequency domain signal including the first RU corresponding subcarrier and the second RU corresponding subcarrier, and adds a Cyclic Prefix (Cyclic Prefix, CP), generating a downlink baseband signal for mixed transmission of IoT and WLAN.
  • IFFT inverse Fourier transform
  • Cyclic Prefix Cyclic Prefix, CP
  • the IoT terminal can obtain the IoT downlink signal from the downlink receiving signal of the downlink data frame sent by the network side device through the receiving channel.
  • the bandwidth of the receiving channel of the IoT terminal in the embodiment of the present invention does not exceed the bandwidth of the first RU.
  • the carrier frequency of the receiving channel of the IoT terminal is set to f 0 +f r , where f 0 is the carrier frequency of the downlink received signal, and f r is the center frequency of the first RU relative to the zero frequency ( For example, the frequency difference of the frequency point corresponding to the subcarrier numbered 0 in FIG.
  • the WLAN downlink signal outside the first RU band is filtered out, so the IoT terminal may filter the remaining IoT downlink.
  • the signal is processed to obtain downlink data between the network side device and the IoT terminal.
  • FIG. 9 is a schematic diagram of a process for processing downlink data between the network side device and the IoT terminal by processing an IoT downlink signal by an IoT terminal according to an OFDM method according to an embodiment of the present invention.
  • the IoT terminal removes the CP from each OFDM symbol of the IoT downlink signal, and performs upsampling and FFT of the corresponding number of points to obtain an IoT modulated signal mapped to the subcarrier included in the first RU.
  • the 20 MHz, 40 MHz, and 80 MHz channel bandwidths are respectively 256 points, 512 points, and 1024 points of FFT, and the IoT modulated signals mapped to the subcarriers included in the first RU are obtained.
  • the IoT terminal demodulates and decodes the IoT modulated signal to obtain downlink data between the network side device and the IoT terminal.
  • the second implementation manner is: the network side device sends a downlink IoT frame to the IoT terminal by using the first RU according to a single carrier (SC) mode.
  • SC single carrier
  • the two edge positions of the first RU may be A set number of subcarriers is used as a protection subcarrier.
  • the downlink IoT frame transmission based on the OFDM method is different from the DC offset of the receiver.
  • the single-carrier mode is less affected by the DC offset of the receiver. Therefore, the DC subcarrier does not need to be reserved.
  • a downlink IoT frame is transmitted to the IoT terminal in a single carrier manner on a frequency band corresponding to the other subcarriers included in the first RU except the protection subcarrier.
  • the first RU when an RU containing 26 subcarriers is used as the first RU, 20 of them can be used.
  • the subcarriers are used for downlink IoT frame transmission in the single carrier mode, and the 6 subcarriers numbered -13, -12, -11, and numbered 10, 11, 12 are used as guard subcarriers.
  • the 6 subcarriers numbered -13, -12, -11, and numbered 10, 11, 12 are used as guard subcarriers.
  • an RU containing 52 subcarriers when an RU containing 52 subcarriers is used as the first RU, only 42 of the subcarriers may be used for the downlink IoT frame transmission in the single carrier mode, and will be numbered -26 to -22, and numbered 21 to 25.
  • a total of 10 subcarriers are used as guard subcarriers.
  • the data field included in the downlink data frame may be generated by using the method shown in FIG. 10, where the network side device between the network side device and the STA is used in FIG.
  • Downstream data shown in Figure 10, is the downlink data of 802.11ax, and is code modulated to obtain WLAN downlink modulation symbols.
  • the WLAN downlink modulation symbol is obtained, the WLAN downlink modulation symbol is mapped to the subcarrier included in the second RU, that is, the transmission position of the WLAN downlink modulation symbol in the data field is located in the first RU Where the carrier is located.
  • the network side device performs an IFFT on the frequency domain signal including the second RU corresponding subcarrier, and adds a CP to generate a WLAN downlink baseband signal.
  • the network side device performs downlink data between the network side device and the IoT terminal, and FIG. 10 encodes and modulates IoT downlink data, and adds a CP to generate an IoT downlink single carrier symbol.
  • the network side device performs waveform shaping filtering on the IoT downlink single carrier symbol to obtain an IoT downlink baseband signal.
  • the network side device performs frequency conversion on the IoT downlink baseband signal, that is, the IoT downlink baseband signal multiplied as shown in FIG. Get the IoT downlink bandpass signal. Where t is a time variable, the center frequency of the IoT downlink bandpass signal is fr , and fr is the frequency difference of the center frequency of the first RU relative to the zero frequency.
  • the network side device adds the IoT downlink bandpass signal and the WLAN downlink baseband signal to obtain a downlink baseband signal that is mixed and transmitted by the IoT and the WLAN.
  • the IoT terminal can obtain the IoT downlink signal from the downlink receiving signal of the downlink data frame that is sent by the network side device through the receiving channel.
  • the bandwidth of the receiving channel of the IoT terminal in the embodiment of the present invention does not exceed the bandwidth of the first RU.
  • the carrier frequency of the receiving channel of the IoT terminal is set to f 0 +f r , where f 0 is the carrier frequency of the downlink received signal, and f r is the center frequency of the first RU relative to the zero frequency ( For example, the frequency difference of the frequency point corresponding to the subcarrier numbered 0 in FIG.
  • the WLAN downlink signal outside the first RU band is filtered out, so the IoT terminal may filter the remaining IoT downlink.
  • the signal is processed to obtain downlink data between the network side device and the IoT terminal.
  • FIG. 11 is a schematic diagram of a process of processing IoT downlink signals by an IoT terminal according to an embodiment of the present invention to obtain downlink data between the network side device and the IoT terminal.
  • the IoT terminal removes the CP from each single carrier symbol of the IoT downlink signal, and performs frequency domain equalization to obtain an IoT modulated signal mapped to a frequency band corresponding to the first RU.
  • the IoT terminal demodulates and decodes the IoT modulated signal to obtain downlink data between the network side device and the IoT terminal.
  • the network side device adopts the frequency domain processing manner, and can simultaneously receive and transmit the IoT and 802.11ax signals, avoiding the dual mode, and reducing the implementation complexity of the network side device to implement the IoT communication.
  • the IoT downlink single carrier modulation symbol used in the single carrier mode transmission may adopt Frequency Shift Keying (FSK) or Differential Phase Shift Keying (DPSK). Quadrant Phase Shift Keying (QPSK), Gaussian Frequency Shift Keying (GFSK) and other constant envelope modulation methods, Quadrature Amplitude Modulation (QAM)
  • the waveform shaping filter used may typically employ a filter such as a Gaussian filter or a halved root raised cosine filter.
  • the bandwidth (about 1/T 1 ) of each IoT downlink single-carrier modulation symbol does not exceed the bandwidth of the first RU used. For example, when the first RU is an RU that includes 26 sub-carriers,
  • each IoT downlink single carrier symbol includes up to 26 modulators in addition to CP. number.
  • each IoT downlink single carrier symbol includes at most 52 modulation symbols in addition to the CP.
  • a typical first RU is an RU that includes 26 or 52 subcarriers, so in the embodiment of the present invention, each 20 MHz, In the first RU in the 40 MHz or 80 MHz channel, at least one basic RU is set, and the IoT terminal first communicates with the network side device using the basic RU.
  • the IoT terminal first receives the IoT downlink signal on the basic RU of the downlink data frame, so as to perform uplink or downlink communication with the network side device such as the AP, and the network side device may send the channel indication information on the basic RU, where The channel indication information is used to indicate that the IoT terminal is switched by the basic RU to other RUs for transmitting downlink IoT frames except the basic RU.
  • the IoT data field may be further divided into a structure of Time Division Multiplexing (TDM), that is, the IoT data field includes at least one subframe.
  • TDM Time Division Multiplexing
  • the IoT data field includes downlink data of at least two IoT terminals, and downlink data of each IoT terminal occupies at least one subframe, or occupies at least one time slot of at least one subframe, or occupies at least one a subframe and at least one time slot of at least one subframe.
  • the IoT data field is equally divided into P subframes, and each subframe may be further divided into Q slots.
  • the slots may not be divided, so that different IoT terminals may use the IoT data field.
  • an IoT-RU can be realized by Time Division Multiple Access (TDMA), and communication between the network side device and multiple IoT terminals can be realized, which satisfies IoT communication.
  • TDMA Time Division Multiple Access
  • the IoT terminal handles low data rates, large numbers, and wide distribution, and needs to cover IoT terminals in a relatively wide range, and supports multi-user multiplexing requirements of a large number of IoT terminals.
  • the smallest unit of the OFDMA signal in the time domain is the OFDM symbol
  • 802.11ax introduces OFDM symbols of different time lengths such as 1 times (abbreviated as 1x), 2 times (abbreviated as 2x), and 4 times (abbreviated as 4x), Including Cyclic Prefix (CP), they are 3.2 micrometers in length. Seconds, 6.4 microseconds and 12.8 microseconds.
  • the 1x and 2x symbol lengths in 802.11ax are mainly used for preamble. For example, they are backward compatible with 802.11a, 802.11n, 802.11ac, etc., traditional preamble, RL-SIG, HE-SIG-A and HE-SIG-B.
  • An OFDM symbol of 1x symbol length is processed with a 64-point FFT in the case of a 20 MHz channel bandwidth, and corresponds to 64 subcarriers in the frequency domain.
  • the longer OFDM symbol CP has less overhead. Therefore, the efficiency data field is 4x symbol length, the 20MHz channel bandwidth is processed by 256 points FFT, and the frequency domain corresponds to 256 subcarriers.
  • the OFDM symbol length of the IoT downlink modulation symbol in the data field included in the downlink data frame is the same length as 802.11ax, that is, the CP length is the same.
  • the length of the IoT downlink modulation symbol is the same as the length of the OFDM symbol of the 802.11ax in the embodiment of the present invention, that is, the IoT downlink modulation symbol is aligned with the upper boundary of the OFDM symbol of the 802.11ax, that is, the 4x symbol. length.
  • the IoT single carrier symbol and the 802.11ax data field OFDM symbol may not be aligned, that is, the IoT single carrier symbol may be selected differently from the 802.11ax data field OFDM symbol.
  • the length, and the length of the CP can also be different.
  • the network device determines that the terminal device that performs downlink data transmission includes an IoT terminal, and the network side device sends a downlink data frame, and the downlink data frame uses a downlink IoT frame frequency division multiplexing data in the 802.11ax.
  • the manner of the data field of the frame enables the network side device to schedule and coordinate the IoT terminal, thereby reducing the risk of interference of the IoT transmission.
  • the STA parses the traditional preamble and the HEW preamble to obtain timing synchronization, frequency synchronization, and channel estimation information
  • the IoT terminal parses the preamble portion in the downlink IoT frame to obtain IoT terminal timing synchronization, frequency synchronization, and channel.
  • the estimated information does not need to be parsed into the preamble part of 802.11ax, so that the frequency division between the IoT terminal and the STA in the 802.11ax channel resources does not interfere with each other.
  • the IoT terminal does not need to support a large bandwidth such as 20/40/80 MHz, and effectively supports a bandwidth-limited narrow-band IoT terminal, thereby ensuring low complexity and low power consumption of the IoT device.
  • Inventive embodiments provide another IoT communication method.
  • FIG. 13 is a flowchart of an implementation of a second IoT communication method according to an embodiment of the present invention.
  • the execution process of the method flow shown in FIG. 13 is an IoT terminal.
  • the implementation process of the IoT communication method includes:
  • the IoT terminal acquires a downlink IoT frame from the downlink received signal.
  • the downlink receiving signal includes a downlink data frame sent by the network side device.
  • the downlink data frame includes a legacy preamble, an HEW preamble, and a data field, where the traditional preamble and the HEW preamble are used for communication between a network side device and a station STA, and the data field corresponds to a subcarrier resource in a frequency domain.
  • the at least one RU is configured to send a downlink IoT frame, where the downlink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the downlink IoT frame,
  • the IoT data field is used to transmit downlink data between the network side device and the IoT terminal.
  • the data field of the downlink data frame sent by the network side device in the embodiment of the present invention may further include at least one other RU different from the RU for transmitting the IoT downlink data frame, where the corresponding subcarrier resource in the frequency domain may further include One other RU is used to transmit downlink data between the network side device and the STA.
  • the RU for transmitting the IoT downlink data frame is referred to as a first RU, and the RU for transmitting downlink data between the network side device and the STA is referred to as a first.
  • Two RU In the embodiment of the present invention, the first RU is used by the network side device to send a downlink IoT frame to the IoT terminal, and the second RU is used by the network side device to send the network side device to the STA Downlink data with the STA.
  • the bandwidth of the receiving channel of the IoT terminal does not exceed the bandwidth of the first RU.
  • the receiving channel of the IoT terminal adopts a carrier frequency of f 0 +f r , where f 0 is a carrier frequency of the downlink received signal, and f r is a frequency of a center frequency of the first RU relative to a zero frequency difference.
  • the IoT terminal processes the downlink IoT frame, and obtains the network side device and the Downlink data between IoT terminals.
  • the IoT terminal processes the downlink IoT frame, and obtains a specific implementation process of the downlink data between the network side device and the IoT terminal.
  • the IoT terminal processes the downlink IoT frame, and obtains a specific implementation process of the downlink data between the network side device and the IoT terminal.
  • the IoT downlink signal received by the IoT terminal includes a downlink data frame sent by the network side device, and the data field of the downlink IoT frame and the 802.11ax data frame in the downlink data frame is frequency division multiplexed, so that the IoT The terminal is scheduled and coordinated by the network side device to reduce the risk of interference of IoT transmission.
  • the STA parses the traditional preamble and the HEW preamble to obtain timing synchronization, frequency synchronization, and channel estimation information
  • the IoT terminal parses the preamble portion in the downlink IoT frame to obtain IoT terminal timing synchronization, frequency synchronization, and channel.
  • the estimated information does not need to be parsed into the preamble part of 802.11ax, so that the frequency division between the IoT terminal and the STA in the 802.11ax channel resources does not interfere with each other.
  • the IoT terminal does not need to support a large bandwidth such as 20/40/80 MHz, and effectively supports a bandwidth-limited narrow-band IoT terminal, thereby ensuring low complexity and low power consumption of the IoT device.
  • the above embodiments of the present invention mainly describe the process of downlink data transmission by the network side device such as an AP, and the downlink data reception by the IoT terminal.
  • the following describes the process of transmitting uplink data by the IoT terminal and the uplink data receiving by the network device such as the AP by using the IoT communication mode provided by the embodiment of the present invention.
  • FIG. 14 is a flowchart of a third IoT communication method according to an embodiment of the present invention.
  • the method of the method shown in FIG. 14 is an IoT terminal, and the IoT terminal performs uplink data transmission.
  • the method includes:
  • the IoT terminal receives an uplink transmission scheduling request sent by the network side device.
  • the network side device when the IoT terminal sends the uplink data to the network side device such as the AP, the network side device needs to send an uplink transmission scheduling request, where the uplink transmission scheduling request is used to schedule the IoT terminal to send an uplink IoT frame and perform uplink data. transmission.
  • the uplink IoT frame is located in a data field of an uplink data frame, and the data field of the uplink data frame includes at least one RU in a corresponding subcarrier resource in the frequency domain, and the at least one RU is used to send the uplink IoT frame.
  • the uplink transmission scheduling request in the embodiment of the present invention may include an identifier of an IoT terminal scheduled to perform uplink data transmission, an uplink transmission resource allocated to the IoT terminal performing uplink data transmission, and a code modulation manner.
  • the IoT terminal that is scheduled to perform uplink data transmission receives the uplink transmission scheduling request, and learns whether the network side device allows the IoT terminal that receives the uplink transmission scheduling request to send uplink data, and acquires transmission resources and transmissions used for transmitting the uplink data.
  • Information such as format, so that the IoT terminal scheduled to perform uplink data transmission transmits uplink data based on the information.
  • the uplink transmission scheduling request may be sent in the form of a downlink data frame, where the downlink data frame includes a traditional preamble, an HEW preamble, and a data field, where the traditional preamble and the HEW preamble are used by the network side device and the station STA.
  • the corresponding subcarrier resource in the frequency domain includes at least one RU for transmitting the uplink transmission scheduling request.
  • the RU for transmitting the uplink transmission scheduling request may also be referred to as a first RU in the embodiment of the present invention.
  • the uplink transmission scheduling request sent by the network side device may be a single downlink trigger frame, and the downlink trigger frame may adopt a frame structure of the downlink data frame shown in FIG. 6.
  • the network side device may also send the downlink data and the downlink trigger frame to schedule the IoT terminal to perform uplink data transmission, that is, the first RU may send the downlink data to the IoT terminal, in addition to the uplink transmission scheduling request, the downlink data.
  • the corresponding IoT terminal may be an IoT terminal scheduled to perform uplink data transmission, or may be another IoT terminal.
  • the IoT terminal sends an uplink IoT frame according to the uplink transmission scheduling request.
  • the uplink IoT frame sent by the IoT terminal in the embodiment of the present invention includes an IoT preamble and an IoT data field, where the uplink IoT frame includes an IoT preamble and an IoT data field, and the IoT preamble is used to transmit the physical of the uplink IoT frame.
  • Layer control information the IoT data field is used to transmit uplink data between the network side device and the IoT terminal.
  • the physical layer control information of the uplink IoT frame transmitted by the IoT preamble includes one or any combination of the following sequence: a synchronization sequence used by the network side device to acquire timing and frequency synchronization of the uplink IoT frame, and used by the network side device Obtaining a training sequence of channel estimates required to demodulate the uplink IoT frame.
  • the uplink IoT frame is located in a data field of the uplink data frame, where
  • the row data frame includes a legacy preamble, an HEW preamble, and a data field, where the legacy preamble and the HEW preamble are used for communication between the network side device and the station STA, and the data field corresponding to the subcarrier resource in the frequency domain includes the first Three RU.
  • the uplink IoT frame is located at the third RU position. In other words, in the embodiment of the present invention, the uplink IoT frame is sent by using the third RU.
  • the uplink transmission scheduling request in the embodiment of the present invention further includes location information of the uplink IoT frame sent by the IoT terminal, where the location information includes a start time of a data field of the uplink data frame, and sending the The identifier of the third RU of the uplink IoT frame.
  • the IoT terminal can transmit the uplink IoT frame on the third RU from the start time of the data field of the uplink data frame according to the uplink transmission scheduling request.
  • the third RU is an RU for transmitting uplink data between the network side device and the IoT terminal, and may also be referred to as an IoT-RU.
  • the non-IoT-RU is an RU for transmitting uplink data between the network side device and the STA.
  • the subcarrier resources in the data field in the data frame are frequency-division multiplexed with the STA by the IoT terminal.
  • the uplink data frame includes a legacy preamble, an HEW preamble, and a data field.
  • the conventional preamble shown in FIG. 15 includes fields such as L-STF, L-LTF, and L-SIG as shown in FIG. 2.
  • the HEW preamble shown in FIG. 15 includes the RL-SIG shown in FIG.
  • Fields such as HE-SIG-A, HE-SIG-B, HE-STF, and HE-LTF, that is, the conventional preamble and HEW preamble included in the uplink data frame and the conventional preamble and HEW preamble in 802.11ax are involved in the embodiments of the present invention.
  • the functions and structures are the same, and are used for communication between the network side device and the STA.
  • the data field included in the uplink data frame shown in FIG. 15 is different from the data field in the data frame structure in the 802.11ax shown in FIG. 2, and the foregoing is involved in the uplink data frame shown in FIG. 15 of the embodiment of the present invention.
  • the subcarrier resources corresponding to the data field in the frequency domain include a third RU and a non-IoT-RU; and the third RU is used to send an uplink IoT frame.
  • the non-IoT-RU is used by the STA to send uplink data between the network side device and the STA to the network side device.
  • An uplink IoT frame located on a third RU of the embodiment of the present invention includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the uplink IoT frame, and the IoT data The field is used to transmit uplink data between the network side device and the IoT terminal.
  • the physical layer control information of the uplink IoT frame transmitted by the IoT preamble includes one or any combination of the following sequences:
  • a synchronization sequence for acquiring, by the network side device, timing and frequency synchronization of the uplink IoT frame
  • the network side device obtains information about timing synchronization, frequency synchronization, or channel estimation of the IoT terminal by parsing the preamble part in the uplink IoT frame, that is, IoT
  • the terminal only needs to send a narrow-band uplink IoT frame, and does not need to support a large bandwidth such as 20/40/80 MHz. Therefore, the present invention can effectively support a bandwidth-limited narrow-band IoT terminal, and ensures low complexity and low power consumption of the IoT device.
  • the subcarrier resources of the data field are all used to transmit the uplink IoT frame.
  • the uplink data frame may not include the legacy preamble and the HEW preamble, and the data field includes the third RU, as shown in FIG. 16.
  • the IoT terminal after receiving the uplink trigger request, that is, the downlink data frame sent by the following data frame structure, the IoT terminal starts the transmission of the uplink data frame after the set time interval, and the set time interval should be greater than The time required for the scheduled IoT terminal to demodulate and decode the downlink data frame, and to prepare for transmission of the uplink data frame (such as the conversion of the RF channel in the downlink, etc.).
  • the physical layer frame structure of the uplink data transmission corresponding to the uplink IoT frame transmission by using the uplink data frame shown in FIG. 15 in the embodiment of the present invention is as shown in FIG. 17.
  • the physical layer frame structure for performing uplink data transmission corresponding to uplink IoT frame transmission using the uplink data frame shown in FIG. 16 is as shown in FIG. 18.
  • the first implementation manner is that the IoT terminal sends an uplink IoT frame by using the third RU according to the OFDM mode.
  • the IoT terminal in order to avoid the interference of the 802.11ax signal in the third RU band to the IoT signal in the third RU band, the IoT terminal sends the uplink IoT frame in the following manner:
  • a set number of subcarriers at the two edge positions of the third RU are used as protection subcarriers.
  • a set number of subcarriers at the intermediate position of the third RU is used as a DC subcarrier.
  • the method shown in FIG. 19 may be adopted, and the uplink IoT frame is sent by using the third RU.
  • the IoT terminal performs uplink data between the network side device and the IoT terminal, and FIG. 19 shows IoT uplink data, performs coding and modulation, obtains an IoT uplink modulation symbol, and uses the IoT uplink modulation symbol. Mapping to subcarriers included in the third RU.
  • the IoT terminal performs IFFT and downsampling on the frequency domain signal including the third RU corresponding subcarrier, and adds a CP to obtain a first IoT uplink baseband signal. And transmitting the first IoT uplink baseband signal through an uplink transmission channel.
  • the carrier frequency of the uplink transmit channel that transmits the first IoT uplink baseband signal is f 0 +f r , where f 0 is the carrier frequency of the channel for transmitting the uplink data frame where the third RU is located, f r The frequency difference of the center frequency of the third RU with respect to the zero frequency.
  • the second mode the IoT terminal sends an uplink IoT frame through the third RU based on the single carrier mode.
  • the IoT terminal in the embodiment of the present invention specifically sends the uplink IoT frame in the following manner:
  • the IoT terminal uses a set number of subcarriers at two edge positions of the third RU as a protection subcarrier.
  • the IoT terminal sends an uplink IoT frame to the network side device in a single carrier manner on a frequency band corresponding to the other subcarriers included in the third RU except the protection subcarrier.
  • the IoT terminal in the embodiment of the present invention may send the uplink IoT frame in a single carrier manner in the manner shown in FIG.
  • the IoT terminal encodes and modulates uplink data between the network side device and the IoT terminal
  • the IoT uplink data shown in FIG. 20 is uplink data between the network side device and the IoT terminal.
  • An additional cyclic prefix is generated to generate an IoT uplink single carrier symbol.
  • the IoT terminal performs waveform shaping filtering on the IoT uplink single carrier symbol to obtain a second IoT uplink base. With signal.
  • the IoT terminal transmits the second IoT uplink baseband signal through an uplink transmission channel.
  • the carrier frequency of the uplink transmission channel is f 0 +f r , where f 0 is a carrier frequency of a channel for transmitting an uplink data frame where the third RU is located, and f r is the third RU The frequency difference between the center frequency point and the zero frequency.
  • the uplink IoT frame is transmitted in the single carrier mode, and the IoT uplink single carrier symbol is the same as the OFDM symbol length of the 802.11ax, that is, the The IoT uplink single carrier symbol and the OFDM symbol of the WLAN uplink baseband signal sent by the STA use the CP of the same length, and the length of the OFDM symbol of the WLAN uplink baseband signal sent by the STA is the same, that is, The IoT uplink single carrier symbol is aligned with the upper boundary of the OFDM symbol of 802.11ax, for example, may be 4x symbol length, as shown in FIG.
  • the length of the IoT uplink modulation symbol in the embodiment of the present invention is the same as the length of the OFDM symbol of the 802.11ax, that is, the IoT uplink modulation symbol and the OFDM of the 802.11ax.
  • the upper boundary of the symbol is aligned, ie 4x symbol length.
  • the IoT-RU is a third RU for transmitting uplink data between the IoT terminal and the network side device, and the non-IoT-RU is used for transmitting the STA and the network side.
  • the IoT terminal sends the uplink IoT frame through the third RU according to the manner, and is not restricted by the network side device to send the downlink IoT frame.
  • the network side device sends the downlink IoT frame by using the OFDM method
  • the IoT terminal may send the uplink IoT frame by using a single carrier.
  • K is a positive integer not exceeding the number of subcarriers included in the third RU
  • T 1 is a period of each modulation symbol
  • T 0 is a length of an OFDM symbol of the WLAN uplink baseband signal transmitted by the STA.
  • the uplink IoT frame includes at least two uplink IoT subframes sent by the IoT terminal, where each IoT terminal sends
  • the uplink IoT subframe sent includes an IoT preamble and an IoT data field.
  • the uplink IoT frame in the uplink data frame includes at least one subframe, and each IoT terminal transmits its own uplink IoT subframe by using at least one of the subframes, and the uplink IoT subframe sent by each IoT terminal includes an IoT preamble.
  • IoT data fields For example, as shown in FIG.
  • the uplink IoT frame is equally divided into P subframes, and different IoT terminals can use different subframes of the uplink IoT frame, that is, an IoT-RU can be implemented by TDMA, and the network side device and multiple devices can be realized.
  • the communication between IoT terminals satisfies IoT communication.
  • the IoT terminal handles low data rates, large numbers and wide distribution, needs to cover IoT terminals in a relatively long range, and supports multi-user multiplexing requirements of a large number of IoT terminals.
  • P subframes of the uplink IoT frame shown in FIG. 22 are equally divided, and are not limited in specific implementation, and the included subframes of the uplink IoT frame may not be equally divided.
  • the IoT terminal can be used with a low voltage power supply, and the transmission power is small, and the uplink PAPR requirement needs to be reduced as much as possible.
  • a constant envelope modulation method may be used, for example, GFSK modulation is adopted.
  • the embodiment of the present invention does not limit the use of the constant envelope modulation method.
  • the QAM modulation method may also be adopted.
  • the PAPR of the QAM modulation mode is slightly larger than the constant envelope modulation, but is still much smaller than the PAPR of the OFDM method. Achieve higher transfer rates.
  • the uplink IoT frame sent by the IoT terminal is located on the third RU of the uplink data frame, and the data field of the data frame in the 802.11ax of the upper IoT terminal and the STA frequency division multiplexing is used in the uplink data frame.
  • the way that the IoT terminal is scheduled and coordinated by the network side device reduces the risk of interference of the IoT transmission.
  • the IoT terminal only needs to transmit the narrowband uplink IoT frame and frequency-multiplex the channel resources in the 802.11ax with the STA without interference.
  • the IoT terminal does not need to support a large bandwidth such as 20/40/80 MHz, and effectively supports a bandwidth-limited narrow-band IoT terminal, thereby ensuring low complexity and low power consumption of the IoT device.
  • FIG. 23 is a flowchart of implementing a fourth IoT communication method according to an embodiment of the present invention.
  • the execution body of the method shown in FIG. 23 is a network side device, as shown in FIG. include:
  • the network side device sends an uplink transmission scheduling request to the IoT terminal.
  • the uplink transmission scheduling request is used to schedule an IoT terminal to send an uplink IoT frame, and perform uplink data transmission.
  • the uplink transmission scheduling request may be sent in the form of a downlink data frame, where the downlink data frame includes a traditional preamble, an HEW preamble, and a data field, where the traditional preamble and the HEW preamble are used by the network side device and the station STA.
  • the corresponding subcarrier resource in the frequency domain includes at least one RU for transmitting the uplink transmission scheduling request.
  • the RU for transmitting the uplink transmission scheduling request may also be referred to as a first RU in the embodiment of the present invention.
  • the network side device acquires an uplink IoT frame that is sent by the IoT terminal according to the uplink transmission scheduling request.
  • the uplink IoT frame is located in a data field of an uplink data frame, and the data field of the uplink data frame includes at least one RU in a corresponding subcarrier resource in the frequency domain, and the at least one RU is used to send the uplink IoT frame.
  • the RU of the uplink IoT frame is referred to as a third RU, and may also be referred to as an IoT-RU.
  • the uplink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the uplink IoT frame, where the IoT data field is used to transmit the network side device and the IoT terminal.
  • Upstream data is used to transmit physical layer control information of the uplink IoT frame.
  • the network side device may receive an uplink data frame that is sent by the IoT terminal according to the uplink transmission scheduling request, as shown in FIG.
  • the network side device acquires an uplink receiving signal, where the uplink receiving signal includes an uplink IoT frame sent by the IoT terminal.
  • the uplink IoT frame is located in a third RU of the uplink data frame.
  • the network side device removes the CP from the uplink received signal, and performs FFT to obtain a frequency domain received signal.
  • the network side device acquires a signal on a subcarrier corresponding to the third RU in the frequency domain received signal, to obtain an IoT frequency domain signal.
  • the network side device performs frequency domain equalization, IFFT, and demodulation and decoding processing on the IoT frequency domain signal to obtain uplink data between the network side device and the IoT terminal that are sent by using the IoT frame.
  • the network side device passes the downlink data frame direction
  • the IoT terminal sends an uplink scheduling request
  • the downlink data frame downlink IoT frame is frequency-division multiplexed with the data field of the 802.11ax data frame, so that the network side device can schedule and coordinate the IoT terminal, thereby reducing the risk of interference of the IoT transmission.
  • the network side device receives an uplink data frame that is sent by the IoT terminal according to the uplink transmission scheduling request.
  • the uplink data frame includes a traditional preamble, an HEW preamble, and a data segment, where the data segment includes a third RU for transmitting uplink data of the IoT terminal and the network side device. Therefore, in the embodiment of the present invention, the IoT terminal only needs to send a narrowband uplink IoT frame, and frequency division multiplexing the channel resources of the 802.11ax with the STA without interference. In the above manner, the IoT terminal does not need to support a large bandwidth such as 20/40/80 MHz, and effectively supports a bandwidth-limited narrow-band IoT terminal, thereby ensuring low complexity and low power consumption of the IoT device.
  • the network side device sends a downlink data frame, where the downlink data frame includes a traditional preamble, an HEW preamble, and a data field.
  • the legacy preamble and the HEW preamble are used for communication between a network side device and a STA.
  • the subcarrier resources corresponding to the data field in the frequency domain include a first RU and a second RU.
  • the first RU is configured to send a downlink IoT frame to the IoT terminal, where the downlink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble includes a physics for transmitting the downlink IoT frame by using the IoT preamble Layer control information, the IoT data field is used to transmit downlink data between the network side device and the IoT terminal.
  • the second RU is configured to send downlink data between the network side device and the STA to the STA.
  • the STA by using the foregoing downlink data frame, parses the traditional preamble and the HEW preamble, and obtains information such as STA timing synchronization, frequency synchronization, or channel estimation, and acquires between the network side device and the STA by using the second RU in the data field. Downstream data.
  • the IoT terminal parses the IoT preamble, obtains the IoT terminal timing synchronization, the frequency synchronization, and the channel estimation through the downlink data frame, and obtains the downlink data sent by the network side device by using the first RU in the data field.
  • the network side device may also send an uplink transmission scheduling request to the IoT terminal, and schedule the IoT terminal to send uplink data.
  • the network side device receives uplink data by using an uplink data frame, where the uplink data frame includes a traditional preamble, an HEW preamble, and a data field, where the traditional preamble and the HEW preamble are used between the network side device and the station STA.
  • Communication the data word
  • the sub-carrier resource corresponding to the segment in the frequency domain includes a third RU, and the third RU is used to transmit uplink data between the network side device and the IoT terminal.
  • the network side device can receive the uplink data frame in a single carrier manner, as shown in FIG. 25, the implementation process of the uplink data frame receiving in the single carrier mode, including: the uplink baseband receiving signal sampled by the network side device, first After removing the CP and IFFT processing, the frequency domain is transformed into a frequency domain, wherein the 20 MHz, 40 MHz, and 80 MHz channel bandwidths are respectively 256 points, 512 points, and 1024 points of FFT.
  • the 802.11ax uplink signal receiving process is performed on the signal on the non-IoT-RU, thereby obtaining the uplink data of the 802.11ax;
  • the signal on the IoT-RU is first subjected to frequency domain equalization, and then subjected to IFFT. Transforming to the time domain, and finally performing IoT uplink signal reception processing such as demodulation and decoding, thereby obtaining uplink data of the IoT.
  • IoT uplink signal reception processing such as demodulation and decoding
  • the IoT-RU is a RU of 26 subcarriers, and can be converted to the time domain by 32-point IFFT, and the IoT signal is sampled after frequency domain equalization.
  • the IoT-RU is an 52-subcarrier RU, which can be converted to the time domain by 64-point IFFT.
  • the IoT terminal does not send and receive the traditional preamble and the HEW preamble included in the uplink data frame and the downlink data frame, and the traditional preamble and the HEW preamble are used for communication between the network side device and the STA. That is, the traditional preamble and the HEW preamble in the downlink data frame are sent by the network side device, and the traditional preamble and the HEW preamble in the uplink data frame are sent by the STA.
  • the IoT-RU out-of-band signal is filtered out through the analog filter of the receiving channel, and the signal in the IoT-RU band is received.
  • the third RU included in the data field of the downlink data frame and the third RU included in the data field of the uplink data frame in the foregoing embodiment of the present invention have a traditional preamble independent of the downlink data frame.
  • the independent frame structure of the HEW preamble may be referred to as an IoT frame in the embodiment of the present invention.
  • the IoT preamble involved in the foregoing embodiment of the present invention includes physical layer control information for transmitting a downlink IoT frame or an uplink IoT frame, where the IoT data field is used to transmit between the network side device and the IoT terminal. Downstream data or uplink data.
  • the physical layer control information of the downlink IoT frame A synchronization sequence for acquiring timing and frequency synchronization of the downlink IoT frame for the IoT terminal, or a training sequence for obtaining an estimated channel required for demodulating the downlink IoT frame by the IoT terminal, or the like.
  • the physical layer control information of the uplink IoT frame includes a synchronization sequence for the network side device to acquire timing and frequency synchronization of the uplink IoT frame, or a training for the network side device to obtain a channel estimation required for demodulating the uplink IoT frame. Sequence, etc.
  • the network side device obtains information about timing synchronization, frequency synchronization, or channel estimation of the IoT terminal by parsing the preamble portion in the uplink IoT frame, that is, the IoT terminal only needs to send a narrowband uplink IoT frame. There is no need to support large bandwidths such as 20/40/80 MHz, so the present invention can effectively support bandwidth-limited narrowband IoT terminals, ensuring low complexity and low power consumption requirements of IoT devices.
  • FIG. 26 is an embodiment of an OFDM-based IoT frame according to an embodiment of the present invention, wherein the IoT-STF is used for IoT timing synchronization, automatic gain control, and the like.
  • the IoT-SIG is used to transmit IoT physical layer signaling.
  • IoT-LTF 1 is used to obtain the channel estimate required to demodulate the IoT-SIG.
  • the IoT-LTF 2 to IoT-LTF N is used for multiple input multiple output (MIMO) transmission to obtain the MIMO channel estimation required to demodulate the IoT data field.
  • the IoT data field is used to transmit IoT uplink data or IoT downlink data.
  • the prior art can be utilized, and the embodiments of the present invention are not described herein again.
  • the IoT-STF adopts a longer synchronization sequence.
  • the IoT-LTF 1 can adopt a similar structure of L-LTF, as shown in Figure 26, where the Double Guard Interval (DGI) is twice the CP length of the IoT OFDM symbol, and two long training sequences are continuously transmitted. (Long Training Sequence, LTS) symbol, each LTS symbol has a length of 12.8 microseconds.
  • DGI Double Guard Interval
  • LTS Long Training Sequence
  • the IoT-LTF 2 to IoT-LTF N can adopt a similar structure of HE-LTF.
  • the symbols of each IoT-LTF 2 to IoT-LTF N adopt the same structure of IoT-LTF 1 . That is, the cyclic prefix uses DGI or 4GI to continuously transmit 2 or 4 identical training symbols.
  • the IoT SIG can also perform repeated transmission. That is, the OFDM symbols of each IoT SIG are repeated 2 times or more.
  • FIG. 27 shows an embodiment of an IoT frame provided based on a single carrier mode according to an embodiment of the present invention, wherein the IoT_sync transmission synchronization sequence is used for IoT timing synchronization and automatic gain control.
  • IoT_sig is used to transmit IoT physical layer signaling.
  • the IoT data field is used to transmit IoT uplink data or IoT downlink data.
  • both the IoT_sig and IoT data fields are modulated by GFSK or DPSK.
  • the embodiment The receiving process of the IoT signal is relatively simple, and has the advantages of low cost and low power consumption.
  • the embodiment of the present invention provides a network side device 100.
  • the network side device 100 includes a determining unit 101 and a sending unit 102, where:
  • the determining unit 101 is configured to determine a terminal device that performs downlink data transmission, where the terminal device includes an IoT terminal.
  • the sending unit 102 is configured to send a downlink data frame.
  • the downlink data frame includes a legacy preamble, a high efficiency wireless local area network HEW preamble and a data field.
  • the data field corresponding to the subcarrier resource in the frequency domain includes at least one RU.
  • the RU is configured to send a downlink IoT frame to the IoT terminal, where the downlink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the downlink IoT frame, where the IoT data is used.
  • the field is used to transmit downlink data between the network side device 100 and the IoT terminal.
  • the terminal device further includes a station STA.
  • the subcarrier resource corresponding to the data field in the frequency domain further includes at least one other RU different from the RU.
  • the at least one other RU is configured to transmit downlink data between the network side device 100 and the STA.
  • the sending unit 102 is configured to send a downlink IoT frame to the IoT terminal by using the RU:
  • a set number of subcarriers at the two edge positions of the RU are used as guard subcarriers.
  • a set number of subcarriers at the intermediate position of the RU are used as DC subcarriers.
  • a downlink IoT frame is transmitted to the IoT terminal by using other subcarriers included in the RU other than the protection subcarrier and the DC subcarrier.
  • the sending unit 102 specifically generates a data field included in the downlink data frame in the following manner:
  • Downlink data between the network side device 100 and the IoT terminal is code modulated to obtain an IoT downlink modulation symbol, and the IoT downlink modulation symbol is mapped to a subcarrier included in the at least one RU.
  • the sending unit 102 may further send a downlink IoT frame to the IoT terminal by using the RU:
  • a set number of subcarriers at the two edge positions of the RU are used as guard subcarriers.
  • the sending unit 102 may specifically generate the data field included in the downlink data frame as follows:
  • Downlink data between the network side device 100 and the IoT terminal is code modulated, and a CP is added to generate an IoT downlink single carrier symbol.
  • Waveform shaping filtering is performed on the IoT downlink single carrier symbol to obtain an IoT downlink baseband signal.
  • fr is a center frequency of an RU for transmitting a downlink IoT frame
  • the frequency difference of the point relative to the zero frequency Adding the IoT downlink bandpass signal and the WLAN downlink baseband signal to obtain a downlink baseband signal that is mixed and transmitted by the IoT and the WLAN.
  • the OFDM symbol of the IoT downlink single carrier symbol and the WLAN downlink baseband signal adopts a CP of the same length, and the length of the IoT downlink single carrier symbol and the OFDM symbol of the WLAN downlink baseband signal The length is the same.
  • T 1 is the period of each modulation symbol
  • T 0 is the length of the OFDM symbol of the WLAN downlink baseband signal.
  • the RU for transmitting a downlink IoT frame includes at least one basic RU.
  • the sending unit 102 is further configured to send channel indication information on the basic RU.
  • the channel indication information is used to indicate that the IoT terminal is switched by the basic RU to other RUs for transmitting downlink IoT frames except the basic RU.
  • the physical layer control information of the downlink IoT frame transmitted by the IoT preamble in the embodiment of the present invention includes one or any combination of the following sequence: timing and frequency synchronization for the IoT terminal to acquire the downlink IoT frame. a synchronization sequence, a training sequence for the IoT terminal to acquire a channel estimate required to demodulate the downlink IoT frame.
  • the IoT data field includes at least one subframe.
  • the IoT data field contains downlink data of at least two IoT terminals. Among them, the downlink data of each IoT terminal Occupy at least one subframe. Or the downlink data of each IoT terminal occupies at least one time slot of at least one subframe. Or the downlink data of each IoT terminal occupies at least one subframe and at least one slot of at least one subframe.
  • the embodiment of the present invention further provides a network side device 1000.
  • the network side device 1000 includes a memory 1001, a processor 1002, and a transmitter 1003, where
  • the memory 1001 is configured to store program code executed by the processor 1002.
  • the processor 1002 is configured to invoke a program stored in the memory 1001 to determine a terminal device that performs downlink data transmission, where the terminal device includes an IoT terminal, and sends a downlink data frame by using the transmitter 1003.
  • the downlink data frame includes a legacy preamble, a high efficiency wireless local area network HEW preamble and a data field.
  • the data field corresponding to the subcarrier resource in the frequency domain includes at least one RU.
  • the RU is configured to send a downlink IoT frame to the IoT terminal, where the downlink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the downlink IoT frame, where the IoT data is used.
  • the field is used to transmit downlink data between the network side device 100 and the IoT terminal.
  • the processor 1002 is further configured to invoke the program stored in the memory 1001, and implement the function of the network side device 100 provided in the embodiment of the present invention to implement the first IoT communication method provided by the embodiment of the present invention. .
  • the functions of the processor 1002 reference may be made to the description of the first IoT communication method and the network side device 100 in the embodiment of the present invention, and details are not described herein again.
  • the network side device 100 and the network side device 1000 provided by the embodiments of the present invention may be, for example, an AP, and are not specifically limited in this embodiment of the present invention.
  • the network side device 100 and the network side device 1000 provided by the embodiment of the present invention determine that the terminal device that performs the downlink data transmission includes the IoT terminal, and the downlink data frame sent by the network side device 100 or the network side device 1000 adopts the downlink IoT frame frequency division.
  • the network side device 100 or the network side device 1000 can schedule and coordinate the IoT terminal, thereby reducing the risk of interference of the IoT transmission.
  • the STA resolves the traditional preamble and
  • the HEW preamble acquires information of timing synchronization, frequency synchronization, and channel estimation
  • the IoT terminal parses the preamble part in the downlink IoT frame to obtain information of timing synchronization, frequency synchronization, and channel estimation of the IoT terminal, without parsing the leading part of the 802.11ax.
  • no interference occurs between each other.
  • the IoT terminal does not need to support a large bandwidth such as 20/40/80 MHz, and effectively supports a bandwidth-limited narrow-band IoT terminal, thereby ensuring low complexity and low power consumption of the IoT device.
  • the IoT terminal 200 is provided by the embodiment of the present invention.
  • the IoT terminal 200 includes an obtaining unit 201 and a processing unit 202, where:
  • the obtaining unit 201 is configured to obtain a downlink IoT frame from the downlink received signal, where the downlink received signal includes a downlink data frame sent by the network side device.
  • the downlink data frame includes a traditional preamble, a high-efficiency WLAN HEW preamble, and a data field, where the corresponding subcarrier resource in the frequency domain includes at least one RU, and the at least one RU is used to send a downlink IoT frame.
  • the downlink IoT frame includes an IoT preamble for transmitting physical layer control information of the downlink IoT frame, and an IoT data field, where the IoT data field is used to transmit the network side device and the IoT terminal 200 Downstream data.
  • the processing unit 202 is configured to process the downlink IoT frame acquired by the acquiring unit 201 to obtain downlink data between the network side device and the IoT terminal 200.
  • the bandwidth of the receiving channel of the IoT terminal 200 does not exceed the bandwidth of the RU.
  • the receiving channel of the IoT terminal 200 adopts a carrier frequency of f 0 +f r , where f 0 is the carrier frequency of the downlink IoT frame, and f r is the frequency difference of the center frequency of the RU relative to the zero frequency .
  • the processing unit 202 is configured to process the downlink IoT frame in the following manner to obtain downlink data between the network side device and the IoT terminal 200:
  • the cyclic prefix CP is removed, and upsampling and Fourier transform FFT are performed to obtain an IoT modulated signal mapped to the subcarriers included in the RU. Demodulating and decoding the IoT modulated signal to obtain the network side device and the device The downlink data between the IoT terminals 200 is described.
  • the processing unit 202 is configured to process the downlink IoT frame in the following manner to obtain downlink data between the network side device and the IoT terminal 200. :
  • the cyclic prefix CP is removed, and frequency domain equalization is performed to obtain an IoT modulated signal mapped to a frequency band corresponding to the RU. Demodulating and decoding the IoT modulated signal to obtain downlink data between the network side device and the IoT terminal 200.
  • the IoT terminal 2000 is provided by the embodiment of the present invention.
  • the IoT terminal 2000 includes a memory 2001, a processor 2002, a sensor 2003, and a communication. Interface 2004, where:
  • the memory 2001 is configured to store program code executed by the processor 2002.
  • the processor 2002 is configured to invoke a program stored in the memory 2001, and control the sensor 2003 to obtain a downlink IoT frame from the downlink received signal through the communication interface 2004, and process the downlink IoT frame to obtain a network. Downlink data between the side device and the IoT terminal 2000.
  • the downlink receiving signal includes a downlink data frame sent by the network side device.
  • the downlink data frame includes a legacy preamble, an HEW preamble, and a data field, where the traditional preamble and the HEW preamble are used for communication between a network side device and a station STA, and the data field corresponds to a subcarrier resource in a frequency domain.
  • the at least one RU is configured to send a downlink IoT frame, where the downlink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the downlink IoT frame,
  • the IoT data field is used to transmit downlink data between the network side device and the IoT terminal.
  • the processor 2002 is further configured to invoke a program stored in the memory 2001,
  • the function of the IoT terminal 200 provided in the embodiment of the present invention is implemented to implement the second IoT communication method provided by the embodiment of the present invention.
  • the functions of the processor 2002 refer to the description of the second IoT communication method and the IoT terminal 200 in the embodiment of the present invention, and details are not described herein again.
  • the IoT terminal 200 and the IoT terminal 2000 provided by the foregoing embodiments of the present invention include the downlink data frame sent by the network side device, and the data field of the downlink IoT frame and the 802.11ax data frame in the downlink data frame.
  • the IoT terminal is scheduled and coordinated by the network side device, which reduces the risk of interference of the IoT transmission.
  • the STA parses the traditional preamble and the HEW preamble to obtain timing synchronization, frequency synchronization, and channel estimation information
  • the IoT terminal parses the preamble portion in the downlink IoT frame to obtain IoT terminal timing synchronization, frequency synchronization, and channel.
  • the estimated information does not need to be parsed into the preamble part of 802.11ax, so that the frequency division between the IoT terminal and the STA in the 802.11ax channel resources does not interfere with each other.
  • the IoT terminal does not need to support a large bandwidth such as 20/40/80 MHz, and effectively supports a bandwidth-limited narrow-band IoT terminal, thereby ensuring low complexity and low power consumption of the IoT device.
  • the embodiment of the present invention provides an IoT terminal 300.
  • the IoT terminal 300 provided by the embodiment of the present invention includes a receiving unit 301 and a sending unit 302, where:
  • the receiving unit 301 is configured to receive an uplink transmission scheduling request sent by the network side device, where the uplink transmission scheduling request is used to schedule the IoT terminal 300 to send an uplink IoT frame, where the uplink IoT frame is located in a data field of the uplink data frame.
  • the data field of the uplink data frame, the corresponding subcarrier resource in the frequency domain, includes at least one resource unit RU, and the at least one RU is used to send the uplink IoT frame.
  • the sending unit 302 is configured to send the uplink IoT frame according to the uplink transmission scheduling request received by the receiving unit 301.
  • the uplink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble is used to transmit physical layer control information of the uplink IoT frame, and the IoT data field is used to transmit the network side device.
  • the sending unit 302 specifically sends the sending manner as follows.
  • a set number of subcarriers at the two edge positions of the RU are used as guard subcarriers.
  • a set number of subcarriers at the intermediate position of the RU are used as DC subcarriers.
  • the sending unit 302 is configured to send the uplink IoT frame by using the RU:
  • the carrier frequency of the uplink transmission channel is f 0 +f r , where f 0 is the carrier frequency of the channel of the uplink data frame in which the RU is transmitted, and f r is the center frequency of the second RU relative to the zero frequency Frequency difference.
  • the sending unit 302 specifically sends the uplink IoT frame in the following manner:
  • a set number of subcarriers at the two edge positions of the RU are used as guard subcarriers. And transmitting an uplink IoT frame to the network side device in a single carrier manner on a frequency band corresponding to the other subcarriers included in the second RU except the protection subcarrier.
  • the sending unit 302 specifically sends the uplink IoT frame in a single carrier manner as follows:
  • the uplink data between the network side device and the IoT terminal 300 is code modulated, and the cyclic prefix CP is added to generate an IoT uplink single carrier symbol.
  • the carrier frequency of the uplink transmission channel is f 0 +f r , where f 0 is the carrier frequency of the channel of the uplink data frame in which the RU is transmitted, and f r is the frequency difference of the center frequency point of the RU relative to the zero frequency .
  • the OFDM symbol of the IoT uplink single carrier symbol and the WLAN uplink baseband signal sent by the STA in the embodiment of the present invention adopts a CP of the same length, and the IoT uplink single carrier symbol and the WLAN sent by the STA The lengths of the OFDM symbols of the uplink baseband signal are the same.
  • T 1 is a period of each modulation symbol
  • T 0 is a length of an OFDM symbol of the WLAN uplink baseband signal transmitted by the STA.
  • a synchronization sequence for timing and frequency synchronization of the uplink IoT frame is acquired by the network side device.
  • the IoT data field in the embodiment of the present invention may include at least one subframe.
  • the IoT data field contains uplink data of at least two IoT terminals 300.
  • the uplink data of each IoT terminal 300 occupies at least one subframe.
  • the uplink data of each IoT terminal 300 occupies at least one time slot of at least one subframe.
  • the uplink data of each IoT terminal 300 occupies at least one subframe and at least one slot of at least one subframe.
  • the uplink transmission scheduling request in the embodiment of the present invention may be sent by using a downlink data frame sent by the network side device.
  • the downlink data frame includes a traditional preamble, a high efficiency wireless local area network HEW preamble and a data field, and the downlink data frame includes a data field, and the corresponding subcarrier resource in the frequency domain includes at least one used to send the uplink transmission scheduling request. RU.
  • the embodiment of the present invention further provides an IoT terminal 3000.
  • the IoT terminal 3000 includes a memory 3001, a processor 3002, a receiver 3003, and Transmitter 3004, wherein:
  • the memory 3001 is configured to store program code executed by the processor 3002.
  • the processor 3002 is configured to invoke a program stored in the memory 3001, receive an uplink transmission scheduling request sent by the network side device by using the receiver 3003, and send an uplink IoT by using the transmitter 3004 according to the uplink transmission scheduling request. frame.
  • the uplink transmission scheduling request is used to schedule the IoT terminal 3000 to send an uplink IoT frame, where the uplink IoT frame is located in a data field of an uplink data frame, and the data field of the uplink data frame corresponds to a data field.
  • the carrier resource includes at least one RU, and the at least one RU is configured to send the uplink IoT frame.
  • the uplink IoT frame sent by the IoT terminal 3000 in the embodiment of the present invention includes an IoT preamble and an IoT data field, where the uplink IoT frame includes an IoT preamble and an IoT data field, and the IoT preamble is used to transmit the uplink IoT frame.
  • Physical layer control information where the IoT data field is used to transmit uplink data between the network side device and the IoT terminal 3000.
  • the processor 3002 is further configured to invoke the program stored in the memory 3001 to implement the function of the IoT terminal 300 provided in the embodiment of the present invention to implement the third IoT communication method provided by the embodiment of the present invention.
  • the functions of the processor 3002 reference may be made to the third IoT communication method and the related description of the IoT terminal 300 in the embodiment of the present invention, and details are not described herein again.
  • the uplink IoT frame sent by the IoT terminal 300 and the IoT terminal 3000 provided by the embodiment of the present invention is located in a data field of an uplink data frame, and the data field of the uplink data frame includes at least one RU in a frequency domain corresponding subcarrier resource.
  • the at least one RU is configured to send the uplink IoT frame.
  • the data field of the data frame in the 802.11ax is used in the uplink data frame in the uplink data frame, so that the IoT terminal is scheduled and coordinated by the network side device, thereby reducing the risk of interference of the IoT transmission.
  • the IoT terminal During the uplink data frame transmission, the IoT terminal only needs to transmit the narrowband uplink IoT frame and frequency-multiplex the channel resources in the 802.11ax with the STA without interference. In the above manner, the IoT terminal does not need to support a large bandwidth such as 20/40/80 MHz, and effectively supports a bandwidth-limited narrow-band IoT terminal, thereby ensuring low complexity and low power consumption of the IoT device.
  • the embodiment of the present invention provides a network side device 400.
  • the network side device 400 provided by the embodiment of the present invention includes a sending unit 401 and an obtaining unit 402. among them:
  • the sending unit 401 is configured to send an uplink transmission scheduling request to the IoT terminal, where the uplink transmission scheduling request is used to schedule the IoT terminal to send an uplink IoT frame.
  • the obtaining unit 402 is configured to acquire the uplink sent by the IoT terminal according to the sending unit 401.
  • the uplink IoT frame is located in a data field of the uplink data frame, and the data field of the uplink data frame includes at least one resource unit RU corresponding to the subcarrier resource in the frequency domain, where the at least one RU is used to send the uplink. IoT frame.
  • the uplink IoT frame includes an IoT preamble for transmitting physical layer control information of the uplink IoT frame, and an IoT data field, where the IoT data field is used to transmit the network side device 400 and the IoT terminal. Upstream data between.
  • the acquiring unit 402 is configured to obtain an uplink IoT frame that is sent by the IoT terminal according to the uplink transmission scheduling request, and includes:
  • the uplink received signal includes an uplink IoT frame sent by the IoT terminal.
  • the cyclic prefix CP is removed from the uplink received signal, and a Fourier transform FFT is performed to obtain a frequency domain received signal.
  • the sending unit 401 specifically sends an uplink transmission scheduling request to the IoT terminal in the following manner:
  • the uplink transmission scheduling request is sent through a downlink data frame.
  • the downlink data frame includes a traditional preamble, a high efficiency wireless local area network HEW preamble and a data field, and the downlink data frame includes a data field, and the corresponding subcarrier resource in the frequency domain includes at least one used to send the uplink transmission scheduling request. RU.
  • a synchronization sequence for timing and frequency synchronization of the uplink IoT frame is acquired by the network side device.
  • the embodiment of the present invention further provides a network side device 4000.
  • the network side device 4000 includes a memory 4001, a processor 4002, and a transceiver. 4003, wherein:
  • the memory 4001 is configured to store program code executed by the processor 4002.
  • the processor 4002 is configured to invoke a program stored in the memory 4001, send an uplink transmission scheduling request to the IoT terminal by using the transceiver 4003, and acquire an uplink IoT frame sent by the IoT terminal according to the uplink transmission scheduling request. .
  • the uplink transmission scheduling request may be sent in the form of a downlink data frame, where the downlink data frame includes a traditional preamble, an HEW preamble, and a data field, where the traditional preamble and the HEW preamble are used by the network side device and the station STA.
  • the corresponding subcarrier resource in the frequency domain includes at least one RU for transmitting the uplink transmission scheduling request.
  • the uplink IoT frame is located in a data field of an uplink data frame, and the data field of the uplink data frame includes at least one RU in a sub-carrier resource corresponding to the frequency domain, where the at least one RU is used to send the Upstream IoT frame.
  • the processor 4002 is further configured to invoke the program stored in the memory 4001, and implement the function of the network side device 400 provided in the embodiment of the present invention to implement the fourth IoT communication method provided by the embodiment of the present invention. .
  • the functions of the processor 4002 refer to the description of the third IoT communication method and the network side device 400 in the embodiment of the present invention, and details are not described herein again.
  • the network side device 400 and the network side device 4000 provided by the foregoing embodiment of the present invention send an uplink scheduling request to the IoT terminal through the downlink data frame, and the downlink data frame downlink IoT frame and the data field of the data frame in the 802.11ax are frequency-division multiplexed, so that The network side device 400 or the network side device 4000 can schedule and coordinate the IoT terminal to reduce the risk of interference of the IoT transmission.
  • the network side device 400 or the network side device 4000 receives an uplink data frame that is sent by the IoT terminal according to the uplink transmission scheduling request.
  • the uplink data frame includes a legacy preamble, an HEW preamble, and a data segment, where the data segment includes an RU for transmitting uplink data of the IoT terminal and the network side device. Therefore, in the embodiment of the present invention, the IoT terminal only needs to send a narrowband uplink IoT frame, and frequency division multiplexing the channel resources of the 802.11ax with the STA without interference. In the above manner, the IoT terminal does not need to support a large bandwidth such as 20/40/80 MHz, and effectively supports a bandwidth-limited narrow-band IoT terminal, thereby ensuring low complexity and low power consumption of the IoT device.
  • the embodiment of the present invention further provides a communication system 500, which includes a network side device 501, a STA 502, and an IoT terminal 503, as shown in FIG.
  • the network side device 501 sends a downlink data frame, where the downlink data frame includes a traditional preamble, an HEW preamble, and a data field.
  • the legacy preamble and the HEW preamble are used for communication between the network side device 501 and the STA 502.
  • the subcarrier resources corresponding to the data field in the frequency domain include a first RU and a second RU.
  • the first RU is configured to send a downlink IoT frame to the IoT terminal 503, where the downlink IoT frame includes an IoT preamble and an IoT data field, where the IoT preamble includes the IoT preamble for transmitting the downlink IoT frame.
  • the second RU is configured to send downlink data between the network side device 501 and the STA 502 to the STA 502.
  • the STA 502 parses the traditional preamble and the HEW preamble by using the foregoing downlink data frame, and obtains information such as the STA 502 timing synchronization, the frequency synchronization, or the channel estimation, and acquires the network side device 501 and the STA 502 by using the second RU in the data field. Downstream data.
  • the IoT terminal 503 parses the IoT preamble, obtains a field of the IoT terminal 503, the timing synchronization, the frequency synchronization, and the channel estimation, and acquires the downlink data sent by the network side device 501 by using the first RU in the data field. .
  • the network side device 501 may also send an uplink transmission scheduling request to the IoT terminal 503, and schedule the IoT terminal 503 to send uplink data.
  • the network side device 501 receives uplink data by using an uplink data frame, where the uplink data frame includes a traditional preamble, an HEW preamble, and a data field, where the traditional preamble and the HEW preamble are used by the network side device 501 and the station STA 502.
  • the communication between the network side device 501 and the IoT terminal 503 is used to transmit the uplink data between the network side device 501 and the IoT terminal 503.
  • the memory involved in the foregoing embodiment of the present invention may be a read-only memory (English: read-only memory; abbreviated as: ROM), a random access memory (English: random access memory; abbreviation: RAM), It can be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a magnetic disk storage medium or other magnetic storage device, or can be used to carry or store a desired form of instruction or data structure.
  • ROM read-only memory
  • RAM random access memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • magnetic disk storage medium or other magnetic storage device or can be used to carry or store a desired form of instruction or data structure.
  • the program code and any other medium that can be accessed by the computer but is not limited thereto, for example, the memory may be a combination of the above memories.
  • a processor may be a general-purpose central processing unit that connects various parts of the entire device by using various interfaces and lines, by running or executing instructions stored in the memory and calling data stored in the memory. Perform various functions and processing data of the corresponding device to monitor the corresponding device as a whole.
  • the processor may include one or more processing units; preferably, the processor may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, etc., and modulates The demodulation processor primarily handles wireless communications. It will be appreciated that the above described modem processor may also not be integrated into the processor 190.
  • the processor, memory can be implemented on a single chip.
  • the network side device 501 of the communication system 500 provided by the embodiment of the present invention may be the network side device 100, the network side device 1000, the network side device 400, or the network side device 4000 provided by the foregoing embodiments, and implement corresponding functions, and the present invention The embodiments are not described herein again.
  • the IoT terminal included in the communication system 500 provided by the embodiment of the present invention may be the IoT terminal device 200, the IoT terminal device 2000, the IoT terminal device 300, or the IoT terminal device 3000 provided by the foregoing embodiments, and implement corresponding functions, which are implemented by the present invention. The examples are not described here.
  • the WLAN data frame includes a data field corresponding to the sub-carrier resource in the frequency domain, and includes an RU for transmitting downlink data or uplink data between the network side device and the IoT terminal, and is used for The downlink data of the network side device and the STA and the RU of the uplink data are transmitted, so that the data frame in the WLAN network can be shared or received between the IoT terminal and the STA, so that the network side device of the WLAN can schedule the IoT. Terminals reduce the risk of conflicts during IoT communication.
  • FIG. 1 These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Power Engineering (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种物联网通信方法、网络侧设备及物联网终端，本发明中，网络侧设备发送的下行数据帧包括传统前导、HEW前导和数据字段；所述数据字段在频域上对应的子载波资源包括至少一个资源单元RU；所述RU用于向所述IoT终端发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据，通过本发明使得WLAN的网络侧设备可以调度IoT终端，降低IoT通信过程中出现冲突的风险。

Description

一种物联网通信方法、网络侧设备及物联网终端
本申请要求在2015年9月2日提交中国专利局、申请号为201510559591.0、发明名称为“一种物联网通信方法、网络侧设备及物联网终端”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及一种物联网通信方法、网络侧设备及物联网终端。
背景技术
物联网(Internet of Thing，IoT)作为一种人与物通信，物与物通信的网络，是新一代信息技术的重要组成部分。
IoT中，为获得物理世界的信息或实现对物理世界的物体进行控制，需要广泛大量的部署IoT终端，IoT终端为具有一定感知、计算、执行和通信等能力的各种设备，进而通过网络实现信息的传输、协同和处理。
由于广泛大量的部署IoT终端，需要较低的成本和复杂度，并要求IoT终端具有很低的功耗。为降低功耗和成本，通常IoT终端通信所用的信道带宽只有1～2MHz，远小于站点(Station，STA)等无线局域网(Wireless local Access Network，WLAN)设备所使用的信道带宽。WLAN标准由逐步演进的802.11a、802.11n、802.11ac等版本组成，目前IEEE 802.11标准组织已启动了称之为高效率无线局域网(High Efficiency WLAN，HEW)的新一代WLAN标准，即802.11ax的标准化工作，支持802.11ax的WLAN设备所使用的信道带宽至少为20MHz，因此，通常情况下，IoT终端不能直接接收和发送WLAN中的信号，即IoT通信不受接入点(Access Point，AP)等WLAN网络侧设备的调度和协调，故在目前的通信网络中，IoT终端之间、以及IoT终端与WLAN设备之间，不可避免的会出现冲突。
发明内容
本发明实施例提供一种IoT通信方法、网络侧设备及IoT终端，以使IoT终端进行IoT通信过程中可以接受网络侧设备的调度，降低IoT通信传输过程中出现冲突的风险。
第一方面，提供一种物联网IoT通信方法，包括：
网络侧设备确定进行下行数据传输的终端设备，所述终端设备包括IoT终端；
所述网络侧设备发送下行数据帧；
所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段；
所述数据字段在频域上对应的子载波资源包括至少一个资源单元RU；
所述RU用于向所述IoT终端发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据。
结合第一方面，在第一种实现方式中，所述终端设备还包括站点STA；
所述数据字段在频域上对应的子载波资源还包括不同于所述RU的至少一个其它RU；
所述至少一个其它RU用于传输所述网络侧设备与所述STA之间的下行数据。
结合第一方面或者第一方面的第一种实现方式，在第二种实现方式中，所述网络侧设备，具体采用如下方式，通过所述RU向所述IoT终端发送下行IoT帧：
将所述RU两个边缘位置处设定数量的子载波作为保护子载波；
将所述RU中间位置处设定数量的子载波作为直流子载波；
通过除所述保护子载波和所述直流子载波之外的、所述RU包含的其它子 载波，向所述IoT终端发送下行IoT帧。
结合第一方面的第二种实现方式，在第三种实现方式中，所述下行数据帧中包括的数据字段，具体采用如下方式生成：
所述网络侧设备将所述网络侧设备与所述IoT终端之间的下行数据，进行编码调制，得到IoT下行调制符号，并将所述IoT下行调制符号映射到所述至少一个RU包含的子载波上；
所述网络侧设备将所述网络侧设备与所述STA之间的下行数据，进行编码调制，得到无线局域网WLAN下行调制符号，并将所述WLAN下行调制符号映射到所述至少一个其它RU包含的子载波上；
所述网络侧设备对包含所述至少一个RU对应子载波和所述至少一个其它RU对应子载波的频域信号，进行傅立叶反变换IFFT，并附加循环前缀，生成IoT与WLAN混合传输的下行基带信号。
结合第一方面或者第一方面的第一种实现方式，在第四种实现方式中，所述网络侧设备，具体采用如下方式，通过所述RU向所述IoT终端发送下行IoT帧：
将所述RU两个边缘位置处设定数量的子载波作为保护子载波；
在除所述保护子载波之外的、所述RU包含的其它子载波所对应的频带上，以单载波方式向所述IoT终端发送下行IoT帧。
结合第一方面的第四种实现方式，在第五种实现方式中，所述下行数据帧中包括的数据字段，具体采用如下方式生成：
所述网络侧设备将所述网络侧设备与所述STA之间的下行数据，进行编码调制，得到无线局域网WLAN下行调制符号，并将所述WLAN下行调制符号映射到所述至少一个其它RU包含的子载波上；
所述网络侧设备对包含所述至少一个其它RU对应子载波的频域信号进行傅立叶反变换IFFT，并附加循环前缀CP，生成WLAN下行基带信号；
所述网络侧设备将所述网络侧设备与IoT终端之间的下行数据，进行编码调制，并附加CP，生成IoT下行单载波符号；
所述网络侧设备对所述IoT下行单载波符号进行波形成型滤波，得到IoT下行基带信号；
所述网络侧设备对所述IoT下行基带信号进行变频，得到IoT下行带通信号，其中，所述IoT下行带通信号的中心频点为fr，其中，fr为用于发送下行IoT帧的RU的中心频点相对于零频的频率差；
所述网络侧设备将所述IoT下行带通信号和所述WLAN下行基带信号相加，得到IoT与WLAN混合传输的下行基带信号。
结合第一方面的第五种实现方式，在第六种实现方式中，所述IoT下行单载波符号和所述WLAN下行基带信号的OFDM符号采用相同长度的CP，且所述IoT下行单载波符号的长度和所述WLAN下行基带信号的OFDM符号的长度相同。
结合第一方面的第五种实现方式或者第六种实现方式，在第七种实现方式中，所述IoT下行单载波符号包括K个调制符号，每个调制符号的周期为T1＝T0/K；
其中，K为不超过用于发送下行IoT帧的RU包含的子载波数的正整数，T1为每个调制符号的周期，T0为所述WLAN下行基带信号的OFDM符号的长度。
结合第一方面或者第一方面的上述任一种实现方式，在第八种实现方式中，所述用于发送下行IoT帧的RU包括至少一个基本RU，所述方法还包括：
所述网络侧设备，在所述基本RU上发送信道指示信息；
其中，所述信道指示信息用于指示IoT终端由所述基本RU切换到除所述基本RU之外的其它用于发送下行IoT帧的RU上。
结合第一方面或者第一方面的上述任一种实现方式中，在第九种实现方式中，所述IoT前导传输的所述下行IoT帧的物理层控制信息包括以下序列之一或任意组合：
用于IoT终端获取所述下行IoT帧的定时和频率同步的同步序列；
用于IoT终端获取解调所述下行IoT帧所需的信道估计的训练序列。
结合第一方面或者第一方面的上述任一种实现方式中，在第十种实现方式中，所述IoT数据字段包括至少一个子帧；
所述IoT数据字段包含至少两个IoT终端的下行数据；
其中，每个IoT终端的下行数据占用至少一个子帧；或者
每个IoT终端的下行数据占用至少一个子帧的至少一个时隙；或者
每个IoT终端的下行数据占用至少一个子帧和至少一个子帧的至少一个时隙。
第二方面，提供一种物联网IoT通信方法，包括：
IoT终端从下行接收信号中获取下行IoT帧，所述下行接收信号包含网络侧设备发送的下行数据帧；
所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一个RU用于发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据；
所述IoT终端对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据。
结合第二方面，在第一种实现方式中，所述IoT终端的接收通道的带宽不超过所述RU的带宽；
所述IoT终端的接收通道采用的载波频率为f0+fr，其中，f0为所述下行IoT帧的载波频率，fr为所述RU的中心频点相对于零频的频率差。
结合第二方面或者第二方面的第一种实现方式，在第二种实现方式中，所述IoT终端对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据，包括：
所述IoT终端对所述下行IoT帧的每个正交频分复用OFDM符号，去除循环前缀CP，并进行上采样以及傅立叶变换FFT，得到映射到所述RU包含的子载波上的IoT调制信号；
所述IoT终端对所述IoT调制信号进行解调解码，得到所述网络侧设备与所述IoT终端之间的下行数据。
结合第二方面或者第二方面的第一种实现方式，在第三种实现方式中，所述IoT终端对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据，包括：
所述IoT终端对所述下行IoT帧的每个单载波符号，去除循环前缀CP，并进行频域均衡，得到映射到所述RU所对应的频带上的IoT调制信号；
所述IoT终端对所述IoT调制信号进行解调解码，得到所述网络侧设备与所述IoT终端之间的下行数据。
结合第二方面或者第二方面的上述任一种实现方式，在第四种实现方式中，所述IoT前导传输的所述下行IoT帧的物理层控制信息包括以下序列之一或任意组合：
用于IoT终端获取所述下行IoT帧的定时和频率同步的同步序列；
用于IoT终端获取解调所述下行IoT帧所需的信道估计的训练序列。
第三方面，提供一种物联网IoT通信方法，包括：
IoT终端接收网络侧设备发送的上行传输调度请求；
所述上行传输调度请求用于调度所述IoT终端发送上行IoT帧；
所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一个RU用于发送所述上行IoT帧；
所述IoT终端依据所述上行传输调度请求，发送所述上行IoT帧；
所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的上行数据。
结合第三方面，在第一种实现方式中，所述IoT终端，具体采用如下方式，发送所述上行IoT帧：
将所述RU两个边缘位置处设定数量的子载波作为保护子载波；
将所述RU中间位置处设定数量的子载波作为直流子载波；
在除所述保护子载波和所述直流子载波之外的、所述RU包含的其它子载波上，向所述网络侧设备发送上行IoT帧。
结合第三方面的第一种实现方式，在第二种实现方式中，所述IoT终端，具体采用如下方式，通过所述RU发送所述上行IoT帧，包括：
所述IoT终端对所述网络侧设备与IoT终端之间的上行数据，进行编码调制，得到IoT上行调制符号，并将所述IoT上行调制符号映射到所述RU包含的子载波上；
所述IoT终端对包含所述RU对应子载波的频域信号，进行傅立叶反变换IFFT以及下采样，并附加循环前缀，得到第一IoT上行基带信号；
将所述第一IoT上行基带信号，通过上行发射通道发送；
所述上行发射通道的载波频率为f0+fr，其中，f0为传输RU所在的上行数据帧的信道的载波频率，fr为所述第二RU的中心频点相对于零频的频率差。
结合第三方面，在第三种实现方式中，所述IoT终端具体采用如下方式，发送所述上行IoT帧：
将所述RU两个边缘位置处的设定数量的子载波作为保护子载波；
在除所述保护子载波之外的、所述第二RU包含的其它子载波所对应的频带上，以单载波方式向所述网络侧设备发送上行IoT帧。
结合第三方面的第三种实现方式，在第四种实现方式中，所述IoT终端，具体采用如下方式以单载波方式发送所述上行IoT帧，包括：
所述IoT终端对所述网络侧设备与IoT终端之间的上行数据，进行编码调制，附加循环前缀CP，生成IoT上行单载波符号；
所述IoT终端对所述IoT上行单载波符号进行波形成型滤波，得到第二IoT上行基带信号；
所述IoT终端将所述第二IoT上行基带信号，通过上行发射通道发送；
所述上行发射通道的载波频率为f0+fr，其中，f0为传输RU所在的上行数据帧的信道的载波频率，fr为所述RU的中心频点相对于零频的频率差。
结合第三方面的第四种实现方式，在第五种实现方式中，所述IoT上行单载波符号和所述STA发送的WLAN上行基带信号的OFDM符号采用相同长度的CP，且所述IoT上行单载波符号和所述STA发送的WLAN上行基带信号的OFDM符号的长度相同。
结合第三方面的第四种实现方式或者第五种实现方式，在第六种实现方式中，所述IoT上行单载波符号包括K个调制符号，每个调制符号的周期为T1＝T0/K；
其中，K为不超过所述RU包含的子载波数的正整数，T1为每个调制符号的周期，T0为所述STA发送的WLAN上行基带信号的OFDM符号的长度。
结合第三方面或者第三方面的上述任一种实现方式，在第七种实现方式中，所述IoT前导传输的所述上行IoT帧的物理层控制信息包括以下序列之一或任意组合：
用于所述网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列；
用于所述网络侧设备获取解调所述下行IoT帧所需的信道估计的训练序列。
结合第三方面或者第三方面的上述任一种实现方式，在第八种实现方式中，所述上行IoT帧包含至少两个IoT终端发送的上行IoT子帧；
其中，每个IoT终端发送的所述上行IoT子帧包括IoT前导和IoT数据字段。
结合第三方面或者第三方面的上述任一种实现方式，在第九种实现方式中，所述上行传输调度请求通过网络侧设备发送的下行数据帧发送；
所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述下行数据帧包括的数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。
第四方面，提供一种物联网IoT通信方法，包括：
网络侧设备向IoT终端发送上行传输调度请求，所述上行传输调度请求用于调度所述IoT终端发送上行IoT帧；
所述网络侧设备获取所述IoT终端依据所述上行传输调度请求发送的上行IoT帧；
其中，所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一个RU用于发送所述上行IoT帧；
所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的上行数据。
结合第四方面，在第一种实现方式中，所述网络侧设备，具体采用如下方式接收所述IoT终端依据所述上行传输调度请求发送的上行IoT帧，包括：
所述网络侧设备获取上行接收信号，所述上行接收信号包含所述IoT终端发送的上行IoT帧；
所述网络侧设备对所述上行接收信号去除循环前缀CP，并进行傅立叶变换FFT，得到频域接收信号；
所述网络侧设备获取所述频域接收信号中所述RU对应的子载波上的信号，得到IoT频域信号；
所述网络侧设备对所述IoT频域信号进行频域均衡、傅立叶反变换IFFT，以及解调解码处理，得到所述网络侧设备与所述IoT终端之间的上行数据。
结合第四方面或者第四方面的第一种实现方式，在第二种实现方式中，所述网络侧设备向IoT终端发送上行传输调度请求，包括：
所述网络侧设备通过下行数据帧发送所述上行传输调度请求；
所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述下行数据帧包括的数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。
结合第四方面或者第四方面的上述任一种实现方式，在第三种实现方式中，所述IoT前导传输的所述上行IoT帧的物理层控制信息包括以下序列之一或任意组合：
用于所述网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列；
用于所述网络侧设备获取解调所述上行IoT帧所需的信道估计的训练序列。
第五方面，一种网络侧设备，包括：
确定单元，用于确定进行下行数据传输的终端设备，所述终端设备包括IoT终端；
发送单元，用于发送下行数据帧；
所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段；
所述数据字段在频域上对应的子载波资源包括至少一个资源单元RU；
所述RU用于向所述IoT终端发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据。
结合第五方面，在第一种实现方式中，所述终端设备还包括站点STA；
所述数据字段在频域上对应的子载波资源还包括不同于所述RU的至少一个其它RU；
所述至少一个其它RU用于传输所述网络侧设备与所述STA之间的下行数据。
结合第五方面或者第五方面的第一种实现方式，在第二种实现方式中，所述发送单元，具体采用如下方式，通过所述RU向所述IoT终端发送下行IoT帧：
将所述RU两个边缘位置处设定数量的子载波作为保护子载波；
将所述RU中间位置处设定数量的子载波作为直流子载波；
通过除所述保护子载波和所述直流子载波之外的、所述RU包含的其它子载波，向所述IoT终端发送下行IoT帧。
结合第五方面的第二种实现方式，在第三种实现方式中，所述发送单元 具体采用如下方式生成下行数据帧包括的数据字段：
将所述网络侧设备与所述IoT终端之间的下行数据，进行编码调制，得到IoT下行调制符号，并将所述IoT下行调制符号映射到所述至少一个RU包含的子载波上；
将所述网络侧设备与所述STA之间的下行数据，进行编码调制，得到无线局域网WLAN下行调制符号，并将所述WLAN下行调制符号映射到所述至少一个其它RU包含的子载波上；
对包含所述至少一个RU对应子载波和所述至少一个其它RU对应子载波的频域信号，进行傅立叶反变换IFFT，并附加循环前缀，生成IoT与WLAN混合传输的下行基带信号。
结合第五方面或者第五方面的第一种实现方式，在第四种实现方式中，所述发送单元，具体采用如下方式，通过所述RU向所述IoT终端发送下行IoT帧：
将所述RU两个边缘位置处设定数量的子载波作为保护子载波；
在除所述保护子载波之外的、所述RU包含的其它子载波所对应的频带上，以单载波方式向所述IoT终端发送下行IoT帧。
结合第五方面的第四种实现方式，在第五种实现方式中，所述发送单元具体采用如下方式生成下行数据帧包括的数据字段：
将所述网络侧设备与所述STA之间的下行数据，进行编码调制，得到无线局域网WLAN下行调制符号，并将所述WLAN下行调制符号映射到所述至少一个其它RU包含的子载波上；
对包含所述至少一个其它RU对应子载波的频域信号进行傅立叶反变换IFFT，并附加循环前缀CP，生成WLAN下行基带信号；
将所述网络侧设备与IoT终端之间的下行数据，进行编码调制，并附加CP，生成IoT下行单载波符号；
对所述IoT下行单载波符号进行波形成型滤波，得到IoT下行基带信号；
对所述IoT下行基带信号进行变频，得到IoT下行带通信号，其中，所述 IoT下行带通信号的中心频点为fr，其中，fr为用于发送下行IoT帧的RU的中心频点相对于零频的频率差；
将所述IoT下行带通信号和所述WLAN下行基带信号相加，得到IoT与WLAN混合传输的下行基带信号。
结合第五方面的第五种实现方式，在第六种实现方式中，所述IoT下行单载波符号和所述WLAN下行基带信号的OFDM符号采用相同长度的CP，且所述IoT下行单载波符号的长度和所述WLAN下行基带信号的OFDM符号的长度相同。
结合第五方面的第五种实现方式或者第六种实现方式，在第七种实现方式中，所述IoT下行单载波符号包括K个调制符号，每个调制符号的周期为T1＝T0/K；
其中，K为不超过用于发送下行IoT帧的RU包含的子载波数的正整数，T1为每个调制符号的周期，T0为所述WLAN下行基带信号的OFDM符号的长度。
结合第五方面或者第五方面的上述任一种实现方式，在第八种实现方式中，所述用于发送下行IoT帧的RU包括至少一个基本RU；
所述发送单元，还用于在所述基本RU上发送信道指示信息；
其中，所述信道指示信息用于指示IoT终端由所述基本RU切换到除所述基本RU之外的其它用于发送下行IoT帧的RU上。
结合第五方面或者第五方面的上述任一种实现方式中，在第九种实现方式中，所述IoT前导传输的所述下行IoT帧的物理层控制信息包括以下序列之一或任意组合：
用于IoT终端获取所述下行IoT帧的定时和频率同步的同步序列；
用于IoT终端获取解调所述下行IoT帧所需的信道估计的训练序列。
结合第五方面或者第五方面的上述任一种实现方式中，在第十种实现方式中，所述IoT数据字段包括至少一个子帧；
所述IoT数据字段包含至少两个IoT终端的下行数据；
其中，每个IoT终端的下行数据占用至少一个子帧；或者
每个IoT终端的下行数据占用至少一个子帧的至少一个时隙；或者
每个IoT终端的下行数据占用至少一个子帧和至少一个子帧的至少一个时隙。
第六方面，提供一种IoT终端，包括：
获取单元，用于从下行接收信号中获取下行IoT帧，所述下行接收信号包含网络侧设备发送的下行数据帧；
所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一个RU用于发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据；
处理单元，用于对所述获取单元获取的所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据。
结合第六方面，在第一种实现方式中，所述IoT终端的接收通道的带宽不超过所述RU的带宽；
所述IoT终端的接收通道采用的载波频率为f0+fr，其中，f0为所述下行IoT帧的载波频率，fr为所述RU的中心频点相对于零频的频率差。
结合第六方面或者第六方面的第一种实现方式，在第二种实现方式中，所述处理单元，具体用于采用如下方式对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据：
对所述下行IoT帧的每个正交频分复用OFDM符号，去除循环前缀CP，并进行上采样以及傅立叶变换FFT，得到映射到所述RU包含的子载波上的IoT调制信号；
对所述IoT调制信号进行解调解码，得到所述网络侧设备与所述IoT终端之间的下行数据。
结合第六方面或者第六方面的第一种实现方式，在第三种实现方式中， 所述处理单元，具体用于采用如下方式对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据：
对所述下行IoT帧的每个单载波符号，去除循环前缀CP，并进行频域均衡，得到映射到所述RU所对应的频带上的IoT调制信号；
对所述IoT调制信号进行解调解码，得到所述网络侧设备与所述IoT终端之间的下行数据。
结合第六方面或者第六方面的上述任一种实现方式，在第四种实现方式中，所述IoT前导传输的所述下行IoT帧的物理层控制信息包括以下序列之一或任意组合：
用于IoT终端获取所述下行IoT帧的定时和频率同步的同步序列；
用于IoT终端获取解调所述下行IoT帧所需的信道估计的训练序列。
第七方面，提供一种IoT终端，包括：
接收单元，用于接收网络侧设备发送的上行传输调度请求，所述上行传输调度请求用于调度所述IoT终端发送上行IoT帧，所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一个RU用于发送所述上行IoT帧；
发送单元，用于依据所述接收单元接收的上行传输调度请求，发送所述上行IoT帧；
所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的上行数据。
结合第七方面，在第一种实现方式中，所述发送单元，具体采用如下方式发送所述上行IoT帧：
将所述RU两个边缘位置处设定数量的子载波作为保护子载波；
将所述RU中间位置处设定数量的子载波作为直流子载波；
在除所述保护子载波和所述直流子载波之外的、所述RU包含的其它子载波上，向所述网络侧设备发送上行IoT帧。
结合第七方面的第一种实现方式，在第二种实现方式中，所述发送单元，具体采用如下方式，通过所述RU发送所述上行IoT帧：
对所述网络侧设备与IoT终端之间的上行数据，进行编码调制，得到IoT上行调制符号，并将所述IoT上行调制符号映射到所述RU包含的子载波上；
对包含所述RU对应子载波的频域信号，进行傅立叶反变换IFFT以及下采样，并附加循环前缀，得到第一IoT上行基带信号；
将所述第一IoT上行基带信号，通过上行发射通道发送；
所述上行发射通道的载波频率为f0+fr，其中，f0为传输RU所在的上行数据帧的信道的载波频率，fr为所述第二RU的中心频点相对于零频的频率差。
结合第七方面，在第三种实现方式中，所述发送单元，具体采用如下方式，发送所述上行IoT帧：
将所述RU两个边缘位置处的设定数量的子载波作为保护子载波；
在除所述保护子载波之外的、所述第二RU包含的其它子载波所对应的频带上，以单载波方式向所述网络侧设备发送上行IoT帧。
结合第七方面的第三种实现方式，在第四种实现方式中，所述发送单元，具体采用如下方式以单载波方式发送所述上行IoT帧：
对所述网络侧设备与IoT终端之间的上行数据，进行编码调制，附加循环前缀CP，生成IoT上行单载波符号；
对所述IoT上行单载波符号进行波形成型滤波，得到第二IoT上行基带信号；
将所述第二IoT上行基带信号，通过上行发射通道发送；
所述上行发射通道的载波频率为f0+fr，其中，f0为传输RU所在的上行数据帧的信道的载波频率，fr为所述RU的中心频点相对于零频的频率差。
结合第七方面的第四种实现方式，在第五种实现方式中，所述IoT上行单载波符号和所述STA发送的WLAN上行基带信号的OFDM符号采用相同长度的CP，且所述IoT上行单载波符号和所述STA发送的WLAN上行基带信号的OFDM符号的长度相同。
结合第七方面的第四种实现方式或者第五种实现方式，在第六种实现方式中，所述IoT上行单载波符号包括K个调制符号，每个调制符号的周期为T1＝T0/K；
其中，K为不超过所述RU包含的子载波数的正整数，T1为每个调制符号的周期，T0为所述STA发送的WLAN上行基带信号的OFDM符号的长度。
结合第七方面或者第七方面的上述任一种实现方式，在第七种实现方式中，所述IoT前导传输的所述上行IoT帧的物理层控制信息包括以下序列之一或任意组合：
用于所述网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列；
用于所述网络侧设备获取解调所述上行IoT帧所需的信道估计的训练序列。
结合第七方面或者第七方面的上述任一种实现方式，在第八种实现方式中，所述上行IoT帧包含至少两个IoT终端发送的上行IoT子帧；
其中，每个IoT终端发送的所述上行IoT子帧包括IoT前导和IoT数据字段。
结合第七方面或者第七方面的上述任一种实现方式，在第九种实现方式中，所述上行传输调度请求通过网络侧设备发送的下行数据帧发送；
所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述下行数据帧包括的数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。
第八方面，提供一种网络侧设备，包括：
发送单元，用于向IoT终端发送上行传输调度请求，所述上行传输调度请求用于调度所述IoT终端发送上行IoT帧；
获取单元，用于获取所述IoT终端依据所述发送单元发送的上行传输调度请求发送的上行IoT帧；
其中，所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一 个RU用于发送所述上行IoT帧；
所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的上行数据。
结合第八方面，在第一种实现方式中，所述获取单元，具体采用如下方式获取所述IoT终端依据所述上行传输调度请求发送的上行IoT帧，包括：
获取上行接收信号，所述上行接收信号包含所述IoT终端发送的上行IoT帧；
对所述上行接收信号去除循环前缀CP，并进行傅立叶变换FFT，得到频域接收信号；
获取所述频域接收信号中所述RU对应的子载波上的信号，得到IoT频域信号；
对所述IoT频域信号进行频域均衡、傅立叶反变换IFFT，以及解调解码处理，得到所述网络侧设备与所述IoT终端之间的上行数据。
结合第八方面或者第八方面的第一种实现方式，在第二种实现方式中，所述发送单元，具体采用如下方式向IoT终端发送上行传输调度请求：
通过下行数据帧发送所述上行传输调度请求；
所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述下行数据帧包括的数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。
结合第八方面或者第八方面的上述任一种实现方式，在第三种实现方式中，所述IoT前导传输的所述上行IoT帧的物理层控制信息包括以下序列之一或任意组合：
用于所述网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列；
用于所述网络侧设备获取解调所述上行IoT帧所需的信道估计的训练序列。
本发明实施例提供的IoT通信方法、网络侧设备及IoT终端，WLAN数据帧 包括的数据字段在频域上对应的子载波资源，包括有用于传输网络侧设备与IoT终端之间的下行数据或上行数据的RU，以及用于传输网络侧设备与STA之间的下行数据或上行数据的RU，故使得IoT终端与STA之间可共享WLAN网络中的数据帧进行数据的发送或接收，进而使得WLAN的网络侧设备可以调度IoT终端，降低IoT通信过程中出现冲突的风险。
附图说明
图1为WLAN网络架构示意图；
图2为802.11ax物理层数据帧的分组结构；
图3为802.11ax数据帧的数据字段在频域上对应的子载波资源划分示意图；
图4为本发明实施例提供的数据帧结构示意图；
图5为本发明实施例提供的第一IoT通信方法实现流程图；
图6为本发明实施例提供的下行数据帧结构示意图；
图7为本发明实施例提供的确定传输IoT数据子载波的示意图；
图8为本发明实施例提供的基于OFDM方式的数据字段生成方法；
图9为本发明实施例提供的基于OFDM方式的IoT终端获取下行数据过程示意图；
图10为本发明实施例中提供的基于单载波方式的数据字段生成方法；
图11为本发明实施例提供的基于单载波方式的IoT终端获取下行数据过程示意图；
图12为本发明实施例提供的下行IoT帧时分复用的结构示意图；
图13为本发明实施例提供的第二IoT通信方法的实现流程图；
图14为本发明实施例提供的第三IoT通信方法的实现流程图；
图15为本发明实施例提供的上行数据帧的结构示意图；
图16为本发明实施例提供上行数据帧的另一结构示意图；
图17为本发明实施例提供的上行数据传输的物理层帧结构示意图；
图18为本发明实施例提供的上行数据传输的另一物理层帧结构示意图；
图19为本发明实施例提供的基于OFDM方式发送上行IoT帧的过程示意图；
图20为本发明实施例提供的基于单载波方式发送上行IoT帧的过程示意图；
图21为本发明实施例提供的上行单载波符号与802.11ax的OFDM符号长度相同的示意图；
图22为本发明实施例提供的上行IoT帧时分复用的结构示意图；
图23为本发明实施例提供的第四IoT通信方法实现流程图；
图24为本发明实施例提供的网络侧设备接收上行数据帧过程示意图；
图25为本发明实施例提供的网络侧设备接收上行数据过程示意图；
图26为本发明实施例提供的基于OFDM的IoT帧的结构示意图；
图27为本发明实施例提供的基于单载波的IoT帧的结构示意图；
图28为本发明实施例提供的第一网络侧设备的结构示意图；
图29为本发明实施例提供的第一网络侧设备的另一结构示意图；
图30为本发明实施例提供的第一IoT终端的结构示意图；
图31为本发明实施例提供的第一IoT终端的另一结构示意图；
图32为本发明实施例提供的第二IoT终端的结构示意图；
图33为本发明实施例提供的第二IoT终端的另一结构示意图；
图34为本发明实施例提供的第二网络侧设备的结构示意图；
图35为本发明实施例提供的第二网络侧设备的另一结构示意图；
图36为本发明实施例提供的通信系统构成示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚地描述。
本发明实施例提供的IoT通信方法，可应用于图1所示的无线局域网 (Wireless local Access Network，WLAN)的网络架构中。图1中接入点(Access Point，AP)等WLAN网络设备负责与多个站点(Station，STA)等WLAN设备进行双向通信，即AP可向STA发送下行数据，如图1中，AP可向STA1和STA2发送下行数据；AP也可接收来自STA的上行数据，如图1中，AP可接收来自STA3发送的上行数据。
WLAN支持IEEE 802.11标准组织提出的802.11a、802.11n、802.11ac以及802.11ax标准，本发明实施例以下为描述方便，以WLAN支持的802.11ax标准为例进行说明。需要说明的是，本发明实施例以下涉及到的802.11ax，即指WLAN。802.11ax支持正交频分复用(Orthogonal Frequency-Division Multiplexing，OFDM)技术，OFDMA将宽带信道在频域划分为多个彼此正交的子载波，并为不同的用户分配不同的子载波，从而实现多个用户的正交复用传输。
本发明实施例中可使IoT终端与STA频分复用802.11ax物理层数据帧在频域上对应的子载波资源，以在802.11ax中实现支持IoT。
图2所示为802.11ax物理层数据帧的分组结构，如图2所示，802.11ax物理层数据帧包括传统前导，HEW前导和数据段。802.11ax物理层数据帧最开始的部分为传统前导，最后为数据字段，传统前导和数据字段之间为802.11ax协议特定的前导即HEW前导。传统前导包括传统短训练字段(Legacy Short Training field，L-STF)、传统长训练字段(Legacy Long Training field，L-LTF)和传统信令字段(Legacy Signal field，简称L-SIG)组成的字段，HEW前导包括重复的传统信令字段(Repeated Legacy Signal field，RL-SIG)、高效率信令A字段(High Efficiency Signal-A field，HE-SIG-A)、高效率信令B字段(High Efficiency Signal-B field，HE-SIG-B)、高效率短训练字段(High Efficiency Short Training field，HE-STF)和高效率长训练字段(High Efficiency Long Training field，HE-LTF)等字段。其中，数据字段用于数据传输；L-SIG、RL-SIG、HE-SIG-A和HE-SIG-B等字段分别用于传输不同类型的物理层信令；L-STF、L-LTF、HE-STF和HE-LTF等字段则主要用于定时和频率同步、自动 增益控制与信道估计等。
802.11ax的物理层数据帧包括的数据字段在频域上对应的子载波资源划分为至少一个资源单元(Resource Unit，RU)。以20MHz信道为例，20MHz信道在频域上对应256个子载波资源，如图3所示，256个子载波资源分别编号为-128、-127、…、126、127，其中，位于中间位置的子载波，即编号为-1、0、1的子载波，称为直流子载波，由于这3个子载波易受收发系统的直流偏移的影响，因此不用于数据传输。位于两个边缘位置处的子载波，即左边编号为-128到-123共6个子载波，以及右边编号为123到127共5个子载波，称为保护子载波。保护子载波用于降低发射信号的带外泄漏，避免对相邻信道产生干扰，因此也不用于数据传输。换言之，20MHz信道中可用于数据传输的子载波，为编号为-122到-2的子载波、以及编号为2到122的子载波，共242个子载波。这242个可用于数据传输的子载波，进一步划分为包含不同子载波数的RU，例如包含26、52、106、242个子载波的RU，因此，20MHz信道中最多可以分别有9个包含26个子载波的RU、4个包含52个子载波的RU、2个包含106个子载波的RU、和1个包含242个子载波的RU，如图3所示。类似地，40MHz信道中最多可以有18个包含26个子载波的RU、8个包含52个子载波的RU、4个包含106个子载波的RU、2个包含242个子载波的RU，以及1个包含484个子载波的RU。80MHz信道中最多可以有37个包含26个子载波的RU、16个包含52个子载波的RU、8个包含106个子载波的RU、4个包含242个子载波的RU、2个包含484个子载波的RU和1个包含996个子载波的RU。
本发明实施例中IoT终端与STA频分复用802.11ax物理层数据帧的数据字段在频域上对应的子载波资源。本发明实施例中802.11ax物理层数据帧的数据字段在频域上对应的子载波资源包括IoT-RU和非IoT-RU，所述IoT-RU用于传输网络侧设备与所述IoT终端之间的下行数据或上行数据；所述非IoT-RU用于传输网络侧设备与所述STA之间的下行数据或上行数据。
进一步的，本发明实施例中802.11ax的物理层数据帧包括的传统前导和 HEW前导并不与IoT通信频分复用，即所述传统前导和所述HEW前导仍用于网络侧设备与STA之间的通信。
图4所示为本发明实施例提供的IoT终端与STA复用802.11ax物理层数据帧数据字段在频域上对应的子载波资源，进行数据传输的数据帧结构示意图。图4中，所述IoT-RU用于传输AP与所述IoT终端之间的下行数据或上行数据；所述非IoT-RU用于传输AP与所述STA之间的下行数据或上行数据。
本发明实施例应用图4所述的数据帧结构进行IoT通信，可实现在802.11ax中支持IoT终端与网络侧设备的通信，即可以实现网络侧设备对IoT通信的调度与协调，从而避免IoT终端之间的冲突，以及IoT终端与WLAN设备之间的冲突。
本发明实施例以下将对如何实现在802.11ax中支持IoT终端与网路侧设备的通信，进行具体的说明。
图5所示为本发明实施例提供的第一IoT通信方法实现流程图，图5中所示方法的执行主体为网络侧设备，该网络侧设备例如可以是AP，本发明实施例不做限定。如图5所示，本发明实施例提供的第一IoT通信方法实现流程图包括：
S101：网络侧设备确定进行下行数据传输的终端设备。
本发明实施例中不同于传统技术中网络侧设备将支持802.11ax的STA确定为进行下行数据传输的终端设备，本发明实施例中网络侧设备还可将IoT终端终端确定为进行下行数据传输的终端设备，即网络侧设备确定的进行下行数据传输的终端设备可以是支持802.11ax的STA，也可以是IoT终端，换言之，本发明实施例中确定的进行下行数据传输的终端设备可以包括支持802.11ax的STA和IoT终端，也可以仅包括IoT终端。
需要说明的是，本发明实施例中所述下行数据传输可指由网络侧设备发送下行数据，并由终端设备接收下行数据的通信过程。
S102：所述网络侧设备发送下行数据帧。
本发明实施例中所述网络侧设备确定了进行下行数据传输的终端设备 后，可发送下行数据帧。
图6所示为本发明实施例涉及的下行数据帧结构示意图，图6所示的下行数据帧包括传统前导、HEW前导和数据字段。其中，图6所示的所述传统前导包括如图2所示的L-STF、L-LTF和L-SIG等字段，图6所示的HEW前导包括如图2所示的RL-SIG、HE-SIG-A、HE-SIG-B、HE-STF和HE-LTF等字段，即本发明实施例涉及的下行数据帧包括的传统前导和HEW前导与802.11ax中的传统前导和HEW前导的功能与结构相同，都是用于网络侧设备与STA之间的通信。
本发明实施例图6所示的下行数据帧包括的数据字段不同于图2所示的802.11ax中数据帧结构的数据字段，本发明实施例图6所示的下行数据帧中涉及的所述数据字段在频域上对应的子载波资源包括有用于向所述IoT终端发送下行IoT帧的至少一个RU。
本发明实施例中所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据。
本发明实施例中网络侧设备确定的终端设备在包括STA的情况下，所述数据字段在频域上对应的子载波资源还包括不同于用于传输IoT下行数据帧的所述RU的至少一个其它RU，所述至少一个其它RU用于传输所述网络侧设备与所述STA之间的下行数据。
本发明实施例以下为描述方便，将用于传输IoT下行数据帧的所述RU称为第一RU，将用于传输所述网络侧设备与所述STA之间的下行数据的RU称为第二RU。本发明实施例中，所述第一RU，相当于图4中的IoT-RU，用于向所述IoT终端发送下行IoT帧。所述第二RU，相当于图4中的非IoT-RU，用于向STA发送所述网络侧设备与所述STA之间的下行数据。
本发明实施例图6所示的第一RU发送的下行IoT帧，包括IoT前导和IoT数据字段，所述IoT前导包括用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据。
本发明实施例中，所述IoT前导传输的所述下行IoT帧的物理层控制信息包括以下序列之一或任意组合：
用于IoT终端获取所述下行IoT帧的定时和频率同步的同步序列；
用于IoT终端获取解调所述下行IoT帧所需的信道估计的训练序列。
本发明实施例中在数据字段的第一RU中发送所述下行IoT帧，使得IoT终端可以解析所述下行IoT帧中的前导部分，获取IoT终端定时同步、频率同步以及信道估计的信息，无需解析802.11ax的前导部分，即IoT终端无需支持20/40/80MHz等大宽带，有效支持带宽受限的窄带IoT终端，保证了IoT设备的低复杂度，低功耗的要求。
本发明实施例提供的上述IoT下行通信方法，网络侧设备确定进行数据传输的终端设备包括IoT终端，即网络侧设备可向IoT终端发送下行数据，实现了网络侧设备对IoT终端的调度和协调。进一步的，本发明实施例中网络侧发送的下行数据帧中的传统前导和HEW前导与802.11ax中的前导采用相同的结构，使得STA可以通过接收本发明实施例中网络侧发送的下行数据帧中的传统前导和HEW前导，接受网络侧设备对STA的调度和协调，因此不会与IoT终端竞争信道，避免STA等WLAN设备与IoT终端发生冲突。本发明实施例中网络侧发送的下行数据帧中的数据字段被IoT终端和STA频分复用，使得STA和IoT终端进行下行传输过程中，可共享WLAN信道资源，彼此不会产生干扰。
本发明实施例以下将对网络侧设备，通过所述第一RU向所述IoT终端发送下行IoT帧的实现过程进行具体说明。
第一种实现方式：网络侧设备基于OFDM方式，通过所述第一RU向所述IoT终端发送下行IoT帧。
IoT设备并不能直接接收802.11ax中的20MHz等大带宽的下行接收信号，而是通过接收通道的模拟滤波器，滤除其下行接收信号中第一RU带外的802.11ax信号，即只接收该第一RU带内的IoT信号。故，本发明实施例中为避免第一RU带外的802.11ax信号对第一RU带内的IoT信号的干扰，将所述 第一RU两个边缘位置处设定数量的子载波作为保护子载波，将所述第一RU中间位置处设定数量的子载波作为直流子载波，所述保护子载波和所述直流子载波均不用于下行IoT帧的数据传输，通过除所述保护子载波和所述直流子载波之外的、所述第一RU包含的其它子载波，向所述IoT终端发送下行IoT帧。
例如，当使用包含26个子载波的RU作为第一RU时，只使用其中16个子载波用于IoT数据传输，如图7所示，若将包含26个子载波的第一RU的子载波从左到右依次按-13、-12…11、12编号，则可以将编号为-13、-12、-11、-10的子载波，以及编号为10、11、12的子载波作为保护子载波。将编号为-1、0、1的子载波作为直流子载波。类似地，当使用包含52个子载波的RU作为IoT-RU时，可以只使用其中的38个用于IoT数据传输，若将包含52个子载波的RU的子载波从左到右依次按-26、-25…24、25编号，则可以将编号为-26到-21的6个子载波，以及编号为21到25的5个子载波作为IoT保护子载波，而编号为-1、0、1的子载波作为IoT直流子载波。
本发明实施例中，所述下行数据帧中包括的数据字段，可采用如图8所示的方法生成，图8中，所述网络侧设备将所述网络侧设备与所述IoT终端之间的下行数据，图8所述为IoT下行数据，进行编码调制，得到IoT下行调制符号。得到IoT下行调制符号后，将所述IoT下行调制符号映射到所述第一RU包含的子载波上，即所述IoT下行调制符号在数据字段中的传输位置位于所述第一RU包含的子载波所处位置。所述网络侧设备将所述网络侧设备与所述STA之间的下行数据，图8中所示为802.11ax下行数据，进行编码调制，得到WLAN下行调制符号。得到WLAN下行调制符号后，将所述WLAN下行调制符号映射到第二RU包含的子载波上，即所述WLAN下行调制符号在数据字段中的传输位置位于所述第二RU包含的子载波所处位置处。所述网络侧设备对包含所述第一RU对应子载波和所述第二RU对应子载波的频域信号，进行傅立叶反变换(Inverse Fast Fourier transform，IFFT)，并附加循环前缀(Cyclic Prefix,CP)，生成IoT与WLAN混合传输的下行基带信号。
相应的，IoT终端可通过接收通道从包含网路侧设备发送的下行数据帧的下行接收信号中获取IoT下行信号。本发明实施例中所述IoT终端的接收通道的带宽不超过所述第一RU的带宽。所述IoT终端的接收通道采用的载波频率设置为f0+fr，其中，f0为所述下行接收信号的载波频率，fr为所述第一RU的中心频点相对于零频(例如图7中的编号为0的子载波对应的频点)的频率差。本发明实施例中下行接收信号经过IoT终端的设置为上述载波频率的接收通道后，滤除了第一RU带外的WLAN下行信号，故所述IoT终端可对滤除剩下的所述IoT下行信号进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据。
图9所示为本发明实施例提供的基于OFDM方式，IoT终端对IoT下行信号进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据的过程示意图。图9中，所述IoT终端对所述IoT下行信号的每个OFDM符号，去除CP，并进行上采样以及相应点数的FFT，得到映射到所述第一RU包含的子载波上的IoT调制信号。例如，20MHz、40MHz、80MHz信道带宽分别采用256点、512点、1024点的FFT，得到映射到所述第一RU包含的子载波上的IoT调制信号。得到IoT调制信号后，所述IoT终端对所述IoT调制信号进行解调解码，得到所述网络侧设备与所述IoT终端之间的下行数据。
第二种实现方式：网络侧设备基于单载波(Single Carrier，SC)方式，通过所述第一RU向所述IoT终端发送下行IoT帧。
本发明实施例中为避免第一RU带外的802.11ax信号对第一RU带内的IoT信号的干扰，与基于OFDM方式的下行IoT帧传输类似，可将所述第一RU两个边缘位置处设定数量的子载波作为保护子载波。与基于OFDM方式的下行IoT帧传输易受接收机直流偏移的影响不同，单载波方式中受接收机直流偏移的影响较小，因此不需要保留直流子载波，故本发明实施例可在除所述保护子载波之外的、所述第一RU包含的其它子载波所对应的频带上，以单载波方式向所述IoT终端发送下行IoT帧。
例如，当使用包含26个子载波的RU作为第一RU时，可使用其中20个 子载波用于单载波方式的下行IoT帧传输，而将编号为-13、-12、-11，以及编号为10、11、12的供6个子载波作为保护子载波。当使用包含52个子载波的RU作为第一RU时，可以只使用其中的42个子载波用于单载波方式的下行IoT帧传输，而将编号为-26到-22，以及编号为21到25的共10个子载波作为保护子载波。
本发明实施例中，所述下行数据帧中包括的数据字段，可采用如图10所示的方法生成，图10中，所述网络侧设备将所述网络侧设备与所述STA之间的下行数据，图10中所示为802.11ax的下行数据，进行编码调制，得到WLAN下行调制符号。得到WLAN下行调制符号后，将所述WLAN下行调制符号映射到所述第二RU包含的子载波上，即所述WLAN下行调制符号在数据字段中的传输位置位于所述第一RU包含的子载波所处位置处。所述网络侧设备对包含所述第二RU对应子载波的频域信号进行IFFT，并附加CP，生成WLAN下行基带信号。所述网络侧设备将所述网络侧设备与IoT终端之间的下行数据，图10所示为IoT下行数据进行编码调制，并附加CP，生成IoT下行单载波符号。所述网络侧设备对所述IoT下行单载波符号进行波形成型滤波，得到IoT下行基带信号。所述网络侧设备对所述IoT下行基带信号进行变频，即图10所示的对IoT下行基带信号乘
Figure PCTCN2016088231-appb-000001
得到IoT下行带通信号。其中，t为时间变量，所述IoT下行带通信号的中心频点为fr，fr为所述第一RU的中心频点相对于零频的频率差。所述网络侧设备将所述IoT下行带通信号和所述WLAN下行基带信号相加，得到IoT与WLAN混合传输的下行基带信号。
相应的，本发明实施例中IoT终端可通过接收通道从包含网路侧设备发送的下行数据帧的下行接收信号中获取IoT下行信号。本发明实施例中所述IoT终端的接收通道的带宽不超过所述第一RU的带宽。所述IoT终端的接收通道采用的载波频率设置为f0+fr，其中，f0为所述下行接收信号的载波频率，fr为所述第一RU的中心频点相对于零频(例如图7中的编号为0的子载波对应的频点)的频率差。本发明实施例中下行接收信号经过IoT终端的设置为上述载波频率的接收通道后，滤除了第一RU带外的WLAN下行信号，故所 述IoT终端可对滤除剩下的所述IoT下行信号进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据。
图11所示为本发明实施例提供的基于单载波方式下，IoT终端对IoT下行信号进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据的过程示意图。图11中，所述IoT终端对所述IoT下行信号的每个单载波符号，去除CP，并进行频域均衡，得到映射到所述第一RU所对应的频带上的IoT调制信号。所述IoT终端对所述IoT调制信号进行解调解码，得到所述网络侧设备与所述IoT终端之间的下行数据。
本发明上述实施例中网络侧设备采用频域处理的方式，即可同时对支持IoT和802.11ax信号进行接收和发送，避免采用双模方式，降低了网络侧设备实现IoT通信的实现复杂度。
需要说明的是，本发明实施例中单载波方式传输所使用的IoT下行单载波调制符号可采用频移键控(Frequency Shift Keying，FSK)、差分相移键控(Differential Phase Shift Keying，DPSK)、四相相移键控(Quadrature Phase Shift Keying，QPSK)、高斯频移键控(Gaussian frequency Shift Keying，GFSK)等恒包络调制方式，也可以采用正交幅度调制(Quadrature Amplitude Modulation，QAM)等较高阶的调制，所采用的波形成型滤波器，典型地可以采用高斯滤波器、平分根升余弦滤波器等滤波器。
可选的，在具体实施本发明实施例过程中，本发明实施例中假设所述IoT下行单载波符号除CP外，包括K个调制符号，则每个调制符号的周期为T1＝T0/K；其中，K为不超过所述第一RU包含的子载波数的正整数，T1为每个调制符号的周期，T0为所述WLAN下行基带信号的OFDM符号的长度。本发明实施例中每个IoT下行单载波调制符号的带宽(约1/T1)不超过所使用的第一RU的带宽，例如第一RU为包含26个子载波的RU时，即有：
Figure PCTCN2016088231-appb-000002
因此K≤26，即每个IoT下行单载波符号除CP外最多包括26个调制符 号。同样地，第一RU为包含52个子载波的RU时，每个IoT下行单载波符号除CP外最多包括52个调制符号。
可选的，在具体实施本发明实施例过程中，由于IoT终端支持的带宽较小，典型的第一RU为包含26或52个子载波的RU，故本发明实施例中可在每个20MHz、40MHz或80MHz信道中的所述第一RU中，设置至少一个基本RU，IoT终端首先使用基本RU与网络侧设备进行通信。
具体地，IoT终端首先在下行数据帧的基本RU上接收IoT下行信号，从而与AP等网络侧设备进行上行或下行通信，网络侧设备可以在所述基本RU上发送信道指示信息，其中，所述信道指示信息用于指示IoT终端由所述基本RU切换到除所述基本RU之外的其它用于发送下行IoT帧的RU上。
通常，单个IoT终端传输的数据量比较小，但是IoT中部署的IoT终端数量很大，因此一个IoT-RU，即第一RU需要同时支持多个IoT终端的通信。为此，本发明实施例中可对IoT数据字段进一步划分为时分复用(Time Division Multiplexing，TDM)的结构，即所述IoT数据字段包括至少一个子帧。
本发明实施例中，所述IoT数据字段包含至少两个IoT终端的下行数据，每个IoT终端的下行数据占用至少一个子帧，或者占用至少一个子帧的至少一个时隙，或者占用至少一个子帧和至少一个子帧的至少一个时隙。例如，图12所示，IoT数据字段等分为P个子帧，每个子帧还可以进一步分为Q个时隙，当然也可以不划分时隙，这样，不同的IoT终端可使用IoT数据字段的不同的子帧或不同时隙，即通过时分多址(Time Division Multiple Access，TDMA)方式使用一个IoT-RU，即可实现网络侧设备与多个IoT终端之间的通信，满足IoT通信中，IoT终端处理数据速率低，数量大且分布广，需要覆盖较远范围的IoT终端，并支持大量IoT终端的多用户复用的要求。
OFDMA信号在时域上的最小单位是OFDM符号，802.11ax中引入了1倍(简写为1x)、2倍(简写为2x)和4倍(简写为4x)等不同时间长度的OFDM符号，不包括循环前缀(Cyclic Prefix,CP)它们的长度分别为3.2微 秒、6.4微秒和12.8微秒。802.11ax中1x和2x符号长度主要用于前导，例如，为与802.11a、802.11n、802.11ac等版本后向兼容，传统前导、RL-SIG、HE-SIG-A和HE-SIG-B采用1x符号长度的OFDM符号，20MHz信道带宽情况下采用64点的FFT进行处理，在频域上对应64个子载波。较长的OFDM符号CP开销较小，因此，为提高效率数据字段采用4x符号长度，20MHz信道带宽情况下采用256点的FFT进行处理，在频域上对应256个子载波。
需要说明的是，本发明实施例中，为便于网络侧设备对IoT与WLAN混合传输的下行基带信号的联合发送和接收，在下行数据帧包括的数据字段中，IoT下行调制符号的OFDM符号长度与802.11ax的OFDM符号长度相同，即CP长度相同。当IoT下行数据帧采用OFDM方式传输时，本发明实施例中IoT下行调制符号长度与802.11ax的的OFDM符号的长度相同，即IoT下行调制符号与802.11ax的OFDM符号上边界对齐，即4x符号长度。
进一步需要说明的是，当IoT下行数据帧采用单载波方式传输时，IoT的单载波符号与802.11ax数据字段OFDM符号可以不用对齐，即IoT的单载波符号可以选择与802.11ax数据字段OFDM符号不同的长度，且CP的长度也可以不同。
本发明上述实施例提供的IoT通信方法，网络侧设备确定进行下行数据传输的终端设备包括IoT终端，网络侧设备发送下行数据帧，下行数据帧中采用下行IoT帧频分复用802.11ax中数据帧的数据字段的方式，使得网络侧设备可以对IoT终端进行调度和协调，降低IoT传输受干扰的风险。下行数据帧传输过程中，STA解析传统前导和HEW前导，获取定时同步、频率同步以及信道估计的信息，IoT终端解析所述下行IoT帧中的前导部分，获取IoT终端定时同步、频率同步以及信道估计的信息，无需解析802.11ax的前导部分，使得IoT终端与STA之间频分共享802.11ax中信道资源过程中，彼此不会产生干扰。并且采用上述方式，IoT终端无需支持20/40/80MHz等大宽带，有效支持带宽受限的窄带IoT终端，保证了IoT设备的低复杂度，低功耗的要求。
基于上述实施例提供的网络侧设备进行下行数据帧发送的实施方法，本 发明实施例提供了另一IoT通信方法。
图13所示为本发明实施例提供的第二IoT通信方法的实现流程图，图13所示的方法流程的执行主体为IoT终端，如图13所示，该IoT通信方法的实施过程包括：
S201：IoT终端从下行接收信号中获取下行IoT帧。
本发明实施例中所述下行接收信号包含网络侧设备发送的下行数据帧。所述下行数据帧包括传统前导、HEW前导和数据字段，所述传统前导和所述HEW前导用于网络侧设备与站点STA之间的通信，所述数据字段在频域上对应的子载波资源包括至少一个RU，所述至少一个RU用于发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据。
本发明实施例中网络侧设备发送的下行数据帧的数据字段在频域上对应的子载波资源还可包括不同于用于传输IoT下行数据帧的所述RU的至少一个其它RU，所述至少一个其它RU用于传输所述网络侧设备与所述STA之间的下行数据。
本发明实施例以下为描述方便，将用于传输IoT下行数据帧的所述RU称为第一RU，将用于传输所述网络侧设备与所述STA之间的下行数据的RU称为第二RU。本发明实施例中，所述第一RU用于所述网络侧设备向所述IoT终端发送下行IoT帧，所述第二RU用于所述网络侧设备向所述STA发送所述网络侧设备与所述STA之间的下行数据。
本发明实施例中，所述IoT终端的接收通道的带宽不超过所述第一RU的带宽。所述IoT终端的接收通道采用的载波频率为f0+fr，其中，f0为所述下行接收信号的载波频率，fr为所述第一RU的中心频点相对于零频的频率差。
本发明实施例中下行接收信号包含的下行数据帧的具体结构，可参阅上述实施例中有关图6的描述，在此不再赘述。
S202：IoT终端对所述下行IoT帧进行处理，得到所述网络侧设备与所述 IoT终端之间的下行数据。
本发明实施例中IoT终端对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据的具体实施过程，可参阅上述实施例中图9和图11的相关描述，在此不再赘述。
本发明上述实施例提供的IoT通信方法，IoT终端接收的IoT下行信号包含网络侧设备发送的下行数据帧，下行数据帧中下行IoT帧和802.11ax数据帧的数据字段频分复用，使得IoT终端受网络侧设备的调度和协调，降低IoT传输受干扰的风险。下行数据帧传输过程中，STA解析传统前导和HEW前导，获取定时同步、频率同步以及信道估计的信息，IoT终端解析所述下行IoT帧中的前导部分，获取IoT终端定时同步、频率同步以及信道估计的信息，无需解析802.11ax的前导部分，使得IoT终端与STA之间频分共享802.11ax中信道资源过程中，彼此不会产生干扰。并且采用上述方式，IoT终端无需支持20/40/80MHz等大宽带，有效支持带宽受限的窄带IoT终端，保证了IoT设备的低复杂度，低功耗的要求。
本发明以上实施例主要是针对AP等网络侧设备进行下行数据发送，IoT终端进行下行数据接收的过程进行说明。本发明实施例以下将以应用本发明实施例提供的IoT通信方式，实现IoT终端进行上行数据发送，AP等网络侧设备进行上行数据接收的过程进行说明。
图14所示为本发明实施例提供的第三IoT通信方式实现流程图，图14所示的方法流程的执行主体为IoT终端，IoT终端进行上行数据发送，如图14所示，包括：
S301：IoT终端接收网络侧设备发送的上行传输调度请求。
本发明实施例中，IoT终端向AP等网络侧设备发送上行数据时，需要由网络侧设备下发上行传输调度请求，所述上行传输调度请求用于调度IoT终端发送上行IoT帧，进行上行数据传输。所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个RU，所述至少一个RU用于发送所述上行IoT帧。
本发明实施例中所述上行传输调度请求中可包括被调度进行上行数据传输的IoT终端的标识符、分配给所述进行上行数据传输的IoT终端的上行传输资源以及码调制方式等信息。被调度进行上行数据传输的IoT终端通过接收所述上行传输调度请求，获知网络侧设备是否允许该接收到上行传输调度请求的IoT终端发送上行数据，以及获取传输上行数据所使用的传输资源、传输格式等信息，以便被调度进行上行数据传输的IoT终端根据这些信息发送上行数据。
本发明实施例中上行传输调度请求可通过下行数据帧的形式发送，所述下行数据帧包括传统前导、HEW前导和数据字段，所述传统前导和所述HEW前导用于网络侧设备与站点STA之间的通信，所述数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。本发明实施例中也可将用于发送所述上行传输调度请求的RU称为第一RU。
需要说明的是，本发明实施例中网络侧设备发送的上行传输调度请求可以是一个单独的下行触发帧，所述下行触发帧可采用图6所示的下行数据帧的帧结构。网络侧设备还可以通过发送下行数据与下行触发帧来调度IoT终端进行上行数据传输，即第一RU除了发送上行传输调度请求外，也可用于网络侧设备向IoT终端发送下行数据，该下行数据对应的IoT终端，可以是被调度进行上行数据传输的IoT终端，也可以是其它的IoT终端。
S302：所述IoT终端依据所述上行传输调度请求，发送上行IoT帧。
本发明实施例中IoT终端发送的所述上行IoT帧，包括IoT前导和IoT数据字段，所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的上行数据。
所述IoT前导传输的所述上行IoT帧的物理层控制信息包括以下序列之一或任意组合：用于网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列、用于网络侧设备获取解调所述上行IoT帧所需的信道估计的训练序列。
具体的，本发明实施例中上行IoT帧位于上行数据帧的数据字段，该上 行数据帧包括传统前导、HEW前导和数据字段，所述传统前导和所述HEW前导用于网络侧设备与站点STA之间的通信，所述数据字段在频域上对应的子载波资源包括第三RU。本发明实施例中所述上行IoT帧即位于第三RU位置处，换言之，本发明实施例中通过第三RU发送所述上行IoT帧。
因此，本发明实施例中所述上行传输调度请求中还包括IoT终端发送的所述上行IoT帧的位置信息，所述位置信息包括该上行数据帧的数据字段的起始时刻，以及发送所述上行IoT帧的第三RU的标识。这样，IoT终端就能根据所述上行传输调度请求，从该上行数据帧的数据字段的起始时刻在第三RU上从发送所述上行IoT帧。
本发明实施例提供的上行数据帧的结构可参阅图15和图16所示。图15和图16中，第三RU即为用于传输所述网络侧设备与IoT终端之间的上行数据的RU，也可称为IoT-RU。非IoT-RU即为用于传输所述网络侧设备与STA之间的上行数据的RU。
图15所示的上行数据帧结构中，数据帧中的数据字段中的子载波资源由IoT终端与STA频分复用。上行数据帧包括传统前导、HEW前导和数据字段。其中，图15所示的所述传统前导包括如图2所示的L-STF、L-LTF和L-SIG等字段，图15所示的HEW前导包括如图2所示的RL-SIG、HE-SIG-A、HE-SIG-B、HE-STF和HE-LTF等字段，即本发明实施例涉及的上行数据帧包括的传统前导和HEW前导与802.11ax中的传统前导和HEW前导的功能与结构相同，都是用于网络侧设备与STA之间的通信。
本发明实施例图15所示的上行数据帧包括的数据字段不同于图2所示的802.11ax中数据帧结构的数据字段，本发明实施例图15所示的上行数据帧中涉及的所述数据字段在频域上对应的子载波资源包括第三RU和非IoT-RU；所述第三RU，用于发送上行IoT帧。所述非IoT-RU用于STA向所述网络侧设备发送所述网络侧设备与所述STA之间的上行数据。
本发明实施例位于第三RU上的上行IoT帧，包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据 字段用于传输所述网络侧设备与所述IoT终端之间的上行数据。
所述IoT前导传输的所述上行IoT帧的物理层控制信息包括以下序列之一或任意组合：
用于网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列；
用于网络侧设备获取解调所述上行IoT帧所需的信道估计的训练序列。
本发明实施例中位于第三RU中的所述上行IoT帧，网络侧设备通过解析所述上行IoT帧中的前导部分，获取与IoT终端的定时同步、频率同步或者信道估计的信息，即IoT终端只需发送窄带的上行IoT帧，无需支持20/40/80MHz等大宽带，因此本发明可以有效支持带宽受限的窄带IoT终端，保证了IoT设备的低复杂度，低功耗的要求。
图16所示的上行数据帧结构，数据字段的子载波资源全部用于传输上行IoT帧。当数据字段的全部RU用于传输上行IoT帧时，上行数据帧可以不包括传统前导和HEW前导，数据字段中包括第三RU，如图16所示。
本发明实施例中IoT终端接收到上行触发请求，即以下行数据帧结构发送的下行数据帧后，经过设定的时间间隔后开始上行数据帧的传输，所述设定的时间间隔应大于被调度的IoT终端解调和解码所述下行数据帧，以及准备上行数据帧的传输(如上下行中射频通道的转换等)所需的时间。
本发明实施例采用图15所示的上行数据帧进行上行IoT帧发送对应的上行数据传输的物理层帧结构如图17所示。采用图16所示的上行数据帧进行上行IoT帧发送对应的上行数据传输的物理层帧结构如图18所示。
本发明实施例以下将对IoT终端，通过上行数据帧中的第三RU发送上行IoT帧的实现过程进行具体说明。
第一实现方式：IoT终端基于OFDM方式，通过所述第三RU发送上行IoT帧。
本发明实施例中为避免第三RU带外的802.11ax信号对第三RU带内的IoT信号的干扰，所述IoT终端，具体采用如下方式，发送所述上行IoT帧：
A：将所述第三RU两个边缘位置处设定数量的子载波作为保护子载波。
B：将所述第三RU中间位置处设定数量的子载波作为直流子载波。
C、在除所述保护子载波和所述直流子载波之外的、所述第三RU包含的其它子载波上，向所述网络侧设备发送上行IoT帧。
可选的，本发明实施例中可采用图19所示的方法，通过所述第三RU发送所述上行IoT帧。图19中，所述IoT终端对所述网络侧设备与IoT终端之间的上行数据，图19所示为IoT上行数据，进行编码调制，得到IoT上行调制符号，并将所述IoT上行调制符号映射到所述第三RU包含的子载波上。所述IoT终端对包含所述第三RU对应子载波的频域信号，进行IFFT以及下采样，并附加CP，得到第一IoT上行基带信号。将所述第一IoT上行基带信号，通过上行发射通道发送。
本发明实施例中发射第一IoT上行基带信号的所述上行发射通道的载波频率为f0+fr，其中，f0为传输第三RU所在的上行数据帧的信道的载波频率，fr为所述第三RU的中心频点相对于零频的频率差。
第二种方式：IoT终端基于单载波方式，通过所述第三RU发送上行IoT帧。
本发明实施例中为避免第三RU带外的802.11ax信号对第三RU带内的IoT信号的干扰，本发明实施例中所述IoT终端具体采用如下方式，发送所述上行IoT帧：
A：所述IoT终端将所述第三RU两个边缘位置处的设定数量的子载波作为保护子载波。
B：所述IoT终端在除所述保护子载波之外的、所述第三RU包含的其它子载波所对应的频带上，以单载波方式向所述网络侧设备发送上行IoT帧。
本发明实施例中所述IoT终端可采用如图20所示的方式以单载波方式发送所述上行IoT帧。图20中，所述IoT终端对所述网络侧设备与IoT终端之间的上行数据进行编码调制，图20中所示IoT上行数据即为所述网络侧设备与IoT终端之间的上行数据，附加循环前缀，生成IoT上行单载波符号。所述IoT终端对所述IoT上行单载波符号进行波形成型滤波，得到第二IoT上行基 带信号。所述IoT终端将所述第二IoT上行基带信号，通过上行发射通道发送。
本发明实施例中，所述上行发射通道的载波频率为f0+fr，其中，f0为传输第三RU所在的上行数据帧的信道的载波频率，fr为所述第三RU的中心频点相对于零频的频率差。
本发明实施例中为了便于AP等网络侧设备对IoT信号和802.11AX信号联合接收，上行IoT帧采用单载波方式发送过程中，IoT上行单载波符号与802.11ax的OFDM符号长度相同，即所述IoT上行单载波符号和所述STA发送的WLAN上行基带信号的OFDM符号采用相同长度的CP，且所述IoT上行单载波符号和所述STA发送的WLAN上行基带信号的OFDM符号的长度相同，即IoT上行单载波符号与802.11ax的OFDM符号上边界对齐，例如可以是4x符号长度，如图21所示。
需要说明的是，本发明实施例中当上行IoT帧采用OFDM方式传输时，本发明实施例中IoT上行调制符号长度与802.11ax的OFDM符号的长度相同，即IoT上行调制符号与802.11ax的OFDM符号上边界对齐，即4x符号长度。
需要说明的是，本发明实施例图21中，IoT-RU即为用于传输IoT终端与网络侧设备之间的上行数据的第三RU，非IoT-RU即为用于传输STA与网络侧设备之间的上行数据的RU。
进一步需要说明的是，本发明实施例中IoT终端基于何种方式通过所述第三RU发送上行IoT帧，并不受限于网络侧设备发送下行IoT帧的形式。例如网络侧设备采用OFDM方式发送下行IoT帧的情况下，IoT终端可采用单载波的方式发送上行IoT帧。
可选的，本发明实施例中所述IoT上行单载波符号包括K个调制符号，每个调制符号的周期为T1＝T0/K。其中，K为不超过所述第三RU包含的子载波数的正整数，T1为每个调制符号的周期，T0为所述STA发送的WLAN上行基带信号的OFDM符号的长度。
可选的，在具体实施本发明实施例提供的IoT通信方法过程中，所述上行IoT帧包含至少两个IoT终端发送的上行IoT子帧；其中，每个IoT终端发 送的所述上行IoT子帧包括IoT前导和IoT数据字段。换言之，上行数据帧中的所述上行IoT帧包括至少一个子帧，每个IoT终端使用至少一个所述子帧发送自己的上行IoT子帧，每个IoT终端发送的上行IoT子帧包括IoT前导和IoT数据字段。例如图22所示，上行IoT帧等分为P个子帧，不同的IoT终端可使用上行IoT帧的不同的子帧，即通过TDMA方式使用一个IoT-RU，即可实现网络侧设备与多个IoT终端之间的通信，满足IoT通信中，IoT终端处理数据速率低，数量大且分布广，需要覆盖较远范围的IoT终端，并支持大量IoT终端的多用户复用的要求。
需要说明的是，本发明实施例图22所示上行IoT帧的P个子帧为等分的，在具体实施时并不限定，上行IoT帧的包括的子帧可不等分。
可选的，由于恒包络调制方法具有最小的峰值均值功率比(Peak to average Power Ratio，PAPR)，能够满足IoT终端采用低压供电，发射功率较小，需要尽可能降低上行的PAPR的要求，本发明实施例中IoT终端发送上行IoT帧过程中，可采用恒包络调制方法，例如，采用GFSK调制。
需要说明的是，本发明实施例并不限定采用恒包络调制方法，例如还可采用QAM调制方式，QAM调制方式的PAPR比恒包络调制稍大，但仍远小于OFDM方式的PAPR，可以实现较高的传输速率。
本发明实施例提供的上述IoT通信方法，IoT终端发送的上行IoT帧位于上行数据帧的第三RU上，上行数据帧中采用上IoT终端和STA频分复用802.11ax中数据帧的数据字段的方式，使得IoT终端受网络侧设备的调度和协调，降低IoT传输受干扰的风险。上行数据帧传输过程中，IoT终端只需发送窄带的上行IoT帧，并与STA之间频分复用802.11ax中的信道资源，彼此不产生干扰。采用上述方式，IoT终端无需支持20/40/80MHz等大宽带，有效支持带宽受限的窄带IoT终端，保证了IoT设备的低复杂度，低功耗的要求。
基于上述实施例提供的IoT终端进行上行数据发送的实施例，本发明实施例还提供一种IoT通信方法。图23所示为本发明实施例提供的第四IoT通信方法实现流程图，图23所示方法的执行主体为网络侧设备，如图23所示， 包括：
S401：网络侧设备向IoT终端发送上行传输调度请求。
本发明实施例中所述上行传输调度请求用于调度IoT终端发送上行IoT帧，进行上行数据传输。
本发明实施例中上行传输调度请求可通过下行数据帧的形式发送，所述下行数据帧包括传统前导、HEW前导和数据字段，所述传统前导和所述HEW前导用于网络侧设备与站点STA之间的通信，所述数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。本发明实施例中也可将用于发送所述上行传输调度请求的RU称为第一RU。
S402：所述网络侧设备获取所述IoT终端依据所述上行传输调度请求发送的上行IoT帧。
其中，所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个RU，所述至少一个RU用于发送所述上行IoT帧，本发明实施例为描述方便，将发送所述上行IoT帧的RU称为第三RU，当然也可称为IoT-RU。
所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的上行数据。
具体的，所述网络侧设备，可采用如图24所示的方式接收所述IoT终端依据所述上行传输调度请求发送的上行数据帧。图24中，所述网络侧设备获取上行接收信号，所述上行接收信号包含所述IoT终端发送的上行IoT帧。所述上行IoT帧位于上行数据帧的第三RU。所述网络侧设备对所述上行接收信号去除CP，并进行FFT，得到频域接收信号。所述网络侧设备获取所述频域接收信号中所述第三RU对应的子载波上的信号，得到IoT频域信号。所述网络侧设备对所述IoT频域信号进行频域均衡、IFFT，以及解调解码处理，得到通过所述IoT帧发送的所述网络侧设备与所述IoT终端之间的上行数据。
本发明上述实施例提供的IoT通信方法，网络侧设备通过下行数据帧向 IoT终端发送上行调度请求，下行数据帧下行IoT帧与802.11ax中数据帧的数据字段频分复用，使得网络侧设备可以对IoT终端进行调度和协调，降低IoT传输受干扰的风险。所述网络侧设备接收所述IoT终端依据所述上行传输调度请求发送的上行数据帧。上行数据帧中包括传统前导、HEW前导和数据段，所述数据段中包括有用于传输IoT终端与网络侧设备上行数据的第三RU。故本发明实施例中，IoT终端只需发送窄带的上行IoT帧，并与STA之间频分复用802.11ax的信道资源，彼此不产生干扰。并且采用上述方式，IoT终端无需支持20/40/80MHz等大宽带，有效支持带宽受限的窄带IoT终端，保证了IoT设备的低复杂度，低功耗的要求。
本发明实施例中网络侧设备发送下行数据帧，下行数据帧包括传统前导、HEW前导和数据字段。所述传统前导和所述HEW前导用于网络侧设备与STA之间的通信。所述数据字段在频域上对应的子载波资源包括第一RU和第二RU。所述第一RU用于向所述IoT终端发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导包括用所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据。所述第二RU用于向STA发送所述网络侧设备与所述STA之间的下行数据。
STA通过上述下行数据帧，解析传统前导和HEW前导，获取STA定时同步、频率同步或者信道估计等信息，并通过所述数据字段中的第二RU获取所述网络侧设备与所述STA之间的下行数据。
IoT终端通过上述下行数据帧，解析IoT前导，获取IoT终端定时同步、频率同步以及信道估计的字段，并通过所述数据字段中的第一RU获取所述网络侧设备发送的下行数据。
本发明实施例中网络侧设备还可向IoT终端发送上行传输调度请求，调度IoT终端发送上行数据。本发明实施例中网络侧设备通过上行数据帧接收上行数据，所述上行数据帧包括传统前导、HEW前导和数据字段，所述传统前导和所述HEW前导用于网络侧设备与站点STA之间的通信，所述数据字 段在频域上对应的子载波资源包括第三RU，所述第三RU用于传输所述网络侧设备与IoT终端之间的上行数据。
本发明实施例中网络侧设备可采用单载波方式接收上行数据帧，如图25所示为单载波方式下上行数据帧接收的实施过程，包括：网络侧设备采样得到的上行基带接收信号，先经过去除CP和IFFT处理变换到频域，其中，20MHz、40MHz、80MHz信道带宽分别采用256点、512点、1024点的FFT。然后经过子载波去映射操作，对非IoT-RU上的信号，进行802.11ax上行信号接收处理，从而获得802.11ax的上行数据；对IoT-RU上的信号，先进行频域均衡，然后经IFFT变换到时域，最后进行解调和解码等IoT上行信号接收处理，从而获得IoT的上行数据。需要说明的是，若采用GFSK等调制方式，则可以不进行频域均衡处理。
典型地，当频域均衡后的IoT信号的采样频率为2.5MHz时，IoT-RU为26个子载波的RU，可以采用32点的IFFT变换到时域，当频域均衡后的IoT信号的采样频率为5MHz时，IoT-RU为52个子载波的RU，可以采用64点的IFFT变换到时域。
需要说明的是，本发明实施例中IoT终端并不发送和接收上行数据帧和下行数据帧中包括的传统前导和HEW前导，传统前导和HEW前导用于网路侧设备与STA之间的通信，即下行数据帧中的传统前导和HEW前导由网络侧设备发送，上行数据帧中传统前导和HEW前导由STA发送。对于IoT设备通过接收通道的模拟滤波器，滤除IoT-RU带外的信号，接收IoT-RU带内的信号。因此，本发明上述实施例中下行数据帧的数据字段中包括的第一RU上，以及上行数据帧的数据字段中包括的第三RU上，都具有不依赖于下行数据帧中的传统前导和HEW前导的独立帧结构，本发明实施例中可将该独立的帧结构称之为IoT帧。
具体的，本发明上述实施例中涉及的IoT前导包括用于传输下行IoT帧或上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据或上行数据。下行IoT帧的所述物理层控制信息 包括用于IoT终端获取所述下行IoT帧的定时和频率同步的同步序列、或者用于IoT终端获取解调所述下行IoT帧所需的信道估计的训练序列等。上行IoT帧的物理层控制信息包括用于网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列、或者用于网络侧设备获取解调所述上行IoT帧所需的信道估计的训练序列等。换言之，本发明实施例中网络侧设备通过解析所述上行IoT帧中的前导部分，获取与IoT终端的定时同步、频率同步或者信道估计的信息，即IoT终端只需发送窄带的上行IoT帧，无需支持20/40/80MHz等大宽带，因此本发明可以有效支持带宽受限的窄带IoT终端，保证了IoT设备的低复杂度，低功耗的要求。
图26为本发明实施例中基于OFDM方式的IoT帧的一个实施例，其中，IoT-STF用于IoT定时同步、自动增益控制等。IoT-SIG用于传输IoT物理层信令。IoT-LTF1用于获得解调IoT-SIG所需的信道估计。IoT-LTF2～IoT-LTFN用于多输入多输出(Multiple Input Multiple Output，MIMO)传输时，获得解调IoT数据字段所需的MIMO信道估计。IoT数据字段用于传输IoT上行数据或IoT下行数据。对于IoT-STF所传输的同步序列的设计，可利用现有技术，本发明实施例在此不再赘述。
本发明实施例中为了覆盖较远范围的IoT设备，IoT-STF采用更长的同步序列，如IoT-STF的长度可为IoT的OFDM符号长度的2倍，即12.8×2＝25.6微秒。IoT-LTF1可以采用L-LTF类似的结构，如图26所示，其中两倍保护间隔(Double Guard Interval，DGI)是IoT的OFDM符号的CP长度的2倍，连续传输两个长训练序列(Long Training Sequence，LTS)符号，每个LTS符号的长度为12.8微秒.或者，采用更长的符号，即使用四倍保护间隔(4x Guard Interval，4GI)，IoT的OFDM符号的CP长度的4倍作为循环前缀，或使用DGI作为循环前缀。IoT-LTF2～IoT-LTFN可以采用HE-LTF类似的结构，为了覆盖较远范围的IoT设备，每个IoT-LTF2～IoT-LTFN的符号均采用IoT-LTF1相同的结构，即循环前缀采用DGI或4GI，连续传输2个或4个同样的训练符号。为保证IoT SIG的可靠传输，可以采用两相相移键控(Binary Phase Shift  Keying，BPSK)及1/2编码速率的信道编码，为了覆盖较远范围的IoT设备，IoT SIG还可以进行重复传输，即每个IoT SIG的OFDM符号均重复2次或以上的次数。
图27所示为本发明实施例基于单载波方式，提供的IoT帧的一个实施例，其中，IoT_sync传输同步序列，用于IoT定时同步、自动增益控制。IoT_sig用于传输IoT物理层信令。IoT数据字段用于传输IoT上行数据或IoT下行数据。在该实施例中，IoT_sig和IoT数据字段均采用GFSK或DPSK调制，由于这类调制不需要信道估计进行相干解调，因此IoT帧的前导没有传输用于发送参考符号的字段，因此，实施例中IoT信号的接收处理比较简单，具有低成本、低功耗的优势。
基于本发明实施例提供的第一IoT通信方法，本发明实施例提供一种网络侧设备100，如图28所示，所述网络侧设备100包括确定单元101和发送单元102，其中：
确定单元101，用于确定进行下行数据传输的终端设备，所述终端设备包括IoT终端。
发送单元102，用于发送下行数据帧。
所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段。
所述数据字段在频域上对应的子载波资源包括至少一个RU。所述RU用于向所述IoT终端发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备100与所述IoT终端之间的下行数据。
在一种实现方式中，所述终端设备还包括站点STA。
所述数据字段在频域上对应的子载波资源还包括不同于所述RU的至少一个其它RU。
所述至少一个其它RU用于传输所述网络侧设备100与所述STA之间的下行数据。
具体的，所述发送单元102，具体采用如下方式，通过所述RU向所述IoT终端发送下行IoT帧：
将所述RU两个边缘位置处设定数量的子载波作为保护子载波。
将所述RU中间位置处设定数量的子载波作为直流子载波。
通过除所述保护子载波和所述直流子载波之外的、所述RU包含的其它子载波，向所述IoT终端发送下行IoT帧。
进一步的，所述发送单元102具体采用如下方式生成下行数据帧包括的数据字段：
将所述网络侧设备100与所述IoT终端之间的下行数据，进行编码调制，得到IoT下行调制符号，并将所述IoT下行调制符号映射到所述至少一个RU包含的子载波上。
将所述网络侧设备100与所述STA之间的下行数据，进行编码调制，得到无线局域网WLAN下行调制符号，并将所述WLAN下行调制符号映射到所述至少一个其它RU包含的子载波上。
对包含所述至少一个RU对应子载波和所述至少一个其它RU对应子载波的频域信号，进行傅立叶反变换IFFT，并附加循环前缀，生成IoT与WLAN混合传输的下行基带信号。
具体的，所述发送单元102，还可采用如下方式，通过所述RU向所述IoT终端发送下行IoT帧：
将所述RU两个边缘位置处设定数量的子载波作为保护子载波。
在除所述保护子载波之外的、所述RU包含的其它子载波所对应的频带上，以单载波方式向所述IoT终端发送下行IoT帧。
进一步的，所述发送单元102可具体采用如下方式生成下行数据帧包括的数据字段：
将所述网络侧设备100与所述STA之间的下行数据，进行编码调制，得到无线局域网WLAN下行调制符号，并将所述WLAN下行调制符号映射到所述至少一个其它RU包含的子载波上。对包含所述至少一个其它RU对应子 载波的频域信号进行傅立叶反变换IFFT，并附加循环前缀CP，生成WLAN下行基带信号。将所述网络侧设备100与IoT终端之间的下行数据，进行编码调制，并附加CP，生成IoT下行单载波符号。对所述IoT下行单载波符号进行波形成型滤波，得到IoT下行基带信号。对所述IoT下行基带信号进行变频，得到IoT下行带通信号，其中，所述IoT下行带通信号的中心频点为fr，其中，fr为用于发送下行IoT帧的RU的中心频点相对于零频的频率差。将所述IoT下行带通信号和所述WLAN下行基带信号相加，得到IoT与WLAN混合传输的下行基带信号。
本发明实施例中，所述IoT下行单载波符号和所述WLAN下行基带信号的OFDM符号采用相同长度的CP，且所述IoT下行单载波符号的长度和所述WLAN下行基带信号的OFDM符号的长度相同。
可选的，本发明实施例中，所述IoT下行单载波符号包括K个调制符号，每个调制符号的周期为T1＝T0/K。
其中，K为不超过用于发送下行IoT帧的RU包含的子载波数的正整数，T1为每个调制符号的周期，T0为所述WLAN下行基带信号的OFDM符号的长度。
在本发明的另一种实现方式中，所述用于发送下行IoT帧的RU包括至少一个基本RU。
所述发送单元102，还用于在所述基本RU上发送信道指示信息。
其中，所述信道指示信息用于指示IoT终端由所述基本RU切换到除所述基本RU之外的其它用于发送下行IoT帧的RU上。
需要说明的是，本发明实施例中所述IoT前导传输的所述下行IoT帧的物理层控制信息包括以下序列之一或任意组合：用于IoT终端获取所述下行IoT帧的定时和频率同步的同步序列、用于IoT终端获取解调所述下行IoT帧所需的信道估计的训练序列。
进一步需要说明的是，所述IoT数据字段包括至少一个子帧。所述IoT数据字段包含至少两个IoT终端的下行数据。其中，每个IoT终端的下行数据 占用至少一个子帧。或者每个IoT终端的下行数据占用至少一个子帧的至少一个时隙。或者每个IoT终端的下行数据占用至少一个子帧和至少一个子帧的至少一个时隙。
基于本发明实施例提供的第一IoT通信方法，本发明实施例还提供一种网络侧设备1000，如图29所示，网络侧设备1000包括存储器1001、处理器1002和发射器1003，其中，
存储器1001，用于存储处理器1002执行的程序代码。
所述处理器1002，用于调用所述存储器1001存储的程序，确定进行下行数据传输的终端设备，所述终端设备包括IoT终端，并通过所述发射器1003发送下行数据帧。
所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段。
所述数据字段在频域上对应的子载波资源包括至少一个RU。所述RU用于向所述IoT终端发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备100与所述IoT终端之间的下行数据。
在本发明实施例中处理器1002，还用于调用所述存储器1001存储的程序，实现本发明实施例中提供的网络侧设备100的功能，以实现本发明实施例提供的第一IoT通信方法。对于处理器1002具体实现的功能，可参阅本发明实施例对第一IoT通信方法以及网络侧设备100的相关描述，在此不再赘述。
本发明实施例提供的网络侧设备100和网络侧设备1000，诸如可以是AP等，本发明实施例不做具体限定。
本发明实施例提供的网络侧设备100和网络侧设备1000，确定进行下行数据传输的终端设备包括IoT终端，网络侧设备100或网络侧设备1000发送的下行数据帧中采用下行IoT帧频分复用802.11ax中数据帧的数据字段的方式，使得网络侧设备100或网络侧设备1000可以对IoT终端进行调度和协调，降低IoT传输受干扰的风险。下行数据帧传输过程中，STA解析传统前导和 HEW前导，获取定时同步、频率同步以及信道估计的信息，IoT终端解析所述下行IoT帧中的前导部分，获取IoT终端定时同步、频率同步以及信道估计的信息，无需解析802.11ax的前导部分，使得IoT终端与STA之间频分共享802.11ax中信道资源过程中，彼此不会产生干扰。并且采用上述方式，IoT终端无需支持20/40/80MHz等大宽带，有效支持带宽受限的窄带IoT终端，保证了IoT设备的低复杂度，低功耗的要求。
基于本发明实施例提供的第二IoT通信方法，本发明实施例提供一种IoT终端200，如图30所示，本发明实施例提供的IoT终端200包括获取单元201和处理单元202，其中：
获取单元201，用于从下行接收信号中获取下行IoT帧，所述下行接收信号包含网络侧设备发送的下行数据帧。
所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述数据字段在频域上对应的子载波资源包括至少一个RU，所述至少一个RU用于发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端200之间的下行数据。
处理单元202，用于对所述获取单元201获取的所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端200之间的下行数据。
本发明实施例中，所述IoT终端200的接收通道的带宽不超过所述RU的带宽。所述IoT终端200的接收通道采用的载波频率为f0+fr，其中，f0为所述下行IoT帧的载波频率，fr为所述RU的中心频点相对于零频的频率差。
本发明实施例的一种实现方式中，所述处理单元202，具体用于采用如下方式对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端200之间的下行数据：
对所述下行IoT帧的每个正交频分复用OFDM符号，去除循环前缀CP，并进行上采样以及傅立叶变换FFT，得到映射到所述RU包含的子载波上的IoT调制信号。对所述IoT调制信号进行解调解码，得到所述网络侧设备与所 述IoT终端200之间的下行数据。
本发明实施例的另一种实现方式中，所述处理单元202，具体用于采用如下方式对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端200之间的下行数据：
对所述下行IoT帧的每个单载波符号，去除循环前缀CP，并进行频域均衡，得到映射到所述RU所对应的频带上的IoT调制信号。对所述IoT调制信号进行解调解码，得到所述网络侧设备与所述IoT终端200之间的下行数据。
需要说明的是，本发明实施例中所述IoT前导传输的所述下行IoT帧的物理层控制信息可包括以下序列之一或任意组合：
A、用于IoT终端200获取所述下行IoT帧的定时和频率同步的同步序列。
B、用于IoT终端200获取解调所述下行IoT帧所需的信道估计的训练序列。
基于本发明实施例提供的第二IoT通信方法和IoT终端200，本发明实施例还提供一种IoT终端2000，如图31所示，IoT终端2000包括存储器2001、处理器2002、传感器2003和通信接口2004，其中：
存储器2001，用于存储处理器2002执行的程序代码。
所述处理器2002，用于调用所述存储器2001存储的程序，控制所述传感器2003通过所述通信接口2004从下行接收信号中获取下行IoT帧，并对所述下行IoT帧进行处理，得到网络侧设备与IoT终端2000之间的下行数据。
本发明实施例中所述下行接收信号包含网络侧设备发送的下行数据帧。所述下行数据帧包括传统前导、HEW前导和数据字段，所述传统前导和所述HEW前导用于网络侧设备与站点STA之间的通信，所述数据字段在频域上对应的子载波资源包括至少一个RU，所述至少一个RU用于发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据。
本发明实施例中，处理器2002，还用于调用所述存储器2001存储的程序， 实现本发明实施例中提供的IoT终端200的功能，以实现本发明实施例提供的第二IoT通信方法。对于处理器2002具体实现的功能，可参阅本发明实施例对第二IoT通信方法以及IoT终端200的相关描述，在此不再赘述。
本发明上述实施例提供的IoT终端200和IoT终端2000，接收的IoT下行信号包含网络侧设备发送的下行数据帧，下行数据帧中下行IoT帧和802.11ax数据帧的数据字段频分复用，使得IoT终端受网络侧设备的调度和协调，降低IoT传输受干扰的风险。下行数据帧传输过程中，STA解析传统前导和HEW前导，获取定时同步、频率同步以及信道估计的信息，IoT终端解析所述下行IoT帧中的前导部分，获取IoT终端定时同步、频率同步以及信道估计的信息，无需解析802.11ax的前导部分，使得IoT终端与STA之间频分共享802.11ax中信道资源过程中，彼此不会产生干扰。并且采用上述方式，IoT终端无需支持20/40/80MHz等大宽带，有效支持带宽受限的窄带IoT终端，保证了IoT设备的低复杂度，低功耗的要求。
基于本发明实施例提供的第三IoT通信方法，本发明实施例提供一种IoT终端300，如图32所示，本发明实施例提供的IoT终端300包括接收单元301和发送单元302，其中：
接收单元301，用于接收网络侧设备发送的上行传输调度请求，所述上行传输调度请求用于调度所述IoT终端300发送上行IoT帧，所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一个RU用于发送所述上行IoT帧。
发送单元302，用于依据所述接收单元301接收的上行传输调度请求，发送所述上行IoT帧。
本发明实施例中，所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端300之间的上行数据。
具体的，本发明实施例中，所述发送单元302，具体采用如下方式发送所 述上行IoT帧：
将所述RU两个边缘位置处设定数量的子载波作为保护子载波。将所述RU中间位置处设定数量的子载波作为直流子载波。在除所述保护子载波和所述直流子载波之外的、所述RU包含的其它子载波上，向所述网络侧设备发送上行IoT帧。
本发明实施例提供的一种实现方式中，所述发送单元302，具体采用如下方式，通过所述RU发送所述上行IoT帧：
对所述网络侧设备与IoT终端300之间的上行数据，进行编码调制，得到IoT上行调制符号，并将所述IoT上行调制符号映射到所述RU包含的子载波上。对包含所述RU对应子载波的频域信号，进行傅立叶反变换IFFT以及下采样，并附加循环前缀，得到第一IoT上行基带信号。将所述第一IoT上行基带信号，通过上行发射通道发送。所述上行发射通道的载波频率为f0+fr，其中，f0为传输RU所在的上行数据帧的信道的载波频率，fr为所述第二RU的中心频点相对于零频的频率差。
本发明的另一种实现方式中，所述发送单元302，具体采用如下方式，发送所述上行IoT帧：
将所述RU两个边缘位置处的设定数量的子载波作为保护子载波。在除所述保护子载波之外的、所述第二RU包含的其它子载波所对应的频带上，以单载波方式向所述网络侧设备发送上行IoT帧。
具体的，所述发送单元302，具体采用如下方式以单载波方式发送所述上行IoT帧：
对所述网络侧设备与IoT终端300之间的上行数据，进行编码调制，附加循环前缀CP，生成IoT上行单载波符号。对所述IoT上行单载波符号进行波形成型滤波，得到第二IoT上行基带信号。将所述第二IoT上行基带信号，通过上行发射通道发送。所述上行发射通道的载波频率为f0+fr，其中，f0为传输RU所在的上行数据帧的信道的载波频率，fr为所述RU的中心频点相对于零频的频率差。
可选的，本发明实施例中所述IoT上行单载波符号和所述STA发送的WLAN上行基带信号的OFDM符号采用相同长度的CP，且所述IoT上行单载波符号和所述STA发送的WLAN上行基带信号的OFDM符号的长度相同。
需要说明的是，本发明实施例中所述IoT上行单载波符号包括K个调制符号，每个调制符号的周期为T1＝T0/K。
其中，K为不超过所述RU包含的子载波数的正整数，T1为每个调制符号的周期，T0为所述STA发送的WLAN上行基带信号的OFDM符号的长度。
进一步需要说明的是，本发明实施例中所述IoT前导传输的所述上行IoT帧的物理层控制信息可包括以下序列之一或任意组合：
用于网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列。
用于网络侧设备获取解调所述上行IoT帧所需的信道估计的训练序列。
可选的，本发明实施例中所述IoT数据字段可包括至少一个子帧。所述IoT数据字段包含至少两个IoT终端300的上行数据。每个IoT终端300的上行数据占用至少一个子帧。或者每个IoT终端300的上行数据占用至少一个子帧的至少一个时隙。或者每个IoT终端300的上行数据占用至少一个子帧和至少一个子帧的至少一个时隙。
可选的，本发明实施例中所述上行传输调度请求可通过网络侧设备发送的下行数据帧发送。所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述下行数据帧包括的数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。
基于本发明实施例提供的第三IoT通信方法和IoT终端300，本发明实施例还提供一种IoT终端3000，如图33所示，IoT终端3000包括存储器3001、处理器3002、接收器3003和发射器3004，其中：
存储器3001，用于存储处理器3002执行的程序代码。
所述处理器3002，用于调用所述存储器3001存储的程序，通过所述接收器3003接收网络侧设备发送的上行传输调度请求，并依据所述上行传输调度请求，通过发射器3004发送上行IoT帧。
本发明实施例中所述上行传输调度请求用于调度IoT终端3000发送上行IoT帧，所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个RU，所述至少一个RU用于发送所述上行IoT帧。
本发明实施例中IoT终端3000发送的所述上行IoT帧，包括IoT前导和IoT数据字段，所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端3000之间的上行数据。
本发明实施例中，处理器3002，还用于调用所述存储器3001存储的程序，实现本发明实施例中提供的IoT终端300的功能，以实现本发明实施例提供的第三IoT通信方法。对于处理器3002具体实现的功能，可参阅本发明实施例对第三IoT通信方法以及IoT终端300的相关描述，在此不再赘述。
本发明实施例提供的上述IoT终端300和IoT终端3000，发送的的上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个RU，所述至少一个RU用于发送所述上行IoT帧。本发明实施例中上行数据帧中采用上IoT终端和STA频分复用802.11ax中数据帧的数据字段的方式，使得IoT终端受网络侧设备的调度和协调，降低IoT传输受干扰的风险。上行数据帧传输过程中，IoT终端只需发送窄带的上行IoT帧，并与STA之间频分复用802.11ax中的信道资源，彼此不产生干扰。采用上述方式，IoT终端无需支持20/40/80MHz等大宽带，有效支持带宽受限的窄带IoT终端，保证了IoT设备的低复杂度，低功耗的要求。
基于本发明实施例提供的第四IoT通信方法，本发明实施例提供一种网络侧设备400，如图34所示，本发明实施例提供的网络侧设备400包括发送单元401和获取单元402，其中：
发送单元401，用于向IoT终端发送上行传输调度请求，所述上行传输调度请求用于调度所述IoT终端发送上行IoT帧。
获取单元402，用于获取所述IoT终端依据所述发送单元401发送的上行 传输调度请求发送的上行IoT帧。
其中，所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一个RU用于发送所述上行IoT帧。所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备400与所述IoT终端之间的上行数据。
本发明实施例的一种实现方式中，所述获取单元402，具体采用如下方式获取所述IoT终端依据所述上行传输调度请求发送的上行IoT帧，包括：
获取上行接收信号，所述上行接收信号包含所述IoT终端发送的上行IoT帧。对所述上行接收信号去除循环前缀CP，并进行傅立叶变换FFT，得到频域接收信号。获取所述频域接收信号中所述RU对应的子载波上的信号，得到IoT频域信号。对所述IoT频域信号进行频域均衡、傅立叶反变换IFFT，以及解调解码处理，得到所述网络侧设备与所述IoT终端之间的上行数据。
本发明实施例中，所述发送单元401，具体采用如下方式向IoT终端发送上行传输调度请求：
通过下行数据帧发送所述上行传输调度请求。所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述下行数据帧包括的数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。
需要说明的是，本发明实施例中所述IoT前导传输的所述上行IoT帧的物理层控制信息可包括以下序列之一或任意组合：
用于网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列。
用于网络侧设备获取解调所述上行IoT帧所需的信道估计的训练序列。
基于本发明实施例提供的第四IoT通信方法和网络侧设备400，本发明实施例还提供一种网络侧设备4000，如图35所示，网络侧设备4000包括存储器4001、处理器4002和收发器4003，其中：
存储器4001，用于存储处理器4002执行的程序代码。
所述处理器4002，用于调用所述存储器4001存储的程序，通过所述收发器4003向IoT终端发送上行传输调度请求，并获取所述IoT终端依据所述上行传输调度请求发送的上行IoT帧。
本发明实施例中上行传输调度请求可通过下行数据帧的形式发送，所述下行数据帧包括传统前导、HEW前导和数据字段，所述传统前导和所述HEW前导用于网络侧设备与站点STA之间的通信，所述数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。
本发明实施例中所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个RU，所述至少一个RU用于发送所述上行IoT帧。
本发明实施例中，处理器4002，还用于调用所述存储器4001存储的程序，实现本发明实施例中提供的网络侧设备400的功能，以实现本发明实施例提供的第四IoT通信方法。对于处理器4002具体实现的功能，可参阅本发明实施例对第三IoT通信方法以及网络侧设备400的相关描述，在此不再赘述。
本发明上述实施例提供的网络侧设备400和网络侧设备4000，通过下行数据帧向IoT终端发送上行调度请求，下行数据帧下行IoT帧与802.11ax中数据帧的数据字段频分复用，使得网络侧设备400或网络侧设备4000可以对IoT终端进行调度和协调，降低IoT传输受干扰的风险。所述网络侧设备400或网络侧设备4000接收所述IoT终端依据所述上行传输调度请求发送的上行数据帧。上行数据帧中包括传统前导、HEW前导和数据段，所述数据段中包括有用于传输IoT终端与网络侧设备上行数据的RU。故本发明实施例中，IoT终端只需发送窄带的上行IoT帧，并与STA之间频分复用802.11ax的信道资源，彼此不产生干扰。并且采用上述方式，IoT终端无需支持20/40/80MHz等大宽带，有效支持带宽受限的窄带IoT终端，保证了IoT设备的低复杂度，低功耗的要求。
本发明实施例还提供一种通信系统500，该通信系统500中包括网络侧设备501、STA502和IoT终端503，如图36所示。
本发明实施例中网络侧设备501发送下行数据帧，下行数据帧包括传统前导、HEW前导和数据字段。所述传统前导和所述HEW前导用于网络侧设备501与STA502之间的通信。所述数据字段在频域上对应的子载波资源包括第一RU和第二RU。所述第一RU用于向所述IoT终端503发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导包括用所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备501与所述IoT终端503之间的下行数据。所述第二RU用于向STA502发送所述网络侧设备501与所述STA502之间的下行数据。
STA502通过上述下行数据帧，解析传统前导和HEW前导，获取STA502定时同步、频率同步或者信道估计等信息，并通过所述数据字段中的第二RU获取所述网络侧设备501与所述STA502之间的下行数据。
IoT终端503通过上述下行数据帧，解析IoT前导，获取IoT终端503定时同步、频率同步以及信道估计的字段，并通过所述数据字段中的第一RU获取所述网络侧设备501发送的下行数据。
本发明实施例中网络侧设备501还可向IoT终端503发送上行传输调度请求，调度IoT终端503发送上行数据。本发明实施例中网络侧设备501通过上行数据帧接收上行数据，所述上行数据帧包括传统前导、HEW前导和数据字段，所述传统前导和所述HEW前导用于网络侧设备501与站点STA502之间的通信，所述数据字段在频域上对应的子载波资源包括第三RU，所述第三RU用于传输所述网络侧设备501与IoT终端503之间的上行数据。
需要说明的是，本发明上述实施例中涉及的存储器，可以是只读存储器(英文：read-only memory；简称：ROM)，随机存取存储器(英文：random access memory；简称：RAM)，也可以是电可擦可编程只读存储器(英文：Electrically Erasable Programmable Read-Only Memory；简称：EEPROM)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此，例如存储器可以是上述存储器的组合。
本发明实施例涉及的处理器，可以是一个通用的中央处理器，利用各种接口和线路连接整个设备的各个部分，通过运行或执行存储在存储器内的指令以及调用存储在存储器内的数据，执行相应设备的各种功能和处理数据，从而对相应设备进行整体监控。可选的，处理器可包括一个或多个处理单元；优选的，处理器可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器190中。
本发明在一些实施例中，处理器、存储器、可以在单一芯片上实现。
本发明实施例提供的通信系统500中包括网络侧设备501可以是上述实施例提供的网络侧设备100、网络侧设备1000、网络侧设备400或网络侧设备4000，并实现相应的功能，本发明实施例在此不再赘述。
本发明实施例提供的通信系统500中包括的IoT终端可以是上述实施例提供的IoT终端设备200、IoT终端设备2000、IoT终端设备300或IoT终端设备3000，并实现相应的功能，本发明实施例在此不再赘述。
本发明实施例提供的通信系统，WLAN数据帧包括的数据字段在频域上对应的子载波资源，包括有用于传输网络侧设备与IoT终端之间的下行数据或上行数据的RU，以及用于传输网络侧设备与STA之间的下行数据或上行数据的RU，故使得IoT终端与STA之间可共享WLAN网络中的数据帧进行数据的发送或接收，进而使得WLAN的网络侧设备可以调度IoT终端，降低IoT通信过程中出现冲突的风险。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分步骤是可以通过程序来指令处理器完成，所述的程序可以存储于计算机可读存储介质中，所述存储介质是非短暂性(英文：non-transitory)介质，例如随机存取存储器，只读存储器，快闪存储器，硬盘，固态硬盘，磁带(英文：magnetic  tape)，软盘(英文：floppy disk)，光盘(英文：optical disc)及其任意组合。
本发明是参照本发明实施例的方法和设备各自的流程图和方框图来描述的。应理解可由计算机程序指令实现流程图和方框图中的每一流程和方框、以及流程图和方框图中的流程和方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和方框图一个方框或多个方框中指定的功能的装置。
以上所述，仅为本发明较佳的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到的变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应该以权利要求的保护范围为准。

Claims (60)

  1. 一种物联网IoT通信方法，其特征在于，包括：
    网络侧设备确定进行下行数据传输的终端设备，所述终端设备包括IoT终端；
    所述网络侧设备发送下行数据帧；
    所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段；
    所述数据字段在频域上对应的子载波资源包括至少一个资源单元RU；
    所述RU用于向所述IoT终端发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据。
  2. 如权利要求1所述的方法，其特征在于，所述终端设备还包括站点STA；
    所述数据字段在频域上对应的子载波资源还包括不同于所述RU的至少一个其它RU；
    所述至少一个其它RU用于传输所述网络侧设备与所述STA之间的下行数据。
  3. 如权利要求1或2所述的方法，其特征在于，所述网络侧设备，具体采用如下方式，通过所述RU向所述IoT终端发送下行IoT帧：
    将所述RU两个边缘位置处设定数量的子载波作为保护子载波；
    将所述RU中间位置处设定数量的子载波作为直流子载波；
    通过除所述保护子载波和所述直流子载波之外的、所述RU包含的其它子载波，向所述IoT终端发送下行IoT帧。
  4. 如权利要求3所述的方法，其特征在于，所述下行数据帧中包括的数据字段，具体采用如下方式生成：
    所述网络侧设备将所述网络侧设备与所述IoT终端之间的下行数据，进 行编码调制，得到IoT下行调制符号，并将所述IoT下行调制符号映射到所述至少一个RU包含的子载波上；
    所述网络侧设备将所述网络侧设备与所述STA之间的下行数据，进行编码调制，得到无线局域网WLAN下行调制符号，并将所述WLAN下行调制符号映射到所述至少一个其它RU包含的子载波上；
    所述网络侧设备对包含所述至少一个RU对应子载波和所述至少一个其它RU对应子载波的频域信号，进行傅立叶反变换IFFT，并附加循环前缀，生成IoT与WLAN混合传输的下行基带信号。
  5. 如权利要求1或2所述的方法，其特征在于，所述网络侧设备，具体采用如下方式，通过所述RU向所述IoT终端发送下行IoT帧：
    将所述RU两个边缘位置处设定数量的子载波作为保护子载波；
    在除所述保护子载波之外的、所述RU包含的其它子载波所对应的频带上，以单载波方式向所述IoT终端发送下行IoT帧。
  6. 如权利要求5所述的方法，其特征在于，所述下行数据帧中包括的数据字段，具体采用如下方式生成：
    所述网络侧设备将所述网络侧设备与所述STA之间的下行数据，进行编码调制，得到无线局域网WLAN下行调制符号，并将所述WLAN下行调制符号映射到所述至少一个其它RU包含的子载波上；
    所述网络侧设备对包含所述至少一个其它RU对应子载波的频域信号进行傅立叶反变换IFFT，并附加循环前缀CP，生成WLAN下行基带信号；
    所述网络侧设备将所述网络侧设备与IoT终端之间的下行数据，进行编码调制，并附加CP，生成IoT下行单载波符号；
    所述网络侧设备对所述IoT下行单载波符号进行波形成型滤波，得到IoT下行基带信号；
    所述网络侧设备对所述IoT下行基带信号进行变频，得到IoT下行带通信号，其中，所述IoT下行带通信号的中心频点为fr，其中，fr为用于发送下行IoT帧的RU的中心频点相对于零频的频率差；
    所述网络侧设备将所述IoT下行带通信号和所述WLAN下行基带信号相加，得到IoT与WLAN混合传输的下行基带信号。
  7. 如权利要求6所述的方法，其特征在于，所述IoT下行单载波符号和所述WLAN下行基带信号的OFDM符号采用相同长度的CP，且所述IoT下行单载波符号的长度和所述WLAN下行基带信号的OFDM符号的长度相同。
  8. 如权利要求6或7所述的方法，其特征在于，所述IoT下行单载波符号包括K个调制符号，每个调制符号的周期为T1＝T0/K；
    其中，K为不超过用于发送下行IoT帧的RU包含的子载波数的正整数，T1为每个调制符号的周期，T0为所述WLAN下行基带信号的OFDM符号的长度。
  9. 如权利要求1至8任一项所述的方法，其特征在于，所述用于发送下行IoT帧的RU包括至少一个基本RU，所述方法还包括：
    所述网络侧设备，在所述基本RU上发送信道指示信息；
    其中，所述信道指示信息用于指示IoT终端由所述基本RU切换到除所述基本RU之外的其它用于发送下行IoT帧的RU上。
  10. 如权利要求1至9任一项所述的方法，其特征在于，所述IoT前导传输的所述下行IoT帧的物理层控制信息包括以下序列之一或任意组合：
    用于IoT终端获取所述下行IoT帧的定时和频率同步的同步序列；
    用于IoT终端获取解调所述下行IoT帧所需的信道估计的训练序列。
  11. 如权利要求1至11任一项所述的方法，其特征在于，所述IoT数据字段包括至少一个子帧；
    所述IoT数据字段包含至少两个IoT终端的下行数据；
    其中，每个IoT终端的下行数据占用至少一个子帧；或者
    每个IoT终端的下行数据占用至少一个子帧的至少一个时隙；或者
    每个IoT终端的下行数据占用至少一个子帧和至少一个子帧的至少一个时隙。
  12. 一种物联网IoT通信方法，其特征在于，包括：
    IoT终端从下行接收信号中获取下行IoT帧，所述下行接收信号包含网络侧设备发送的下行数据帧；
    所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一个RU用于发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据；
    所述IoT终端对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据。
  13. 如权利要求12所述的方法，其特征在于，
    所述IoT终端的接收通道的带宽不超过所述RU的带宽；
    所述IoT终端的接收通道采用的载波频率为f0+fr，其中，f0为所述下行IoT帧的载波频率，fr为所述RU的中心频点相对于零频的频率差。
  14. 如权利要求12或13所述的方法，其特征在于，所述IoT终端对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据，包括：
    所述IoT终端对所述下行IoT帧的每个正交频分复用OFDM符号，去除循环前缀CP，并进行上采样以及傅立叶变换FFT，得到映射到所述RU包含的子载波上的IoT调制信号；
    所述IoT终端对所述IoT调制信号进行解调解码，得到所述网络侧设备与所述IoT终端之间的下行数据。
  15. 如权利要求12或13所述的方法，其特征在于，所述IoT终端对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据，包括：
    所述IoT终端对所述下行IoT帧的每个单载波符号，去除循环前缀CP，并进行频域均衡，得到映射到所述RU所对应的频带上的IoT调制信号；
    所述IoT终端对所述IoT调制信号进行解调解码，得到所述网络侧设备与 所述IoT终端之间的下行数据。
  16. 如权利要求12至15任一项所述的方法，其特征在于，所述IoT前导传输的所述下行IoT帧的物理层控制信息包括以下序列之一或任意组合：
    用于IoT终端获取所述下行IoT帧的定时和频率同步的同步序列；
    用于IoT终端获取解调所述下行IoT帧所需的信道估计的训练序列。
  17. 一种物联网IoT通信方法，其特征在于，包括：
    IoT终端接收网络侧设备发送的上行传输调度请求；
    所述上行传输调度请求用于调度所述IoT终端发送上行IoT帧；
    所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一个RU用于发送所述上行IoT帧；
    所述IoT终端依据所述上行传输调度请求，发送所述上行IoT帧；
    所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的上行数据。
  18. 如权利要求17所述的方法，其特征在于，所述IoT终端，具体采用如下方式，发送所述上行IoT帧：
    将所述RU两个边缘位置处设定数量的子载波作为保护子载波；
    将所述RU中间位置处设定数量的子载波作为直流子载波；
    在除所述保护子载波和所述直流子载波之外的、所述RU包含的其它子载波上，向所述网络侧设备发送上行IoT帧。
  19. 如权利要求18所述的方法，其特征在于，所述IoT终端，具体采用如下方式，通过所述RU发送所述上行IoT帧，包括：
    所述IoT终端对所述网络侧设备与IoT终端之间的上行数据，进行编码调制，得到IoT上行调制符号，并将所述IoT上行调制符号映射到所述RU包含的子载波上；
    所述IoT终端对包含所述RU对应子载波的频域信号，进行傅立叶反变换 IFFT以及下采样，并附加循环前缀，得到第一IoT上行基带信号；
    将所述第一IoT上行基带信号，通过上行发射通道发送；
    所述上行发射通道的载波频率为f0+fr，其中，f0为传输RU所在的上行数据帧的信道的载波频率，fr为所述第二RU的中心频点相对于零频的频率差。
  20. 如权利要求17所述的方法，其特征在于，所述IoT终端具体采用如下方式，发送所述上行IoT帧：
    将所述RU两个边缘位置处的设定数量的子载波作为保护子载波；
    在除所述保护子载波之外的、所述第二RU包含的其它子载波所对应的频带上，以单载波方式向所述网络侧设备发送上行IoT帧。
  21. 如权利要求20所述的方法，其特征在于，所述IoT终端，具体采用如下方式以单载波方式发送所述上行IoT帧，包括：
    所述IoT终端对所述网络侧设备与IoT终端之间的上行数据，进行编码调制，附加循环前缀CP，生成IoT上行单载波符号；
    所述IoT终端对所述IoT上行单载波符号进行波形成型滤波，得到第二IoT上行基带信号；
    所述IoT终端将所述第二IoT上行基带信号，通过上行发射通道发送；
    所述上行发射通道的载波频率为f0+fr，其中，f0为传输RU所在的上行数据帧的信道的载波频率，fr为所述RU的中心频点相对于零频的频率差。
  22. 如权利要求21所述的方法，其特征在于，所述IoT上行单载波符号和所述STA发送的WLAN上行基带信号的OFDM符号采用相同长度的CP，且所述IoT上行单载波符号和所述STA发送的WLAN上行基带信号的OFDM符号的长度相同。
  23. 如权利要求21或22所述的方法，其特征在于，所述IoT上行单载波符号包括K个调制符号，每个调制符号的周期为T1＝T0/K；
    其中，K为不超过所述RU包含的子载波数的正整数，T1为每个调制符号的周期，T0为所述STA发送的WLAN上行基带信号的OFDM符号的长度。
  24. 如权利要求17至23任一项所述的方法，其特征在于，所述IoT前 导传输的所述上行IoT帧的物理层控制信息包括以下序列之一或任意组合：
    用于所述网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列；
    用于所述网络侧设备获取解调所述上行IoT帧所需的信道估计的训练序列。
  25. 如权利要求17至24任一项所述的方法，其特征在于，所述上行IoT帧包含至少两个IoT终端发送的上行IoT子帧；
    其中，每个IoT终端发送的所述上行IoT子帧包括IoT前导和IoT数据字段。
  26. 如权利要求17至25任一项所述的方法，其特征在于，所述上行传输调度请求通过网络侧设备发送的下行数据帧发送；
    所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述下行数据帧包括的数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。
  27. 一种物联网IoT通信方法，其特征在于，包括：
    网络侧设备向IoT终端发送上行传输调度请求，所述上行传输调度请求用于调度所述IoT终端发送上行IoT帧；
    所述网络侧设备获取所述IoT终端依据所述上行传输调度请求发送的上行IoT帧；
    其中，所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一个RU用于发送所述上行IoT帧；
    所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的上行数据。
  28. 如权利要求27所述的方法，其特征在于，所述网络侧设备，具体采用如下方式接收所述IoT终端依据所述上行传输调度请求发送的上行IoT帧，包括：
    所述网络侧设备获取上行接收信号，所述上行接收信号包含所述IoT终端发送的上行IoT帧；
    所述网络侧设备对所述上行接收信号去除循环前缀CP，并进行傅立叶变换FFT，得到频域接收信号；
    所述网络侧设备获取所述频域接收信号中所述RU对应的子载波上的信号，得到IoT频域信号；
    所述网络侧设备对所述IoT频域信号进行频域均衡、傅立叶反变换IFFT，以及解调解码处理，得到所述网络侧设备与所述IoT终端之间的上行数据。
  29. 如权利要求27或28所述的方法，其特征在于，所述网络侧设备向IoT终端发送上行传输调度请求，包括：
    所述网络侧设备通过下行数据帧发送所述上行传输调度请求；
    所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述下行数据帧包括的数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。
  30. 如权利要求27至29任一项所述的方法，其特征在于，所述IoT前导传输的所述上行IoT帧的物理层控制信息包括以下序列之一或任意组合：
    用于所述网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列；
    用于所述网络侧设备获取解调所述上行IoT帧所需的信道估计的训练序列。
  31. 一种网络侧设备，其特征在于，包括：
    确定单元，用于确定进行下行数据传输的终端设备，所述终端设备包括IoT终端；
    发送单元，用于发送下行数据帧；
    所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段；
    所述数据字段在频域上对应的子载波资源包括至少一个资源单元RU；
    所述RU用于向所述IoT终端发送下行IoT帧，所述下行IoT帧包括IoT 前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据。
  32. 如权利要求31所述的网络侧设备，其特征在于，所述终端设备还包括站点STA；
    所述数据字段在频域上对应的子载波资源还包括不同于所述RU的至少一个其它RU；
    所述至少一个其它RU用于传输所述网络侧设备与所述STA之间的下行数据。
  33. 如权利要求31或32所述的网络侧设备，其特征在于，所述发送单元，具体采用如下方式，通过所述RU向所述IoT终端发送下行IoT帧：
    将所述RU两个边缘位置处设定数量的子载波作为保护子载波；
    将所述RU中间位置处设定数量的子载波作为直流子载波；
    通过除所述保护子载波和所述直流子载波之外的、所述RU包含的其它子载波，向所述IoT终端发送下行IoT帧。
  34. 如权利要求33所述的网络侧设备，其特征在于，所述发送单元具体采用如下方式生成下行数据帧包括的数据字段：
    将所述网络侧设备与所述IoT终端之间的下行数据，进行编码调制，得到IoT下行调制符号，并将所述IoT下行调制符号映射到所述至少一个RU包含的子载波上；
    将所述网络侧设备与所述STA之间的下行数据，进行编码调制，得到无线局域网WLAN下行调制符号，并将所述WLAN下行调制符号映射到所述至少一个其它RU包含的子载波上；
    对包含所述至少一个RU对应子载波和所述至少一个其它RU对应子载波的频域信号，进行傅立叶反变换IFFT，并附加循环前缀，生成IoT与WLAN混合传输的下行基带信号。
  35. 如权利要求31或32所述的网络侧设备，其特征在于，所述发送单 元，具体采用如下方式，通过所述RU向所述IoT终端发送下行IoT帧：
    将所述RU两个边缘位置处设定数量的子载波作为保护子载波；
    在除所述保护子载波之外的、所述RU包含的其它子载波所对应的频带上，以单载波方式向所述IoT终端发送下行IoT帧。
  36. 如权利要求35所述的网络侧设备，其特征在于，所述发送单元具体采用如下方式生成下行数据帧包括的数据字段：
    将所述网络侧设备与所述STA之间的下行数据，进行编码调制，得到无线局域网WLAN下行调制符号，并将所述WLAN下行调制符号映射到所述至少一个其它RU包含的子载波上；
    对包含所述至少一个其它RU对应子载波的频域信号进行傅立叶反变换IFFT，并附加循环前缀CP，生成WLAN下行基带信号；
    将所述网络侧设备与IoT终端之间的下行数据，进行编码调制，并附加CP，生成IoT下行单载波符号；
    对所述IoT下行单载波符号进行波形成型滤波，得到IoT下行基带信号；
    对所述IoT下行基带信号进行变频，得到IoT下行带通信号，其中，所述IoT下行带通信号的中心频点为fr，其中，fr为用于发送下行IoT帧的RU的中心频点相对于零频的频率差；
    将所述IoT下行带通信号和所述WLAN下行基带信号相加，得到IoT与WLAN混合传输的下行基带信号。
  37. 如权利要求36所述的网络侧设备，其特征在于，所述IoT下行单载波符号和所述WLAN下行基带信号的OFDM符号采用相同长度的CP，且所述IoT下行单载波符号的长度和所述WLAN下行基带信号的OFDM符号的长度相同。
  38. 如权利要求36或37所述的网络侧设备，其特征在于，所述IoT下行单载波符号包括K个调制符号，每个调制符号的周期为T1＝T0/K；
    其中，K为不超过用于发送下行IoT帧的RU包含的子载波数的正整数，T1为每个调制符号的周期，T0为所述WLAN下行基带信号的OFDM符号的 长度。
  39. 如权利要求31至38任一项所述的网络侧设备，其特征在于，所述用于发送下行IoT帧的RU包括至少一个基本RU；
    所述发送单元，还用于在所述基本RU上发送信道指示信息；
    其中，所述信道指示信息用于指示IoT终端由所述基本RU切换到除所述基本RU之外的其它用于发送下行IoT帧的RU上。
  40. 如权利要求31至39任一项所述的网络侧设备，其特征在于，所述IoT前导传输的所述下行IoT帧的物理层控制信息包括以下序列之一或任意组合：
    用于IoT终端获取所述下行IoT帧的定时和频率同步的同步序列；
    用于IoT终端获取解调所述下行IoT帧所需的信道估计的训练序列。
  41. 如权利要求31至40任一项所述的网络侧设备，其特征在于，所述IoT数据字段包括至少一个子帧；
    所述IoT数据字段包含至少两个IoT终端的下行数据；
    其中，每个IoT终端的下行数据占用至少一个子帧；或者
    每个IoT终端的下行数据占用至少一个子帧的至少一个时隙；或者
    每个IoT终端的下行数据占用至少一个子帧和至少一个子帧的至少一个时隙。
  42. 一种物联网IoT终端，其特征在于，包括：
    获取单元，用于从下行接收信号中获取下行IoT帧，所述下行接收信号包含网络侧设备发送的下行数据帧；
    所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一个RU用于发送下行IoT帧，所述下行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述下行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的下行数据；
    处理单元，用于对所述获取单元获取的所述下行IoT帧进行处理，得到 所述网络侧设备与所述IoT终端之间的下行数据。
  43. 如权利要求42所述的IoT终端，其特征在于，
    所述IoT终端的接收通道的带宽不超过所述RU的带宽；
    所述IoT终端的接收通道采用的载波频率为f0+fr，其中，f0为所述下行IoT帧的载波频率，fr为所述RU的中心频点相对于零频的频率差。
  44. 如权利要求42或43所述的IoT终端，其特征在于，所述处理单元，具体用于采用如下方式对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据：
    对所述下行IoT帧的每个正交频分复用OFDM符号，去除循环前缀CP，并进行上采样以及傅立叶变换FFT，得到映射到所述RU包含的子载波上的IoT调制信号；
    对所述IoT调制信号进行解调解码，得到所述网络侧设备与所述IoT终端之间的下行数据。
  45. 如权利要求42或43所述的IoT终端，其特征在于，所述处理单元，具体用于采用如下方式对所述下行IoT帧进行处理，得到所述网络侧设备与所述IoT终端之间的下行数据：
    对所述下行IoT帧的每个单载波符号，去除循环前缀CP，并进行频域均衡，得到映射到所述RU所对应的频带上的IoT调制信号；
    对所述IoT调制信号进行解调解码，得到所述网络侧设备与所述IoT终端之间的下行数据。
  46. 如权利要求42至45任一项所述的IoT终端，其特征在于，所述IoT前导传输的所述下行IoT帧的物理层控制信息包括以下序列之一或任意组合：
    用于IoT终端获取所述下行IoT帧的定时和频率同步的同步序列；
    用于IoT终端获取解调所述下行IoT帧所需的信道估计的训练序列。
  47. 一种物联网IoT终端，其特征在于，包括：
    接收单元，用于接收网络侧设备发送的上行传输调度请求，所述上行传输调度请求用于调度所述IoT终端发送上行IoT帧；
    发送单元，用于依据所述接收单元接收的上行传输调度请求，发送所述上行IoT帧；
    所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的上行数据。
  48. 如权利要求47所述的IoT终端，其特征在于，所述发送单元，具体采用如下方式发送所述上行IoT帧：
    将所述RU两个边缘位置处设定数量的子载波作为保护子载波；
    将所述RU中间位置处设定数量的子载波作为直流子载波；
    在除所述保护子载波和所述直流子载波之外的、所述RU包含的其它子载波上，向所述网络侧设备发送上行IoT帧。
  49. 如权利要求48所述的IoT终端，其特征在于，所述发送单元，具体采用如下方式，通过所述RU发送所述上行IoT帧：
    对所述网络侧设备与IoT终端之间的上行数据，进行编码调制，得到IoT上行调制符号，并将所述IoT上行调制符号映射到所述RU包含的子载波上；
    对包含所述RU对应子载波的频域信号，进行傅立叶反变换IFFT以及下采样，并附加循环前缀，得到第一IoT上行基带信号；
    将所述第一IoT上行基带信号，通过上行发射通道发送；
    所述上行发射通道的载波频率为f0+fr，其中，f0为传输RU所在的上行数据帧的信道的载波频率，fr为所述第二RU的中心频点相对于零频的频率差。
  50. 如权利要求47所述的IoT终端，其特征在于，所述发送单元，具体采用如下方式，发送所述上行IoT帧：
    将所述RU两个边缘位置处的设定数量的子载波作为保护子载波；
    在除所述保护子载波之外的、所述第二RU包含的其它子载波所对应的频带上，以单载波方式向所述网络侧设备发送上行IoT帧。
  51. 如权利要求50所述的IoT终端，其特征在于，所述发送单元，具体采用如下方式以单载波方式发送所述上行IoT帧：
    对所述网络侧设备与IoT终端之间的上行数据，进行编码调制，附加循环前缀CP，生成IoT上行单载波符号；
    对所述IoT上行单载波符号进行波形成型滤波，得到第二IoT上行基带信号；
    将所述第二IoT上行基带信号，通过上行发射通道发送；
    所述上行发射通道的载波频率为f0+fr，其中，f0为传输RU所在的上行数据帧的信道的载波频率，fr为所述RU的中心频点相对于零频的频率差。
  52. 如权利要求51所述的IoT终端，其特征在于，所述IoT上行单载波符号和所述STA发送的WLAN上行基带信号的OFDM符号采用相同长度的CP，且所述IoT上行单载波符号和所述STA发送的WLAN上行基带信号的OFDM符号的长度相同。
  53. 如权利要求51或52所述的IoT终端，其特征在于，所述IoT上行单载波符号包括K个调制符号，每个调制符号的周期为T1＝T0/K；
    其中，K为不超过所述RU包含的子载波数的正整数，T1为每个调制符号的周期，T0为所述STA发送的WLAN上行基带信号的OFDM符号的长度。
  54. 如权利要求47至53任一项所述的IoT终端，其特征在于，所述IoT前导传输的所述上行IoT帧的物理层控制信息包括以下序列之一或任意组合：
    用于所述网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列；
    用于所述网络侧设备获取解调所述上行IoT帧所需的信道估计的训练序列。
  55. 如权利要求47至54任一项所述的IoT终端，其特征在于，所述上行IoT帧包含至少两个IoT终端的上行IoT子帧；
    其中，每个IoT终端的所述上行IoT子帧包括所述IoT终端发送的IoT前导和IoT数据字段；
    每个IoT终端的所述上行IoT子帧占用至少一个子帧。
  56. 如权利要求47至55任一项所述的IoT终端，其特征在于，所述上行传输调度请求通过网络侧设备发送的下行数据帧发送；
    所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述下行数据帧包括的数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。
  57. 一种网络侧设备，其特征在于，包括：
    发送单元，用于向IoT终端发送上行传输调度请求，所述上行传输调度请求用于调度所述IoT终端发送上行IoT帧；
    获取单元，用于获取所述IoT终端依据所述发送单元发送的上行传输调度请求发送的上行IoT帧；
    其中，所述上行IoT帧位于上行数据帧的数据字段，所述上行数据帧的数据字段在频域上对应的子载波资源包括至少一个资源单元RU，所述至少一个RU用于发送所述上行IoT帧；
    所述上行IoT帧包括IoT前导和IoT数据字段，所述IoT前导用于传输所述上行IoT帧的物理层控制信息，所述IoT数据字段用于传输所述网络侧设备与所述IoT终端之间的上行数据。
  58. 如权利要求57所述的网络侧设备，其特征在于，所述获取单元，具体采用如下方式获取所述IoT终端依据所述上行传输调度请求发送的上行IoT帧，包括：
    获取上行接收信号，所述上行接收信号包含所述IoT终端发送的上行IoT帧；
    对所述上行接收信号去除循环前缀CP，并进行傅立叶变换FFT，得到频域接收信号；
    获取所述频域接收信号中所述RU对应的子载波上的信号，得到IoT频域信号；
    对所述IoT频域信号进行频域均衡、傅立叶反变换IFFT，以及解调解码处理，得到所述网络侧设备与所述IoT终端之间的上行数据。
  59. 如权利要求57或58所述的网络侧设备，其特征在于，所述发送单元，具体采用如下方式向IoT终端发送上行传输调度请求：
    通过下行数据帧发送所述上行传输调度请求；
    所述下行数据帧包括传统前导、高效率无线局域网HEW前导和数据字段，所述下行数据帧包括的数据字段在频域上对应的子载波资源包括至少一个用于发送所述上行传输调度请求的RU。
  60. 如权利要求57至59任一项所述的网络侧设备，其特征在于，所述IoT前导传输的所述上行IoT帧的物理层控制信息包括以下序列之一或任意组合：
    用于所述网络侧设备获取所述上行IoT帧的定时和频率同步的同步序列；
    用于所述网络侧设备获取解调所述上行IoT帧所需的信道估计的训练序列。
PCT/CN2016/088231 2015-09-02 2016-07-01 一种物联网通信方法、网络侧设备及物联网终端 Ceased WO2017036246A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
KR1020187008343A KR102175875B1 (ko) 2015-09-02 2016-07-01 사물 인터넷 통신 방법, 네트워크 측 디바이스, 및 사물 인터넷 단말기
EP16840675.9A EP3337096B1 (en) 2015-09-02 2016-07-01 Internet of things communication method, network side device and internet of things terminal
RU2018111215A RU2693293C1 (ru) 2015-09-02 2016-07-01 Способ осуществления связи посредством интернета вещей, устройство на стороне сети и терминал интернета вещей
JP2018511197A JP6556336B2 (ja) 2015-09-02 2016-07-01 モノのインターネット通信方法、ネットワーク側装置、およびモノのインターネット端末
US15/909,771 US10616026B2 (en) 2015-09-02 2018-03-01 Internet of things communication method, network side device, and internet of things terminal
US16/839,520 US11388035B2 (en) 2015-09-02 2020-04-03 Internet of things communication method, network side device, and internet of things terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510559591.0A CN106487573B (zh) 2015-09-02 2015-09-02 一种物联网通信方法、网络侧设备及物联网终端
CN201510559591.0 2015-09-02

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/909,771 Continuation US10616026B2 (en) 2015-09-02 2018-03-01 Internet of things communication method, network side device, and internet of things terminal

Publications (1)

Publication Number Publication Date
WO2017036246A1 true WO2017036246A1 (zh) 2017-03-09

Family

ID=58186578

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/088231 Ceased WO2017036246A1 (zh) 2015-09-02 2016-07-01 一种物联网通信方法、网络侧设备及物联网终端

Country Status (7)

Country Link
US (2) US10616026B2 (zh)
EP (1) EP3337096B1 (zh)
JP (1) JP6556336B2 (zh)
KR (1) KR102175875B1 (zh)
CN (2) CN111132362B (zh)
RU (1) RU2693293C1 (zh)
WO (1) WO2017036246A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109687945A (zh) * 2017-10-19 2019-04-26 华为技术有限公司 帧的传输方法及相关设备
WO2019213798A1 (zh) * 2018-05-07 2019-11-14 南通朗恒通信技术有限公司 一种被用于无线通信的用户设备、基站中的方法和装置
JP2020523846A (ja) * 2017-06-12 2020-08-06 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 無線通信ネットワークにおいて通信を実施するための技法
WO2021139807A1 (en) * 2020-01-10 2021-07-15 Huawei Technologies Co., Ltd. Modulation and coding for multiple resource units in wireless network
CN114363999A (zh) * 2021-12-10 2022-04-15 天翼物联科技有限公司 物联网下行指令发送方法、装置及存储介质
CN117641595A (zh) * 2024-01-11 2024-03-01 东莞市满佳电子科技有限公司 基于物联网的充电控制方法

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10405312B2 (en) * 2015-07-22 2019-09-03 Futurewei Technologies, Inc. System and method for transmissions with frequency diversity
CN111132362B (zh) * 2015-09-02 2024-06-28 华为技术有限公司 一种物联网通信方法、网络侧设备及物联网终端
CN114826526B (zh) * 2015-12-18 2024-12-31 弗劳恩霍夫应用研究促进协会 无线通信系统中具有缩短的端到端延时的数据信号传输
US10958378B2 (en) * 2017-03-28 2021-03-23 Lg Electronics Inc. Method for communication apparatus processing an in-band emission interference signal when the communication apparatus operating in FDR mode tranceives signals using FDM manner
CN107197443B (zh) * 2017-06-21 2020-09-25 深圳市盛路物联通讯技术有限公司 一种基于物联网的数据传输控制方法及系统
EP3641169A4 (en) * 2017-07-27 2020-06-17 Huawei Technologies Co., Ltd. DATA PROCESSING METHOD, OPTICAL LINE TERMINAL, OPTICAL NETWORK UNIT, AND SYSTEM
CN109640396B (zh) * 2017-10-09 2022-07-15 中兴通讯股份有限公司 信号传输方法、相应设备及存储介质
CN107947829B (zh) * 2017-12-27 2023-07-25 上海道生物联技术有限公司 一种结合扩频和窄带mimo的时分双工通信系统及方法
US10952084B2 (en) * 2018-03-08 2021-03-16 Qualcomm Incorporated Interference management for spectrum sharing
CN108712418B (zh) * 2018-05-18 2021-07-27 深圳昂瑞微电子技术有限公司 一种接收机
CN110798293B (zh) * 2018-08-02 2023-03-10 华为技术有限公司 物理层聚合过程协议数据单元的通信方法和相关装置
CN110913493B (zh) * 2018-09-18 2023-04-07 中国电信股份有限公司 数据上报方法和系统、核心网网元和计算机可读存储介质
TR201820700A2 (tr) * 2018-12-27 2020-07-21 Univ Istanbul Medipol Ultra güveni̇li̇r ve düşük geci̇kmeli̇ i̇leti̇şi̇m si̇stemleri̇ne yöneli̇k adapti̇f sönümlenme faktörü i̇le tek taşiyicili i̇leti̇m
CN112134712B (zh) * 2019-06-25 2021-12-31 华为技术有限公司 一种信号处理方法以及相关设备
EP4007069A4 (en) * 2019-07-31 2023-01-25 NEC Corporation WIRELESS COMMUNICATION DEVICE AND WIRELESS COMMUNICATION METHOD
CN112583562B (zh) * 2019-09-30 2022-08-26 华为技术有限公司 数据传输的方法与装置
WO2025208624A1 (en) * 2024-04-05 2025-10-09 Qualcomm Incorporated Physical interface structure design for ambient internet of things device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102355741A (zh) * 2011-08-04 2012-02-15 中国电信股份有限公司 远程控制系统、方法和局端接入设备
CN102769913A (zh) * 2011-05-04 2012-11-07 普天信息技术研究院有限公司 机器类型通信设备分组上传数据的方法和物联网系统
CN103916178A (zh) * 2009-09-29 2014-07-09 北京新岸线移动多媒体技术有限公司 数据发送和数据接收方法
WO2015076861A1 (en) * 2013-11-19 2015-05-28 Intel IP Corporation Master station and method for high-efficiency wi-fi (hew) communication using multi-device hew preamble

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3581286B2 (ja) * 2000-01-19 2004-10-27 松下電器産業株式会社 Ｏｆｄｍ送信装置、ｏｆｄｍ受信装置および信号割当方法
CN101136894B (zh) 2007-03-23 2012-11-28 中兴通讯股份有限公司 可扩展的ofdm及ofdma带宽分配的方法和系统
JP4999893B2 (ja) * 2009-08-06 2012-08-15 シャープ株式会社 無線通信システム、基地局装置、移動局装置および無線通信方法
CN102291845B (zh) * 2010-06-21 2016-03-30 中兴通讯股份有限公司 随机接入方法及系统
CN102547581B (zh) * 2010-12-17 2015-04-15 北京创毅视讯科技有限公司 一种物联网的网内数据交互方法及系统
US9485075B2 (en) * 2011-04-29 2016-11-01 Futurewei Technologies Inc. Method and system for transmission and reception of signals and related method of signaling
CN103001749B (zh) * 2011-09-13 2016-03-30 华为技术有限公司 传输数据的方法、物联网设备和网络侧设备
US8594023B2 (en) * 2011-12-16 2013-11-26 International Business Machines Corporation Quasi-dynamic spectrum access for internet of things (IOT) applications
US9591429B2 (en) 2012-05-11 2017-03-07 Qualcomm Incorporated Methods and apparatus for managing machine-type communications
CN105706522A (zh) * 2013-10-29 2016-06-22 Lg电子株式会社 发送数据的方法以及使用该方法的装置
US20150173109A1 (en) * 2013-12-16 2015-06-18 Intel Corporation Apparatus, method and system of communicating via an application service platform (asp) session
EP3132583B1 (en) * 2014-04-16 2020-08-26 NXP USA, Inc. Signal field length indication in a high efficiency wireless local area network (wlan)
US9854520B2 (en) * 2015-01-20 2017-12-26 Intel IP Corporation Power saving channel access for wireless devices in dense wireless networks
US9826069B2 (en) * 2015-01-27 2017-11-21 Intel IP Corporation Wireless device, method, and computer readable media restriction of upload traffic in a high-efficiency wireless local area network
CN111132362B (zh) * 2015-09-02 2024-06-28 华为技术有限公司 一种物联网通信方法、网络侧设备及物联网终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103916178A (zh) * 2009-09-29 2014-07-09 北京新岸线移动多媒体技术有限公司 数据发送和数据接收方法
CN102769913A (zh) * 2011-05-04 2012-11-07 普天信息技术研究院有限公司 机器类型通信设备分组上传数据的方法和物联网系统
CN102355741A (zh) * 2011-08-04 2012-02-15 中国电信股份有限公司 远程控制系统、方法和局端接入设备
WO2015076861A1 (en) * 2013-11-19 2015-05-28 Intel IP Corporation Master station and method for high-efficiency wi-fi (hew) communication using multi-device hew preamble

Non-Patent Citations (1)

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

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11582701B2 (en) 2017-06-12 2023-02-14 Telefonaktiebolaget Lm Ericsson (Publ) Technique for performing clear channel assessments in a wireless communication network
JP2020523846A (ja) * 2017-06-12 2020-08-06 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 無線通信ネットワークにおいて通信を実施するための技法
US11057844B2 (en) 2017-06-12 2021-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Technique for performing clear channel assessments in a wireless communication network
JP7175926B2 (ja) 2017-06-12 2022-11-21 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 無線通信ネットワークにおいて通信を実施するための技法
CN109687945B (zh) * 2017-10-19 2021-11-30 华为技术有限公司 帧的传输方法及相关设备
CN109687945A (zh) * 2017-10-19 2019-04-26 华为技术有限公司 帧的传输方法及相关设备
WO2019213798A1 (zh) * 2018-05-07 2019-11-14 南通朗恒通信技术有限公司 一种被用于无线通信的用户设备、基站中的方法和装置
WO2021139807A1 (en) * 2020-01-10 2021-07-15 Huawei Technologies Co., Ltd. Modulation and coding for multiple resource units in wireless network
US11115149B2 (en) 2020-01-10 2021-09-07 Huawei Technologies Co., Ltd. Modulation and coding for multiple resource units in wireless network
US11606164B2 (en) 2020-01-10 2023-03-14 Huawei Technologies Co., Ltd. Modulation and coding for multiple resource units in wireless network
CN114363999A (zh) * 2021-12-10 2022-04-15 天翼物联科技有限公司 物联网下行指令发送方法、装置及存储介质
CN114363999B (zh) * 2021-12-10 2023-10-03 天翼物联科技有限公司 物联网下行指令发送方法、装置及存储介质
CN117641595A (zh) * 2024-01-11 2024-03-01 东莞市满佳电子科技有限公司 基于物联网的充电控制方法

Also Published As

Publication number Publication date
CN106487573B (zh) 2020-01-10
US11388035B2 (en) 2022-07-12
US20200304358A1 (en) 2020-09-24
RU2693293C1 (ru) 2019-07-02
KR102175875B1 (ko) 2020-11-06
US20180191545A1 (en) 2018-07-05
EP3337096A4 (en) 2018-07-25
JP2018533252A (ja) 2018-11-08
CN111132362B (zh) 2024-06-28
CN111132362A (zh) 2020-05-08
EP3337096B1 (en) 2021-03-31
JP6556336B2 (ja) 2019-08-07
US10616026B2 (en) 2020-04-07
EP3337096A1 (en) 2018-06-20
CN106487573A (zh) 2017-03-08
KR20180048765A (ko) 2018-05-10

Similar Documents

Publication Publication Date Title
CN106487573B (zh) 一种物联网通信方法、网络侧设备及物联网终端
EP3101833A1 (en) Wireless apparatus for high-efficiency (he) communication with additional subcarriers
CN106664177B (zh) 用于发送数据的方法和装置
US10158516B2 (en) Method and apparatus for transmitting data block
US10097250B2 (en) Method for transmitting a PPDU in a transmission bandwidth and device for same
CN103139125A (zh) 下行数据发送、接收方法及基站与用户终端
EP3466006B1 (en) A method for communicating non-ofdm data in a wireless ofdm communication system
RU2737000C1 (ru) Точка доступа, станция, способы и компьютерные программы
KR20090064359A (ko) 대역폭 비대칭 통신 시스템
EP3161990A1 (en) Bandwidth signaling
EP3162152A2 (en) Method and device for transmitting data
KR101909123B1 (ko) 복수의 서브밴드를 이용한 데이터 전송 방법 및 이를 이용한 기기
CN103477598B (zh) 一种基于ofdm的数据传输方法和发射站点
US11902074B2 (en) System and method to generate a waveform in a communication network
BR112018004089B1 (pt) Método de comunicação de internet das coisas, dispositivo de lado de rede, e terminal de internet das coisas

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: 16840675

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018511197

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016840675

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20187008343

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2018111215

Country of ref document: RU

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112018004089

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112018004089

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20180228