IoT Server Coordinated Radio Resource Scheduling for Low Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication technologies fail to meet the low-latency requirements in Internet of Things (IoT) applications, such as V2X and industrial IoT, where timely communication is critical for scenarios like emergency vehicle collision avoidance and industrial system maintenance.
Innovation Solution
A communication resource scheduling method where an IoT application server coordinates with a radio transceiver node to prioritize and efficiently allocate radio resources, enabling coordinated radio resource scheduling based on service requirements, reducing latency by actively allocating resources without the need for terminal requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If current wireless communication technology is used, then device complexity is reduced, but communication latency increases and cannot meet low-latency requirements
Solution Approach 1:
The patent introduces an IoT application server as an intermediary between the terminal and the radio transceiver node. This server receives scheduling requests from terminals, determines whether coordinated scheduling is needed based on service requirements, and sends activation requests to the radio transceiver node. This intermediary structure enables low-latency coordinated scheduling without requiring complex direct coordination between terminals and network infrastructure.
2Loss of time
If terminal requests radio resource actively, then resource allocation responsiveness improves, but communication latency increases due to request-response cycle
Solution Approach 1:
The patent implements preliminary action by having the radio transceiver node proactively allocate radio resources to terminals before the terminals actually need to transmit data. When the IoT application server activates coordinated scheduling for a terminal, the radio transceiver node pre-allocates resources and notifies the terminal in advance. This eliminates the traditional request-response cycle and reduces communication latency significantly.
3Loss of time
If coordinated radio resource scheduling is implemented, then communication latency is reduced, but system complexity increases
Solution Approach 1:
The IoT application server serves as a centralized coordinator that simplifies the overall system architecture. It receives service requirement information from terminals, makes scheduling decisions based on pre-configured rules or algorithms, and manages the activation/deactivation of coordinated scheduling for multiple terminals. This centralized approach reduces complexity compared to distributed coordination mechanisms while achieving low latency.
Solution Approach 2:
The system dynamically changes the scheduling mode parameter based on service requirements. When low-latency communication is needed, the IoT application server activates coordinated scheduling mode for specific terminals. When normal communication suffices, it deactivates the coordinated scheduling. This parameter change approach allows the system to achieve low latency only when necessary, reducing overall system complexity.
Data Source
AI summary
When an Internet of things application server determines, based on a service requirement and a service scenario, to start coordinated radio resource scheduling on a terminal, the Internet of things application server sends a coordinated radio resource scheduling activation request to a radio transceiver node, to request the radio transceiver node to perform coordinated radio resource scheduling on the terminal based on a requirement of the Internet of things application server, and after receiving the request, the radio transceiver node allocates a radio resource to the terminal at a higher priority or higher efficiency. If the terminal does not need to apply for the radio resource, the radio transceiver node actively allocates the radio resource to the terminal in order to reduce a radio communication latency of the terminal and implement a low-latency communication requirement in a specific service scenario.