# US 2018/0324580 A1 · Exchanging a message including drone-coupled capability information between a drone-coupled user equipment and a component of a terrestrial wireless communication subscriber network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0324580 A1
- Document ID: US20180324580A1
- Status: Published application
- Kind: A1
- Application number: 15/969,738
- Filed: 2018-05-02
- Published: 2018-11-08
- Earliest claimed: 2017-05-03
- Assignees: QUALCOMM Incorporated
- Applicants: QUALCOMM Incorporated
- Inventors: Umesh PHUYAL; Alberto RICO ALVARINO; Haris ZISIMOPOULOS; Masato KITAZOE
- Web page: https://patentgrep.com/patent/US20180324580A1

## CPC

- H04W 8/24: Transfer of terminal data
- H04B 7/15: Active relay systems
- H04B 7/15507: {Relay station based processing for cell extension or control of coverage area, (network planning with network coordinated processing with regard to cell extension H04W16/26; network topologies using dedicated repeater stations H04W84/047; terminal devices adapted for relaying to or from an other terminal H04W88/04)}
- H04B 7/18504: {Aircraft used as relay or high altitude atmospheric platform}
- H04W 48/16: Discovering, processing access restriction or access information
- H04W 48/18: Selecting a network or a communication service
- B64U 10/13: Flying platforms
- B64U 2101/20: for use as communications relays, e.g. high-altitude platforms
- B64U 2101/31: for surveillance
- B64U 2101/64: for parcel delivery or retrieval
- B64U 2201/20: Remote controls
- H04W 4/02: Services making use of location information
- H04W 36/08: Reselecting an access point
- H04W 48/20: Selecting an access point
- H04W 76/10: Connection setup
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04B: TRANSMISSION
- B64U: UNMANNED AERIAL VEHICLES [UAV]; EQUIPMENT THEREFOR

## Abstract

In an embodiment, a drone-coupled UE transmits a message to a network component (e.g., eNB) of a terrestrial wireless communication subscriber network that identifies a drone-coupled capability information of the drone-coupled UE, the drone-coupled capability information being configured to indicate, to the network component, that the drone-coupled UE is capable of engaging in a flying state. The network component receives the message and determines that the drone-coupled UE is capable of engaging in a flying state based on the received message.

## Claims

### Claim 1

A method of operating a drone-coupled user equipment (UE), comprising:
transmitting a message to a network component of a terrestrial wireless communication subscriber network that identifies a drone-coupled capability information of the drone-coupled UE, the drone-coupled capability information being configured to indicate, to the network component, that the drone-coupled UE is capable of engaging in a flying state.

### Claim 2 (depends on 1)

The method of claim 1, wherein the transmitting occurs during an Attach procedure between the drone-coupled UE and the terrestrial wireless communication subscriber network.

### Claim 3 (depends on 2)

The method of claim 2, wherein the message is a UE capability signaling message that indicates the drone-coupled capability information of the drone-coupled UE.

### Claim 4 (depends on 1)

The method of claim 1, wherein the transmitting occurs during a reconfiguration procedure that occurs after an Attach procedure between the drone-coupled UE and the terrestrial wireless communication subscriber network.

### Claim 5 (depends on 1)

The method of claim 1, wherein the message identifies a UE category that is reserved for drone-coupled UEs.

### Claim 6 (depends on 1)

The method of claim 1, wherein the message includes a subscriber identifier (ID) and/or a certification ID that is reserved for drone-coupled UEs.

### Claim 7 (depends on 1)

The method of claim 1, wherein the message includes a predefined key or identification code using Non-Access Stratum (NAS) signaling.

### Claim 8 (depends on 1)

The method of claim 1, wherein the network component is an access network component of the terrestrial wireless communication subscriber network.

### Claim 9 (depends on 1)

The method of claim 1, wherein the network component is a core network component of the terrestrial wireless communication subscriber network.

### Claim 10

A method of operating a network component of a terrestrial wireless communication subscriber network, comprising:
receiving a message from a drone-coupled user equipment (UE) that identifies a drone-coupled capability information of the drone-coupled UE; and
determining that the drone-coupled UE is capable of engaging in a flying state based on the received message.

### Claim 11 (depends on 10)

The method of claim 10, wherein the receiving occurs during an Attach procedure between the drone-coupled UE and the terrestrial wireless communication subscriber network.

### Claim 12 (depends on 11)

The method of claim 11, wherein the message is a UE capability signaling message that indicates the drone-coupled capability information of the drone-coupled UE.

### Claim 13 (depends on 10)

The method of claim 10, wherein the receiving occurs during a reconfiguration procedure that occurs after an Attach procedure between the drone-coupled UE and the terrestrial wireless communication subscriber network.

### Claim 14 (depends on 10)

The method of claim 10, wherein the message identifies a UE category that is reserved for drone-coupled UEs.

### Claim 15 (depends on 10)

The method of claim 10, wherein the message includes a subscriber identifier (ID) and/or a certification ID that is reserved for drone-coupled UEs.

### Claim 16 (depends on 10)

The method of claim 10, wherein the message includes a predefined key or identification code using Non-Access Stratum (NAS) signaling.

### Claim 17 (depends on 10)

The method of claim 10, wherein the network component is an access network component of the terrestrial wireless communication subscriber network.

### Claim 18 (depends on 10)

The method of claim 10, wherein the network component is a core network component of the terrestrial wireless communication subscriber network.

### Claim 19 (depends on 10)

The method of claim 10, further comprising:
implementing a drone-coupled status protocol or a non-drone-coupled status protocol based on the determining.

### Claim 20 (depends on 19)

The method of claim 19, wherein the non-drone-coupled status protocol corresponds to the terrestrial wireless communication subscriber network providing the same level of service to the drone-coupled UE as is provided by the terrestrial wireless communication subscriber network to one or more non-drone-coupled UEs.

### Claim 21 (depends on 19)

The method of claim 19, wherein the drone-coupled status protocol includes:
refusing to admit the drone-coupled UE to the terrestrial wireless communication subscriber network based on the drone-coupled UE being unauthorized for drone-coupled service.

### Claim 22 (depends on 19)

The method of claim 19, wherein the drone-coupled status protocol includes:
refusing to admit the drone-coupled UE to the terrestrial wireless communication subscriber network based on the terrestrial wireless communication subscriber network being unable to provide and/or unauthorized to provide drone-coupled service to any drone-coupled UE.

### Claim 23 (depends on 19)

The method of claim 19, wherein the drone-coupled status protocol includes:
admitting the drone-coupled UE to the terrestrial wireless communication subscriber network for a subset of drone-coupled services while the drone-coupled UE is not engaged in a flying state, the subset of drone-coupled services including at least one service that is not available to non-drone-coupled UEs.

### Claim 24 (depends on 19)

The method of claim 19, wherein the drone-coupled status protocol includes:
implementing a power control scheme for the drone-coupled UE that is different from power control schemes used for non-drone-coupled UEs.

### Claim 25 (depends on 19)

The method of claim 19, wherein the drone-coupled status protocol includes:
implementing a charging or pricing scheme for the drone-coupled UE that is different than charging and/or pricing schemes used for non-drone-coupled UEs.

### Claim 26

A drone-coupled user equipment (UE), comprising:
a memory;
at least one processor coupled to the memory and a wireless communications interface and configured to:
transmit a message to a network component of a terrestrial wireless communication subscriber network that identifies a drone-coupled capability information of the drone-coupled UE, the drone-coupled capability information being configured to indicate, to the network component, that the drone-coupled UE is capable of engaging in a flying state.

### Claim 27 (depends on 26)

The drone-coupled UE of claim 26,
wherein the message is a UE capability signaling message that indicates the drone-coupled capability information of the drone-coupled UE,
wherein the message identifies a UE category that is reserved for drone-coupled UEs,
wherein the message includes a subscriber identifier (ID) and/or a certification ID that is reserved for drone-coupled UEs, and/or
wherein the message includes a predefined key or identification code using Non-Access Stratum (NAS) signaling.

### Claim 28

A network component of a terrestrial wireless communication subscriber network, comprising:
a memory; and
at least one processor coupled to the memory and at least one communications interface and configured to:
receive a message from a drone-coupled user equipment (UE) that identifies a drone-coupled capability information of the drone-coupled UE; and
determine that the drone-coupled UE is capable of engaging in a flying state based on the received message.

### Claim 29 (depends on 28)

The network component of claim 28,
wherein the message is a UE capability signaling message that indicates the drone-coupled capability information of the drone-coupled UE,
wherein the message identifies a UE category that is reserved for drone-coupled UEs,
wherein the message includes a subscriber identifier (ID) and/or a certification ID that is reserved for drone-coupled UEs, and/or
wherein the message includes a predefined key or identification code using Non-Access Stratum (NAS) signaling.

### Claim 30 (depends on 28)

The network component of claim 28, wherein the at least one processor is configured to implement a drone-coupled status protocol or a non-drone-coupled status protocol based on the determination.
