IP Library Patent Application 18949358
Patent Application
App. No. 18/949,358

SYSTEMS AND METHODS FOR SECURE AND RELIABLE COMMAND AND CONTROL OF IN-FLIGHT UNCREWED AERIAL VEHICLES VIA PUBLIC LAND MOBILE NETWORKS

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
18/949,358
Abstract

Systems and methods for supporting multiple uncrewed aerial vehicle (UAV) Service Suppliers (multi-USS) are described. The methods may be performed by a wireless transmit/receive unit (WTRU) including a UAV application enabling (UAE) client located in the UAV with the method performed with the UAV in-flight. Steps may include: sending a registration request to a UAE server, the registration request including an indication of multi-USS capability; receiving a registration response message that includes an indication that the UAE server supports multi-USS capability; receiving a multi-USS configuration request that includes multi-USS configuration parameters related to conditions under which the UAE client may initiate a USS change and a list of allowed USSs; sending a multi-USS configuration response; and performing a multi-USS change and sending a multi-USS change notification based on the multi-USS configuration parameters.

Claims (28)

1 . A method performed by an uncrewed aerial vehicle (UAV) application enabling (UAE) server for supporting multiple UAV system (UAS) Service Suppliers (multi-USS), the method comprising:

receiving a registration request from a USS including an indication of multi-USS capability for a UAE client;

sending a registration response message;

receiving a USS change request including UAV identity; and

sending a USS configuration request to the UAE client that includes a multi-USS policy comprising an allowed USS.

2 . The method of claim 1 , wherein the multi-USS policy further includes serving USS information.

3 . The method of claim 1 , wherein the USS configuration request is a request to delete a first USS configuration and the method further comprises removing the first USS configuration if the request to delete is associated with a USS that matches a USS associated with the UAE.

4 . The method of claim 3 , wherein the USS associated with the UAE holds a subscription for the UAV.

5 . The method of claim 3 , wherein the USS associated with the UAE previously authenticated and authorized the UAV.

6 . The method of claim 1 , wherein the multi-USS configuration request is a request to add a second USS configuration and the method further comprises storing the second USS configuration.

7 . The method of claim 1 , wherein the USS change request includes a cause for the multi-USS change.

8 . The method of claim 1 , wherein the multi-USS policy includes a rule for initiating a USS change wherein only a first USS can initiate a change.

9 . The method of claim 1 , wherein the multi-USS policy includes a rule allowing any allowed USS to initiate a USS change when a connection is lost with a first USS.

10 . The method of claim 1 , wherein the multi-USS policy further comprises a geographical area in which the allowed USS is active.

11 . An uncrewed aerial vehicle (UAV) application enabling (UAE) server for supporting multiple UAV system (UAS) Service Suppliers (multi-USS), the UAE server configured to:

receive a registration request from a USS including an indication of multi-USS capability for a UAE client;

send a registration response message;

receive a USS change request including UAV identity; and

send a USS configuration request to the UAE client that includes a multi-USS policy comprising an allowed USS.

12 . The UAE server of claim 11 , wherein the multi-USS policy further includes serving USS information.

13 . The UAE server of claim 11 , wherein the USS configuration request is a request to delete a first USS configuration and the UAE server is further configured to remove the first USS configuration if the request to delete is associated with a USS that matches a USS associated with the UAE.

14 . The UAE server of claim 13 , wherein the USS associated with the UAE holds a subscription for the UAV.

15 . The UAE server of claim 13 , wherein the USS associated with the UAE previously authenticated and authorized the UAV.

16 . The UAE server of claim 11 , wherein the multi-USS configuration request is a request to add a second USS configuration and the UAE server is further configured to store the second USS configuration.

17 . The UAE server of claim 11 , wherein the USS change request includes a cause for the USS change.

18 . The UAE server of claim 11 , wherein the multi-USS policy includes a rule for initiating a USS change wherein only a first USS can initiate a change.

19 . The UAE server of claim 11 , wherein the multi-USS policy includes a rule allowing any allowed USS to initiate a USS change when a connection is lost with a first USS.

20 . The UAE server of claim 11 , wherein the multi-USS policy further comprises a geographical area in which the allowed USS is active.