hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
4d761cc8095b5982244110685dcb04f8 | 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].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.4.5 5G ProSe Intermediate UE-to-Network Relay
| |
4d761cc8095b5982244110685dcb04f8 | 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.
|
4d761cc8095b5982244110685dcb04f8 | 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 provides 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 the 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 link can be used to support only one 5G ProSe Layer-3 Remote UE.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.4.5.3 5G ProSe Layer-2 Intermediate UE-to-Network Relay
| The 5G ProSe Layer-2 Intermediate UE-to-Network Relay is defined in TS 38.300 [12].
For one 5G ProSe Layer-2 Intermediate UE-to-Network Relay, it connects with only one parent relay for Layer-2 based multi-hop UE-to-Network relay operation. In both Model A and Model B discovery procedures, the 5G ProSe Layer-2 Intermediate UE-to-Network Relay provides information for only one path to the network.
The 5G ProSe Layer-2 Intermediate UE-to-Network Relay only establishes one upstream Layer-2 link towards the parent relay for Layer-2 based multi-hop UE-to-Network relay operation, regardless of the number of Remote UEs it serves.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.5 IP address allocation
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.5.1 General
| |
4d761cc8095b5982244110685dcb04f8 | 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.
|
4d761cc8095b5982244110685dcb04f8 | 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.
|
4d761cc8095b5982244110685dcb04f8 | 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.
|
4d761cc8095b5982244110685dcb04f8 | 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.
|
4d761cc8095b5982244110685dcb04f8 | 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].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.6 QoS handling
| |
4d761cc8095b5982244110685dcb04f8 | 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.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.6.2 QoS handling for 5G ProSe UE-to-Network Relay operations
| |
4d761cc8095b5982244110685dcb04f8 | 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).
|
4d761cc8095b5982244110685dcb04f8 | 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.
|
4d761cc8095b5982244110685dcb04f8 | 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].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.6.2.4 QoS handling for 5G ProSe Multi-hop Layer-3 UE-to-Network Relay without N3IWF
| |
4d761cc8095b5982244110685dcb04f8 | 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.
|
4d761cc8095b5982244110685dcb04f8 | 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 establishment 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 Intermediate 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 Intermediate 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.
|
4d761cc8095b5982244110685dcb04f8 | 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.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.6.3 QoS handling for 5G ProSe UE-to-UE Relay operations
| |
4d761cc8095b5982244110685dcb04f8 | 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 divided 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.
|
4d761cc8095b5982244110685dcb04f8 | 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].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.7 Subscription to 5G ProSe
| The subscription information in the UDM contains information to give the user permission to use 5G ProSe.
At any time, the operator can amend or remove the ProSe UE subscription rights from subscription information in the UDM, or to revoke the user's permission to use 5G ProSe.
The following subscription information is defined for 5G ProSe:
- subscription for open 5G ProSe Direct Discovery for NR PC5:
- open 5G ProSe Direct Discovery Model A.
- subscription for restricted 5G ProSe Direct Discovery for NR PC5:
- restricted 5G ProSe Direct Discovery Model A;
- restricted 5G ProSe Direct Discovery Model A with application-controlled extension;
- restricted 5G ProSe Direct Discovery Model A with "on demand" announcing;
- restricted 5G ProSe Direct Discovery Model B.
- subscription for Broadcast, Groupcast and Unicast mode 5G ProSe Direct Communication for NR PC5.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-2 UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 UE-to-Network Relay.
- subscription for 5G ProSe Layer-2 Remote UE access via 5G ProSe Layer-2 UE-to-Network Relay.
- subscription for 5G ProSe Layer-3 Remote UE access via 5G ProSe Layer-3 UE-to-Network Relay.
- subscription 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 for 5G ProSe UE acting as 5G ProSe Layer-2 UE-to-UE Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 UE-to-UE Relay.
- subscription for 5G ProSe Layer-2 End UE access via 5G ProSe Layer-2 UE-to-UE Relay.
- subscription for 5G ProSe Layer-3 End UE access via 5G ProSe Layer-3 UE-to-UE Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 Intermediate UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 Remote UE supporting Multi-hop 5G ProSe Layer-3 UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 UE-to-Network Relay supporting Multi-hop 5G ProSe Layer-3 UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-2 Intermediate UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-2 Remote UE supporting Multi-hop 5G ProSe Layer-2 UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-2 UE-to-Network Relay supporting Multi-hop 5G ProSe Layer-2 UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 UE-to-UE Relay supporting Multi-hop 5G ProSe Layer-3 UE-to-UE Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 End UE supporting Multi-hop 5G ProSe Layer-3 UE-to-UE Relay.
- UE-PC5-AMBR for NR PC5.
- PC5 QoS parameters as defined in clause 5.6.1 used by NG-RAN.
- the list of the PLMNs authorized for 5G ProSe services, including:
- the list of the PLMNs where the UE is authorised for open 5G Direct Discovery Model A, i.e. to announce or monitor or both.
- the list of the PLMNs where the UE is authorised for restricted 5G ProSe Direct Discovery Model A, i.e. to announce or monitor or both.
- the list of the PLMNs where the UE is authorised for restricted 5G ProSe Direct Discovery Model B, i.e. to perform Discoverer operation or Discoveree operation or both.
- the list of the PLMNs where the UE is authorised to perform Broadcast, Groupcast and Unicast mode 5G ProSe Direct Communication for NR PC5.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 Remote UE.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 UE-to-UE Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 UE-to-UE Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 End UE.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 End UE.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 Intermediate UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 UE-to-Network Relay supporting Multi-hop 5G ProSe Layer-3 UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 Intermediate UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 UE-to-Network Relay supporting Multi-hop 5G ProSe Layer-2 UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 Remote UE supporting Multi-hop 5G ProSe Layer-2 UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 UE-to-UE Relay supporting Multi-hop 5G ProSe Layer-3 UE-to-UE Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 End UE supporting Multi-hop 5G ProSe Layer-3 UE-to-UE Relay.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8 Identifiers
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1 Identifiers for 5G ProSe Direct Discovery
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.0 General
| NOTE: The 5G DDNMF takes the role of "ProSe Function" if it exists in the following definitions in TS 23.303 [3].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.1 ProSe Application ID
| ProSe Application ID is defined in TS 23.303 [3].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.2 Destination Layer-2 ID
| Destination Layer-2 ID is defined in clause 5.6.1 of TS 23.287 [2].
The Destination Layer-2 ID for 5G ProSe Direct Discovery with Model A is selected based on the configuration as described in clause 5.1.2.1. The Destination Layer-2 ID for a Solicitation message for Model B is selected based on the configuration as described in clause 5.1.2.1. The Destination Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery is selected as described in clause 5.8.4.2.
For Group member discovery:
- If an Application Layer Group ID has a configured Layer-2 Group ID, which is provisioned as specified in clause 5.1.2.1, the UE uses this Layer-2 Group ID as the Destination Layer-2 ID,
- otherwise, the UE converts the Application Layer Group ID into a Destination Layer-2 ID.
NOTE: The mechanism for converting the application layer provided Application Layer Group ID to the Destination Layer-2 ID is defined in Stage 3.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.3 Source Layer-2 ID
| Source Layer-2 ID is defined in clause 5.6.1 of TS 23.287 [2].
The UE self-selects a Source Layer-2 ID for 5G ProSe Direct Discovery and Group member discovery. The Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery is selected as described in clause 5.8.4.2.
NOTE: The UE implementation needs to ensure that when the UE self-selects Source Layer-2 IDs, the self-selected Source Layer-2 IDs are different between 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery) in clause 6.3.2 and 5G ProSe Direct Communication (including 5G ProSe UE-to-Network Relay Communication and 5G ProSe UE-to-UE Relay Communication) in clauses 6.4, 6.5 and 6.7 and are different from any other provisioned Destination Layer-2 IDs as described in clause 5.1 and any other self-selected Source Layer-2 IDs used in a simultaneous 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery) with a different discovery model.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.4 ProSe Application Code
| ProSe Application Code is defined in TS 23.303 [3].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.5 ProSe Restricted Code
| ProSe Restricted Code is defined in TS 23.303 [3].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.6 ProSe Query Code
| ProSe Query Code is defined in TS 23.303 [3].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.7 ProSe Response Code
| ProSe Response Code is defined in TS 23.303 [3].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.8 User Info ID
| User Info ID (including Announcer Info, Discoverer Info, Discoveree Info) is defined in clause 3.1.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.9 ProSe Discovery UE ID
| ProSe Discovery UE ID is defined in TS 23.303 [3].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.10 Restricted ProSe Application User ID
| Restricted ProSe Application User ID is defined in TS 23.303 [3].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.11 Announcing PLMN ID
| Announcing PLMN ID is defined in TS 32.277 [22].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.12 Announcer Info
| Announcer Info is one of the uses of User Info ID as described in clause 5.8.1.8.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.13 Discoverer Info
| Discoverer Info is one of the uses of User Info ID as described in clause 5.8.1.8.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.14 Target Info
| Target Info provides information about the targeted discoveree in the Group Member Discovery Solicitation message specified in clause 6.3.2.2.3 and in the 5G ProSe UE-to-Network Relay Discovery Solicitation message specified in clause 6.3.2.3.3. The Target Info is the User Info ID of the discoveree.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.15 Discoveree Info
| Discoveree Info is one of the uses of User Info ID as described in clause 5.8.1.8.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.16 Application Layer Group ID
| Application Layer Group ID is defined in TS 23.303 [3].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.1.17 Monitored PLMN ID
| Monitored PLMN ID is defined in TS 32.277 [22].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.2 Identifiers for 5G ProSe Direct Communication
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.2.1 General
| Each UE has one or more Layer-2 IDs for 5G ProSe direct communication over PC5 reference point, consisting of:
- Source Layer-2 ID(s); and
- Destination Layer-2 ID(s).
Source and Destination Layer-2 IDs are included in layer-2 frames sent on the layer-2 link of the PC5 reference point identifying the layer-2 source and destination of these frames. Source Layer-2 IDs are always self-assigned by the UE originating the corresponding layer-2 frames.
The selection of the Source and Destination Layer-2 ID(s) by a UE depends on the communication mode of 5G ProSe direct communication over PC5 reference point for this layer-2 link, as described in clauses 5.8.2.2, 5.8.2.3 and 5.8.2.4. The Source Layer-2 IDs may differ between different communication modes.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.2.2 Identifiers for broadcast mode 5G ProSe direct communication
| For broadcast mode of 5G ProSe direct communication over PC5 reference point, the UE is configured with the Destination Layer-2 ID(s) to be used for ProSe applications. The Destination Layer-2 ID for a 5G ProSe direct communication is selected based on the configuration as described in clause 5.1.3.1.
The UE self-selects a Source Layer-2 ID.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.2.3 Identifiers for groupcast mode 5G ProSe direct communication
| For groupcast mode of 5G ProSe direct communication over PC5 reference point, the application layer may provide Application Layer Group ID.
The UE determines a Destination Layer-2 ID as below:
- When the Application Layer Group ID is provided by the application layer,
- and when ProSe Layer-2 Group ID is configured for the Application Layer Group ID provided by the application layer as specified in clause 5.1.3.1, the UE uses the ProSe Layer-2 Group ID as the Destination Layer-2 ID; or
- and when ProSe Layer-2 Group ID is not configured for the Application Layer Group ID provided by the application layer, the UE converts the Application Layer Group ID into a Destination Layer-2 ID.
- When the Application Layer Group ID is not provided by the application layer, the UE determines the Destination Layer-2 ID based on configuration of the mapping between ProSe Identifier and Layer-2 ID, as specified in clause 5.1.3.1.
NOTE: The mechanism for converting the application layer provided Application Layer Group ID to the Destination Layer-2 ID is defined in Stage 3.
The UE self-selects a Source Layer-2 ID.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.2.4 Identifiers for unicast mode 5G ProSe direct communication
| For unicast mode of 5G ProSe direct communication over PC5 reference point, the Destination Layer-2 ID used depends on the communication peer. The Layer-2 ID of the communication peer, identified by the peer's Application Layer ID, may be discovered during the establishment of the PC5 unicast link, or known to the UE via prior ProSe direct communications, e.g. existing or prior unicast link to the same Application Layer ID, or obtained from 5G ProSe direct discovery process. The initial signalling for the establishment of the PC5 unicast link may use the known Layer-2 ID of the communication peer, or a default destination Layer-2 ID associated with the ProSe service (i.e. ProSe identifier) configured for PC5 unicast link establishment, as specified in clause 5.1.3.1. During the PC5 unicast link establishment procedure, Layer-2 IDs are exchanged and should be used for future communication between the two UEs, as specified in clause 6.4.3.
The UE maintains a mapping between the Application Layer IDs and the source Layer-2 IDs used for the PC5 unicast links, as the ProSe application layer does not use the Layer-2 IDs. This allows the change of source Layer-2 ID without interrupting the ProSe applications.
When Application Layer IDs change, the source Layer-2 ID(s) of the PC5 unicast link(s) shall be changed if the link(s) was used for 5G ProSe communication with the changed Application Layer IDs.
Based on privacy configuration as specified in clause 5.1.3.1, the update of the new identifiers of a source UE to the peer UE for the established unicast link may cause the peer UE to change its Layer-2 ID and optionally IP address/prefix if IP communication is used as defined in clause 6.4.3.2.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.3 Identifiers for 5G ProSe UE-to-Network Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.3.1 Common identifiers for 5G ProSe UE-to-Network Relay
| The following parameters are used for the 5G ProSe UE-to-Network Relay Discovery Announcement message (Model A), where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and Announcer Info and Relay Service Code are contained in the message:
- Source Layer-2 ID: the 5G ProSe UE-to-Network Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery.
- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery is selected based on the configuration as described in clause 5.1.4.1.
- Announcer Info: provides information (i.e. User Info ID) about the announcing user.
- Relay Service Code: parameter identifying a connectivity service the 5G ProSe UE-to-Network Relay provides to a 5G ProSe Remote UE. The Relay Service Codes are configured in a 5G ProSe UE-to-Network Relay for advertisement. Additionally, the Relay Service Code may also identifies authorized users the 5G ProSe UE-to-Network Relay would offer service to and may be used to select the related security policies or information e.g. necessary for authentication and authorization between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay (e.g. a Relay Service Code for relays for police members only would be different than a Relay Service Code for relays for Fire Fighters only, even though potentially they provided connectivity to same DN e.g. to support Internet Access).
The 5G ProSe UE-to-Network Relay Discovery Announcement message (Model A) is extended and modified as follows when used for 5G ProSe Multi-hop UE-to-Network Relay discovery:
- Hop-Count: This value reflects the number of PC5 hops for the 5G ProSe Remote UE to reach the network. It is set to 1 by the 5G ProSe UE-to-Network Relay and shall be incremented by 1 every time the 5G ProSe UE-to-Network Relay Discovery Announcement message is forwarded by a 5G ProSe Intermediate UE-to-Network Relay.
A 5G ProSe Intermediate UE-to-Network Relay shall only process the 5G ProSe UE-to-Network Relay Discovery Announcement if the Hop-Count is present and the value is less than the (pre-)configured maximum number of hops for the associated RSC and the optional Hop-Limit in the message.
- Source Layer-2 ID: the 5G ProSe UE-to-Network Relay or the 5G ProSe Intermediate UE-to-Network Relay self-selects a Source Layer-2 ID when sending the discovery message.
- Destination Layer-2 ID: the 5G ProSe Intermediate UE-to-Network Relay sets the Destination Layer-2 ID of the 5G ProSe UE-to-Network Relay Discovery Announcement message based on configuration described in clause 5.1.4.1.
- Announcer Info: identify information (i.e. User Info ID) of the announcing 5G ProSe UE-to-Network Relay or the 5G ProSe Intermediate UE-to-Network Relay.
- (optional) Root Relay Info: this is the User Info ID of the 5G ProSe UE-to-Network Relay. A 5G ProSe Intermediate UE-to-Network Relay may store it in the discovery entry and included it in the 5G ProSe UE-to-Network Relay Discovery Announcement message. This information can be used in the relay selection at the 5G ProSe Remote UE or other 5G ProSe Intermediate UE-to-Network Relays.
- (optional) Accumulated QoS for PC5 link: this reflects the QoS supported over all the PC5 links to the Root Relay, i.e. the 5G ProSe UE-to-Network Relay, for this RSC.
- (optional) Hop-Limit: this is the hop limit set by the announcing 5G ProSe UE-to-Network Relay to a value smaller than the configured maximum number of hops.
The following parameters are used for the 5G ProSe UE-to-Network Relay Discovery Solicitation message (Model B), where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and Discoverer Info and Relay Service Code are contained in the message:
- Source Layer-2 ID: the 5G ProSe Remote-UE self-selects a Source Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery.
- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery is selected based on the configuration as described in clause 5.1.4.1.
- Discoverer Info: provides information (i.e. User Info ID) about the discoverer user.
- Target Info: provides information (i.e. User Info ID) about the targeted discoveree user.
- Relay Service Code: information about connectivity that the discoverer UE is interested in. The Relay Service Codes are configured in the 5G ProSe Remote UEs interested in related connectivity services.
To support Multi-hop 5G ProSe UE-to-Network Relay discovery the following parameters are added:
- (Optional) Hop-Count: indicates the number of hops that the message is already relayed. It is increased by 1 per hop.
- (Optional) Hop-Limit: an unmodified value that indicates the hop limit of the message. It is set, by the 5G ProSe Remote UE, to a value smaller than the (pre)configured maximum number of hops.
- Path information: an (ordered) list of User Info ID(s) and corresponding L2 ID(s) of Intermediate UE-to-Network Relay(s) that indicates the transmitted path of the message.
- (optional) Accumulated QoS for PC5 link: this reflects the QoS supported over all the PC5 links starting from the PC5 link between the Remote UE and an Intermediate UE-to-Network Relay in the path information for this RSC.
The following parameters are used in the 5G ProSe UE-to-Network Relay Discovery Response message (Model B), where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and Discoveree Info and Relay Service Code are contained in the message:
- Source Layer-2 ID: the 5G ProSe UE-to-Network Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery.
- Destination Layer-2 ID: set to the Source Layer-2 ID of the received 5G ProSe UE-to-Network Relay Discovery Solicitation message.
- Relay Service Code: identifies the connectivity service the 5G ProSe UE-to-Network Relay provides to 5G ProSe Remote UEs that matches the Relay Service Code from the corresponding Discovery Solicitation message.
- Discoveree Info: provides information (i.e. User Info ID) about the discoveree.
To support Multi-hop 5G ProSe UE-to-Network Relay discovery the following parameters are added:
- (Optional) Hop-Count: indicates the number of hops between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay on the path selected by the 5G ProSe UE-to-Network Relay.
- Path information: an (ordered) list of User Info ID(s) and corresponding L2 ID(s) of the discoverer user and the Intermediate UE-to-Network Relay(s) on the path selected by the 5G ProSe UE-to-Network Relay.
- (optional) Accumulated QoS for PC5 link: this reflects the QoS supported over all the PC5 links along the path from Remote UE to the 5G ProSe UE-to-Network Relay for this RSC.
The following parameters may be used in the Relay Discovery Additional Information message (using Model A) based on the procedure defined in clause 6.5.1.3 for 5G ProSe UE-to-Network Relay and clause 6.3.2.5.4 for 5G ProSe Multi-hop UE-to-Network Relay where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and the other parameters are contained in the message:
- Source Layer-2 ID: the 5G ProSe UE-to-Network Relay or the 5G ProSe Intermediate UE-to-Network Relay self-selects a Source Layer-2 ID to send the Relay Discovery Additional Information message.
- Destination Layer-2 ID: the Destination Layer-2 ID to send the Relay Discovery Additional Information message is selected based on the configuration as described in clause 5.1.4.1.
- Relay Service Code: the Relay Service Code associated with the message. The Relay Service Code is used to identify the security parameters needed by the receiving UE to process the discovery message.
Announcer Info: provides information about the announcing user that transmits or forwards the Relay Discovery Additional Information message (i.e. User Info ID of the 5G ProSe UE-to-Network Relay or 5G ProSe Intermediate UE-to-Network Relay). User Info ID of the 5G ProSe Intermediate UE-to-Network Relay is only applicable to the additional parameter announcement procedure over 5G ProSe Multi-hop UE-to-Network Relay specified in clause 6.3.2.5.4.
- Hop-Count: This value reflects the number of PC5 hops for the 5G ProSe Remote UE to reach the network. It is set to 1 by the 5G ProSe UE-to-Network Relay and shall be incremented by 1 every time the Relay Discovery Additional Information message is forwarded by a 5G ProSe Intermediate UE-to-Network Relay.
A 5G ProSe Intermediate UE-to-Network Relay shall only process the Relay Discovery Additional Information message if the Hop-Count is present and the value is less than the (pre-)configured maximum number of hops for the associated RSC and the optional Hop-Limit in the message.
- (optional) Root Relay Info: provides the User Info ID of the 5G ProSe UE-to-Network Relay.
- (optional) Announcer Info of 5G ProSe Intermediate UE-to-Network Relay: identify information (i.e. User Info ID) of the 5G ProSe Intermediate UE-to-Network Relay connected to 5G ProSe UE-to-Network Relay. This parameter is only applicable to the additional parameter announcement procedure over 5G ProSe Multi-hop UE-to-Network Relay specified in clause 6.3.2.5.4.
- (optional) Hop-Limit: this is the hop limit set by the announcing 5G ProSe UE-to-Network Relay to a value smaller than the configured maximum number of hops.
- Additional parameters: the additional parameters for 5G ProSe Layer-3 UE-to-Network Relay (when applicable) are defined in clause 5.8.3.2.
NOTE 1: The UE implementation needs to ensure that when the UE self-selects Source Layer-2 IDs, the self-selected Source Layer-2 IDs are different between 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery) in clause 6.3.2 and 5G ProSe Direct Communication (including 5G ProSe UE-to-Network Relay Communication) in clause 6.4 and are different from any other provisioned Destination Layer-2 IDs as described in clause 5.1 and any other self-selected Source Layer-2 IDs used in a simultaneous 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery) with a different discovery model.
NOTE 2: If a 5G ProSe UE-to-Network Relay and 5G ProSe Remote UE from different PLMNs discover each other, it means that the Relay Service Code is associated with the same connectivity service and the same Relay Service Code is provisioned based on Service Level Agreement among PLMNs.
NOTE 3: The Hop count, Hop-Limit and Path information are used for Multi-hop 5G ProSe UE-to-Network Relay Discovery with Model B. The Multi-hop UE-to-Network Relay Discovery message has no impact on 5G ProSe UE-to-Network Relay or 5G ProSe Remote UE that only supports the single-hop UE-to-Network Relay. Single-hop and Multi-hop UE-to-Network Relays discoveries can be distinguished based on RSC.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.3.2 Identifiers for 5G ProSe Layer-3 UE-to-Network Relay
| For 5G ProSe Layer-3 UE-to-Network relay, a Relay Service Code in the Announcement Message is associated with a set of PDU session parameters (e.g. PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference). The Relay Service Code may also represent if the relay UE can provide secure N3IWF connection.
For 5G ProSe Layer-3 Remote UE discovering 5G ProSe Layer-3 UE-to-Network relay, the Relay Service Code in the Solicitation Message represents the PDU session parameters that a PDU session of the relay should be able to support. The Relay Service Code may also represent if the remote UE requires secure N3IWF connection.
The following additional parameters may be used in the Relay Discovery Additional Information message (using Model A) for 5G ProSe Layer-3 UE-to-Network Relay:
- NCGI: indicates the NCGI of the serving cell of the 5G ProSe Layer-3 UE-to-Network Relay. This parameter may be requested by application running on 5G ProSe Layer-3 Remote UE.
- TAI: indicates the Tracking Area Identity of the serving cell of the 5G ProSe Layer-3 UE-to-Network Relay. This parameter may be used by 5G ProSe Layer-3 Remote UE to select a N3IWF.
- NCGI of 5G ProSe Intermediate UE-to-Network Relay: indicates the NCGI of the serving cell of the 5G ProSe Intermediate UE-to-Network Relay connected to the 5G ProSe UE-to-Network Relay. This parameter may be requested by application running on 5G ProSe Layer-3 Remote UE and is only applicable to the additional parameter announcement procedure over 5G ProSe Multi-hop UE-to-Network Relay specified in clause 6.3.2.5.4.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.3.3 Identifiers for 5G ProSe Layer-2 UE-to-Network Relay
| The following parameters may be used in Announcement message (Model A) or Response message (Model B) in addition to the parameters as specified in clause 5.8.3.1:
- NCGI: indicates the NCGI of the serving cell of the 5G ProSe Layer-2 UE-to-Network Relay for 5G ProSe Layer-2 UE-to-Network Relay (re)selection.
- RRC Container: An RRC container, as defined in TS 38.331 [16], which includes the cell access related information for the serving cell of the 5G ProSe Layer-2 UE-to-Network Relay.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.4 Identifiers for 5G ProSe UE-to-UE Relay Discovery
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.4.1 General
| The 5G ProSe UE-to-UE Relay Discovery message contains two sets of identifiers, a Direct Discovery set and a UE-to-UE Relay Discovery set.
- The Direct Discovery set of identifiers are part of the contents of the 5G ProSe Direct Discovery message as defined in clause 5.8.1. This set of identifiers provides information about the 5G ProSe End UE(s) (e.g. user info (i.e. Application Layer ID)) to be discovered via 5G ProSe UE-to-UE Relay.
- The UE-to-UE Relay Discovery set of identifiers as defined in clause 5.8.4.2 contain information to support the discovery of the 5G ProSe UE-to-UE Relay and extensions of the Direct Discovery.
5G ProSe UE-to-UE Relay shall modify the UE-to-UE Relay Discovery set of identifiers and forward the Direct Discovery set and the UE-to-UE Relay Discovery set of identifiers during the discovery procedures. The Direct Discovery set can be protected using different keys as used to protect the UE-to-UE Relay Discover set according to TS 33.503 [29].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.4.2 Common identifiers for 5G ProSe UE-to-UE Relay Discovery
| The following parameters are used as UE-to-UE Relay Discovery set of identifiers for the 5G ProSe UE-to-UE Relay Discovery Announcement message (Model A), where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message:
- Source Layer-2 ID: the 5G ProSe UE-to-UE Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Announcement message.
- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Announcement message is selected based on the configuration as described in clause 5.1.5.1.
- User Info ID of 5G ProSe UE-to-UE Relay: provides information about the 5G ProSe UE-to-UE Relay.
- Relay Service Code: information to indicate the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs.
The following parameters are used as UE-to-UE Relay Discovery set of identifiers for the 5G ProSe UE-to-UE Relay Discovery Solicitation message (Model B) between discoverer 5G ProSe End UE and 5G ProSe UE-to-UE Relay, where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message:
- Source Layer-2 ID: the discoverer 5G ProSe End UE self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Solicitation message.
- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Solicitation message is selected based on the configuration as described in clause 5.1.5.1.
- Relay Service Code: information about connectivity service that the discoverer 5G ProSe End UE is interested in.
The following parameters are used as UE-to-UE Relay Discovery set of identifiers in the 5G ProSe UE-to-UE Relay Discovery Response message (Model B) between discoverer 5G ProSe End UE and 5G ProSe UE-to-UE Relay, where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message:
- Source Layer-2 ID: the 5G ProSe UE-to-UE Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Response message.
- Destination Layer-2 ID: set to the Source Layer-2 ID of the received 5G ProSe UE-to-UE Relay Discovery Solicitation message.
- User Info ID of 5G ProSe UE-to-UE Relay: provides information about the 5G ProSe UE-to-UE Relay.
- Relay Service Code: identifies the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs that matches the Relay Service Code from the corresponding Discovery Solicitation message.
The following parameters are used as UE-to-UE Relay Discovery set of identifiers for the 5G ProSe UE-to-UE Relay Discovery Solicitation message (Model B) between 5G ProSe UE-to-UE Relay and discoveree 5G ProSe End UE, where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message:
- Source Layer-2 ID: the 5G ProSe UE-to-UE Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Solicitation message.
When a 5G ProSe UE-to-UE Relay self-selects a Source Layer-2 ID for a received 5G ProSe UE-to-UE Relay Discovery Solicitation message, it selects a different Source Layer-2 ID values for each 5G ProSe UE-to-UE Relay Discovery Solicitation message, so that the 5G ProSe UE-to-UE Relay can correlate the 5G ProSe UE-to-UE Relay Discovery Response message with the 5G ProSe UE-to-UE Relay Discovery Solicitation message. The 5G ProSe UE-to-UE Relay can determine the discoverer 5G ProSe End UE that triggered the 5G ProSe UE-to-UE Relay Discovery Solicitation based on the destination Layer-2 ID of the received 5G ProSe UE-to-UE Relay Discovery Response message.
- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Solicitation message is selected based on the configuration as described in clause 5.1.5.1.
- User Info ID of 5G ProSe UE-to-UE Relay: provides information about the 5G ProSe UE-to-UE Relay.
- Relay Service Code: identifies the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs.
The following parameters are used as UE-to-UE Relay Discovery set of identifiers in the 5G ProSe UE-to-UE Relay Discovery Response message (Model B) between 5G ProSe UE-to-UE Relay and discoveree 5G ProSe End UE, where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message:
- Source Layer-2 ID: the discoveree 5G ProSe End UE self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Response message.
- Destination Layer-2 ID: set to the Source Layer-2 ID of the received 5G ProSe UE-to-UE Relay Discovery Solicitation message.
- Relay Service Code: identifies the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs that matches the Relay Service Code from the corresponding Discovery Solicitation message.
NOTE 1: The UE implementation needs to ensure that when the UE self-selects Source Layer-2 IDs, the self-selected Source Layer-2 IDs are different between 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery) in clause 6.3.2 and 5G ProSe Direct Communication (including 5G ProSe UE-to-Network Relay Communication and 5G ProSe UE-to-UE Relay Communication) in clause 6.4, 6.5 and 6.7 and are different from any other provisioned Destination Layer-2 IDs as described in clause 5.1 and any other self-selected Source Layer-2 IDs used in a simultaneous 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery) with a different discovery model.
NOTE 2: If a 5G ProSe UE-to-UE Relay and 5G ProSe End UEs from different PLMNs discover each other, it means that the Relay Service Code is associated with the same connectivity service and the same Relay Service Code is provisioned based on Service Level Agreement among PLMNs.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.5 Identifiers for 5G ProSe UE-to-UE Relay Communication with integrated Discovery
| For the broadcast Direct Communication Request message over the first hop PC5 reference point, the Source Layer-2 ID is self-selected by the source 5G ProSe End UE and the Destination Layer-2 ID is selected based on the configuration as described in clause 5.1.
For the broadcast Direct Communication Request message over the second hop PC5 reference point, the Source Layer-2 ID is self-selected by the 5G ProSe UE-to-UE Relay and the Destination Layer-2 ID is selected based on the configuration as described in clause 5.1.
5G ProSe UE-to-UE Relay may send a unicast Direct Communication Request message to the target 5G ProSe End UE by setting the Destination Layer-2 ID with a received unicast Destination Layer-2 ID of the target 5G ProSe End UE as specified in clause 6.4.3.7. The Source Layer-2 ID is self-selected by the 5G ProSe UE-to-UE Relay.
For unicast Direct Communication Accept message, the Source Layer-2 ID is self-selected by the target 5G ProSe End UE or 5G ProSe UE-to-UE Relay.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.6 Identifiers for 5G ProSe Multi-hop UE-to-UE Relay Discovery
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.6.1 General
| There are two types of discovery mechanisms for the support of 5G ProSe Multi-hop UE-to-UE Relays, i.e. for IP PDU type and for non-IP PDU type (Ethernet or Unstructured). The 5G ProSe End UE and 5G ProSe Multi-hop UE-to-UE Relay choose the discovery mechanism based on the associated indication of the RSC, as defined in clause 5.1.5.1a.
The identifiers used for the two types of discovery mechanisms are specified in clause 5.8.6.2 and clause 5.8.6.3 respectively.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.6.2 Identifiers for 5G ProSe Multi-hop UE-to-UE Relay discovery of IP PDU type
| The Multi-hop UE-to-UE Relay Discovery Announcement message (Model A) is sent by the relay and contains the following information:
- Source Layer-2 ID: the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay self-selects a Source Layer-2 ID. It is used for the transmitting the message at AS layer and included in the AS layer headers only.
- Destination Layer-2 ID: the Destination Layer-2 ID for Multi-hop UE-to-UE Relay Discovery Announcement message (Model A) is selected based on the configuration (associated with the RSC) as defined in clause 5.1.5.1a.
- User Info ID of 5G ProSe Multi-hop UE-to-UE Relay: provides information about the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay.
- Relay Service Code: information to indicate the connectivity service the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay provides to the 5G ProSe End UEs.
The 5G ProSe Multi-hop UE-to-UE Relay Discovery Solicitation message (Model B) is sent by the source 5G ProSe End UE or a 5G ProSe Layer-3 Multi-hop UE-to-UE Relay and includes the following information:
- Source Layer-2 ID: the discoverer 5G ProSe End UE or 5G ProSe Layer-3 Multi-hop UE-to-UE Relay self-selects a Source Layer-2 ID.
- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe Multi-hop UE-to-UE Relay Discovery Solicitation message is selected based on the configuration (associated with the RSC) as defined in clause 5.1.5.1a.
User Info of discoverer: provides information about the sender of the Solicitation message.
- (optional) User Info ID of 5G Prose UE-to-UE Relay: this may be used by the receiver of the message to determine whether to respond to the solicitation. It is only included when the sender wants to find a specific target relay.
- Relay Service Code: information about connectivity service offered by the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay(s).
The 5G ProSe UE-to-UE Relay Discovery Response message (Model B) sent by the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay(s) matching the RSC includes the following:
- Source Layer-2 ID: the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay self-selects a Source Layer-2 ID.
- Destination Layer-2 ID: set to the Source Layer-2 ID of the received 5G ProSe Multi-hop UE-to-UE Relay Discovery Solicitation message.
- User Info of discoverer: the User Info from the received Solicitation message, to ensure the response can be matched at the receiver.
- User Info ID of 5G ProSe UE-to-UE Relay: provides information about the 5G ProSe Multi-hop UE-to-UE Relay sending the Response message.
- Relay Service Code: information about connectivity service offered by the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.8.6.3 Identifiers for 5G ProSe Multi-hop UE-to-UE Relay discovery of non-IP PDU type
| The 5G ProSe UE-to-UE Relay Discovery Announcement message (Model A) is sent by the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay and contains the following parameters for Multi-hop relaying in addition to as described in clause 5.8.4:
- For each user info in the Direct Discovery set:
- Hop count: indicates the number of hops that the message is already relayed. It is increased by 1 per hop.
- (Optional) Hop-Limit: value that indicates the limit of the number of hops of the message.
- Path information: an (ordered) list of User Info ID(s) of Multi-hop UE-to-UE Relay(s) that indicates the transmitted path of the message.
The 5G ProSe UE-to-UE Relay Discovery Solicitation message (Model B) is sent by the source 5G ProSe End UE and includes the following parameters for Multi-hop relaying in addition to as described in clause 5.8.4:
- Hop count: indicates the number of hops that the message is already relayed. It is set to 0 initially by the Discoverer End UE and is increased by 1 per hop.
- (Optional) Hop-Limit: value that indicates the limit of the number of hops of the message. It is set, by the 5G ProSe Remote UE, to a value smaller than or equal to the (pre)configured maximum number of hops.
The 5G ProSe UE-to-UE Relay Discovery Solicitation message (Model B) is sent by the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay(s) matching the RSC and includes the following parameters for Multi-hop relaying in addition to as described in clause 5.8.4:
- Hop count: indicates the number of hops that the message is already relayed. It is increased by 1 per hop.
- (Optional) Hop-Limit: value that indicates the limit of the number of hops of the message. It is set, by the 5G ProSe Remote UE, to a value smaller than or equal to the (pre)configured maximum number of hops.
- Path information: an (ordered) list of User Info ID(s) of Multi-hop UE-to-UE Relay(s) that indicates the transmitted path of the message. Path information also includes source layer-2 ID of discoverer UE.
The 5G ProSe UE-to-UE Relay Discovery Response message (Model B) sent by the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay(s) matching the RSC includes the following parameters for Multi-hop relaying in addition to as described in clause 5.8.4:
- Hop count: indicates the number of hops that the message is already relayed.
- Path information: an (ordered) list of User Info ID(s) of Multi-hop UE-to-UE Relay(s) that indicates the transmitted path of the message. Path information also includes source layer-2 ID of discoverer Prose End UE.
The 5G ProSe UE-to-UE Relay Discovery Response message (Model B) sent by the target 5G ProSe End UE matching the RSC includes the following the following parameters for Multi-hop relaying in addition to as described in clause 5.8.4:
- Hop count: indicates the number of hops that the message is already relayed.
- Path information: an (ordered) list of User Info ID(s) of Multi-hop UE-to-UE Relay(s) that indicates the transmitted path of the message. Path information also includes source layer-2 ID of discoverer Prose End UE.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.9 Support for 5G ProSe for UEs in limited service state
| For UE in limited service state, as defined in TS 23.122 [14], 5G ProSe can be used over PC5 reference point with the following considerations.
UEs that are authorized to use 5G ProSe over PC5 reference point according to clause 5.1 shall be able to use the corresponding services following the principles defined in clause 5.1.2.2 for 5G ProSe Direct Discovery, clause 5.1.3.2 for 5G ProSe Direct Communication, clause 5.1.4.2 for 5G ProSe UE-to-Network Relay and clause 5.1.5.2 for 5G ProSe UE-to-UE Relay when the UE enters in limited service state in 5GS:
- because UE cannot find a suitable cell of the selected PLMN as described in TS 23.122 [14]; or
- as the result of receiving one of the following reject reasons defined in TS 23.122 [14]:
- a "PLMN not allowed" response to a registration request or;
- a "5GS services not allowed" response to a registration request or service request.
A UE in limited service state shall only use the radio resources and procedure available in CM-IDLE mode for ProSe over PC5 reference point, for details see TS 36.300 [11] and TS 38.300 [12].
UEs shall not use 5G ProSe over PC5 reference point using the "operator-managed" radio resources, as specified in clauses 5.1.2.1, 5.1.3.1, 5.1.4.1 and 5.1.5.1, if the UE has entered in limited service state due to all other situations (e.g. no SIM in the MS, an "illegal MS" or "illegal ME" response to a registration request, or an "IMSI unknown in HLR" response to a registration request) defined in TS 23.122 [14], where the UE is unable to obtain normal service from a PLMN. The UEs may use ProSe over PC5 reference point using the "non-operator-managed" radio resources, as specified in clauses 5.1.2.1, 5.1.3.1, 5.1.4.1 and 5.1.5.1, according to the corresponding principles defined in clauses 5.1.2.2, 5.1.3.2, 5.1.4.2 and 5.1.5.2.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.10 PC5 operation in EPS for Public Safety UE
| When the UE is in EPS, the UE shall use the valid ProSe policy and parameters provisioned by the ProSe Function in EPC for ProSe Direct Discovery and Prose Direct Communication. If the UE does not have valid ProSe policy and parameters, the UE shall request the network to provision the ProSe policy and parameters.
The UE that is authorized to perform ProSe Direct Discovery and/or ProSe Direct Communication in EPS can perform the authorized PC5 operation in EPS as specified in TS 23.303 [3].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.11 Communication path selection between PC5 and Uu reference points
| The "communication path selection between PC5 and Uu reference points" refers to the procedure on how a UE selects a communication path between PC5 reference point and Uu reference point before it communicates with another UE. The communication path over PC5 reference point means that the communication with another UE is performed by using 5G ProSe Direct Communication only. The communication path over Uu reference point means that the communication with another UE is performed via the network.
NOTE 1: The communication via 5G ProSe UE-to-Network Relay (Layer-2 or Layer-3) can be considered as the communication path over Uu reference point, as it involves communication via the network.
Path selection policy is provided to the UE to indicate which path(s) is preferred for all or specific ProSe services (i.e. PC5 preferred, Uu preferred or no preference indicated) as specified in clause 5.1.3.1.
The ProSe Application Server can provide a path preference for ProSe Services to UDR as specified in clause 6.2.5 and this may be used by PCF for path selection policy generation and update as specified in clause 6.2.2.
NOTE 2: ProSe Application Server can use QoS Sustainability analytics defined in TS 23.288 [8] to determine the path preference.
The UE may use the provisioned path selection policy to select the appropriate communication path for all or specific ProSe services.
UE operation related to the path selection for ProSe service is as follows:
- The UE evaluates the path selection policy in the policy and parameters for ProSe Direct Communication applicable to the ProSe service and selects the communication path as below:
- If PC5 preferred is indicated, the UE should prefer to use the PC5 for communication path for the ProSe service.
- If Uu preferred is indicated, the UE should prefer to use the Uu for communication path for the ProSe service.
- If no preference is indicated or no path selection policy is provisioned, the UE selects either a Uu or PC5 communication path based on its pre-configuration or implementation for the ProSe service.
NOTE 3: When either PC5 preferred or Uu preferred is indicated, the UE can still select the other non-preferred path, e.g. because the peer UE is not in proximity.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.12 NAS level congestion control for 5G ProSe UE-to-Network Relay
| The 5G ProSe UE-to-Network Relay may be subject to NAS level congestion control, as specified in clause 5.19.7 of TS 23.501 [4].
Both 5G ProSe Layer-2 UE-to-Network Relays and Layer-3 UE-to-Network Relays, when NAS Mobility Management congestion control as specified in clause 5.19.7.2 of TS 23.501 [4] is activated, i.e. the 5G ProSe UE-to-Network Relay receives a Mobility Management back-off timer from the AMF, the 5G ProSe UE-to-Network Relay is not able to serve the 5G ProSe Remote UE after the 5G ProSe UE-to-Network Relay enters CM_IDLE state. If the 5G ProSe UE-to-Network Relay has a Mobility Management back-off timer when it enters CM_IDLE state the 5G ProSe UE-to-Network Relay releases the PC5 connections with its 5G ProSe Remote UEs indicating it is temporarily not available, so the Remote UE can (re)select another 5G ProSe UE-to-Network Relay. The 5G ProSe UE-to-Network Relay does not perform UE-to-Network Relay Discovery as described in clause 6.3.2.3 and does not accept any PC5 connections for relaying until the back-off timer expires if the 5G ProSe UE-to-Network Relay is in CM_IDLE state.
A Remote UE may also be subject to NAS level congestion control as specified in TS 23.501 [4].
NOTE: The form of the temporarily not available indication will be determined by stage 3.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.13 Support for PC5 DRX operations
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.13.1 General
| PC5 DRX operations are supported to enable 5G ProSe-enabled UE power saving for the following functions:
- 5G ProSe Direct Discovery;
- Unicast, groupcast and broadcast mode 5G ProSe Direct Communication;
- 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-Network Relay Communication;
- 5G ProSe UE-to-UE Relay Discovery and 5G ProSe UE-to-UE Relay Communication.
Support for PC5 DRX operations in the AS layer is specified in TS 38.300 [12].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.13.2 PC5 DRX operations for 5G ProSe Direct Discovery, 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery
| For 5G ProSe Direct Discovery, 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery when the UE is "not served by NG-RAN", the UE uses the provisioned default PC5 DRX configuration for PC5 DRX operation as specified in clause 5.1.2.1, clause 5.1.4.1 and clause 5.1.5.1, respectively.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.13.3 PC5 DRX operations for 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay Communication and 5G ProSe UE-to-UE Relay Communication
| The ProSe layer determines the respective ProSe services (i.e. ProSe identifiers) and derives the corresponding PC5 QoS parameters based on either the mapping of ProSe services (i.e. ProSe identifiers) to PC5 QoS parameters, or the ProSe Application Requirements for the ProSe services (i.e. ProSe identifiers) provided by the application layer. For broadcast and groupcast, the ProSe layer also determines the NR Tx Profile based on the mapping of ProSe services (i.e. ProSe identifiers) to NR Tx Profiles as described in clause 5.1.3.1. The ProSe layer passes the PC5 QoS parameters and destination Layer-2 ID to the AS layer as specified in clauses 6.4.1, 6.4.2 and 6.4.3. The ProSe layer also passes the corresponding NR Tx Profile to the AS layer, if the ProSe layer has determined the corresponding NR Tx Profile.
NOTE: For broadcast and groupcast, the AS layer needs PC5 QoS parameters as well to determine the PC5 DRX parameter values for reception operation over PC5 reference point. Therefore, the ProSe layer determines the interested ProSe services (i.e. ProSe identifiers) and derives the PC5 QoS parameters based on its reception needs besides the transmission needs. How to derive the PC5 QoS parameters based on its reception needs (e.g. without establishing the PC5 QoS Flows) depends on UE implementation.
For broadcast or groupcast, the ProSe layer maintains a list of all ProSe services (i.e. ProSe identifiers), i.e. activated ProSe services and/or ProSe services that the UE is interested for reception, for a given destination Layer-2 ID and determines the NR Tx Profile to be mapped for the respective ProSe service based on the configuration described in clause 5.1.3.1. Whenever the list of the ProSe services for a given destination Layer-2 ID changes, the ProSe layer updates the AS layer for the NR Tx Profiles information by providing all the mapped NR Tx Profiles to the AS layer for the given destination Layer-2 ID, e.g. when providing other information such as the destination Layer-2 ID, PC5 QoS parameters.
For broadcast, the mapping from destination Layer-2 ID to NR Tx Profile is configured in the NG-RAN. The NG-RAN may derive the NR Tx Profile from the destination Layer-2 ID to perform the network scheduled operation mode, alignment of Uu DRX and PC5 DRX, etc.
When the PC5 DRX operation is needed, the AS layer determines the PC5 DRX parameter values for 5G ProSe Direct Communication or 5G ProSe UE-to-Network Relay Communication over PC5 reference point, taking into account, e.g. PC5 QoS parameters and/or destination Layer-2 ID provided by the ProSe layer.
For broadcast and groupcast, the UE enables the PC5 DRX based on the NR Tx Profile.
For unicast mode 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay Communication and 5G ProSe UE-to-UE Relay Communication, two UEs may negotiate the PC5 DRX configuration in the AS layer and the PC5 DRX parameter values can be configured per pair of source and destination Layer-2 IDs in the AS layer. For transmitting and receiving Direct Communication Request messages, a default PC5 DRX configuration may be used (see TS 38.300 [12]).
For broadcast and groupcast when the UE is "not served by NG-RAN", the UE uses the provisioned PC5 DRX configuration for PC5 DRX operation as specified in clause 5.1.3.1.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.14 5G ProSe UE-to-UE Relay Communication
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.14.1 5G ProSe Layer-3 UE-to-UE Relay Communication
| The 5G ProSe Layer-3 UE-to-UE Relay shall provide generic function that can relay any IP, Ethernet or Unstructured traffic.
The 5G ProSe Layer-3 UE-to-UE Relay provides the functionality to support connectivity between 5G ProSe Layer-3 End UEs. A 5G ProSe Layer-3 UE-to-UE Relay and 5G ProSe Layer-3 End UEs can be located within NG-RAN coverage or outside of NG-RAN coverage.
The type of traffic supported over PC5 reference point is indicated by the 5G ProSe Layer-3 UE-to-UE Relay e.g. using the corresponding RSC.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.14.2 5G ProSe Layer-2 UE-to-UE Relay Communication
| The 5G ProSe Layer-2 UE-to-UE Relay provides forwarding functionality that can relay any type of traffic over the PC5 link.
The 5G ProSe Layer-2 UE-to-UE Relay provides the functionality to support connectivity between 5G ProSe Layer-2 End UEs. A 5G ProSe Layer-2 UE-to-UE Relay and 5G ProSe Layer-2 End UEs can be located within NG-RAN coverage or outside of NG-RAN coverage.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.14.3 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.14.3.1 General
| Two types of 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communications are supported, i.e. IP based and non-IP based (for Ethernet or Unstructured).
Different RSCs are used for the two types of communications. Different discovery and link management procedures are used.
NOTE: Ethernet or Unstructured traffics between 5G ProSe End UEs may be carried over IP based 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication links by encapsulated them within IP packets. 5G ProSe End UEs can modify the established Layer-2 link to add the corresponding IP flows encapsulating the non-IP traffic as specified in clause 6.7.5.2.1.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.14.3.2 IP based 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication
| The RSC configuration as defined in defined in 5.1.5.1 indicates if IP based 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication is used. The 5G ProSe Multi-hop UE-to-UE Relays supporting the same RSC establish IP based Layer-2 links with each other and form a relay cloud to provide IP connectivity for 5G ProSe End UEs connected to any of the 5G ProSe Multi-hop UE-to-UE Relays.
NOTE 1: If a 5G ProSe Multi-hop UE-to-UE Relay support multiple RSCs, different Layer-2 links will be established, with each associated with a specific RSC. The 5G ProSe UE-to-UE Relay operates as separate logical entities in the separate relay clouds of different RSCs, i.e. no routing table sharing and no traffic forwarding across different relays clouds of different RSCs. The 5G ProSe End UE can have separate IP address, separate routing with different RSCs as well.
The 5G ProSe End UE may establish multiple Layer-2 links with different 5G ProSe UE-to-UE Relays supporting the same RSC, in order to maximize the reachability (e.g. in some cases, different 5G ProSe UE-to-UE Relays may serve different disjointed IP subnets).
Mobile Ad-hoc Network (MANET) based routing protocols are used over the IP connectivity in the relay cloud to provide Multi-hop forwarding functionality between 5G ProSe End UEs. Each of the 5G ProSe Multi-hop UE-to-UE Relay acts as a MANET router. The exact MANET routing protocols to be supported, e.g. Neighborhood Discovery Protocol (NHDP) [36], OLSRv2 [35], are associated with the RSCs based on configuration. The MANET multicast protocol to be used for IP multicast handling, e.g. Simplified Multicast Forwarding (SMF) RFC 6621 [40], is the same for all relay nodes with the same RSC.
Based on configuration associated with the RSC, the 5G ProSe End UE obtains the IP address/prefix in two options:
- Each of the 5G ProSe End UE may be configured with a routable IP address/prefix associated with the RSC. This IP address/prefix does not change when the 5G ProSe End UE changes the connections with 5G ProSe Multi-hop UE-to-UE Relays.
- If the 5G ProSe End UE does not have an IP address/prefix configured for the RSC, it obtains an IP address/prefix from the 5G ProSe UE-to-UE Relay it connects to. In this case, the 5G ProSe End UE may need to change the IP address/prefix when it changes its connection to another 5G ProSe UE-to-UE Relay.
The 5G ProSe End UE obtains the IP address/prefix of the target 5G ProSe End UE via DNS queries (per RSC). 5G ProSe Multi-hop UE-to-UE Relay needs to support DNS operations.
Once the 5G ProSe Multi-hop UE-to-UE Relay becomes aware of the 5G ProSe End UE's IP address/prefix, the 5G ProSe Multi-hop UE-to-UE Relay propagates the related DNS information (i.e. User Info ID and associated IP address/prefix) to all other 5G ProSe Multi-hop UE-to-UE Relays connected to the same MANET (i.e. corresponding to the same RSC) using a dedicated MANET Discovery Info message. The MANET Discovery Info message is diffused throughout the MANET using Multipoint Relay flooding (MPR flooding) as defined in IETF RFC 7181 [35], if available. If MPR flooding is not available, then the MANET Discovery Info message is diffused using simple flooding i.e. by transmitting a copy of the MANET Discovery Info message on all interfaces except the one on which the message has been received.
The MANET Discovery Info message is based on the generalized MANET message format defined in IETF RFC 5444 [37]. The 5G ProSe Multi-hop UE-to-UE Relay initiating the sending of the MANET Discovery Info message controls the propagation depth of the MANET Discovery Info message based on the configured "maximum number of hops per RSC" as specified in 5.1.5.1a or based on the Hop Limit if provided by the target End UE, by using the built-in mechanism defined in IETF RFC 5444 [37].
When a 5G ProSe Multi-hop UE-to-UE Relay detects an End UE is no longer connected (e.g. the PC5 link is released), it may delete the corresponding DNS entry and initiate MANET Discovery Info message to enable other 5G ProSe Multi-hop UE-to-UE Relay(s) to delete the corresponding DNS entry. The propagation depth of the MANET Discovery Info message is controlled based on the configured hop limit.
When MANET protocol determines the route for IP forwarding, layer-2 link QoS and hop counts can be reflected, e.g. with the Link Metrics value as defined in OLSRv2 [35]. The 5G ProSe Multi-hop UE-to-UE Relay can also enforce the configured hop limit based on the link metrics when building the routing tables, e.g. ignore the route that exceeds the threshold derived from hop limit.
If 5G ProSe Multi-hop UE-to-UE Relay has traffic for its own, it can use any IP address it owns for the transmission.
If PC5 groupcast mode for MANET multicast is configured for the RSC, as defined in clause 5.1.5.1a, MANET multicast routing messages (e.g. HELLO, TC) and MANET IP multicast traffic shall be transmitted over the corresponding PC5 groupcast mode bearer associated with the RSC. Upon reception of a MANET multicast routing message or a MANET IP multicast packet and only if the message or packet is from one of the neighbor nodes which has already established a Layer-2 unicast link with the relay, the relay associates the message or the IP multicast packet to the corresponding Layer-2 unicast link and delivers it to the IP layer.
When PC5 groupcast mode is used for MANET multicast routing messages (e.g. HELLO, TC), the Destination Layer-2 ID is derived from the IP multicast address as defined in RFC 5498 [39] and the associated RSC. When PC5 groupcast mode is used for MANET IP multicast packets, the Destination Layer-2 ID is derived from the associated RSC and the IP multicast address of the packets where the combination of RSC and IP Multicast Address is used as the Application Layer Group ID. The 5G ProSe Multi-hop UE-to-UE Relay may make use of the MANET multicast protocol information to determine which PC5 groupcast Layer-2 ID to receive data from.
NOTE 2: Security protection of the PC5 groupcast mode for MANET multicast use is specified in TS 33.503 [29].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.15 Path switching between two UE-to-Network Relays
| If relay reselection has been triggered (see clause 6.5.3), the 5G ProSe Remote UE performs the path switching between two UE-to-Network Relays based on the URSP rules of the 5G ProSe Remote UE traffic handling described in clause 6.5.4, 5G ProSe Policy in clause 5.1.4, or information from application layer (if available) with following considerations:
- The 5G ProSe Remote UE shall first select the target path which has same type with the original path (i.e. 5G ProSe Layer-2 UE-to-Network Relay, 5G ProSe Layer-3 UE-to-Network Relay with N3IWF and 5G ProSe Layer-3 UE-to-Network Relay without N3IWF), by using the RSC associated with the original path.
- If the same type target path is not available, then this 5G ProSe Remote UE re-evaluates the URSP as specified in clause 6.5.4, or 5G ProSe Policy in clause 5.1.4 for the target path selection.
NOTE: If there is the information from the application layer (e.g. provided by an application server), the 5G ProSe Remote UE can use this information to discover the target 5G ProSe UE-to-Network Relay UE. If there are multiple discovered 5G ProSe UE-to-Network Relay UEs, the 5G ProSe Remote UE selects the target 5G ProSe UE-to-Network Relay based on the priority, if any, in the information from the application layer.
The principles from the 5G ProSe Policy in clause 5.1.4 and URSP rules of the 5G ProSe Remote UE traffic handling described in clause 6.5.4 take the higher priority than the information from the application layer.
The path switching procedures between two indirect network communication paths are as described in clause 6.5.5.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.16 Communication path switching between PC5 and Uu reference points
| The "communication path switching between PC5 and Uu reference points" refers to the procedure on how a UE switches between Uu communication path and direct PC5 communication path when it is communicating with another UE as illustrated in Figure 5.16-1. The direct communication path over PC5 reference point means that the communication with another UE is performed by using 5G ProSe Direct Communication only. The communication path over Uu reference point means that the communication with another UE is performed via the network.
Figure 5.16-1: Example scenario of communication path switching between PC5 and Uu reference points (i.e. switching between Figure a and Figure b)
Communication path switching between PC5 and Uu reference points is performed at ProSe service level, e.g. some of ProSe services of PC5 unicast link or PDU Session, all ProSe services of PC5 unicast link or PDU Session.
The UE takes the path selection policy into account to determine whether and for which ProSe service(s) to switch the communication path. UE operation related to the path switch for ProSe service is as follows:
- The UE evaluates the path selection policy in the policy and parameters for ProSe Direct Communication applicable to the ProSe service and switches the communication path as below:
- If the Uu path is used and PC5 preferred is indicated, the UE should prefer to switch to the PC5 communication path for the ProSe service.
- If the PC5 path is used and Uu preferred is indicated, the UE should prefer to switch to the Uu communication path for the ProSe service.
- If no preference is indicated or no path selection policy is provisioned, the UE switches between Uu and PC5 communication path based on its pre-configuration or implementation for the ProSe service.
NOTE 1: When either PC5 preferred or Uu preferred is indicated, the UE can still switch to the other non-preferred path, e.g. signal strength of any path below a certain configured signal strength threshold.
The UE may decide to perform path switching from Uu path to PC5 path, e.g. because the peer UE is in proximity or for offloading some traffic from the network. The UE may decide to perform path switching from PC5 path to Uu path, e.g. when the PC5 signal strength of the unicast link with the peer UE becomes weak.
At path switching, the same traffic type between for PDU Session and for PC5 unicast link is maintained, i.e. IP type, Ethernet type and Unstructured type.
For communication path switching from PC5 to Uu reference point, the Uu QoS parameters of each UE are decided based on PC5 QoS parameters and negotiated via the existing PC5 connection between two UEs. Each UE may perform the UE requested PDU Session Modification as defined in TS 23.502 [5] clause 4.3.3 to request the Uu QoS parameters. For IP type traffic, the IP addresses/prefixes of the peer UEs over the Uu reference point can be shared via the existing PC5 connection between the UEs by using application layer signalling to assist them to establish communication with each other via the communication path over the Uu reference point.
When both Uu path and PC5 path are available, a make-before-break mechanism is used when switching between PC5 path and Uu path. That is, the UEs first prepare the target path to communicate with each other and then perform the path switching and communicate over the target path and after this the former path may be released.
NOTE 2: It is not targeted to support session continuity (e.g. IP address preservation) during path switching between PC5 and Uu reference points.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.17 Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.17.1 General
| Multi-path communication uses one direct network communication path and one indirect network communication path with UE-to-Network Relay as illustrated in Figure 5.17.1-1, where path #1 shows the direct communication path via Uu and path #2 is shows the indirect communication path via 5G ProSe UE-to-Network Relay.
Figure 5.17.1-1: Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay
The indirect communication path may be via a 5G ProSe Layer-2 UE-to-Network Relay, or via a 5G ProSe Layer-3 UE-to-Network Relay with or without N3IWF.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.17.2 Multi-path communication via direct Uu path and via 5G ProSe Layer-3 UE-to-Network Relay
| A 5G ProSe Layer-3 Remote UE may access the network via a 5G ProSe Layer-3 UE-to-Network Relay with or without N3IWF.
When a 5G ProSe Layer-3 Remote UE accesses the network via a 5G ProSe Layer-3 UE-to-Network Relay without N3IWF, the multi-path communication via direct Uu path and via the UE-to-Network Relay may be applied to the application traffic.
When a 5G ProSe Layer-3 Remote UE accesses the network via a 5G ProSe Layer-3 UE-to-Network Relay with N3IWF, the Layer-3 Remote UE connection via Layer-3 UE-to-Network Relay with N3IWF is considered as "untrusted non-3GPP access to 5GC via N3IWF", therefore the multi-path communication can be achieved using MA PDU Session in ATSSS features specified in clause 5.32 of TS 23.501 [4].
NOTE: MA PDU Session requires ATSSS Information in SM subscription data as specified in TS 23.502 [5].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.18 Support of Public Warning Notification Relaying
| As specified in TS 22.268 [33], if UE that is authorised to act as 5G ProSe UE-to-Network Relay receives Public Warning Notification from the network and the UE is configured to perform Public Warning relaying, it shall handle the Public Warning message acting in the role of 5G ProSe UE-to-Network Relay.
The 5G ProSe UE-to-Network Relay broadcasts the warning message i.e. SIB 6/7/8 received from the network to the 5G ProSe Remote UE(s) by using Broadcast mode of 5G ProSe direct communication as specified in clause 5.3.2. The 5G ProSe UE-to-Network Relay uses a configured Destination Layer-2 ID(s) as specified in clause 5.1.4.1 when broadcasting the warning message and the 5G ProSe Remote UE receives warning messages broadcasted over PC5 reference point by using a configured Destination Layer-2 ID(s) as specified in clause 5.1.4.1. The PC5 QoS parameters as specified in clause 5.1.4.1 are used to broadcast and receive the warning message for the 5G ProSe UE-to-Network Relay and the 5G ProSe Remote UE, respectively.
If the UE that is authorized to act as a 5G ProSe Intermediate UE-to-Network Relay receives the broadcasted warning message by using a configured Destination Layer-2 ID(s) as specified in clause 5.1.4.1a and the UE is configured to perform Public Warning relaying, it shall broadcast the message and increment the Hop-Count value, or add a Hop-Count set to 2 into the message if it is not present. The 5G ProSe Intermediate UE-to-Network Relay shall not broadcast the warning message if the Hop-Count value is larger than the stored Hop-Count in its discovery entry. The 5G ProSe Intermediate UE-to-Network Relay uses a configured Destination Layer-2 ID(s) as specified in clause 5.1.4.1a when broadcasting the warning message and the 5G ProSe Remote UE receives warning messages broadcasted over PC5 reference point by using a configured Destination Layer-2 ID(s) as specified in clause 5.1.4.1a. The PC5 QoS parameters as specified in clause 5.1.4.1 are used to broadcast and receive the warning message for the 5G ProSe Intermediate UE-to-Network Relay and the 5G ProSe Remote UE, respectively.
A 5G ProSe Remote UE can receive the broadcasted warning message without establishing a connection to the 5G ProSe UE-to-Network Relay or 5G ProSe Intermediate UE-to-Network Relay.
The 5G ProSe UE-to-Network Relay performs the duplication detection function as specified in TS 23.041 [32] to suppress the received duplicated warning messages over Uu. The 5G ProSe Intermediate UE-to-Network Relay and 5G ProSe UE-to-Network Remote UE performs the duplication detection function as specified in TS 23.041 [32] to detect duplicated warning messages received over PC5 and/or Uu.
NOTE: The duplication detection function in the 5G ProSe UE-to-Network Relay and 5G ProSe Intermediate UE-to-Network Relay avoids broadcasting the duplicated warning message over PC5.
If the 5G ProSe Layer-2 UE-to-Network Relay does not have Destination Layer-2 ID to broadcast Public Warning messages, the 5G ProSe Layer-2 UE-to-Network Relay forwards the PWS SIBs (i.e. SIB 6/7/8) to a connected 5G ProSe Layer-2 Remote UE over the unicast link as specified in TS 38.300 [12].
The Public Warning System architecture for 5G System is specified in TS 23.041 [32].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6 Functional description and information flows
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1 Control and user plane stacks
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1 Control Plane
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.1 General
| The control plane stack consists of protocols for controlling:
- 5G ProSe Direct Discovery, specified in clause 6.1.1.2.1, clause 6.1.1.3, clause 6.1.1.4, clause 6.1.1.5 and clause 6.1.1.6;
- 5G ProSe Direct Communication, specified in clause 6.1.1.2.2;
- 5G ProSe UE-to-Network Relay, specified in clause 6.1.1.7;
- 5G ProSe UE-to-UE Relay, specified in clause 6.1.1.8.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.2 UE - UE
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.2.1 Discovery plane PC5 interface
| The PC5 communication channel is used to carry the discovery messages over PC5 which are differentiated from other PC5 messages by the AS layer.
Figure 6.1.1.2.1-1 depicts a discovery plane for NR PC5 reference point.
Legend:
- PC5-D: The PDCP/RLC/MAC/PHY functionality is specified in TS 38.300 [12].
- The "ProSe Discovery protocol" is used for handling ProSe Direct Discovery as specified in clause 6.3.2.
Figure 6.1.1.2.1-1: Discovery Plane PC5 Interface
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.2.2 PC5 Signalling Protocol
| The PC5 Signalling Protocol stack specified in clause 6.1.2 of TS 23.287 [2] is used. The protocol used for the control plane signalling over the PC5 reference point for the secure layer-2 link is specified in clauses 6.4.3, 6.5.1 and 6.5.2.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.3 UE - 5G DDNMF
|
Legend:
- ProSe Control Signalling between UE and 5G DDNMF is carried over the user plane and using the PC3a protocol as specified in TS 24.554 [23].
NOTE 1: PC3a may be realized with one or more protocols.
NOTE 2: If 5G DDNMF is integrated with ProSe Application Server, 5G DDNMF provides PC3a interface towards UE and ProSe Application Server provides PC1 interface towards UE.
Figure 6.1.1.3-1 Control Plane for PC3a Interface
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.4 5G DDNMF – UDM
| 5G DDNMF uses Nudm interface defined in TS 23.501 [4] to obtain the UE's subscription information for the authorization of the 5G ProSe Direct Discovery requests.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.5 5G DDNMF – 5G DDNMF
| The control plane protocol(s) between 5G DDNMFs are defined in TS 29.500 [30].
The 5G DDNMFs uses N5g-ddnmf 5G DDNMF services defined in clause 7.1 to access the services provided by the other 5G DDNMF(s). The 5G DDNMF in HPLMN uses NRF to discover the 5G DDNMFs in VPLMN and Local PLMNs.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.6 5G DDNMF – ProSe Application Server
| The 5G System architecture supports the service based Npc2 interface between 5G DDNMF and ProSe Application Server and optionally supports PC2 interface between 5G DDNMF and ProSe Application Server, to enable Proximity Services. See TS 23.501 [4] and TS 23.303 [3].
NOTE: PC2 support between 5G DDNMF and ProSe Application Server is for backwards compatibility for early deployments using Diameter. PC2 interface is used for 5G ProSe Direct Discovery authorization.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.7 5G ProSe UE-to-Network Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.7.1 5G ProSe Layer-3 UE-to-Network Relay
| The UE-UE protocol stacks for discovery and PC5 link management as defined in clause 6.1.1.2 apply to 5G ProSe Remote UE, 5G ProSe Intermediate UE-to-Network Relay and 5G ProSe Layer-3 UE-to-Network Relay. There could be zero, one or multiple 5G ProSe Intermediate UE-to-Network Relay(s) between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay. If there is no 5G ProSe Intermediate UE-to-Network Relay, the IP connection and the PC5 link is between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay.
Additionally, when N3IWF is supported by the 5G ProSe Layer-3 UE-to-Network Relay, the following control plane protocol stack apply.
Legend:
- NAS, EAP-5G and IKEv2 between the Remote UE and the N3IWF are defined in clause 8.2.4 of TS 23.501 [4].
Figure 6.1.1.7.1-1: Control plane protocol stacks between 5G ProSe Layer-3 Remote UE and N3IWF over 5G ProSe Layer-3 UE-to-Network Relay before the signalling IPSec SA is established
Legend:
- NAS, TCP and IPsec between the Remote UE and the N3IWF are defined in TS 23.501 [4] clause 8.2.4.
Figure 6.1.1.7.1-2: Control plane protocol stacks between 5G ProSe Layer-3 Remote UE and N3IWF over 5G ProSe Layer-3 UE-to-Network Relay after the signalling IPSec SA is established
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.7.2 5G ProSe Layer-2 UE-to-Network Relay
| The UE-UE protocol stacks for discovery and PC5 signalling defined in clause 6.1.1.2 apply to 5G ProSe Remote UE and 5G ProSe Layer-2 UE-to-Network Relay.
Figure 6.1.1.7.2-1 illustrates the protocol stack of the NAS connection for the 5G ProSe Layer-2 Remote UE for NAS-MM and NAS-SM. The NAS messages are transparently transferred between the 5G ProSe Layer-2 Remote UE and NG-RAN over the 5G ProSe Layer-2 UE-to-Network Relay using:
- PDCP end-to-end connection between the 5G ProSe Layer-2 Remote UE and NG-RAN, where the role of the 5G ProSe Layer-2 UE-to-Network Relay is to relay the PDUs over the signalling radio bear without any modifications and using the functionality of the adaptation layer as specified in TS 38.300 [12].
- Connection between NG-RAN and AMF over N2.
- Connection between AMF and SMF over N11.
Figure 6.1.1.7.2-1: End-to-End Control Plane for a Remote UE using Layer-2 UE-to-Network Relay
The control plane protocol stack used by the 5G ProSe Layer-2 UE-to-Network Relay is defined in clause 8.2.2 of TS 23.501 [4].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.8 5G ProSe UE-to-UE Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.8.1 5G ProSe Layer-2 UE-to-UE Relay
| Figure 6.1.1.8.1-1 illustrates control plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay. Security is established end-to-end between 5G ProSe End UEs as shown by the PDCP layer terminating in the 5G ProSe End UEs.
Figure 6.1.1.8.1-1: End-to-End Control Plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay
NOTE 1: Only the End-to-End control plane protocol stack is shown. The control plane protocol stack of the per-hop PC5 unicast link between 5G ProSe End UEs and 5G ProSe Layer-2 UE-to-UE Relay reuses the PC5-S protocol stack defined in clause 6.1.1.2.
NOTE 2: PC5-S messages over per-hop PC5 unicast links and over End-to-End PC5 unicast links are supported. A End-to-End PC5-S message is the message transferred between the 5G ProSe End UEs and a direct PC5-S message is the message transferred between a 5G ProSe End UE and a 5G ProSe Layer-2 UE-to-UE Relay.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.1.1.8.2 5G ProSe Layer-3 UE-to-UE Relay
| The control plane protocol stack of the PC5 unicast link between 5G ProSe End UEs and 5G ProSe Layer-3 UE-to-UE Relay reuses the PC5-S protocol stack defined in clause 6.1.1.2.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.