Methods, apparatus, and systems for uncrewed/unmanned aerial system (uas) event/exception and policy control exposure services

Patent metadata

Field	Value
Publication number	US-2024187861-A1
Application number	US-202218285617-A
Country	US
Kind code	A1
Filing date	Apr 1, 2022
Priority date	Apr 5, 2021
Publication date	Jun 6, 2024
Grant date	—

Abstract

Methods, apparatus and systems are disclosed. In one embodiment, a method, implemented by a UAS control entity includes the UAS control entity: receiving, from a USS/UTM, a monitoring request including information indicating a uncrewed/unmanned aerial vehicle (UAV) identifier to be monitored and one or more types of events the USS/UTM is subscribing to; subscribing with a network entity serving a UAV associated with the UAV identifier to be monitored based on the information indicating a type of event; receiving a published event report from the network entity, the publish event report including information indicating the UAV identifier, the event type and meta information related to an event; and sending the published event report received to the USS/UTM.

First claim

1 . A method implemented by a Network Entity (NE) to control a revocation of a connection of an Unmanned Aerial Vehicle (UAV), the method comprising:
receiving a monitoring request, the monitoring request including: (1) a UAV identifier (ID); (2) information indicating a network event of a first type to be tracked for the UAV and (3) information indicating one or more rules or triggering conditions associated with the network event of the first type to trigger a connection revocation action; detecting the network event of the first type associated with the UAV ID; determining that the connection revocation action is to be performed based on the indicated one or more rules or triggering conditions associated with the network event of the first type; and sending a message to control performance of the connection revocation action to revoke the connection of the UAV with a UAV control entity.

2 . The method of claim 1 , wherein:
the NE includes an Unmanned Aerial System (UAS) Network Function (NF); and the reception of the monitoring request is from the UAV control entity.

3 . The method of claim 1 , wherein:
the network event of the first type is one of a plurality of types of events; and the plurality of types of events including any of: (1) a service available/authorized event type; (2) an abnormal event type; (3) a registration event type; (4) a deregistration event type; (5) an aerial subscription revocation event type; (6) an aerial subscription event type; (7) a network slice authorization event type; (8) a network slice revocation event type; (9) a connectivity service authorization event; and (10) a link Quality of Service (QOS) variation event.

4 . The method of claim 1 , wherein:
the determining that the connection revocation action is to be performed includes one of:
determining that the connection revocation action without a revocation confirmation is to be performed based on the indicated one or more rules and/or triggering conditions; or
determining that the connection revocation action is to be performed after the revocation confirmation is received by:
sending a confirmation request to any of: (1) a UAS Service Supplier (USS) and/or (2) a UAS Traffic Management (UTM), and
receiving a confirmation response including confirmation information such that the determining that the connection revocation action is to be performed is further based on the received confirmation information.

5 . The method of claim 1 , wherein sending the message to control performance of the connection revocation action includes sending, to a further NE, a command to revoke the connection of the UAV.

6 . The method of claim 5 , wherein the further NE includes any of: (1) an Access and Mobility Management Function (AMF) or (2) a Session Management Function (SMF).

7 . The method of claim 1 , wherein the UAV ID corresponds to any of: (1) a UAV, (2) an aerial drone, (3) an autonomous vehicle, and (4) an emergency vehicle.

8 . The method of claim 1 , wherein the indicated one or more rules or triggering conditions associated with the network event of the first type relate to any of: (1) a subscription authorization revocation, (2) a subscription authorization change, (3) a network slice authorization revocation, and (4) a network slice authorization change.

9 . The method of claim 1 , comprising:
sending a confirmation request to an Unmanned Aerial System (UAS) entity; and receiving, from the UAS entity, a confirmation response including confirmation information indicating to perform the connection revocation of the UAV; wherein the sending of the message to control performance of the connection revocation action is performed after reception of the confirmation response indicating to perform the connection revocation.

10 - 19 . (canceled)

20 . A network entity (NE) comprising:
circuitry, including any of a processor, memory, transmitter and receiver, the circuitry configured to: receive a monitoring request, the monitoring request including: (1) a UAV identifier (ID); (2) information indicating a network event of a first type to be tracked for the UAV and (3) information indicating one or more rules or triggering conditions associated with the network event of the first type to trigger a connection revocation action; detect the network event of the first type associated with the UAV ID; determine that the connection revocation action is to be performed based on the one or more rules or triggering conditions associated with the network event of the first type; and
send a message to control performance of the connection revocation action to revoke the connection of the UAV with a UAV control entity.

21 . The NE of claim 20 , wherein:
the NE includes an Unmanned Aerial System (UAS) Network Function (NF); and the reception of the monitoring request is from the UAV control entity.

22 . The NE of claim 20 , wherein:
the network event of the first type is one of a plurality of types of events; and the plurality of types of events including any of: (1) a service available/authorized event type; (2) an abnormal event type; (3) a registration event type; (4) a deregistration event type; (5) an aerial subscription revocation event type; (6) an aerial subscription event type; (7) a network slice authorization event type; (8) a network slice revocation event type; (9) a connectivity service authorization event; and (10) a link Quality of Service (QOS) variation event.

23 . The NE of claim 20 , wherein, to determine that the connection revocation action is to be performed, the circuitry is configured to one of:
determine that the connection revocation action without a revocation confirmation is to be performed based on the indicated one or more rules and/or triggering conditions; or determine that the connection revocation action is to be performed after the revocation confirmation is received by:
sending a confirmation request to any of: (1) a UAS Service Supplier (USS) and/or (2) a UAS Traffic Management (UTM), and
receiving a confirmation response including confirmation information such that the determining that the connection revocation action is to be performed is further based on the received confirmation information.

24 . The NE of claim 20 , wherein the circuitry is configured to send, to a further NE, a command to revoke the connection of the UAV.

25 . The NE of claim 24 , wherein the further NE includes any of: (1) an Access and Mobility Management Function (AMF) and/or (2) a Session Management Function (SMF).

26 . The NE of claim 20 , wherein the UAV ID corresponds to any of: (1) a UAV, (2) an aerial drone, (3) an autonomous vehicle, and (4) an emergency vehicle.

27 . The NE of claim 20 , wherein the indicated one or more rules or triggering conditions associated with the network event of the first type relate to any of: (1) a subscription authorization revocation, (2) a subscription authorization change, (3) a network slice authorization revocation, and (4) a network slice authorization change.

28 . The NE of claim 20 , wherein the circuitry is configured to:
send a confirmation request to an Unmanned Aerial System (UAS) entity; and receive, from the UAS entity, a confirmation response including confirmation information indicating to perform the connection revocation of the UAV; wherein the message to control performance of the connection revocation action is sent after reception of the confirmation response indicating to perform the connection revocation.

Assignees

• Interdigital Patent Holdings Inc

Inventors

• Ferdi Samir
• Wang Guanzhou
• Monrad Atle

Classifications

• H04W12/082 Primary

  using revocation of authorisation · CPC title

• H04W12/009

  specially adapted for networks, e.g. wireless sensor networks, ad-hoc networks, RFID networks or cloud networks · CPC title

• H04W12/60

  Context-dependent security · CPC title

• H04W60/04

  using triggered events · CPC title

• H04W60/06

  De-registration or detaching · CPC title