Content for TS 23.255 Word version: 19.0.0
7.1a UAE layer registration
7.1a.1 General
7.1a.2 Procedures
7.1a.2.1 UAS UE registration
7.1a.2.2 UAS UE deregistration
7.1a.2.3 UAS UE registration update
7.1a.3 Information flows
7.1a.3.1 Registration request
7.1a.3.2 Registration response
7.1a.3.3 Deregistration request
7.1a.3.4 Deregistration response
7.1a.3.5 Registration update request
7.1a.3.6 Registration update response
...
...
7.1a UAE layer registration p. 28
7.1a.1 General p. 28
The UAE capabilities provide support for registering UAV/UAV-C at the UAE server. The UAE server uses the registration information to distribute UAE layer messages or UAS application specific layer messages to the appropriate UAS UEs, and to distinguish what capabilities that can be provided to different UAE clients.
7.1a.2 Procedures p. 28
7.1a.2.1 UAS UE registration p. 28
7.1a.2.1.1 General p. 28
This clause describes the procedure for UAS UE (UAV/UAV-C) to register with the UAE server.
7.1a.2.1.2 Procedure p. 28
Pre-conditions:
- The UAE client has discovered the UAE server and is aware of the address of the UAE server (e.g. FDQN).
- The UAV/UAV-C has already been assigned with the UAV ID.
Figure 7.1a.2.1.1-1: Procedure for registering the UAE client at the UAE server
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Step 1.
The UAE client sends a registration request to the UAE server.
Step 2.
The UAE server performs authentication and authorization check (e.g. based on pre-provisioned security information or by interacting with UAS application specific server (e.g. USS/UTM)).
Step 3.
The UAE server sends a registration response to the UAE client indicating success or failure of the registration.
7.1a.2.2 UAS UE deregistration p. 29
7.1a.2.2.1 General p. 29
This clause describes the procedures for UAS UE (UAV/UAV-C) to deregister at the UAE server.
7.1a.2.2.2 Procedure p. 29
Pre-condition:
- The UAE client has already registered with the UAE server as described in subclause 7.1a.2.1.
Figure 7.1a.2.2.2-1: Procedure for deregistering the UAE client at the UAE server
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
7.1a.2.3 UAS UE registration update p. 29
7.1a.2.3.1 General p. 29
This clause describes the procedures for UAS UE (UAV/UAV-C) to update its registration with the UAE server.
7.1a.2.3.2 Procedure p. 29
Pre-conditions:
- The UAE client has already registered with the UAE server as described in subclause 7.1a.2.1.
Figure 7.1a.2.3.1-1: Procedure for registration update by the UAE client at the UAE server
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
7.1a.3 Information flows p. 30
7.1a.3.1 Registration request p. 30
Table 7.1a.3.1-1 describes the information flow for a UAE client to register with the UAE server.
| Information element | Status | Description |
|---|---|---|
| UAV ID | M | The identifier of the UAV/UAV-C (e.g. 3GPP UE ID or CAA level UAV ID) which initiates the registration request |
| UAS UE information | O | UAS UE information like IP address, Multi-USS capability, DAA assist capability, Dual Network-Assisted C2 communication link capability, etc. |
| Proposed registration lifetime (NOTE) | O | Proposed registration lifetime. |
|
NOTE:
If Proposed registration lifetime IE is not included, then the registration lifetime is valid until explicit deregistration is performed.
|
||
7.1a.3.2 Registration response p. 30
Table 7.1a.3.2-1 describes the information flow for UAE server to respond for registration request from the UAE client.
| Information element | Status | Description |
|---|---|---|
| Result | M | Result from the UAE server in response to registration request indicating success or failure |
| Registration lifetime | O | The registration lifetime provided by UAE server if registration is successful |
7.1a.3.3 Deregistration request p. 30
Table 7.1a.3.3-1 describes the information flow for a UAE client to deregister at the UAE server.
| Information element | Status | Description |
|---|---|---|
| UAV ID | M | The identifier of the UAV/UAV-C (e.g. 3GPP UE ID or CAA level UAV ID) which initiates the deregistration request |
7.1a.3.4 Deregistration response p. 30
Table 7.1a.3.4-1 describes the information flow for UAE server to respond for deregistration request from the UAE client.
| Information element | Status | Description |
|---|---|---|
| Result | M | Result from the UAE server in response to the deregistration request |
7.1a.3.5 Registration update request p. 30
Table 7.1a.3.5-1 describes the information flow for a UAE client to update registration with the UAE server.
| Information element | Status | Description |
|---|---|---|
| UAV ID | M | The identifier of the UAV/UAV-C (e.g. 3GPP UE ID or CAA level UAV ID) which initiates the registration request |
| UAS UE information | M | UAS UE information like IP address, Multi-USS capability, DAA assist capability, Dual Network-Assisted C2 communication link capability, etc. |
| Proposed registration lifetime | O | Proposed registration lifetime. |
7.1a.3.6 Registration update response p. 31
Table 7.1a.3.6-1 describes the information flow for UAE server to respond for registration update request from the UAE client.
| Information element | Status | Description |
|---|---|---|
| Result | M | Result from the UAE server in response to registration update request indicating success or failure |
| Registration lifetime | O | The registration lifetime provided by UAE server if registration update is successful |
