Content for TS 23.255 Word version: 19.0.0
7.2 Communications between UAVs within a geographical area
7.2.1 General
7.2.2 Procedures
7.2.2.1 Communications between UAVs within a geographical area using unicast Uu
7.2.3 Information flows
7.2.3.1 UAV application message
...
...
7.2 Communications between UAVs within a geographical area p. 31
7.2.1 General p. 31
This clause describes the procedure for communications between UAVs within a geographical area. The geographical area is from the perspective of the UAV initiating the communication with other UAVs.
The following transport mechanisms can be supported for communications between UAVs within a geographical area:
- Using unicast Uu.
7.2.2 Procedures p. 31
7.2.2.1 Communications between UAVs within a geographical area using unicast Uu p. 31
Figure 7.2.2.1-1 illustrates the procedure for communications between UAVs within a geographical area using unicast Uu.
Pre-conditions:
- The UAE clients of UAVs have successfully registered and connected to the UAE server.
- The SEAL's LM server information is configured at the UAE server.
Figure 7.2.2.1-1: Communications between UAVs within a geographical area using unicast Uu
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Step 1.
The UAE client of UAV sends a UAV application message to the UAE server in order to communicate the payload information of the UAV application message to other UAVs in a range of the location corresponding to the UAV.
Step 2.
The UAE server obtains the other UAV(s) information in the location of the UAV from the LMS as specified in TS 23.434.
Step 3.
Upon receiving the list of other UAV(s), the UAE server sends the payload in UAV application message to each of the UAV via unicast channel.
Step 4.
Upon completing step 3, the UAE server may send an acknowledgement to the UAE client.
7.2.3 Information flows p. 32
7.2.3.1 UAV application message p. 32
Table 7.2.3.1-1 describes the information flow for the UAV application message from UAE client to UAE server and from UAE server to UAE client.
| Information element | Status | Description |
|---|---|---|
| UAV ID | M | The identifier of the UAV (e.g. 3GPP UE ID or CAA level UAV ID) which initiates the UAV application message. |
| Application defined proximity range information (NOTE 2) | M | Description of the range information over which the UAV application message is to be sent. |
| Application Payload (NOTE 1) | M | Application payload that is to be delivered to the other UAVs |
|
NOTE 1:
This IE is provided by the UAS application specific client and its details are out of scope of 3GPP.
NOTE 2:
This IE is not included when the UAV application message is sent from UAE server to UAE client.
|
||
