hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.7.3 Procedures
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.7.3.1 One-from-server video pull enhancement
| Procedure in figure 7.7.3.1-1 is the common signalling control plane procedures for the MCVideo communication enhancement with ECN marking for L4S capability.
Pre-condition:
1. The MCVideo server has already obtained the L4S handling capability from the MCVideo client 1.
Figure 7.7.3.1-1: One-from-server video pull enhancement with ECN marking for L4S capability
1-5. Same as step 1 to step 5 in clause 7.3.2.4.2 of 3GPP TS 23.281 [4].
6a. The MCVideo server may determine to utilize the 5GS L4S capabilities to obtain the congestion information to improve the downlink stream transmission control. The MCVideo server interacts with the 5GS to request the ECN marking for L4S as specified in 3GPP TS 23.502 [10].
6b. The 5GS starts to perform the ECN marking as specified in 3GPP TS 23.501 [7]. The MCVideo UE receives the DL media stream with ECN marking in the IP header which reflects the DL network congestion status.
6c. The MCVideo client, based on the DL ECN marking in the IP header, generates and sends the L4S feedback report towards the MCVideo server as described in IETF RFC 9330 [24].
7. The MCVideo server, based on step 6b performs the DL media stream control, e.g., adjust the DL media packet sending rate.
NOTE: How the DL media packet sending rate is adapted is outside the scope of the present document.
8.-9. Step 8 and step 9 are same as step 6 and step 7 of clause 7.3.2.4.2 of 3GPP TS 23.281 [4], respectively.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.7.3.2 One-to-server- video push enhancement
| Figure 7.7.3.2-1 describes a common signalling control plane procedure for MC video client initiating the establishment of video push where the push feature is enhanced via ECN marking for L4S capability.
Precondition:
- The MCVideo server has already obtained the L4S handling capability from the MCVideo client 1.
Figure 7.7.3.2-1: One-to-server video push with ECN marking for L4S capability
1.-5. Same as steps 1 to step 5 of 3GPP TS 23.281 [4] clause 7.4.2.4.2.
6. The MCVideo server may determine to utilize the 5GS L4S capability to obtain the congestion information to improve the UL stream transmission control. For this purpose, the MCVideo server interacts with the 5GS to request the ECN marking for L4S as specified in 3GPP TS 23.502 [10].
7. The 5GS starts to perform the ECN marking as specified in 3GPP TS 23.501 [7]. The 5GS receives the UL media stream with ECN marking in the IP header which reflects the UL network congestion status. The 5GS exposes the congestion information to the MCVideo server as specified in 3GPP TS 23.501 [7].
8. Based on the UL ECN marking in the IP header, the MCVideo server generates and sends the L4S feedback report towards the MCVideo client as described in IETF RFC 9330 [24].
9. Based on the L4S feedback report, the MCVideo performs UL stream control, e.g., adjust the UL media packet sending rate.
NOTE: How the UL media packet sending rate is adapted is outside the scope of the present document.
10.-11. Step 10 and step 11 are same as step 6 and step 7 f clause 7.4.7.4.2 of 3GPP TS 23.281 [4], respectively.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.8 5MBS support for MC clients hosted on non-3GPP devices
| The 5MBS support for MC clients hosted on non-3GPP devices are supported by the procedures and information flows as defined in clause 11.5.3 of 3GPP TS 23.280 [3] with following clarifications and changes:
- the "MBMS" is the "5MBS", the "MBMS bearer" is the "MBS session".
- the "TMGI(s)" IE should be "MBS session ID", and its corresponding description should be "identifier(s) of the MBS session(s)";
- the message "MC GW MBMS bearer announcement" is renamed as "MC GW MBS session announcement” and shall take the IEs from table 7.3.2.1 without the "eMBMS bearer information" IE.
- the message "MC GW MBMS listening status report" is renamed as "MC GW MBS listening status report” and shall take the IEs from table 7.3.2.10.
- the message "MC GW MapGroupToBearer request" is renamed as "MC GW MapGroupToSessionStream request" shall take the IEs from table 7.3.2.3.
- the message "MC GW MapGroupToBearer response" is renamed as "MC GW MapGroupToSessionStream response" shall reuse the IEs from table 11.5.3.2.4 in 3GPP TS 23.280 [3].
- the message "MC GW UnMapGroupToBearer request" is renamed as "MC GW UnMapGroupToSessionStream request" shall take the IEs from table 7.3.2.7.
- the message "MC GW UnMapGroupToBearer response" is renamed as "MC GW UnMapGroupToSessionStream response" shall reuse the IEs from table 11.5.3.2.8 in 3GPP TS 23.280 [3].
- the message "MC GW MBMS bearer suspension indication" is renamed as "MC GW MBS session suspension indication" shall reuse the IEs from table 11.5.3.2.6 in 3GPP TS 23.280 [3].
When multicast MBS session is used, the MC gateway UE joins the multicast MBS session based on the MBS session mode indicationg multicast MBS session received in MC GW MBS session announcement. If the UE session join notification indication is included in the MC GW MBS session announcement, the MC gateway UE sends the MC GW UE session join notification message to the MC client. This message shall take the IEs from table 7.3.2.2 without the MC service ID IE. Further the MC client sends the MBS UE session join notification to the MC service server as described in clause 7.3.2.2.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.9 Reporting the quality of MC service client connection
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.9.1 General
| This clause describes the procedure to inform authorised MC service user(s) about the connection quality of a target MC service client. As a result, the target MC service client obtains the signal strength measurement, and any necessary information associated with the current connection utilized by the MC service UE and report it back to the MC service server, where the latter provide it to the requested authorised MC service client.
In case the target MC service UE is directly connected to the 5GS over the Uu interface, the MC service client obtains the Uu signal strength measurements from the lower layers of the MC service UE.
NOTE 1: The interaction between the MC service client and the lower layers of the MC service UE are out of scope of 3GPP.
NOTE 2: The reported signal strength measurements are RSRP and RSRQ as indicated in 3GPP TS 38.300 [28].
In case the target MC service UE is remote and is indirectly connected to the 5GS via an MC service capable 5G ProSe (multihop) UE-to-Network relay over the PC5 interface, the MC service client obtains from the ProSe lower layer of the remote MC service UE the sidelink signal strength measurements along with the indirect path information which comprises of the MC capable 5G ProSe (multihop) UE-to-Network relay and MC capable 5G ProSe intermediate UE-to-Network relay(s) if available. Upon receiving the information, the MC service server requests MC service client(s) comprising the indirect path information to report the quality of their own connection to the MC service server to be provided to the requesting authorised MC service client.
NOTE 3: The interaction between the MC service client and the ProSe lower layers of the MC service UE are out of scope of 3GPP.
NOTE 4: The reported sidelink signal strength measurements are SL-RSRP and SD-RSRP as defined in 3GPP TS 38.300 [28].
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.9.2 Information flows
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.9.2.1 Quality of MC service client connection request
| Table 7.9.2.1-1 describes the information flow of the quality of MC service client connection request sent from the MC service client to the MC service server, and from the MC service server to the MC service client.
Table 7.9.2.1-1: Quality of MC service client connection request
Information element
Status
Description
MC service ID
M
The MC service identity of the MC service client
MC service ID(s) (NOTE)
O
The MC service identity of the MC service client(s) to report the quality of connection
NOTE: This information element is mandatory if the request is sent from an authorised MC service client.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.9.2.2 Quality of MC service client connection response
| Table 7.9.2.2-1 describes the information flow of the quality of MC service client connection response sent from the MC service client to the MC service server.
Table 7.9.2.2-1: Quality of MC service client connection response
Information element
Status
Description
MC service ID
M
The MC service identity of the MC service client sending the response
Sidelink signal strength measurements
O
The measurements of the sidelink signal strength towards the immediate (adjacent) relay the MC service client has obtained from ProSe lower layers. The immediate (adjacent) relay is either the MC service capable 5G ProSe UE-to-Network relay, or the MC service capable 5G ProSe intermediate UE-to-Network relay if available
Uu signal strength measurements
O
The Uu signal strength measurements obtained from the MC service if available
Measurement time stamp
O
The time stamp associated with the reported measurements.
Indirect path information (NOTE 1)
O
(An ordered list of) the User Info ID(s) of the MC service client(s) associated with the current indirect connection, as defined in 3GPP TS 23.304 [17].
Number of hops
O
The current number of hops towards the MC service capable 5G ProSe multihop UE-to-Network relay forming the current indirect path in case of multihop connectivity
The maximum number of hops
O
The maximum number of hops supported by the MC service capable 5G ProSe multihop UE-to-Network relay
Result (NOTE 2)
M
It indicates the success or failure of the request.
NOTE 1: This information element is mandatory for reporting quality of connection of remote MC service UE.
NOTE 2: This information element is mandatory when the MC service server sends the quality of MC service client connection response to an authorised MC service client.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.9.3 Provide quality of direct connection of an MC service UE
| Figure 7.9.3-1 illustrates the procedure to provide an authorised MC service client the quality of direct connection of a certain MC service UE.
Figure 7.9.3-1: Providing the quality of MC service client connection
1. The MC service user 1 would like to know the direct connection quality of the MC service UE 2. Therefore, the MC service client 1 sends a quality of MC service client connection request including the MC service ID of MC service client 2.
2. The MC service server performs an authorisation check. If the MC service client 1 is not authorised to request the connection quality of MC service client 2, the MC service server provides the MC service client 1 a failure response in step 7 and the procedure terminates.
3. If the authorisation check is successful, the MC service server sends a quality of MC service client connection request to the MC service client 2 at the MC service UE 2.
4. The MC service client 2 obtains the signal strength measurements from the lower layers of MC service UE 2.
5. MC service client 2 sends the MC service server a quality of MC service client connection response, which includes the obtained measurements from the previous step.
6. The MC service server stores the signal strength measurements that corresponds to the direct connection of the MC service UE 2.
7. The MC service server sends the MC service client1 a quality of MC service client connection response including the obtained measurements that corresponds to the direct connection of MC service client 2.
NOTE: Aspects related to re-sending the quality of MC service client connection request/response to update the signal strength measurements is left to implementation, e.g., after a certain period of time.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.9.4 Provide quality of indirect connection of a remote MC service UE
| Figure 7.9.4-1 illustrates the procedure to provide an authorised MC service client the quality of the indirect connection of a certain remote MC service UE.
Precondition:
- MC service UE 2 is connected to the 5GS via an MC capable 5G ProSe (multihop) UE-to-Network relay.
Figure 7.9.4-1: Providing the quality of a remote MC service client connection
1. The MC service user 1 would like to know the connection quality of the indirect path of the MC service UE 2. Therefore, the MC service client 1 sends a quality of MC service client connection request.
2. The MC service server performs an authorisation check. If the MC service client 1 is not authorised to request the connection quality of MC service client 2, the MC service server provides the MC service client 1 a failure response in step 11 and the procedure terminates.
3. If the authorisation check is successful, the MC service server sends a quality of MC service client connection request to the MC service client 2 at the MC service UE 2.
4. The MC service client 2 obtains the necessary information from the remote MC service UE 2. The information is the sidelink signal strength towards the MC service capable 5G ProSe UE-to-Network relay and the indirect path information associated with the remote MC service UE 2. In case of multihop connectivity, the MC service client 2 obtains the sidelink signal strength towards the immediate hop MC service capable 5G ProSe intermediate UE-to-Network relay, and the indirect path information associated with the remote MC service UE 2. The indirect path information is the (ordered list of) User Info ID the MC service capable 5G ProSe (multihop) UE-to-Network relay and the User Info ID(s) of the MCservice capable 5G ProSe intermediate UE-to-Network relay(s) if available, as described in 3GPP TS23.304 [17]. Furthermore, in case of multihop connectivity, the MC service client 2 may provide the number of hops associated with the indirect path information and the maximum number of hops associated with the MC service capable 5G ProSe multihop UE-to-Network relay under consideration.
5. MC service client 2 provides the MC service server the quality of MC service client response, which includes the obtained information in the previous step.
6. The MC service server stores the information received in the previous step. Furthermore, the MC service server retrieves the (ordered list of) MC service ID(s) that corresponds to the (list of) User Info ID(s) of the indirect path.
7. The MC service server sends the MC service client at the MC service capable 5G ProSe (multihop) UE-to-Network relay a quality of MC service client connection request. In case of multihop connectivity, the MC service server additionally sends the MC service capable 5G ProSe intermediate UE-to-Network relay(s) a quality of MC service server connection request.
8. The MC service client(s) obtains the respective sidelink signal strength measurements and the Uu signal strength measurements from the MC service capable 5G ProSe (multihop) UE-to-Network relay and the MC service capable 5G ProSe intermediate UE-to-Network relay(s) if available, respectively.
9. The MC service client(s) sends the MC service server a quality of MC service client connection response including the respective measurements obtained in the previous step.
10. The MC service server stores the measurements that correspond to the indirect connection utilized by the remote MC service UE 2.
11. The MC service server sends the MC service client 1 a quality of MC service client connection response including the obtained indirect path information and the respective measurements.
NOTE: Aspects related to re-sending the quality of MC service client connection request/response to update the signal strength measurements is left to implementation, e.g., after a certain period of time.
Annex A (normative):
Configuration data for MC services using 5GS
A.1 General
This Annex provides information about the static data needed for configuration of MC services encompassing the following category:
- Initial MC service UE configuration data (see subclause A.2).
- MC service user profile configuration data (see subclause A.3).
- MC service group configuration data (see subclause A.4).
- MC service configuration data (see subclause A.5).
- Location user profile configuration data (see subclause A.6)
- Initial recording admin UE and/ or replay UE configuration data (see subclause A.7).
- ACM client user profile configuration data (see subclause A.8).
Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MC service UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism.
A.2 Initial MC service UE configuration data
The configuration data defined in 3GPP TS 23.280 [3] in Annex A.6 apply, with the following exceptions:
- DNN and the corresponding DN credentials instead of the PDN credentials shall be used, along with the S-NSSAI to be used for each MC service;
The Default Configured slice(s) information may be pre-configured at the MC service UE and be utilized as defined in 3GPP TS 23.501 [7]. Additional MC network slice identification information may be provided for each S-NSSAI, e.g., the corresponding network slice credentials.
NOTE: It is up to UE implementation, whether an S-NSSAI value is included in the Requested NSSAI. If not included, the corresponding MC traffic could be handled according to the URSP rule with the "match all" Traffic descriptor.
A.3 MC service user profile configuration data
The configuration data defined in 3GPP TS 23.379 [6] in Annex A.3, in 3GPP TS 23.281 [4] in Annex A.3, and 3GPP TS 23.282 [5] in Annex A.3 apply, with the following exceptions:
- The "ProSe discovery group ID" is not used;
The configuration data defined in 3GPP TS 23.281 [4] in Annex A.3, apply, with the following exceptions:
- The "ProSe discovery group ID" is not used;
The configuration data defined in 3GPP TS 23.282 [5] in Annex A.3, apply, with the following exceptions:
- The "Discovery group ID" is not used;
A.4 MC service group configuration data
The configuration data defined in 3GPP TS 23.379 [6] in Annex A.4, 3GPP TS 23.281 [4] in Annex A.4, 3GPP TS 23.282 [5] in Annex A.4, apply, with the following exceptions:
- " Default PQI (as specified in 3GPP TS 23.304 [17]) values" instead of "Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values" shall be used;
Furthermore, Table A.4-1 and Table A.4-2 include the necessary configurations to enable 5G ProSe UE-to-Network Relay and 5G ProSe UE-to-UE Relay services (off-network communication), respectively.
Table A.4-1: Common group configuration data to enable 5G ProSe UE-to-network relay service (on‑network)
Reference
Parameter description
MC service UE
MC service Server
Group management server
Subclause 4.8.2
RSC(s) associated to 5G ProSe UE-to-Network Relay services (as specified in 3GPP TS 23.304 [17])
Y
N
Y
> UE-to-Network Relay Layer indicator per RSC (NOTE 1)
Subclause 4.8.3
RSC(s) associated to 5G ProSe multihop UE-to-Network Relay services (as specified in 3GPP TS 23.304 [17].
Y
N
Y
> UE-to-Network Relay Layer indicator per RSC (NOTE 1)
Y
N
Y
> Multihop indicator per RSC (NOTE 2)
Y
N
Y
> Maximum number of hops per RSC (NOTE 3)
Y
N
Y
NOTE 1: The UE-to-Network Relay Layer indicator indicates whether the associated RSC offers 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service.
NOTE 2: Indicates whether the associated RSC supports multihop connectivity, i.e., 5G ProSe multihop UE-to-Network Relay operationNOTE 3: Indicates the maximum number of hops which can be supported by the associated RSC.
Table A.4-2: Common group configuration data to enable 5G ProSe UE-to-UE relay service (off‑network)
Reference
Parameter description
MC service UE
MC service server
Group management server
Subclause 4.10.2
RSC(s) associated to 5G ProSe UE-to-UE Relay services (as specified in 3GPP TS 23.304 [17])
Y
N
Y
> UE-to-UE Relay Layer indicator per RSC (NOTE 1)
Subclause 4.10.2
ProSe layer-2 group ID (as specified in 3GPP TS 23.304 [17])
Y
N
Y
Subclause 4.10.3
RSC(s) associated to 5G ProSe multihop UE-to-UE Relay services (as specified in 3GPP TS 23.304 [17])
> UE-to-UE Relay Layer indicator per RSC (NOTE 1)
Y
N
Y
> Multihop indicator per RSC (NOTE 2)
Y
N
Y
> Maximum number of hops per RSC (NOTE 3)
Y
N
Y
NOTE 1: The UE-to-UE Relay Layer indicator indicates whether the associated RSC offers 5G ProSe Layer-2 or Layer-3 UE-to-UE Relay service.
NOTE 2: Indicates whether the associated RSC supports multihop connectivity, i.e., 5G ProSe multihop UE-to-UE Relay operation.
NOTE 3: Indicates the maximum number of hops which can be supported for the associated RSC.
A.5 MC service configuration data
The configuration data defined in 3GPP TS 23.379 [6] in Annex A.5, 3GPP TS 23.281 [4] in Annex A.5, 3GPP TS 23.282 [5] in Annex A.5, apply, with the following exceptions:
- "Default PQI (as specified in 3GPP TS 23.304 [17]) values" instead of "Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values" shall be used;
A.6 Location user profile configuration data
The location user profile configuration data defined in A.8 of 3GPP TS 23.280 [3] applies.
A.7 Initial recording admin UE and/or replay UE configuration data
The initial recording admin and replay UE configuration data defined in A.10 of 3GPP TS 23.280 [6] is applicable with the following exceptions:
- DNN and the corresponding PDU access credentials shall be used instead of APN and PDN access credentials for configurations related to 3GPP connectivity information.
The default configured slice(s) information may be pre-configured at the MC service UE and be utilized as defined in 3GPP TS 23.501 [7].
A.8 ACM client user profile configuration data
The ACM client user profile configuration data defined in 3GPP TS 23.280 [6] clause A.9 is applicable.
A.9 MC UE configuration data
Annex A.2 in 3GPP TS 23.379 [6], Annex 2 in 3GPP TS 23.281 [4] and Annex 2 in 3GPP TS 23.282 [5] applies with the following updates in Table A.2-2 in 3GPP TS 23.379 [6], Table A.2-2 in 3GPP TS 23.281 [4] and Table A.2-2 in 3GPP TS 23.282 [5] to support 5G ProSe UE-to-Network Relay services as described in clause 4.8.
Table A.9-1: UE configuration data to enable 5G ProSe UE-to-Network Relay service (on network)
Reference
Parameter description
Subclause 4.8.2
Relay service (Y/N)
Subclause 4.8.2
List of allowed relayed MCPTT groups, MCVideo groups, or MCData groups and their RSC(s) (as specified in 3GPP TS 23.304 [17]) (optional) (see NOTE)
> MCPTT group ID, MCVideo group ID, or MCData group ID
> RSC(s) for 5G ProSe UE-to-Network Relay service (as specified in 3GPP TS 23.304 [17])
NOTE: When the value of the parameter Relay service is N, this parameter and its child parameters are not needed.
A.10 MC UE configuration data
Annex A.2 in 3GPP TS 23.379 [6], Annex 2 in 3GPP TS 23.281 [4] and Annex 2 in 3GPP TS 23.282 [5] applies with the following updates in Table A.2-2 in 3GPP TS 23.379 [6], Table A.2-2 in 3GPP TS 23.281 [4] and Table A.2-2 in 3GPP TS 23.282 [5] to support 5G ProSe UE-to-Network Relay services as described in clause 4.8.
Table A.x-1: UE configuration data to enable 5G ProSe UE-to-Network Relay service (on network)
Reference
Parameter description
Subclause 4.8.2
Relay service (Y/N)
Subclause 4.8.2
List of allowed relayed MCPTT groups, MCVideo groups, or MCData groups and their RSC(s) (as specified in 3GPP TS 23.304 [17]) (optional) (see NOTE 1)
> MCPTT group ID, MCVideo group ID, or MCData group ID
> RSC(s) for 5G ProSe UE-to-Network Relay service (as specified in 3GPP TS 23.304 [17])
>> UE-to-Network Relay Layer indicator (Note 2)
Subclause 4.8.3
RSC(s) for 5G Prose multihop UE-to-Network Relay service (as specified in 3GPP TS 23.304 [17])
> UE-to-Network Relay Layer indicator per RSC (NOTE 2)
> Multihop indicator per RSC (NOTE 3)
> Maximum number of hops per RSC (NOTE 4)
NOTE 1: When the value of the parameter Relay service is N, this parameter and its child parameters are not needed.
NOTE 2: The UE-to-Network Relay Layer indicator indicates whether the associated RSC offers 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service.
NOTE 3: Indicates whether the associated RSC can be supported for 5G ProSe multihop UE-to-Network Relay operation for the associated RSC.
NOTE 4: Indicates the maximum number of hops which can be supported for the associated RSC.
Annex B (informative):
Service continuity for MC service
B.1 Service continuity between on-network MC service and UE-to-network relay MC service
This annex describes how 3GPP TS 23.237 [18] mechanisms for IMS service continuity can be used to provide service continuity between on-network MC service and UE-to-network relay MC service.
Figure B.1-1: Service continuity from on-network to UE-to-network relay
The details of MBS interfaces are specified in clause 4.7. The interaction between SIP core and 5GC is specified in 3GPP TS 23.228 [2]. The procedure for service continuity from on-network MCPTT service to UE-to-network relay MCPTT service is described in Annex B of 3GPP TS 23.280 [3].
As illustrated in figure B.1-1:
- Initially UE-1 has a direct connection to the network via 5GS (on-network MCPTT service). It is registered with the SIP core and is engaged in a SIP session with the MCPTT Application Server (solid lines SIP-1 and MC[service]-1 in figure B.1-1).
- When UE-1 realises that it is losing connection to the network, or after the connection to the network has been lost, UE-1 discovers a UE-to-network relay (UE-R) and establishes a PC5 connection with UE-R. UE-1 registers with the SIP core over the target access leg and enters UE-to-network relay MC service by transferring the media streams over the target leg (dashed lines SIP-1 and MC[service]-1 in figure B.1-1).
- The SIP session is anchored at a Service Centralisation and Continuity Application Server (SCC AS) before and after the handover, as described in 3GPP TS 23.237 [18].
Annex C (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2020-10
SA6#39-BIS-e
Initial version.
0.0.0
2020-10
Implemented the following pCRs approved in SA6#39-BIS-e:
S6-201792, S6-201981.
0.1.0
2020-11
SA6#40-e
Implemented the following pCRs approved in SA6#40-e:
S6-202308, S6-202309.
0.2.0
2021-01
SA6#41-e
Implemented the following pCRs approved in SA6#41-e:
S6-210197, S6-210199, S6-210214,S6-210216, S6-210217, S6-210218, S6-210219, S6-210333
0.3.0
2021-03
SA6#42-e
Implemented the following pCRs approved in SA6#42-e:
S6-210553, S6-210650, S6-210686
0.4.0
2021-03
SA#91-e
SP-210176
Presentation for information at SA#91-e
1.0.0
2021-04
SA6#42-BIS-e
Implemented the following pCRs approved in SA6#42-BIS-e:
S6-210953, S6-210954
1.1.0
2021-05
Editorial corrections
1.1.1
2021-06
SA6#43-e
Implemented the following pCRs approved in SA6#43-e:
S6-211405, S6-211407, S6-211408, S6-211409, S6-211410
1.2.0
2021-06
SA#92-e
SP-210473
Presentation for approval at SA#92-e
2.0.0
2021-06
SA#92-e
SP-210473
MCC Editorial update for publication after TSG SA approval (SA#92)
17.0.0
2021-12
SA#94-e
SP-211526
0013
1
F
Corrections on network slicing
17.1.0
2021-12
SA#94-e
SP-211530
0004
2
B
MBS session release
18.0.0
2021-12
SA#94-e
SP-211530
0007
2
B
MC service media distribution over 5G MBS
18.0.0
2021-12
SA#94-e
SP-211530
0008
1
B
Call connect and disconnect over 5G MBS in MCPTT context
18.0.0
2021-12
SA#94-e
SP-211530
0009
1
B
Call connect and disconnect over 5G MBS in MCVideo context
18.0.0
2021-12
SA#94-e
SP-211530
0010
1
B
Service continuity between 5G MBS delivery and unicast delivery
18.0.0
2021-12
SA#94-e
SP-211530
0011
2
B
Architecture for MC/5MBS
18.0.0
2021-12
SA#94-e
SP-211530
0012
3
B
MBS architecture and functionalities
18.0.0
2021-12
SA#94-e
SP-211530
0014
1
B
Request for creation of MBS resources for group communications
18.0.0
2021-12
SA#94-e
SP-211530
0016
B
Request for updating MBS resources for group communications
18.0.0
2021-12
SA#94-e
SP-211530
0017
1
B
Request to activate or de-activate multicast MBS sessions
18.0.0
2021-12
SA#94-e
SP-211530
0020
1
B
MC service control signalling over 5G MBS
18.0.0
2021-12
SA#94-e
SP-211530
0021
2
B
Multi-server MBS session coordination
18.0.0
2021-12
SA#94-e
SP-211530
0022
2
B
Procedure for inter-system switching between eMBMS and 5G MBS
18.0.0
2022-03
SA#95-e
SP-220107
0023
1
C
Alignment of section 4.7 of 23.289 with latest version of 23.247 (v 17.1.0)
18.1.0
2022-03
SA#95-e
SP-220107
0024
1
F
Updating aspects related to the MBS resources update
18.1.0
2022-03
SA#95-e
SP-220107
0025
1
F
Alignment of some information flows within TS 23.289
18.1.0
2022-03
SA#95-e
SP-220108
0026
1
B
Use of 5G ProSe UE-to-network relay service for MC services
18.1.0
2022-03
SA#95-e
SP-220107
0027
1
F
Updating aspects and terminology related to MBS session creation and MC traffic transmission
18.1.0
2022-03
SA#95-e
SP-220107
0028
1
F
Updating the MBS session release related terminology and aspects
18.1.0
2022-03
SA#95-e
SP-220107
0029
1
F
Minor corrections to the procedures related to MBS session creation
18.1.0
2022-03
SA#95-e
SP-220107
0030
B
EPS interworking requirements
18.1.0
2022-03
SA#95-e
SP-220107
0031
B
MC services over 5GS supporting EPS interworking
18.1.0
2022-03
SA#95-e
SP-220107
0032
B
Network notifications for EPS interworking related events
18.1.0
2022-03
SA#95-e
SP-220107
0033
C
Update to inter-system switching between 5G MBS and eMBMS procedures
18.1.0
2022-03
SA#95-e
SP-220107
0034
2
C
Clean up of EPS-5GMBS interworking
18.1.0
2022-03
SA#95-e
SP-220107
0035
2
C
Clean up of switching between unicast and 5G MBS, between LTE eMBMS and 5G MBS
18.1.0
2022-03
SA#95-e
SP-220107
0036
1
C
Enhanced MCPTT group call setup procedure with 5MBS session
18.1.0
2022-03
SA#95-e
SP-220107
0037
1
C
Information flows for media distribution over 5MBS
18.1.0
2022-03
SA#95-e
SP-220107
0038
1
C
Description of 5G MBS usage for MCData
18.1.0
2022-03
SA#95-e
SP-220107
0039
1
C
Updates to usage of 5MBS for MCVideo
18.1.0
2022-03
SA#95-e
SP-220107
0040
1
F
Corrections to align with SA2 5G MBS specification
18.1.0
2022-03
SA#95-e
SP-220107
0041
1
C
Usage of FEC capabilities
18.1.0
2022-03
SA#95-e
SP-220108
0042
1
B
Architectural model over 5G ProSe
18.1.0
2022-03
SA#95-e
SP-220108
0043
1
B
Off-network functional model over 5G ProSe
18.1.0
2022-03
SA#95-e
SP-220108
0044
B
Off network group communication for MC service
18.1.0
2022-03
SA#95-e
SP-220108
0045
1
B
Off network private communication for MC service
18.1.0
2022-03
SA#95-e
SP-220108
0046
1
B
5G ProSe UE-to-network relay for MC service
18.1.0
2022-03
SA#95-e
SP-220108
0047
2
B
Service continuity with a 5G ProSe UE-to-network relay for MBMS
18.1.0
2022-06
SA#96
SP-220480
0048
1
C
Clarifications related to multi carrier support for MBS session creation and announcement
18.2.0
2022-06
SA#96
SP-220480
0049
1
B
Clarifications related to multi carrier support for MBS session update
18.2.0
2022-06
SA#96
SP-220479
0050
1
C
Update to service continuity procedure from an MBS session to 5G ProSe UE-to-network relay
18.2.0
2022-06
SA#96
SP-220479
0051
1
C
Update to service continuity procedure from 5G ProSe UE-to-network relay to an MBS session
18.2.0
2022-06
SA#96
SP-220479
0052
1
B
Requirements related to 5G ProSe Layer-3 relaying via N3IWF
18.2.0
2022-06
SA#96
SP-220476
0053
F
Corrections to the use of MC service system
18.2.0
2022-06
SA#96
SP-220480
0054
F
Corrections in MBS UE session join notification
18.2.0
2022-06
SA#96
SP-220480
0055
D
Small editorial corrections
18.2.0
2022-06
SA#96
SP-220480
0056
1
B
Update to 5G MBS service announcement
18.2.0
2022-06
SA#96
SP-220480
0057
1
F
Update to broadcast MBS sessions monitoring and the reception quality of the MBS session
18.2.0
2022-06
SA#96
SP-220480
0058
F
Resolve the EN about architecture and reference alignment in clause 4.7.1
18.2.0
2022-06
SA#96
SP-220480
0059
1
C
Resolve the EN in clause 5.2
18.2.0
2022-06
SA#96
SP-220480
0060
1
C
Resolve the EN on SA4 aspect
18.2.0
2022-06
SA#96
SP-220480
0064
3
F
Architectural and functional model for 5G MBS mission critical UE
18.2.0
2022-06
SA#96
SP-220480
0067
1
F
Rename "MBS service announcement" to "MBS session announcement" for self consistency in the spec
18.2.0
2022-06
SA#96
SP-220480
0068
2
B
Group communication connect and disconnect over 5G MBS for MCData
18.2.0
2022-06
SA#96
SP-220475
0069
1
A
Updating network slicing requirements for MC services
18.2.0
2022-06
SA#96
SP-220480
0071
1
C
Including MBS FSA ID into the location information report
18.2.0
2022-06
SA#96
SP-220480
0073
C
Removing unicast bearer status from eMBMS bearer information
18.2.0
2022-06
SA#96
SP-220480
0074
F
Add MBS service announcement acknowledge
18.2.0
2022-06
SA#96
SP-220480
0075
1
F
Clarification on GC1 in clause 4.7
18.2.0
2022-06
SA#96
SP-220480
0076
1
F
Format corrections to clause 7.3.2.9
18.2.0
2022-06
SA#96
SP-220480
0077
1
F
UE session join notification message name alignment
18.2.0
2022-06
SA#96
SP-220480
0078
1
F
Update to de-announcement
18.2.0
2022-09
SA#97-e
SP-220929
0079
F
Various textual fixes in 23.289 v 18.2.0
18.3.0
2022-09
SA#97-e
SP-220929
0080
1
C
Updating the general architecture of MBS system
18.3.0
2022-09
SA#97-e
SP-220929
0081
1
F
Clarification on MBS capable RAT usage
18.3.0
2022-09
SA#97-e
SP-220929
0082
1
F
Adding SCEF+NEF deployment option
18.3.0
2022-09
SA#97-e
SP-220929
0083
2
F
Clarification on MBS QoS
18.3.0
2022-09
SA#97-e
SP-220929
0084
2
F
Corrections to inter-RAT change report via LMC and LMS
18.3.0
2022-09
SA#97-e
SP-220929
0086
1
F
Message name corrections to clause 7.3.3.6.2
18.3.0
2022-09
SA#97-e
SP-220929
0087
F
Configurations for MC over 5G Prose
18.3.0
2022-09
SA#97-e
SP-220929
0088
1
F
Clarifications on UE´s MBMS/MBS capabilities
18.3.0
2022-09
SA#97-e
SP-220929
0089
1
F
Adding references to 3GPP TS 26.502
18.3.0
2022-09
SA#97-e
SP-220929
0090
1
C
Correcting MBS session ID types
18.3.0
2022-09
SA#97-e
SP-220929
0091
1
F
Update the scope clause with reference to 5G network architecture specs
18.3.0
2022-12
SA#98-e
SP-221248
0092
1
F
N5 descriptions update for MBS
18.4.0
2022-12
SA#98-e
SP-221248
0093
1
F
Added additional subclause for switching from MBS session to unicast bearer for MCPTT
18.4.0
2022-12
SA#98-e
SP-221248
0094
F
Corrections to reference point usage in switching from MBS session to unicast bearer for MCData
18.4.0
2022-12
SA#98-e
SP-221248
0095
F
Title correction and use of group communication connect & disconnect clarification in MCData
18.4.0
2023-03
SA#99
SP-230291
0096
1
F
MBS session identity corrections
18.5.0
2023-03
SA#99
SP-230291
0097
2
F
Clarification on MBS service area in pre-conditions
18.5.0
2023-03
SA#99
SP-230291
0098
2
F
Clarification on the unicast delivery stop after MBS delivery
18.5.0
2023-03
SA#99
SP-230291
0100
1
F
Correction for usage of term MCX to MC service
18.5.0
2023-06
SA#100
SP-230703
0101
1
C
Add 5G NR Cell Global Identifier (NCGI) to Location Information Element
18.6.0
2023-09
SA#101
SP-231006
0104
F
Add 5G NR Cell Global Identifier (NCGI) to Location Information Element
18.7.0
2023-09
SA#101
SP-231006
0105
2
F
Resolve the ENs about NPN utilization
18.7.0
2023-09
SA#101
SP-231006
0107
2
F
Support of multicast MBS data reception in RRC inactive state
18.7.0
2023-12
SA#102
SP-231554
0108
1
F
Update resources management procedures
19.0.0
2023-12
SA#102
SP-231554
0109
1
F
Including clarification related to the IE of resource management
19.0.0
2024-03
SA#103
SP-231554
0117
A
Alignments of 23.289 Rel-19 with other specs
19.1.0
2024-06
SA#104
SP-240759
0119
1
A
Including NID in the MBS session announcement
19.2.0
2024-06
SA#104
SP-240767
0120
2
B
UE to UE single hop relay
19.2.0
2024-06
SA#104
SP-240768
0121
F
Add the FRMCS requirements reference
19.2.0
2024-06
SA#104
SP-240767
0122
1
F
Correction of the reference in the scope clause
19.2.0
2024-06
SA#104
SP-240767
0123
B
5G MC interworking with legacy system
19.2.0
2024-06
SA#104
SP-240767
0124
1
D
Corrections of the NOTE number
19.2.0
2024-09
SA#105
SP-241223
0125
1
B
Support of exposing network congestion information for MC services
19.3.0
2024-09
SA#105
SP-241223
0127
1
B
Enhancement to MCVideo with 5G network capabilities
19.3.0
2024-12
SA#106
SP-241722
0126
3
B
Location reporting information obtained from the PLMN operator (5G)
19.4.0
2024-12
SA#106
SP-241708
0129
3
A
MBS service area handling
19.4.0
2024-12
SA#106
SP-241722
0130
2
F
Corrections in clauses related to ECN marking for L4S
19.4.0
2024-12
SA#106
SP-241722
0131
1
B
MCVideo push enhancement via ECN marking for L4S
19.4.0
2024-12
SA#106
SP-241723
0132
B
Support of MCGWUE over 5GS
19.4.0
2024-12
SA#106
SP-241717
0133
1
B
Support of MC services over NTN
19.4.0
2024-12
SA#106
SP-241717
0134
1
B
Business agreements related to NTN
19.4.0
2024-12
SA#106
SP-241722
0136
1
B
Include the support of MC recording and replay and ACM for 5GS
19.4.0
2024-12
SA#106
SP-241708
0138
A
Correction of reference points in 23.289 Rel-19
19.4.0
2024-12
SA#106
SP-241707
0140
2
A
Correction of a reference in clause 7.3.3.1.3
19.4.0
2024-12
SA#106
SP-241707
0141
2
C
Support of provisioning MBS assistance information to the 5GC
19.4.0
2025-03
SA#107
SP-250211
0144
1
F
Some corrections to 23.289
19.5.0
2025-03
SA#107
SP-250205
0145
F
Minor correction in clause 4.12.1
19.5.0
2025-06
SA#108
SP-250605
0150
3
F
Support 5G MBS in MC gateway UE
19.6.0
2025-06
SA#108
SP-250607
0151
1
F
Support of 5G IOPS in 23.289
19.6.0
2025-06
SA#108
SP-250613
0147
1
B
The support to enable 5G ProSe multi-hop UE-to-network relay
20.0.0
2025-06
SA#108
SP-250613
0148
1
B
The support to enable 5G ProSe multi-hop UE-to-UE relay
20.0.0
2025-06
SA#108
SP-250613
0149
1
B
Update cl. 5.3.5 to enable off-network via UE2UE relay and multi-hop UE2UE relay
20.0.0
2025-06
SA#108
SP-250604
0153
F
Configurations fixes
20.0.0
2025-09
SA#109
SP-251060
0156
1
A
5G ProSe configurations correction
20.1.0
2025-09
SA#109
SP-251057
0159
1
A
Clarification on receiving multicast MBS data in RRC_INACTIVE state
20.1.0
2026-01
SA#110
SP-251488
0161
B
5G ProSe multihop configurations addition
20.2.0
2026-01
SA#110
SP-251488
0163
2
B
Provide the quality of MC client connection to authorized MC users
20.2.0
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 1 Scope
| The present document specifies the Stage 2 of the Proximity based Services (ProSe) features in 5GS. 5G ProSe features consist of: 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay, 5G ProSe UE-to-UE Relay and 5G ProSe Intermediate UE-to-Network Relay.
5G ProSe Direct Discovery identifies that 5G ProSe-enabled UEs are in proximity using NR.
5G ProSe Direct Communication enables establishment of communication paths between two or more 5G ProSe-enabled UEs that are in direct communication range using NR.
5G ProSe UE-to-Network Relay enables indirect Layer-2 and Layer-3 single-hop communication and Layer-2 and Layer-3 Multi-hop communication between the 5G network and 5G ProSe-enabled UEs (e.g. for 5G ProSe-enabled UEs that are out of coverage of the network).
5G ProSe UE-to-UE Relay enables indirect Layer-2 and Layer-3 single-hop communication and Layer-3 Multi-hop communication between two 5G ProSe End UEs.
5G ProSe Intermediate UE-to-Network Relay enables Layer-2 and Layer-3 multi-hop communication between a 5G Remote UE and a 5G ProSe UE-to-Network Relay.
Security aspects of ProSe in 5GS are defined in TS 33.503 [29].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
[3] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".
[4] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[5] 3GPP TS 23.502: "Procedures for the 5G System (5GS); Stage 2".
[6] 3GPP TS 22.261: "Service requirements for next generation new services and markets; Stage 1".
[7] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
[8] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[9] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System".
[10] Void.
[11] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[12] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
[13] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in idle mode".
[14] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station in idle mode".
[15] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[16] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol Specification".
[17] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration".
[18] IETF RFC 3927: "Dynamic Configuration of IPv4 Link-Local Addresses".
[19] IETF RFC 826: "An Ethernet Address Resolution Protocol".
[20] Void.
[21] 3GPP TR 23.752: "Study on system enhancement for Proximity based Services (ProSe) in the 5G System (5GS)".
[22] 3GPP TS 32.277: "Proximity-based Services (ProSe) charging".
[23] 3GPP TS 24.554: "Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3".
[24] IETF RFC 2131: "Dynamic Host Configuration Protocol".
[25] IETF RFC 4039: "Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)".
[26] Void.
[27] Void.
[28] 3GPP TS 38.351: "NR; Sidelink Adaptation Layer Protocol".
[29] 3GPP TS 33.503: "Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS)".
[30] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[31] 3GPP TS 23.167: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; IP Multimedia Subsystem (IMS) emergency sessions".
[32] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[33] 3GPP TS 22.268: "Public Warning System (PWS) requirements".
[34] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[35] IETF RFC 7181: "The Optimized Link State Routing Protocol Version 2 (OLSRv2)".
[36] IETF RFC 6130: "Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)".
[37] IETF RFC 5444: "Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format".
[38] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[39] IETF RFC 5498: "IANA Allocations for Mobile Ad Hoc Network (MANET) Protocols".
[40] IETF RFC 6621: "Simplified Multicast Forwarding".
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 3 Definitions of terms and abbreviations
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
5G ProSe-enabled UE: A UE that supports 5G ProSe requirements and associated procedures.
5G ProSe Direct Discovery: A procedure employed by a 5G ProSe-enabled UE to discover other 5G ProSe-enabled UEs in its vicinity based on direct radio transmissions between the two UEs with NR technology.
5G ProSe Direct Communication: A communication between two or more UEs in proximity that are 5G ProSe-enabled, by means of user plane transmission using NR technology via a path not traversing any network node.
5G ProSe UE-to-Network Relay: A 5G ProSe-enabled UE that provides functionality to support connectivity to the network for 5G ProSe Remote UE(s).
5G ProSe Intermediate UE-to-Network Relay: A 5G ProSe-enabled UE that provides functionality to support connectivity to the network for 5G ProSe Remote UE(s) by using the PC5 reference point with other 5G ProSe-enabled UEs. The 5G ProSe Intermediate UE-to-Network Relay is located on the path between 5G ProSe Remote UE and 5G ProSe UE-to-Network Relay.
5G ProSe Remote UE: A 5G ProSe-enabled UE that communicates with a DN via zero or more 5G ProSe Intermediate UE-to-Network Relay(s) and a 5G ProSe UE-to-Network Relay.
5G ProSe UE-to-UE Relay: A 5G ProSe-enabled UE that provides functionality to support connectivity between 5G ProSe End UEs.
5G ProSe End UE: A 5G ProSe-enabled UE that connects with another 5G ProSe-enabled UE(s) via one or more 5G ProSe UE-to-UE Relay(s).
Application Layer ID: An identifier identifying a 5G ProSe-enabled UE within the context of a specific application. The format of this identifier is outside the scope of 3GPP.
Direct Network Communication: One mode of network communication, where there is no 5G ProSe UE-to-Network Relay between a UE and the 5G network.
Indirect Network Communication: One mode of network communication, where there is a 5G ProSe UE-to-Network Relay between a UE and the 5G network.
Member ID: An identifier uniquely identifying a member in the Application Layer managed group and that is managed by the ProSe application layer.
Mode of communication: Mode of communication to be used by the 5G ProSe-enabled UE over PC5 reference point, i.e. broadcast mode, groupcast mode or unicast mode.
Open ProSe Discovery: ProSe Direct Discovery without explicit permission from the 5G ProSe-enabled UE being discovered, according to TS 22.278 [7].
ProSe identifier: A globally unique identifier used to identify the ProSe Application associated with the ProSe operation in 5G ProSe Direct Discovery and 5G ProSe Direct Communication. In this Release, the "Application ID" defined in TS 23.303 [3] can be used as the ProSe identifier in 5G ProSe Direct Discovery and in a consequent 5G ProSe Direct Communication.
Restricted ProSe Discovery: ProSe Direct Discovery that only takes place with explicit permission from the 5G ProSe-enabled UE being discovered, according to TS 22.278 [7].
Relay Service Code: A Relay Service Code is used for the case of UE-to-Network Relay as well as for the case of UE-to-UE Relay. The definition for the case of UE-to-Network Relay is in TS 23.303 [3]. For the case of UE-to-UE Relay, the Relay Service Code is used to identify a connectivity service the 5G ProSe UE-to-UE Relay provides and the authorized users the 5G ProSe UE-to-UE Relay would offer service to. The definition of values of Relay Service Code for the case of UE-to-UE Relay is out of scope of this specification.
User Info ID: The User Info ID is configured for Model A or Model B Group Member Discovery, 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery, either for public safety or commercial applications based on the policy of the HPLMN or via the ProSe application server that allocates it. The definition of values of User Info ID is out of scope of this specification.
For the purposes of the present document, the following term and definition given in TS 23.303 [3] apply:
Application Layer Group ID
Destination Layer-2 ID
Discovery Entry ID
Discovery Filter
Discovery Query Filter
Discovery Response Filter
Geographical Area
Local PLMN
Model A
Model B
Metadata Index Mask
ProSe Application ID
ProSe Application Code
ProSe Application Mask
ProSe Query Code
ProSe Response Code
ProSe Restricted Code
ProSe Restricted Code Prefix
ProSe Restricted Code Suffix
ProSe Discovery UE ID
ProSe Layer-2 Group ID
Restricted ProSe Application User ID
Source Layer-2 ID
For the purposes of the present document, the following term and definition given in TS 23.287 [2] apply:
NR Tx Profile
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
5G DDNMF 5G Direct Discovery Name Management Function
AS layer Access Stratum layer
NCGI NR Cell Global ID
PDUID ProSe Discovery UE ID
PFI PC5 QoS Flow Identifier
PQI PC5 5QI
ProSe Proximity based Services
RPAUID Restricted ProSe Application User ID
RSC Relay Service Code
RSD Rule Selection Descriptor
TAI Tracking Area Identity
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4 Architecture model and concepts
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.1 General concept
| Proximity based Services (ProSe) are services that can be provided by the 5GS based on UEs being in proximity to each other.
The 5GS enablers for ProSe include the following functions:
- 5G ProSe Direct Discovery;
- 5G ProSe Direct Communication;
- 5G ProSe UE-to-Network Relay;
- 5G ProSe Intermediate UE-to-Network Relay;
- 5G ProSe UE-to-UE Relay.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2 Architectural reference model
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.1 Non-roaming reference architecture
| Figure 4.2.1-1 shows the high-level view of the non-roaming 5G System architecture for Proximity-based Services (ProSe) with service-based interfaces within the Control Plane. In this figure, UE A and UE B use a subscription of the same PLMN.
Figure 4.2.1-1: Non-roaming 5G System architecture for Proximity-based Services
Figure 4.2.1-2 shows the high-level view of the non-roaming 5G System architecture for Proximity-based Services (ProSe) in reference point representation. In this figure, UE A and UE B use a subscription of the same PLMN.
Figure 4.2.1-2: Non-roaming 5G System architecture for Proximity-based Services in reference point representation
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.2 Roaming reference architecture
| Figure 4.2.2-1 shows the high-level view of the roaming 5G System architecture for Proximity-based Services (ProSe) with service-based interfaces within the Control Plane. In the figure, UE A uses a subscription of HPLMN.
Figure 4.2.2-1: Roaming 5G System architecture for Proximity-based Services
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.3 Inter-PLMN reference architecture
| The following figure 4.2.3-1 shows the high level view of the non-roaming inter-PLMN architecture with service-based interfaces within the Control Plane. In this figure, PLMN A is the HPLMN of UE A and PLMN B is the HPLMN of UE B.
Figure 4.2.3-1: Non-roaming Inter-PLMN 5G System architecture for Proximity-based Services
Figure 4.2.3-2 shows the high level view of the roaming architecture with service-based interfaces within the Control Plane. In this figure, UE A uses a subscription of PLMN A and UE B uses a subscription of PLMN B; UE A is roaming in PLMN C while UE B is not roaming.
Figure 4.2.3-2: Roaming Inter-PLMN 5G System architecture for Proximity-based Services
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.4 AF-based service parameter provisioning
| The 5G System provides NEF services to enable communication between NFs in the PLMN and a ProSe Application Server. Figure 4.2.4-1 shows the high level view of AF-based service parameter provisioning for 5G ProSe communications. The ProSe Application Server may provide ProSe service parameters to the PLMN via NEF. The NEF stores the ProSe service parameters in the UDR.
Figure 4.2.4-1: 5G System architecture for AF-based service parameter provisioning for 5G ProSe communications
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.5 Reference points
| PC1: The reference point between the ProSe application in the UE and in the ProSe Application Server. It is used to define application level signalling requirements. This reference point is not specified in this release of the specification.
PC3a: The reference point between the UE and the 5G DDNMF. PC3a relies on 5GC user plane for transport (i.e. an "over IP" reference point). It is used to authorise 5G ProSe Direct Discovery request and perform allocation of ProSe Application Codes / ProSe Restricted Codes corresponding to ProSe Application Identities used for 5G ProSe Direct Discovery.
PC5: The reference point between ProSe-enabled UEs used for control and user plane for 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay, 5G ProSe Intermediate UE-to-Network Relay and 5G ProSe UE-to-UE Relay.
PC8: The reference point between the UE and the 5G ProSe Key Management Function (5G PKMF). The details are defined in TS 33.503 [29].
Npc2: The reference point between the ProSe Application Server and the 5G DDNMF. It is used to define the interaction between ProSe Application Server and 5G DDNMF for 5G ProSe Direct Discovery.
Npc4: The reference point between the UDM and 5G DDNMF. It is used to provide subscription information in order to authorise 5G ProSe Direct Discovery request.
Npc6: The reference point between the 5G DDNMF in the HPLMN and the 5G DDNMF in a Local PLMN (5G ProSe Direct Discovery). This reference point is used for HPLMN control of ProSe service authorization.
Npc7: The reference point between the 5G DDNMF in the HPLMN and the 5G DDNMF in the VPLMN. It is used for HPLMN control of ProSe service authorization.
Npc8: The reference point between the PCF and the 5G DDNMF. It is used to define the interactions between the 5G DDNMF and the PCF to e.g. get a PDUID from the PCF.
Npc9: The reference point between the 5G PKMF of the 5G ProSe Remote UE and the 5G PKMF of the 5G ProSe UE-to-Network Relay and between the 5G PKMF of the 5G ProSe End UE and the 5G PKMF of the 5G ProSe UE-to-UE Relay. The details are defined in TS 33.503 [29].
Npc10: The reference point between the 5G PKMF and UDM. The details are specified in TS 33.503 [29].
Npc11: The reference point between the AUSF and Prose Anchor Function (PAnF). The details are specified in TS 33.503 [29].
Npc12: The reference point between the PAnF and UDM. The details are specified in TS 33.503 [29].
Npc13: The reference point between the SMF and PKMF. The details are specified in TS 33.503 [29].
Npc14: The reference point between the SMF and PAnF. The details are specified in TS 33.503 [29].
NOTE: Npc2, Npc4, Npc6, Npc7, Npc8, Npc9, Npc10, Npc11, Npc12, Npc13 and Npc14 show the interactions that exist between the NF services in the NFs. These reference points are realised by corresponding NF service-based interfaces and by specifying the identified consumer and producer NF service as well as their interaction in order to realize a particular system procedure.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.6 Service-based interfaces
| N5g-ddnmf: Services provided by 5G DDNMF to manage inter-PLMN 5G ProSe Direct Discovery operations.
Npkmf: Service provided by 5G PKMF to support inter-PLMN ProSe security management. The function of Npkmf is defined in TS 33.503 [29].
In addition to the relevant services defined in TS 23.501 [4] for the following service-based interfaces, in the case of ProSe Service, the services can be provided by corresponding NF are as follows:
Nudm: Services provided by UDM are used to get 5G ProSe Service related subscription information to the AMF during Initial Registration procedure or UE Configuration Update (UCU) procedure to inform the AMF the subscription information has changed and to provide ProSe Service related subscription information to 5G DDNMF for the authorisation of 5G ProSe Direct Discovery requests. The subscription information is described in TS 23.502 [5]. Services provided by UDM may also be used by the 5G PKMF for relay service authorisation, see TS 33.503 [29].
Npcf: Services provided by H-PCF are used to provide 5G ProSe Service related parameters to V-PCF for the UE and NG-RAN in the roaming case and to enable the 5G DDNMF to get a PDUID or be notified of PDUID change.
Nudr: Services provided by UDR are used to notify the PCF and the UDM of the update of the 5G ProSe Service related information as described in TS 23.502 [5].
Nnef: Services provided by NEF are used by the ProSe Application Server to update 5G ProSe Service related information of 5GC.
Namf: Services provided by AMF are consumed by PCF to provide the 5G ProSe Service related parameters for the UE and the NG-RAN to the AMF and to enable the AMF create or update the UE context related to 5G ProSe service.
Nnrf: Services provided by NRF are used to discover the PCF that supports 5G ProSe service and for 5G DDNMF in HPLMN to discover other 5G DDNMFs in VPLMN or local PLMN.
Naf: Services provided by AF are consumed by the DDNMF to request authorization for Discovery Request. The AF may update the authorization information to revoke the Restricted ProSe Direct Discovery permission.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.7 5G ProSe UE-to-Network Relay reference architecture
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.7.1 5G ProSe Layer-3 UE-to-Network Relay reference architecture
| The following figure 4.2.7.1-1 shows the high level reference architecture for 5G ProSe Layer-3 UE-to-Network Relay. In this figure, the 5G ProSe Layer-3 UE-to-Network Relay may be in the HPLMN or a VPLMN.
Figure 4.2.7.1-1: Reference architecture for 5G ProSe Layer-3 UE-to-Network Relay
The following figure 4.2.7.1-2 shows the non-roaming reference architecture for 5G ProSe Layer-3 UE-to-Network Relay when N3IWF is supported. In this figure, the PLMN A and PLMN B may be the same or different. When the 5G ProSe Layer-3 Remote UE may connect to NG-RAN directly to access PLMN B and in that case it would take the role of UE in the figure. The N3IWF may be connected to Relay UE UPF via a Data Network.
Figure 4.2.7.1-2: Non-roaming architecture model for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support
The following figure 4.2.7.1-3 shows the roaming reference architecture for 5G ProSe Layer-3 UE-to-Network Relay. In this figure, the PLMN A and PLMN B may be the same or different and/or the PLMN A and PLMN C may be the same or different. The N3IWF may be connected to Relay UE UPF via a Data Network.
Figure 4.2.7.1-3: Roaming architecture model for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support
4.2.7.1A 5G ProSe Multi-hop Layer-3 UE-to-Network Relay reference architecture
Figure 4.2.7.1A-1 shows the high level reference architecture for 5G ProSe Multi-hop Layer-3 UE-to-Network Relay. There may be one or multiple 5G ProSe Intermediate UE-to-Network Relays between the 5G Prose Remote UE and the 5G ProSe UE-to-Network Relay. In this figure, the 5G ProSe Layer-3 UE-to-Network Relay may be in the HPLMN or a VPLMN.
Figure 4.2.7.1A-1: Reference architecture for 5G ProSe Multi-hop Layer-3 UE-to-Network Relay
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.7.2 5G ProSe Layer-2 UE-to-Network Relay reference architecture
| Figure 4.2.7.2-1 shows the 5G ProSe Layer-2 UE-to-Network Relay reference architecture. The 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay may be served by the same or different PLMNs. If the serving PLMNs of the 5G ProSe Layer-2 Remote UE and the 5G ProSe Layer-2UE-to-Network Relay are different then NG-RAN is shared by the serving PLMNs, see the 5G MOCN architecture in clause 5.18 of TS 23.501 [4].
Figure 4.2.7.2-1: 5G ProSe Layer-2 UE-to-Network Relay reference architecture
NOTE 1: Uu between the 5G ProSe Layer-2 Remote UE and NG-RAN consists of RRC, SDAP and PDCP.
NOTE 2: The 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay are served by the same NG-RAN. The Core Network entities (e.g. AMF, SMF, UPF) serving the 5G ProSe Layer-2 Remote UE and the 5G ProSe Layer-2 UE-to-Network Relay can be the same or different.
4.2.7.2a 5G ProSe Multi-hop Layer-2 UE-to-Network Relay reference architecture
Figure 4.2.7.2a-1 shows the 5G ProSe Multi-hop Layer-2 UE-to-Network Relay reference architecture. The 5G ProSe Layer-2 Remote UE, the 5G ProSe Layer-2 Intermediate UE-to-Network Relay and 5G ProSe Layer-2 UE-to-Network Relay may be served by the same or different PLMNs. If the serving PLMNs of the 5G ProSe Layer-2 Remote UE, the 5G ProSe Layer-2 Intermediate UE-to-Network Relay and the 5G ProSe Layer-2 UE-to-Network Relay are different then NG-RAN is shared by the serving PLMNs, see the 5G MOCN architecture in clause 5.18 of TS 23.501 [4].
Figure 4.2.7.2a-1: 5G ProSe Multi-hop Layer-2 UE-to-Network Relay reference architecture
NOTE 1: Uu between the 5G ProSe Layer-2 Remote UE and NG-RAN is specified in TS 38.300 [12].
NOTE 2: The 5G ProSe Layer-2 Remote UE, the 5G ProSe Layer-2 Intermediate UE-to-Network Relay and the 5G ProSe Layer-2 UE-to-Network Relay are served by the same NG-RAN. The Core Network entities (e.g. AMF, SMF, UPF) serving the 5G ProSe Layer-2 Remote UE, the 5G ProSe Layer-2 Intermediate UE-to-Network Relay and the 5G ProSe Layer-2 UE-to-Network Relay can be the same or different.
NOTE 3: There may be one or two 5G ProSe Layer-2 Intermediate UE-to-Network Relays between the 5G ProSe Layer-2 Remote UE and the 5G ProSe Layer-2 UE-to-Network Relay.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.8 5G ProSe UE-to-UE Relay reference architecture
| Figure 4.2.8-1 shows the Layer-2 and Layer-3 5G ProSe UE-to-UE Relay reference architecture. The 5G ProSe End UEs communicate with each other via a 5G ProSe UE-to-UE Relay.
Figure 4.2.8-1: Reference architecture for 5G ProSe UE-to-UE Relay
Each 5G ProSe End UE and the 5G ProSe UE-to-UE Relay may have subscriptions from the same PLMN or different PLMNs.
4.2.8A 5G ProSe Multi-hop UE-to-UE Relay reference architecture
Figure 4.2.8A-1 shows the Layer-3 5G ProSe UE-to-UE Relay reference architecture. The 5G ProSe End UEs communicate with each other via a set of interconnected 5G ProSe Multi-hop UE-to-UE Relays.
Figure 4.2.8A-1: Reference architecture for Layer-3 5G ProSe Multi-hop UE-to-UE Relay
Based on capability and configuration the 5G ProSe UE can act as a 5G ProSe End UE, a 5G ProSe Multi-hop UE-to-UE Relay or both. Each 5G ProSe End UE and the 5G ProSe UE-to-UE Relay may have subscriptions from the same PLMN or different PLMNs.
- For IP PDU type, the 5G ProSe Multi-hop UE-to-UE Relays form a MANET network as defined in IETF RFC 7181 [35]. A 5G ProSe UE acting as 5G ProSe UE-to-UE Relay shall support the protocols defined in IETF RFC 7181 [35] and IETF RFC 6130 [36] on the PC5 interfaces towards other 5G ProSe Multi-hop UE-to-UE Relays. In addition, the 5G ProSe UE-to-UE Relay shall support a dedicated MANET Discovery Info message on the PC5 interfaces towards other 5G ProSe Multi-hop UE-to-UE Relays for propagation of DNS information, as described in clause 5.14.3.2.
NOTE: The MANET Discovery Info message will be specified in Stage 3.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.9 Support for 5G ProSe in NPNs
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.9.1 Support for 5G ProSe in SNPN
| The proximity based services defined in this specification are applicable to SNPN(s) with the following adaptations:
- The non-roaming architecture in clause 4.2.1 is applicable also to SNPN, whereby the term PLMN is replaced by subscribed SNPN.
- The roaming architecture in clause 4.2.2 is not supported.
- Inter-SNPN operation in clause 4.2.3 is not supported.
- For 5G ProSe Direct Discovery, the procedures in clauses 5.2 and 6, the network function services in clause 7 and the identifiers as specified in clause 5.8.1 are used with the following adaptations:
- The concept of Local PLMN for direct discovery is not supported.
- In the ProSe Application ID in clause 5.8.1.1 the value of PLMN ID within the ProSe Application ID shall be combined with a Network Identifier (NID) to identify an SNPN.
- The ProSe Application Code in clause 5.8.1.4 is extended to allow the value of PLMN ID within the ProSe Application Code to be combined with a Network Identifier (NID) to identify an SNPN.
- The Announcing PLMN ID in clause 5.8.1.11 is not used in the case of SNPNs.
- The Monitored PLMN ID in clause 5.8.1.17 is ignored in the case of SNPNs.
- In the 5G ProSe Direct Discovery with 5G DDNMF procedures as specified in clause 6.3.1, the term PLMN is to be replaced by SNPN, whereby PLMN IDs shall be combined with a Network Identifier (NID) to identify an SNPN, except if it pertains to PLMN IDs of VPLMNs or Local PLMNs or Announcing PLMN IDs. The term HPLMN is to be replaced by subscribed SNPN.
- The 5G ProSe UE-to-Network Relay reference architectures for 5G ProSe Layer-2 UE-to-Network relay (including Multi-hop), 5G ProSe Layer-3 UE-to-Network relay (including Multi-hop) and UE-to-UE relay (including Multi-hop) in clauses 4.2.7, 4.2.8 and 4.2.8A are supported. In clause 4.2.7.1 only the non-roaming architecture as specified for 5G ProSe Layer-3 UE-to-Network relay is supported for SNPNs and the PLMN A, PLMN B and PLMN C in clause 4.2.7 are the same in case of SNPNs and are replaced by the SNPN. The term PLMN is replaced by SNPN and the term HPLMN is replaced by subscribed SNPN. The term VPLMN is not applicable to SNPNs. For ProSe Multi-hop UE-to-Network relay in clauses 5.4.5 and 6.3.2.5, all 5G ProSe Intermediate UE-to-Network Relays, 5G ProSe Remote UEs and the 5G ProSe UE-to-Network Relays belong to the same SNPN.
- For Authorization and Provisioning and for the subscription information of the ProSe service in NPNs, the procedures and functionality as specified in clauses 5.1 and 5.7 and 6.2 are used with the following adaptations:
- The term PLMN is replaced by SNPN. The term HPLMN is replaced by subscribed SNPN. The term VPLMN is not applicable to SNPNs. Except the subscribed SNPN, no other SNPNs are authorized to perform the 5G ProSe service (i.e. 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay discovery, 5G ProSe UE-to-Network Relay communication, 5G ProSe UE-to-UE Relay discovery and 5G ProSe UE-to-UE Relay communication, including support for Multi-hop) over PC5 reference point.
- For 5G ProSe Layer-2 UE-to-Network relay operation, the procedures as specified in clauses 5.4.2, 5.4.4.2 and 5.4.5 and the identifiers as specified in clause 5.8.3 are used with the following adaptations:
- The term PLMN is replaced by SNPN.
- The 5G ProSe Layer-2 Remote UE has to operate in SNPN access mode, if it intends to access SNPN for ProSe via 5G ProSe Layer-2 UE-to-Network relay.
- The 5G ProSe UE-to-Network Relay and 5G ProSe Intermediate UE-to-Network Relay has to operate in SNPN access mode, if it intends to access SNPN for ProSe via 5G ProSe Layer-2 UE-to-Network relay.
- The 5G ProSe Layer-2 UE-to-Network relay may participate in the 5G ProSe UE-to-Network Relay Discovery procedure for emergency service if the serving NG-RAN broadcasts ims-EmergencySupport or imsEmergencySupportForSNPN in system information as specified in TS 38.300 [12] and TS 38.331 [16].
- The NCGI in clause 5.8.3.3 includes the Network identifier (NID) of the SNPN together with the PLMN ID in case the serving cell is operated by an SNPN.
- The 5G ProSe Layer-2 Remote UE only selects the 5G ProSe Layer-2 UE-to-Network Relay or 5G ProSe Intermediate UE-to-Network Relay for which the NCGI includes the subscribed SNPN of 5G ProSe Layer-2 Remote UE for non-emergency service.
NOTE 1: To prevent that unauthorized 5G ProSe Remote UEs can gain access to an NPN via 5G ProSe UE-to-Network Relay, the existing User Plane and/or Control Plane authorization verification procedures as specified in clauses 6.3.4 and 6.3.8 of TS 33.503 [29] and restricted 5G ProSe related discovery procedures as specified in clause 6.1.3 of TS 33.503 [29] are reused.
- For 5G ProSe Layer-3 UE-to-Network relay operation, the procedures as specified in clauses 5.4.1, 5.4.4.3, 5.4.5 and 6.5 and the identifiers as specified in clause 5.8.3 apply with the following adaptations:
- The term PLMN is replaced by SNPN. The term HPLMN is replaced by subscribed SNPN. The term VPLMN is not applicable to SNPNs.
- The 5G ProSe Layer-3 UE-to-Network relay has to operate in SNPN access mode in order to relay traffic to/from an SNPN for a 5G ProSe Layer-3 Remote UE.
- The 5G ProSe Layer-3 Remote UE has to operate in SNPN access mode in order to exchange traffic to/from an SNPN via a 5G ProSe Layer-3 UE-to-Network relay.
- The NCGI in clause 5.8.3.2 includes the Network identifier (NID) of the SNPN together with the PLMN ID in case the serving cell is operated by an SNPN.
- The TAI in clause 5.8.3.2 includes the Network identifier (NID) of the SNPN together with the PLMN ID in case the serving cell is operated by an SNPN.
NOTE 2: To prevent that unauthorized 5G ProSe Remote UEs can gain access to an NPN via 5G ProSe UE-to-Network Relay, the existing User Plane and/or Control Plane authorization verification procedures as specified in clauses 6.3.3 and 6.3.8 of TS 33.503 [29] and restricted 5G ProSe related discovery procedures as specified in clause 6.1.3 of TS 33.503 [29] are reused.
- The support for 5G ProSe for UEs in limited service state as specified in clause 5.9 applies whereby the term PLMN is replaced by an SNPN.
The SNPN onboarding procedure defined in clause 5.30.2.10 of TS 23.501 [4] via 5G ProSe UE-to-Network Relay is not supported.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.2.9.2 Support for 5G ProSe in conjunction with CAG in PNI-NPN
| In this Release, the CAG based access control is not applicable to the 5G ProSe Layer-3 UE-to-Network Remote UE accessing the network via 5G Layer-3 ProSe Relay.
NOTE 1: PNI-NPNs by means of one (or more) Network Slice instances or dedicated DNNs are supported for 5G Layer-3 ProSe UE-to-Network Relay.
The 5G ProSe Layer-2 UE-to-Network Relay procedures in conjunction with CAG for PNI-NPN are supported with the following adaptations:
- The 5G ProSe Layer-2 UE-to-Network relay may participate in the 5G ProSe UE-to-Network Relay Discovery procedure if the 5G ProSe Layer-2 UE-to-Network relay is accessing a CAG cell in the Allowed CAG list configured on the 5G ProSe Layer-2 UE-to-Network relay.
NOTE 2: 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay can access different CAG IDs.
NOTE 3: In order to prevent that unauthorized 5G ProSe Remote UEs can gain access to a CAG cell operated by a PNI-NPN which a 5G ProSe Layer-2 Remote UE is not allowed to access, the existing access control mechanisms as specified in clause 5.30.3.4 of TS 23.501 [4] and clause 16.7.4 of TS 38.300 [12] are reused.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3 Functional Entities
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.1 UE
| Any 5G ProSe-enabled UE may support the following functions:
- Exchange of information for 5G ProSe Direct Discovery between 5G ProSe-enabled UE and the 5G DDNMF over PC3a reference point.
- Procedures for 5G ProSe Direct Discovery of other 5G ProSe-enabled UEs over PC5 reference point.
- Procedures for 5G ProSe Direct Communication over PC5 reference point, including Broadcast, Groupcast and Unicast mode 5G ProSe Direct Communication.
- Procedures to act as a 5G ProSe Layer-2 UE-to-Network Relay.
- Procedures to act as a 5G ProSe Layer-3 UE-to-Network Relay.
- Procedures to act as a 5G ProSe Layer-2 Intermediate UE-to-Network Relay.
- Procedures to act as a 5G ProSe Layer-3 Intermediate UE-to-Network Relay.
- Procedures to act as a 5G ProSe Layer-2 Remote UE.
- Procedures to act as a 5G ProSe Layer-3 Remote UE.
- Procedures to act as a 5G ProSe Layer-2 UE-to-UE Relay.
- Procedures to act as a 5G ProSe Layer-3 UE-to-UE Relay.
- Procedures to act as a 5G ProSe Layer-2 End UE.
- Procedures to act as a 5G ProSe Layer-3 End UE.
- Procedures for communication path switching between PC5 and Uu reference points.
- Procedures for Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay.
- Indicating UE Policy Provisioning Request in UE Policy Container for UE triggered 5G ProSe Policy provisioning, which requests one or multiple types of policies/parameters as listed below:
- Policy/parameters for 5G ProSe Direct Discovery;
- Policy/parameters for 5G ProSe Direct Communication;
- Policy/parameters for 5G ProSe Layer-2 Remote UE;
- Policy/parameters for 5G ProSe Layer-3 Remote UE;
- Policy/parameters for 5G ProSe Layer-2 UE-to-Network Relay;
- Policy/parameters for 5G ProSe Layer-3 UE-to-Network Relay;
- Policy/parameters for 5G ProSe Layer-2 Intermediate UE-to-Network Relay;
- Policy/parameters for 5G ProSe Layer-3 Intermediate UE-to-Network Relay;
- Policy/parameters for 5G ProSe Layer-2 End UE;
- Policy/parameters for 5G ProSe Layer-3 End UE;
- Policy/parameters for 5G ProSe Layer-2 UE-to-UE Relay;
- Policy/parameters for 5G ProSe Layer-3 UE-to-UE Relay;
- Policy/parameters for 5G ProSe Multi-hop Layer-2 UE-to-Network Relay Discovery;
- Policy/parameters for 5G ProSe Multi-hop Layer-3 UE-to-Network Relay Discovery;
- Policy/parameters for 5G ProSe Multi-hop Layer-3 UE-to-UE Relay Discovery;
- Policy/parameters for 5G ProSe Communication via Multi-hop Layer-2 UE-to-Network Relay;
- Policy/parameters for 5G ProSe Communication via Multi-hop Layer-3 UE-to-Network Relay;
- Policy/parameters for 5G ProSe Communication via Multi-hop Layer-3 UE-to-UE Relay.
NOTE: Encoding of these policy bits is defined in TS 24.554 [23].
- Receiving the 5G ProSe Policy from 5GC over N1 reference point.
- Configuration of parameters for 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe Single-hop UE-to-Network Relay (e.g. including IP addresses, ProSe Layer-2 Group IDs, see clause 5.1), 5G ProSe Multi-hop UE-to-Network Relay, 5G ProSe Single-hop UE-to-UE Relay and 5G ProSe Multi-hop Layer-3 UE-to-UE Relay. These parameters can be pre-configured in the UE, or, if in coverage, provisioned or updated by signalling over the N1 reference point from the PCF in the HPLMN or over PC1 reference point from the ProSe Application Server.
- Reporting the following capabilities to 5GC over the N1 reference point:
- 5G ProSe Capability.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.2 5G DDNMF
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.2.1 General
| The 5G DDNMF is the logical function handling network related actions required for dynamic 5G ProSe Direct Discovery. In this version of the specification, it is assumed that there is only one logical 5G DDNMF in each PLMN that supports 5G ProSe Direct Discovery service.
NOTE: If multiple 5G DDNMFs are deployed within the same PLMN (e.g. for load reasons), the method to locate the 5G DDNMF that has allocated a specific ProSe Application Code or ProSe Restricted Code (e.g. through a database lookup, etc.) is not defined in this version of the specification.
The 5G DDNMF interacts with the 5G ProSe-enabled UE using procedures over PC3a reference point defined in clause 6.3.1 to allocate and resolve the mapping of ProSe Applications IDs and ProSe Application Codes used in 5G ProSe Direct Discovery. It uses ProSe related subscriber data stored in UDM for the authorisation of each discovery request. It also provides the UE with the necessary security material in order to protect discovery messages transmitted over the air. In restricted 5G ProSe Direct Discovery, it also interacts with the Application Server via Npc2 reference points or with other 5G DDNMFs via Npc6/Npc7 reference points for the authorization of the discovery requests.
The 5G ProSe-enabled UE use procedure defined in clause 4.3.2.2 to discovery the 5G DDNMF in the HPLMN. Based on the UE Local Configuration or URSP as defined in TS 23.503 [9], an existing PDU session is selected or a new PDU session is established, to carry the control signalling between the UE and the 5G DDNMF in the HPLMN.
The 5G DDNMF provides the necessary charging functionality or charging information for the usage of 5G ProSe Direct Discovery and/or ProSe Direct Communication to interact with CHF or for the provision to CEF.
The 5G DDNMF in the HPLMN may interact with the 5G DDNMF in a VPLMN or Local PLMN in order to manage the 5G ProSe Direct Discovery service.
The 5G DDNMF gets the address of the PCF for the UE from the BSF.
The 5G DDNMF gets the PDUID from the PCF and subscribes to notifications on Change of PDUID.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.2.2 5G DDNMF Discovery
| The 5G DDNMF of HPLMN is discovered through interaction with the Domain Name Service function. The UE may have the 5G DDNMF address in the Home PLMN (either as a FQDN or an IP address) pre-configured or provisioned as specified in clause 5.1.2.1. If it is not pre-configured or provisioned then the UE self-constructs the FQDN for it using e.g. the PLMN ID of the HPLMN.
The 5G DDNMF in the HPLMN uses the NRF to discovery other 5G DDNMFs in a VPLMN or local PLMN.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.3 PCF
| In addition to the functions defined in TS 23.501 [4] and TS 23.503 [9], the PCF includes functions to provision the UE with necessary policies and parameters to use 5G ProSe services, as part of the UE ProSe Policy information as defined in TS 23.503 [9] clause 4.2.2:
- PC5 usage reporting configuration.
- Authorization policy and parameters for 5G ProSe Direct Discovery and Communication.
- Authorization policy and parameters for 5G ProSe UE-to-Network Relay Discovery and Communication (i.e. as 5G ProSe Layer-2 Remote UE, as 5G ProSe Layer-3 Remote UE, as 5G ProSe Layer-2 UE-to-Network Relay, as 5G ProSe Layer-3 UE-to-Network Relay).
- PDUID allocation with its validity timer.
- Authorization policy and parameters for 5G ProSe UE-to-UE Relay Discovery and Communication.
- Authorization policy and parameters for 5G ProSe Multi-hop UE-to-Network Relay Discovery and Communication.
- Authorization policy and parameters for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay Discovery and Communication.
The PCF may update the 5G ProSe policy and parameters to the UE under certain conditions.
When receiving the 5G ProSe Capability in Npcf_UEPolicyControl_Create Request from the AMF or when receiving the updated subscription data from UDR, the PCF generates the PC5 QoS parameters used by NG-RAN corresponding to a UE as defined in clause 5.4.2 of TS 23.287 [2].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.4 AMF
| In addition to the functions defined in TS 23.501 [4], the AMF performs the following functions:
- Select a PCF supporting 5G ProSe Policy/Parameter provisioning based on indication of 5G ProSe Capability as part of the "5GMM capability" in the Registration Request.
- Store the 5G ProSe Capability.
- Forward the 5G ProSe Capability to PCF in Npcf_UEPolicyControl_Create Request.
- Obtain from UDM the subscription information related to 5G ProSe and store them as part of the UE context data.
- Obtain PC5 QoS parameters from the PCF and store them as part of the UE context data.
- Provision the NG-RAN with indication about the UE authorization status about the following:
- 5G ProSe Direct Discovery and 5G ProSe Direct Communication (i.e. as 5G ProSe-enabled UE for ProSe Direct Discovery, as 5G ProSe-enabled UE for ProSe Direct Communication);
- 5G ProSe UE-to-Network Relay Discovery and Communication (i.e. as 5G ProSe Layer-2 Remote UE, as 5G ProSe Layer-2 UE-to-Network Relay, as 5G ProSe Layer-3 UE-to-Network Relay);
- Multi-path communication via direct Uu path and via 5G ProSe Layer 2 UE-to-Network Relay as a 5G ProSe Layer-2 Remote UE;
- 5G ProSe UE-to-UE Relay Discovery and Communication (i.e. as 5G ProSe Layer-2 End UE, as 5G ProSe Layer-2 UE-to-UE Relay);
- 5G ProSe Layer-3 Multi-hop UE-to-Network Relay Discovery and Communication (i.e. as 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay;
- 5G ProSe Layer-2 Multi-hop UE-to-Network Relay Discovery and Communication (i.e. as 5G ProSe Layer-2 UE-to-Network Relay supporting 5G ProSe Layer-2 Multi-hop UE-to-Network Relay, as 5G ProSe Layer-2 Intermediate UE-to-Network Relay, as 5G ProSe Layer-2 Remote UE supporting 5G ProSe Layer-2 Multi-hop UE-to-Network Relay).
- Provision the NG-RAN with PC5 QoS parameters related to 5G ProSe Direct Communication.
- Optionally support security procedures over Control Plane for 5G ProSe UE-to-Network relaying as defined in TS 33.503 [29].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.5 UDM
| In addition to the functions defined in TS 23.501 [4], the UDM performs the following functions:
- Subscription management for 5G ProSe Direct Discovery and Communication.
- Subscription management for 5G ProSe UE-to-Network Relay Discovery and Communication.
- Subscription management for multi-path communication via direct Uu path and via 5G ProSe Layer 2 UE-to-Network Relay as a 5G ProSe Layer-2 Remote UE.
- Subscription management for 5G ProSe UE-to-UE Relay Discovery and Communication.
- Subscription management for 5G ProSe Multi-hop UE-to-Network Relay Discovery and Communication.
- Subscription management for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay Discovery and Communication.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.6 UDR
| In addition to the functions defined in TS 23.501 [4], the UDR performs the following functions:
- Stores a path preference for ProSe services provided by the AF.
- Stores ProSe service parameters.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.7 NRF
| In addition to the functions defined in TS 23.501 [4], the NRF performs the following functions:
- PCF discovery by considering 5G ProSe Capability.
- 5G DDNMF Discovery.
Similar procedure can be used for 5G DDNMF discovery across PLMNs as specified in clause 4.17.5 of TS 23.502 [5] with the difference as below:
- The serving PLMN is replaced by home PLMN and home PLMN is replaced by local PLMN or serving PLMN.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.8 ProSe Application Server
| The ProSe Application Server supports the following functionalities.
For 5G ProSe Direct Discovery:
- Maintains permission information for the restricted 5G ProSe Direct Discovery using RPAUIDs;
- Storage of ProSe Discovery UE IDs and metadata;
- Mapping of RPAUID and PDUID for restricted 5G ProSe Direct Discovery;
- Provisioning parameters for Group Member Discovery to UE.
- Interaction with 5G DDNMF for 5G ProSe Direct Discovery, including:
- Allocation of the ProSe Restricted Code Suffix pool, if restricted Direct Discovery with application-controlled extension is used;
- Allocation of the mask(s) for ProSe Restricted Code Suffix, if restricted Direct Discovery with application-controlled extension is used;
- Allocation of the ProSe Application Code Suffix pool, if open Direct Discovery with application-controlled extension is used;
- Allocation of the mask(s) for ProSe Application Code Suffix, if open Direct Discovery with application-controlled extension is used.
For 5G ProSe Direct Communication:
- Provisioning a path preference for 5G ProSe Services to UDR;
- Provisioning parameters for 5G ProSe Direct Communication to UE.
For 5G ProSe UE-to-Network Relay service:
- Provisioning parameters for 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-Network Relay Communication to UDR.
For 5G ProSe UE-to-UE Relay service:
- Provisioning parameters for 5G ProSe UE-to-UE Relay Discovery and 5G ProSe UE-to-UE Relay Communication to UDR.
For 5G ProSe Multi-hop UE-to-Network Relay service:
- Provisioning parameters for 5G ProSe Multi-hop UE-to-Network Relay Discovery and 5G ProSe Multi-hop UE-to-Network Relay Communication to UDR.
For 5G ProSe Layer-3 Multi-hop UE-to-UE Relay service:
- Provisioning parameters for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay Discovery and 5G ProSe Layer-3 Multi-hop UE-to-UE Relay Communication to UDR.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.9 5G ProSe UE-to-Network Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.9.1 General
| Both 5G ProSe Layer-2 and Layer-3 UE-to-Network Relay entity provides the relaying functionality to support connectivity to the network for 5G ProSe Remote UEs. It can be used for both public safety services and commercial services (e.g. interactive service).
Both 5G ProSe Layer-2 and Layer-3 UE-to-Network Relay supports the following functions to enable connectivity to the network:
- 5G ProSe UE-to-Network Relay Discovery service as defined in clause 6.3.2.3, to allow discovery by the 5G ProSe Remote UE;
- access the 5GS as a UE as defined in TS 23.501 [4] with the enhancements as specified in clauses 6.2 and 6.6;
- relays unicast traffic (uplink and downlink) between the 5G ProSe Remote UE and the network, supporting IP, Ethernet or Unstructured traffic type.
NOTE: Relaying MBS traffic to a 5G ProSe Remote UE by a 5G ProSe UE-to-Network Relay is not supported in this release of the specification.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.9.2 5G ProSe Layer-3 UE-to-Network Relay
| In addition to the common 5G ProSe UE-to-Network Relay functions defined in clause 4.3.9.1, 5G ProSe Layer-3 UE-to-Network Relay supports the following functions to enable connectivity to the network:
- 5G ProSe Direct Communication via 5G ProSe Layer-3 UE-to-Network Relay as specified in clause 6.5.1, for the communication with the 5G ProSe Layer-3 Remote UEs for the relay operations;
- end-to-end QoS treatment for the 5G ProSe Layer-3 Remote UE's traffic without N3IWF as defined in clause 5.6.2.1 and when accessing via an N3IWF as defined in clause 5.6.2.2;
- IP address management for the 5G ProSe Layer-3 Remote UE as defined in clause 5.5.1.3 in case the 5G ProSe Layer-3 Remote UE uses IP traffic type.
- Emergency PDU Session establishment for 5G ProSe Layer-3 Remote UE via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF support.
NOTE: For emergency service via N3IWF, see clause 5.4.4.3.
If 5G ProSe Multi-hop UE-to-Network Relay is supported, a 5G ProSe Layer-3 UE-to-Network Relay supports the following functions:
- 5G ProSe Multi-hop UE-to-Network Relay Discovery.
- 5G ProSe Communication via Multi-hop UE-to-Network Relay as defined in clause 6.5.1.4.
- Relay unicast traffic originating from the 5G ProSe Remote UE and received from a 5G ProSe Intermediate UE-to-Network Relay to the network supporting IP, Ethernet or Unstructured traffic type.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.9.3 5G ProSe Layer-2 UE-to-Network Relay
| In addition to the common 5G ProSe UE-to-Network Relay functions defined in clause 4.3.9.1, 5G ProSe Layer-2 UE-to-Network Relay supports the following functions to enable connectivity to the network:
- 5G ProSe Direct Communication via 5G ProSe Layer-2 UE-to-Network Relay as specified in clause 6.5.2, for the communication with the 5G ProSe Layer-2 Remote UEs for the relay operations;
- QoS handling for 5G ProSe Layer-2 UE-to-Network Relay and end-to-end QoS treatment as defined in clause 5.6.2.3.
- For a 5G ProSe Layer-2 UE-to-Network Relay to participate in the 5G ProSe UE-to-Network Relay Discovery procedure for emergency service (i.e. sending the UE-to-Network Relay Discovery Announcement message or UE-to-Network Relay Discovery Response message), the serving NG-RAN support of emergency services is required as the Layer-2 Remote UE may select a different PLMN from the Layer-2 Relay.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.10 SMF
| In addition to the functions defined in TS 23.501 [4], the SMF supports the following function:
- Receiving 5G ProSe Layer-3 Remote UE report and maintaining the information of 5G ProSe Layer-3 Remote UE(s) handled by a 5G ProSe Layer-3 UE-to-Network Relay in the 5G ProSe Layer-3 UE-to-Network Relay's SM context for the PDU Session associated with the relay.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.11 NEF
| In addition to the functions defined in TS 23.501 [4], the NEF supports the following:
- To enable AFs to provide service specific information to the 3GPP network, the NEF supports additional service parameters for ProSe policy as specified in clause 6.2.5.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.12 5G ProSe UE-to-UE Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.12.1 General
| Both 5G ProSe Layer-2 and Layer-3 UE-to-UE Relay provides the relaying functionality to support connectivity between 5G ProSe End UEs. 5G ProSe UE-to-UE Relay can be used for both public safety services and commercial services (e.g. interactive service).
Both 5G ProSe Layer-2 and Layer-3 UE-to-UE Relay supports the following functions to enable connectivity between 5G ProSe End UEs:
- 5G ProSe UE-to-UE Relay Discovery service as defined in clause 6.3.2.4, to allow discovery by the 5G ProSe End UE;
- 5G ProSe Discovery integrated into PC5 unicast link establishment as specified in clause 6.7.3;
- Access 5GS as a UE as defined in TS 23.501 [4] with the enhancements as specified in clauses 6.2;
- Relay unicast traffic between the 5G ProSe End UEs directly in the case of 5G ProSe Single-hop UE-to UE Relay, or via one or more Layer-3 UE-to-UE Relays in the case of 5G ProSe Multi-hop Layer-3 UE-to-UE Relay, supporting IP, Ethernet or Unstructured traffic type.
NOTE: Relaying groupcast and broadcast traffic to a 5G ProSe End UE by a 5G ProSe UE-to-UE Relay is not supported in this release of the specification.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.12.2 5G ProSe Layer-3 UE-to-UE Relay
| In addition to the common 5G ProSe UE-to-UE Relay functionality defined in clause 4.3.12.1, a 5G ProSe Layer-3 UE-to-UE Relay supports the following functions:
- 5G ProSe Direct Communication via 5G ProSe Layer-3 UE-to-UE Relay as specified in clause 6.7.1, for the communication between 5G ProSe Layer-3 End UEs for relay operations;
- QoS handling and end-to-end QoS treatment for the 5G ProSe Layer-3 End UE's traffic as defined in clause 5.6.3.1;
- IP address management for the 5G ProSe Layer-3 End UE as defined in clause 5.5.1.4 when the 5G ProSe Layer-3 End UE uses IP traffic type;
- 5G ProSe UE-to-UE Relay reselection as specified in clause 6.7.4.3.
If 5G ProSe Multi-hop UE-to-UE Relay is supported, a 5G ProSe Layer-3 UE-to-UE Relay supports the following functions:
- 5G ProSe Multi-hop UE-to-UE Relay Discovery service;
- 5G ProSe Communication via Multi-hop UE-to-UE Relay as defined in clause 6.7.5;
- Relay unicast traffic between the 5G ProSe End UEs via one or more Layer-3 UE-to-UE Relays, supporting IP, Ethernet or Unstructured traffic type;
- For IP PDU type MANET based routing protocols are used to provide multi-hop forwarding functionality. The MANET routing protocols to be supported, i.e. Neighborhood Discovery Protocol (NHDP) [36] and OLSRv2 [35], are associated with the RSCs based on configuration;
- For non-IP (Ethernet or Unstructured) PDU type with multi-hop support the Relay discovery procedures as defined in clause 6.3.2.6.3.1 (Model A) and clause 6.3.2.6.3.2 (Model B), the Layer-2 link establishment and management procedures as defined in clause 6.4.3.10.2 and the Communication procedure as defined in clause 6.7.5.2.2.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.12.3 5G ProSe Layer-2 UE-to-UE Relay
| In addition to the common 5G ProSe UE-to-UE Relay functions defined in clause 4.3.12.1, 5G ProSe Layer-2 UE-to-UE Relay supports the following functions:
- 5G ProSe Direct Communication via 5G ProSe Layer-2 UE-to-UE Relay as specified in clause 6.7.2, for the communication between 5G ProSe Layer-2 End UEs for relay operations;
- QoS handling and end-to-end QoS treatment for 5G ProSe Layer-2 End UE's traffic as defined in clause 5.6.3.2;
- 5G ProSe UE-to-UE Relay reselection as specified in clause 6.7.4.2.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 4.3.13 5G ProSe Intermediate UE-to-Network Relay
| The 5G ProSe Intermediate UE-to-Network Relay entity provides the relaying functionality to support multi-hop connectivity between the 5G ProSe Remote UEs and the 5G ProSe UE-to-Network Relay. It can be used for both public safety services and commercial services (e.g. interactive service). There can be more than one 5G ProSe Intermediate UE-to-Network Relay connecting the 5G ProSe Remote UEs and the 5G ProSe UE-to-Network Relay.
The 5G ProSe Intermediate UE-to-Network Relay supports the following functions to enable connectivity between the 5G ProSe Remote UEs and the 5G ProSe UE-to-Network Relay:
- 5G ProSe Multi-hop UE-to-Network Relay Discovery service to allow discovery by the 5G ProSe Remote UE as defined in clause 6.3.2.5.
- Access the 5GS as a UE as defined in TS 23.501 [4].
- Relays unicast traffic (uplink and downlink) between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay directly or via other 5G ProSe Intermediate UE-to-Network Relay(s), supporting IP, Ethernet or Unstructured traffic type.
- 5G ProSe Multi-hop Communication via 5G ProSe Layer-3 UE-to-Network Relay as specified in clause 6.5.1.4;
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5 High level functionality and features
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1 Authorization and Provisioning for ProSe service
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.1 General
| In 5GS, the parameters for 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay, 5G ProSe UE-to-UE Relay, 5G ProSe Multi-hop UE-to-Network Relay and 5G ProSe Layer-3 Multi-hop UE-to-UE Relay services may be made available to the UE in following ways:
- provisioned in the ME; or
- configured in the UICC; or
- provisioned in the ME and configured in the UICC; or
- provided or updated by the ProSe Application Server via PCF and/or PC1 reference point; or
- provided or updated by the PCF to the UE.
If the same parameters described in clauses 5.1.2.1, 5.1.3.1, 5.1.4.1 and 5.1.5.1 are provided by different sources, the UE shall consider them in the following priority order:
- provided or updated by the PCF (including parameters determined by the PCF itself and parameters provided by the ProSe Application Server to the PCF as specified in clause 6.2.5);
- provided or updated by the ProSe Application Server via PC1 reference point;
- configured in the UICC;
- provisioned in the ME.
The parameters provided or updated by the ProSe Application Server via PC1 reference point may need to be complemented with configuration data from other sources listed above.
NOTE: The ProSe Application Server can provision the same ProSe parameters via 5GC as specified in clause 6.2.5 or directly to the UE via PC1 reference point and can revoke (e.g. delete) the ProSe parameters via 5GC as specified in clause 6.2.5 in order for the provisioning via PC1 reference point to take effect.
The basic principles of service authorization and provisioning for 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay, 5G ProSe UE-to-UE Relay, 5G ProSe Multi-hop UE-to-Network Relay and 5G ProSe Layer-3 Multi-hop UE-to-UE Relay services are as follows:
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorized to use 5G ProSe Direct Discovery.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to use 5G ProSe Direct Communication.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe UE-to-Network Relay. Authorisation for 5G ProSe Layer-2 UE-to-Network Relay and 5G ProSe Layer-3 UE-to-Network Relay are independent of each other.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to access 5GC via 5G ProSe UE-to-Network Relay (i.e. to act as 5G ProSe Remote UE). Authorisation to access via 5G ProSe Layer-2 UE-to-Network Relay and via 5G ProSe Layer-3 UE-to-Network Relay are independent of each other.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe UE-to-UE Relay. Authorisation for 5G ProSe Layer-2 UE-to-UE Relay and 5G ProSe Layer-3 UE-to-UE Relay are independent of each other.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to access 5G ProSe UE-to-UE Relay (i.e. to act as 5G ProSe End UE). Authorisation to access via 5G ProSe Layer-2 UE-to-UE Relay and via 5G ProSe Layer-3 UE-to-UE Relay are independent of each other.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe Multi-hop UE-to-Network Relay. Authorisation for 5G ProSe Multi-hop Layer-2 UE-to-Network Relay and 5G ProSe Multi-hop Layer-3 UE-to-Network Relay are independent of each other.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe Multi-hop Remote UE supporting 5G ProSe Multi-hop UE-to-Network Relay. Authorisation for 5G ProSe Multi-hop Layer-2 Remote UE and 5G ProSe Multi-hop Layer-3 Remote UE are independent of each other.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe Layer-2 Multi-hop Intermediate UE-to-Network Relay and 5G ProSe Layer-3 Multi-hop Intermediate UE-to-Network Relay.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay.
- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe Layer-3 End UE supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay.
- The PCF in the HPLMN merges authorization information from home and other PLMNs and provides the UE with the final authorization information.
- The PCF in the VPLMN or HPLMN may revoke the authorization (via H-PCF when roaming) at any time by using the UE Configuration Update procedure for transparent UE Policy delivery procedure defined in clause 4.2.4.3 of TS 23.502 [5].
- The ProSe Policy/parameters provisioning to UE is controlled by the PCF and may be triggered by UE. The PCF provisions one or more of the following ProSe Policy/parameters:
- ProSe Policy/parameters for 5G ProSe Direct Discovery as specified in clause 5.1.2.1;
- ProSe Policy/parameters for 5G ProSe Direct Communications as specified in clause 5.1.3.1;
- ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 UE-to-Network Relay as specified in clause 5.1.4.1;
- ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 Remote UE as specified in clause 5.1.4.1.
- ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 UE-to-UE Relay as specified in clause 5.1.5.1.
- ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 End UE as specified in clause 5.1.5.1.
- ProSe Policy/parameters for 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-2 and/or Layer-3 Multi-hop UE-to-Network Relay as specified in clause 5.1.4.1a.
- ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 Multi-hop Remote UE supporting 5G ProSe Multi-hop UE-to-Network Relay as specified in clause 5.1.4.1a.
- ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 Multi-hop Intermediate UE-to-Network Relay as specified in clause 5.1.4.1a.
- ProSe Policy/parameters for 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay as specified in clause 5.1.5.1a.
- ProSe Policy/parameters for 5G ProSe Layer-3 End UE supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay as specified in clause 5.1.5.1a.
- The PCF includes the 5G ProSe Policy/parameters in a Policy Section identified by a Policy Section Identifier (PSI) as specified in clause 6.1.2.2.2 of TS 23.503 [9].
In addition to the above, ProSe usage reporting configuration and rules for charging can be (pre)configured in the UE or provided by the PCF.
In addition to the above, the path selection policy can be (pre)configured in the UE or provided by the PCF as defined in clause 5.11. A path preference for ProSe Services can be provided by ProSe Application Server to UDR and may be used by PCF for path selection policy generation and update.
When a 5G ProSe Layer-3 Remote UE is using a 5G ProSe Layer-3 UE-to-Network Relay without involving N3IWF, the PCF based provisioning and update of 5G ProSe Policy/parameters to the 5G ProSe Layer-3 Remote UE are not supported.
5.1.1a General principles for applying policy/parameters
For services (i.e. 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay discovery, 5G ProSe UE-to-Network Relay communication, 5G ProSe UE-to-UE Relay discovery, 5G ProSe UE-to-UE Relay communication, 5G ProSe Multi-hop UE-to-Network Relay discovery, 5G ProSe Multi-hop UE-to-Network Relay communication, 5G ProSe Layer-3 Multi-hop UE-to-UE Relay discovery and 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication) over PC5 reference point, the operator may pre-configure the UEs with the required provisioning parameters for the service, without the need for the UEs to connect to the 5GC to get this initial configuration. The following apply:
- The provisioning parameters for the service could be from different sources and their priorities are described in clause 5.1.1.
- The ME provisioning parameters shall not be erased when a USIM is deselected or replaced.
- The UE shall use radio resources for the service as follows:
- While a UE has a serving cell and is camped on a cell and the UE intends to use for 5G ProSe the radio resources (i.e. carrier frequency) operated by this cell, then the UE shall use the radio resource description indicated by this cell the UE is camped on and ignore any radio resource description of the same radio resource provisioned in the ME or the UICC. If the cell does not provide radio resources for ProSe, the UE shall not perform ProSe message transmission and reception on radio resources operated by this cell. The UE is allowed to perform the service with another UE not served by the same PLMN;
- If the UE intends to use "operator-managed" radio resources (i.e. carrier frequency) for 5G ProSe that are not operated by the UE's serving cell, as specified in the related Policy/Parameter provisioning, or if the UE is out of coverage, the UE shall search for a cell in any PLMN that is operating the provisioned radio resources (i.e. carrier frequency) as defined in TS 38.300 [12] and TS 38.304 [13]; and:
- If the UE finds such a cell in the registered PLMN or a PLMN equivalent to the registered PLMN and authorization for the service to this PLMN is confirmed, the UE shall use the radio resource description indicated by that cell. If that cell does not provide radio resources for ProSe, the UE shall not perform ProSe message transmission and reception on those radio resources;
- If the UE finds such a cell but not in the registered PLMN or a PLMN equivalent to the registered PLMN and that cell belongs to a PLMN authorized for the service and provides radio resources for ProSe then the UE shall perform PLMN selection triggered by the service as defined in TS 23.122 [14];
- If the UE finds such cell but not in a PLMN authorized for the service the UE shall not use the service;
- If the UE does not find any such cell in any PLMN, then the UE shall consider itself "not served by NG-RAN" and use radio resources provisioned in the ME or the UICC. If no such provision exists in the ME or the UICC or the provision does not authorize the service, then the UE is not authorized to transmit;
- The UE is allowed to use "operator-managed" radio resources (i.e. carrier frequency) provisioned in the ME or the UICC for the service if the UICC indicates it is authorized;
- If the UE intends to use "non-operator-managed" radio resources (i.e. carrier frequency) for 5G ProSe, according to TS 36.331 [15] or TS 38.331 [16] and as specified in clause 5.1.2.1, then the UE shall perform the service using resource provisioned in the ME or the UICC. If no such provision exists in the ME or the UICC or the provision does not authorize the service, then the UE is not authorized to transmit;
NOTE 1: It is possible for operators to configure UEs (e.g. Public Safety UEs) to use only "operator-managed" radio resources (i.e. carrier frequency) for the service when the UE is "not served by NG-RAN".
- The UE provisioning shall support setting Geographical Areas;
NOTE 2: It is possible for a UE to use other radio resources for 5G ProSe based on the Geographical Area instead of those operated by the serving NG-RAN cell, when provisioned in the UE, even if the UE's serving cell offers normal service and the SIBs for NR Sidelink communication defined in TS 38.331 [16] indicates that the service (the service) is available. This is to cover the scenario when e.g. the radio resources used for the service are not owned by the serving network of the UE.
NOTE 3: When cross-carrier operation is supported, according to TS 36.331 [15] or TS 38.331 [16], a UE can be instructed by its serving cell to perform the service over a different carrier frequency. The UE is still considered as "served by NG-RAN" in this case.
NOTE 4: The scenario that a cell is detected and the cell does not provide support for the service when the UE attempts to use a carrier frequency configured for the service, is considered a configuration error. Therefore, the UE does not transmit on that frequency to avoid interference to the network.
- The service is only specified for NR.
NOTE 5: It is out of scope of the present specification to define how the UE can locate itself in a specific Geographical Area. When the UE is in coverage of a 3GPP RAT, it can for example, use information derived from the serving PLMN. When the UE is not in coverage of a 3GPP RAT, it can use other techniques, e.g. Global Navigation Satellite System (GNSS). User provided location is not a valid input.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.2 Authorization and Provisioning for 5G ProSe Direct Discovery
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.2.1 Policy/Parameter provisioning for 5G ProSe Direct Discovery
| The following sets of information for 5G ProSe Direct Discovery over PC5 reference point is provisioned to the UE:
1) Authorization policy for 5G ProSe Direct Discovery:
- When the UE is "served by NG-RAN":
- For open 5G ProSe Direct Discovery:
a) open 5G ProSe Direct Discovery Model A monitoring authorization policy:
- PLMNs in which the UE is authorised to perform 5G ProSe Direct Discovery monitoring.
b) open 5G ProSe Direct Discovery Model A announcing authorization policy:
- PLMNs in which the UE is authorized to perform announcing.
- For restricted 5G ProSe Direct Discovery:
a) restricted 5G ProSe Direct Discovery Model A monitoring authorization policy:
- PLMNs in which the UE is authorised to perform restricted 5G ProSe Direct Discovery Model A monitoring.
b) restricted 5G ProSe Direct Discovery Model A announcing authorization policy:
- PLMNs in which the UE is authorized to perform restricted 5G ProSe Direct Discovery Model A announcing.
c) restricted 5G ProSe Direct Discovery Model B Discoverer operation authorization policy:
- PLMNs in which the UE is authorized to perform Model B Discoverer operation.
d) restricted 5G ProSe Direct Discovery Model B Discoveree operation authorization policy:
- PLMNs in which the UE is authorized to perform Model B Discoveree operation.
NOTE 1: In this specification, [When the UE is "served by NG-RAN"] and [When the UE is "not served by NG-RAN"] have similar meaning as in "served by E-UTRAN" and "not served by E-UTRAN" in TS 23.303 [3], but applied to 5G ProSe Direct discovery/communications over NR PC5 reference point.
- When the UE is "not served by NG-RAN":
- Indicates whether the UE is authorized to perform 5G ProSe Direct Discovery for Model A and Model B when "not served by NG-RAN".
NOTE 2: If both Model A and Model B are authorized for 5G ProSe Direct Discovery, it is up to UE and application implementation to select a discovery model or perform both models simultaneously.
2) Parameters used for 5G ProSe Direct Discovery:
- The mapping of ProSe services (i.e. ProSe identifiers) to Destination Layer-2 ID(s) for sending/receiving initial signalling of discovery messages.
NOTE 3: The same Destination Layer-2 ID for 5G ProSe Direct Discovery can be mapped to more than one ProSe services.
NOTE 4: The values provisioned for the Destination Layer-2 ID(s) for 5G ProSe Direct Discovery, for Destination Layer-2 ID(s) for 5G ProSe Direct Communication, defined in clause 5.1.3.1, for Destination Layer-2 ID(s) for 5G ProSe UE-to-Network Relay Discovery defined in clause 5.1.4.1 and for Destination Layer-2 ID(s) for 5G ProSe UE-to-UE Relay Discovery defined in clause 5.1.5.1, are different from each other.
NOTE 5: A "catch all" entry with the lowest priority can be used for the ProSe services that do not have explicit mapping to the Destination Layer-2 ID(s) for sending/receiving initial signalling of discovery messages.
- Application identifiers to be used for 5G ProSe Direct Discovery over PC5 interface.
NOTE 6: The Security parameters for 5G ProSe Direct Discovery can be provisioned by 5G DDNMF as defined in TS 33.503 [29].
3) Radio parameters when the UE is "not served by NG-RAN":
- Includes the radio parameters per NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 7: Whether a frequency band is "operator managed" or "non-operator managed" in a given Geographical Area is defined by local regulations.
- Default PC5 DRX configuration (see TS 38.331 [16]).
NOTE 8: Radio parameters for 5G ProSe UE-to-UE Relay Discovery when the UE is not "served by NG-RAN" in clause 5.1.5.2.1 and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Discovery are expected to be aligned for direct and relayed discovery for UE to UE communication.
4) Restricted ProSe Discovery UE ID for Restricted Direct Discovery:
- ProSe Discovery UE ID.
5) Group Member Discovery parameters:
- For each discovery group that the UE belongs to include the following parameters that enable the UE to perform Group Member Discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- Application Layer Group ID: Identifies an application layer group or a discovery group that the UE belongs to;
- Layer-2 Group ID: layer-2 ID for Application Layer Group ID;
- User Info ID: For Model A, this corresponds to the Announcer Info parameter when the UE is acting as an announcing UE. For Model B, this corresponds to the Discoverer Info in Solicitation messages and the Discoveree Info in Response messages, when the UE is acting as a discoverer or discoveree UE respectively.
NOTE 9: User Info ID is expected to be assigned uniquely to a user within the discovery group.
6) Optionally, the 5G DDNMF address (either FQDN or IP address) in the Home PLMN.
7) Validity timer indicating the expiration time of the Policy/Parameter for 5G ProSe Direct Discovery.
The above parameter sets bullet 2), bullet 3), bullet 5) and bullet 7) may be provided or updated to the UE by the ProSe Application Server, except for the Security parameters in bullet 2).
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.2.2 Principles for applying parameters for 5G ProSe Direct Discovery
| The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe Direct Discovery service.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.3 Authorization and Provisioning for 5G ProSe Direct Communication
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.3.1 Policy/Parameter provisioning for 5G ProSe Direct Communication
| The following sets of information for 5G ProSe Direct Communications over PC5 reference point is provisioned to the UE:
1) Authorization policy:
- When the UE is "served by NG-RAN":
- PLMNs in which the UE is authorized to perform 5G ProSe Direct Communications over PC5 reference point when "served by NG-RAN".
- When the UE is "not served by NG-RAN":
- Indicates whether the UE is authorized to perform 5G ProSe Direct Communications over PC5 reference point when "not served by NG-RAN".
NOTE 1: In this specification, [When the UE is "served by NG-RAN"] and [When the UE is "not served by NG-RAN"] are relevant to 5G ProSe Direct Communications over NR PC5 reference point.
2) Groupcast mode 5G ProSe Direct Communication policy/parameters:
- For each application layer group supported include the parameters that enable the UE to perform Groupcast mode 5G ProSe Direct Communication when provided by PCF or provisioned in the ME or configured in the UICC:
- Application Layer Group ID: Identifies an application layer group that the UE belongs to.
- ProSe Layer-2 Group ID: Destination Layer-2 ID applicable only when the Application Layer Group ID is provided by the application layer
- ProSe Group IP multicast address
NOTE 2: For MANET multicast routing message delivery, the IP multicast address is set as defined in RFC 5498 [39] and not included in the configuration.
- Indication whether the UE should use IPv4 or IPv6 for that group
- For a specific Group configured to operate using IPv4, optionally an IPv4 address to be used by the UE as a source address. If none is provisioned, then the UE shall use Dynamic Configuration of IPv4 Link-Local Addresses RFC 3927 [18] to obtain a link local address for the Group.
3) Radio parameters when the UE is "not served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform ProSe Direct Communications over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 3: Whether a frequency band is "operator managed" or "non-operator managed" in a given Geographical Area is defined by local regulations.
NOTE 4: Radio parameters for 5G ProSe Direct Communication when the UE is not "served by NG-RAN" in clause 5.1.5.2.1 and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe UE-to-UE Relay communication are expected to be aligned for direct and relayed UE to UE communication.
4) Policy/parameters related to privacy:
- The list of ProSe services (i.e. ProSe identifiers) with Geographical Area(s) that require privacy support.
- A privacy timer value indicating the duration after which the UE shall change each source Layer-2 ID self-assigned by the UE when privacy is required.
5) Policy/parameters when NR PC5 is selected:
- The mapping of ProSe services (i.e. ProSe identifiers) to radio frequencies with Geographical Area(s).
- The mapping of ProSe services (i.e. ProSe identifiers) to Destination Layer-2 ID(s) for broadcast.
- The mapping of ProSe services (i.e. ProSe identifiers) to Destination Layer-2 ID(s) for groupcast.
- The mapping of ProSe services (i.e. ProSe identifiers) to default Destination Layer-2 ID(s) for initial signalling to establish unicast connection.
NOTE 5: The same default Destination Layer-2 ID for unicast initial signalling can be mapped to more than one ProSe service. In the case where different ProSe services are mapped to distinct default Destination Layer-2 IDs, when the UE intends to establish a single unicast link that can be used for more than one ProSe service, the UE can select any of the default Destination Layer-2 IDs to use for the initial signalling.
NOTE 6: Security policies for Unicast mode 5G ProSe Direct Communication can be provisioned by PCF as defined in TS 33.503 [29].
- The mapping of ProSe services (i.e. ProSe identifiers) to PC5 QoS parameters defined in clause 5.6.1 (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.).
- The mapping of ProSe services (i.e. ProSe identifiers) to the corresponding NR Tx Profiles for broadcast and groupcast (see TS 38.300 [12] and TS 38.331 [16] for further information).
NOTE 7: A "catch all" entry with the lowest priority in each above mapping can be used for the ProSe services that do not have explicit policy/parameters mapping above.
- AS layer configurations (see TS 38.331 [16]), i.e. the mapping of PC5 QoS profile(s) to radio bearer(s), when the UE is "not served by NG-RAN".
- The PC5 QoS profile contains PC5 QoS parameters described in clause 5.4.2 of TS 23.287 [2] and value for the QoS characteristics regarding Priority Level, Averaging Window, Maximum Data Burst Volume if default value is not used as defined in Table 5.4.4-1 of TS 23.287 [2] and in Table 5.6.1-1.
- For broadcast, groupcast and initial signalling to establish unicast connection, PC5 DRX configuration (see TS 38.331 [16]), e.g. the mapping of PC5 QoS profile(s) to PC5 DRX cycle(s), default PC5 DRX configuration, when the UE is "not served by NG-RAN".
6) Path selection policy:
- The mapping of ProSe services (i.e. ProSe identifiers) to path preference (i.e. PC5 preferred, Uu preferred, or no preference) as defined in clause 5.11.
NOTE 8: The path selection policy can be a one mapping for all ProSe services, i.e. same path preference for all ProSe services.
7) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Direct Communication.
The above parameter sets from bullet 2) to 7) may be provided or updated to the UE by the ProSe Application Server.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.3.2 Principles for applying parameters for 5G ProSe Direct Communication
| The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe Direct Communication service.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.4 Authorization and Provisioning for 5G ProSe UE-to-Network Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.4.1 Policy/Parameter provisioning for 5G ProSe UE-to-Network Relay
| The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe UE-to-Network Relay:
1) Authorisation policy for acting as a 5G ProSe Layer-3 and/or Layer-2 UE-to-Network Relay when "served by NG-RAN":
- PLMNs in which the UE is authorized to relay traffic for 5G ProSe Layer-3 and/or Layer-2 Remote UEs.
The authorisation for a UE to act as a 5G ProSe UE-to-Network Relay also authorizes the use of 5G ProSe UE-to-Network Relay Discovery with Model A and Model B.
NOTE 1: It is up to UE and application implementation to select a discovery model or whether to perform both models simultaneously.
2) ProSe Relay Discovery policy/parameters for 5G ProSe UE-to-Network Relay:
- Includes the parameters that enable the UE to perform 5G ProSe UE-to-Network Relay Discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe UE-to-Network Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-Network Relay Layer Indicator per RSC, optional Control Plane Security Indicator per RSC). The UE-to-Network Relay Layer Indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service. If the Control Plane Security Indicator is provided for a RSC, then the Control Plane based security procedure as described in clause 5.1.4.3.2 is performed for UE-to-Network Relay Communication for that RSC, otherwise if it is not provided for a RSC, then the User Plane based security procedure as described in clause 5.1.4.3.3 is performed for that RSC. RSC dedicated for emergency service may also be provisioned.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Announcement and Relay Discovery Additional Information messages and receiving Relay Discovery Solicitation messages;
- For 5G ProSe Layer-3 UE-to-Network Relay, the PDU Session parameters (PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference) to be used for the relayed traffic for each ProSe Relay Service Code;
- Includes security related content for 5G ProSe UE-to-Network Relay, see TS 33.503 [29].
NOTE 2: 5G ProSe Relay Discovery policy/parameters can be provided from ProSe Application Server to the 5G ProSe UE-to-Network Relay, except for the Security parameters in bullet 2).
3) For 5G ProSe Layer-3 UE-to-Network Relay, QoS mapping(s):
- Each QoS mapping entry includes:
- a mapping between a 5QI value and a PQI value;
- a PQI PDB adjustment factor, for the PC5 communication for the 5G ProSe Layer-3 UE-to-Network Relay operation;
- optional the Relay Service Code(s) associates with the QoS mapping entry.
4) For 5G ProSe Layer-3 UE-to-Network Relay to relay Ethernet or Unstructured traffic from 5G ProSe Layer-3 Remote UE by using IP type PDU Session:
- Mapping of ProSe Service(s) to ProSe Application Server address information (consisting of IP address/FQDN and transport layer port number).
5) Parameters to broadcast warning messages:
- Configured Destination Layer-2 ID(s);
- PC5 QoS parameters defined in clause 5.6.1;
- the NR Tx Profile based on the configuration as specified in clause 5.1.3.1.
NOTE 3: It is up to inter operator alignment and network configuration whether a common Destination Layer-2 ID or IDs are used for all UEs cross PLMNs in a particular region for Public Warning Notification Relaying.
6) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe UE-to-Network Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Remote UE and thereby enabling the use of a 5G ProSe UE-to-Network Relay:
1) Authorisation policy for using a 5G ProSe Layer-3 and/or Layer-2 UE-to-Network Relay:
- For 5G ProSe Layer-3 Remote UE, indicates whether the UE is authorised to use a 5G ProSe Layer-3 UE-to-Network Relay.
- For 5G ProSe Layer-2 Remote UE, indicates the PLMNs in which the UE is authorized to use a 5G ProSe Layer-2 UE-to-Network Relay.
The authorisation for a UE to act as a 5G ProSe Remote UE also authorizes the use of 5G ProSe UE-to-Network Relay discovery with Model A and Model B.
NOTE 4: It is up to UE and application implementation to select a discovery model or whether to perform both models simultaneously.
2) Policy/parameters for 5G ProSe UE-to-Network Relay Discovery:
- Includes the parameters for 5G ProSe Relay Discovery and for enabling the UE to connect to the 5G ProSe UE-to-Network Relay after discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe UE-to-Network Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-Network Relay Layer indicator per RSC, optional Control Plane Security Indicator per RSC). The UE-to-Network Relay Layer Indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service. If the Control Plane Security Indicator is provided for a RSC, then the Control Plane based security procedures as described in clause 5.1.4.3.2 is performed for UE-to-Network Relay Communication for that RSC, otherwise if it is not provided for a RSC, then the User Plane based security procedures as described in clause 5.1.4.3.3 is performed for that RSC. RSC(s) dedicated for emergency service may be provisioned to enable the support of emergency services for UE-to-Network Relaying.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Solicitation messages and receiving Relay Discovery Announcement and Relay Discovery Additional Information messages;
- For 5G ProSe Layer-3 UE-to-Network Relay, the PDU Session parameters (PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference) to be used for the relayed traffic without using N3IWF access, or an indication of N3IWF access, for each ProSe Relay Service Code;
- For 5G ProSe Layer-3 UE-to-Network Relay, optionally the ProSe application Traffic Descriptor(s) (as defined in TS 23.503 [9]) to be used for the relayed traffic for each ProSe Relay Service Code;
- Includes security related content for 5G ProSe UE-to-Network Relay, see TS 33.503 [29].
3) Policy/parameters for N3IWF selection for 5G ProSe Layer-3 Remote UE:
- N3IWF identifier configuration for 5G ProSe Layer-3 Remote UE (either FQDN or IP address) in the HPLMN.
- 5G ProSe Layer-3 UE-to-Network Relay access node selection information - a prioritized list of PLMNs for N3IWF selection. It also indicates if selection of an N3IWF in a PLMN should be based on Tracking Area Identity FQDN or on Operator Identifier FQDN.
NOTE 5: 5G ProSe Relay Discovery policy/parameters can be provided from ProSe Application Server to the 5G ProSe Remote UE, except for the Security parameters in bullet 2).
4) Parameters to receive warning messages:
- Configured Destination Layer-2 ID(s);
- PC5 QoS parameters defined in clause 5.6.1;
- the NR Tx Profile based on the configuration as specified in clause 5.1.3.1.
NOTE 6: It is up to inter operator alignment and network configuration whether a common Destination Layer-2 ID or IDs are used for all UEs cross PLMNs in a particular region for Public Warning Notification Relaying.
5) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe UE-to-Network Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe UE-to-Network Relay as well as in the UE in support of the UE assuming the role of a 5G ProSe Remote UE and thereby enabling the use of a 5G ProSe UE-to-Network Relay:
1) Radio parameters for 5G ProSe UE-to-Network Relay Discovery when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
- Default PC5 DRX configuration (see TS 38.331 [16]).
2) Radio parameters for 5G ProSe UE-to-Network Relay communication when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Communication over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 7: The validity time of these radio parameters is the same as the validity time of the Policy/Parameter listed above for 5G ProSe UE-to-Network Relay or 5G ProSe Remote UE.
3) Policy/parameters related to privacy:
- A privacy timer value indicating the duration after which the UE shall change each source Layer-2 ID self-assigned by the UE when privacy is required.
5.1.4.1a Policy/Parameter provisioning for 5G ProSe Multi-hop UE-to-Network Relay
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Multi-hop UE-to-Network Relay:
1) Authorisation policy for acting as a 5G ProSe Layer-3 and/or Layer-2 Multi-hop UE-to-Network Relay when "served by NG-RAN":
- PLMNs in which the UE is authorized to relay traffic for 5G ProSe Multi-hop Layer-3 and/or Layer-2 Remote UEs supporting 5G ProSe Multi-hop UE-to-Network Relay.
The authorisation for a UE to act as a 5G ProSe Multi-hop UE-to-Network Relay also authorizes the use of 5G ProSe Multi-hop UE-to-Network Relay Discovery with Model A and Model B.
NOTE 1: It is up to UE and application implementation to select a discovery model or whether to perform both models simultaneously.
2) ProSe Relay Discovery policy/parameters for 5G ProSe Multi-hop UE-to-Network Relay:
- Includes the parameters that enable the UE to perform 5G ProSe Multi-hop UE-to-Network Relay Discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe Multi-hop UE-to-Network Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-Network Relay Layer Indicator per RSC, Multi-hop indicator per RSC, maximum number of hops per RSC). The UE-to-Network Relay Layer Indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service. RSC dedicated for emergency service may also be provisioned. The Multi-hop indicator indicates whether the associated RSC can be supported for 5G ProSe Multi-hop UE-to-Network Relay operation. The maximum number of hops per RSC indicates the maximum number of hops can be supported for the associated RSC.
NOTE 2: The RSC used for Multi-hop service is different from the RSC used for single-hop service.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Announcement and Relay Discovery Additional Information messages and receiving Relay Discovery Solicitation messages;
- For 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay, the PDU Session parameters (PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference) to be used for the relayed traffic for each ProSe Relay Service Code;
NOTE 3: 5G ProSe Relay Discovery policy/parameters can be provided from ProSe Application Server to the 5G ProSe UE-to-Network Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay.
3) For 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay to relay Ethernet or Unstructured traffic from 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay by using IP type PDU Session:
- Mapping of ProSe Service(s) to ProSe Application Server address information (consisting of IP address/FQDN and transport layer port number).
4) Parameters to broadcast warning messages:
- Configured Destination Layer-2 ID(s);
- PC5 QoS parameters defined in clause 5.6.1;
- the NR Tx Profile based on the configuration as specified in clause 5.1.3.1.
NOTE 4: It is up to inter operator alignment and network configuration whether a common Destination Layer-2 ID or IDs are used for all UEs cross PLMNs in a particular region for Public Warning Notification Relaying.
5) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Multi-hop UE-to-Network Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Multi-hop Remote UE and thereby enabling the use of a 5G ProSe Multi-hop UE-to-Network Relay:
1) Authorisation policy for using a 5G ProSe Layer-3 and/or Layer-2 Multi-hop UE-to-Network Relay:
- For 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay, indicates whether the UE is authorised to use a 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay.
- For 5G ProSe Multi-hop Layer-2 Remote UE, indicates the PLMNs in which the UE is authorized to use a 5G ProSe Multi-hop Layer-2 UE-to-Network Relay.
The authorisation for a UE to act as a 5G ProSe Multi-hop UE-to-Network Relay also authorizes the use of 5G ProSe Multi-hop UE-to-Network Relay discovery with Model A and Model B.
NOTE 5: It is up to UE and application implementation to select a discovery model or whether to perform both models simultaneously.
2) Policy/parameters for 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay:
- Includes the parameters for 5G ProSe Relay Discovery and for enabling the UE to connect to the 5G ProSe UE-to-Network Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay after discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe Layer-3 Multi-hop UE-to-Network Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-Network Relay Layer indicator per RSC, Multi-hop indicator per RSC, maximum number of hops per RSC). The UE-to-Network Relay Layer Indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service. RSC(s) dedicated for emergency service may be provisioned to enable the support of emergency services for Multi-hop UE-to-Network Relaying. The Multi-hop indicator indicates whether the associated RSC can be supported for 5G ProSe Multi-hop UE-to-Network Relay operation. The maximum number of hops per RSC indicates the maximum number of hops can be supported for the associated RSC.
NOTE 6: The RSC used for Multi-hop service is different from the RSC used for single-hop service.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Solicitation messages and receiving Relay Discovery Announcement and Relay Discovery Additional Information messages;
- For 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay, the PDU Session parameters (PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference) to be used for the relayed traffic without using N3IWF access, or an indication of N3IWF access, for each ProSe Relay Service Code;
- For 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay, optionally the ProSe application Traffic Descriptor(s) (as defined in TS 23.503 [9]) to be used for the relayed traffic for each ProSe Relay Service Code;
3) Policy/parameters for N3IWF selection for 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay:
- N3IWF identifier configuration for 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay (either FQDN or IP address) in the HPLMN.
- 5G ProSe Layer-3 UE-to-Network Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay access node selection information - a prioritized list of PLMNs for N3IWF selection. It also indicates if selection of an N3IWF in a PLMN should be based on Tracking Area Identity FQDN or on Operator Identifier FQDN.
NOTE 7: 5G ProSe Relay Discovery policy/parameters can be provided from ProSe Application Server to the 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 Multi-hop UE-to-Network Relay.
4) Parameters to broadcast warning messages:
- Configured Destination Layer-2 ID(s);
- PC5 QoS parameters defined in clause 5.6.1;
- the NR Tx Profile based on the configuration as specified in clause 5.1.3.1.
NOTE 8: It is up to inter operator alignment and network configuration whether a common Destination Layer-2 ID or IDs are used for all UEs cross PLMNs in a particular region for Public Warning Notification Relaying.
5) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Multi-hop UE-to-Network Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Intermediate UE-to-Network Relay:
1) Authorisation policy for acting as a 5G ProSe Intermediate UE-to-Network Relay:
- For 5G ProSe Layer-3 Intermediate UE-to-Network Relay, indicates whether the UE is authorised to act as a 5G ProSe Layer-3 Intermediate UE-to-Network Relay.
- For 5G ProSe Layer-2 Intermediate UE-to-Network Relay, indicates the PLMNs in which the UE is authorized to act as a 5G ProSe Layer-2 Intermediate UE-to-Network Relay.
The authorisation for a UE to act as a 5G ProSe Intermediate UE-to-Network Relay also authorizes the use of 5G ProSe Multi-hop UE-to-Network Relay Discovery with Model A and Model B.
NOTE 9: It is up to UE and application implementation to select a discovery model or whether to perform both models simultaneously.
2) ProSe Relay Discovery policy/parameters for 5G ProSe Layer-3 Intermediate UE-to-Network Relay:
- Includes the parameters that enable the UE to perform 5G ProSe Layer-3 Multi-hop UE-to-Network Relay Discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe Layer-3 Multi-hop UE-to-Network Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-Network Relay Layer Indicator per RSC, Multi-hop indicator per RSC, maximum number of hops per RSC). The UE-to-Network Relay Layer Indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service. RSC dedicated for emergency service may also be provisioned. The Multi-hop indicator indicates whether the associated RSC can be supported for 5G ProSe Multi-hop UE-to-Network Relay operation. The maximum number of hops per RSC indicates the maximum number of hops can be supported for the associated RSC.
NOTE 10: The RSC used for Multi-hop service is different from the RSC used for single-hop service.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Announcement and Relay Discovery Additional Information messages and receiving Relay Discovery Solicitation messages;
- For 5G ProSe Layer-3 Intermediate UE-to-Network Relay, the traffic type (IP, Ethernet, Unstructured) to be used for the relayed traffic for each Relay Service Code;
NOTE 11: 5G ProSe Relay Discovery policy/parameters can be provided from ProSe Application Server to the 5G ProSe Layer-3 Intermediate UE-to-Network Relay.
3) Parameters to broadcast warning messages:
- Configured Destination Layer-2 ID(s);
- PC5 QoS parameters defined in clause 5.6.1;
- the NR Tx Profile based on the configuration as specified in clause 5.1.3.1.
NOTE 12: It is up to inter operator alignment and network configuration whether a common Destination Layer-2 ID or IDs are used for all UEs cross PLMNs in a particular region for Public Warning Notification Relaying.
4) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Intermediate UE-to-Network Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Multi-hop UE-to-Network Relay, in the UE in support of the UE assuming the role of a 5G ProSe Multi-hop Remote UE supporting 5G ProSe Multi-hop UE-to-Network Relay and thereby enabling the use of a 5G ProSe UE-to-Network Relay and in the UE in support of the UE assuming the role of a 5G ProSe Intermediate UE-to-Network Relay:
1) Radio parameters for 5G ProSe Multi-hop UE-to-Network Relay Discovery when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
- Default PC5 DRX configuration (see TS 38.331 [16]).
2) Radio parameters for 5G ProSe Multi-hop UE-to-Network Relay communication when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Communication over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 13: The validity time of these radio parameters is the same as the validity time of the Policy/Parameter listed above for 5G ProSe Multi-hop UE-to-Network Relay or 5G ProSe Multi-hop Remote UE supporting 5G ProSe Multi-hop UE-to-Network Relay or 5G ProSe Intermediate UE-to-Network Relay.
3) Policy/parameters related to privacy:
- A privacy timer value indicating the duration after which the UE shall change each source Layer-2 ID self-assigned by the UE when privacy is required.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.4.2 Principles for applying parameters for 5G ProSe UE-to-Network Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.4.2.1 Principles for applying parameters for ProSe UE-to-Network Relay discovery
| The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe UE-to-Network Relay discovery service.
5.1.4.2.1a Principles for applying parameters for 5G ProSe Multi-hop UE-to-Network Relay discovery
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe Multi-hop UE-to-Network Relay discovery service.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.4.2.2 Principles for applying parameters for 5G ProSe UE-to-Network Relay communication
| The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe UE-to-Network Relay communication service.
5.1.4.2.2a Principles for applying parameters for 5G ProSe Multi-hop UE-to-Network Relay communication
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe Multi-hop UE-to-Network Relay communication service.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.4.3 Network controlled security procedures for 5G ProSe UE-to-Network Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.4.3.1 General
| Security procedures over Control Plane and User Plane are specified for 5G ProSe UE-to-Network relaying in TS 33.503 [29].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.4.3.2 Control Plane based security procedures for 5G ProSe UE-to-Network Relay
| Control Plane-based security procedures for 5G ProSe UE-to-Network Relay call flow and procedure are defined in TS 33.503 [29], characterised by the following principles:
- 5G ProSe UE-to-Network Relay's NAS signalling is used for the control plane based security procedure to authenticate and authorize a 5G ProSe Remote UE.
- A UE assuming the role of 5G ProSe UE-to-Network Relay can be configured to use a set of slices supporting Control Plane based security procedure. An AMF supporting Control Plane based security procedure for a 5G ProSe UE-to-Network Relay is selected as part of the slice. The 5G ProSe UE-to-Network Relay shall include in discovery messages the RSCs with the Control Plane Security Indicator set, as specified in clause 5.1.4.1, when the requested slice(s) corresponds to Control Plane based security procedure is(are) accepted. In addition, the 5G ProSe UE-to-Network Relay shall includes in discovery messages the RSCs without Control Plane Security Indicator as specified in clause 5.1.4.1.
- A 5G ProSe-enabled UE shall use Control Plane based security procedures if a RSC with Control Plane Security Indicator set is used by the Remote UE to establish the connection. Otherwise, if a RSC without Control Plane Security Indicator is used by the Remote UE to establish the connection, the 5G ProSe-enabled UEs shall use User Plane based security procedures as specified in clause 5.1.4.3.3.
- The AMF serving the 5G ProSe UE-to-Network Relay selects AUSF as specified in clause 6.3.4 of TS 23.501 [4] using the identification information the 5G ProSe Remote UE provided as specified in clause 6.3.3.3.2 of TS 33.503 [29].
- If the 5G ProSe Remote UE is configured by HPLMN to use control plane security procedure, the 5G ProSe Remote UE's HPLMN AUSF shall support control plane based security procedure.
- If a network intends to use control plane security procedure, then all the AMFs within the network slices that the 5G ProSe UE-to-Network Relay uses shall support the control plane based security procedures.
NOTE: If the control plane security procedure is not supported, then the 5G ProSe Remote UE can select another 5G ProSe UE-to-Network Relay or user plane based security can be used.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.4.3.3 User Plane based security procedures
| User Plane-based security procedures for 5G ProSe UE-to-Network Relay are defined in TS 33.503 [29].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.5 Authorization and Provisioning for 5G ProSe UE-to-UE Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.5.1 Policy/Parameter provisioning for 5G ProSe UE-to-UE Relay
| The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe UE-to-UE Relay:
1) Authorisation policy for acting as a 5G ProSe Layer-3 and/or Layer-2 UE-to-UE Relay:
- when the UE is "served by NG-RAN":
- PLMNs in which the UE is authorized to relay traffic for 5G ProSe Layer-3 and/or Layer-2 End UEs accessing 5G ProSe UE-to-UE Relays over PC5 reference point.
- when the UE is not "served by NG-RAN":
- Indicates whether the UE is authorized to relay traffic for 5G ProSe Layer-3 and/or Layer-2 End UEs accessing 5G ProSe UE-to-UE Relays over PC5 reference point.
- The authorisation for a UE to act as a 5G ProSe UE-to-UE Relay also authorizes the use of 5G ProSe UE-to-UE Relay Discovery with Model A and Model B.
NOTE 1: It is up to UE and application implementation to select a discovery model, or whether to perform both models simultaneously.
2) ProSe Relay Discovery policy/parameters for 5G ProSe UE-to-UE Relay:
- Includes the parameters that enable the UE to perform 5G ProSe UE-to-UE Relay Discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe UE-to-UE Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-UE Relay Layer indicator, Network Assistance Security Indicator). The UE-to-UE Relay Layer indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-UE Relay service. Network Assistance Security Indicator indicates whether the associated RSC is offering security procedures with or without network assistance when the 5G ProSe UE-to-UE Relay is served by NG-RAN.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Announcement message and sending/receiving Relay Discovery Solicitation messages;
- Default Destination Layer-2 ID(s) for sending/receiving Direct Communication Request message for ProSe UE-to-UE Relay Communication with integrated Discovery;
- For 5G ProSe Layer-3 UE-to-UE Relay, the traffic type (IP, Ethernet, Unstructured) to be used for the relayed traffic for each Relay Service Code;
- Includes security related content for 5G ProSe UE-to-UE Relay, see TS 33.503 [29].
NOTE 2: The security mechanism selection according to Network Assistance Security Indicator is specified in TS 33.503 [29].
3) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe UE-to-UE Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe End UE and thereby enabling the use of a 5G ProSe UE-to-UE Relay:
1) Authorisation policy for using a 5G ProSe Layer-3 and/or Layer-2 UE-to-UE Relay:
- When the UE is "served by NG-RAN":
- PLMNs in which the UE is authorized to use a 5G ProSe Layer-3 and/or Layer-2 UE-to-UE Relay.
- When the UE is "not served by NG-RAN":
- Indicates whether the UE is authorised to use a 5G ProSe Layer-3 and/or Layer-2 UE-to-UE Relay.
The authorisation for a UE to act as a 5G ProSe End UE also authorizes the use of 5G ProSe UE-to-UE Relay discovery with Model A and Model B.
NOTE 3: It is up to UE and application implementation to select a discovery model, or whether to perform both models simultaneously.
2) Policy/parameters for 5G ProSe UE-to-UE Relay Discovery:
- Includes the parameters for 5G ProSe UE-to-UE Relay Discovery as a 5G ProSe End UE and for enabling the UE to connect to the 5G ProSe UE-to-UE Relay after discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe UE-to-UE Relay Discovery parameters (Relay Service Code(s), UE-to-UE Relay Layer indicator, Network Assistance Security Indicator). The UE-to-UE Relay Layer indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-UE Relay service. Network Assistance Security Indicator indicates whether the associated RSC is offering security procedures with or without network assistance when the 5G ProSe UE-to-UE Relay is served by NG-RAN.
- Default Destination Layer-2 ID(s) for sending/receiving Relay Discovery Solicitation messages and receiving Relay Discovery Announcement message;
- Default Destination Layer-2 ID(s) for sending/receiving Direct Communication Request message for ProSe UE-to-UE Relay Communication with integrated Discovery;
- For 5G ProSe Layer-3 UE-to-UE Relay, the traffic type (IP, Ethernet, Unstructured) to be used for the relayed traffic for each Relay Service Code;
- Includes security related content for 5G ProSe UE-to-UE Relay, see TS 33.503 [29].
NOTE 4: The security mechanism selection according to Network Assistance Security Indicator is specified in TS 33.503 [29].
3) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe UE-to-UE Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe UE-to-UE Relay as well as in the UE in support of the UE assuming the role of a 5G ProSe End UE and thereby enabling the use of a 5G ProSe UE-to-UE Relay:
1) Radio parameters for 5G ProSe UE-to-UE Relay Discovery when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
- Default PC5 DRX configuration (see TS 38.331 [16]).
NOTE 5: Radio parameters for 5G ProSe UE-to-UE Relay Discovery when the UE is not "served by NG-RAN" and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Discovery in clause 5.1.2.1 are expected to be aligned for direct and relayed discovery for UE to UE communication.
2) Radio parameters for 5G ProSe UE-to-UE Relay communication when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Communication over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 6: Radio parameters for 5G ProSe UE-to-UE Relay communication when the UE is not "served by NG-RAN" and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Communication in clause 5.1.3.1 are expected to be aligned for direct and relayed UE to UE communication.
5.1.5.1a Policy/Parameter provisioning for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay:
1) Authorisation policy for acting as a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay:
- when the UE is "served by NG-RAN":
- PLMNs in which the UE is authorized to relay traffic for 5G ProSe Layer-3 End UEs supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay accessing 5G ProSe Layer-3 UE-to-UE Relays supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay over PC5 reference point.
- when the UE is not "served by NG-RAN":
- Indicates whether the UE is authorized to relay traffic for 5G ProSe Layer-3 End UEs supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay accessing 5G ProSe Layer-3 UE-to-UE Relays supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay over PC5 reference point.
- The authorisation for a UE to act as a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay also authorizes the use of 5G ProSe Layer-3 Multi-hop UE-to-UE Relay Discovery with Model A and Model B.
NOTE 1: It is up to UE and application implementation to select a discovery model, or whether to perform both models simultaneously.
2) ProSe Relay Discovery policy/parameters for 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay:
- Includes the parameters that enable the UE to perform 5G ProSe Layer-3 Multi-hop UE-to-UE Relay Discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe Layer-3 Multi-hop UE-to-UE Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-UE Relay Layer indicator, Multi-hop indicator per RSC, maximum number of hops per RSC). The UE-to-UE Relay Layer indicator indicates the associated RSC is offering 5G ProSe Layer-3 UE-to-UE Relay service. The Multi-hop indicator indicates whether the associated RSC can be supported for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay operation. The maximum number of hops per RSC indicates the maximum number of hops can be supported for the associated RSC.
- Default Destination Layer-2 ID(s) for sending Relay Discovery Announcement message and sending/receiving Relay Discovery Solicitation messages;
- For 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay, the traffic type (IP, Ethernet, Unstructured) to be used for the relayed traffic for each Relay Service Code;
3) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 End UE supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay and thereby enabling the use of a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay:
1) Authorisation policy for using a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay:
- When the UE is "served by NG-RAN":
- PLMNs in which the UE is authorized to use a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay.
- When the UE is "not served by NG-RAN":
- Indicates whether the UE is authorised to use a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay.
The authorisation for a UE to act as a 5G ProSe Layer-3 End UE supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay also authorizes the use of 5G ProSe Layer-3 UE-to-UE Relay discovery with Model A and Model B.
NOTE 2: It is up to UE and application implementation to select a discovery model, or whether to perform both models simultaneously.
2) Policy/parameters for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay Discovery:
- Includes the parameters for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay Discovery as a 5G ProSe Layer-3 End UE supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay and for enabling the UE to connect to the 5G ProSe Layer-3 UE-to-UE Relay after discovery when provided by PCF or provisioned in the ME or configured in the UICC:
- 5G ProSe Layer-3 Multi-hop UE-to-UE Relay Discovery parameters (Relay Service Code(s), UE-to-UE Relay Layer indicator, Multi-hop indicator per RSC, maximum number of hops per RSC). The UE-to-UE Relay Layer indicator indicates the associated RSC is offering 5G ProSe Layer-3 UE-to-UE Relay service. The Multi-hop indicator indicates whether the associated RSC can be supported for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay operation. The maximum number of hops per RSC indicates the maximum number of hops can be supported for the associated RSC.
- Default Destination Layer-2 ID(s) for sending/receiving Relay Discovery Solicitation messages and receiving Relay Discovery Announcement message;
- For 5G ProSe Layer-3 Remote UE supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay, the traffic type (IP, Ethernet, Unstructured) to be used for the relayed traffic for each Relay Service Code;
3) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay discovery and communication.
The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 UE-to-UE Relay supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay as well as in the UE in support of the UE assuming the role of a 5G ProSe Layer-3 End UE supporting 5G ProSe Layer-3 Multi-hop UE-to-UE Relay and thereby enabling the use of a 5G ProSe Layer-3 UE-to-UE Relay:
1) Radio parameters for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay Discovery when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
- Default PC5 DRX configuration (see TS 38.331 [16]).
NOTE 3: Radio parameters for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay Discovery when the UE is not "served by NG-RAN" and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Discovery in clause 5.1.2.1 are expected to be aligned for direct and relayed discovery for UE to UE communication.
2) Radio parameters for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication when the UE is not "served by NG-RAN":
- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Communication over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 4: Radio parameters for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication when the UE is not "served by NG-RAN" and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Communication in clause 5.1.3.1 are expected to be aligned for direct and relayed UE to UE communication.
NOTE 5: The RSC used for Multi-hop service is different from the RSC used for single-hop service.
3) Policy/parameters for PC5 groupcast for MANET multicast operation:
- Includes for each RSC an indication of whether to use PC5 groupcast mode for MANET multicast operation.
NOTE 6: All other PC5 groupcast parameters are set as defined in clause 5.1.3.1.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.5.2 Principles for applying parameters for 5G ProSe UE-to-UE Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.5.2.1 Principles for applying parameters for ProSe UE-to-UE Relay discovery
| The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe UE-to-UE Relay discovery service.
5.1.5.2.1a Principles for applying parameters for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay discovery
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay discovery service.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.1.5.2.2 Principles for applying parameters for 5G ProSe UE-to-UE Relay communication
| The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe UE-to-UE Relay communication service.
5.1.5.2.2a Principles for applying parameters for 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication
The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication service.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.2 5G ProSe Direct Discovery
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.2.1 General
| 5G ProSe Direct Discovery is defined as the process that detects and identifies another UE in proximity via NR PC5 reference point. As defined in clause 5.3.1.1 in TS 23.303 [3], 5G ProSe Direct Discovery can be open or restricted; it can be standalone or used for subsequent actions e.g. to initiate 5G ProSe Direct Communication.
In the case of inter-PLMN ProSe discovery and communication over PC5 reference point, the PC5 parameters need to be configured in a consistent way among the UEs within a certain region. The architecture for the Inter-PLMN PC5 case is defined in clause 4.2.3.
The UEs may use the PC5 DRX mechanism to perform 5G ProSe Direct Discovery and 5G ProSe UE-to-Network Relay Discovery over PC5 reference point as specified in clause 5.13.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.2.2 5G ProSe Direct Discovery Models
| There are two models for 5G ProSe Direct Discovery: Model A and Model B which are defined in clause 5.3.1.2 in TS 23.303 [3].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.2.3 5G ProSe UE-to-Network Relay Discovery
| For 5G ProSe UE-to-Network Relay discovery, both Model A and Model B discovery are supported:
- Model A uses a single discovery protocol message (Announcement).
- Model B uses two discovery protocol messages (Solicitation and Response).
For Relay Discovery Additional Information, only Model A discovery is used.
The procedures for 5G ProSe UE-to-Network Relay discovery are defined in clause 6.3.2.3.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.2.4 5G ProSe Direct Discovery Characteristics
| 5G ProSe Direct Discovery over the PC5 reference point has the following characteristics:
- PC5 communication channel is used to carry the discovery message over PC5. The discovery message over PC5 is differentiated with other PC5 messages by AS layer.
- ProSe layer shall indicate to AS layer whether the signalling is discovery message or PC5-S message.
NOTE 1: The discovery message format is defined in stage 3.
Group discovery/management to support on demand-based group communication for commercial services has the following characteristics:
- The group discovery/formation/management can be carried out in the Application layer in coordination with the Application Server.
- Application layer signalling between the UE and the Application Server is out of scope of this specification.
5G ProSe Direct Discovery with 5G DDNMF has the following characteristics:
- 5G DDNMF in the 5GS is used for 5G ProSe Discovery Direct Code management (including allocation and resolution). The 5G DDNMF gets the PDUID from the PCF and subscribes to notifications on Change of PDUID.
- 5G DDNMF is defined in clause 4.3.2 and the detail procedure for 5G ProSe Direct Discovery with 5G DDNMF is defined in clause 6.3.
Group discovery/management to support public safety has the following characteristics:
- Pre-configured or provisioned information can be used for the 5G ProSe Direct Discovery procedure as defined in clause 5.1.2.
The information elements included in the 5G ProSe Direct Discovery messages are described in clause 5.8.1 and clause 6.3.2.
NOTE 2: Based on UE implementation, the application layer discovery messages are exchanged either as user traffic over PC5 or alternatively as part of metadata in PC5 Direct Discovery message as specified in clause 6.3.2.1 and clause 6.4.2. In the latter case, the PC5 Direct Discovery message can contain additional field carrying application layer metadata information, e.g. the Application layer discovery messages for group discovery. The format and contents of this additional field is out of scope of 3GPP. Performance of the PC5 Direct Discovery message including the application layer information will be affected if the resulted PC5 Direct Discovery message size is too big, e.g. longer delay and lower reliability.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.2.5 5G ProSe UE-to-UE Relay Discovery
| For 5G ProSe UE-to-UE Relay Discovery, both Model A and Model B discovery are supported:
- Model A uses a single discovery protocol message (Announcement).
- Model B uses two discovery protocol messages (Solicitation and Response).
The procedures for 5G ProSe UE-to-UE Relay Discovery with Model A/Model B are defined in clause 6.3.2.4.
5G ProSe UE-to-UE Relay Communication with integrated Discovery is also supported as specified in clause 6.7.3.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.2.6 5G ProSe Multi-hop UE-to-Network Relay Discovery
| For 5G ProSe Multi-hop UE-to-Network Relay discovery, both Model A and Model B discovery are supported.
The procedures for 5G ProSe Multi-hop UE-to-Network Relay discovery Model A are defined in clause 6.3.2.5.2.
The procedures for 5G ProSe Multi-hop UE-to-Network Relay discovery Model B are defined in clause 6.3.2.5.3.
For Additional parameters announcement procedure, only Model A discovery is used and is defined in clause 6.3.2.5.4.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.2.7 5G ProSe Multi-hop UE-to-UE Relay Discovery
| For 5G ProSe Multi-hop UE-to-UE Relay discovery, both Model A and Model B discovery are supported:
- Model A uses a single discovery protocol message (Announcement).
- Model B uses two discovery protocol messages (Solicitation and Response).
Based on the RSC used for the discovery, the 5G ProSe Multi-hop UE-to-UE Relay discovery may use one of the two different types of discovery operations, i.e. discovery for IP PDU type and discovery for non-IP PDU type. A 5G ProSe Multi-hop UE-to-UE Relay may support only one or both types of discovery operations.
The procedures for 5G ProSe Multi-hop UE-to-UE Relay discovery Model A/B for IP PDU type are defined in clause 6.3.2.6.2. The procedures for 5G ProSe Multi-hop UE-to-UE Relay discovery Model A/B for non-IP PDUs (e.g. Ethernet or Unstructured) are defined in clause 6.3.2.6.3.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.3 5G ProSe Direct Communication
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.3.1 General
| 5G ProSe Direct Communication over PC5 reference point is supported when the UE is "served by NG-RAN" or when the UE is "not served by NG-RAN". A UE is authorized to perform 5G ProSe Direct Communication when it has valid authorization and configuration as specified in clause 5.1.3. 5G ProSe Direct Communication supports both the cases of public safety and commercial service.
5G ProSe Direct Communication over NR based PC5 reference point supports broadcast mode, groupcast mode and unicast mode.
For broadcast and groupcast mode 5G ProSe Direct Communication, the following data unit types are supported: IPv4, IPv6, Ethernet, Unstructured and Address Resolution Protocol (see RFC 826 [19]).
For unicast mode 5G ProSe Direct Communication, the following data unit types are supported: IPv4, IPv6, Ethernet and Unstructured.
The identifiers used in the 5G ProSe Direct Communication over PC5 reference point are described in clause 5.8.2.
The QoS handling and procedures for the 5G ProSe Direct Communication over PC5 reference point are defined in clauses 5.6 and 6.4.
The UEs may use the PC5 DRX mechanism to perform 5G ProSe Direct Communication over PC5 reference point as specified in clause 5.13.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.3.2 Broadcast mode 5G ProSe Direct Communication
| Broadcast mode of 5G ProSe direct communication is supported over NR based PC5 reference point. The transmitting UE in broadcast communication determines the destination Layer-2 ID for broadcast as specified in clause 5.8.2 and assigns itself a source Layer-2 ID. The receiving UE determines the destination Layer-2 ID for broadcast reception as specified in clause 5.8.2. The transmitting UE determines the PC5 QoS parameters for this broadcast as specified in clause 5.6.1. The transmitting UE sends the service data using the source Layer-2 ID and the destination Layer-2 ID.
For IP type 5G ProSe direct communication over PC5 reference point, the mechanism for IP address allocation is described in clause 5.5.1.2.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.3.3 Groupcast mode 5G ProSe Direct Communication
| Groupcast mode of 5G ProSe direct communication is supported over NR based PC5 reference point. Group management is carried out by the application layer in coordination with Application Server and is out of scope of this specification. For commercial services, the Application Layer Group ID is provided by Application Server; and for public safety services, the pre-configured or provisioned Application Layer Group ID will be used for groupcast communication. The group size and member ID information could be used for groupcast control if it is provided by the application layer.
The transmitting UE in groupcast communication determines a source Layer-2 ID and a destination Layer-2 ID and the receiving UE determines destination Layer-2 ID, as specified in clause 5.8.2. The transmitting UE determines the PC5 QoS parameters for this groupcast as specified in clause 5.6.1. The transmitting UE sends the service data using the source Layer-2 ID and the destination Layer-2 ID.
For IP type 5G ProSe direct communication over PC5 reference point, the mechanism for IP address allocation is described in clause 5.5.1.2.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.3.4 Unicast mode 5G ProSe Direct Communication
| Unicast mode of 5G ProSe direct communication is supported over NR based PC5 reference point. A PC5 unicast link between two UEs is established for the 5G ProSe direct communication; and the PC5 unicast link could be maintained, modified and released according to the application layer requests or communication requirements.
For the PC5 unicast link of the 5G ProSe direct communication, the principal for the PC5 unicast link of V2X communication described in TS 23.287 [2] clause 5.2.1.4 is reused with the following differences:
- V2X service is replaced by ProSe Application;
- V2X service type is replaced by ProSe identifier;
- New data unit types are supported (including IPv4, Ethernet and Unstructured).
For IP type 5G ProSe direct communication over PC5 reference point, the mechanism for IP address/prefix allocation is described in clause 5.5.1.1. The PC5 QoS handling for the unicast mode 5G ProSe direct communication is specified in clause 5.6.1.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.4 5G ProSe UE-to-Network Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.4.1 5G ProSe Layer-3 UE-to-Network Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.4.1.1 General
| The 5G ProSe Layer-3 UE-to-Network Relay shall provide generic function that can relay any IP, Ethernet or Unstructured traffic:
- For IP traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay uses IP type PDU Session towards 5GC.
- For Ethernet traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay can use Ethernet type PDU Session or IP type PDU Session towards 5GC.
- For Unstructured traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay can use Unstructured type PDU Session or IP type PDU Session (i.e. IP encapsulation/de-capsulation by 5G ProSe Layer-3 UE-to-Network Relay) towards 5GC.
The type of traffic supported over PC5 reference point is indicated by the 5G ProSe Layer-3 UE-to-Network Relay e.g. using the corresponding RSC. The 5G ProSe Layer-3 UE-to-Network Relay determines the PDU Session Type based on configuration of the mapping between PDU Session parameters and RSC, as specified in clause 5.1.4.1.
IP type PDU Session and Ethernet type PDU Session can be used to support more than one 5G ProSe Layer-3 Remote UEs while Unstructured type PDU Session can be used to support only one 5G ProSe Layer-3 Remote UE.
NOTE: The maximum number of PDU Sessions can affect the maximum number of 5G ProSe Layer-3 Remote UEs that the 5G ProSe UE-to-Network Relay can support.
The 5G ProSe Layer-3 UE-to-Network Relay provides the functionality to support indirect connectivity to the 5GS for 5G ProSe Layer-3 Remote UEs. A 5G ProSe Layer-3 Remote UE can be located within NG-RAN coverage or outside of NG-RAN coverage.
The 5G ProSe Layer-3 Remote UE and 5G ProSe Layer-3 UE-to-Network Relay may use the PC5 DRX mechanism to perform 5G ProSe UE-to-Network Relay Communications over PC5 reference point as specified in clause 5.13.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.4.1.2 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support
| To support 5G ProSe Layer-3 Remote UE services with end-to-end confidentiality and IP address preservation requirements, the 5G ProSe Layer-3 UE-to-Network Relay with N3IWF shall provide access to the 5GC for the 5G ProSe Layer-3 Remote UE via N3IWF using the features defined in clause 4.2.8 of TS 23.501 [4].
5G ProSe Layer-3 UE-to-Network Relay is provisioned with RSC(s) and the corresponding PDU session parameters (e.g. S-NSSAI) to support N3IWF access as part of 5G ProSe Layer-3 UE-to-Network Relay Policy/parameters. When a 5G ProSe Layer-3 Remote UE connects with the corresponding RSC, the 5G ProSe Layer-3 UE-to-Network Relay determines the corresponding PDU session parameters based on the requested RSC.
NOTE: The 5G ProSe Layer-3 UE-to-Network Relay only includes a RSC in discovery message when the corresponding PDU session parameters (e.g. S-NSSAI) are authorized to be used in the accessed network.
The 5G ProSe Layer-3 Remote UE selects N3IWF as specified in clause 6.5.1.2.2. The selection of N3IWF follows the regulatory rules of the country where it is located and when required by the regulations the 5G ProSe Layer-3 Remote UE only selects a N3IWF within the local country. QoS differentiation can be provided on per-IPsec Child Security Association basis and the details are provided in clause 5.6.2.2.
The 5GC to which the 5G ProSe Layer-3 UE-to-Network Relay registers and the 5GC to which the 5G ProSe Layer-3 Remote UE registers may be in the same PLMN or different PLMN.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.4.1.3 Policy control and session binding to support 5G ProSe Layer-3 UE-to-Network Relay without N3IWF
| To enable support for policy control for 5G ProSe Layer-3 Remote UEs accessing 5GC via a 5G ProSe Layer-3 UE-to-Network Relay without involving N3IWF, the policy control functionality specified in TS 23.503 [9] is applied with the following functionalities:
- For non-emergency service over the 5G ProSe Layer-3 UE-to-Network Relay, the SMF and PCF shall be configured with DNN(s) dedicated for UE-to-Network Relay connectivity, as specified in clause 5.1.4.1.
NOTE 1: If Local Breakout configuration is supported for relay connectivity, the DNN dedicated for UE-to-Network Relay connectivity needs to be well-known DNN to allow seamless operation across various operators' networks.
NOTE 2: For emergency service over the 5G ProSe Layer-3 UE-to-Network Relay (as specified in clause 5.4.4.3), emergency DNN configured in the Relay's AMF (as specified in clause 5.16.4 of TS 23.501 [4]) is used.
- The AF discovers the PCF serving the 5G ProSe Layer-3 UE-to-Network Relay PDU Session as specified in clause 6.1.1.2 of TS 23.503 [9].
- The PCF may validate any 5G ProSe Layer-3 Remote UE related service information from the AF based on roaming agreement and the DNN dedicated for UE-to-Network Relay connectivity for non-emergency service from the 5G ProSe Layer-3 Remote UE or emergency DNN for emergency service from the 5G ProSe Layer-3 Remote UE.
NOTE 3: For 5G ProSe Layer-3 UE-to-Network Relay connectivity, the UE identity that the SMF has provided (i.e. 5G ProSe Layer-3 UE-to-Network Relay Identity) and a UE identity provided by the AF (i.e. 5G ProSe Layer-3 Remote UE Identity) can be different, while the Session binding with the PDU Session is valid.
- The 5G ProSe Layer-3 Remote UEs may be assigned a /64 IPv6 Prefix from a shorter IPv6 prefix by the 5G ProSe Layer-3 UE-to-Network Relay. A /64 IPv6 Prefix from a shorter IPv6 prefix needs to be assigned to support policy control and session binding of a 5G ProSe Layer-3 Remote UE behind a 5G ProSe Layer-3 UE-Network Relay.
- For a PDU Session to the DNN dedicated for 5G ProSe Layer-3 UE-to-Network Relay connectivity and using IPv6 prefix delegation (i.e. the assigned IPv6 network prefix is shorter than 64), the PCF shall perform session binding based on the IPv6 network prefix only. A successful session binding occurs whenever a longer prefix received from an AF matches the prefix value of the PDU Session. PCF shall not use the UE Identity for session binding for this PDU Session.
NOTE 4: Support for policy control of Remote UEs behind a 5G ProSe Layer-3 UE-Network Relay using IPv4 is not available.
NOTE 5: If a /64 IPv6 Prefix from a shorter IPv6 prefix is not assigned to the 5G ProSe Layer-3 Remote UE by the 5G ProSe Layer-3 UE-Network Relay then support for policy control and session binding of 5G ProSe Layer-3 Remote UE behind a 5G ProSe Layer-3 UE-Network Relay is not available.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.4.2 5G ProSe Layer-2 UE-to-Network Relay
| The 5G ProSe Layer-2 UE-to-Network Relay provides forwarding functionality that can relay any type of traffic over the PC5 link.
The 5G ProSe Layer-2 UE-to-Network Relay provides the functionality to support connectivity to the 5GS for 5G ProSe Layer-2 Remote UEs. A UE is considered to be a 5G ProSe Layer-2 Remote UE if it has successfully established a PC5 link to the 5G ProSe Layer-2 UE-to-Network Relay. A 5G ProSe Layer-2 Remote UE can be located within NG-RAN coverage or outside of NG-RAN coverage.
For PLMN selection and relay selection in the 5G ProSe Layer-2 Remote UE:
- The 5G ProSe Layer-2 Remote UE checks whether the PLMN(s) within the RRC Container (see clause 5.8.3.3) obtained from the 5G ProSe Layer-2 UE-to-Network Relay(s) during 5G ProSe UE-to-Network Relay Discovery in clause 6.3.2.3 are authorized to be connected to via a 5G ProSe Layer-2 UE-to-Network Relay(s) and only the authorized PLMN(s) are then available PLMNs for NAS PLMN selection;
- The 5G ProSe Layer-2 Remote UE selects the 5G ProSe Layer-2 UE-to-Network Relay considering the selected PLMN by NAS layer.
NOTE: A Layer-2 Remote UE can select a PLMN different from the 5G ProSe Layer-2 UE-to-Network Relay's serving PLMN to access emergency and non-emergency services.
The 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay may use the PC5 DRX mechanism to perform 5G ProSe UE-to-Network Relay Communications over PC5 reference point as specified in clause 5.13.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.4.3 Mobility Restrictions for 5G ProSe UE-to-Network Relaying
| The handling of Mobility Restrictions for 5G ProSe enabled UE follows the principles as specified in clause 5.3.4.1 of TS 23.501 [4] with the following additions and clarifications:
- Forbidden Area:
- In a Forbidden Area, a 5G ProSe enabled UE is not allowed to perform the Relay operation. If the 5G ProSe UE-to-Network Relay operates in a Forbidden Area of the 5G ProSe Remote UE, the 5G ProSe Remote UE is not allowed to access the network via this 5G ProSe UE-to-Network Relay unless the 5G ProSe Remote UE is attempting for emergency service.
- Service Area Restriction:
- Service Area Restriction is not applicable to 5G ProSe Layer-3 Remote UE.
- Service Area Restriction is not applicable to 5G ProSe enabled MCX-subscribed UEs as defined in clause 5.3.4.1 of TS 23.501 [4].
NOTE 1: It is expected that all 5G ProSe enabled Public Safety UEs are MCX-subscribed as defined in clause 5.16.6 of TS 23.501 [4].
- In a Non-Allowed Area, a 5G ProSe enabled UE follows the principles of a UE in limited service state as specified in clause 5.9. It cannot perform the Relay operation as 5G ProSe Layer-2 UE-to-Network Relay or 5G ProSe Layer-3 UE-to-Network Relay based on the conditions described in clause 5.9 except for emergency service from the 5G ProSe Remote UE as specified in clause 5.4.4.
- In a Non-Allowed Area, a 5G ProSe Layer-2 Remote UE follows the principles as specified in clause 5.3.4.1 of TS 23.501 [4], for communication with the network via the 5G ProSe Layer-2 UE-to-Network Relay.
- Core Network type restriction, RAT type restriction:
In these cases, a 5G ProSe enabled UE is not able to register in the network for normal service and stays in limited service state and the principles in clause 5.9 shall apply. The 5G ProSe Layer-2 Remote UE is allowed to register to the network via the 5G ProSe UE-to-Network Relay for emergency service.
NOTE 2: Closed Access Group information is not specified for 5G ProSe.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.4.4 Support of emergency service from 5G ProSe Remote UE via 5G ProSe UE-to-Network Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.4.4.1 General
| When a 5G ProSe enabled UE does not have direct connection to the network for emergency service, the UE may attempt to obtain emergency service via 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay.
NOTE: Direct connection refers to the UE connected to the network via Uu or WLAN. No direct connection to the network for emergency service includes also the case that the RAN broadcast SIB indicates no emergency support as specified in TS 23.122 [14].
A 5G ProSe enabled UE acting as 5G ProSe UE-to-Network Relay shall have a normal registration (including also normal registration for a 5G ProSe Relay enabled UE in Non-Allowed Area). A 5G ProSe enabled UE in limited-service state shall not act as 5G ProSe UE-to-Network Relay. Mobility Restrictions that are overruled for UE requesting direct emergency service are overruled also for 5G ProSe UE-to-Network Relay that is relaying emergency service as specified in clause 5.4.3.
A 5G ProSe enabled UE acting as 5G ProSe UE-to-Network Relay shall only advertise its support for relaying emergency services as defined in clause 5.4.4.2 and clause 5.4.4.3 during 5G ProSe UE-to-Network Relay Discovery.
Dedicated RSC(s) for emergency service needs to be provisioned in the 5G ProSe enabled UEs with capability of 5G ProSe UE-to-Network Relay and/or 5G ProSe Remote UE as specified in clause 5.1.4.
The dedicated RSC(s) for emergency service are used by the 5G ProSe UE-to-Network Relay and 5G ProSe Remote UE during 5G ProSe UE-to-Network Relay Discovery and PC5 link establishment.
A PC5 link associated with a dedicated emergency RSC shall be used for emergency service and for emergency service only.
If the 5G ProSe UE-to-Network Relay needs to establish RRC Connection when the 5G ProSe Remote UE has requested emergency service over the PC5 link, the 5G ProSe UE-to-Network Relay shall use RRC establishment cause "emergency".
The existing positioning function as applicable is reused for the 5G ProSe Remote UE. If no other information is available, the location of the 5G ProSe UE-to-Network Relay can be used as Remote UE location estimate.
For more information on UE specific behaviour and location handling, refer to TS 23.167 [31].
PC5 link for emergency services over 5G ProSe UE-to-Network Relay can be established with or without PC5 security; how to establish PC5 security link for emergency service is specified in TS 33.503 [29].
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 5.4.4.2 Emergency service from 5G ProSe Remote UE via 5G ProSe Layer-2 UE-to-Network Relay
| For a 5G ProSe Layer-2 UE-to-Network Relay to participate in the 5G ProSe UE-to-Network Relay Discovery procedure for emergency service (i.e. sending the UE-to-Network Relay Discovery Announcement message or UE-to-Network Relay Discovery Response message), the serving NG-RAN support of emergency services is required, indicated by it broadcasting ims-EmergencySupport in system information as specified in TS 38.300 [12] and TS 38.331 [16]. The 5G ProSe Layer-2 Remote UE may select a different PLMN from the 5G ProSe Layer-2 UE-to-Network Relay. The 5G ProSe Layer-2 Remote UE may select any PLMN within the RRC Container (see clause 5.8.3.3) obtained from any 5G ProSe Layer-2 UE-to-Network Relay(s) which has announced the RSC dedicated for emergency service during 5G ProSe UE-to-Network Relay Discovery in clause 6.3.2.3.
NOTE: When emergency support is indicated by RAN, 5G ProSe Layer-2 UE-to-Network Relay can participate in the 5G ProSe UE-to-Network Relay Discovery procedure for emergency service (i.e. sending the UE-to-Network Relay Discovery Announcement message or UE-to-Network Relay Discovery Response message) even if its serving PLMN does not support emergency service.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.