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

Content for  TS 23.289  Word version:  19.3.0

Top   Top   Up   Prev   Next
0…   4…   4.7…   4.7.4…   4.8…   5…   5.4…   6…   6.3…   6.3.2…   7…   7.2.4…   7.3…   7.3.3…   7.3.3.2…   7.3.3.4…   7.3.3.5…   7.3.3.7…   7.3.3.8…   7.3.3.9…   7.3.3.10…   7.3.3.11…   7.3.3.12…   7.3.3.13…   7.4…   7.5…   7.6…   A… 
4.8 Use of 5G ProSe UE-to-network relay  4.8.1 General  4.8.2 5G ProSe UE-to-network relay service requirements  4.9 EPS interworking  4.9.1 General  4.9.2 Requirements  4.10   4.11 Support of the 5GS congestion information exposure using L4S 
...

 

4.8  Use of 5G ProSe UE-to-network relay |R18|  p. 23

4.8.1  General  p. 23

The MC service shall support the capabilities for 5G ProSe UE-to-network relay. For this matter, 5G ProSe Layer-2 and 5G ProSe Layer-3 UE-to-network relaying techniques can be utilized, as described in TS 23.304. The 5G ProSe Layer-3 UE-to-Network relaying technique may be done with or without the support of N3IWF, as described in TS 23.304.
A 5G ProSe UE-to-network relay supporting MC service UE provides means of connectivity and relaying of MC traffic to remote MC service UE(s). For this matter, the 5G ProSe UE-to-network Relay Discovery service allows the MC service remote UE to discover a potential UE-to-network relay UE supporting MC service in its proximity as described in TS 23.304. Upon its discovery, the 5G ProSe Direct UE-to-network Relay Communication functionality is utilized to achieve communication to provide the MC service remote UE access to 5GS, and relay MC traffic via the UE-to-network relay UE over the NR PC5 reference point.
Up

4.8.2  5G ProSe UE-to-network relay service requirements  p. 24

In order to enable 5G ProSe UE-to-network relaying capabilities - whether based on Layer-3 or Layer-2 UE-to-network relaying techniques, the MC system provides the appropriate parameters and configurations to the MC service UE(s).
As defined in TS 23.304, among these parameters are: Relay Service Code(s) (RSCs) which can be associated to a certain MC service group, User Info, ProSe Layer-2 Group ID and ProSe Group IP multicast address. Moreover, the MC service group ID is resolved to the ProSe Layer-2 Group ID and ProSe Group IP multicast address, which are utilized within the 5G ProSe Relay Discovery and 5G ProSe Direct Communication procedures, as described in TS 23.304. Furthermore, the RSCs are utilized to restrict the necessary UE-to-network relay service and related procedures within members of a certain MC service group.
Moreover, in case of 5G ProSe Layer-3 UE-to-network relay with the support of N3IWF, the UE-to-network relay is provisioned with policies and parameters, among others suitable RSC(s), in order to support N3IWF access, as defined in TS 23.304.
Up

4.9  EPS interworking |R18|  p. 24

4.9.1  General  p. 24

Network deployments of MC services over 5GS may support interworking with EPS. EPS interworking aspects in 5G systems are specified in TS 23.501, TS 23.502, and TS 23.503.

4.9.2  Requirements  p. 24

For MC services over a 5G system with EPS interworking, inter-system mobility between 5GC and EPC/E-UTRAN of MC service UEs shall be supported by the network based on the capabilities and procedures defined in TS 23.501, TS 23.502, and TS 23.503.
For the case that seamless session continuity is required for MC services, e.g. for MCPTT services, EPS interworking with N26 (interface between AMF in 5GC and MME in EPC) is required for inter-system change.
The MC system should be able to subscribe/unsubscribe to notification capabilities of specific events from the network related to EPS interworking. Thereby, the MC system can identify whether an MC service UE is registered on 5GS or EPS.
Up

4.10  |R19|

4.10.1  General  p. 24

The MC service shall support the capabilities for 5G ProSe UE-to-UE single hop relay. For this matter, 5G ProSe Layer-2 and 5G ProSe Layer-3 UE-to-UE relaying techniques can be utilized, as described in TS 23.304.
A 5G ProSe UE-to-UE relay supporting MC service UE provides means of connectivity and relaying of MC traffic from a MC service UE to another MC service UE(s) via a MC UE Relay. For this matter, the 5G ProSe UE-to-UE Relay Discovery service allows the MC service remote UE to discover a potential UE-to-UE relay supporting MC service in its proximity as described in TS 23.304. Upon its discovery, the 5G ProSe Direct UE-to-UE Relay Communication functionality is utilized to achieve communication to provide the MC service between MC UEs, relaying MC traffic via the UE-to-UE relay UE over the NR PC5 reference point.
Up

4.10.2  5G ProSe UE-to-UE relay service requirements  p. 25

In order to enable 5G ProSe UE-to-UE relaying capabilities - whether based on Layer-3 or Layer-2 UE-to-UE relaying techniques, the MC system provides the appropriate parameters and configurations to the MC service UE(s).
As defined in TS 23.304, among these parameters are: Relay Service Code(s) (RSCs) which can be associated to a certain MC service group, User Info, ProSe Layer-2 Group ID and ProSe Group IP multicast address. Moreover, the MC service group ID is resolved to the ProSe Layer-2 Group ID and ProSe Group IP multicast address, which are utilized within the 5G ProSe Relay Discovery and 5G ProSe Direct Communication procedures, as described in TS 23.304. Furthermore, the RSCs are utilized to restrict the necessary UE-to-UE relay service and related procedures within members of a certain MC service group.
Up

4.11  Support of the 5GS congestion information exposure using L4S |R19|  p. 25

Based on the request from the MC system, the 5G system can expose network congestion information on the media path between the MC service server and MC service UE to enable reacting accordingly, e.g., adjust the application layer bit rate at the media sender side.
The 5G System can support Explicit Congestion Notification (ECN) marking for Low Latency, Low Loss and Scalable Throughput (L4S) support as defined in clause 5.37.3 of TS 23.501. When supported and enabled, the 5G System is applying ECN marking for L4S on a per QoS flow basis in the uplink and/or downlink direction and may be used for GBR and non-GBR QoS flows.
To support this feature on a service data flow, the MC service client and MC service server are capable of supporting the L4S handling including e.g., parsing the L4S ECN mark in the IP header, reporting the L4S feedback about downlink and/or uplink direction. The MC service server enables this feature by initiating the request for L4S marking towards the network (either directly towards PCF or indirectly via NEF).
Related procedures are specified in clause 7.7.
Up

Up   Top   ToC