Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.256  Word version:  19.0.0

Top   Top   Up   Prev   None
1…   4…   4.2…   4.2.3…   4.3…   4.4…   4.5…   5…   5.2.3…   5.2.4…   5.2.5…   5.2.5.3…   5.2.5.4…   5.2.7   5.2.8…   5.2.9…   5.3…   5.4…   5.5…   5.12…   5.13…   5.14…   6…   6.2…   6.3…   6.3.4…   A… 
A Methods to support C2 communication reliability  A.1 Methods to establish redundant C2 connenctions for C2 communication reliability  $ Change history 

 

A  Methods to support C2 communication reliability |R19|  p. 100

A.1  Methods to establish redundant C2 connenctions for C2 communication reliability  p. 100

Existing redundant transmission mechanism defined in TS 23.501 can be used for the End-to-End C2 communication reliability with additional redundant information in C2 aviation payload and C2 authorization payload to allow UAV or UTM to synchronize information regarding the usage of redundant C2 connections via 5G system, because existing paring information within the aviation payload only includes one C2 connection.
Following principles applies to establish redundant C2 connections for C2 communication reliability:
  1. UAV and 5G system support the redundant transmission mechanism defined in clause 5.33.2 of TS 23.501 to be able to establish two redundant C2 connection with a UAV-C or UTM within one network.
  2. The C2 redundant information is added into the C2 aviation payload (from UAV to UTM) and C2 authorization payload (from UTM to UAV) to exchange C2 redundant information between UAV and UTM. The redundant information can include the indication of establishment of redundant C2 connections. This C2 redundant information can be part of the C2 paring information associate with the UAV-C.
    It is up to UAV and UTM to decide which C2 PDU session is primary or secondary. 5G system is only aware of two C2 redundant connections being established and has no knowledge of the primary and secondary C2 connection.
  3. The information exchange using C2 aviation payload and C2 authorization payload between UAV and UTM on the status change of C2 redundant connection can occur during C2 PDU connection establishment / modification phase, or UAV controller replacement phase.
    In the Figure A.1-1, the UE initiation PDU session establishment for 2 redundant PDU sessions for C2 communications with a UAV-C is specified.
Reproduction of 3GPP TS 23.256, Fig. A.1-1: Procedure for PDU Session establishment for C2 redundant
Figure A.1-1: Procedure for PDU Session establishment for C2 redundant
Up
Step 0.
The UAV has performed a successful UUAA with the USS.
Step 1.
The UE first initiates PDU session establishment request for establishing the first PDU session for C2 connection with the UAV-C. In the PDU Session establishment request CAA-Level UAV ID, a C2 Aviation Payload to be used for C2 authorization which includes the C2 redundant information.
Step 2.
The SMF then sends a Nnef_Authentication_AuthenticateAuthorize request including the C2 Aviation Payload, which is used to request authorization redundant C2 communication with 2 redundant C2 connections.
Step 3.
The UAS NF/NEF forwards the received authorization request as a Naf_Authentication_AuthenticateAuthorize request to the UTM.
Step 4.
The UTM performs C2 authorization based on the received information and sends the Naf_Authentication_AuthenticateAuthorize response to the UAS NF/NEF including the Service Level Device Identity (e.g. the CAA-Level UAV-ID), the C2 Authorization Result, and the C2 Authorization Payload (e.g. C2 redundant pairing information).
Step 5.
The UAS-NF/NEF forwards the information received from the UTM in the Nnef_Authentication_AuthenticateAuthorize response sent to the SMF.
Step 6.
SMF informs the UE about the C2 Authorization Result. SMF conducts PDU session establishment procedure until finalized for the establishment of the first C2 PDU session for the UAV-C.
Step 7.
[Conditional] If the C2 authorization is successful, the UTM subscribes via the UAS-NF to a PDU Session Status event for the PDU sessions used for the C2. The UAS NF determines DNN, S-NSSAI corresponding to the PDU session used for the C2 communication and uses this DNN, S-NSSAI to subscribe to SMF for PDU Session Status event. The SMF detects, as described in steps 6-7 of Figure 4.15.3.2.3-1 in TS 23.502, when the PDU Session is established and send the PDU Session Status event report to the UTM via UAS NF/NEF including GPSI and the C2 PDU session IP Address.
Step 8.
Repeat steps 1-7 to establish the second C2 PDU session.
Step 9.
(optional), The UTM stores the received two PDU session IP addresses and invokes the UTM initiated pairing policy configuration procedure (see Figure 5.2.5.4.1-1) for the primary C2 connection.
Step 10.
(optional), The UTM initiates C2 pairing policy configuration for the secondary C2 connection.
Up

$  Change history  p. 102

Up   Top