Core-Network Flightpath Server for UAV Handover Data Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems, particularly 5G NR, face challenges in managing and storing flightpath information for unmanned aerial vehicles (UAVs) efficiently, leading to potential loss of context and unavailability of flightpath data during RRC IDLE mode or handovers, which can impact coordination and management of UAVs across different networks.
Innovation Solution
Implementing a Flightpath Server (FP server) within the core network to manage and store flightpath information received from UAVs, user equipment, and external servers, ensuring seamless data availability and coordination across networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If flightpath information is stored at radio access network nodes or access and mobility management functions, then the system can process flightpath data locally, but the context is lost during idle modes or handovers causing unavailability of flightpath data
Solution Approach 1:
The patent introduces a flightpath server as an intermediary component in the core network that receives flightpath information from radio access network nodes and external servers, stores it reliably, and provides it to network entities during idle modes or handovers. This mediator ensures flightpath data persistence and availability without being affected by context loss at individual network nodes.
2Reliability
If a flightpath server is introduced in the core network to ensure data availability, then flightpath information consistency is improved, but the device complexity increases
Solution Approach 1:
The flightpath server is designed to perform multiple functions: receiving flightpath information from various sources (radio access network nodes, external servers), storing it in a centralized database, and providing it to different network entities. This multi-functionality consolidates what would otherwise require multiple separate components, improving reliability while limiting the increase in overall system complexity.
Data Source
AI summary
An apparatus may be a first network entity configured to receive, from a second network entity or a first wireless device, first information regarding a flightpath of at least one wireless device, receive, from the second network entity or the first wireless device, an indication to store second information regarding the flightpath of the at least one wireless device based on the first information, and transmit, to a third network entity based on the second information, third information regarding the flightpath of the at least one wireless device. An apparatus may be a second network entity configured to receive, from a first wireless device, first information regarding a flightpath of at least one wireless device and transmit, to a first network entity, an indication to store second information regarding the flightpath of the at least one wireless device.