Content for TS 23.256 Word version: 19.0.0

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…

4.2.3 5GS Non-roaming Reference Architecture 4.2.4 5GS Roaming Reference Architecture 4.2.5 Service-based interfaces 4.2.6 Reference points
...

4.2.3 5GS Non-roaming Reference Architecture p. 17

Reproduction of 3GPP TS 23.256, Fig. 4.2.3-1: 5G System non-roaming architecture for UAVs and for A2X communication over PC5 and Uu reference points

Figure 4.2.3-1: 5G System non-roaming architecture for UAVs and for A2X communication over PC5 and Uu reference points

4.2.4 5GS Roaming Reference Architecture p. 18

Reproduction of 3GPP TS 23.256, Fig. 4.2.4-1: Roaming 5G System architecture for UAVs and for A2X communication over PC5 and Uu reference points - local breakout scenario in service-based interface representation

Figure 4.2.4-1: Roaming 5G System architecture for UAVs and for A2X communication over PC5 and Uu reference points - local breakout scenario in service-based interface representation

Reproduction of 3GPP TS 23.256, Fig. 4.2.4-2: Roaming 5G System architecture for UAVs and for A2X communication over PC5 and Uu reference points - Home routed scenario

Figure 4.2.4-2: Roaming 5G System architecture for UAVs and for A2X communication over PC5 and Uu reference points - Home routed scenario

4.2.4A Void

4.2.5 Service-based interfaces p. 19

The 5G System Architecture for UAVs contains the service-based interfaces defined in TS 23.501, with the following differences:

Nudm:

In the case of A2X Service, services provided by UDM are used to get A2X Service related subscription information to AMF during Initial registration procedure or UE Configuration Update (UCU) procedure to inform AMF subscription information has changed.

Npcf:

In the case of A2X Service, services provided by H-PCF are used to provide A2X Service related parameters to V-PCF for UE and NG-RAN in the roaming case.

Nudr:

In the case of A2X Service, services provided by UDR are used to notify the PCF and the UDM of the update of the A2X Service related information.

Nnef:

In the case of A2X Service, services provided by NEF are used by the A2X Application Server to update A2X Service related information of 5GC.

Namf:

In the case of A2X Service, services provided by AMF are consumed by PCF to provide the A2X Service related parameters for the UE and the NG-RAN to AMF, and to enable the AMF create or update UE context related to A2X service.

Nnrf:

In the case of A2X Service, services provided by NRF are used to discover the PCF that supports A2X.

4.2.6 Reference points p. 20

The 5G System Architecture for UAV contains the reference points defined in TS 23.501. In addition, the reference points of TS 23.287 apply, with the following differences:

A2X1:

The reference point between the A2X applications in the UAV UE and in the UAV-C, and the A2X Application Server. This reference point is out of scope of this specification.

A2X5:

The reference point between the A2X applications in the UEs. This reference point is not specified in this release of the specification.

N1:

In addition to the relevant functions defined in TS 23.501 for N1, in the case of A2X Service it is also used to convey the A2X Policy and parameters (including service authorization) from AMF to UE and to convey the UE's A2X Capability and PC5 Capability for A2X information from UE to AMF.

N2:

In addition to the relevant functions defined in TS 23.501 for N2, in the case of A2X Service it is also used to convey the A2X Policy and parameters (including service authorization) from AMF to NG-RAN.