hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.7 Subscription to 5G ProSe
|
The subscription information in the UDM contains information to give the user permission to use 5G ProSe.
At any time, the operator can amend or remove the ProSe UE subscription rights from subscription information in the UDM, or to revoke the user's permission to use 5G ProSe.
The following subscription information is defined for 5G ProSe:
- subscription for open 5G ProSe Direct Discovery for NR PC5:
- open 5G ProSe Direct Discovery Model A.
- subscription for restricted 5G ProSe Direct Discovery for NR PC5:
- restricted 5G ProSe Direct Discovery Model A;
- restricted 5G ProSe Direct Discovery Model A with application-controlled extension;
- restricted 5G ProSe Direct Discovery Model A with "on demand" announcing;
- restricted 5G ProSe Direct Discovery Model B.
- subscription for Broadcast, Groupcast and Unicast mode 5G ProSe Direct Communication for NR PC5.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-2 UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 UE-to-Network Relay.
- subscription for 5G ProSe Layer-2 Remote UE access via 5G ProSe Layer-2 UE-to-Network Relay.
- subscription for 5G ProSe Layer-3 Remote UE access via 5G ProSe Layer-3 UE-to-Network Relay.
- subscription for multi-path communication via direct Uu path and via 5G ProSe Layer 2 UE-to-Network Relay as a 5G ProSe Layer-2 Remote UE.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-2 UE-to-UE Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 UE-to-UE Relay.
- subscription for 5G ProSe Layer-2 End UE access via 5G ProSe Layer-2 UE-to-UE Relay.
- subscription for 5G ProSe Layer-3 End UE access via 5G ProSe Layer-3 UE-to-UE Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 Intermediate UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 Remote UE supporting Multi-hop 5G ProSe Layer-3 UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 UE-to-Network Relay supporting Multi-hop 5G ProSe Layer-3 UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-2 Intermediate UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-2 Remote UE supporting Multi-hop 5G ProSe Layer-2 UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-2 UE-to-Network Relay supporting Multi-hop 5G ProSe Layer-2 UE-to-Network Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 UE-to-UE Relay supporting Multi-hop 5G ProSe Layer-3 UE-to-UE Relay.
- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 End UE supporting Multi-hop 5G ProSe Layer-3 UE-to-UE Relay.
- UE-PC5-AMBR for NR PC5.
- PC5 QoS parameters as defined in clause 5.6.1 used by NG-RAN.
- the list of the PLMNs authorized for 5G ProSe services, including:
- the list of the PLMNs where the UE is authorised for open 5G Direct Discovery Model A, i.e. to announce or monitor or both.
- the list of the PLMNs where the UE is authorised for restricted 5G ProSe Direct Discovery Model A, i.e. to announce or monitor or both.
- the list of the PLMNs where the UE is authorised for restricted 5G ProSe Direct Discovery Model B, i.e. to perform Discoverer operation or Discoveree operation or both.
- the list of the PLMNs where the UE is authorised to perform Broadcast, Groupcast and Unicast mode 5G ProSe Direct Communication for NR PC5.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 Remote UE.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 UE-to-UE Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 UE-to-UE Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 End UE.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 End UE.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 Intermediate UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 UE-to-Network Relay supporting Multi-hop 5G ProSe Layer-3 UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 Intermediate UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 UE-to-Network Relay supporting Multi-hop 5G ProSe Layer-2 UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 Remote UE supporting Multi-hop 5G ProSe Layer-2 UE-to-Network Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 UE-to-UE Relay supporting Multi-hop 5G ProSe Layer-3 UE-to-UE Relay.
- the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 End UE supporting Multi-hop 5G ProSe Layer-3 UE-to-UE Relay.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8 Identifiers
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1 Identifiers for 5G ProSe Direct Discovery
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.0 General
|
NOTE: The 5G DDNMF takes the role of "ProSe Function" if it exists in the following definitions in TS 23.303 [3].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.1 ProSe Application ID
|
ProSe Application ID is defined in TS 23.303 [3].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.2 Destination Layer-2 ID
|
Destination Layer-2 ID is defined in clause 5.6.1 of TS 23.287 [2].
The Destination Layer-2 ID for 5G ProSe Direct Discovery with Model A is selected based on the configuration as described in clause 5.1.2.1. The Destination Layer-2 ID for a Solicitation message for Model B is selected based on the configuration as described in clause 5.1.2.1. The Destination Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery is selected as described in clause 5.8.4.2.
For Group member discovery:
- If an Application Layer Group ID has a configured Layer-2 Group ID, which is provisioned as specified in clause 5.1.2.1, the UE uses this Layer-2 Group ID as the Destination Layer-2 ID,
- otherwise, the UE converts the Application Layer Group ID into a Destination Layer-2 ID.
NOTE: The mechanism for converting the application layer provided Application Layer Group ID to the Destination Layer-2 ID is defined in Stage 3.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.3 Source Layer-2 ID
|
Source Layer-2 ID is defined in clause 5.6.1 of TS 23.287 [2].
The UE self-selects a Source Layer-2 ID for 5G ProSe Direct Discovery and Group member discovery. The Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery is selected as described in clause 5.8.4.2.
NOTE: The UE implementation needs to ensure that when the UE self-selects Source Layer-2 IDs, the self-selected Source Layer-2 IDs are different between 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery) in clause 6.3.2 and 5G ProSe Direct Communication (including 5G ProSe UE-to-Network Relay Communication and 5G ProSe UE-to-UE Relay Communication) in clauses 6.4, 6.5 and 6.7 and are different from any other provisioned Destination Layer-2 IDs as described in clause 5.1 and any other self-selected Source Layer-2 IDs used in a simultaneous 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery) with a different discovery model.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.4 ProSe Application Code
|
ProSe Application Code is defined in TS 23.303 [3].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.5 ProSe Restricted Code
|
ProSe Restricted Code is defined in TS 23.303 [3].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.6 ProSe Query Code
|
ProSe Query Code is defined in TS 23.303 [3].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.7 ProSe Response Code
|
ProSe Response Code is defined in TS 23.303 [3].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.8 User Info ID
|
User Info ID (including Announcer Info, Discoverer Info, Discoveree Info) is defined in clause 3.1.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.9 ProSe Discovery UE ID
|
ProSe Discovery UE ID is defined in TS 23.303 [3].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.10 Restricted ProSe Application User ID
|
Restricted ProSe Application User ID is defined in TS 23.303 [3].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.11 Announcing PLMN ID
|
Announcing PLMN ID is defined in TS 32.277 [22].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.12 Announcer Info
|
Announcer Info is one of the uses of User Info ID as described in clause 5.8.1.8.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.13 Discoverer Info
|
Discoverer Info is one of the uses of User Info ID as described in clause 5.8.1.8.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.14 Target Info
|
Target Info provides information about the targeted discoveree in the Group Member Discovery Solicitation message specified in clause 6.3.2.2.3 and in the 5G ProSe UE-to-Network Relay Discovery Solicitation message specified in clause 6.3.2.3.3. The Target Info is the User Info ID of the discoveree.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.15 Discoveree Info
|
Discoveree Info is one of the uses of User Info ID as described in clause 5.8.1.8.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.16 Application Layer Group ID
|
Application Layer Group ID is defined in TS 23.303 [3].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.1.17 Monitored PLMN ID
|
Monitored PLMN ID is defined in TS 32.277 [22].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.2 Identifiers for 5G ProSe Direct Communication
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.2.1 General
|
Each UE has one or more Layer-2 IDs for 5G ProSe direct communication over PC5 reference point, consisting of:
- Source Layer-2 ID(s); and
- Destination Layer-2 ID(s).
Source and Destination Layer-2 IDs are included in layer-2 frames sent on the layer-2 link of the PC5 reference point identifying the layer-2 source and destination of these frames. Source Layer-2 IDs are always self-assigned by the UE originating the corresponding layer-2 frames.
The selection of the Source and Destination Layer-2 ID(s) by a UE depends on the communication mode of 5G ProSe direct communication over PC5 reference point for this layer-2 link, as described in clauses 5.8.2.2, 5.8.2.3 and 5.8.2.4. The Source Layer-2 IDs may differ between different communication modes.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.2.2 Identifiers for broadcast mode 5G ProSe direct communication
|
For broadcast mode of 5G ProSe direct communication over PC5 reference point, the UE is configured with the Destination Layer-2 ID(s) to be used for ProSe applications. The Destination Layer-2 ID for a 5G ProSe direct communication is selected based on the configuration as described in clause 5.1.3.1.
The UE self-selects a Source Layer-2 ID.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.2.3 Identifiers for groupcast mode 5G ProSe direct communication
|
For groupcast mode of 5G ProSe direct communication over PC5 reference point, the application layer may provide Application Layer Group ID.
The UE determines a Destination Layer-2 ID as below:
- When the Application Layer Group ID is provided by the application layer,
- and when ProSe Layer-2 Group ID is configured for the Application Layer Group ID provided by the application layer as specified in clause 5.1.3.1, the UE uses the ProSe Layer-2 Group ID as the Destination Layer-2 ID; or
- and when ProSe Layer-2 Group ID is not configured for the Application Layer Group ID provided by the application layer, the UE converts the Application Layer Group ID into a Destination Layer-2 ID.
- When the Application Layer Group ID is not provided by the application layer, the UE determines the Destination Layer-2 ID based on configuration of the mapping between ProSe Identifier and Layer-2 ID, as specified in clause 5.1.3.1.
NOTE: The mechanism for converting the application layer provided Application Layer Group ID to the Destination Layer-2 ID is defined in Stage 3.
The UE self-selects a Source Layer-2 ID.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.2.4 Identifiers for unicast mode 5G ProSe direct communication
|
For unicast mode of 5G ProSe direct communication over PC5 reference point, the Destination Layer-2 ID used depends on the communication peer. The Layer-2 ID of the communication peer, identified by the peer's Application Layer ID, may be discovered during the establishment of the PC5 unicast link, or known to the UE via prior ProSe direct communications, e.g. existing or prior unicast link to the same Application Layer ID, or obtained from 5G ProSe direct discovery process. The initial signalling for the establishment of the PC5 unicast link may use the known Layer-2 ID of the communication peer, or a default destination Layer-2 ID associated with the ProSe service (i.e. ProSe identifier) configured for PC5 unicast link establishment, as specified in clause 5.1.3.1. During the PC5 unicast link establishment procedure, Layer-2 IDs are exchanged and should be used for future communication between the two UEs, as specified in clause 6.4.3.
The UE maintains a mapping between the Application Layer IDs and the source Layer-2 IDs used for the PC5 unicast links, as the ProSe application layer does not use the Layer-2 IDs. This allows the change of source Layer-2 ID without interrupting the ProSe applications.
When Application Layer IDs change, the source Layer-2 ID(s) of the PC5 unicast link(s) shall be changed if the link(s) was used for 5G ProSe communication with the changed Application Layer IDs.
Based on privacy configuration as specified in clause 5.1.3.1, the update of the new identifiers of a source UE to the peer UE for the established unicast link may cause the peer UE to change its Layer-2 ID and optionally IP address/prefix if IP communication is used as defined in clause 6.4.3.2.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.3 Identifiers for 5G ProSe UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.3.1 Common identifiers for 5G ProSe UE-to-Network Relay
|
The following parameters are used for the 5G ProSe UE-to-Network Relay Discovery Announcement message (Model A), where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and Announcer Info and Relay Service Code are contained in the message:
- Source Layer-2 ID: the 5G ProSe UE-to-Network Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery.
- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery is selected based on the configuration as described in clause 5.1.4.1.
- Announcer Info: provides information (i.e. User Info ID) about the announcing user.
- Relay Service Code: parameter identifying a connectivity service the 5G ProSe UE-to-Network Relay provides to a 5G ProSe Remote UE. The Relay Service Codes are configured in a 5G ProSe UE-to-Network Relay for advertisement. Additionally, the Relay Service Code may also identifies authorized users the 5G ProSe UE-to-Network Relay would offer service to and may be used to select the related security policies or information e.g. necessary for authentication and authorization between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay (e.g. a Relay Service Code for relays for police members only would be different than a Relay Service Code for relays for Fire Fighters only, even though potentially they provided connectivity to same DN e.g. to support Internet Access).
The 5G ProSe UE-to-Network Relay Discovery Announcement message (Model A) is extended and modified as follows when used for 5G ProSe multi-hop UE-to-Network Relay discovery:
- Hop-Count: This value reflects the number of PC5 hops for the 5G ProSe Remote UE to reach the network. It is set to 1 by the 5G ProSe UE-to-Network Relay and shall be incremented by 1 every time the 5G ProSe UE-to-Network Relay Discovery Announcement message is forwarded by a 5G ProSe Intermediate UE-to-Network Relay.
A 5G ProSe Intermediate UE-to-Network Relay shall only process the 5G ProSe UE-to-Network Relay Discovery Announcement if the Hop-Count is present and the value is less than the (pre-)configured maximum number of hops for the associated RSC and the optional Hop-Limit in the message.
- Source Layer-2 ID: the 5G ProSe UE-to-Network Relay or the 5G ProSe Intermediate UE-to-Network Relay self-selects a Source Layer-2 ID when sending the discovery message.
- Destination Layer-2 ID: the 5G ProSe Intermediate UE-to-Network Relay sets the Desination Layer-2 ID of the 5G ProSe UE-to-Network Relay Discovery Announcement message based on configuration described in clause 5.1.4.1.
- Announcer Info: identify information (i.e. User Info ID) of the announcing 5G ProSe UE-to-Network Relay or the 5G ProSe Intermediate UE-to-Network Relay.
- (optinal) Root Relay Info: this is the User Info ID of the 5G ProSe UE-to-Network Relay. A 5G ProSe Intermediate UE-to-Network Relay may stored it in the discovery entry and included it in the 5G ProSe UE-to-Network Relay Discovery Announcement message. This information can be used in the relay selection at the 5G ProSe Remote UE or other 5G ProSe Intermediate UE-to-Network Relays.
- (optional) Accumulated QoS for PC5 link: this reflects the QoS supported over all the PC5 links to the Root Relay, i.e. the 5G ProSe UE-to-Network Relay, for this RSC.
- (optional) Hop-Limit: this is the hop limit set by the announcing 5G ProSe UE-to-Network Relay to a value smaller than the configured maximum number of hops.
The following parameters are used for the 5G ProSe UE-to-Network Relay Discovery Solicitation message (Model B), where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and Discoverer Info and Relay Service Code are contained in the message:
- Source Layer-2 ID: the 5G ProSe Remote-UE self-selects a Source Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery.
- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery is selected based on the configuration as described in clause 5.1.4.1.
- Discoverer Info: provides information (i.e. User Info ID) about the discoverer user.
- Target Info: provides information (i.e. User Info ID) about the targeted discoveree user.
- Relay Service Code: information about connectivity that the discoverer UE is interested in. The Relay Service Codes are configured in the 5G ProSe Remote UEs interested in related connectivity services.
To support Multi-hop 5G ProSe UE-to-Network Relay discovery the following parameters are added:
- (Optional) Hop count: indicates the number of hops that the message is already relayed. It is increased by 1 per hop.
- (Optional) Hop-Limit: a unmodified value that indicates the hop limit of the message. It is set, by the 5G ProSe Remote UE, to a value smaller than the (pre)configured maximum number of hops.
- Path information: an (ordered) list of User Info ID(s) of Intermediate UE-to-Network Relay(s) that indicates the transmitted path of the message.
- (optional) Accumulated QoS for PC5 link: this reflects the QoS supported over all the PC5 links starting from the PC5 link between the Remote UE and a Intermediate UE-to-Network Relay in the path information for this RSC.
The following parameters are used in the 5G ProSe UE-to-Network Relay Discovery Response message (Model B), where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and Discoveree Info and Relay Service Code are contained in the message:
- Source Layer-2 ID: the 5G ProSe UE-to-Network Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery.
- Destination Layer-2 ID: set to the Source Layer-2 ID of the received 5G ProSe UE-to-Network Relay Discovery Solicitation message.
- Relay Service Code: identifies the connectivity service the 5G ProSe UE-to-Network Relay provides to 5G ProSe Remote UEs that matches the Relay Service Code from the corresponding Discovery Solicitation message.
- Discoveree Info: provides information (i.e. User Info ID) about the discoveree.
To support Multi-hop 5G ProSe UE-to-Network Relay discovery the following parameters are added:
- (Optional) Hop count: indicates the number of hops between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay on the path selected by the 5G ProSe UE-to-Network Relay.
- Path information: an (ordered) list of User Info ID(s) of the discoverer user and the Intermediate UE-to-Network Relay(s) on the path selected by the 5G ProSe UE-to-Network Relay.
- (optional) Accumulated QoS for PC5 link: this reflects the QoS supported over all the PC5 links along the path from Remote UE to the 5G ProSe UE-to-Network Relay for this RSC.
The following parameters may be used in the Relay Discovery Additional Information message (using Model A) based on the procedure defined in clause 6.5.1.3 for 5G ProSe UE-to-Network Relay and clause 6.3.2.5.4 for 5G ProSe multi-hop UE-to-Network Relay where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and the other parameters are contained in the message:
- Source Layer-2 ID: the 5G ProSe UE-to-Network Relay or the 5G ProSe Intermediate UE-to-Network Relay self-selects a Source Layer-2 ID to send the Relay Discovery Additional Information message.
- Destination Layer-2 ID: the Destination Layer-2 ID to send the Relay Discovery Additional Information message is selected based on the configuration as described in clause 5.1.4.1.
- Relay Service Code: the Relay Service Code associated with the message. The Relay Service Code is used to identify the security parameters needed by the receiving UE to process the discovery message.
- Announcer Info: provides information about the announcing user (i.e. User Info ID of the 5G ProSe UE-to-Network Relay).
- Hop-Count: This value reflects the number of PC5 hops for the 5G ProSe Remote UE to reach the network. It is set to 1 by the 5G ProSe UE-to-Network Relay and shall be incremented by 1 every time the Relay Discovery Additional Information message is forwarded by a 5G ProSe Intermediate UE-to-Network Relay.
A 5G ProSe Intermediate UE-to-Network Relay shall only process the Relay Discovery Additional Information message if the Hop-Count is present and the value is less than the (pre-)configured maximum number of hops for the associated RSC and the optional Hop-Limit in the message.
- Announcer Info of 5G ProSe Intermediate UE-to-Network Relay: identify information (i.e. User Info ID) of the 5G ProSe Intermediate UE-to-Network Relay connected to 5G ProSe UE-to-Network Relay. This parameter is only applicable to the additional parameter announcement procedure over 5G ProSe multi-hop UE-to-Network Relay specified in clause 6.3.2.5.4.
- (optional) Hop-Limit: this is the hop limit set by the announcing 5G ProSe UE-to-Network Relay to a value smaller than the configured maximum number of hops.
- Additional parameters: the additional parameters for 5G ProSe Layer-3 UE-to-Network Relay (when applicable) are defined in clause 5.8.3.2.
NOTE 1: The UE implementation needs to ensure that when the UE self-selects Source Layer-2 IDs, the self-selected Source Layer-2 IDs are different between 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery) in clause 6.3.2 and 5G ProSe Direct Communication (including 5G ProSe UE-to-Network Relay Communication) in clause 6.4 and are different from any other provisioned Destination Layer-2 IDs as described in clause 5.1 and any other self-selected Source Layer-2 IDs used in a simultaneous 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery) with a different discovery model.
NOTE 2: If a 5G ProSe UE-to-Network Relay and 5G ProSe Remote UE from different PLMNs discover each other, it means that the Relay Service Code is associated with the same connectivity service and the same Relay Service Code is provisioned based on Service Level Agreement among PLMNs.
NOTE 3: The Hop count, Hop-Limit and Path information are used for multi-hop 5G ProSe UE-to-Network Relay Discovery with Model B. The multi-hop UE-to-Network Relay Discovery message has no impact on 5G ProSe UE-to-Network Relay or 5G ProSe Remote UE that only supports the single-hop UE-to-Network Relay. Single-hop and Multi-hop UE-to-Network Relays discoveries can be distinguished based on RSC.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.3.2 Identifiers for 5G ProSe Layer-3 UE-to-Network Relay
|
For 5G ProSe Layer-3 UE-to-Network relay, a Relay Service Code in the Announcement Message is associated with a set of PDU session parameters (e.g. PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference). The Relay Service Code may also represent if the relay UE can provide secure N3IWF connection.
For 5G ProSe Layer-3 Remote UE discovering 5G ProSe Layer-3 UE-to-Network relay, the Relay Service Code in the Solicitation Message represents the PDU session parameters that a PDU session of the relay should be able to support. The Relay Service Code may also represent if the remote UE requires secure N3IWF connection.
The following additional parameters may be used in the Relay Discovery Additional Information message (using Model A) for 5G ProSe Layer-3 UE-to-Network Relay:
- NCGI: indicates the NCGI of the serving cell of the 5G ProSe Layer-3 UE-to-Network Relay. This parameter may be requested by application running on 5G ProSe Layer-3 Remote UE.
- TAI: indicates the Tracking Area Identity of the serving cell of the 5G ProSe Layer-3 UE-to-Network Relay. This parameter may be used by 5G ProSe Layer-3 Remote UE to select a N3IWF.
- NCGI of 5G ProSe Intermediate UE-to-Network Relay: indicates the NCGI of the serving cell of the 5G ProSe Intermediate UE-to-Network Relay connected to the 5G ProSe UE-to-Network Relay. This parameter may be requested by application running on 5G ProSe Layer-3 Remote UE and is only applicable to the additional parameter announcement procedure over 5G ProSe multi-hop UE-to-Network Relay specified in clause 6.3.2.5.4.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.3.3 Identifiers for 5G ProSe Layer-2 UE-to-Network Relay
|
The following parameters may be used in Announcement message (Model A) or Response message (Model B) in addition to the parameters as specified in clause 5.8.3.1:
- NCGI: indicates the NCGI of the serving cell of the 5G ProSe Layer-2 UE-to-Network Relay for 5G ProSe Layer-2 UE-to-Network Relay (re)selection.
- RRC Container: An RRC container, as defined in TS 38.331 [16], which includes the cell access related information for the serving cell of the 5G ProSe Layer-2 UE-to-Network Relay.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.4 Identifiers for 5G ProSe UE-to-UE Relay Discovery
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.4.1 General
|
The 5G ProSe UE-to-UE Relay Discovery message contains two sets of identifiers, a Direct Discovery set and a UE-to-UE Relay Discovery set.
- The Direct Discovery set of identifiers are part of the contents of the 5G ProSe Direct Discovery message as defined in clause 5.8.1. This set of identifiers provides information about the 5G ProSe End UE(s) (e.g. user info (i.e. Application Layer ID)) to be discovered via 5G ProSe UE-to-UE Relay.
- The UE-to-UE Relay Discovery set of identifiers as defined in clause 5.8.4.2 contain information to support the discovery of the 5G ProSe UE-to-UE Relay and extensions of the Direct Discovery.
5G ProSe UE-to-UE Relay shall modify the UE-to-UE Relay Discovery set of identifiers and forward the Direct Discovery set and the UE-to-UE Relay Discovery set of identifiers during the discovery procedures. The Direct Discovery set can be protected using different keys as used to protect the UE-to-UE Relay Discover set according to TS 33.503 [29].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.4.2 Common identifiers for 5G ProSe UE-to-UE Relay Discovery
|
The following parameters are used as UE-to-UE Relay Discovery set of identifiers for the 5G ProSe UE-to-UE Relay Discovery Announcement message (Model A), where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message:
- Source Layer-2 ID: the 5G ProSe UE-to-UE Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Announcement message.
- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Announcement message is selected based on the configuration as described in clause 5.1.5.1.
- User Info ID of 5G ProSe UE-to-UE Relay: provides information about the 5G ProSe UE-to-UE Relay.
- Relay Service Code: information to indicate the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs.
The following parameters are used as UE-to-UE Relay Discovery set of identifiers for the 5G ProSe UE-to-UE Relay Discovery Solicitation message (Model B) between discoverer 5G ProSe End UE and 5G ProSe UE-to-UE Relay, where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message:
- Source Layer-2 ID: the discoverer 5G ProSe End UE self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Solicitation message.
- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Solicitation message is selected based on the configuration as described in clause 5.1.5.1.
- Relay Service Code: information about connectivity service that the discoverer 5G ProSe End UE is interested in.
The following parameters are used as UE-to-UE Relay Discovery set of identifiers in the 5G ProSe UE-to-UE Relay Discovery Response message (Model B) between discoverer 5G ProSe End UE and 5G ProSe UE-to-UE Relay, where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message:
- Source Layer-2 ID: the 5G ProSe UE-to-UE Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Response message.
- Destination Layer-2 ID: set to the Source Layer-2 ID of the received 5G ProSe UE-to-UE Relay Discovery Solicitation message.
- User Info ID of 5G ProSe UE-to-UE Relay: provides information about the 5G ProSe UE-to-UE Relay.
- Relay Service Code: identifies the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs that matches the Relay Service Code from the corresponding Discovery Solicitation message.
The following parameters are used as UE-to-UE Relay Discovery set of identifiers for the 5G ProSe UE-to-UE Relay Discovery Solicitation message (Model B) between 5G ProSe UE-to-UE Relay and discoveree 5G ProSe End UE, where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message:
- Source Layer-2 ID: the 5G ProSe UE-to-UE Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Solicitation message.
When a 5G ProSe UE-to-UE Relay self-selects a Source Layer-2 ID for a received 5G ProSe UE-to-UE Relay Discovery Solicitation message, it selects a different Source Layer-2 ID values for each 5G ProSe UE-to-UE Relay Discovery Solicitation message, so that the 5G ProSe UE-to-UE Relay can correlate the 5G ProSe UE-to-UE Relay Discovery Response message with the 5G ProSe UE-to-UE Relay Discovery Solicitation message. The 5G ProSe UE-to-UE Relay can determine the discoverer 5G ProSe End UE that triggered the 5G ProSe UE-to-UE Relay Discovery Solicitation based on the destination Layer-2 ID of the received 5G ProSe UE-to-UE Relay Discovery Response message.
- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Solicitation message is selected based on the configuration as described in clause 5.1.5.1.
- User Info ID of 5G ProSe UE-to-UE Relay: provides information about the 5G ProSe UE-to-UE Relay.
- Relay Service Code: identifies the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs.
The following parameters are used as UE-to-UE Relay Discovery set of identifiers in the 5G ProSe UE-to-UE Relay Discovery Response message (Model B) between 5G ProSe UE-to-UE Relay and discoveree 5G ProSe End UE, where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message:
- Source Layer-2 ID: the discoveree 5G ProSe End UE self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Response message.
- Destination Layer-2 ID: set to the Source Layer-2 ID of the received 5G ProSe UE-to-UE Relay Discovery Solicitation message.
- Relay Service Code: identifies the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs that matches the Relay Service Code from the corresponding Discovery Solicitation message.
NOTE 1: The UE implementation needs to ensure that when the UE self-selects Source Layer-2 IDs, the self-selected Source Layer-2 IDs are different between 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery) in clause 6.3.2 and 5G ProSe Direct Communication (including 5G ProSe UE-to-Network Relay Communication and 5G ProSe UE-to-UE Relay Communication) in clause 6.4, 6.5 and 6.7 and are different from any other provisioned Destination Layer-2 IDs as described in clause 5.1 and any other self-selected Source Layer-2 IDs used in a simultaneous 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery) with a different discovery model.
NOTE 2: If a 5G ProSe UE-to-UE Relay and 5G ProSe End UEs from different PLMNs discover each other, it means that the Relay Service Code is associated with the same connectivity service and the same Relay Service Code is provisioned based on Service Level Agreement among PLMNs.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.5 Identifiers for 5G ProSe UE-to-UE Relay Communication with integrated Discovery
|
For the broadcast Direct Communication Request message over the first hop PC5 reference point, the Source Layer-2 ID is self-selected by the source 5G ProSe End UE and the Destination Layer-2 ID is selected based on the configuration as described in clause 5.1.
For the broadcast Direct Communication Request message over the second hop PC5 reference point, the Source Layer-2 ID is self-selected by the 5G ProSe UE-to-UE Relay and the Destination Layer-2 ID is selected based on the configuration as described in clause 5.1.
5G ProSe UE-to-UE Relay may send a unicast Direct Communication Request message to the target 5G ProSe End UE by setting the Destination Layer-2 ID with a received unicast Destination Layer-2 ID of the target 5G ProSe End UE as specified in clause 6.4.3.7. The Source Layer-2 ID is self-selected by the 5G ProSe UE-to-UE Relay.
For unicast Direct Communication Accept message, the Source Layer-2 ID is self-selected by the target 5G ProSe End UE or 5G ProSe UE-to-UE Relay.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.6 Identifiers for 5G ProSe Multi-hop UE-to-UE Relay Discovery
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.6.1 General
|
There are two types of discovery mechanisms for the support of 5G ProSe Multi-hop UE-to-UE Relays, i.e. for IP PDU type and for non-IP PDU type (Ethernet or Unstructured). The 5G ProSe End UE and 5G ProSe Multi-hop UE-to-UE Relay choose the discovery mechanism based on the associated indication of the RSC, as defined in clause 5.1.5.1.
The identifiers used for the two types of discovery mechanisms are specified in clause 5.8.6.2 and clause 5.8.3 respectively.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.6.2 Identifiers for 5G ProSe Multi-hop UE-to-UE Relay discovery of IP PDU type
|
The Multi-hop UE-to-UE Relay Discovery Announcement message (Model A) is sent by the relay and contains the following information:
- Source Layer-2 ID: the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay self-selects a Source Layer-2 ID. It is used for the transmitting the message at AS layer and included in the AS layer headers only.
- Destination Layer-2 ID: the Destination Layer-2 ID for Multi-hop UE-to-UE Relay Discovery Announcement message (Model A) is selected based on the configuration (associated with the RSC) as defined in clause 5.1.5.1.
- User Info ID of 5G ProSe Multi-hop UE-to-UE Relay: provides information about the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay.
- Relay Service Code: information to indicate the connectivity service the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay provides to the 5G ProSe End UEs.
The 5G ProSe Multi-hop UE-to-UE Relay Discovery Solicitation message (Model B) is sent by the source 5G ProSe End UE or a 5G ProSe Layer-3 Multi-hop UE-to-UE Relay and includes the following information:
- Source Layer-2 ID: the discoverer 5G ProSe End UE or 5G ProSe Layer-3 Multi-hop UE-to-UE Relay self-selects a Source Layer-2 ID.
- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe Multi-hop UE-to-UE Relay Discovery Solicitation message is selected based on the configuration (associated with the RSC) as defined in clause 5.1.5.1.
User Info of discoverer: provides information about the sender of the Solicitation message.
- (optional) User Info ID of 5G Prose UE-to-UE Relay: this may be used by the receiver of the message to determine whether to respond to the solicitation. It is only included when the sender wants to find a specific target relay.
- Relay Service Code: information about connectivity service offered by the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay(s).
The 5G ProSe UE-to-UE Relay Discovery Response message (Model B) sent by the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay(s) matching the RSC includes the following:
- Source Layer-2 ID: the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay self-selects a Source Layer-2 ID.
- Destination Layer-2 ID: set to the Source Layer-2 ID of the received 5G ProSe Multi-hop UE-to-UE Relay Discovery Solicitation message.
- User Info of discoverer: the User Info from the received Solicitation message, to ensure the response can be matched at the receiver.
- User Info ID of 5G ProSe UE-to-UE Relay: provides information about the 5G ProSe Multi-hop UE-to-UE Relay sending the Response message.
- Relay Service Code: information about connectivity service offered by the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.8.6.3 Identifiers for 5G ProSe Multi-hop UE-to-UE Relay discovery of non-IP PDU type
|
The 5G ProSe UE-to-UE Relay Discovery Announcement message (Model A) is sent by the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay and contains the following parameters for multi-hop relaying in addition to as described in clause 5.8.4:
- For each user info in the Direct Discovery set:
- Hop count: indicates the number of hops that the message is already relayed. It is increased by 1 per hop.
- (Optional) Hop-Limit: value that indicates the limit of the number of hops of the message.
- Path information: an (ordered) list of User Info ID(s) of Multi-hop UE-to-UE Relay(s) that indicates the transmitted path of the message. Path information also includes source layer-2 ID of discoverer Prose End UE.
The 5G ProSe UE-to-UE Relay Discovery Solicitation message (Model B) is sent by the source 5G ProSe End UE and includes the following parameters for multi-hop relaying in addition to as described in clause 5.8.4:
- Hop count: indicates the number of hops that the message is already relayed. It is set to 0 initially by the Discoverer End UE and is increased by 1 per hop.
- (Optional) Hop-Limit: value that indicates the limit of the number of hops of the message. It is set, by the 5G ProSe Remote UE, to a value smaller than or equal to the (pre)configured maximum number of hops.
The 5G ProSe UE-to-UE Relay Discovery Solicitation message (Model B) is sent by the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay(s) matching the RSC and includes the following parameters for multi-hop relaying in addition to as described in clause 5.8.4:
- Hop count: indicates the number of hops that the message is already relayed. It is increased by 1 per hop.
- (Optional) Hop-Limit: value that indicates the limit of the number of hops of the message. It is set, by the 5G ProSe Remote UE, to a value smaller than or equal to the (pre)configured maximum number of hops.
- Path information: an (ordered) list of User Info ID(s) of Multi-hop UE-to-UE Relay(s) that indicates the transmitted path of the message. Path information also includes source layer-2 ID of discoverer UE.
The 5G ProSe UE-to-UE Relay Discovery Response message (Model B) sent by the 5G ProSe Layer-3 Multi-hop UE-to-UE Relay(s) matching the RSC includes the following parameters for multi-hop relaying in addition to as described in clause 5.8.4:
- Hop count: indicates the number of hops that the message is already relayed.
- Path information: an (ordered) list of User Info ID(s) of Multi-hop UE-to-UE Relay(s) that indicates the transmitted path of the message. Path information also includes source layer-2 ID of discoverer Prose End UE.
The 5G ProSe UE-to-UE Relay Discovery Response message (Model B) sent by the target 5G ProSe End UE matching the RSC includes the following the following parameters for multi-hop relaying in addition to as described in clause 5.8.4:
- Hop count: indicates the number of hops that the message is already relayed.
- Path information: an (ordered) list of User Info ID(s) of Multi-hop UE-to-UE Relay(s) that indicates the transmitted path of the message. Path information also includes source layer-2 ID of discoverer Prose End UE.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.9 Support for 5G ProSe for UEs in limited service state
|
For UE in limited service state, as defined in TS 23.122 [14], 5G ProSe can be used over PC5 reference point with the following considerations.
UEs that are authorized to use 5G ProSe over PC5 reference point according to clause 5.1 shall be able to use the corresponding services following the principles defined in clause 5.1.2.2 for 5G ProSe Direct Discovery, clause 5.1.3.2 for 5G ProSe Direct Communication, clause 5.1.4.2 for 5G ProSe UE-to-Network Relay and clause 5.1.5.2 for 5G ProSe UE-to-UE Relay when the UE enters in limited service state in 5GS:
- because UE cannot find a suitable cell of the selected PLMN as described in TS 23.122 [14]; or
- as the result of receiving one of the following reject reasons defined in TS 23.122 [14]:
- a "PLMN not allowed" response to a registration request or;
- a "5GS services not allowed" response to a registration request or service request.
A UE in limited service state shall only use the radio resources and procedure available in CM-IDLE mode for ProSe over PC5 reference point, for details see TS 36.300 [11] and TS 38.300 [12].
UEs shall not use 5G ProSe over PC5 reference point using the "operator-managed" radio resources, as specified in clauses 5.1.2.1, 5.1.3.1, 5.1.4.1 and 5.1.5.1, if the UE has entered in limited service state due to all other situations (e.g. no SIM in the MS, an "illegal MS" or "illegal ME" response to a registration request, or an "IMSI unknown in HLR" response to a registration request) defined in TS 23.122 [14], where the UE is unable to obtain normal service from a PLMN. The UEs may use ProSe over PC5 reference point using the "non-operator-managed" radio resources, as specified in clauses 5.1.2.1, 5.1.3.1, 5.1.4.1 and 5.1.5.1, according to the corresponding principles defined in clauses 5.1.2.2, 5.1.3.2, 5.1.4.2 and 5.1.5.2.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.10 PC5 operation in EPS for Public Safety UE
|
When the UE is in EPS, the UE shall use the valid ProSe policy and parameters provisioned by the ProSe Function in EPC for ProSe Direct Discovery and Prose Direct Communication. If the UE does not have valid ProSe policy and parameters, the UE shall request the network to provision the ProSe policy and parameters.
The UE that is authorized to perform ProSe Direct Discovery and/or ProSe Direct Communication in EPS can perform the authorized PC5 operation in EPS as specified in TS 23.303 [3].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.11 Communication path selection between PC5 and Uu reference points
|
The "communication path selection between PC5 and Uu reference points" refers to the procedure on how a UE selects a communication path between PC5 reference point and Uu reference point before it communicates with another UE. The communication path over PC5 reference point means that the communication with another UE is performed by using 5G ProSe Direct Communication only. The communication path over Uu reference point means that the communication with another UE is performed via the network.
NOTE 1: The communication via 5G ProSe UE-to-Network Relay (Layer-2 or Layer-3) can be considered as the communication path over Uu reference point, as it involves communication via the network.
Path selection policy is provided to the UE to indicate which path(s) is preferred for all or specific ProSe services (i.e. PC5 preferred, Uu preferred or no preference indicated) as specified in clause 5.1.3.1.
The ProSe Application Server can provide a path preference for ProSe Services to UDR as specified in clause 6.2.5 and this may be used by PCF for path selection policy generation and update as specified in clause 6.2.2.
NOTE 2: ProSe Application Server can use QoS Sustainability analytics defined in TS 23.288 [8] to determine the path preference.
The UE may use the provisioned path selection policy to select the appropriate communication path for all or specific ProSe services.
UE operation related to the path selection for ProSe service is as follows:
- The UE evaluates the path selection policy in the policy and parameters for ProSe Direct Communication applicable to the ProSe service and selects the communication path as below:
- If PC5 preferred is indicated, the UE should prefer to use the PC5 for communication path for the ProSe service.
- If Uu preferred is indicated, the UE should prefer to use the Uu for communication path for the ProSe service.
- If no preference is indicated or no path selection policy is provisioned, the UE selects either a Uu or PC5 communication path based on its pre-configuration or implementation for the ProSe service.
NOTE 3: When either PC5 preferred or Uu preferred is indicated, the UE can still select the other non-preferred path, e.g. because the peer UE is not in proximity.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.12 NAS level congestion control for 5G ProSe UE-to-Network Relay
|
The 5G ProSe UE-to-Network Relay may be subject to NAS level congestion control, as specified in clause 5.19.7 of TS 23.501 [4].
Both 5G ProSe Layer-2 UE-to-Network Relays and Layer-3 UE-to-Network Relays, when NAS Mobility Management congestion control as specified in clause 5.19.7.2 of TS 23.501 [4] is activated, i.e. the 5G ProSe UE-to-Network Relay receives a Mobility Management back-off timer from the AMF, the 5G ProSe UE-to-Network Relay is not able to serve the 5G ProSe Remote UE after the 5G ProSe UE-to-Network Relay enters CM_IDLE state. If the 5G ProSe UE-to-Network Relay has a Mobility Management back-off timer when it enters CM_IDLE state the 5G ProSe UE-to-Network Relay releases the PC5 connections with its 5G ProSe Remote UEs indicating it is temporarily not available, so the Remote UE can (re)select another 5G ProSe UE-to-Network Relay. The 5G ProSe UE-to-Network Relay does not perform UE-to-Network Relay Discovery as described in clause 6.3.2.3 and does not accept any PC5 connections for relaying until the back-off timer expires if the 5G ProSe UE-to-Network Relay is in CM_IDLE state.
A Remote UE may also be subject to NAS level congestion control as specified in TS 23.501 [4].
NOTE: The form of the temporarily not available indication will be determined by stage 3.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.13 Support for PC5 DRX operations
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.13.1 General
|
PC5 DRX operations are supported to enable 5G ProSe-enabled UE power saving for the following functions:
- 5G ProSe Direct Discovery;
- Unicast, groupcast and broadcast mode 5G ProSe Direct Communication;
- 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-Network Relay Communication;
- 5G ProSe UE-to-UE Relay Discovery and 5G ProSe UE-to-UE Relay Communication.
Support for PC5 DRX operations in the AS layer is specified in TS 38.300 [12].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.13.2 PC5 DRX operations for 5G ProSe Direct Discovery, 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery
|
For 5G ProSe Direct Discovery, 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery when the UE is "not served by NG-RAN", the UE uses the provisioned default PC5 DRX configuration for PC5 DRX operation as specified in clause 5.1.2.1, clause 5.1.4.1 and clause 5.1.5.1, respectively.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.13.3 PC5 DRX operations for 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay Communication and 5G ProSe UE-to-UE Relay Communication
|
The ProSe layer determines the respective ProSe services (i.e. ProSe identifiers) and derives the corresponding PC5 QoS parameters based on either the mapping of ProSe services (i.e. ProSe identifiers) to PC5 QoS parameters, or the ProSe Application Requirements for the ProSe services (i.e. ProSe identifiers) provided by the application layer. For broadcast and groupcast, the ProSe layer also determines the NR Tx Profile based on the mapping of ProSe services (i.e. ProSe identifiers) to NR Tx Profiles as described in clause 5.1.3.1. The ProSe layer passes the PC5 QoS parameters and destination Layer-2 ID to the AS layer as specified in clauses 6.4.1, 6.4.2 and 6.4.3. The ProSe layer also passes the corresponding NR Tx Profile to the AS layer, if the ProSe layer has determined the corresponding NR Tx Profile.
NOTE: For broadcast and groupcast, the AS layer needs PC5 QoS parameters as well to determine the PC5 DRX parameter values for reception operation over PC5 reference point. Therefore, the ProSe layer determines the interested ProSe services (i.e. ProSe identifiers) and derives the PC5 QoS parameters based on its reception needs besides the transmission needs. How to derive the PC5 QoS parameters based on its reception needs (e.g. without establishing the PC5 QoS Flows) depends on UE implementation.
For broadcast or groupcast, the ProSe layer maintains a list of all ProSe services (i.e. ProSe identifiers), i.e. activated ProSe services and/or ProSe services that the UE is interested for reception, for a given destination Layer-2 ID and determines the NR Tx Profile to be mapped for the respective ProSe service based on the configuration described in clause 5.1.3.1. Whenever the list of the ProSe services for a given destination Layer-2 ID changes, the ProSe layer updates the AS layer for the NR Tx Profiles information by providing all the mapped NR Tx Profiles to the AS layer for the given destination Layer-2 ID, e.g. when providing other information such as the destination Layer-2 ID, PC5 QoS parameters.
For broadcast, the mapping from destination Layer-2 ID to NR Tx Profile is configured in the NG-RAN. The NG-RAN may derive the NR Tx Profile from the destination Layer-2 ID to perform the network scheduled operation mode, alignment of Uu DRX and PC5 DRX, etc.
When the PC5 DRX operation is needed, the AS layer determines the PC5 DRX parameter values for 5G ProSe Direct Communication or 5G ProSe UE-to-Network Relay Communication over PC5 reference point, taking into account, e.g. PC5 QoS parameters and/or destination Layer-2 ID provided by the ProSe layer.
For broadcast and groupcast, the UE enables the PC5 DRX based on the NR Tx Profile.
For unicast mode 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay Communication and 5G ProSe UE-to-UE Relay Communication, two UEs may negotiate the PC5 DRX configuration in the AS layer and the PC5 DRX parameter values can be configured per pair of source and destination Layer-2 IDs in the AS layer. For transmitting and receiving Direct Communication Request messages, a default PC5 DRX configuration may be used (see TS 38.300 [12]).
For broadcast and groupcast when the UE is "not served by NG-RAN", the UE uses the provisioned PC5 DRX configuration for PC5 DRX operation as specified in clause 5.1.3.1.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.14 5G ProSe UE-to-UE Relay Communication
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.14.1 5G ProSe Layer-3 UE-to-UE Relay Communication
|
The 5G ProSe Layer-3 UE-to-UE Relay shall provide generic function that can relay any IP, Ethernet or Unstructured traffic.
The 5G ProSe Layer-3 UE-to-UE Relay provides the functionality to support connectivity between 5G ProSe Layer-3 End UEs. A 5G ProSe Layer-3 UE-to-UE Relay and 5G ProSe Layer-3 End UEs can be located within NG-RAN coverage or outside of NG-RAN coverage.
The type of traffic supported over PC5 reference point is indicated by the 5G ProSe Layer-3 UE-to-UE Relay e.g. using the corresponding RSC.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.14.2 5G ProSe Layer-2 UE-to-UE Relay Communication
|
The 5G ProSe Layer-2 UE-to-UE Relay provides forwarding functionality that can relay any type of traffic over the PC5 link.
The 5G ProSe Layer-2 UE-to-UE Relay provides the functionality to support connectivity between 5G ProSe Layer-2 End UEs. A 5G ProSe Layer-2 UE-to-UE Relay and 5G ProSe Layer-2 End UEs can be located within NG-RAN coverage or outside of NG-RAN coverage.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.14.3 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.14.3.1 General
|
Two types of 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communications are supported, i.e. IP based and non-IP based (for Ethernet or Unstructured).
Different RSCs are used for the two types of communications. Different discovery and link management procedures are used.
NOTE: Ethernet or Unstructured traffics between 5G ProSe End UEs may be carried over IP based 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication links by encapsulated them within IP packets. 5G ProSe End UEs can modify the established Layer-2 link to add the corresponding IP flows encapsulating the non-IP traffic as specified in clause 6.7.5.2.1.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.14.3.2 IP based 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication
|
The RSC configuration as defined in defined in 5.1.5.1 indicates if IP based 5G ProSe Layer-3 Multi-hop UE-to-UE Relay communication is used. The 5G ProSe Multi-hop UE-to-UE Relays supporting the same RSC establishe IP based Layer-2 links with each other and form a relay cloud to provide IP connectivity for 5G ProSe End UEs connected to any of the 5G ProSe Multi-hop UE-to-UE Relays.
NOTE: If a 5G ProSe Multi-hop UE-to-UE Relay support multiple RSCs, different Layer-2 links will be established, with each associated with a specific RSC. The 5G ProSe UE-to-UE Relay operates as separate logical entities in the separate relay clouds of different RSCs, i.e. no routing table sharing and no traffic forwarding across different relays clouds of different RSCs.
The 5G ProSe End UE may establish multiple Layer-2 links with different 5G ProSe UE-to-UE Relays supporting the same RSC, in order to maximize the reachability (e.g. in some cases, different 5G ProSe UE-to-UE Relays may serve different disjointed IP subnets).
Mobile Ad-hoc Network (MANET) based routing protocols are used over the IP connectivies in the relay cloud to provide multi-hop forwarding functionality between 5G ProSe End UEs. Each of the 5G ProSe Multi-hop UE-to-UE Relay acts as a MANET router. The exact MANET routing protocols to be supported, e.g. Neighborhood Discovery Protocol (NHDP) [36], OLSRv2 [35], are associated with the RSCs based on configuration.
Based on configuration associated with the RSC, the 5G ProSe End UE obtains the IP address/prefix in two options:
- Each of the 5G ProSe End UE may be configured with a routable IP address/prefix associated with the RSC. This IP address/prefix does not change when the 5G ProSe End UE changes the connections with 5G ProSe Multi-hop UE-to-UE Relays.
- If the 5G ProSe End UE does not have an IP address/prefix configured for the RSC, it obtains an IP address/prefix from the 5G ProSe UE-to-UE Relay it connects to. In this case, the 5G ProSe End UE may need to change the IP address/prefix when it changes its connection to another 5G ProSe UE-to-UE Relay.
The 5G ProSe End UE obtains the IP address/prefix of the target 5G ProSe End UE via DNS queries (per RSC). 5G ProSe Multi-hop UE-to-UE Relay needs to support DNS operations.
Once the 5G ProSe Multi-hop UE-to-UE Relay becomes aware of the 5G ProSe End UE's IP address/prefix, the 5G ProSe Multi-hop UE-to-UE Relay propagates the related DNS information (i.e. User Info ID and associated IP address/prefix) to all other 5G ProSe Multi-hop UE-to-UE Relays connected to the same MANET (i.e. corresponding to the same RSC) using a dedicated MANET Discovery Info message. The MANET Discovery Info message is diffused throughout the MANET using Multipoint Relay flooding (MPR flooding) as defined in IETF RFC 7181 [35], if available. If MPR flooding is not available, then the MANET Discovery Info message is diffused using simple flooding i.e. by transmitting a copy of the MANET Discovery Info message on all interfaces except the one on which the message has been received.
The MANET Discovery Info message is based on the generalized MANET message format defined in IETF RFC 5444 [37]. The 5G ProSe Multi-hop UE-to-UE Relay initiating the sending of the MANET Discovery Info message controls the propagation depth of the MANET Discovery Info message based on the configured "maximum number of hops per RSC" as specified in 5.1.5.1a or based on the Hop Limit if provided by the target End UE, by using the built-in mechanism defined in IETF RFC 5444 [37].
When a 5G ProSe Multi-hop UE-to-UE Relay detects an End UE is no longer connected (e.g. the PC5 link is released), it may delete the corresponding DNS entry and initiate MANET Discovery Info message to enable other 5G ProSe Multi-hop UE-to-UE Relay(s) to delete the corresponding DNS entry. The propagation depth of the MANET Discovery Info message is controlled based on the configured hop limit.
When MANET protocol determines the route for IP forwarding, layer-2 link QoS and hop counts can be refelected, e.g. with the Link Metrics value as defined in OLSRv2 [35]. The 5G ProSe Multi-hop UE-to-UE Relay can also enforce the configured hop limit based on the link metrics when building the routing tables, e.g. ignore the route that exceeds the threshold derived from hop limit.
If 5G ProSe Multi-hop UE-to-UE Relay has traffic for its own, it can use any IP address it owns for the transmission.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.15 Path switching between two UE-to-Network Relays
|
If relay reselection has been triggered (see clause 6.5.3), the 5G ProSe Remote UE performs the path switching between two UE-to-Network Relays based on the URSP rules of the 5G ProSe Remote UE traffic handling described in clause 6.5.4, 5G ProSe Policy in clause 5.1.4, or information from application layer (if available) with following considerations:
- The 5G ProSe Remote UE shall first select the target path which has same type with the original path (i.e. 5G ProSe Layer-2 UE-to-Network Relay, 5G ProSe Layer-3 UE-to-Network Relay with N3IWF and 5G ProSe Layer-3 UE-to-Network Relay without N3IWF), by using the RSC associated with the original path.
- If the same type target path is not available, then this 5G ProSe Remote UE re-evaluates the URSP as specified in clause 6.5.4, or 5G ProSe Policy in clause 5.1.4 for the target path selection.
NOTE: If there is the information from the application layer (e.g. provided by an application server), the 5G ProSe Remote UE can use this information to discover the target 5G ProSe UE-to-Network Relay UE. If there are multiple discovered 5G ProSe UE-to-Network Relay UEs, the 5G ProSe Remote UE selects the target 5G ProSe UE-to-Network Relay based on the priority, if any, in the information from the application layer.
The principles from the 5G ProSe Policy in clause 5.1.4 and URSP rules of the 5G ProSe Remote UE traffic handling described in clause 6.5.4 take the higher priority than the information from the application layer.
The path switching procedures between two indirect network communication paths are as described in clause 6.5.5.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.16 Communication path switching between PC5 and Uu reference points
|
The "communication path switching between PC5 and Uu reference points" refers to the procedure on how a UE switches between Uu communication path and direct PC5 communication path when it is communicating with another UE as illustrated in Figure 5.16-1. The direct communication path over PC5 reference point means that the communication with another UE is performed by using 5G ProSe Direct Communication only. The communication path over Uu reference point means that the communication with another UE is performed via the network.
Figure 5.16-1: Example scenario of communication path switching between PC5 and Uu reference points (i.e. switching between Figure a and Figure b)
Communication path switching between PC5 and Uu reference points is performed at ProSe service level, e.g. some of ProSe services of PC5 unicast link or PDU Session, all ProSe services of PC5 unicast link or PDU Session.
The UE takes the path selection policy into account to determine whether and for which ProSe service(s) to switch the communication path. UE operation related to the path switch for ProSe service is as follows:
- The UE evaluates the path selection policy in the policy and parameters for ProSe Direct Communication applicable to the ProSe service and switches the communication path as below:
- If the Uu path is used and PC5 preferred is indicated, the UE should prefer to switch to the PC5 communication path for the ProSe service.
- If the PC5 path is used and Uu preferred is indicated, the UE should prefer to switch to the Uu communication path for the ProSe service.
- If no preference is indicated or no path selection policy is provisioned, the UE switches between Uu and PC5 communication path based on its pre-configuration or implementation for the ProSe service.
NOTE 1: When either PC5 preferred or Uu preferred is indicated, the UE can still switch to the other non-preferred path, e.g. signal strength of any path below a certain configured signal strength threshold.
The UE may decide to perform path switching from Uu path to PC5 path, e.g. because the peer UE is in proximity or for offloading some traffic from the network. The UE may decide to perform path switching from PC5 path to Uu path, e.g. when the PC5 signal strength of the unicast link with the peer UE becomes weak.
At path switching, the same traffic type between for PDU Session and for PC5 unicast link is maintained, i.e. IP type, Ethernet type and Unstructured type.
For communication path switching from PC5 to Uu reference point, the Uu QoS parameters of each UE are decided based on PC5 QoS parameters and negotiated via the existing PC5 connection between two UEs. Each UE may perform the UE requested PDU Session Modification as defined in TS 23.502 [5] clause 4.3.3 to request the Uu QoS parameters. For IP type traffic, the IP addresses/prefixes of the peer UEs over the Uu reference point can be shared via the existing PC5 connection between the UEs by using application layer signalling to assist them to establish communication with each other via the communication path over the Uu reference point.
When both Uu path and PC5 path are available, a make-before-break mechanism is used when switching between PC5 path and Uu path. That is, the UEs first prepare the target path to communicate with each other and then perform the path switching and communicate over the target path and after this the former path may be released.
NOTE 2: It is not targeted to support session continuity (e.g. IP address preservation) during path switching between PC5 and Uu reference points.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.17 Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.17.1 General
|
Multi-path communication uses one direct network communication path and one indirect network communication path with UE-to-Network Relay as illustrated in Figure 5.17.1-1, where path #1 shows the direct communication path via Uu and path #2 is shows the indirect communication path via 5G ProSe UE-to-Network Relay.
Figure 5.17.1-1: Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay
The indirect communication path may be via a 5G ProSe Layer-2 UE-to-Network Relay, or via a 5G ProSe Layer-3 UE-to-Network Relay with or without N3IWF.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.17.2 Multi-path communication via direct Uu path and via 5G ProSe Layer-3 UE-to-Network Relay
|
A 5G ProSe Layer-3 Remote UE may access the network via a 5G ProSe Layer-3 UE-to-Network Relay with or without N3IWF.
When a 5G ProSe Layer-3 Remote UE accesses the network via a 5G ProSe Layer-3 UE-to-Network Relay without N3IWF, the multi-path communication via direct Uu path and via the UE-to-Network Relay may be applied to the application traffic.
When a 5G ProSe Layer-3 Remote UE accesses the network via a 5G ProSe Layer-3 UE-to-Network Relay with N3IWF, the Layer-3 Remote UE connection via Layer-3 UE-to-Network Relay with N3IWF is considered as "untrusted non-3GPP access to 5GC via N3IWF", therefore the multi-path communication can be achieved using MA PDU Session in ATSSS features specified in clause 5.32 of TS 23.501 [4].
NOTE: MA PDU Session requires ATSSS Information in SM subscription data as specified in TS 23.502 [5].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
5.18 Support of Public Warning Notification Relaying
|
As specified in TS 22.268 [33], if UE that is authorised to act as 5G ProSe UE-to-Network Relay receives Public Warning Notification from the network and the UE is configured to perform Public Warning relaying, it shall handle the Public Warning message acting in the role of 5G ProSe UE-to-Network Relay.
The 5G ProSe UE-to-Network Relay broadcasts the warning message i.e. SIB 6/7/8 received from the network to the 5G ProSe Remote UE(s) by using Broadcast mode of 5G ProSe direct communication as specified in clause 5.3.2. The 5G ProSe UE-to-Network Relay uses a configured Destination Layer-2 ID(s) as specified in clause 5.1.4.1 when broadcasting the warning message and the 5G ProSe Remote UE receives warning messages broadcasted over PC5 reference point by using a configured Destination Layer-2 ID(s) as specified in clause 5.1.4.1. The PC5 QoS parameters as specified in clause 5.1.4.1 are used to broadcast and receive the warning message for the 5G ProSe UE-to-Network Relay and the 5G ProSe Remote UE, respectively.
If the UE that is authorized to act as a 5G ProSe Intermediate UE-to-Network Relay receives the broadcasted warning message and the UE is configured to perform Public Warning relaying, it shall broadcast the message and increment the Hop-Count value, or add a Hop-Count set to 2 into the message if it is not present. The 5G ProSe Intermediate UE-to-Network Relay shall not broadcast the warning message if the Hop-Count value is larger than the stored Hop-Count in its discovery entry.
A 5G ProSe Remote UE can receive the broadcasted warning message without establishing a connection to the 5G ProSe UE-to-Network Relay or 5G ProSe Intermediate UE-to-Network Relay.
The 5G ProSe UE-to-Network Relay performs the duplication detection function as specified in TS 23.041 [32] to suppress the received duplicated warning messages over Uu. The 5G ProSe Intermediate UE-to-Network Relay and 5G ProSe UE-to-Network Remote UE performs the duplication detection function as specified in TS 23.041 [32] to detect duplicated warning messages received over PC5 and/or Uu.
NOTE: The duplication detection function in the 5G ProSe UE-to-Network Relay and 5G ProSe Intermediate UE-to-Network Relay avoids broadcasting the duplicated warning message over PC5.
If the 5G ProSe Layer-2 UE-to-Network Relay does not have Destination Layer-2 ID to broadcast Public Warning messages, the 5G ProSe Layer-2 UE-to-Network Relay forwards the PWS SIBs (i.e. SIB 6/7/8) to a connected 5G ProSe Layer-2 Remote UE over the unicast link as specified in TS 38.300 [12].
The Public Warning System architecture for 5G System is specified in TS 23.041 [32].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6 Functional description and information flows
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1 Control and user plane stacks
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1 Control Plane
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.1 General
|
The control plane stack consists of protocols for controlling:
- 5G ProSe Direct Discovery, specified in clause 6.1.1.2.1, clause 6.1.1.3, clause 6.1.1.4, clause 6.1.1.5 and clause 6.1.1.6;
- 5G ProSe Direct Communication, specified in clause 6.1.1.2.2;
- 5G ProSe UE-to-Network Relay, specified in clause 6.1.1.7;
- 5G ProSe UE-to-UE Relay, specified in clause 6.1.1.8.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.2 UE - UE
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.2.1 Discovery plane PC5 interface
|
The PC5 communication channel is used to carry the discovery messages over PC5 which are differentiated from other PC5 messages by the AS layer.
Figure 6.1.1.2.1-1 depicts a discovery plane for NR PC5 reference point.
Legend:
- PC5-D: The PDCP/RLC/MAC/PHY functionality is specified in TS 38.300 [12].
- The "ProSe Discovery protocol" is used for handling ProSe Direct Discovery as specified in clause 6.3.2.
Figure 6.1.1.2.1-1: Discovery Plane PC5 Interface
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.2.2 PC5 Signalling Protocol
|
The PC5 Signalling Protocol stack specified in clause 6.1.2 of TS 23.287 [2] is used. The protocol used for the control plane signalling over the PC5 reference point for the secure layer-2 link is specified in clauses 6.4.3, 6.5.1 and 6.5.2.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.3 UE - 5G DDNMF
|
Legend:
- ProSe Control Signalling between UE and 5G DDNMF is carried over the user plane and using the PC3a protocol as specified in TS 24.554 [23].
NOTE 1: PC3a may be realized with one or more protocols.
NOTE 2: If 5G DDNMF is integrated with ProSe Application Server, 5G DDNMF provides PC3a interface towards UE and ProSe Application Server provides PC1 interface towards UE.
Figure 6.1.1.3-1 Control Plane for PC3a Interface
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.4 5G DDNMF – UDM
|
5G DDNMF uses Nudm interface defined in TS 23.501 [4] to obtain the UE's subscription information for the authorization of the 5G ProSe Direct Discovery requests.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.5 5G DDNMF – 5G DDNMF
|
The control plane protocol(s) between 5G DDNMFs are defined in TS 29.500 [30].
The 5G DDNMFs uses N5g-ddnmf 5G DDNMF services defined in clause 7.1 to access the services provided by the other 5G DDNMF(s). The 5G DDNMF in HPLMN uses NRF to discover the 5G DDNMFs in VPLMN and Local PLMNs.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.6 5G DDNMF – ProSe Application Server
|
The 5G System architecture supports the service based Npc2 interface between 5G DDNMF and ProSe Application Server and optionally supports PC2 interface between 5G DDNMF and ProSe Application Server, to enable Proximity Services. See TS 23.501 [4] and TS 23.303 [3].
NOTE: PC2 support between 5G DDNMF and ProSe Application Server is for backwards compatibility for early deployments using Diameter. PC2 interface is used for 5G ProSe Direct Discovery authorization.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.7 5G ProSe UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.7.1 5G ProSe Layer-3 UE-to-Network Relay
|
The UE-UE protocol stacks for discovery and PC5 link management as defined in clause 6.1.1.2 apply to 5G ProSe Remote UE, 5G ProSe Intermediate UE-to-Network Relay and 5G ProSe Layer-3 UE-to-Network Relay. There could be zero, one or multiple 5G ProSe Intermediate UE-to-Network Relay(s) between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay. If there is no 5G ProSe Intermediate UE-to-Network Relay, the IP connection and the PC5 link is between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay.
Additionally, when N3IWF is supported by the 5G ProSe Layer-3 UE-to-Network Relay, the following control plane protocol stack apply.
Legend:
- NAS, EAP-5G and IKEv2 between the Remote UE and the N3IWF are defined in clause 8.2.4 of TS 23.501 [4].
Figure 6.1.1.7.1-1: Control plane protocol stacks between 5G ProSe Layer-3 Remote UE and N3IWF over 5G ProSe Layer-3 UE-to-Network Relay before the signalling IPSec SA is established
Legend:
- NAS, TCP and IPsec between the Remote UE and the N3IWF are defined in TS 23.501 [4] clause 8.2.4.
Figure 6.1.1.7.1-2: Control plane protocol stacks between 5G ProSe Layer-3 Remote UE and N3IWF over 5G ProSe Layer-3 UE-to-Network Relay after the signalling IPSec SA is established
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.7.2 5G ProSe Layer-2 UE-to-Network Relay
|
The UE-UE protocol stacks for discovery and PC5 signalling defined in clause 6.1.1.2 apply to 5G ProSe Remote UE and 5G ProSe Layer-2 UE-to-Network Relay.
Figure 6.1.1.7.2-1 illustrates the protocol stack of the NAS connection for the 5G ProSe Layer-2 Remote UE for NAS-MM and NAS-SM. The NAS messages are transparently transferred between the 5G ProSe Layer-2 Remote UE and NG-RAN over the 5G ProSe Layer-2 UE-to-Network Relay using:
- PDCP end-to-end connection between the 5G ProSe Layer-2 Remote UE and NG-RAN, where the role of the 5G ProSe Layer-2 UE-to-Network Relay is to relay the PDUs over the signalling radio bear without any modifications and using the functionality of the adaptation layer as specified in TS 38.300 [12].
- Connection between NG-RAN and AMF over N2.
- Connection between AMF and SMF over N11.
Figure 6.1.1.7.2-1: End-to-End Control Plane for a Remote UE using Layer-2 UE-to-Network Relay
The control plane protocol stack used by the 5G ProSe Layer-2 UE-to-Network Relay is defined in clause 8.2.2 of TS 23.501 [4].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.8 5G ProSe UE-to-UE Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.8.1 5G ProSe Layer-2 UE-to-UE Relay
|
Figure 6.1.1.8.1-1 illustrates control plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay. Security is established end-to-end between 5G ProSe End UEs as shown by the PDCP layer terminating in the 5G ProSe End UEs.
Figure 6.1.1.8.1-1: End-to-End Control Plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay
NOTE 1: Only the End-to-End control plane protocol stack is shown. The control plane protocol stack of the per-hop PC5 unicast link between 5G ProSe End UEs and 5G ProSe Layer-2 UE-to-UE Relay reuses the PC5-S protocol stack defined in clause 6.1.1.2.
NOTE 2: PC5-S messages over per-hop PC5 unicast links and over End-to-End PC5 unicast links are supported. A End-to-End PC5-S message is the message transferred between the 5G ProSe End UEs and a direct PC5-S message is the message transferred between a 5G ProSe End UE and a 5G ProSe Layer-2 UE-to-UE Relay.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.1.8.2 5G ProSe Layer-3 UE-to-UE Relay
|
The control plane protocol stack of the PC5 unicast link between 5G ProSe End UEs and 5G ProSe Layer-3 UE-to-UE Relay reuses the PC5-S protocol stack defined in clause 6.1.1.2.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.2 User Plane
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.2.1 General
|
The user plane stack consists of protocols for data transmission via:
- 5G ProSe Direct Communication, specified in clause 6.1.2.2;
- 5G ProSe UE-to-Network Relay, specified in clause 6.1.2.3;
- 5G ProSe UE-to-UE Relay, specified in clause 6.1.2.4.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.2.2 UE - UE
|
Figure 6.1.2.2-1 depicts a user plane for NR PC5 reference point, i.e. PC5 User Plane Protocol stack.
Legend:
- PC5-U: The SDAP/PDCP/RLC/MAC/PHY functionality is specified in TS 38.300 [12].
Figure 6.1.2.2-1: User Plane for NR PC5 reference point
PDCP SDU types of IP, Ethernet, Unstructured and Address Resolution Protocol are supported. For IP PDCP SDU type, both IPv4 and IPv6 are supported.
NOTE: Address Resolution Protocol is only supported for broadcast and groupcast mode 5G ProSe Direct Communication.
The packets from ProSe application layer are handled by the ProSe layer before transmitting them to the AS layer, e.g. ProSe layer maps the IP, Ethernet and Unstructured packets to PC5 QoS Flow and marks the corresponding PFI.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.2.3 5G ProSe UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.2.3.1 5G ProSe Layer-3 UE-to-Network Relay
|
Legend:
- GPRS Tunnelling Protocol for the user plane (GTP‑U): This protocol tunnels user data between NG-RAN node and UPF as well as between the UPFs in the backbone network (not shown in the figure). GTP-U shall encapsulate all end user PDU packets.
- SMF controls the user plane tunnel establishment and establishes User Plane Bearers between NG-RAN node and UPF.
- UDP/IP: These are the backbone network protocols used for routing user data and control signalling.
- Uu: The NR Uu radio protocols of NG-RAN between the UE-to-Network Relay and the NG-RAN node are specified in TS 38.300 [12].
- PC5-U: The radio protocols between the UE and the UE-to-Network Relay are specified in clause 6.1.2.2.
Figure 6.1.2.3.1-1: User plane protocol stack for Layer-3 UE-to-Network Relay
Legend:
- IPSec, Inner IP and GRE between the UE and the N3IWF are defined in TS 23.501 [4] clause 8.3.2.
Figure 6.1.2.3.1-2: User plane protocol stacks for Layer-3 UE-to-Network Relay with N3IWF support
There may be zero, one or multiple 5G ProSe Intermediate UE-to-Network Relay(s) between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay. If there is no 5G ProSe Intermediate UE-to-Network Relay, the IP connection and the PC5 link is between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.2.3.2 5G ProSe Layer-2 UE-to-Network Relay
|
Figure 6.1.2.2.2-1 illustrates the protocol stack for the user plane transport, related to a PDU Session, including a 5G ProSe Layer 2 UE-to-Network Relay. The PDU layer corresponds to the PDU carried between the 5G ProSe Layer-2 Remote UE and the Data Network (DN) over the PDU session. The SDAP and PDCP protocols are specified in TS 38.300 [12]. PDCP end-to-end connection is between the 5G ProSe Layer-2 Remote UE and NG-RAN. The functionality of the adaptation layer is specified in TS 38.351 [28].
Figure 6.1.2.3.2-1: End-to-End User Plane Stack for a 5G ProSe Remote UE using 5G ProSe Layer-2 UE-to-Network Relay
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.2.4 5G ProSe UE-to-UE Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.2.4.1 5G ProSe Layer-2 UE-to-UE Relay
|
Figure 6.1.2.4.1-1 illustrates user plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay. Security is established end-to-end between 5G ProSe End UEs as shown by the PDCP layer terminating in the 5G ProSe End UEs.
Figure 6.1.2.4.1-1: End-to-End User Plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay
NOTE: IP, Ethernet and Unstructured traffic types are supported.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.1.2.4.2 5G ProSe Layer-3 UE-to-UE Relay
|
The user plane protocol stack of the PC5 unicast link between 5G ProSe End UEs and 5G ProSe Layer-3 UE-to-UE Relay reuses the user plane protocol stack defined in clause 6.1.2.2.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.2 Procedures for Service Authorization and Provisioning to UE
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.2.1 General
|
The procedures for service authorization and provisioning to UE may be initiated by the PCF (as described in clause 6.2.2), by the UE (as described in clause 6.2.4), or by the AF (as described in clause 6.2.5).
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.2.2 PCF based Service Authorization and Provisioning to UE
|
For PCF based Service Authorization and Provisioning to UE, the Registration procedures as defined in clause 4.2.2.2 of TS 23.502 [5], UE Policy Association Establishment procedure as defined in clause 4.16.11 of TS 23.502 [5] and UE Policy Association Modification procedure as defined in clause 4.16.12 of TS 23.502 [5] apply with the following additions:
- If the UE indicates 5G ProSe Capability in the Registration Request message and if the UE is authorized to use 5G ProSe service based on subscription data, the AMF selects the PCF which supports 5G ProSe Policy/Parameter provisioning as described in clause 6.2.3 and establishes a UE policy association with the PCF for 5G ProSe Policy/Parameter delivery. The AMF reports the authorized 5G ProSe Capability to the selected PCF, which may determine the 5G ProSe Policy/Parameter based on the UE's authorized 5G ProSe Capability.
The PCF may update the 5G ProSe Policy/parameters to the UE in following conditions:
- UE Mobility, e.g. UE moves from one PLMN to another PLMN. This is achieved by using the procedure of UE Policy Association Modification initiated by the AMF, as defined in clause 4.16.12.1 of TS 23.502 [5].
- When there is a subscription change in the list of PLMNs where the UE is authorized to perform 5G ProSe services. This is achieved by using UE Policy Association Modification initiated by the PCF procedure as defined in clause 4.16.12.2 of TS 23.502 [5].
- When there is a change of service specific parameter (including path selection policy) as described in clause 6.2.5 (performing the procedure in clause 4.15.6.7 of TS 23.502 [5]).
- When the timer associated with some Policy/parameter expires.
- When the UE determines that the ProSe Policy/parameter(s) is invalid and performs UE triggered Policy Provisioning procedure to the PCF.
If the serving PLMN is removed from the list of PLMNs in the service authorization parameters, the service authorization is revoked in the UE.
When the UE is roaming, the change of subscription resulting in updates of the service authorization parameters are transferred to the UE by H-PCF via V-PCF.
The UE may perform ProSe UE triggered Policy Provisioning procedure to the PCF, after Registration procedure has been completed, as specified in clause 6.2.4 when the UE determines the 5G ProSe Policy/Parameter is invalid (e.g. Policy/Parameter is outdated, missing or invalid).
When the UE disables a ProSe capability, the PCF may stop updating the corresponding ProSe Policy/parameter(s) and when the UE enables a ProSe capability the PCF may need to provide or update the corresponding ProSe Policy/parameter(s).
When a 5G ProSe Layer-3 Remote UE is accessing to 5GC via 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.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.2.3 PCF discovery
|
PCF discovery and selection mechanism defined in clause 6.3.7.1 of TS 23.501 [4] applies with the following addition to enable a PCF instance is selected for 5G ProSe service and for UE:
- Based on the indication from the UE and/or UE subscription data during the Registration procedure as specified in clause 6.2.2, the AMF may include the 5G ProSe Capability indication in the Nnrf_NFDiscovery_Request message as the optional input parameter. If provided, the NRF takes the information into account for discovering the PCF instance.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.2.4 Procedure for UE triggered ProSe Policy provisioning
|
The UE triggered Policy Provisioning procedure is initiated by the UE to request ProSe Policy/Parameter from the PCF when UE determines the 5G ProSe Policy/Parameter is invalid in the following cases:
- if the validity timer indicated in the 5G ProSe Policy/Parameter expires;
- if there are no valid parameters, e.g. for the 5G ProSe Identifier a UE wants to use, for current area, or due to abnormal situation.
Figure 6.2.4-1: UE triggered 5G ProSe Policy provisioning procedure
1. The UE sends the UL NAS TRANSPORT message carrying the UE Policy Container (UE Policy Provisioning Request to request 5G ProSe policies) to the AMF.
2. The AMF sends Namf_Communication_N1MessageNotify request to the PCF including the UE Policy Container received from UE.
3. The PCF receives UE Policy Container which indicates UE Policy Provisioning Request to request 5G ProSe policies. If the 5G ProSe policies are authorized based on AMF input, the PCF performs the UE Policy delivery procedure as defined in clause 4.2.4.3 of TS 23.502 [5].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.2.5 AF-based service parameter provisioning for ProSe over control plane
|
For 5G ProSe service parameter provisioning (i.e. creating, updating and deleting), the procedure defined in clause 4.15.6.7 of TS 23.502 [5] is performed with the following considerations:
- The AF in TS 23.502 [5] is considered as ProSe Application Server in this specification.
- Service Description indicates 5G ProSe service domain information.
- Service Parameters include parameters for 5G ProSe Direct Discovery and 5G ProSe Direct Communications. The detailed information on the parameters is described in clause 5.1.2.1 and clause 5.1.3.1.
- Service Parameters for 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-Network Relay Communications. The detailed information on the parameters is described in clause 5.1.4.1.
- Service Parameters for 5G ProSe UE-to-UE Relay Discovery and 5G ProSe UE-to-UE Relay Communications. The detailed information on the parameters is described in clause 5.1.5.1.
NOTE: It is assumed that the ProSe service domain information is set based on the Service Level Agreement with the operator.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.3 5G ProSe Direct Discovery
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.3.1 5G ProSe Direct Discovery with 5G DDNMF
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.3.1.1 Overview
|
5G ProSe Direct Discovery is defined as the process that detects and identifies another UE in proximity using NR radio signals. There are two types of 5G ProSe Direct Discovery supported over PC3a reference point: open and restricted, as defined in TS 23.303 [3]. 5G ProSe Direct Discovery can be a standalone service or can be used for subsequent actions e.g. to initiate 5G ProSe Direct Communication.
ProSe-enabled UEs which have obtained authorization to participate in 5G ProSe Direct Discovery shall not continue in participating in 5G ProSe Direct Discovery procedures over PC3a reference point defined in clause 6.3.1 when they detect loss of NG-RAN coverage in the serving PLMN.
With 5G ProSe Direct Discovery, the UE can use inter-PLMN discovery transmission based on the indication from the serving NG-RAN or the provisioned radio resource on the UE. How the serving cell authorizes the UE to use inter-PLMN radio resource is specified in TS 38.331 [16].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.3.1.2 Overall procedure for 5G ProSe Direct Discovery (Model A)
|
Figure 6.3.1.2-1: Overall procedure for Model A 5G ProSe Direct Discovery
This procedure is applied for open and restricted 5G ProSe Direct Discovery when the ProSe enabled UE is served by NG-RAN.
1. Service authorisation for 5G ProSe Direct Discovery services is performed for as defined in clause 6.2.
If the UE is authorised to announce:
2a. When the UE is triggered to announce, then it sends a discovery request for announcing to the 5G DDNMF in HPLMN as defined in clause 6.3.1.4. In addition, for restricted 5G ProSe Direct Discovery, the 5G DDNMF further interacts with the ProSe Application server for the authorization of the discovery request.
3a. If the request is successful and is provided with ProSe Application Code/ProSe Restricted Code, it starts announcing on PC5 interface.
For ProSe restricted discovery and UE requests "on demand" announcing, ProSe Restricted Code may be provided to UE after this procedure. In this case, UE waits for the ProSe Restricted Code allocation and starts to announce the ProSe Restricted Code on PC5 after receiving it in Announcing Alert procedure specified in clause 6.3.1.6.
NOTE 1: More details on the Access Stratum protocol of this step are provided in RAN specifications.
If the UE is authorised to monitor:
2b. When the UE is triggered to monitor, it sends a discovery request for monitoring to the 5G DDNMF as defined in clause 6.3.1.4. In addition, for restricted 5G ProSe Direct Discovery, the 5G DDNMF further interacts with the ProSe Application server for the authorization of the discovery request.
3b. If the request is successful and the UE is provided with a Discovery Filter consisting of ProSe Application Code(s)/ProSe Restricted Code(s) and/or ProSe Application Mask(s), it starts monitoring for these ProSe Application Codes/ProSe Restricted Codes on the PC5 interface.
NOTE 2: More details on the Access Stratum protocol of this step are provided in RAN specifications.
4b. When the UE detects that one or more ProSe Application Code(s)/ProSe Restricted Code(s) that match the filter (see clause 5.8.1), it reports the ProSe Application Code(s)/ProSe Restricted Code(s) to the 5G DDNMF as defined in clause 6.3.1.5.
Non-roaming direct discovery procedures cover the case where both the "announcing UE" and "monitoring UE" are served by their respective HPLMN. Roaming direct discovery procedures cover the other cases.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.3.1.3 Overall procedure for 5G ProSe Direct Discovery (Model B)
|
Figure 6.3.1.3-1: Overall procedure for Model B 5G ProSe Direct Discovery
This procedure is applied for restricted 5G ProSe Direct Discovery when the ProSe enabled UE is served by NG-RAN.
1. Service authorisation for 5G ProSe Direct Discovery services is performed as defined in clause 6.2.
If the UE is authorised to perform restricted 5G ProSe Direct Discovery, Model B, as a Discoveree UE, the following steps take place:
2a. When the UE is triggered to perform restricted 5G ProSe Direct Discovery, Model B, it sends a discovery request to the 5G DDNMF in the HPLMN to obtain a ProSe Response Code as defined in clause 6.3.1.4. The 5G DDNMF further interacts with ProSe Application Server for the authorization of the discovery request.
3a. If the request is successful and the UE is provided with a ProSe Response Code and an associated Discovery Query Filter(s), then the UE starts monitoring for the ProSe Query Code on PC5 interface.
4a. If a received ProSe Query Code matches any of the Discovery Query Filter(s), the UE announces the associated ProSe Response Code on the PC5 interface.
NOTE 1: More details on the Access Stratum protocol of this step are provided in RAN specifications.
If the UE is authorised to perform restricted 5G ProSe Direct Discovery, Model B, as a Discoverer UE, the following steps take place:
2b. When the UE is triggered to perform restricted 5G ProSe Direct Discovery, Model B, it sends a discovery request to the 5G DDNMF in the HPLMN for a ProSe Query Code as defined in clause 6.3.1.4. The 5G DDNMF further interacts with ProSe Application Server for the authorization of the discovery request.
3b. If the request is successful and the UE is provided with a ProSe Query Code and the Discovery Response Filter(s) consisting of ProSe Response Code(s) and ProSe Application Mask(s), the UE announces the ProSe Query Code on the PC5 interface.
4b. The UE starts to monitor on PC5 interface for any ProSe Response Code(s) that might match the Discovery Response Filter(s).
NOTE 2: More details on the Access Stratum protocol of this step are provided in RAN specifications.
5b. When the UE detects a match for one or more ProSe Response Code(s), it reports the ProSe Response Code to the 5G DDNMF as defined in clause 6.3.1.5.
Non-roaming direct discovery procedures cover the case where both the Discoveree UE and Discoverer UE are served by their respective HPLMN. Roaming direct discovery procedures cover the other cases.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.3.1.4 Discovery Request procedures
|
The Discovery Request procedure can be used by the "announcing UE" or "monitoring UE" in order to be authorised to access the discovery resources and perform 5G ProSe Direct Discovery. The exact signalling procedures involving the UE, the 5G DDNMFs and the ProSe Application Server are specified in TS 23.303 [3] clause 5.3.3, with the following modifications:
- the 5G DDNMF takes the role of "ProSe Function" in the procedure;
- Upon receiving a Discovery Request for restricted discovery from a UE, if the 5G DDNMF does not have a valid PDUID for that UE, the 5G DDNMF searches the PCF for the UE using Nbsf_Management_Subscribe Request and BSF provides the address of the PCF for the UE in Nbsf_Management_Subscribe Response as defined in the clause 5.2.13.2.6 in TS 23.502 [5]. The 5G DDNMF gets the PDUID and subscribes to notifications on Change of PDUID using Npcf_AMPolicyAuthorization_Subscribe from the PCF for the UE as defined in the clause 5.2.5.8.6 in TS 23.502 [5], including the SUPI, Event ID set to "Change of PDUID" and immediate reporting flag to indicate that the current PDUID value should be provided to the consumer. The PCF provides the PDUID and its validity timer.
NOTE: If the address of the PCF for the UE is changed, the BSF notifies the 5G DDNMF of the changed PCF address in Nbsf_Management_Notify as defined in the clause 5.2.13.2.8 in TS 23.502 [5].
- At the time the PCF generates a new PDUID, if the subscription to "Change of PDUID" is active it sends Npcf_AMPolicyAuthorization_Notify to the 5G DDNMF to report a new PDUID and its validity timer.
- the HSS is replaced by UDM;
- the E-UTRAN is replaced by NG-RAN and E-UTRA is replaced with NR;
- corresponding 5GS identifiers replace the EPS identifiers, e.g. use SUPI instead of IMSI and use GPSI instead of MSISDN;
- PC5_tech parameter is omitted and the intended PC5 radio technology is NR.
The Discovery Request procedure can also be used by the Discoveree UE or the Discoverer UE in order to be authorised to access the discovery resources and perform 5G ProSe Direct Discovery, Model B. The exact signalling procedures are defined in TS 23.303 [3] clause 5.3.3A, with the same modifications as in the above list apply.
The events reported by the PCF, described in clause 6.1.3.18 in TS 23.503 [9] are extended to report "Change of PDUID" to the 5G DDNMF.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.3.1.5 Discovery Reporting procedures
|
The Discovery Reporting procedure can be used by the "monitoring UE" (in Model A) and Discoverer UE (in Model B) to request the 5G DDNMF to resolve a matched ProSe Discovery Code(s) (ProSe Application Code for open discovery and ProSe Restricted Code for restricted discovery) and obtain the corresponding ProSe Application ID(s) or RPAUID and additional information, e.g. metadata.
The signalling procedures for the "monitoring UE" (in Model A) is specified in TS 23.303 [3] clause 5.3.4 and the signalling procedures for the Discoverer UE (in Model B) is specified in TS 23.303 [3] clause 5.3.4A, with the following modifications:
- the 5G DDNMF takes the role of "ProSe Function" in the procedure;
- the HSS is replaced by UDM;
- corresponding 5GS identifiers replace the EPS identifiers, e.g. use SUPI instead of IMSI and use GPSI instead of MSISDN;
- PC5_tech parameter is omitted and the intended PC5 radio technology is NR.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.3.1.6 Announcing Alert Procedures for restricted discovery
|
When supported by the 5G DDNMF and the UE, the Announcing Alert procedure allows the 5G DDNMF to postpone the ProSe Restricted Code allocation, so that the announcing UE would be only triggered by this procedure to announce when the 5G DDNMF receives a Monitor Request from a UE in the vicinity of the announcing UE. This procedure is an optional step of the Discovery Request procedure defined in clause 6.3.1.4.
The signalling procedure of Announcing Alert Procedure is specified in TS 23.303 [3] clause 5.3.5, with the same modifications listed in clause 6.3.1.4.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.3.1.7 Direct Discovery Update Procedures
|
The 5G DDNMF can at any time update/revoke a previously allocated ProSe Application Code, or Discovery Filters. The UE can decide at any time to stop announcing a ProSe Application Code or monitoring set of Discovery Filter(s). The Direct Discovery Update procedure as specified in TS 23.303 [3] clause 5.3.6A.1 allows both the 5G DDNMF and the UE to update or revoke the previously authorized discovery. In the defined signalling procedures, the 5G DDNMF(s) takes the role of the "ProSe Function".
A user may decide at any time to change the discovery permissions relating to other users in a ProSe Application Server; then the corresponding ProSe Application Server triggers the procedure as specified in clause 5.3.6A.2 of TS 23.303 [3] towards the affected 5G DDNMF(s) to update/revoke the discovery permissions. In the defined signalling procedures, the 5G DDNMF(s) takes the role of the "ProSe Function".
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.3.2 5G ProSe Direct Discovery procedures over PC5 reference point
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.