IoT Terminal Scheduling via WLAN Resource Units
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IoT communication systems face conflicts between IoT terminals and WLAN devices due to differences in channel bandwidths, leading to inefficiencies in scheduling and coordination, particularly as IoT terminals cannot directly receive or send WLAN signals.
Innovation Solution
The proposed solution involves a network side device that schedules IoT terminals by using a downlink data frame with a legacy preamble, a high efficiency wireless local area network (HEW) preamble, and a data field, where the data field includes at least one resource unit (RU) for IoT communication, allowing for the transmission of IoT frames with specific subcarrier resource allocation to avoid conflicts with WLAN devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by stationary object
If IoT terminals use a channel bandwidth of 1 to 2 MHz to reduce power consumption and costs, then power consumption and costs are reduced, but the IoT terminals cannot directly receive or send WLAN signals, leading to conflicts between IoT terminals and WLAN devices
Solution Approach 1:
The patent segments the channel bandwidth into different portions: a first bandwidth portion for IoT terminals (1-2 MHz) and a second bandwidth portion for WLAN devices (20 MHz or more). This segmentation allows each type of device to operate in its appropriate bandwidth range, enabling IoT terminals to maintain low power consumption while preventing conflicts with WLAN devices that operate in wider bandwidths.
2Device complexity
If IoT terminals use a channel bandwidth of 1 to 2 MHz to reduce complexity, then device complexity is reduced, but the IoT terminals cannot be scheduled by WLAN network side devices, leading to coordination conflicts
Solution Approach 1:
The patent introduces a network side device as an intermediary that performs frequency conversion. The network side device receives signals from WLAN devices in the second bandwidth portion, converts them to the first bandwidth portion, and forwards them to IoT terminals. This intermediary function enables IoT terminals with simple architecture to communicate with WLAN devices without requiring the terminals to support wide bandwidths directly.
3Productivity
If WLAN devices use a channel bandwidth of at least 20 MHz for high efficiency communication, then communication efficiency is improved, but IoT terminals cannot directly receive or send these signals, causing scheduling conflicts
Solution Approach 1:
The patent segments the communication system into two parts: WLAN devices operating in a second bandwidth portion (20 MHz or more) for high efficiency communication, and IoT terminals operating in a first bandwidth portion (1-2 MHz) for low complexity operation. The network side device acts as a bridge that performs frequency conversion between these segmented bandwidth portions, allowing each component to operate at its optimal complexity level while maintaining overall system efficiency.
Data Source
AI summary
The present disclosure discloses an Internet of Things communication method. In the present disclosure, a downlink data frame sent by the network side device includes a legacy preamble, a HEW preamble, and a data field; a subcarrier resource that is corresponding to the data field in a frequency domain includes at least one resource unit RU; and the RU is used to send a downlink IoT frame to the IoT terminal, where the downlink IoT frame includes an IoT preamble and an IoT data field, 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 downlink data between the network side device and the IoT terminal. According to the present disclosure, a network side device in a WLAN can schedule an IoT terminal, thereby reducing a conflict risk in an IoT communication process.