LoRa Terminal Mobility Reporting for Network Scheduling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional LoRa networks face challenges in timely adjusting network scheduling strategies due to a lack of mobility information about terminal devices, leading to inefficient resource allocation and interaction between terminals and servers.
Innovation Solution
The terminal sends mobility-related state information to the server through MAC command messages, allowing the server to update network scheduling strategies accordingly, including adjustments based on mobile attributes, moving states, and direction information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the server adopts conventional network scheduling mechanisms without mobility information, then the system structure remains simple, but the server cannot timely adjust scheduling strategies according to terminal mobility changes
Solution Approach 1:
The terminal periodically reports its mobility state (stationary or mobile) to the server through uplink messages. The server uses this feedback information to dynamically adjust network scheduling strategies, switching between ADR mechanism and terminal-specific strategies based on the reported state. This feedback loop enables timely adaptation without requiring complex proactive detection mechanisms.
Solution Approach 2:
The terminal proactively reports its mobility state changes to the server in advance. When a terminal transitions from stationary to mobile or vice versa, it sends a notification message to the server before the mobility change fully takes effect, allowing the server to preemptively adjust scheduling parameters and avoid latency in response.
2Productivity
If the server implements real-time mobility state monitoring, then network resource allocation efficiency improves, but energy consumption increases
Solution Approach 1:
Instead of continuous monitoring, the system uses periodic state reporting where terminals transmit mobility state information at predetermined intervals or when state changes occur. This periodic mechanism balances the need for timely scheduling adjustments with energy conservation, as terminals only transmit when necessary rather than continuously monitoring and reporting.
Solution Approach 2:
The terminal autonomously determines and reports its own mobility state based on local detection, without requiring the server to actively query or monitor the terminal's position. This self-service approach reduces uplink traffic and terminal energy consumption while still providing the server with necessary scheduling information.
3Ease of operation
If the server uses ADR mechanism for all terminals, then network management is simplified, but mobile terminals experience suboptimal resource allocation
Solution Approach 1:
The server dynamically switches between ADR mechanism and terminal-specific scheduling strategies based on the terminal's reported mobility state. For stationary terminals, the simplified ADR mechanism is used; for mobile terminals, the server adopts specialized strategies (such as priority-based or location-aware scheduling). This dynamic adaptation maintains network management simplicity while improving resource allocation effectiveness for mobile devices.
Solution Approach 2:
The server applies different scheduling strategies to different terminals based on their individual mobility characteristics. Rather than using a uniform approach for all terminals, the system tailors the scheduling mechanism to each terminal's specific needs (stationary vs. mobile), optimizing resource allocation for each local condition while maintaining overall system simplicity.
Data Source
AI summary
Embodiments of the present disclosure provide methods and devices for communication by a terminal. The method can include: sending a first message to a server, the first message comprising command information, the command information comprising first state information of the terminal, and the first state information comprising at least one of mobile attribute information, moving state information, mobile state start information, stationary state start information, or moving direction state information, wherein the mobile attribute information is used to indicate that the terminal is a mobile terminal, the moving state information is used to indicate that the terminal is in a mobile state, the mobile state start information is used to indicate a transition of the terminal from a stationary state to a mobile state, the stationary state start information is used to indicate a transition of the terminal from a mobile state to a stationary state, and the moving direction information is used to indicate direction information of movement of the terminal; and receiving a second message sent by the server, wherein the second message is used to confirm the at least one of first state information in the command information.