hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.2.6 Service-based interfaces
|
N5g-ddnmf: Services provided by 5G DDNMF to manage inter-PLMN 5G ProSe Direct Discovery operations.
Npkmf: Service provided by 5G PKMF to support inter-PLMN ProSe security management. The function of Npkmf is defined in TS 33.503 [29].
In addition to the relevant services defined in TS 23.501 [4] for the following service-based interfaces, in the case of ProSe Service, the services can be provided by corresponding NF are as follows:
Nudm: Services provided by UDM are used to get 5G ProSe Service related subscription information to the AMF during Initial Registration procedure or UE Configuration Update (UCU) procedure to inform the AMF the subscription information has changed and to provide ProSe Service related subscription information to 5G DDNMF for the authorisation of 5G ProSe Direct Discovery requests. The subscription information is described in TS 23.502 [5]. Services provided by UDM may also be used by the 5G PKMF for relay service authorisation, see TS 33.503 [29].
Npcf: Services provided by H-PCF are used to provide 5G ProSe Service related parameters to V-PCF for the UE and NG-RAN in the roaming case and to enable the 5G DDNMF to get a PDUID or be notified of PDUID change.
Nudr: Services provided by UDR are used to notify the PCF and the UDM of the update of the 5G ProSe Service related information as described in TS 23.502 [5].
Nnef: Services provided by NEF are used by the ProSe Application Server to update 5G ProSe Service related information of 5GC.
Namf: Services provided by AMF are consumed by PCF to provide the 5G ProSe Service related parameters for the UE and the NG-RAN to the AMF and to enable the AMF create or update the UE context related to 5G ProSe service.
Nnrf: Services provided by NRF are used to discover the PCF that supports 5G ProSe service and for 5G DDNMF in HPLMN to discover other 5G DDNMFs in VPLMN or local PLMN.
Naf: Services provided by AF are consumed by the DDNMF to request authorization for Discovery Request. The AF may update the authorization information to revoke the Restricted ProSe Direct Discovery permission.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.2.7 5G ProSe UE-to-Network Relay reference architecture
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.2.7.1 5G ProSe Layer-3 UE-to-Network Relay reference architecture
|
The following figure 4.2.7.1-1 shows the high level reference architecture for 5G ProSe Layer-3 UE-to-Network Relay. In this figure, the 5G ProSe Layer-3 UE-to-Network Relay may be in the HPLMN or a VPLMN.
Figure 4.2.7.1-1: Reference architecture for 5G ProSe Layer-3 UE-to-Network Relay
The following figure 4.2.7.1-2 shows the non-roaming reference architecture for 5G ProSe Layer-3 UE-to-Network Relay when N3IWF is supported. In this figure, the PLMN A and PLMN B may be the same or different. When the 5G ProSe Layer-3 Remote UE may connect to NG-RAN directly to access PLMN B and in that case it would take the role of UE in the figure. The N3IWF may be connected to Relay UE UPF via a Data Network.
Figure 4.2.7.1-2: Non-roaming architecture model for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support
The following figure 4.2.7.1-3 shows the roaming reference architecture for 5G ProSe Layer-3 UE-to-Network Relay. In this figure, the PLMN A and PLMN B may be the same or different and/or the PLMN A and PLMN C may be the same or different. The N3IWF may be connected to Relay UE UPF via a Data Network.
Figure 4.2.7.1-3: Roaming architecture model for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support
4.2.7.1A 5G ProSe Multi-hop Layer-3 UE-to-Network Relay reference architecture
Figure 4.2.7.1A-1 shows the high level reference architecture for 5G ProSe multi-hop Layer-3 UE-to-Network Relay. There may be one or multiple 5G ProSe Intermediate UE-to-Network Relays between the 5G Prose Remote UE and the 5G ProSe UE-to-Network Relay. In this figure, the 5G ProSe Layer-3 UE-to-Network Relay may be in the HPLMN or a VPLMN.
Figure 4.2.7.1A-1: Reference architecture for 5G ProSe multi-hop Layer-3 UE-to-Network Relay
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.2.7.2 5G ProSe Layer-2 UE-to-Network Relay reference architecture
|
Figure 4.2.7.2-1 shows the 5G ProSe Layer-2 UE-to-Network Relay reference architecture. The 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay may be served by the same or different PLMNs. If the serving PLMNs of the 5G ProSe Layer-2 Remote UE and the 5G ProSe Layer-2UE-to-Network Relay are different then NG-RAN is shared by the serving PLMNs, see the 5G MOCN architecture in clause 5.18 of TS 23.501 [4].
Figure 4.2.7.2-1: 5G ProSe Layer-2 UE-to-Network Relay reference architecture
NOTE 1: Uu between the 5G ProSe Layer-2 Remote UE and NG-RAN consists of RRC, SDAP and PDCP.
NOTE 2: The 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay are served by the same NG-RAN. The Core Network entities (e.g. AMF, SMF, UPF) serving the 5G ProSe Layer-2 Remote UE and the 5G ProSe Layer-2 UE-to-Network Relay can be the same or different.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.2.8 5G ProSe UE-to-UE Relay reference architecture
|
Figure 4.2.8-1 shows the Layer-2 and Layer-3 5G ProSe UE-to-UE Relay reference architecture. The 5G ProSe End UEs communicate with each other via a 5G ProSe UE-to-UE Relay.
Figure 4.2.8-1: Reference architecture for 5G ProSe UE-to-UE Relay
Each 5G ProSe End UE and the 5G ProSe UE-to-UE Relay may have subscriptions from the same PLMN or different PLMNs.
4.2.8A 5G ProSe Multi-hop UE-to-UE Relay reference architecture
Figure 4.2.8A-1 shows the Layer-3 5G ProSe UE-to-UE Relay reference architecture. The 5G ProSe End UEs communicate with each other via a set of interconnected 5G ProSe Multi-hop UE-to-UE Relays.
Figure 4.2.8A-1: Reference architecture for Layer-3 5G ProSe Multi-hop UE-to-UE Relay
Based on capability and configuration the 5G ProSe UE can act as a 5G ProSe End UE, a 5G ProSe Multi-hop UE-to-UE Relay or both. Each 5G ProSe End UE and the 5G ProSe UE-to-UE Relay may have subscriptions from the same PLMN or different PLMNs.
- For IP PDU type, the 5G ProSe Multi-hop UE-to-UE Relays form a MANET network as defined in IETF RFC 7181 [35]. A 5G ProSe UE acting as 5G ProSe UE-to-UE Relay shall support the protocols defined in IETF RFC 7181 [35] and IETF RFC 6130 [36] on the PC5 interfaces towards other 5G ProSe Multi-hop UE-to-UE Relays. In addition, the 5G ProSe UE-to-UE Relay shall support a dedicated MANET Discovery Info message on the PC5 interfaces towards other 5G ProSe Multi-hop UE-to-UE Relays for propagation of DNS information, as described in clause 5.14.3.2.
NOTE: The MANET Discovery Info message will be specified in Stage 3.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.2.9 Support for 5G ProSe in NPNs
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.2.9.1 Support for 5G ProSe in SNPN
|
The proximity based services defined in this specification are applicable to SNPN(s) with the following adaptations:
- The non-roaming architecture in clause 4.2.1 is applicable also to SNPN, whereby the term PLMN is replaced by subscribed SNPN.
- The roaming architecture in clause 4.2.2 is not supported.
- Inter-SNPN operation in clause 4.2.3 is not supported.
- For 5G ProSe Direct Discovery, the procedures in clauses 5.2 and 6, the network function services in clause 7 and the identifiers as specified in clause 5.8.1 are used with the following adaptations:
- The concept of Local PLMN for direct discovery is not supported.
- In the ProSe Application ID in clause 5.8.1.1 the value of PLMN ID within the ProSe Application ID shall be combined with a Network Identifier (NID) to identify an SNPN.
- The ProSe Application Code in clause 5.8.1.4 is extended to allow the value of PLMN ID within the ProSe Application Code to be combined with a Network Identifier (NID) to identify an SNPN.
- The Announcing PLMN ID in clause 5.8.1.11 is not used in the case of SNPNs.
- The Monitored PLMN ID in clause 5.8.1.17 is ignored in the case of SNPNs.
- In the 5G ProSe Direct Discovery with 5G DDNMF procedures as specified in clause 6.3.1, the term PLMN is to be replaced by SNPN, whereby PLMN IDs shall be combined with a Network Identifier (NID) to identify an SNPN, except if it pertains to PLMN IDs of VPLMNs or Local PLMNs or Announcing PLMN IDs. The term HPLMN is to be replaced by subscribed SNPN.
- The 5G ProSe UE-to-Network Relay reference architectures for 5G ProSe Layer-2 UE-to-Network relay, 5G ProSe Layer-3 UE-to-Network relay and UE-to-UE relay in clauses 4.2.7 and 4.2.8 are supported, where only the non-roaming architecture as specified for 5G ProSe Layer-3 UE-to-Network relay in clause 4.2.7.1 is supported for SNPNs and the PLMN A, PLMN B and PLMN C in clauses 4.2.7 are the same in case of SNPNs and are replaced by the SNPN. The term PLMN is replaced by SNPN and the term HPLMN is replaced by subscribed SNPN. The term VPLMN is not applicable to SNPNs.
- For Authorization and Provisioning and for the subscription information of the ProSe service in NPNs, the procedures and functionality as specified in clauses 5.1 and 5.7 and 6.2 are used with the following adaptations:
- The term PLMN is replaced by SNPN. The term HPLMN is replaced by subscribed SNPN. The term VPLMN is not applicable to SNPNs. Except the subscribed SNPN, no other SNPNs are authorized to perform the 5G ProSe service (i.e. 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay discovery, 5G ProSe UE-to-Network Relay communication, 5G ProSe UE-to-UE Relay discovery and 5G ProSe UE-to-UE Relay communication) over PC5 reference point.
- For 5G ProSe Layer-2 UE-to-Network relay operation, the procedures as specified in clauses 5.4.2 and 5.4.4.2 and the identifiers as specified in clause 5.8.3 are used with the following adaptations:
- The term PLMN is replaced by SNPN.
- The 5G ProSe Layer-2 Remote UE has to operate in SNPN access mode, if it intends to access SNPN for ProSe via 5G ProSe Layer-2 UE-to-Network relay.
- The 5G ProSe UE-to-Network Relay has to operate in SNPN access mode, if it intends to access SNPN for ProSe via 5G ProSe Layer-2 UE-to-Network relay.
- The 5G ProSe Layer-2 UE-to-Network relay may participate in the 5G ProSe UE-to-Network Relay Discovery procedure for emergency service if the serving NG-RAN broadcasts ims-EmergencySupport or imsEmergencySupportForSNPN in system information as specified in TS 38.300 [12] and TS 38.331 [16].
- The NCGI in clause 5.8.3.3 includes the Network identifier (NID) of the SNPN together with the PLMN ID in case the serving cell is operated by an SNPN.
- The 5G ProSe Layer-2 Remote UE only selects the 5G ProSe Layer-2 UE-to-Network Relay for which the NCGI includes the subscribed SNPN of 5G ProSe Layer-2 Remote UE for non-emergency service.
NOTE 1: To prevent that unauthorized 5G ProSe Remote UEs can gain access to an NPN via 5G ProSe UE-to-Network Relay, the existing User Plane and/or Control Plane authorization verification procedures as specified in clause 6.3.4 of TS 33.503 [29] and restricted 5G ProSe Direct Discovery procedures as specified in clause 6.1.3.2 of TS 33.503 [29] are reused.
- For 5G ProSe Layer-3 UE-to-Network relay operation, the procedures as specified in clauses 5.4.1, 5.4.4.3 and 6.5 and the identifiers as specified in clause 5.8.3 apply with the following adaptations:
- The term PLMN is replaced by SNPN. The term HPLMN is replaced by subscribed SNPN. The term VPLMN is not applicable to SNPNs.
- The 5G ProSe Layer-3 UE-to-Network relay has to operate in SNPN access mode in order to relay traffic to/from an SNPN for a 5G ProSe Layer-3 Remote UE.
- The 5G ProSe Layer-3 Remote UE has to operate in SNPN access mode in order to exchange traffic to/from an SNPN via a 5G ProSe Layer-3 UE-to-Network relay.
- The NCGI in clause 5.8.3.2 includes the Network identifier (NID) of the SNPN together with the PLMN ID in case the serving cell is operated by an SNPN.
- The TAI in clause 5.8.3.2 includes the Network identifier (NID) of the SNPN together with the PLMN ID in case the serving cell is operated by an SNPN.
NOTE 2: To prevent that unauthorized 5G ProSe Remote UEs can gain access to an NPN via 5G ProSe UE-to-Network Relay, the existing User Plane and/or Control Plane authorization verification procedures as specified in clause 6.3.3 of TS 33.503 [29] and restricted 5G ProSe Direct Discovery procedures as specified in clause 6.1.3.2 of TS 33.503 [29] are reused.
- The support for 5G ProSe for UEs in limited service state as specified in clause 5.9 applies whereby the term PLMN is replaced by an SNPN.
The SNPN onboarding procedure defined in clause 5.30.2.10 of TS 23.501 [4] via 5G ProSe UE-to-Network Relay is not supported.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.2.9.2 Support for 5G ProSe in conjunction with CAG in PNI-NPN
|
In this Release, the CAG based access control is not applicable to the 5G ProSe Layer-3 UE-to-Network Remote UE accessing the network via 5G Layer-3 ProSe Relay.
NOTE 1: PNI-NPNs by means of one (or more) Network Slice instances or dedicated DNNs are supported for 5G Layer-3 ProSe UE-to-Network Relay.
The 5G ProSe Layer-2 UE-to-Network Relay procedures in conjunction with CAG for PNI-NPN are supported with the following adaptations:
- The 5G ProSe Layer-2 UE-to-Network relay may participate in the 5G ProSe UE-to-Network Relay Discovery procedure if the 5G ProSe Layer-2 UE-to-Network relay is accessing a CAG cell in the Allowed CAG list configured on the 5G ProSe Layer-2 UE-to-Network relay.
NOTE 2: 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay can access different CAG IDs.
NOTE 3: In order to prevent that unauthorized 5G ProSe Remote UEs can gain access to a CAG cell operated by a PNI-NPN which a 5G ProSe Layer-2 Remote UE is not allowed to access, the existing access control mechanisms as specified in clause 5.30.3.4 of TS 23.501 [4] and clause 16.7.4 of TS 38.300 [12] are reused.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3 Functional Entities
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.1 UE
|
Any 5G ProSe-enabled UE may support the following functions:
- Exchange of information for 5G ProSe Direct Discovery between 5G ProSe-enabled UE and the 5G DDNMF over PC3a reference point.
- Procedures for 5G ProSe Direct Discovery of other 5G ProSe-enabled UEs over PC5 reference point.
- Procedures for 5G ProSe Direct Communication over PC5 reference point, including Broadcast, Groupcast and Unicast mode 5G ProSe Direct Communication.
- Procedures to act as a 5G ProSe Layer-2 UE-to-Network Relay.
- Procedures to act as a 5G ProSe Layer-3 UE-to-Network Relay.
- Procedures to act as a 5G ProSe Intermediate UE-to-Network Relay.
- Procedures to act as a 5G ProSe Layer-2 Remote UE.
- Procedures to act as a 5G ProSe Layer-3 Remote UE.
- Procedures to act as a 5G ProSe Layer-2 UE-to-UE Relay.
- Procedures to act as a 5G ProSe Layer-3 UE-to-UE Relay.
- Procedures to act as a 5G ProSe Layer-2 End UE.
- Procedures to act as a 5G ProSe Layer-3 End UE.
- Procedures for communication path switching between PC5 and Uu reference points.
- Procedures for Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay.
- Indicating UE Policy Provisioning Request in UE Policy Container for UE triggered 5G ProSe Policy provisioning, which requests one or multiple types of policies/parameters as listed below:
- Policy/parameters for 5G ProSe Direct Discovery;
- Policy/parameters for 5G ProSe Direct Communication;
- Policy/parameters for 5G ProSe Layer-2 Remote UE;
- Policy/parameters for 5G ProSe Layer-3 Remote UE;
- Policy/parameters for 5G ProSe Layer-2 UE-to-Network Relay;
- Policy/parameters for 5G ProSe Layer-3 UE-to-Network Relay;
- Policy/parameters for 5G ProSe Layer-3 Intermediate UE-to-Network Relay;
- Policy/parameters for 5G ProSe Layer-2 End UE;
- Policy/parameters for 5G ProSe Layer-3 End UE;
- Policy/parameters for 5G ProSe Layer-2 UE-to-UE Relay;
- Policy/parameters for 5G ProSe Layer-3 UE-to-UE Relay;
- Policy/parameters for 5G ProSe Multi-hop Layer-3 UE-to-Network Relay Discovery;
- Policy/parameters for 5G ProSe Multi-hop Layer-3 UE-to-UE Relay Discovery;
- Policy/parameters for 5G ProSe Communication via Multi-hop Layer-3 UE-to-Network Relay;
- Policy/parameters for 5G ProSe Communication via Multi-hop Layer-3 UE-to-UE Relay.
NOTE: Encoding of these policy bits is defined in TS 24.554 [23].
- Receiving the 5G ProSe Policy from 5GC over N1 reference point.
- Configuration of parameters for 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe Single-hop UE-to-Network Relay (e.g. including IP addresses, ProSe Layer-2 Group IDs, see clause 5.1), 5G ProSe Multi-hop Layer-3 UE-to-Network Relay, 5G ProSe Single-hop UE-to-UE Relay and 5G ProSe Multi-hop Layer-3 UE-to-UE Relay. These parameters can be pre-configured in the UE, or, if in coverage, provisioned or updated by signalling over the N1 reference point from the PCF in the HPLMN or over PC1 reference point from the ProSe Application Server.
- Reporting the following capabilities to 5GC over the N1 reference point:
- 5G ProSe Capability.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.2 5G DDNMF
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.2.1 General
|
The 5G DDNMF is the logical function handling network related actions required for dynamic 5G ProSe Direct Discovery. In this version of the specification, it is assumed that there is only one logical 5G DDNMF in each PLMN that supports 5G ProSe Direct Discovery service.
NOTE: If multiple 5G DDNMFs are deployed within the same PLMN (e.g. for load reasons), the method to locate the 5G DDNMF that has allocated a specific ProSe Application Code or ProSe Restricted Code (e.g. through a database lookup, etc.) is not defined in this version of the specification.
The 5G DDNMF interacts with the 5G ProSe-enabled UE using procedures over PC3a reference point defined in clause 6.3.1 to allocate and resolve the mapping of ProSe Applications IDs and ProSe Application Codes used in 5G ProSe Direct Discovery. It uses ProSe related subscriber data stored in UDM for the authorisation of each discovery request. It also provides the UE with the necessary security material in order to protect discovery messages transmitted over the air. In restricted 5G ProSe Direct Discovery, it also interacts with the Application Server via Npc2 reference points or with other 5G DDNMFs via Npc6/Npc7 reference points for the authorization of the discovery requests.
The 5G ProSe-enabled UE use procedure defined in clause 4.3.2.2 to discovery the 5G DDNMF in the HPLMN. Based on the UE Local Configuration or URSP as defined in TS 23.503 [9], an existing PDU session is selected or a new PDU session is established, to carry the control signalling between the UE and the 5G DDNMF in the HPLMN.
The 5G DDNMF provides the necessary charging functionality or charging information for the usage of 5G ProSe Direct Discovery and/or ProSe Direct Communication to interact with CHF or for the provision to CEF.
The 5G DDNMF in the HPLMN may interact with the 5G DDNMF in a VPLMN or Local PLMN in order to manage the 5G ProSe Direct Discovery service.
The 5G DDNMF gets the address of the PCF for the UE from the BSF.
The 5G DDNMF gets the PDUID from the PCF and subscribes to notifications on Change of PDUID.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.2.2 5G DDNMF Discovery
|
The 5G DDNMF of HPLMN is discovered through interaction with the Domain Name Service function. The UE may have the 5G DDNMF address in the Home PLMN (either as a FQDN or an IP address) pre-configured or provisioned as specified in clause 5.1.2.1. If it is not pre-configured or provisioned then the UE self-constructs the FQDN for it using e.g. the PLMN ID of the HPLMN.
The 5G DDNMF in the HPLMN uses the NRF to discovery other 5G DDNMFs in a VPLMN or local PLMN.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.3 PCF
|
In addition to the functions defined in TS 23.501 [4] and TS 23.503 [9], the PCF includes functions to provision the UE with necessary policies and parameters to use 5G ProSe services, as part of the UE ProSe Policy information as defined in TS 23.503 [9] clause 4.2.2:
- PC5 usage reporting configuration.
- Authorization policy and parameters for 5G ProSe Direct Discovery and Communication.
- Authorization policy and parameters for 5G ProSe UE-to-Network Relay Discovery and Communication (i.e. as 5G ProSe Layer-2 Remote UE, as 5G ProSe Layer-3 Remote UE, as 5G ProSe Layer-2 UE-to-Network Relay, as 5G ProSe Layer-3 UE-to-Network Relay).
- PDUID allocation with its validity timer.
- Authorization policy and parameters for 5G ProSe UE-to-UE Relay Discovery and Communication.
- Authorization policy and parameters for 5G ProSe Layer-3 multi-hop UE-to-Network Relay Discovery and Communication.
- Authorization policy and parameters for 5G ProSe Layer-3 multi-hop UE-to-UE Relay Discovery and Communication.
The PCF may update the 5G ProSe policy and parameters to the UE under certain conditions.
When receiving the 5G ProSe Capability in Npcf_UEPolicyControl_Create Request from the AMF or when receiving the updated subscription data from UDR, the PCF generates the PC5 QoS parameters used by NG-RAN corresponding to a UE as defined in clause 5.4.2 of TS 23.287 [2].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.4 AMF
|
In addition to the functions defined in TS 23.501 [4], the AMF performs the following functions:
- Select a PCF supporting 5G ProSe Policy/Parameter provisioning based on indication of 5G ProSe Capability as part of the "5GMM capability" in the Registration Request.
- Store the 5G ProSe Capability.
- Forward the 5G ProSe Capability to PCF in Npcf_UEPolicyControl_Create Request.
- Obtain from UDM the subscription information related to 5G ProSe and store them as part of the UE context data.
- Obtain PC5 QoS parameters from the PCF and store them as part of the UE context data.
- Provision the NG-RAN with indication about the UE authorization status about the following:
- 5G ProSe Direct Discovery and 5G ProSe Direct Communication (i.e. as 5G ProSe-enabled UE for ProSe Direct Discovery, as 5G ProSe-enabled UE for ProSe Direct Communication);
- 5G ProSe UE-to-Network Relay Discovery and Communication (i.e. as 5G ProSe Layer-2 Remote UE, as 5G ProSe Layer-2 UE-to-Network Relay, as 5G ProSe Layer-3 UE-to-Network Relay);
- Multi-path communication via direct Uu path and via 5G ProSe Layer 2 UE-to-Network Relay as a 5G ProSe Layer-2 Remote UE;
- 5G ProSe UE-to-UE Relay Discovery and Communication (i.e. as 5G ProSe Layer-2 End UE, as 5G ProSe Layer-2 UE-to-UE Relay);
- 5G ProSe Layer-3 multi-hop UE-to-Network Relay Discovery and Communication (i.e. as 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay;
- 5G ProSe Layer-2 multi-hop UE-to-Network Relay Discovery and Communication (i.e. as 5G ProSe Layer-2 UE-to-Network Relay supporting 5G ProSe Layer-2 multi-hop UE-to-Network Relay, as 5G ProSe Layer-2 Intermediate UE-to-Network Relay, as 5G ProSe Layer-2 Remote UE supporting 5G ProSe Layer-2 multi-hop UE-to-Network Relay).
- Provision the NG-RAN with PC5 QoS parameters related to 5G ProSe Direct Communication.
- Optionally support security procedures over Control Plane for 5G ProSe UE-to-Network relaying as defined in TS 33.503 [29].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.5 UDM
|
In addition to the functions defined in TS 23.501 [4], the UDM performs the following functions:
- Subscription management for 5G ProSe Direct Discovery and Communication.
- Subscription management for 5G ProSe UE-to-Network Relay Discovery and Communication.
- Subscription management for multi-path communication via direct Uu path and via 5G ProSe Layer 2 UE-to-Network Relay as a 5G ProSe Layer-2 Remote UE.
- Subscription management for 5G ProSe UE-to-UE Relay Discovery and Communication.
- Subscription management for 5G ProSe Layer-3 multi-hop UE-to-Network Relay Discovery and Communication.
- Subscription management for 5G ProSe Layer-3 multi-hop UE-to-UE Relay Discovery and Communication.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.6 UDR
|
In addition to the functions defined in TS 23.501 [4], the UDR performs the following functions:
- Stores a path preference for ProSe services provided by the AF.
- Stores ProSe service parameters.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.7 NRF
|
In addition to the functions defined in TS 23.501 [4], the NRF performs the following functions:
- PCF discovery by considering 5G ProSe Capability.
- 5G DDNMF Discovery.
Similar procedure can be used for 5G DDNMF discovery across PLMNs as specified in clause 4.17.5 of TS 23.502 [5] with the difference as below:
- The serving PLMN is replaced by home PLMN and home PLMN is replaced by local PLMN or serving PLMN.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.8 ProSe Application Server
|
The ProSe Application Server supports the following functionalities.
For 5G ProSe Direct Discovery:
- Maintains permission information for the restricted 5G ProSe Direct Discovery using RPAUIDs;
- Storage of ProSe Discovery UE IDs and metadata;
- Mapping of RPAUID and PDUID for restricted 5G ProSe Direct Discovery;
- Provisioning parameters for Group Member Discovery to UE.
- Interaction with 5G DDNMF for 5G ProSe Direct Discovery, including:
- Allocation of the ProSe Restricted Code Suffix pool, if restricted Direct Discovery with application-controlled extension is used;
- Allocation of the mask(s) for ProSe Restricted Code Suffix, if restricted Direct Discovery with application-controlled extension is used;
- Allocation of the ProSe Application Code Suffix pool, if open Direct Discovery with application-controlled extension is used;
- Allocation of the mask(s) for ProSe Application Code Suffix, if open Direct Discovery with application-controlled extension is used.
For 5G ProSe Direct Communication:
- Provisioning a path preference for 5G ProSe Services to UDR;
- Provisioning parameters for 5G ProSe Direct Communication to UE.
For 5G ProSe UE-to-Network Relay service:
- Provisioning parameters for 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-Network Relay Communication to UDR.
For 5G ProSe UE-to-UE Relay service:
- Provisioning parameters for 5G ProSe UE-to-UE Relay Discovery and 5G ProSe UE-to-UE Relay Communication to UDR.
For 5G ProSe Layer-3 multi-hop UE-to-Network Relay service:
- Provisioning parameters for 5G ProSe Layer-3 multi-hop UE-to-Network Relay Discovery and 5G ProSe multi-hop UE-to-Network Relay Communication to UDR.
For 5G ProSe Layer-3 multi-hop UE-to-UE Relay service:
- Provisioning parameters for 5G ProSe Layer-3 multi-hop UE-to-UE Relay Discovery and 5G ProSe Layer-3 multi-hop UE-to-UE Relay Communication to UDR.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.9 5G ProSe UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.9.1 General
|
Both 5G ProSe Layer-2 and Layer-3 UE-to-Network Relay entity provides the relaying functionality to support connectivity to the network for 5G ProSe Remote UEs. It can be used for both public safety services and commercial services (e.g. interactive service).
Both 5G ProSe Layer-2 and Layer-3 UE-to-Network Relay supports the following functions to enable connectivity to the network:
- 5G ProSe UE-to-Network Relay Discovery service as defined in clause 6.3.2.3, to allow discovery by the 5G ProSe Remote UE;
- access the 5GS as a UE as defined in TS 23.501 [4] with the enhancements as specified in clauses 6.2 and 6.6;
- relays unicast traffic (uplink and downlink) between the 5G ProSe Remote UE and the network, supporting IP, Ethernet or Unstructured traffic type.
NOTE: Relaying MBS traffic to a 5G ProSe Remote UE by a 5G ProSe UE-to-Network Relay is not supported in this release of the specification.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.9.2 5G ProSe Layer-3 UE-to-Network Relay
|
In addition to the common 5G ProSe UE-to-Network Relay functions defined in clause 4.3.9.1, 5G ProSe Layer-3 UE-to-Network Relay supports the following functions to enable connectivity to the network:
- 5G ProSe Direct Communication via 5G ProSe Layer-3 UE-to-Network Relay as specified in clause 6.5.1, for the communication with the 5G ProSe Layer-3 Remote UEs for the relay operations;
- end-to-end QoS treatment for the 5G ProSe Layer-3 Remote UE's traffic without N3IWF as defined in clause 5.6.2.1 and when accessing via an N3IWF as defined in clause 5.6.2.2;
- IP address management for the 5G ProSe Layer-3 Remote UE as defined in clause 5.5.1.3 in case the 5G ProSe Layer-3 Remote UE uses IP traffic type.
- Emergency PDU Session establishment for 5G ProSe Layer-3 Remote UE via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF support.
NOTE: For emergency service via N3IWF, see clause 5.4.4.3.
If 5G ProSe Multi-hop UE-to-Network Relay is supported, a 5G ProSe Layer-3 UE-to-Network Relay supports the following functions:
- 5G ProSe Multi-hop UE-to-Network Relay Discovery.
- 5G ProSe Communication via Multi-hop UE-to-Network Relay as defined in clause 6.5.1.4.
- Relay unicast traffic originating from the 5G ProSe Remote UE and received from a 5G ProSe Intermediate UE-to-Network Relay to the network supporting IP, Ethernet or Unstructured traffic type.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.9.3 5G ProSe Layer-2 UE-to-Network Relay
|
In addition to the common 5G ProSe UE-to-Network Relay functions defined in clause 4.3.9.1, 5G ProSe Layer-2 UE-to-Network Relay supports the following functions to enable connectivity to the network:
- 5G ProSe Direct Communication via 5G ProSe Layer-2 UE-to-Network Relay as specified in clause 6.5.2, for the communication with the 5G ProSe Layer-2 Remote UEs for the relay operations;
- QoS handling for 5G ProSe Layer-2 UE-to-Network Relay and end-to-end QoS treatment as defined in clause 5.6.2.3.
- For a 5G ProSe Layer-2 UE-to-Network Relay to participate in the 5G ProSe UE-to-Network Relay Discovery procedure for emergency service (i.e. sending the UE-to-Network Relay Discovery Announcement message or UE-to-Network Relay Discovery Response message), the serving NG-RAN support of emergency services is required as the Layer-2 Remote UE may select a different PLMN from the Layer-2 Relay.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.10 SMF
|
In addition to the functions defined in TS 23.501 [4], the SMF supports the following function:
- Receiving 5G ProSe Layer-3 Remote UE report and maintaining the information of 5G ProSe Layer-3 Remote UE(s) handled by a 5G ProSe Layer-3 UE-to-Network Relay in the 5G ProSe Layer-3 UE-to-Network Relay's SM context for the PDU Session associated with the relay.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.11 NEF
|
In addition to the functions defined in TS 23.501 [4], the NEF supports the following:
- To enable AFs to provide service specific information to the 3GPP network, the NEF supports additional service parameters for ProSe policy as specified in clause 6.2.5.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.12 5G ProSe UE-to-UE Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.12.1 General
|
Both 5G ProSe Layer-2 and Layer-3 UE-to-UE Relay provides the relaying functionality to support connectivity between 5G ProSe End UEs. 5G ProSe UE-to-UE Relay can be used for both public safety services and commercial services (e.g. interactive service).
Both 5G ProSe Layer-2 and Layer-3 UE-to-UE Relay supports the following functions to enable connectivity between 5G ProSe End UEs:
- 5G ProSe UE-to-UE Relay Discovery service as defined in clause 6.3.2.4, to allow discovery by the 5G ProSe End UE;
- 5G ProSe Discovery integrated into PC5 unicast link establishment as specified in clause 6.7.3;
- Access 5GS as a UE as defined in TS 23.501 [4] with the enhancements as specified in clauses 6.2;
- Relay unicast traffic between the 5G ProSe End UEs directly in the case of 5G ProSe Single-hop UE-to UE Relay, or via one or more Layer-3 UE-to-UE Relays in the case of 5G ProSe Multi-hop Layer-3 UE-to-UE Relay, supporting IP, Ethernet or Unstructured traffic type.
NOTE: Relaying groupcast and broadcast traffic to a 5G ProSe End UE by a 5G ProSe UE-to-UE Relay is not supported in this release of the specification.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.12.2 5G ProSe Layer-3 UE-to-UE Relay
|
In addition to the common 5G ProSe UE-to-UE Relay functionality defined in clause 4.3.12.1, a 5G ProSe Layer-3 UE-to-UE Relay supports the following functions:
- 5G ProSe Direct Communication via 5G ProSe Layer-3 UE-to-UE Relay as specified in clause 6.7.1, for the communication between 5G ProSe Layer-3 End UEs for relay operations;
- QoS handling and end-to-end QoS treatment for the 5G ProSe Layer-3 End UE's traffic as defined in clause 5.6.3.1;
- IP address management for the 5G ProSe Layer-3 End UE as defined in clause 5.5.1.4 when the 5G ProSe Layer-3 End UE uses IP traffic type;
- 5G ProSe UE-to-UE Relay reselection as specified in clause 6.7.4.3.
If 5G ProSe Multi-hop UE-to-UE Relay is supported, a 5G ProSe Layer-3 UE-to-UE Relay supports the following functions:
- 5G ProSe Multi-hop UE-to-UE Relay Discovery service;
- 5G ProSe Communication via Multi-hop UE-to-UE Relay as defined in clause 6.7.5;
- Relay unicast traffic between the 5G ProSe End UEs via one or more Layer-3 UE-to-UE Relays, supporting IP, Ethernet or Unstructured traffic type;
- For IP PDU type MANET based routing protocols are used to provide multi-hop forwarding functionality. The MANET routing protocols to be supported, i.e. Neighborhood Discovery Protocol (NHDP) [36] and OLSRv2 [35], are associated with the RSCs based on configuration;
- For non-IP (Ethernet or Unstructured) PDU type with multi-hop support the Relay discovery procedures as defined in clause 6.3.2.6.3.1 (Model A) and clause 6.3.2.6.3.2 (Model B), the Layer-2 link establishment and management procedures as defined in clause 6.4.3.10.2 and the Communication procedure as defined in clause 6.7.5.2.2.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.12.3 5G ProSe Layer-2 UE-to-UE Relay
|
In addition to the common 5G ProSe UE-to-UE Relay functions defined in clause 4.3.12.1, 5G ProSe Layer-2 UE-to-UE Relay supports the following functions:
- 5G ProSe Direct Communication via 5G ProSe Layer-2 UE-to-UE Relay as specified in clause 6.7.2, for the communication between 5G ProSe Layer-2 End UEs for relay operations;
- QoS handling and end-to-end QoS treatment for 5G ProSe Layer-2 End UE's traffic as defined in clause 5.6.3.2;
- 5G ProSe UE-to-UE Relay reselection as specified in clause 6.7.4.2.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
4.3.13 5G ProSe Intermediate UE-to-Network Relay
|
The 5G ProSe Intermediate UE-to-Network Relay entity provides the relaying functionality to support multi-hop connectivity between the 5G ProSe Remote UEs and the 5G ProSe UE-to-Network Relay. It can be used for both public safety services and commercial services (e.g. interactive service). There can be more than one 5G ProSe Intermediate UE-to-Network Relay connecting the 5G ProSe Remote UEs and the 5G ProSe UE-to-Network Relay.
The 5G ProSe Intermediate UE-to-Network Relay supports the following functions to enable connectivity between the 5G ProSe Remote UEs and the 5G ProSe UE-to-Network Relay:
- 5G ProSe Multi-hop UE-to-Network Relay Discovery service to allow discovery by the 5G ProSe Remote UE as defined in clause 6.3.2.5.
- Access the 5GS as a UE as defined in TS 23.501 [4].
- Relays unicast traffic (uplink and downlink) between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay directly or via other 5G ProSe Intermediate UE-to-Network Relay(s), supporting IP, Ethernet or Unstructured traffic type.
- 5G ProSe Multi-hop Communication via 5G ProSe Layer-3 UE-to-Network Relay as specified in clause 6.5.1.4;
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5 High level functionality and features
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1 Authorization and Provisioning for ProSe service
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.1 General
|
In 5GS, the parameters for 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay, 5G ProSe UE-to-UE Relay, 5G ProSe Layer-3 multi-hop UE-to-Network Relay and 5G ProSe Layer-3 multi-hop UE-to-UE Relay services may be made available to the UE in following ways:
- provisioned in the ME; or
- configured in the UICC; or
- provisioned in the ME and configured in the UICC; or
- provided or updated by the ProSe Application Server via PCF and/or PC1 reference point; or
- provided or updated by the PCF to the UE.
If the same parameters described in clauses 5.1.2.1, 5.1.3.1, 5.1.4.1 and 5.1.5.1 are provided by different sources, the UE shall consider them in the following priority order:
- provided or updated by the PCF (including parameters determined by the PCF itself and parameters provided by the ProSe Application Server to the PCF as specified in clause 6.2.5);
- provided or updated by the ProSe Application Server via PC1 reference point;
- configured in the UICC;
- provisioned in the ME.
The parameters provided or updated by the ProSe Application Server via PC1 reference point may need to be complemented with configuration data from other sources listed above.
NOTE: The ProSe Application Server can provision the same ProSe parameters via 5GC as specified in clause 6.2.5 or directly to the UE via PC1 reference point and can revoke (e.g. delete) the ProSe parameters via 5GC as specified in clause 6.2.5 in order for the provisioning via PC1 reference point to take effect.
The basic principles of service authorization and provisioning for 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay, 5G ProSe UE-to-UE Relay, 5G ProSe Layer-3 multi-hop UE-to-Network Relay and 5G ProSe Layer-3 multi-hop UE-to-UE Relay services are as follows:
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorized to use 5G ProSe Direct Discovery.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to use 5G ProSe Direct Communication.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe UE-to-Network Relay. Authorisation for 5G ProSe Layer-2 UE-to-Network Relay and 5G ProSe Layer-3 UE-to-Network Relay are independent of each other.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to access 5GC via 5G ProSe UE-to-Network Relay (i.e. to act as 5G ProSe Remote UE). Authorisation to access via 5G ProSe Layer-2 UE-to-Network Relay and via 5G ProSe Layer-3 UE-to-Network Relay are independent of each other.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe UE-to-UE Relay. Authorisation for 5G ProSe Layer-2 UE-to-UE Relay and 5G ProSe Layer-3 UE-to-UE Relay are independent of each other.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to access 5G ProSe UE-to-UE Relay (i.e. to act as 5G ProSe End UE). Authorisation to access via 5G ProSe Layer-2 UE-to-UE Relay and via 5G ProSe Layer-3 UE-to-UE Relay are independent of each other.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe Layer-3 multi-hop Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe Layer-3 multi-hop Intermediate UE-to-Network Relay.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe Layer-3 End UE supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay.
- The PCF in the HPLMN merges authorization information from home and other PLMNs and provides the UE with the final authorization information.
- The PCF in the VPLMN or HPLMN may revoke the authorization (via H-PCF when roaming) at any time by using the UE Configuration Update procedure for transparent UE Policy delivery procedure defined in clause 4.2.4.3 of TS 23.502 [5].
- The ProSe Policy/parameters provisioning to UE is controlled by the PCF and may be triggered by UE. The PCF provisions one or more of the following ProSe Policy/parameters:
- ProSe Policy/parameters for 5G ProSe Direct Discovery as specified in clause 5.1.2.1;
- ProSe Policy/parameters for 5G ProSe Direct Communications as specified in clause 5.1.3.1;
- ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 UE-to-Network Relay as specified in clause 5.1.4.1;
- ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 Remote UE as specified in clause 5.1.4.1.
- ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 UE-to-UE Relay as specified in clause 5.1.5.1.
- ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 End UE as specified in clause 5.1.5.1.
- ProSe Policy/parameters for 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay as specified in clause 5.1.4.1a.
- ProSe Policy/parameters for 5G ProSe Layer-3 multi-hop Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay as specified in clause 5.1.4.1a.
- ProSe Policy/parameters for 5G ProSe Layer-3 multi-hop Intermediate UE-to-Network Relay as specified in clause 5.1.4.1a.
- ProSe Policy/parameters for 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay as specified in clause 5.1.5.1a.
- ProSe Policy/parameters for 5G ProSe Layer-3 End UE supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay as specified in clause 5.1.5.1a.
- The PCF includes the 5G ProSe Policy/parameters in a Policy Section identified by a Policy Section Identifier (PSI) as specified in clause 6.1.2.2.2 of TS 23.503 [9].
In addition to the above, ProSe usage reporting configuration and rules for charging can be (pre)configured in the UE or provided by the PCF.
In addition to the above, the path selection policy can be (pre)configured in the UE or provided by the PCF as defined in clause 5.11. A path preference for ProSe Services can be provided by ProSe Application Server to UDR and may be used by PCF for path selection policy generation and update.
When a 5G ProSe Layer-3 Remote UE is using a 5G ProSe Layer-3 UE-to-Network Relay without involving N3IWF, the PCF based provisioning and update of 5G ProSe Policy/parameters to the 5G ProSe Layer-3 Remote UE are not supported.
5.1.1a General principles for applying policy/parameters
For services (i.e. 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay discovery, 5G ProSe UE-to-Network Relay communication, 5G ProSe UE-to-UE Relay discovery, 5G ProSe UE-to-UE Relay communication, 5G ProSe Layer-3 multi-hop UE-to-Network Relay discovery, 5G ProSe Layer-3 multi-hop UE-to-Network Relay communication, 5G ProSe Layer-3 multi-hop UE-to-UE Relay discovery and 5G ProSe Layer-3 multi-hop UE-to-UE Relay communication) over PC5 reference point, the operator may pre-configure the UEs with the required provisioning parameters for the service, without the need for the UEs to connect to the 5GC to get this initial configuration. The following apply:
- The provisioning parameters for the service could be from different sources and their priorities are described in clause 5.1.1.
- The ME provisioning parameters shall not be erased when a USIM is deselected or replaced.
- The UE shall use radio resources for the service as follows:
- While a UE has a serving cell and is camped on a cell and the UE intends to use for 5G ProSe the radio resources (i.e. carrier frequency) operated by this cell, then the UE shall use the radio resource description indicated by this cell the UE is camped on and ignore any radio resource description of the same radio resource provisioned in the ME or the UICC. If the cell does not provide radio resources for ProSe, the UE shall not perform ProSe message transmission and reception on radio resources operated by this cell. The UE is allowed to perform the service with another UE not served by the same PLMN;
- If the UE intends to use "operator-managed" radio resources (i.e. carrier frequency) for 5G ProSe that are not operated by the UE's serving cell, as specified in the related Policy/Parameter provisioning, or if the UE is out of coverage, the UE shall search for a cell in any PLMN that is operating the provisioned radio resources (i.e. carrier frequency) as defined in TS 38.300 [12] and TS 38.304 [13]; and:
- If the UE finds such a cell in the registered PLMN or a PLMN equivalent to the registered PLMN and authorization for the service to this PLMN is confirmed, the UE shall use the radio resource description indicated by that cell. If that cell does not provide radio resources for ProSe, the UE shall not perform ProSe message transmission and reception on those radio resources;
- If the UE finds such a cell but not in the registered PLMN or a PLMN equivalent to the registered PLMN and that cell belongs to a PLMN authorized for the service and provides radio resources for ProSe then the UE shall perform PLMN selection triggered by the service as defined in TS 23.122 [14];
- If the UE finds such cell but not in a PLMN authorized for the service the UE shall not use the service;
- If the UE does not find any such cell in any PLMN, then the UE shall consider itself "not served by NG-RAN" and use radio resources provisioned in the ME or the UICC. If no such provision exists in the ME or the UICC or the provision does not authorize the service, then the UE is not authorized to transmit;
- The UE is allowed to use "operator-managed" radio resources (i.e. carrier frequency) provisioned in the ME or the UICC for the service if the UICC indicates it is authorized;
- If the UE intends to use "non-operator-managed" radio resources (i.e. carrier frequency) for 5G ProSe, according to TS 36.331 [15] or TS 38.331 [16] and as specified in clause 5.1.2.1, then the UE shall perform the service using resource provisioned in the ME or the UICC. If no such provision exists in the ME or the UICC or the provision does not authorize the service, then the UE is not authorized to transmit;
NOTE 1: It is possible for operators to configure UEs (e.g. Public Safety UEs) to use only "operator-managed" radio resources (i.e. carrier frequency) for the service when the UE is "not served by NG-RAN".
- The UE provisioning shall support setting Geographical Areas;
NOTE 2: It is possible for a UE to use other radio resources for 5G ProSe based on the Geographical Area instead of those operated by the serving NG-RAN cell, when provisioned in the UE, even if the UE's serving cell offers normal service and the SIBs for NR Sidelink communication defined in TS 38.331 [16] indicates that the service (the service) is available. This is to cover the scenario when e.g. the radio resources used for the service are not owned by the serving network of the UE.
NOTE 3: When cross-carrier operation is supported, according to TS 36.331 [15] or TS 38.331 [16], a UE can be instructed by its serving cell to perform the service over a different carrier frequency. The UE is still considered as "served by NG-RAN" in this case.
NOTE 4: The scenario that a cell is detected and the cell does not provide support for the service when the UE attempts to use a carrier frequency configured for the service, is considered a configuration error. Therefore, the UE does not transmit on that frequency to avoid interference to the network.
- The service is only specified for NR.
NOTE 5: It is out of scope of the present specification to define how the UE can locate itself in a specific Geographical Area. When the UE is in coverage of a 3GPP RAT, it can for example, use information derived from the serving PLMN. When the UE is not in coverage of a 3GPP RAT, it can use other techniques, e.g. Global Navigation Satellite System (GNSS). User provided location is not a valid input.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.2 Authorization and Provisioning for 5G ProSe Direct Discovery
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.2.1 Policy/Parameter provisioning for 5G ProSe Direct Discovery
|
The following sets of information for 5G ProSe Direct Discovery over PC5 reference point is provisioned to the UE:
1) Authorization policy for 5G ProSe Direct Discovery:
- When the UE is "served by NG-RAN":
- For open 5G ProSe Direct Discovery:
a) open 5G ProSe Direct Discovery Model A monitoring authorization policy:
- PLMNs in which the UE is authorised to perform 5G ProSe Direct Discovery monitoring.
b) open 5G ProSe Direct Discovery Model A announcing authorization policy:
- PLMNs in which the UE is authorized to perform announcing.
- For restricted 5G ProSe Direct Discovery:
a) restricted 5G ProSe Direct Discovery Model A monitoring authorization policy:
- PLMNs in which the UE is authorised to perform restricted 5G ProSe Direct Discovery Model A monitoring.
b) restricted 5G ProSe Direct Discovery Model A announcing authorization policy:
- PLMNs in which the UE is authorized to perform restricted 5G ProSe Direct Discovery Model A announcing.
c) restricted 5G ProSe Direct Discovery Model B Discoverer operation authorization policy:
- PLMNs in which the UE is authorized to perform Model B Discoverer operation.
d) restricted 5G ProSe Direct Discovery Model B Discoveree operation authorization policy:
- PLMNs in which the UE is authorized to perform Model B Discoveree operation.
NOTE 1: In this specification, [When the UE is "served by NG-RAN"] and [When the UE is "not served by NG-RAN"] have similar meaning as in "served by E-UTRAN" and "not served by E-UTRAN" in TS 23.303 [3], but applied to 5G ProSe Direct discovery/communications over NR PC5 reference point.
- When the UE is "not served by NG-RAN":
- Indicates whether the UE is authorized to perform 5G ProSe Direct Discovery for Model A and Model B when "not served by NG-RAN".
NOTE 2: If both Model A and Model B are authorized for 5G ProSe Direct Discovery, it is up to UE and application implementation to select a discovery model or perform both models simultaneously.
2) Parameters used for 5G ProSe Direct Discovery:
- The mapping of ProSe services (i.e. ProSe identifiers) to Destination Layer-2 ID(s) for sending/receiving initial signalling of discovery messages.
NOTE 3: The same Destination Layer-2 ID for 5G ProSe Direct Discovery can be mapped to more than one ProSe services.
NOTE 4: The values provisioned for the Destination Layer-2 ID(s) for 5G ProSe Direct Discovery, for Destination Layer-2 ID(s) for 5G ProSe Direct Communication, defined in clause 5.1.3.1, for Destination Layer-2 ID(s) for 5G ProSe UE-to-Network Relay Discovery defined in clause 5.1.4.1 and for Destination Layer-2 ID(s) for 5G ProSe UE-to-UE Relay Discovery defined in clause 5.1.5.1, are different from each other.
NOTE 5: A "catch all" entry with the lowest priority can be used for the ProSe services that do not have explicit mapping to the Destination Layer-2 ID(s) for sending/receiving initial signalling of discovery messages.
- Application identifiers to be used for 5G ProSe Direct Discovery over PC5 interface.
NOTE 6: The Security parameters for 5G ProSe Direct Discovery can be provisioned by 5G DDNMF as defined in TS 33.503 [29].
3) Radio parameters when the UE is "not served by NG-RAN":
- Includes the radio parameters per NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 7: Whether a frequency band is "operator managed" or "non-operator managed" in a given Geographical Area is defined by local regulations.
- Default PC5 DRX configuration (see TS 38.331 [16]).
NOTE 8: Radio parameters for 5G ProSe UE-to-UE Relay Discovery when the UE is not "served by NG-RAN" in clause 5.1.5.2.1 and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Discovery are expected to be aligned for direct and relayed discovery for UE to UE communication.
4) Restricted ProSe Discovery UE ID for Restricted Direct Discovery:
- ProSe Discovery UE ID.
5) Group Member Discovery parameters:
- For each discovery group that the UE belongs to include the following parameters that enable the UE to perform Group Member Discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- Application Layer Group ID: Identifies an application layer group or a discovery group that the UE belongs to;
- Layer-2 Group ID: layer-2 ID for Application Layer Group ID;
- User Info ID: For Model A, this corresponds to the Announcer Info parameter when the UE is acting as an announcing UE. For Model B, this corresponds to the Discoverer Info in Solicitation messages and the Discoveree Info in Response messages, when the UE is acting as a discoverer or discoveree UE respectively.
NOTE 9: User Info ID is expected to be assigned uniquely to a user within the discovery group.
6) Optionally, the 5G DDNMF address (either FQDN or IP address) in the Home PLMN.
7) Validity timer indicating the expiration time of the Policy/Parameter for 5G ProSe Direct Discovery.
The above parameter sets bullet 2), bullet 3), bullet 5) and bullet 7) may be provided or updated to the UE by the ProSe Application Server, except for the Security parameters in bullet 2).
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.2.2 Principles for applying parameters for 5G ProSe Direct Discovery
|
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe Direct Discovery service.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.3 Authorization and Provisioning for 5G ProSe Direct Communication
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.3.1 Policy/Parameter provisioning for 5G ProSe Direct Communication
|
The following sets of information for 5G ProSe Direct Communications over PC5 reference point is provisioned to the UE:
1) Authorization policy:
- When the UE is "served by NG-RAN":
- PLMNs in which the UE is authorized to perform 5G ProSe Direct Communications over PC5 reference point when "served by NG-RAN".
- When the UE is "not served by NG-RAN":
- Indicates whether the UE is authorized to perform 5G ProSe Direct Communications over PC5 reference point when "not served by NG-RAN".
NOTE 1: In this specification, [When the UE is "served by NG-RAN"] and [When the UE is "not served by NG-RAN"] are relevant to 5G ProSe Direct Communications over NR PC5 reference point.
2) Groupcast mode 5G ProSe Direct Communication policy/parameters:
- For each application layer group supported include the parameters that enable the UE to perform Groupcast mode 5G ProSe Direct Communication when provided by PCF or provisioned in the ME or configured in the UICC:
- Application Layer Group ID: Identifies an application layer group that the UE belongs to.
- ProSe Layer-2 Group ID: Destination Layer-2 ID applicable only when the Application Layer Group ID is provided by the application layer
- ProSe Group IP multicast address
- Indication whether the UE should use IPv4 or IPv6 for that group
- For a specific Group configured to operate using IPv4, optionally an IPv4 address to be used by the UE as a source address. If none is provisioned, then the UE shall use Dynamic Configuration of IPv4 Link-Local Addresses RFC 3927 [18] to obtain a link local address for the Group.
3) Radio parameters when the UE is "not served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform ProSe Direct Communications over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 2: Whether a frequency band is "operator managed" or "non-operator managed" in a given Geographical Area is defined by local regulations.
NOTE 3: Radio parameters for 5G ProSe Direct Communication when the UE is not "served by NG-RAN" in clause 5.1.5.2.1 and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe UE-to-UE Relay communication are expected to be aligned for direct and relayed UE to UE communication.
4) Policy/parameters related to privacy:
- The list of ProSe services (i.e. ProSe identifiers) with Geographical Area(s) that require privacy support.
- A privacy timer value indicating the duration after which the UE shall change each source Layer-2 ID self-assigned by the UE when privacy is required.
5) Policy/parameters when NR PC5 is selected:
- The mapping of ProSe services (i.e. ProSe identifiers) to radio frequencies with Geographical Area(s).
- The mapping of ProSe services (i.e. ProSe identifiers) to Destination Layer-2 ID(s) for broadcast.
- The mapping of ProSe services (i.e. ProSe identifiers) to Destination Layer-2 ID(s) for groupcast.
- The mapping of ProSe services (i.e. ProSe identifiers) to default Destination Layer-2 ID(s) for initial signalling to establish unicast connection.
NOTE 4: The same default Destination Layer-2 ID for unicast initial signalling can be mapped to more than one ProSe service. In the case where different ProSe services are mapped to distinct default Destination Layer-2 IDs, when the UE intends to establish a single unicast link that can be used for more than one ProSe service, the UE can select any of the default Destination Layer-2 IDs to use for the initial signalling.
NOTE 5: Security policies for Unicast mode 5G ProSe Direct Communication can be provisioned by PCF as defined in TS 33.503 [29].
- The mapping of ProSe services (i.e. ProSe identifiers) to PC5 QoS parameters defined in clause 5.6.1 (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.).
- The mapping of ProSe services (i.e. ProSe identifiers) to the corresponding NR Tx Profiles for broadcast and groupcast (see TS 38.300 [12] and TS 38.331 [16] for further information).
NOTE 6: A "catch all" entry with the lowest priority in each above mapping can be used for the ProSe services that do not have explicit policy/parameters mapping above.
- AS layer configurations (see TS 38.331 [16]), i.e. the mapping of PC5 QoS profile(s) to radio bearer(s), when the UE is "not served by NG-RAN".
- The PC5 QoS profile contains PC5 QoS parameters described in clause 5.4.2 of TS 23.287 [2] and value for the QoS characteristics regarding Priority Level, Averaging Window, Maximum Data Burst Volume if default value is not used as defined in Table 5.4.4-1 of TS 23.287 [2] and in Table 5.6.1-1.
- For broadcast, groupcast and initial signalling to establish unicast connection, PC5 DRX configuration (see TS 38.331 [16]), e.g. the mapping of PC5 QoS profile(s) to PC5 DRX cycle(s), default PC5 DRX configuration, when the UE is "not served by NG-RAN".
6) Path selection policy:
- The mapping of ProSe services (i.e. ProSe identifiers) to path preference (i.e. PC5 preferred, Uu preferred, or no preference) as defined in clause 5.11.
NOTE 7: The path selection policy can be a one mapping for all ProSe services, i.e. same path preference for all ProSe services.
7) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Direct Communication.
The above parameter sets from bullet 2) to 7) may be provided or updated to the UE by the ProSe Application Server.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.3.2 Principles for applying parameters for 5G ProSe Direct Communication
|
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe Direct Communication service.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.4 Authorization and Provisioning for 5G ProSe UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.4.1 Policy/Parameter provisioning for 5G ProSe UE-to-Network Relay
|
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe UE-to-Network Relay:
1) Authorisation policy for acting as a 5G ProSe Layer-3 and/or Layer-2 UE-to-Network Relay when "served by NG-RAN":
- PLMNs in which the UE is authorized to relay traffic for 5G ProSe Layer-3 and/or Layer-2 Remote UEs.
The authorisation for a UE to act as a 5G ProSe UE-to-Network Relay also authorizes the use of 5G ProSe UE-to-Network Relay Discovery with Model A and Model B.
NOTE 1: It is up to UE and application implementation to select a discovery model or whether to perform both models simultaneously.
2) ProSe Relay Discovery policy/parameters for 5G ProSe UE-to-Network Relay:
- Includes the parameters that enable the UE to perform 5G ProSe UE-to-Network Relay Discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe UE-to-Network Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-Network Relay Layer Indicator per RSC, optional Control Plane Security Indicator per RSC). The UE-to-Network Relay Layer Indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service. If the Control Plane Security Indicator is provided for a RSC, then the Control Plane based security procedure as described in clause 5.1.4.3.2 is performed for UE-to-Network Relay Communication for that RSC, otherwise if it is not provided for a RSC, then the User Plane based security procedure as described in clause 5.1.4.3.3 is performed for that RSC. RSC dedicated for emergency service may also be provisioned.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Announcement and Relay Discovery Additional Information messages and receiving Relay Discovery Solicitation messages;
- For 5G ProSe Layer-3 UE-to-Network Relay, the PDU Session parameters (PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference) to be used for the relayed traffic for each ProSe Relay Service Code;
- Includes security related content for 5G ProSe UE-to-Network Relay, see TS 33.503 [29].
NOTE 2: 5G ProSe Relay Discovery policy/parameters can be provided from ProSe Application Server to the 5G ProSe UE-to-Network Relay, except for the Security parameters in bullet 2).
3) For 5G ProSe Layer-3 UE-to-Network Relay, QoS mapping(s):
- Each QoS mapping entry includes:
- a mapping between a 5QI value and a PQI value;
- a PQI PDB adjustment factor, for the PC5 communication for the 5G ProSe Layer-3 UE-to-Network Relay operation;
- optional the Relay Service Code(s) associates with the QoS mapping entry.
4) For 5G ProSe Layer-3 UE-to-Network Relay to relay Ethernet or Unstructured traffic from 5G ProSe Layer-3 Remote UE by using IP type PDU Session:
- Mapping of ProSe Service(s) to ProSe Application Server address information (consisting of IP address/FQDN and transport layer port number).
5) Parameters to broadcast warning messages:
- Configured Destination Layer-2 ID(s);
- PC5 QoS parameters defined in clause 5.6.1;
- the NR Tx Profile based on the configuration as specified in clause 5.1.3.1.
NOTE 3: It is up to inter operator alignment and network configuration whether a common Destination Layer-2 ID or IDs are used for all UEs cross PLMNs in a particular region for Public Warning Notification Relaying.
6) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe UE-to-Network Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Remote UE and thereby enabling the use of a 5G ProSe UE-to-Network Relay:
1) Authorisation policy for using a 5G ProSe Layer-3 and/or Layer-2 UE-to-Network Relay:
- For 5G ProSe Layer-3 Remote UE, indicates whether the UE is authorised to use a 5G ProSe Layer-3 UE-to-Network Relay.
- For 5G ProSe Layer-2 Remote UE, indicates the PLMNs in which the UE is authorized to use a 5G ProSe Layer-2 UE-to-Network Relay.
The authorisation for a UE to act as a 5G ProSe Remote UE also authorizes the use of 5G ProSe UE-to-Network Relay discovery with Model A and Model B.
NOTE 4: It is up to UE and application implementation to select a discovery model or whether to perform both models simultaneously.
2) Policy/parameters for 5G ProSe UE-to-Network Relay Discovery:
- Includes the parameters for 5G ProSe Relay Discovery and for enabling the UE to connect to the 5G ProSe UE-to-Network Relay after discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe UE-to-Network Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-Network Relay Layer indicator per RSC, optional Control Plane Security Indicator per RSC). The UE-to-Network Relay Layer Indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service. If the Control Plane Security Indicator is provided for a RSC, then the Control Plane based security procedures as described in clause 5.1.4.3.2 is performed for UE-to-Network Relay Communication for that RSC, otherwise if it is not provided for a RSC, then the User Plane based security procedures as described in clause 5.1.4.3.3 is performed for that RSC. RSC(s) dedicated for emergency service may be provisioned to enable the support of emergency services for UE-to-Network Relaying.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Solicitation messages and receiving Relay Discovery Announcement and Relay Discovery Additional Information messages;
- For 5G ProSe Layer-3 UE-to-Network Relay, the PDU Session parameters (PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference) to be used for the relayed traffic without using N3IWF access, or an indication of N3IWF access, for each ProSe Relay Service Code;
- For 5G ProSe Layer-3 UE-to-Network Relay, optionally the ProSe application Traffic Descriptor(s) (as defined in TS 23.503 [9]) to be used for the relayed traffic for each ProSe Relay Service Code;
- Includes security related content for 5G ProSe UE-to-Network Relay, see TS 33.503 [29].
3) Policy/parameters for N3IWF selection for 5G ProSe Layer-3 Remote UE:
- N3IWF identifier configuration for 5G ProSe Layer-3 Remote UE (either FQDN or IP address) in the HPLMN.
- 5G ProSe Layer-3 UE-to-Network Relay access node selection information - a prioritized list of PLMNs for N3IWF selection. It also indicates if selection of an N3IWF in a PLMN should be based on Tracking Area Identity FQDN or on Operator Identifier FQDN.
NOTE 5: 5G ProSe Relay Discovery policy/parameters can be provided from ProSe Application Server to the 5G ProSe Remote UE, except for the Security parameters in bullet 2).
4) Parameters to receive warning messages:
- Configured Destination Layer-2 ID(s);
- PC5 QoS parameters defined in clause 5.6.1;
- the NR Tx Profile based on the configuration as specified in clause 5.1.3.1.
NOTE 6: It is up to inter operator alignment and network configuration whether a common Destination Layer-2 ID or IDs are used for all UEs cross PLMNs in a particular region for Public Warning Notification Relaying.
5) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe UE-to-Network Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe UE-to-Network Relay as well as in the UE in support of the UE assuming the role of a 5G ProSe Remote UE and thereby enabling the use of a 5G ProSe UE-to-Network Relay:
1) Radio parameters for 5G ProSe UE-to-Network Relay Discovery when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
- Default PC5 DRX configuration (see TS 38.331 [16]).
2) Radio parameters for 5G ProSe UE-to-Network Relay communication when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Communication over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 7: The validity time of these radio parameters is the same as the validity time of the Policy/Parameter listed above for 5G ProSe UE-to-Network Relay or 5G ProSe Remote UE.
3) Policy/parameters related to privacy:
- A privacy timer value indicating the duration after which the UE shall change each source Layer-2 ID self-assigned by the UE when privacy is required.
5.1.4.1a Policy/Parameter provisioning for 5G ProSe multi-hop UE-to-Network Relay
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay:
1) Authorisation policy for acting as a 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay when "served by NG-RAN":
- PLMNs in which the UE is authorized to relay traffic for 5G ProSe Layer-3 Remote UEs supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay.
The authorisation for a UE to act as a 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay also authorizes the use of 5G ProSe Layer-3 multi-hop UE-to-Network Relay Discovery with Model A and Model B.
NOTE 1: It is up to UE and application implementation to select a discovery model or whether to perform both models simultaneously.
2) ProSe Relay Discovery policy/parameters for 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay:
- Includes the parameters that enable the UE to perform 5G ProSe Layer-3 multi-hop UE-to-Network Relay Discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe Layer-3 multi-hop UE-to-Network Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-Network Relay Layer Indicator per RSC, multi-hop indicator per RSC, maximum number of hops per RSC). The UE-to-Network Relay Layer Indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service. RSC dedicated for emergency service may also be provisioned. The multi-hop indicator indicates whether the associated RSC can be supported for 5G ProSe multi-hop UE-to-Network Relay operation. The maximum number of hops per RSC indicates the maximum number of hops can be supported for the associated RSC.
NOTE 2: The RSC used for multi-hop service is different from the RSC used for single-hop service.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Announcement and Relay Discovery Additional Information messages and receiving Relay Discovery Solicitation messages;
- For 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay, the PDU Session parameters (PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference) to be used for the relayed traffic for each ProSe Relay Service Code;
NOTE 3: 5G ProSe Relay Discovery policy/parameters can be provided from ProSe Application Server to the 5G ProSe UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay.
3) For 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay to relay Ethernet or Unstructured traffic from 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay by using IP type PDU Session:
- Mapping of ProSe Service(s) to ProSe Application Server address information (consisting of IP address/FQDN and transport layer port number).
4) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Layer-3 multi-hop UE-to-Network Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay and thereby enabling the use of a 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay:
1) Authorisation policy for using a 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay:
- For 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay, indicates whether the UE is authorised to use a 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay.
The authorisation for a UE to act as a 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay also authorizes the use of 5G ProSe Layer-3 multi-hop UE-to-Network Relay discovery with Model A and Model B.
NOTE 4: It is up to UE and application implementation to select a discovery model or whether to perform both models simultaneously.
2) Policy/parameters for 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay:
- Includes the parameters for 5G ProSe Relay Discovery and for enabling the UE to connect to the 5G ProSe UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay after discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe Layer-3 multi-hop UE-to-Network Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-Network Relay Layer indicator per RSC, multi-hop indicator per RSC, maximum number of hops per RSC). The UE-to-Network Relay Layer Indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service. RSC(s) dedicated for emergency service may be provisioned to enable the support of emergency services for multi-hop UE-to-Network Relaying. The multi-hop indicator indicates whether the associated RSC can be supported for 5G ProSe multi-hop UE-to-Network Relay operation. The maximum number of hops per RSC indicates the maximum number of hops can be supported for the associated RSC.
NOTE 5: The RSC used for multi-hop service is different from the RSC used for single-hop service.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Solicitation messages and receiving Relay Discovery Announcement and Relay Discovery Additional Information messages;
- For 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay, the PDU Session parameters (PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference) to be used for the relayed traffic without using N3IWF access, or an indication of N3IWF access, for each ProSe Relay Service Code;
- For 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay, optionally the ProSe application Traffic Descriptor(s) (as defined in TS 23.503 [9]) to be used for the relayed traffic for each ProSe Relay Service Code;
3) Policy/parameters for N3IWF selection for 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay:
- N3IWF identifier configuration for 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay (either FQDN or IP address) in the HPLMN.
- 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay access node selection information - a prioritized list of PLMNs for N3IWF selection. It also indicates if selection of an N3IWF in a PLMN should be based on Tracking Area Identity FQDN or on Operator Identifier FQDN.
NOTE 6: 5G ProSe Relay Discovery policy/parameters can be provided from ProSe Application Server to the 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay.
4) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Layer-3 multi-hop UE-to-Network Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 Intermediate UE-to-Network Relay:
1) Authorisation policy for acting as a 5G ProSe Layer-3 Intermediate UE-to-Network Relay:
- For 5G ProSe Layer-3 Intermediate UE-to-Network Relay, indicates whether the UE is authorised to act as a 5G ProSe Layer-3 Intermediate UE-to-Network Relay.
The authorisation for a UE to act as a 5G ProSe Layer-3 Intermediate UE-to-Network Relay also authorizes the use of 5G ProSe Layer-3 multi-hop UE-to-Network Relay Discovery with Model A and Model B.
NOTE 7: It is up to UE and application implementation to select a discovery model or whether to perform both models simultaneously.
2) ProSe Relay Discovery policy/parameters for 5G ProSe Layer-3 Intermediate UE-to-Network Relay:
- Includes the parameters that enable the UE to perform 5G ProSe Layer-3 multi-hop UE-to-Network Relay Discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe Layer-3 multi-hop UE-to-Network Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-Network Relay Layer Indicator per RSC, multi-hop indicator per RSC, maximum number of hops per RSC). The UE-to-Network Relay Layer Indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service. RSC dedicated for emergency service may also be provisioned. The multi-hop indicator indicates whether the associated RSC can be supported for 5G ProSe multi-hop UE-to-Network Relay operation. The maximum number of hops per RSC indicates the maximum number of hops can be supported for the associated RSC.
NOTE 8: The RSC used for multi-hop service is different from the RSC used for single-hop service.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Announcement and Relay Discovery Additional Information messages and receiving Relay Discovery Solicitation messages;
- For 5G ProSe Layer-3 Intermediate UE-to-Network Relay, the traffic type (IP, Ethernet, Unstructured) to be used for the relayed traffic for each Relay Service Code;
NOTE 9: 5G ProSe Relay Discovery policy/parameters can be provided from ProSe Application Server to the 5G ProSe Layer-3 Intermediate UE-to-Network Relay.
3) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Layer-3 Intermediate UE-to-Network Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay, in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay and thereby enabling the use of a 5G ProSe Layer-3 UE-to-Network Relay and in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 Intermediate UE-to-Network Relay:
1) Radio parameters for 5G ProSe Layer-3 multi-hop UE-to-Network Relay Discovery when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
- Default PC5 DRX configuration (see TS 38.331 [16]).
2) Radio parameters for 5G ProSe Layer-3 multi-hop UE-to-Network Relay communication when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Communication over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 10: The validity time of these radio parameters is the same as the validity time of the Policy/Parameter listed above for 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay or 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-Network Relay or 5G ProSe Layer-3 Intermediate UE-to-Network Relay.
3) Policy/parameters related to privacy:
- A privacy timer value indicating the duration after which the UE shall change each source Layer-2 ID self-assigned by the UE when privacy is required.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.4.2 Principles for applying parameters for 5G ProSe UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.4.2.1 Principles for applying parameters for ProSe UE-to-Network Relay discovery
|
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe UE-to-Network Relay discovery service.
5.1.4.2.1a Principles for applying parameters for 5G ProSe multi-hop UE-to-Network Relay discovery
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe multi-hop UE-to-Network Relay discovery service.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.4.2.2 Principles for applying parameters for 5G ProSe UE-to-Network Relay communication
|
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe UE-to-Network Relay communication service.
5.1.4.2.2a Principles for applying parameters for 5G ProSe multi-hop UE-to-Network Relay communication
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe multi-hop UE-to-Network Relay communication service.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.4.3 Network controlled security procedures for 5G ProSe UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.4.3.1 General
|
Security procedures over Control Plane and User Plane are specified for 5G ProSe UE-to-Network relaying in TS 33.503 [29].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.4.3.2 Control Plane based security procedures for 5G ProSe UE-to-Network Relay
|
Control Plane-based security procedures for 5G ProSe UE-to-Network Relay call flow and procedure are defined in TS 33.503 [29], characterised by the following principles:
- 5G ProSe UE-to-Network Relay's NAS signalling is used for the control plane based security procedure to authenticate and authorize a 5G ProSe Remote UE.
- A UE assuming the role of 5G ProSe UE-to-Network Relay can be configured to use a set of slices supporting Control Plane based security procedure. An AMF supporting Control Plane based security procedure for a 5G ProSe UE-to-Network Relay is selected as part of the slice. The 5G ProSe UE-to-Network Relay shall include in discovery messages the RSCs with the Control Plane Security Indicator set, as specified in clause 5.1.4.1, when the requested slice(s) corresponds to Control Plane based security procedure is(are) accepted. In addition, the 5G ProSe UE-to-Network Relay shall includes in discovery messages the RSCs without Control Plane Security Indicator as specified in clause 5.1.4.1.
- A 5G ProSe-enabled UE shall use Control Plane based security procedures if a RSC with Control Plane Security Indicator set is used by the Remote UE to establish the connection. Otherwise, if a RSC without Control Plane Security Indicator is used by the Remote UE to establish the connection, the 5G ProSe-enabled UEs shall use User Plane based security procedures as specified in clause 5.1.4.3.3.
- The AMF serving the 5G ProSe UE-to-Network Relay selects AUSF as specified in clause 6.3.4 of TS 23.501 [4] using the identification information the 5G ProSe Remote UE provided as specified in clause 6.3.3.3.2 of TS 33.503 [29].
- If the 5G ProSe Remote UE is configured by HPLMN to use control plane security procedure, the 5G ProSe Remote UE's HPLMN AUSF shall support control plane based security procedure.
- If a network intends to use control plane security procedure, then all the AMFs within the network slices that the 5G ProSe UE-to-Network Relay uses shall support the control plane based security procedures.
NOTE: If the control plane security procedure is not supported, then the 5G ProSe Remote UE can select another 5G ProSe UE-to-Network Relay or user plane based security can be used.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.4.3.3 User Plane based security procedures
|
User Plane-based security procedures for 5G ProSe UE-to-Network Relay are defined in TS 33.503 [29].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.5 Authorization and Provisioning for 5G ProSe UE-to-UE Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.5.1 Policy/Parameter provisioning for 5G ProSe UE-to-UE Relay
|
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe UE-to-UE Relay:
1) Authorisation policy for acting as a 5G ProSe Layer-3 and/or Layer-2 UE-to-UE Relay:
- when the UE is "served by NG-RAN":
- PLMNs in which the UE is authorized to relay traffic for 5G ProSe Layer-3 and/or Layer-2 End UEs accessing 5G ProSe UE-to-UE Relays over PC5 reference point.
- when the UE is not "served by NG-RAN":
- Indicates whether the UE is authorized to relay traffic for 5G ProSe Layer-3 and/or Layer-2 End UEs accessing 5G ProSe UE-to-UE Relays over PC5 reference point.
- The authorisation for a UE to act as a 5G ProSe UE-to-UE Relay also authorizes the use of 5G ProSe UE-to-UE Relay Discovery with Model A and Model B.
NOTE 1: It is up to UE and application implementation to select a discovery model, or whether to perform both models simultaneously.
2) ProSe Relay Discovery policy/parameters for 5G ProSe UE-to-UE Relay:
- Includes the parameters that enable the UE to perform 5G ProSe UE-to-UE Relay Discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe UE-to-UE Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-UE Relay Layer indicator, Network Assistance Security Indicator). The UE-to-UE Relay Layer indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-UE Relay service. Network Assistance Security Indicator indicates whether the associated RSC is offering security procedures with or without network assistance when the 5G ProSe UE-to-UE Relay is served by NG-RAN.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Announcement message and sending/receiving Relay Discovery Solicitation messages;
- Default Destination Layer-2 ID(s) for sending/receiving Direct Communication Request message for ProSe UE-to-UE Relay Communication with integrated Discovery;
- For 5G ProSe Layer-3 UE-to-UE Relay, the traffic type (IP, Ethernet, Unstructured) to be used for the relayed traffic for each Relay Service Code;
- Includes security related content for 5G ProSe UE-to-UE Relay, see TS 33.503 [29].
NOTE 2: The security mechanism selection according to Network Assistance Security Indicator is specified in TS 33.503 [29].
3) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe UE-to-UE Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe End UE and thereby enabling the use of a 5G ProSe UE-to-UE Relay:
1) Authorisation policy for using a 5G ProSe Layer-3 and/or Layer-2 UE-to-UE Relay:
- When the UE is "served by NG-RAN":
- PLMNs in which the UE is authorized to use a 5G ProSe Layer-3 and/or Layer-2 UE-to-UE Relay.
- When the UE is "not served by NG-RAN":
- Indicates whether the UE is authorised to use a 5G ProSe Layer-3 and/or Layer-2 UE-to-UE Relay.
The authorisation for a UE to act as a 5G ProSe End UE also authorizes the use of 5G ProSe UE-to-UE Relay discovery with Model A and Model B.
NOTE 3: It is up to UE and application implementation to select a discovery model, or whether to perform both models simultaneously.
2) Policy/parameters for 5G ProSe UE-to-UE Relay Discovery:
- Includes the parameters for 5G ProSe UE-to-UE Relay Discovery as a 5G ProSe End UE and for enabling the UE to connect to the 5G ProSe UE-to-UE Relay after discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe UE-to-UE Relay Discovery parameters (Relay Service Code(s), UE-to-UE Relay Layer indicator, Network Assistance Security Indicator). The UE-to-UE Relay Layer indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-UE Relay service. Network Assistance Security Indicator indicates whether the associated RSC is offering security procedures with or without network assistance when the 5G ProSe UE-to-UE Relay is served by NG-RAN.
- Default Destination Layer-2 ID(s) for sending/receiving Relay Discovery Solicitation messages and receiving Relay Discovery Announcement message;
- Default Destination Layer-2 ID(s) for sending/receiving Direct Communication Request message for ProSe UE-to-UE Relay Communication with integrated Discovery;
- For 5G ProSe Layer-3 UE-to-UE Relay, the traffic type (IP, Ethernet, Unstructured) to be used for the relayed traffic for each Relay Service Code;
- Includes security related content for 5G ProSe UE-to-UE Relay, see TS 33.503 [29].
NOTE 4: The security mechanism selection according to Network Assistance Security Indicator is specified in TS 33.503 [29].
3) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe UE-to-UE Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe UE-to-UE Relay as well as in the UE in support of the UE assuming the role of a 5G ProSe End UE and thereby enabling the use of a 5G ProSe UE-to-UE Relay:
1) Radio parameters for 5G ProSe UE-to-UE Relay Discovery when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
- Default PC5 DRX configuration (see TS 38.331 [16]).
NOTE 5: Radio parameters for 5G ProSe UE-to-UE Relay Discovery when the UE is not "served by NG-RAN" and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Discovery in clause 5.1.2.1 are expected to be aligned for direct and relayed discovery for UE to UE communication.
2) Radio parameters for 5G ProSe UE-to-UE Relay communication when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Communication over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 6: Radio parameters for 5G ProSe UE-to-UE Relay communication when the UE is not "served by NG-RAN" and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Communication in clause 5.1.3.1 are expected to be aligned for direct and relayed UE to UE communication.
5.1.5.1a Policy/Parameter provisioning for 5G ProSe Layer-3 multi-hop UE-to-UE Relay
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay:
1) Authorisation policy for acting as a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay:
- when the UE is "served by NG-RAN":
- PLMNs in which the UE is authorized to relay traffic for 5G ProSe Layer-3 End UEs supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay accessing 5G ProSe Layer-3 UE-to-UE Relays supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay over PC5 reference point.
- when the UE is not "served by NG-RAN":
- Indicates whether the UE is authorized to relay traffic for 5G ProSe Layer-3 End UEs supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay accessing 5G ProSe Layer-3 UE-to-UE Relays supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay over PC5 reference point.
- The authorisation for a UE to act as a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay also authorizes the use of 5G ProSe Layer-3 multi-hop UE-to-UE Relay Discovery with Model A and Model B.
NOTE 1: It is up to UE and application implementation to select a discovery model, or whether to perform both models simultaneously.
2) ProSe Relay Discovery policy/parameters for 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay:
- Includes the parameters that enable the UE to perform 5G ProSe Layer-3 multi-hop UE-to-UE Relay Discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe Layer-3 multi-hop UE-to-UE Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-UE Relay Layer indicator, multi-hop indicator per RSC, maximum number of hops per RSC). The UE-to-UE Relay Layer indicator indicates the associated RSC is offering 5G ProSe Layer-3 UE-to-UE Relay service. The multi-hop indicator indicates whether the associated RSC can be supported for 5G ProSe Layer-3 multi-hop UE-to-UE Relay operation. The maximum number of hops per RSC indicates the maximum number of hops can be supported for the associated RSC.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Announcement message and sending/receiving Relay Discovery Solicitation messages;
- For 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay, the traffic type (IP, Ethernet, Unstructured) to be used for the relayed traffic for each Relay Service Code;
3) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Layer-3 multi-hop UE-to-UE Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 End UE supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay and thereby enabling the use of a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay:
1) Authorisation policy for using a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay:
- When the UE is "served by NG-RAN":
- PLMNs in which the UE is authorized to use a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay.
- When the UE is "not served by NG-RAN":
- Indicates whether the UE is authorised to use a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay.
The authorisation for a UE to act as a 5G ProSe Layer-3 End UE supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay also authorizes the use of 5G ProSe Layer-3 UE-to-UE Relay discovery with Model A and Model B.
NOTE 2: It is up to UE and application implementation to select a discovery model, or whether to perform both models simultaneously.
2) Policy/parameters for 5G ProSe Layer-3 multi-hop UE-to-UE Relay Discovery:
- Includes the parameters for 5G ProSe Layer-3 multi-hop UE-to-UE Relay Discovery as a 5G ProSe Layer-3 End UE supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay and for enabling the UE to connect to the 5G ProSe Layer-3 UE-to-UE Relay after discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe Layer-3 multi-hop UE-to-UE Relay Discovery parameters (Relay Service Code(s), UE-to-UE Relay Layer indicator, multi-hop indicator per RSC, maximum number of hops per RSC). The UE-to-UE Relay Layer indicator indicates the associated RSC is offering 5G ProSe Layer-3 UE-to-UE Relay service. The multi-hop indicator indicates whether the associated RSC can be supported for 5G ProSe Layer-3 multi-hop UE-to-UE Relay operation. The maximum number of hops per RSC indicates the maximum number of hops can be supported for the associated RSC.
- Default Destination Layer-2 ID(s) for sending/receiving Relay Discovery Solicitation messages and receiving Relay Discovery Announcement message;
- For 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay, the traffic type (IP, Ethernet, Unstructured) to be used for the relayed traffic for each Relay Service Code;
3) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Layer-3 multi-hop UE-to-UE Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay as well as in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 End UE supporting 5G ProSe Layer-3 multi-hop UE-to-UE Relay and thereby enabling the use of a 5G ProSe Layer-3 UE-to-UE Relay:
1) Radio parameters for 5G ProSe Layer-3 multi-hop UE-to-UE Relay Discovery when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
- Default PC5 DRX configuration (see TS 38.331 [16]).
NOTE 3: Radio parameters for 5G ProSe Layer-3 multi-hop UE-to-UE Relay Discovery when the UE is not "served by NG-RAN" and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Discovery in clause 5.1.2.1 are expected to be aligned for direct and relayed discovery for UE to UE communication.
2) Radio parameters for 5G ProSe Layer-3 multi-hop UE-to-UE Relay communication when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Communication over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 4: Radio parameters for 5G ProSe Layer-3 multi-hop UE-to-UE Relay communication when the UE is not "served by NG-RAN" and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Communication in clause 5.1.3.1 are expected to be aligned for direct and relayed UE to UE communication.
NOTE 5: The RSC used for multi-hop service is different from the RSC used for single-hop service.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.5.2 Principles for applying parameters for 5G ProSe UE-to-UE Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.5.2.1 Principles for applying parameters for ProSe UE-to-UE Relay discovery
|
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe UE-to-UE Relay discovery service.
5.1.5.2.1a Principles for applying parameters for 5G ProSe Layer-3 multi-hop UE-to-UE Relay discovery
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe Layer-3 multi-hop UE-to-UE Relay discovery service.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.1.5.2.2 Principles for applying parameters for 5G ProSe UE-to-UE Relay communication
|
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe UE-to-UE Relay communication service.
5.1.5.2.2a Principles for applying parameters for 5G ProSe Layer-3 multi-hop UE-to-UE Relay communication
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe Layer-3 multi-hop UE-to-UE Relay communication service.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.2 5G ProSe Direct Discovery
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.2.1 General
|
5G ProSe Direct Discovery is defined as the process that detects and identifies another UE in proximity via NR PC5 reference point. As defined in clause 5.3.1.1 in TS 23.303 [3], 5G ProSe Direct Discovery can be open or restricted; it can be standalone or used for subsequent actions e.g. to initiate 5G ProSe Direct Communication.
In the case of inter-PLMN ProSe discovery and communication over PC5 reference point, the PC5 parameters need to be configured in a consistent way among the UEs within a certain region. The architecture for the Inter-PLMN PC5 case is defined in clause 4.2.3.
The UEs may use the PC5 DRX mechanism to perform 5G ProSe Direct Discovery and 5G ProSe UE-to-Network Relay Discovery over PC5 reference point as specified in clause 5.13.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.2.2 5G ProSe Direct Discovery Models
|
There are two models for 5G ProSe Direct Discovery: Model A and Model B which are defined in clause 5.3.1.2 in TS 23.303 [3].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.2.3 5G ProSe UE-to-Network Relay Discovery
|
For 5G ProSe UE-to-Network Relay discovery, both Model A and Model B discovery are supported:
- Model A uses a single discovery protocol message (Announcement).
- Model B uses two discovery protocol messages (Solicitation and Response).
For Relay Discovery Additional Information, only Model A discovery is used.
The procedures for 5G ProSe UE-to-Network Relay discovery are defined in clause 6.3.2.3.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.2.4 5G ProSe Direct Discovery Characteristics
|
5G ProSe Direct Discovery over the PC5 reference point has the following characteristics:
- PC5 communication channel is used to carry the discovery message over PC5. The discovery message over PC5 is differentiated with other PC5 messages by AS layer.
- ProSe layer shall indicate to AS layer whether the signalling is discovery message or PC5-S message.
NOTE 1: The discovery message format is defined in stage 3.
Group discovery/management to support on demand-based group communication for commercial services has the following characteristics:
- The group discovery/formation/management can be carried out in the Application layer in coordination with the Application Server.
- Application layer signalling between the UE and the Application Server is out of scope of this specification.
5G ProSe Direct Discovery with 5G DDNMF has the following characteristics:
- 5G DDNMF in the 5GS is used for 5G ProSe Discovery Direct Code management (including allocation and resolution). The 5G DDNMF gets the PDUID from the PCF and subscribes to notifications on Change of PDUID.
- 5G DDNMF is defined in clause 4.3.2 and the detail procedure for 5G ProSe Direct Discovery with 5G DDNMF is defined in clause 6.3.
Group discovery/management to support public safety has the following characteristics:
- Pre-configured or provisioned information can be used for the 5G ProSe Direct Discovery procedure as defined in clause 5.1.2.
The information elements included in the 5G ProSe Direct Discovery messages are described in clause 5.8.1 and clause 6.3.2.
NOTE 2: Based on UE implementation, the application layer discovery messages are exchanged either as user traffic over PC5 or alternatively as part of metadata in PC5 Direct Discovery message as specified in clause 6.3.2.1 and clause 6.4.2. In the latter case, the PC5 Direct Discovery message can contain additional field carrying application layer metadata information, e.g. the Application layer discovery messages for group discovery. The format and contents of this additional field is out of scope of 3GPP. Performance of the PC5 Direct Discovery message including the application layer information will be affected if the resulted PC5 Direct Discovery message size is too big, e.g. longer delay and lower reliability.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.2.5 5G ProSe UE-to-UE Relay Discovery
|
For 5G ProSe UE-to-UE Relay Discovery, both Model A and Model B discovery are supported:
- Model A uses a single discovery protocol message (Announcement).
- Model B uses two discovery protocol messages (Solicitation and Response).
The procedures for 5G ProSe UE-to-UE Relay Discovery with Model A/Model B are defined in clause 6.3.2.4.
5G ProSe UE-to-UE Relay Communication with integrated Discovery is also supported as specified in clause 6.7.3.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.2.6 5G ProSe multi-hop UE-to-Network Relay Discovery
|
For 5G ProSe multi-hop UE-to-Network Relay discovery, both Model A and Model B discovery are supported.
The procedures for 5G ProSe multi-hop UE-to-Network Relay discovery Model A are defined in clause 6.3.2.5.2.
The procedures for 5G ProSe multi-hop UE-to-Network Relay discovery Model B are defined in clause 6.3.2.5.3.
For Additional parameters announcement procedure, only Model A discovery is used and is defined in clause 6.3.2.5.4.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.2.7 5G ProSe Multi-hop UE-to-UE Relay Discovery
|
For 5G ProSe Multi-hop UE-to-UE Relay discovery, both Model A and Model B discovery are supported:
- Model A uses a single discovery protocol message (Announcement).
- Model B uses two discovery protocol messages (Solicitation and Response).
Based on the RSC used for the discovery, the 5G ProSe Multi-hop UE-to-UE Relay discovery may use one of the two different types of discovery operations, i.e. discovery for IP PDU type and discovery for non-IP PDU type. A 5G ProSe Multi-hop UE-to-UE Relay may support only one or both types of discovery operations.
The procedures for 5G ProSe Multi-hop UE-to-UE Relay discovery Model A/B for IP PDU type are defined in clause 6.3.2.6.2. The procedures for 5G ProSe Multi-hop UE-to-UE Relay discovery Model A/B for non-IP PDUs (e.g. Ethernet or Unstructured) are defined in clause 6.3.2.6.3.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.3 5G ProSe Direct Communication
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.3.1 General
|
5G ProSe Direct Communication over PC5 reference point is supported when the UE is "served by NG-RAN" or when the UE is "not served by NG-RAN". A UE is authorized to perform 5G ProSe Direct Communication when it has valid authorization and configuration as specified in clause 5.1.3. 5G ProSe Direct Communication supports both the cases of public safety and commercial service.
5G ProSe Direct Communication over NR based PC5 reference point supports broadcast mode, groupcast mode and unicast mode.
For broadcast and groupcast mode 5G ProSe Direct Communication, the following data unit types are supported: IPv4, IPv6, Ethernet, Unstructured and Address Resolution Protocol (see RFC 826 [19]).
For unicast mode 5G ProSe Direct Communication, the following data unit types are supported: IPv4, IPv6, Ethernet and Unstructured.
The identifiers used in the 5G ProSe Direct Communication over PC5 reference point are described in clause 5.8.2.
The QoS handling and procedures for the 5G ProSe Direct Communication over PC5 reference point are defined in clauses 5.6 and 6.4.
The UEs may use the PC5 DRX mechanism to perform 5G ProSe Direct Communication over PC5 reference point as specified in clause 5.13.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.3.2 Broadcast mode 5G ProSe Direct Communication
|
Broadcast mode of 5G ProSe direct communication is supported over NR based PC5 reference point. The transmitting UE in broadcast communication determines the destination Layer-2 ID for broadcast as specified in clause 5.8.2 and assigns itself a source Layer-2 ID. The receiving UE determines the destination Layer-2 ID for broadcast reception as specified in clause 5.8.2. The transmitting UE determines the PC5 QoS parameters for this broadcast as specified in clause 5.6.1. The transmitting UE sends the service data using the source Layer-2 ID and the destination Layer-2 ID.
For IP type 5G ProSe direct communication over PC5 reference point, the mechanism for IP address allocation is described in clause 5.5.1.2.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.3.3 Groupcast mode 5G ProSe Direct Communication
|
Groupcast mode of 5G ProSe direct communication is supported over NR based PC5 reference point. Group management is carried out by the application layer in coordination with Application Server and is out of scope of this specification. For commercial services, the Application Layer Group ID is provided by Application Server; and for public safety services, the pre-configured or provisioned Application Layer Group ID will be used for groupcast communication. The group size and member ID information could be used for groupcast control if it is provided by the application layer.
The transmitting UE in groupcast communication determines a source Layer-2 ID and a destination Layer-2 ID and the receiving UE determines destination Layer-2 ID, as specified in clause 5.8.2. The transmitting UE determines the PC5 QoS parameters for this groupcast as specified in clause 5.6.1. The transmitting UE sends the service data using the source Layer-2 ID and the destination Layer-2 ID.
For IP type 5G ProSe direct communication over PC5 reference point, the mechanism for IP address allocation is described in clause 5.5.1.2.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.3.4 Unicast mode 5G ProSe Direct Communication
|
Unicast mode of 5G ProSe direct communication is supported over NR based PC5 reference point. A PC5 unicast link between two UEs is established for the 5G ProSe direct communication; and the PC5 unicast link could be maintained, modified and released according to the application layer requests or communication requirements.
For the PC5 unicast link of the 5G ProSe direct communication, the principal for the PC5 unicast link of V2X communication described in TS 23.287 [2] clause 5.2.1.4 is reused with the following differences:
- V2X service is replaced by ProSe Application;
- V2X service type is replaced by ProSe identifier;
- New data unit types are supported (including IPv4, Ethernet and Unstructured).
For IP type 5G ProSe direct communication over PC5 reference point, the mechanism for IP address/prefix allocation is described in clause 5.5.1.1. The PC5 QoS handling for the unicast mode 5G ProSe direct communication is specified in clause 5.6.1.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4 5G ProSe UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.1 5G ProSe Layer-3 UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.1.1 General
|
The 5G ProSe Layer-3 UE-to-Network Relay shall provide generic function that can relay any IP, Ethernet or Unstructured traffic:
- For IP traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay uses IP type PDU Session towards 5GC.
- For Ethernet traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay can use Ethernet type PDU Session or IP type PDU Session towards 5GC.
- For Unstructured traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay can use Unstructured type PDU Session or IP type PDU Session (i.e. IP encapsulation/de-capsulation by 5G ProSe Layer-3 UE-to-Network Relay) towards 5GC.
The type of traffic supported over PC5 reference point is indicated by the 5G ProSe Layer-3 UE-to-Network Relay e.g. using the corresponding RSC. The 5G ProSe Layer-3 UE-to-Network Relay determines the PDU Session Type based on configuration of the mapping between PDU Session parameters and RSC, as specified in clause 5.1.4.1.
IP type PDU Session and Ethernet type PDU Session can be used to support more than one 5G ProSe Layer-3 Remote UEs while Unstructured type PDU Session can be used to support only one 5G ProSe Layer-3 Remote UE.
NOTE: The maximum number of PDU Sessions can affect the maximum number of 5G ProSe Layer-3 Remote UEs that the 5G ProSe UE-to-Network Relay can support.
The 5G ProSe Layer-3 UE-to-Network Relay provides the functionality to support indirect connectivity to the 5GS for 5G ProSe Layer-3 Remote UEs. A 5G ProSe Layer-3 Remote UE can be located within NG-RAN coverage or outside of NG-RAN coverage.
The 5G ProSe Layer-3 Remote UE and 5G ProSe Layer-3 UE-to-Network Relay may use the PC5 DRX mechanism to perform 5G ProSe UE-to-Network Relay Communications over PC5 reference point as specified in clause 5.13.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.1.2 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support
|
To support 5G ProSe Layer-3 Remote UE services with end-to-end confidentiality and IP address preservation requirements, the 5G ProSe Layer-3 UE-to-Network Relay with N3IWF shall provide access to the 5GC for the 5G ProSe Layer-3 Remote UE via N3IWF using the features defined in clause 4.2.8 of TS 23.501 [4].
5G ProSe Layer-3 UE-to-Network Relay is provisioned with RSC(s) and the corresponding PDU session parameters (e.g. S-NSSAI) to support N3IWF access as part of 5G ProSe Layer-3 UE-to-Network Relay Policy/parameters. When a 5G ProSe Layer-3 Remote UE connects with the corresponding RSC, the 5G ProSe Layer-3 UE-to-Network Relay determines the corresponding PDU session parameters based on the requested RSC.
NOTE: The 5G ProSe Layer-3 UE-to-Network Relay only includes a RSC in discovery message when the corresponding PDU session parameters (e.g. S-NSSAI) are authorized to be used in the accessed network.
The 5G ProSe Layer-3 Remote UE selects N3IWF as specified in clause 6.5.1.2.2. The selection of N3IWF follows the regulatory rules of the country where it is located and when required by the regulations the 5G ProSe Layer-3 Remote UE only selects a N3IWF within the local country. QoS differentiation can be provided on per-IPsec Child Security Association basis and the details are provided in clause 5.6.2.2.
The 5GC to which the 5G ProSe Layer-3 UE-to-Network Relay registers and the 5GC to which the 5G ProSe Layer-3 Remote UE registers may be in the same PLMN or different PLMN.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.1.3 Policy control and session binding to support 5G ProSe Layer-3 UE-to-Network Relay without N3IWF
|
To enable support for policy control for 5G ProSe Layer-3 Remote UEs accessing 5GC via a 5G ProSe Layer-3 UE-to-Network Relay without involving N3IWF, the policy control functionality specified in TS 23.503 [9] is applied with the following functionalities:
- For non-emergency service over the 5G ProSe Layer-3 UE-to-Network Relay, the SMF and PCF shall be configured with DNN(s) dedicated for UE-to-Network Relay connectivity, as specified in clause 5.1.4.1.
NOTE 1: If Local Breakout configuration is supported for relay connectivity, the DNN dedicated for UE-to-Network Relay connectivity needs to be well-known DNN to allow seamless operation across various operators' networks.
NOTE 2: For emergency service over the 5G ProSe Layer-3 UE-to-Network Relay (as specified in clause 5.4.4.3), emergency DNN configured in the Relay's AMF (as specified in clause 5.16.4 of TS 23.501 [4]) is used.
- The AF discovers the PCF serving the 5G ProSe Layer-3 UE-to-Network Relay PDU Session as specified in clause 6.1.1.2 of TS 23.503 [9].
- The PCF may validate any 5G ProSe Layer-3 Remote UE related service information from the AF based on roaming agreement and the DNN dedicated for UE-to-Network Relay connectivity for non-emergency service from the 5G ProSe Layer-3 Remote UE or emergency DNN for emergency service from the 5G ProSe Layer-3 Remote UE.
NOTE 3: For 5G ProSe Layer-3 UE-to-Network Relay connectivity, the UE identity that the SMF has provided (i.e. 5G ProSe Layer-3 UE-to-Network Relay Identity) and a UE identity provided by the AF (i.e. 5G ProSe Layer-3 Remote UE Identity) can be different, while the Session binding with the PDU Session is valid.
- The 5G ProSe Layer-3 Remote UEs may be assigned a /64 IPv6 Prefix from a shorter IPv6 prefix by the 5G ProSe Layer-3 UE-to-Network Relay. A /64 IPv6 Prefix from a shorter IPv6 prefix needs to be assigned to support policy control and session binding of a 5G ProSe Layer-3 Remote UE behind a 5G ProSe Layer-3 UE-Network Relay.
- For a PDU Session to the DNN dedicated for 5G ProSe Layer-3 UE-to-Network Relay connectivity and using IPv6 prefix delegation (i.e. the assigned IPv6 network prefix is shorter than 64), the PCF shall perform session binding based on the IPv6 network prefix only. A successful session binding occurs whenever a longer prefix received from an AF matches the prefix value of the PDU Session. PCF shall not use the UE Identity for session binding for this PDU Session.
NOTE 4: Support for policy control of Remote UEs behind a 5G ProSe Layer-3 UE-Network Relay using IPv4 is not available.
NOTE 5: If a /64 IPv6 Prefix from a shorter IPv6 prefix is not assigned to the 5G ProSe Layer-3 Remote UE by the 5G ProSe Layer-3 UE-Network Relay then support for policy control and session binding of 5G ProSe Layer-3 Remote UE behind a 5G ProSe Layer-3 UE-Network Relay is not available.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.2 5G ProSe Layer-2 UE-to-Network Relay
|
The 5G ProSe Layer-2 UE-to-Network Relay provides forwarding functionality that can relay any type of traffic over the PC5 link.
The 5G ProSe Layer-2 UE-to-Network Relay provides the functionality to support connectivity to the 5GS for 5G ProSe Layer-2 Remote UEs. A UE is considered to be a 5G ProSe Layer-2 Remote UE if it has successfully established a PC5 link to the 5G ProSe Layer-2 UE-to-Network Relay. A 5G ProSe Layer-2 Remote UE can be located within NG-RAN coverage or outside of NG-RAN coverage.
For PLMN selection and relay selection in the 5G ProSe Layer-2 Remote UE:
- The 5G ProSe Layer-2 Remote UE checks whether the PLMN(s) within the RRC Container (see clause 5.8.3.3) obtained from the 5G ProSe Layer-2 UE-to-Network Relay(s) during 5G ProSe UE-to-Network Relay Discovery in clause 6.3.2.3 are authorized to be connected to via a 5G ProSe Layer-2 UE-to-Network Relay(s) and only the authorized PLMN(s) are then available PLMNs for NAS PLMN selection;
- The 5G ProSe Layer-2 Remote UE selects the 5G ProSe Layer-2 UE-to-Network Relay considering the selected PLMN by NAS layer.
NOTE: A Layer-2 Remote UE can select a PLMN different from the 5G ProSe Layer-2 UE-to-Network Relay's serving PLMN to access emergency and non-emergency services.
The 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay may use the PC5 DRX mechanism to perform 5G ProSe UE-to-Network Relay Communications over PC5 reference point as specified in clause 5.13.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.3 Mobility Restrictions for 5G ProSe UE-to-Network Relaying
|
The handling of Mobility Restrictions for 5G ProSe enabled UE follows the principles as specified in clause 5.3.4.1 of TS 23.501 [4] with the following additions and clarifications:
- Forbidden Area:
- In a Forbidden Area, a 5G ProSe enabled UE is not allowed to perform the Relay operation. If the 5G ProSe UE-to-Network Relay operates in a Forbidden Area of the 5G ProSe Remote UE, the 5G ProSe Remote UE is not allowed to access the network via this 5G ProSe UE-to-Network Relay unless the 5G ProSe Remote UE is attempting for emergency service.
- Service Area Restriction:
- Service Area Restriction is not applicable to 5G ProSe Layer-3 Remote UE.
- Service Area Restriction is not applicable to 5G ProSe enabled MCX-subscribed UEs as defined in clause 5.3.4.1 of TS 23.501 [4].
NOTE 1: It is expected that all 5G ProSe enabled Public Safety UEs are MCX-subscribed as defined in clause 5.16.6 of TS 23.501 [4].
- In a Non-Allowed Area, a 5G ProSe enabled UE follows the principles of a UE in limited service state as specified in clause 5.9. It cannot perform the Relay operation as 5G ProSe Layer-2 UE-to-Network Relay or 5G ProSe Layer-3 UE-to-Network Relay based on the conditions described in clause 5.9 except for emergency service from the 5G ProSe Remote UE as specified in clause 5.4.4.
- In a Non-Allowed Area, a 5G ProSe Layer-2 Remote UE follows the principles as specified in clause 5.3.4.1 of TS 23.501 [4], for communication with the network via the 5G ProSe Layer-2 UE-to-Network Relay.
- Core Network type restriction, RAT type restriction:
In these cases, a 5G ProSe enabled UE is not able to register in the network for normal service and stays in limited service state and the principles in clause 5.9 shall apply. The 5G ProSe Layer-2 Remote UE is allowed to register to the network via the 5G ProSe UE-to-Network Relay for emergency service.
NOTE 2: Closed Access Group information is not specified for 5G ProSe.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.4 Support of emergency service from 5G ProSe Remote UE via 5G ProSe UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.4.1 General
|
When a 5G ProSe enabled UE does not have direct connection to the network for emergency service, the UE may attempt to obtain emergency service via 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay.
NOTE: Direct connection refers to the UE connected to the network via Uu or WLAN. No direct connection to the network for emergency service includes also the case that the RAN broadcast SIB indicates no emergency support as specified in TS 23.122 [14].
A 5G ProSe enabled UE acting as 5G ProSe UE-to-Network Relay shall have a normal registration (including also normal registration for a 5G ProSe Relay enabled UE in Non-Allowed Area). A 5G ProSe enabled UE in limited-service state shall not act as 5G ProSe UE-to-Network Relay. Mobility Restrictions that are overruled for UE requesting direct emergency service are overruled also for 5G ProSe UE-to-Network Relay that is relaying emergency service as specified in clause 5.4.3.
A 5G ProSe enabled UE acting as 5G ProSe UE-to-Network Relay shall only advertise its support for relaying emergency services as defined in clause 5.4.4.2 and clause 5.4.4.3 during 5G ProSe UE-to-Network Relay Discovery.
Dedicated RSC(s) for emergency service needs to be provisioned in the 5G ProSe enabled UEs with capability of 5G ProSe UE-to-Network Relay and/or 5G ProSe Remote UE as specified in clause 5.1.4.
The dedicated RSC(s) for emergency service are used by the 5G ProSe UE-to-Network Relay and 5G ProSe Remote UE during 5G ProSe UE-to-Network Relay Discovery and PC5 link establishment.
A PC5 link associated with a dedicated emergency RSC shall be used for emergency service and for emergency service only.
If the 5G ProSe UE-to-Network Relay needs to establish RRC Connection when the 5G ProSe Remote UE has requested emergency service over the PC5 link, the 5G ProSe UE-to-Network Relay shall use RRC establishment cause "emergency".
The existing positioning function as applicable is reused for the 5G ProSe Remote UE. If no other information is available, the location of the 5G ProSe UE-to-Network Relay can be used as Remote UE location estimate.
For more information on UE specific behaviour and location handling, refer to TS 23.167 [31].
PC5 link for emergency services over 5G ProSe UE-to-Network Relay can be established with or without PC5 security; how to establish PC5 security link for emergency service is specified in TS 33.503 [29].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.4.2 Emergency service from 5G ProSe Remote UE via via 5G ProSe Layer-2 UE-to-Network Relay
|
For a 5G ProSe Layer-2 UE-to-Network Relay to participate in the 5G ProSe UE-to-Network Relay Discovery procedure for emergency service (i.e. sending the UE-to-Network Relay Discovery Announcement message or UE-to-Network Relay Discovery Response message), the serving NG-RAN support of emergency services is required, indicated by it broadcasting ims-EmergencySupport in system information as specified in TS 38.300 [12] and TS 38.331 [16]. The 5G ProSe Layer-2 Remote UE may select a different PLMN from the 5G ProSe Layer-2 UE-to-Network Relay. The 5G ProSe Layer-2 Remote UE may select any PLMN within the RRC Container (see clause 5.8.3.3) obtained from any 5G ProSe Layer-2 UE-to-Network Relay(s) which has announced the RSC dedicated for emergency service during 5G ProSe UE-to-Network Relay Discovery in clause 6.3.2.3.
NOTE: When emergency support is indicated by RAN, 5G ProSe Layer-2 UE-to-Network Relay can participate in the 5G ProSe UE-to-Network Relay Discovery procedure for emergency service (i.e. sending the UE-to-Network Relay Discovery Announcement message or UE-to-Network Relay Discovery Response message) even if its serving PLMN does not support emergency service.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.4.3 Emergency service from 5G ProSe Remote UE via 5G ProSe Layer-3 UE-to-Network Relay
|
A 5G ProSe Layer-3 UE-to-Network Relay participates in the 5G ProSe UE-to-Network Relay Discovery procedure (i.e. sending the UE-to-Network Relay Discovery Announcement message or UE-to-Network Relay Discovery Response message) for emergency service only when it has received the Emergency Service Support indicator in its latest Registration Accept from the AMF.
If PC5 connection is requested using dedicated RSC for emergency service, then the 5G ProSe Layer-3 UE-to-Network Relay sets the RRC Establishment cause to "emergency" when establishing an RRC connection.
For 5G ProSe Layer-3 UE-to-Network Relay without N3IWF:
- the 5G ProSe Layer-3 UE-to-Network Relay sets up an emergency PDU Session to support the 5G ProSe Remote UE's emergency service.
- A 5G ProSe Layer-3 UE-to-Network Relay shall only serve emergency services for either itself or for one 5G ProSe Layer-3 Remote UE but not for more than one UE at the same time. In possible conflict case, the prioritisation between the emergency calls is determined by the local regulations, if available. In the absence of local regulations, prioritisation between the emergency calls is 5G ProSe Layer-3 UE-to-Network Relay implementation specific.
- If a 5G ProSe Layer-3 UE-to-Network Relay is not able to handle relayed emergency services due to having an active emergency service (of its own or for a 5G ProSe Layer-3 Remote UE emergency service), the 5G ProSe Layer-3 UE-to-Network Relay shall not advertise its support of emergency service and shall not respond to any new 5G ProSe Layer-3 Remote UE's requests for relaying emergency services.
NOTE: The 5G ProSe Layer-3 Remote UE's requests refers to either 5G ProSe UE-to-Network Relay Discovery Solicitation message with model B, or Direct Communication Request message including the dedicated RSC for emergency service.
When a 5G ProSe Layer-3 Remote UE needs to initiate emergency service, it should attempt to use 5G ProSe Communication for emergency service via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF procedures before attempting to establish an emergency PDU Session via 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support.
For information on the handling of emergency number, P-CSCF address and access type setting, refer to TS 23.167 [31].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.5 5G ProSe Intermediate UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.5.1 General
|
5G ProSe Intermediate UE-to-Network Relay can operate within NG-RAN coverage or out of NG-RAN coverage. The 5G ProSe Intermediate UE-to-Network Relays, 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay may have different HPLMNs.
The maximum number of 5G ProSe Intermediate UE-to-Network Relay on the path of 5G ProSe Remote UE is controlled by the maximum number of hops value configured on the 5G ProSe Intermediate UE-to-Network Relays per RSC, i.e. less than the value of the maximum number of hops. When multiple 5G ProSe Intermediate UE-to-Network Relays are used on the path, a relay (5G ProSe Intermediate UE-to-Network Relay or 5G ProSe UE-to-Network Relay) that has less hops to the NG-RAN is the parent relay of the child relay (5G ProSe Intermediate UE-to-Network Relay) that has more hops to the NG-RAN.
For a 5G ProSe Remote UE accessing 5G ProSe UE-to-Network Relay via one or more 5G ProSe Intermediate UE-to-Network Relay, the principles defined in clauses 5.4.1 to 5.4.4 apply.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.4.5.2 5G ProSe Layer-3 Intermediate UE-to-Network Relay
|
The 5G ProSe Layer-3 Intermediate UE-to-Network Relay proides relay service for any IP, Ethernet or Unstructured traffic based on the corresponding RSC announced by the 5G ProSe UE-to-Network Relay. The 5G ProSe Layer-3 Intermediate UE-to-Network Relay determines the traffic type based on configuration of the mapping between PDU Session parameters and RSC, as specified in clause 5.1.4.1a.
For IP type of traffic, the 5G ProSe Layer-3 Intermediate UE-to-Network Relay needs to act as an IP router and for Ethernet type of traffic, the 5G ProSe Layer-3 Intermediate UE-to-Network Relay needs to act as an Ethernet switch.
In case of IP type of traffic or Ethernet type of traffic, the 5G ProSe Layer-3 Intermediate UE-to-Network Relay's upstream Layer-2 Link (with the 5G ProSe UE-to-Network Relay or another 5G ProSe Layer-3 Intermediate UE-to-Network Relay) can be shared by more than one 5G ProSe Layer-3 Remote UEs or downstream 5G ProSe Layer-3 Intermediate UE-to-Network Relays. For Unstructured type of traffic, one upstream Layer-2 Links can be used to support only one 5G ProSe Layer-3 Remote UE.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.5 IP address allocation
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.5.1 General
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.5.1.1 IP address allocation for unicast mode of 5G ProSe direct communication
|
For unicast mode of 5G ProSe direct communication, the following mechanism for IP address/prefix allocation may be used:
a) DHCP-based IPv4 address allocation with one of the two UEs acting as a DHCP server.
b) IPv6 Stateless Address auto configuration specified in RFC 4862 [17] for assignment of IPv6 prefix, with one of the two UEs acting as IPv6 default router.
NOTE: Which UE acts as a DHCPv4 server or IPv6 default router is negotiated during secure layer-2 link establishment by exchanging the IP Address Configuration as described in clause 6.4.3.
c) IPv6 link-local addresses as defined in RFC 4862 [17] are formed by UEs locally. The IPv6 link-local addresses are exchanged during the establishment of a secure layer-2 link over PC5. The UEs shall disable duplicate address detection after the layer-2 link is established.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.5.1.2 IP address allocation for broadcast and groupcast modes of 5G ProSe direct communication
|
For broadcast and groupcast modes of 5G ProSe direct communication, the following source IP address management applies:
a) the UE configures a link local IPv4 address to be used as the source IP address, as defined in clause 4.5.3 of TS 23.303 [3]. If it is not configured with an address, it uses Dynamic Configuration of IPv4 Link-Local Addresses RFC 3927 [18].
b) the UE configures a link local IPv6 address to be used as the source IP address, as defined in clause 4.5.3 of TS 23.303 [3]. The UE may use this IP address for direct communication without sending Neighbour Solicitation and Neighbour Advertisement message for Duplicate Address Detection.
NOTE: The destination IP address management for broadcast and groupcast modes of ProSe direct communication is left to UE implementation.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.5.1.3 IP address allocation for communication with a 5G ProSe Layer-3 ProSe UE-to-Network Relay
|
For communication with a 5G ProSe Layer-3 UE-to-Network Relay, the following mechanism for IP address/prefix allocation applies:
- The PDU Session Type used for the relay traffic shall support the IP version used by the 5G ProSe Layer-3 Remote UE. If the 5G ProSe Layer-3 Remote UE initiates an allocation of IPv4 address or an IPv6 prefix when the requested IP version is not supported in the corresponding PDU Session then IP address/prefix allocation fails.
a) When the 5G ProSe Layer-3 Remote UE uses IPv4 to access the external DN:
a1) The IPv4 address allocation and IPv4 parameter configuration via DHCPv4 are performed according to RFC 2131 [24] and RFC 4039 [25] procedures. The IPv4 address provided to the 5G ProSe Layer-3 Remote UE from the 5G ProSe Layer-3 UE-to-Network Relay by DHCPv4 procedure shall correspond to a local IPv4 address range configured in the 5G ProSe Layer-3 UE-to-Network Relay.
a2) The DHCPv4 request from the 5G ProSe Layer-3 Remote UE is always sent subsequent to the establishment of the one-to-one 5G ProSe Direct Communication between the 5G ProSe Layer-3 Remote UE and the 5G ProSe Layer-3 UE-to-Network Relay, see details for the IPv4 address allocation in clause 5.4.4.3 of TS 23.303 [3] with the following difference:
- The ProSe Relay UE ID of the ProSe UE-to-Network Relay is replaced by the source Layer-2 ID of the 5G ProSe UE-to-Network Relay for PC5 unicast communication.
b) When the 5G ProSe Layer-3 Remote UE uses IPv6 to access the external DN:
b1) IPv6 network prefix allocation via IPv6 Stateless Address auto-configuration. Router solicitation from the 5G ProSe Layer-3 Remote UE is always sent subsequent to the establishment of the one-to-one ProSe Direct Communication between the 5G ProSe Layer-3 Remote UE and the 5G ProSe Layer-3 UE-to-Network Relay, see details for IPv6 prefix allocation in clause 5.4.4.2 of TS 23.303 [3] with the following differences:
- The 5G ProSe Layer-3 UE-to-Network Relay shall obtain the IPv6 prefix assigned to the 5G ProSe Layer-3 Remote UE via prefix delegation function from the network as defined in clause 5.5.2.
- The ProSe Relay UE ID of the ProSe UE-to-Network Relay is replaced by the source Layer-2 ID of the 5G ProSe UE-to-Network Relay for PC5 unicast communication.
- PDN connection is replaced by PDU Session.
b2) IPv6 parameter configuration via Stateless DHCPv6: The UE may use stateless DHCPv6 for additional parameter configuration.
b3) The 5G ProSe Layer-3 UE-to-Network Relay assigns IPv6 prefixes from IPv6 prefix range that have been assigned to the PDU Session used for the relay traffic via IPv6 prefix delegation.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.5.1.4 IP address allocation for communication with a 5G ProSe Layer-3 UE-to-UE Relay
|
For communication with a 5G ProSe Layer-3 UE-to-UE Relay, the following mechanism for IP address/prefix allocation applies:
- IP address allocation mechanisms of unicast mode of 5G ProSe direct communication as described in clause 5.5.1.1 can be reused on each hop between a 5G ProSe End UE and the 5G ProSe Layer-3 UE-to-UE Relay.
- The 5G ProSe Layer-3 UE-to-UE Relay may provide the IP address of the target 5G ProSe End UE to the source 5G ProSe End UE in the Direct Communication Accept message, if the target 5G ProSe End UE IP address is available at the time.
- The 5G ProSe End UE may obtain the IP address of other 5G ProSe End UEs via the 5G ProSe Layer-3 UE-to-UE Relay using DNS query.
NOTE: 5G ProSe Layer-3 UE-to-UE Relay may support 5G ProSe End UEs of different IP versions by performing IP conversions.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.5.2 IPv6 Prefix Delegation via DHCPv6 for 5G ProSe Layer-3 UE-to-Network Relay
|
IPv6 Prefix Delegation via DHCPv6 for 5G ProSe Layer-3 UE-to-Network Relay is defined in clause 5.8.2.2.4 of TS 23.501 [4].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6 QoS handling
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6.1 QoS handling for 5G ProSe Direct Communication
|
In order to support QoS handling for 5G ProSe Direct Communication, the mechanism defined in clause 5.4 of TS 23.287 [2] is reused with the following differences:
- Only NR PC5 QoS model is used.
- PC5 Packet Filter Set supports three types of packet filters, i.e. the Prose IP Packet Filter Set, ProSe Ethernet Packet Filter Set and the Prose Packet Filter Set. Each PC5 QoS Rule additionally contains the ProSe identifier when the ProSe identifier is not included in the PC5 Packet Filter Set.
- V2X IP Packet Filter Set is replaced by ProSe IP Packet Filter Set.
- V2X Packet Filter Set is replaced by ProSe Packet Filter Set. ProSe Packet Filter Set shall support Packet Filters based on at least any combination of:
- ProSe identifier;
- Source/Destination Layer-2 ID;
- Application Layer ID.
- ProSe Ethernet Packet Filter Set that has the same format as the Ethernet Packet Filter Set defined in clause 5.7.6.3 of TS 23.501 [4] is additionally defined.
- V2X application layer is replaced by ProSe application layer.
- V2X layer is replaced by ProSe layer.
- V2X service type is replaced by ProSe identifier.
- UE-PC5-AMBR is only applied for NR PC5.
- The PQI values are additionally defined. The one-to-one mapping of standardized PQI values that are additionally defined to PC5 QoS characteristics is specified in table 5.6.1-1.
Table 5.6.1-1: Standardized PQI values that are additionally defined to QoS characteristics mapping
PQI
Value
Resource Type
Default Priority Level
Packet Delay Budget
Packet Error
Rate
Default Maximum Data Burst Volume
Default
Averaging Window
Example Services
24
GBR
(NOTE 1)
1
150 ms
10-2
N/A
2000 ms
Mission Critical user plane Push To Talk voice (e.g. MCPTT)
25
2
200 ms
10-2
N/A
2000 ms
Non-Mission-Critical user plane Push To Talk voice, Conversational Voice
26
2
200 ms
10-3
N/A
2000 ms
Mission Critical Video user plane
32
4
300 ms
10-3
N/A
2000 ms
Conversational Video (Live Streaming)
33
3
100 ms
10-3
N/A
2000 ms
Real Time Gaming, Process automation monitoring
34
5
600 ms
10-6
N/A
2000 ms
Non-Conversational Video (Buffered Streaming)
60
Non-GBR
1
120 ms
10-6
N/A
N/A
Mission Critical delay sensitive signalling (e.g. MC-PTT signalling)
61
6
400 ms
10-6
N/A
N/A
Mission Critical Data (e.g. example services are the same as 5QI 6/8/9 as specified in TS 23.501 [4])
70
7
200 ms
10-3
N/A
N/A
Voice,
Video (Live Streaming)
Interactive Gaming
71
7
20 ms
10-6
N/A
N/A
Low Latency eMBB applications Augmented Reality
92
Delay Critical GBR
(NOTE 1)
5
5ms
10-4
20000 bytes
2000 ms
Interactive service - consume VR content with high compression rate via tethered VR headset (See TS 22.261 [6])
93
6
10ms
10-4
20000 bytes
2000 ms
interactive service - consume VR content with low compression rate via tethered VR headset;
Gaming or Interactive Data Exchanging (See TS 22.261 [6])
NOTE 1: GBR and Delay Critical GBR PQIs can only be used for unicast PC5 communications.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6.2 QoS handling for 5G ProSe UE-to-Network Relay operations
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6.2.1 QoS handling for 5G ProSe Layer-3 UE-to-Network Relay without N3IWF
|
For a 5G ProSe Layer-3 Remote UE accessing network via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF, the QoS requirement of the relay traffic between 5G ProSe Layer-3 Remote UE and UPF can be satisfied by the corresponding QoS control for the PC5 link between 5G ProSe Layer-3 Remote UE and 5G ProSe Layer-3 UE-to-Network Relay (PC5 QoS control) and the QoS control for the PDU session established between 5G ProSe Layer-3 UE-to-Network Relay and UPF (i.e. Uu QoS control). The PC5 QoS is controlled with PC5 QoS rules and PC5 QoS parameters (e.g. PQI, GFBR, MFBR, PC5 LINK-AMBR) as specified in clause 5.4 of TS 23.287 [2]. The QoS for the PDU session established between the 5G ProSe Layer-3 UE-to-Network Relay and UPF (i.e. Uu QoS control) is controlled with QoS rules and 5G QoS parameters (e.g. 5QI, GFBR, MFBR) as specified in clause 5.7 of TS 23.501 [4].
As shown in figure 5.6.2.1-1 below, the end-to-end QoS can be met only when the QoS requirements are properly translated and satisfied over the two legs respectively.
Figure 5.6.2.1-1: End-to-End QoS translation for 5G ProSe Layer-3 UE-to-Network Relay operation
To achieve this, the QoS mapping can be pre-configured or provided to the 5G ProSe Layer-3 UE-to-Network Relay by the PCF using Prose Policy as specified in clause 5.1.4.1. The QoS mapping includes combinations of the 5QIs and PQIs mapping as entries. The PQI shall have standardized values as defined in Table 5.6.1-1 and in Table 5.4.4-1 of TS 23.287 [2]. The 5QI shall have standardized values as defined in TS 23.501 [4] clause 5.7.4. The QoS mapping also includes an adjustment factor for the PQI's PDB, e.g. 1/5 of the standardized PDB value in Table 5.6.1-1 and Table 5.4.4-1 of TS 23.287 [2].
If the QoS Flows setup are initiated by network, the SMF can base on the PCC rules or its local configuration to generates the QoS rules and QoS Flow level QoS parameters (e.g. 5QI, GFBR, MFBR) and signal to the 5G ProSe Layer-3 UE-to-Network Relay using PDU Session Establishment/Modification procedure. For the PDU sessions used for relaying, the SMF always provides the QoS Flow level QoS parameters to the 5G ProSe Layer-3 UE-to-Network Relay when establishes a QoS Flow. Then the 5G ProSe Layer-3 UE-to-Network Relay decides the PC5 QoS parameters for the corresponding PC5 QoS Flow by determining the PQI based the QoS mapping and the GFBR and MFBR values for the PC5 GBR QoS Flow are set equal to the GFBR and MFBR values for the GBR QoS Flow respectively. The PCF differentiates the relay traffic based on either local configuration, e.g.by a dedicated DNN or S-NSSAI used for relay traffic or by the traffic filters.
NOTE: Separate QoS mappings can be configured for different RSCs.
If the 5G ProSe Layer-3 Remote UE initiates PC5 QoS Flows setup or modification during the Layer-2 link establishment or modification procedure, the 5G ProSe Layer-3 Remote UE provides the QoS Info as described in clause 6.4.3.6 to the 5G ProSe Layer-3 UE-to-Network Relay. The received PC5 QoS parameters of the QoS Info (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) are interpreted as the end-to-end QoS requirements by the 5G ProSe Layer-3 UE-to-Network Relay for the traffic transmission between 5G ProSe Layer-3 Remote UE and UPF. If the end-to-end QoS requirements can be supported by an entry in QoS mapping, the 5G ProSe Layer-3 UE-to-Network Relay uses the 5QI of the entry for the Uu QoS control and uses the PQI of the entry for the PC5 QoS control. If the end-to-end QoS requirements cannot be supported by any entries in QoS mapping, the 5G ProSe Layer-3 UE-to-Network Relay, based on its implementation, decides the 5QI for the Uu QoS control and PQI for the PC5 QoS control. The 5G ProSe Layer-3 UE-to-Network Relay provides the QoS Info (including PQI value chosen by the 5G ProSe Layer-3 UE-to-Network Relay) as part of the Accept message to the 5G ProSe Layer-3 Remote UE. If the 5G ProSe Layer-3 Remote UE performs the Layer-2 link modification procedure to add new PC5 QoS Flow(s) or modify the existing PC5 QoS Flow(s) for IP traffic or Ethernet traffic over PC5 reference point, the 5G ProSe Layer-3 Remote UE may also provide the PC5 QoS Rule(s) for the PC5 QoS Flow(s) to be added or modified to the 5G ProSe Layer-3 UE-to-Network Relay. The 5G ProSe Layer-3 UE-to-Network Relay may generate the Packet Filters used over Uu reference point based on the received PC5 QoS Rule(s).
The 5G ProSe Layer-3 UE-to-Network Relay performs the UE requested PDU session Modification as defined in TS 23.502 [5], clause 4.3.3 for authorizing the requested QoS including the 5QI and the Packet Filters. If the PCF authorizes the requested QoS with a different 5QI value, the 5G ProSe Layer-3 UE-to-Network Relay may further update the PQI value based on the authorized 5QI value and the 5G ProSe Layer-3 UE-to-Network Relay performs the Layer-2 link modification procedure as defined in clause 6.4.3.6 to update the corresponding PC5 QoS Flow with the updated PQI value.
Alternatively, reflective QoS control over Uu as defined in TS 23.501 [4], clause 5.6.5.3 can be leveraged for dynamic QoS handling of 5G ProSe Layer-3 Remote UE to save on signalling between SMF and 5G ProSe Layer-3 UE-to-Network Relay. Upon reception of a DL packet with RQI on the Uu for the 5G ProSe Layer-3 Remote UE, based on the indicated QFI, the 5G ProSe Layer-3 UE-to-Network Relay creates a new derived QoS rule or updates existing derived QoS rule corresponding to the remote UE, as defined in TS 23.501 [4]. The derived QoS rule is for UL packets from the 5G ProSe Layer-3 Remote UE at Uu interface.
Based on signalled QoS rules (via SMF) or derived QoS rules (Uplink Uu via reflective QoS), the 5G ProSe Layer-3 UE-to-Network Relay may generate the Packet Filters used over PC5 reference point and use the L2 Link Modification procedures as defined in clause 6.4.3.6 to either update existing PC5 QoS Flow(s) or to set up new PC5 QoS Flow(s) (when the QFI to PC5 QoS Flow mapping does not exist). The 5G ProSe Layer-3 UE-to-Network Relay may also provide the PC5 QoS Rule(s) for the PC5 QoS Flow(s) to be added or modified to the 5G ProSe Layer-3 Remote UE.
When the 5G ProSe Layer-3 UE-to-Network relay deletes the derived QoS rule e.g. after the RQ Timer expires, the 5G ProSe Layer-3 UE-to-Network Relay may perform L2 Link Modification procedures defined in clause 6.4.3.6 accordingly using the PQI mapped from the 5QI of the currently used QoS rule after the deletion of the derived QoS rule(s).
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6.2.2 QoS handling for 5G ProSe Layer-3 UE-to-Network relay with N3IWF
|
When accessing 5GS via a 5G ProSe Layer-3 UE-to-Network Relay with N3IWF, the 5G ProSe Layer-3 Remote UE can request for PDU Session establishment or handover an existing PDU session to the N3IWF using UE requested PDU Session Establishment procedure defined in TS 23.502 [5] clause 4.12.5.
Figure 5.6.2.2-1: End-to-End QoS support via Layer-3 UE-to-Network Relay with N3IWF
For the 5G ProSe Layer-3 Remote UE's PDU session(s) established via N3IWF, QoS differentiation can be provided on per-IPsec Child Security Association basis. N3IWF determines the IPsec child SAs as defined in TS 23.502 [5] clause 4.12. The N3IWF is preconfigured to allocate different IPsec child SAs for QoS Flows with different QoS profiles.
Based on configuration, the N3IWF can use one of the options below for QoS support in 5G ProSe Layer-3 UE-to-Network Relay UE's serving PLMN:
- a static QoS mapping mechanism;
- a dynamic QoS signalling based mechanism.
For the static QoS mapping mechanism, a SLA is established to govern the QoS handling between the 5G ProSe Layer-3 Remote UE's 5GC and the 5G ProSe Layer-3 UE-to-Network Relay UE's 5GC, e.g. when the RSC is configured. The SLA can include the mapping between the DSCP markings for the IPsec child SAs with the Remote UE and the corresponding QoS and N3IWF IP address(es). The non-alteration of the DSCP field between N3IWF and the 5G ProSe Layer-3 UE-to-Network Relay UE's UPF is also assumed to be governed by an SLA and by transport-level arrangements that are outside of 3GPP scope. The packet detection filters at the 5G ProSe Layer-3 UE-to-Network Relay UE's UPF can be based on the N3IWF IP address and the DSCP markings.
When the dynamic QoS signalling based mechanism is used by N3IWF, it works as follows:
- When the 5G ProSe Layer-3 Remote UE establishes or handovers a PDU session via the N3IWF as described in clause 4.12.5 of TS 23.502 [5], the PCF serving the PDU Session in the 5G ProSe Layer-3 Remote UE's 5GC detects need for specific QoS and provides corresponding PCC rules to SMF in the 5G ProSe Layer-3 Remote UE's 5GC. The resulted QoS information is provided to N3IWF in step 2b of clause 4.12.5 of TS 23.502 [5]. The N3IWF determines the IPSec Child SA(s) and signals to the 5G ProSe Layer-3 Remote UE, as in step 4 of clause 4.12.5 of TS 23.502 [5] via IKE signalling including the PDU Session ID, the QFI(s), optionally a DSCP value and optionally the Additional QoS Information specified in clause 4.12.5 of TS 23.502 [5]. The PDU Session Establishment Accept message will be sent to the 5G ProSe Layer-3 Remote UE as in step 5 of clause 4.12.5 of TS 23.502 [5].
- Based on Additional QoS Information received from the N3IWF, the 5G ProSe Layer-3 Remote UE determines whether it is necessary to request for QoS session modification for the dedicated QoS Flows toward the 5G ProSe Layer-3 UE-to-Network Relay as described in clause 5.6.2.1. The 5G ProSe Layer-3 Remote UE also provides the N3IWF address, DSCP and the SPI as the traffic filter to enable filtering and mapping of DL traffic towards the right PDU Session/QoS Flow within the 5G ProSe Layer-3 UE-to-Network Relay UE's 5GC.
NOTE: This mechanism allows to communicate GBR related parameters such as GFBR and MFBR from the PCF of the 5G ProSe Layer-3 Remote UE via the N3IWF and the 5G ProSe Layer-3 Remote UE to the 5G ProSe Layer-3 UE-to-Network Relay UE. The 5G ProSe Layer-3 UE-to-Network Relay UE would be able to request the GBR resources from its serving network using UE requested PDU session modification as in clause 4.3.3. of TS 23.502 [5].
- If the 5G ProSe Layer-3 UE-to-Network Relay performs the PDU Session Modification procedure, the PCF in the 5G ProSe Layer-3 UE-to-Network Relay UE's 5GC authorizes the QoS parameters. If the PDU Session Modification procedure authorized the requested QoS parameters, the 5G ProSe Layer-3 UE-to-Network Relay acknowledges the 5G ProSe Layer-3 Remote UE over PC5. The 5G ProSe Layer-3 UE-to-Network Relay also provides the traffic filter provided by the 5G ProSe Layer-3 Remote UE to the SMF during the PDU Session Modification procedure and the SMF updates the PSA UPF with DL Packet Detection Rules.
- The PSA UPF in the 5G ProSe Layer-3 UE-to-Network Relay UE's 5GC maps the DL traffic from IPSec Child SA tunnel to appropriate PDU Session/QoS Flow considering SPI and N3IWF address (filters provided by the 5G ProSe Layer-3 Remote UE).
- The 5G ProSe Layer-3 Remote UE's or the 5G ProSe Layer-3 Remote UE's 5GC may initiated PDU Session Modification procedures as specified in clause 4.12.6 of TS 23.502 [5]. When the 5G ProSe Layer-3 Remote UE received QoS information from the N3IWF, the same interactions between the 5G ProSe Layer-3 Remote UE and 5G ProSe Layer-3 UE-to-Network Relay and between the 5G ProSe Layer-3 UE-to-Network Relay and its 5GC as described above apply.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6.2.3 QoS handling for 5G ProSe Layer-2 UE-to-Network Relay
|
For a 5G ProSe Layer-2 Remote UE accessing network via 5G ProSe Layer-2 UE-to-Network Relay, the existing 5G QoS control is reused between the 5G ProSe Layer-2 Remote UE and the 5G ProSe Layer-2 Remote UE's core network. The 5G ProSe Layer-2 Remote UE's SMF provides QoS profiles to NG-RAN, how NG-RAN performs QoS enforcement for PC5 interface (between the 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay) and Uu interface (between the 5G ProSe Layer-2 UE-to-Network Relay and RAN) is specified in TS 38.300 [12].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6.2.4 QoS handling for 5G ProSe Multi-hop Layer-3 UE-to-Network Relay without N3IWF
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6.2.4.1 General
|
End-to-end QoS management for Multi-hop UE-to-Network Relays is done similarly as QoS management for single hop Layer-3 UE-to-Network Relay as defined in clause 5.6.2.1, with enhancement to handle QoS split over multiple legs of PC5 interface.
As shown in figure 5.6.2.4-1 below, the end-to-end QoS can be met only when the QoS requirements are properly translated and satisfied over the multiple legs respectively.
Figure 5.6.2.4-1: End-to-End QoS translation for 5G ProSe Multi-hop Layer-3 UE-to-Network Relay operation
To achieve this, the QoS mapping can be pre-configured or provided to the 5G ProSe Layer-3 UE-to-Network Relay by the PCF using Prose Policy as specified in clause 5.1.4.1. When 5G ProSe Layer-3 UE-to-Network Relay conducts the mapping between 5QI and PQI, it may use the mapping information as specified in clause 5.6.2.1, with multi-hop adjustment taking into account the number of hops to the 5G ProSe Layer-3 Remote UE.
The 5G ProSe Layer-3 UE-to-Network to derive the maximum packet delay budget that applies to the PC5 link over each adjacent hop from the end-to-end QoS info based on a hop adjustment factor, e.g. 1/5 of the standardized PDB value of the PQI for hop count =5.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6.2.4.2 Network initiated QoS Flows
|
If the QoS Flows setup are initiated by the network, the SMF can base on the PCC rules or its local configuration to generates the QoS rules and QoS Flow level QoS parameters (e.g. 5QI, GFBR, MFBR) and signal to the 5G ProSe Layer-3 UE-to-Network Relay using PDU Session Establishment/Modification procedure. For the PDU sessions used for relaying, the SMF always provides the QoS Flow level QoS parameters to the 5G ProSe Layer-3 UE-to-Network Relay when the network triggers establishement of a QoS Flow.
Based on the received QoS parameters from SMF, the 5G ProSe Layer-3 UE-to-Network Relay decides the end-to-end PC5 QoS parameters for the corresponding PC5 QoS Flow based on the QoS mapping as defined in clause 5.6.2.1, taking into account the number of hops to the 5G ProSe Layer-3 Remote UE. The end-to-end PC5 QoS parameters are interpreted as the end-to-end QoS requirements for the traffic transmission between 5G ProSe Layer-3 Remote UE and the 5G ProSe Layer-3 UE-to-Network Relay. The 5G ProSe Layer-3 UE-to-Network Relay also decides the maximum PC5 PDB based on the end-to-end PC5 QoS parameters and the number of hops to the 5G ProSe Layer-3 Remote UE. The 5G ProSe Layer-3 UE-to-Network Relay determines the PC5 QoS Flow parameters, based on the end-to-end PC5 QoS parameters, hop adjustment factor and hop info (e.g. hop count or path info). The 5G ProSe Layer-3 UE-to-Network Relay provides the end-to-end PC5 QoS info, the maximum PC5 PDB and the generated PC5 QoS Flow parameters to the next hop Iintermediate UE-to-Network Relay towards the 5G ProSe Layer-3 Remote UE, using layer-2 link modification procedure.
The Intermediate UE-to-Network Relay(s) applies the received PC5 QoS Flow parameters on the upstream PC5 link towards the parent relay. The Intermediate UE-to-Network Relay(s), based on its implementation, determines the PC5 Flow QoS parameters for next hop PC5 link towards the 5G ProSe Layer-3 Remote UE, based the received end-to-end PC5 QoS info, maximum PC5 PDB, hop adjustment factor and hop info (e.g. hop count or path info). The PDB for the PC5 QoS Flow parameters needs to be lower than the maximum PC5 PDB. The GFBR and MFBR values for the next hop PC5 GBR QoS Flow are set equal to the GFBR and MFBR values of the received end-to-end PC5 QoS info respectively.
Then the Intermediate UE-to-Network Relay(s) provides the end-to-end PC5 QoS info, the maximum PC5 PDB and the generated PC5 QoS Flow parameters to the next hop Iintermediate UE-to-Network Relay towards the 5G ProSe Layer-3 Remote UE, using layer-2 link modification procedure, until it reaches the 5G ProSe Remote UE.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6.2.4.3 Remote UE initiated QoS Flows
|
If the 5G ProSe Layer-3 Remote UE initiates PC5 QoS Flows setup or modification during the Layer-2 link establishment or modification procedure, the 5G ProSe Layer-3 Remote UE provides the QoS Info as described in clause 6.4.3.6 to its connected Intermediate UE-to-Network Relay. The PC5 QoS parameters of the QoS Info (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) sent by the 5G ProSe Layer-3 Remote UE are interpreted as the end-to-end QoS requirements for the traffic transmission between 5G ProSe Layer-3 Remote UE and UPF. The intermediate UE-to-Network Relay(s) forwards the received QoS info to the 5G ProSe Layer-3 UE-to-Network Relay, using Layer-2 link establishment or modification procedure.
Based on the received end-to-end QoS parameters from the 5G ProSe Layer-3 Remote UE via intermediate UE-to-Network Relay(s), the 5G ProSe Layer-3 UE-to-Network Relay determines the 5QI for the Uu QoS control and the PQI for end-to-end PC5 QoS control based on the QoS mapping as defined in clause 5.6.2.1 it may also do mapping adjustment by implementation taking into account the number of hops to the 5G ProSe Layer-3 Remote UE.
The 5G ProSe Layer-3 UE-to-Network Relay also determines the maximum PC5 PDB and PC5 QoS Flow parameters for the PC5 link with the next hop Intermediate UE-to-Network Relay towards the 5G ProSe Layer-3 Remote UE, as described in clause 5.6.2.4.2. The 5G ProSe Layer-3 UE-to-Network Relay provides the end-to-end PC5 QoS info and the determined maximum PC5 PDB and PC5 QoS Flow parameters to the next hop Intermediate UE-to-Network Relay towards the 5G ProSe Layer-3 Remote UE, as part of the Accept message for the Layer-2 Link establishment or modification procedure.
The Intermediate UE-to-Network Relay(s) applies the received PC5 QoS Flow parameters in the Accept message from the 5G ProSe Layer-3 UE-to-Network Relay or its parent Intermediate UE-to-Network Relay over the PC5 link.
The Intermediate UE-to-Network Relay(s) decides the PC5 QoS Flow parameters for the next hop PC5 link towards the 5G ProSe Layer-3 Remote UE as described in clause 5.6.2.4.2 and provides the end-to-end PC5 QoS info, maximum PC5 PDB and the PC5 QoS Flow parameters to its connected next hop Intermediate UE-to-Network Relay towards the 5G ProSe Layer-3 Remote UE as part of the Accept message for the Layer-2 Link establishment or modification procedure, until reaching the 5G ProSe Layer-3 Remote UE.
The 5G ProSe Layer-3 UE-to-Network Relay performs the UE requested PDU session Modification as defined in clause 4.3.3 of TS 23.502 [5] for authorizing the requested QoS including the 5QI and the Packet Filters. If the PCF authorizes the requested QoS with a different 5QI value, the 5G ProSe Layer-3 UE-to-Network Relay may further update the PQI value based on the authorized 5QI value and the 5G ProSe Layer-3 UE-to-Network Relay performs the Layer-2 link modification procedure as defined above to update the corresponding PC5 QoS Flow parameters over all the PC5 links towards the 5G ProSe Layer-3 Remote UE.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6.3 QoS handling for 5G ProSe UE-to-UE Relay operations
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6.3.1 QoS handling for 5G ProSe Layer-3 UE-to-UE Relay
|
For a 5G ProSe Layer-3 End UE connecting with another 5G ProSe Layer-3 End UE(s) via 5G ProSe Layer-3 UE-to-UE Relay, the QoS requirement of the relay traffic between the peer 5G ProSe Layer-3 End UE(s) can be satisfied by the corresponding QoS control for the PC5 link between source 5G ProSe Layer-3 End UE and 5G ProSe Layer-3 UE-to-UE Relay (i.e. first hop PC5 QoS control) and the QoS control for the PC5 link between 5G ProSe Layer-3 UE-to-UE Relay and target 5G ProSe Layer-3 End UE (i.e. second hop PC5 QoS control). The first hop PC5 QoS and second hop PC5 QoS is controlled with PC5 QoS rules and PC5 QoS parameters (e.g. PQI, GFBR, MFBR, PC5 LINK-AMBR) as specified in clause 5.6.1.
As shown in figure 5.6.3.1-1 below, the end-to-end QoS is met only when the QoS requirements are properly translated and satisfied over the two legs respectively.
Figure 5.6.3.1-1: End-to-End QoS for 5G ProSe Layer-3 UE-to-UE Relay operation
To achieve this, the source 5G ProSe Layer-3 End UE initiates PC5 QoS Flows setup or modification during the Layer-2 link establishment or modification procedure, the source 5G ProSe Layer-3 End UE provides the QoS Info as described in clause 6.4.3.7.3 to the 5G ProSe Layer-3 UE-to-UE Relay. The received PC5 QoS parameters of the QoS Info (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) are interpreted as the end-to-end QoS requirements by the 5G ProSe Layer-3 UE-to-UE Relay for the traffic transmission between source 5G ProSe Layer-3 End UE and target 5G ProSe Layer-3 End UE. The source 5G ProSe Layer-3 End UE derives the end-to-end QoS parameters as defined in clause 5.6.1. The 5G ProSe Layer-3 UE-to-UE Relay, based on its implementation, decides the PQI for the first hop PC5 QoS control and the PQI for the second hop PC5 QoS control, by considering the received PC5 QoS parameters from the source 5G ProSe Layer-3 End UE. The 5G ProSe Layer-3 UE-to-UE Relay provides the QoS Info (including PQI value chosen by the 5G ProSe Layer-3 UE-to-UE Relay for the second hop) to the target 5G ProSe Layer-3 End UE. After accepted QoS Info of the second hop QoS from the target 5G ProSe Layer-3 End UE is received, 5G ProSe Layer-3 UE-to-UE Relay provides the QoS Info (including PQI value chosen by the 5G ProSe Layer-3 UE-to-UE Relay for the first hop) to the source 5G ProSe Layer-3 End UE with considering the received second hop QoS. If the source 5G ProSe Layer-3 End UE performs the Layer-2 link modification procedure to add new PC5 QoS Flow(s) or modify the existing PC5 QoS Flow(s) for IP traffic or Ethernet traffic over PC5 reference point, the source 5G ProSe Layer-3 End UE may also provide the PC5 QoS Rule(s) for the PC5 QoS Flow(s) to be added or modified to the 5G ProSe Layer-3 UE-to-UE Relay. The 5G ProSe Layer-3 UE-to-UE Relay may generate the Packet Filters used over the second hop based on the received PC5 QoS Rule(s).
For multi-hop 5G ProSe Layer-3 UE-to-UE Relay for non-IP type PDU, each 5G ProSe Layer-3 UE-to-UE Relays split the QoS parameters, according to the received QoS Info, into two parts: one part is the QoS parameters of the previous hop, the other part is the QoS parameters from the 5G ProSe Layer-3 UE-to-UE Relay to the target End UE (the rest QoS parameters). The 5G ProSe Layer-3 UE-to-UE Relay sends the rest QoS parameters to the next hop. When 5G ProSe Layer-3 UE-to-UE determines the QoS parameter, such as PDB, of the previous hop, it may consider the maximum value as the received PDB devided by the number of hops to the target End UE.
As shown in figure 5.6.3.1-2 below, the end-to-end QoS is met only when the QoS requirements are properly satisfied over the multiple legs respectively.
Figure 5.6.3.1-2: End-to-End QoS for Multi-hop 5G ProSe Layer-3 UE-to-UE Relay for non-IP type PDU operation
To achieve this, when the source End UE sets up a PC5 QoS Flow, it provides the End-to-End QoS parameters to a 5G ProSe Layer-3 UE-to-UE Relay. Each 5G ProSe Layer-3 UE-to-UE Relay splits the QoS parameters, according to the received QoS Info, into the QoS parameters of the previous hop and the QoS parameters from itself to the target End UE. The 5G ProSe Layer-3 UE-to-UE Relay sends the rest PC5 QoS parameters to the next hop. Each 5G ProSe Layer-3 UE-to-UE Relay may equally split the PDB among the hops, or up to its own implementation (based on equally splitted value as upper bound).
The target End UE and each 5G ProSe Layer-3 UE-to-UE Relay sends the accepted PC5 QoS parameters and optionally the accumulated QoS parameters to the previous hop during the Layer-2 link establishment or modification procedure. The accepted PC5 QoS parameters may be determined based on the QoS parameters of the previous hop as mentioned above, with considering the received accumulated QoS from next hop.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.6.3.2 QoS handling for 5G ProSe Layer-2 UE-to-UE Relay
|
For a 5G ProSe Layer-2 End UE connecting with another 5G ProSe Layer-2 End UE(s) via 5G ProSe Layer-2 UE-to-UE Relay, the source 5G ProSe Layer-2 End UE and the target 5G ProSe Layer-2 End UE negotiate the end-to-end QoS for the traffic transmission between source 5G ProSe Layer-2 End UE and target 5G ProSe Layer-2 End UE. The QoS enforcement for first hop PC5 interface (between the source 5G ProSe Layer-2 End UE and 5G ProSe Layer-2 UE-to-UE Relay) and second hop PC5 interface (between the 5G ProSe Layer-2 UE-to-UE Relay and the target 5G ProSe Layer-2 End UE) is specified in TS 38.300 [12].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.