hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.7.5.2.1 Layer-2 link establishment via 5G ProSe Layer-3 Multi-hop UE-to-UE-Relays (IP type)
|
Figure 6.7.5.2.1-1 shows the Layer-2 link establshment procedure via 5G ProSe Layer-3 Multi-hop UE-to-UE-Relays. This procedure is used by an 5G ProSe End UE to connect to the relay cloud, or for a 5G ProSe Layer-3 Multi-hop UE-to-UE-Relay to connect to other 5G ProSe Layer-3 Multi-hop UE-to-UE-Relays.
Figure 6.7.5.2.1-1: 5G ProSe Communication via IP type of 5G ProSe Multi-hop UE-to-UE Relay
0. The 5G ProSe Layer-3 Multi-hop UE-to-UE-Relays and the other 5G ProSe End UEs have already established IP type of connections. The 5G ProSe Layer-3 Multi-hop UE-to-UE-Relays and 5G ProSe End UEs may have used the discovery procedure as defined in clause 6.3.2.6.2 and established the Layer-2 link as defined in clause 6.4.3.10.1.
1. The 5G ProSe End UE performs the 5G Multi-hop UE-to-UE Relay discovery procedure as described in clause 6.3.2.6.2 and finds the 5G Multi-hop UE-to-UE Relay-1.
2. The 5G ProSe End UE establishes an IP based Layer-2 link with the 5G ProSe Multi-hop UE-to-UE Relay-1 as described in clause 6.4.3.10.1.
Depends on the configuration, the 5G ProSe End UE may obtain an IP address/Prefix from the 5G ProSe Multi-hop UE-to-UE Relay-1. Otherwise, the 5G ProSe End UE informs the 5G ProSe Multi-hop UE-to-UE Relay-1 of its pre-configured IP address/prefix.
The 5G ProSe End UE may also configure the corresponding services and PC5 QoS Flows over the Layer-2 like with the 5G ProSe Multi-hop UE-to-UE Relay-1. The 5G ProSe End UE may use the Layer-2 link modification procedure as defined in clause 6.4.3.4 to add/modify/remove PC5 QoS Flows corresponding to the services and link status.
3. The 5G ProSe Multi-hop UE-to-UE Relay-1 updates its records of the 5G ProSe End UEs and may trigger the MANET signalling, e.g. OLSRv2 signalling [35], to update other connected 5G ProSe Multi-hop UE-to-UE Relays. This will result in a routing table on the relays that allows other UEs to reach the newly connected 5G ProSe End UE.
The 5G ProSe Multi-hop UE-to-UE Relay may also trigger signalling to update the DNS entries in other connected 5G ProSe Multi-hop UE-to-UE Relays for the 5G ProSe End UE using the MANET Discovery Info message, as described in clause 5.14.3.2.
4. The 5G ProSe End UE may perform a DNS query for a target 5G ProSe End UE, if it does not know the IP address/prefix of the target. The DNS query may stop at the 5G ProSe Multi-hop UE-to-UE Relays that has the entry for the target 5G ProSe End UE.
The UE-to-UE Relay should only use the DNS entry associated with the RSC, corresponding to the PC5 link that the DNS query message is received.
5G ProSe End UE starts to communicate with the target 5G ProSe End UE using IP based communications. The 5G ProSe Multi-hop UE-to-UE Relays forwards the packets based on the routing table established with the MANET protocols.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.7.5.2.2 5G ProSe Communication via Multi-hop 5G ProSe Layer-3 UE-to-UE Relay for Non-IP Type PDU
|
Figure 6.7.5.2.2-1: Layer-2 link establishment via 5G ProSe Layer-3 UE-to-UE Relay for Non-IP Type PDU
1. 5G ProSe Layer-3 End UE1 and 5G ProSe Layer-3 End UE2 are authorized for multi-hop UE-to-UE Relay service as End UE and are provisioned with parameters for discovery and connection setup with other UEs via multi-hop UE-to-UE Relay services.
5G ProSe Layer-3 UE-to-UE Relays are authorized for multi-hop UE-to-UE Relay service as Relay UE and are provisioned with parameters for discovery and connection setup with other UEs and relay UEs via multi-hop UE-to-UE Relay services (as described in clause 5.1.5.1). The provisioned parameter may include parameters such as RSC (Relay service Code)(s), list of PLMN, user info of UE for application which are allowed at multi-hop relay connection.
2. It is assumed that the source 5G ProSe Layer-3 End UE1 selects a relay path to the Target End UE2 from the discovery procedure which is captured in clause 6.3.2.4.
3. The source 5G ProSe Layer-3 End UE1 initiates the unicast Layer-2 link establishment procedure with the 5G ProSe Layer-3 UE-to-UE Relays by sending a Direct Communication Request message to the UE-to-UE Relay. The parameters included in the Direct Communication Request message are described in clause 6.4.3.10.2.
If there is already a PC5 link with the same RSC been established between the End UE and the UE-to-UE Relay or between UE-to-UE Relays, a Link Modification Request message is sent instead of Direct Communication Request message. The parameters included in the LMR message are described in clause 6.4.3.10.2.
4. (Optional) When the security protection is enabled, the source 5G ProSe Layer-3 End UE sends the parameters as described in clause 6.4.3.10.2 to the 5G ProSe Layer-3 UE-to-UE Relay.
If 5G ProSe Layer-3 UE-to-UE relay detects the Ethernet MAC address of source 5G ProSe Layer-3 End UE is already used by another 5G ProSe Layer-3 End UE, then the 5G ProSe Layer-3 UE-to-UE Relay rejects the direct link establishment indicating that the MAC address is not unique.
5. A UE-to-UE Relay sends a Direct Communication Request or Link Modification Request message to the next UE-to-UE Relay according to the path information in the received Direct Communication Request or Link Modification Request message.
The Source Layer-2 ID of the Direct Communication Request message is self-assigned by the UE-to-UE Relay and the Destination Layer-2 ID is the unicast Layer-2 ID associated with the User Info ID of the next hop UE-to-UE Relay. This association may be determined by UE-to-UE relay during discovery procedure in step 2.
6. (Optional) When the security protection is enabled, the UE-to-UE Relays may establish security association as described in clause 6.4.3.10.2.
7. A UE-to-UE Relay may know it is the last Relay in the path (e.g. according to the User Info ID of Relays in the received Direct Communication Request/Link Modification Request message). The UE-to-UE Relay sends a Direct Communication Request/Link Modification Request message to the target 5G ProSe Layer-3 End UE.
The Destination Layer-2 ID is the unicast Layer-2 ID of target End UE or a broadcast Layer-2 ID. Unicast Layer-2 ID is used if the Layer-2 ID of the Target End UE is known to the UE-to-UE Relay.
8. (Optional) When the security protection is enabled, the UE-to-UE Relay (here, U2U Relay 2) may establish security association with the target 5G ProSe Layer-3 End UE as described in clause 6.4.3.10.2.
9. The target End UE sends a Direct Communication Accept message to the UE-to-UE Relay it has successfully established security with. The DCA message may include the path information.
10-11. After receiving a DCA message, the UE-to-UE Relay (e.g. Relay2) sends a DCA message to the next UE-to-UE Relay (e.g. Relay1) or Source End UE it has successfully established security with. The UE-to-UE Relay may decide the next UE-to-UE Relay (e.g. Relay1) according to the received DCA message or from which it previously received a corresponding DCR message.
NOTE 1: In step 6, U2U Relay2 may detect the Ethernet MAC address of source 5G ProSe Layer-3 End UE is already used by another 5G ProSe Layer-3 End UE.
NOTE 2: In step 9 and step 10, U2U Relay1 and U2U Relay2 may detect the Ethernet MAC address of target 5G ProSe Layer-3 End UE is already used by another 5G ProSe Layer-3 End UE.
For Ethernet communication, the 5G ProSe Layer-3 UE-to-UE Relay maintains the association between PC5 links and Ethernet MAC addresses received from the 5G ProSe Layer-3 End UE.
For Unstructured traffic communication, for each pair of source and target 5G ProSe Layer-3 End UEs, the 5G ProSe Layer-3 UE-to-UE Relay maintains the 1:1 mapping between two PC5 links to the (next hop to) source 5G ProSe Layer-3 End UE and the (next hop to) target 5G ProSe Layer-3 End UE.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.8 Procedures for communication path switching between PC5 and Uu reference points
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.8.1 Procedure for communication path switching from Uu reference point to PC5 reference point
|
Figure 6.8.1-1 depicts the procedure for communication path switching from Uu reference point to PC5 reference point.
Figure 6.8.1-1: Procedure for communication path switching from Uu reference point to PC5 reference point
1. UE-1 and UE-2 communicate with each other via Uu path, i.e. by using established PDU Sessions.
2. UE-1 decides to perform path switching for ProSe service(s) from Uu path to PC5 path, e.g. because UE-1 and UE-2 are in proximity each other or for offloading some traffic from the network.
NOTE 1: UE-1 can perform ProSe discovery to determine whether UE-2 is in proximity using the User Info of UE-2 provided by the application layer.
UE-1 determines whether and which ProSe service(s) can be switched to PC5 path based on the path selection policy.
3. UE-1 triggers the establishment of a PC5 unicast link by using the Layer-2 link establishment procedure as specified in clause 6.4.3.1. The PC5 unicast link is established including the ProSe service(s) that can be switched to PC5 path. If any Layer-2 link already established between UE-1 and UE-2 can be used for this path switching, the Layer-2 link modification as specified in clause 6.4.3.4 is used.
4. Traffic for the ProSe service(s) is switched from Uu path to PC5 path.
5a. UE-1 may release its PDU Session, e.g. if no traffic transmitted over the PDU Session, or modify its PDU Session, e.g. only part of the services is switched.
5b. UE-2 may release its PDU Session, e.g. if no traffic transmitted over the PDU Session, or modify its PDU Session, e.g. only part of the services is switched.
NOTE 2: Steps 5a and 5b can be executed in parallel.
NOTE 3: As an alternative to steps 5a and 5b, the UP connection of the relevant PDU Sessions can be deactivated as specified in clause 4.3.7 of TS 23.502 [5].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.8.2 Procedure for communication path switching from PC5 reference point to Uu reference point
|
Figure 6.8.2-1 depicts the procedure for communication path switching from PC5 reference point to Uu reference point.
Figure 6.8.2-1: Procedure for communication path switching from PC5 reference point to Uu reference point
1. UE-1 and UE-2 communicate with each other via PC5 path, i.e. by using the established PC5 unicast link between them.
2. UE-1 decides to path switch ProSe service(s) from PC5 path to Uu path, e.g. if the PC5 signal strength of the unicast link with UE-2 reaches or below certain configured signal strength threshold.
UE-1 determines whether and which ProSe service(s) can be switched to Uu path based on e.g. the availability of the Uu path, the path selection policy, etc.
UE-1 sends a Path Switch Request message to UE-2 to negotiate the ProSe service(s) to be switched. UE-1 includes the ProSe service(s) that can be switched to Uu path in the Path Switch Request message.
Optionally, UE-1 can decide the Uu QoS parameters of each UE based on PC5 QoS parameters for each ProSe service. UE-1 may include Uu QoS parameters used for UE-2's Uu path for the ProSe service(s) that can be switched to a Uu path in the Path Switch Request message.
3. UE-2 responds with a Path Switch Response message.
UE-2 determines whether and which ProSe service(s) can be switched to Uu path based on e.g. the path selection policy, availability of Uu path, etc.
If UE-2 accepts the path switch request from UE-1, UE-2 includes the accepted ProSe service(s) to be switched to Uu path in the Path Switch Response message from those indicated by UE-1. Otherwise, UE-2 rejects the path switch request with the appropriate cause (e.g. path switching to Uu path for the ProSe service(s) is not permitted, Uu path is not available) in the Path Switch Response message.
4a. UE-1 may establish or modify PDU Session by using the PDU session establishment procedure as specified in clause 4.3.2 or the PDU session modification procedure as specified in clause 4.3.3 of TS 23.502 [5]. UE-1 may set the Requested QoS as the Uu QoS parameters used for UE-1's Uu path for the specific accepted ProSe service in the PDU Session Modification Request. The PDU Session needs to support QoS requirements for the ProSe service(s) to be switched from PC5 path.
4b. UE-2 may establish or modify PDU Session by using the PDU session establishment procedure as specified in clause 4.3.2 or the PDU session modification procedure as specified in clause 4.3.3 of TS 23.502 [5]. UE-2 may set the Requested QoS as the Uu QoS parameters used for UE-2's Uu path for the specific accepted ProSe service in the PDU Session Modification Request. The PDU Session needs to support QoS requirements for the ProSe service(s) to be switched from PC5 path.
NOTE 1: Steps 4a and 4b can be executed in parallel and step 4b can be performed before step 3.
5. Traffic for the accepted ProSe service(s) is switched from PC5 path to Uu path.
6. The PC5 unicast link may be released, e.g. if no more ProSe services over the PC5 unicast link.
NOTE 2: The UEs can agree to maintain the PC5 unicast link after path switching from PC5 path to Uu path. In this case, the UEs can determine to switch back to PC5 path from Uu path based on e.g. the path selection policy, the PC5 signal level of the maintained unicast link (e.g. the measured link quality is good).
NOTE 3: When the UEs cannot successfully exchange Path Switch Request/Response due to, e.g. the PC5 unicast link suddenly breaks, whether to perform path switching to Uu path is left to UE implementation.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.9 Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.9.1 General
|
This clause describes the procedures to support multi-path communication via direct Uu path and via 5G ProSe UE-to-Network Relay.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.9.2 Multi-path communication via direct Uu path and via 5G ProSe Layer-3 UE-to-Network Relay
|
When a 5G ProSe enabled UE accesses the network, if the UE decides to establish multi-path via direct Uu path and via the 5G ProSe Layer-3 UE-to-Network Relay without N3IWF based on "ProSe Multi-path Preference" in the selected RSD of the matched URSP rule for the application traffic as specified in clause 6.5.4, the following is performed:
- The UE may establish a new PDU Session as specified in clause 4.3.2 of TS 23.502 [5] or modify an existing PDU Session as specified in clause 4.3.3 of TS 23.502 [5] for the direct Uu path.
- The UE takes the role of 5G ProSe Layer-3 Remote UE either establishes 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF as specified in clause 6.5.1.1 or modifies an existing PC5 connection with a 5G ProSe Layer-3 UE-to-Network Relay as specified in clause 6.4.3.6.
NOTE 1: How to make use of the multi-path communication via direct Uu path and via a 5G ProSe Layer-3 UE-to-Network Relay for redundant or split traffic delivery is out of scope of this specifications.
When a 5G ProSe enabled UE accesses the network, if the UE decides to establish multi-path via direct Uu path and via the 5G ProSe Layer-3 UE-to-Network Relay with N3IWF based on the "multi-access" Access Type of the selected RSD, the UE establishes a MA PDU Session as specified in clause 4.22 of TS 23.502 [5], the following is performed:
- The UE sets up path over Uu by establishing a MA PDU session using the procedures for 3GPP access in clause 4.22 of TS 23.502 [5].
- The UE taking the role of 5G ProSe Layer-3 Remote UE, if not connected and registered to the network via a Layer-3 UE-to-Network Relay with N3IWF, performs Relay (re)selection and performs registration with 5GC as specified in clause 6.5.1.2 and then performs MA PDU Session Establishment procedure or adds the user plane resources over the path via 5G ProSe Layer-3 UE-to-Network Relay with N3IWF using the procedures for non-3GPP access in clause 4.22 of TS 23.502 [5].
NOTE 2: The Remote UE may establish MA PDU session over the path via 5G ProSe Layer-3 UE-to-Network Relay with N3IWF before the direct Uu path. The sequence could be arbitrary.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
6.9.3 Multi-path communication via direct Uu path and via 5G ProSe Layer-2 UE-to-Network Relay
|
Procedures for Multi-path communication via direct Uu path and via 5G ProSe Layer-2 UE-to-Network Relay is specified in TS 38.300 [12].
In the case that the direct Uu path and indirect path via 5G Prose Layer-2 UE-to-Network Relay connect via different cells of the same NG-RAN, the NG-RAN shall provide the cell ID of the direct path in the ULI information. The same applies to NG-RAN Location reporting procedures defined in clause 4.10 of TS 23.502 [5] if AMF enables location reporting towards NG-RAN.
Path management of the 5G ProSe Layer-2 Remote UE is specified in clause 16.21 of TS 38.300 [12].
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7 Network Function Services
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.1 5G DDNMF Services
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.1.1 General
|
The following table illustrates the 5G DDNMF Services.
Table 7.1.1-1: Services provided by 5G DDNMF
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
N5g-ddnmf_Discovery
AnnounceAuthorize
Request/Response
5G DDNMF
AnnounceUpdate
Request/Response
5G DDNMF
MonitorAuthorize
Request/Response
5G DDNMF
MonitorUpdate
Request/Response
5G DDNMF
MonitorUpdateResult
Notify
5G DDNMF
DiscoveryAuthorize
Request/Response
5G DDNMF
MatchReport
Request/Response
5G DDNMF
MatchInformation
Notify
5G DDNMF
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.1.2 N5g-ddnmf_Discovery service
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.1.2.1 General
|
Service description: This service enables a 5G DDNMF to manage inter-PLMN ProSe Direct Discovery operations.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.1.2.2 N5g-ddnmf_Discovery_AnnounceAuthorize service operation
|
Service operation name: N5g-ddnmf_Discovery_AnnounceAuthorize
Description: The consumer NF obtains the authorization from the 5G DDNMF for announcing in the PLMN.
Input, Required: Discovery type ("open" or " restricted ") and
- (for "open" discovery type:) ProSe Application ID, ProSe Application Code/Prefix, UE Identity, validity timer, Discovery Entry ID,
- (for "restricted" discovery type:) RPAUID, Application ID, ProSe Restricted Code/Prefix, UE Identity, Discovery Entry ID,
Input, Optional: metadata, Application Code Suffix pool, Restricted Code Suffix pool.
Output, Required: authorization result.
Output, Optional: None.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.1.2.3 N5g-ddnmf_Discovery_AnnounceUpdate service operation
|
Service operation name: N5g-ddnmf_Discovery_AnnounceUpdate
Description: The consumer NF updates or revoke the authorization from the 5G DDNMF for announcing in the PLMN.
Input, Required: Discovery type = "open", UE Identity, validity timer, Discovery Entry ID
Input, Optional: ProSe Application Code
Output, Required: result.
Output, Optional: None.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.1.2.4 N5g-ddnmf_Discovery_MonitorAuthorize service operation
|
Service operation name: N5g-ddnmf_Discovery_MonitorAuthorize
Description: The consumer NF obtains the authorization from the 5G DDNMF for monitoring in the PLMN.
Input, Required: Discovery type ("open" or " restricted ") and
- (for "open" discovery type:) ProSe Application ID Name(s), UE Identity, Discovery Entry ID;
- (for "restricted" discovery type:) RPAUID, UE Identity, Target PDUID, Application ID, Target RPAUID, Discovery Entry ID,
Input, Optional: None,
Output, Required: (for "open" discovery) ProSe Application Code(s)/Prefix, ProSe Application Mask(s), TTL; or (for "restricted" discovery) ProSe Restricted Code(s)/Prefix, validity timer
Output, Optional: None.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.1.2.5 N5g-ddnmf_Discovery_MonitorUpdate service operation
|
Service operation name: N5g-ddnmf_Discovery_MonitorUpdate
Description: The consumer NF updates or revoke the authorization for the indicated UE to monitor in the PLMN.
Input, Required: Discovery type ("open" or "restricted"); and
- (for "open" discovery type:) ProSe Application ID name, UE Identity, TTL, Discovery Entry ID;
- (for "restricted" discovery type:) ProSe Restricted Code, Application ID, Banned RPAUID, Banned PDUID.
Input, Optional: None.
Output, Required: Result.
Output, Optional: None.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.1.2.6 N5g-ddnmf_Discovery_MonitorUpdateResult service operation
|
Service operation name: N5g-ddnmf_Discovery_MonitorUpdateResult
Description: The consumer NF informs the 5G DDNMF of the monitoring revocation results.
Input, Required: Discovery type = "restricted", ProSe Restricted Code, Application ID, Banned RPAUID, Banned PDUID, Result.
Input, Optional: None.
Output, Required: None.
Output, Optional: None.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.1.2.7 N5g-ddnmf_Discovery_DiscoveryAuthorize service operation
|
Service operation name: N5g-ddnmf_Discovery_DiscoveryAuthorize
Description: The consumer NF obtains the authorization from the 5G DDNMF for a discoverer UE in the PLMN to operate Model B restricted discovery.
Input, Required: Discovery type = "restricted", Restricted ProSe App User ID, UE Identity, Target PDUID, Application ID, Target RPAUID, Discovery Entry ID.
Input, Optional: None.
Output, Required: ProSe Query Code(s), ProSe Response Code, validity timer.
Output, Optional: None.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.1.2.8 N5g-ddnmf_Discovery_MatchReport service operation
|
Service operation name: N5g-ddnmf_Discovery_MatchReport
Description: The consumer NF obtains the information about the indicated discovery code from the 5G DDNMF.
Input, Required: Discovery type = "open", ProSe Application Code(s), UE identity, Monitored PLMN ID.
Input, Optional: None.
Output, Required: ProSe Application ID Name(s), validity timer(s).
Output, Optional: Metadata, Metadata Index Mask(s).
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.1.2.9 N5g-ddnmf_Discovery_MatchInformation service operation
|
Service operation name: N5g-ddnmf_Discovery_MatchInformation
Description: The consumer NF receives from the 5G DDNMF of a matching result and the information can be used for charging purpose.
Input, Required: Discovery type ("open" or "restricted"); and
- (for "open" type:) ProSe Application ID(s), UE Identity;
- (for "restricted" type:) RPAUID, Target RPAUID, UE Identity, ProSe Restricted Code.
Input, Optional: None.
Output, Required: None.
Output, Optional: None.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.2 AF Services
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.2.1 General
|
This service enables consumer NF to request authorization for Discovery Request. This service is also used by producer NF to update the authorization of discovery request.
Table 7.2.1-1: Services provided by AF
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Naf_ProSe
DiscoveryAuthorization
Request/Response
5G DDNMF
DiscoveryAuthorizationUpdateNotify
Subscribe/Notify
5G DDNMF
DiscoveryAuthorizationResultUpdate
Request/Response
5G DDNMF
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.2.2 Naf_ProSe service
| |
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.2.2.1 General
|
Service description: This service enables consumer NF to request authorization for Discovery Request. The AF may update the authorization information to revoke the Restricted ProSe Direct Discovery permission.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.2.2.2 Naf_ProSe_DiscoveryAuthorization service operation
|
Service operation name: Naf_ProSe_DiscoveryAuthorization
Description: Authorize Discovery Request from the consumer NF.
Input, Required: Request type ("open" or " restricted ") and:
- (for "open" discovery type): ProSe Application ID;
- (for "restricted" discovery type): RPAUID.
Input, Optional: Application Level Container, Allowed number of suffixes, Target RPAUID.
Output, Required: Response Type, PDUID(s).
Output, Optional: Target PDUID, ProSe Application Code Suffix pool, ProSe Restricted Code Suffix pool, Mask(s) for the ProSe Application Code Suffix(es) corresponding to ProSe Application ID, Mask(s) for the ProSe Restricted Code Suffix(es) corresponding to RPAUID, N sets of Target PDUID - Target RPAUID - Metadata Indicator, Application Level Container.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.2.2.3 Naf_ProSe_DiscoveryAuthorizationUpdateNotify service operation
|
Service operation name: Naf_ProSe_DiscoveryAuthorizationUpdateNotify
Description: The AF update the authorization information to revoke discovery permissions relating to some other users in the NF consumer.
Input, Required: Discovery type = "restricted", RPAUID, Banned RPAUID, Banned PDUID.
Input, Optional: None.
Output, Required: Result.
Output, Optional: None.
|
a8d70e48ab373cc561a495222059d495
|
23.304
|
7.2.2.4 Naf_ProSe_DiscoveryAuthorizationResultUpdate service operation
|
Service operation name: Naf_ProSe_DiscoveryAuthorizationResultUpdate Description: The NF consumer informs the AF of the revocation result because of update in authorization information. Input, Required: Discovery type = "restricted", RPAUID, Banned RPAUID, Banned PDUID. Input, Optional: None. Output, Required: Result. Output, Optional: None. Annex A (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2021-03 SA2#143e Skeleton for this TS (approved in S2-2101633) 0.0.0 2021-06 SA#92-e SP-210367 - - - MCC editorial update for presentation to TSG SA#92E for information 1.0.0 2021-09 SA#93-e SP-210940 - - - MCC editorial update for presentation to TSG SA#92E for approval 2.0.0 2021-09 SA#93-e - - - - MCC editorial update for publication after TSG SA#92E approval 17.0.0 2021-12 SA#94-e SP-211281 0001 - F EN resolution about U2N Relay reselection 17.1.0 2021-12 SA#94-e SP-211281 0002 1 F Correction on IP address allocation for U2N Relay 17.1.0 2021-12 SA#94-e SP-211281 0003 1 F Clarification on scope 17.1.0 2021-12 SA#94-e SP-211281 0004 - F Correction to UE triggered Policy provisioning Procedure 17.1.0 2021-12 SA#94-e SP-211281 0005 1 F PC5 Discovery Model Selection 17.1.0 2021-12 SA#94-e SP-211281 0012 2 F Clarification for the PC5 QoS parameters and PC5 QoS rule 17.1.0 2021-12 SA#94-e SP-211281 0013 1 F Removing the EN of policy control for L3 U2N Relay 17.1.0 2021-12 SA#94-e SP-211281 0014 1 F N3IWF connection via data network 17.1.0 2021-12 SA#94-e SP-211281 0015 1 F Clarification on Parameters Provided by ProSe Application Server 17.1.0 2021-12 SA#94-e SP-211281 0016 1 F Clarification on Discovery Request Procedure 17.1.0 2021-12 SA#94-e SP-211281 0017 - F Change ProSe Service Type to ProSe Identifier 17.1.0 2021-12 SA#94-e SP-211281 0018 1 F Clarification on Layer-2 Relay selection 17.1.0 2021-12 SA#94-e SP-211281 0019 4 F Clarification on Relay Discovery Additional Information message 17.1.0 2021-12 SA#94-e SP-211281 0020 1 B Identifiers for Layer-2 UE-to-Network Relay discovery 17.1.0 2021-12 SA#94-e SP-211281 0021 1 B Remove ENs on RAN2 dependency issues 17.1.0 2021-12 SA#94-e SP-211281 0022 - F Mega Editorial CR on 5G ProSe 17.1.0 2021-12 SA#94-e SP-211281 0023 1 F DDNMF stack 17.1.0 2021-12 SA#94-e SP-211281 0026 1 F Clarifications on QoS handling for L3 relay 17.1.0 2021-12 SA#94-e SP-211282 0029 1 F Corrections on 5G ProSe UE-to-Network Relay 17.1.0 2021-12 SA#94-e SP-211282 0030 1 F Corrections on ProSe Direct Discovery with 5G DDNMF 17.1.0 2021-12 SA#94-e SP-211282 0031 1 F PDU Session release for L3 U2N Relay on authorisation revocation 17.1.0 2021-12 SA#94-e SP-211282 0037 1 F Update to ProSe identifier definition 17.1.0 2021-12 SA#94-e SP-211282 0038 2 F Update to Groupcast mode 5G ProSe Direct Communication 17.1.0 2021-12 SA#94-e SP-211282 0039 - F terminology correction 17.1.0 2021-12 SA#94-e SP-211282 0049 1 F Miscellaneous clarifications and corrections 17.1.0 2021-12 SA#94-e SP-211282 0050 1 F Clarification on the ID for Group discovery 17.1.0 2021-12 SA#94-e SP-211282 0051 1 F PC5 link release and CM state update for L2 U2N relay 17.1.0 2021-12 SA#94-e SP-211282 0054 1 F Updates and alignments based on further RAN2 feedback 17.1.0 2021-12 SA#94-e SP-211282 0055 - F Update on Unicast link profile for UE-to-Network Relay 17.1.0 2021-12 SA#94-e SP-211282 0056 1 F Clarification on subscription information to 5G ProSe 17.1.0 2021-12 SA#94-e SP-211282 0057 1 F N3IWF connection via Dual PDU sessions 17.1.0 2021-12 SA#94-e SP-211282 0058 1 F Clarification about path selection policy 17.1.0 2021-12 SA#94-e SP-211282 0059 1 F User Info ID clarifications 17.1.0 2022-01 - - 0020 1 B Correction of CR0020R1 implementation: Removal of editor's notes in clause 5.8.3.3 17.1.1 2022-03 SA#95-e SP-220050 0024 2 B DRX support for direct discovery and communication and L3 relay 17.2.0 2022-03 SA#95-e SP-220050 0060 1 F Clarification on QoS handling for Layer-3 Relay with N3IWF 17.2.0 2022-03 SA#95-e SP-220354 0061 4 F Resolve EN for Mobility Restriction 17.2.0 2022-03 SA#95-e SP-220050 0063 1 F Capture the reference point of PKMF 17.2.0 2022-03 SA#95-e SP-220050 0064 1 F Resolve ENs for Security Parameters Provisioning 17.2.0 2022-03 SA#95-e SP-220050 0065 - F High-level description of UE-to-Network Relay discovery 17.2.0 2022-03 SA#95-e SP-220050 0066 1 F Editorial fixes related to referred clauses 17.2.0 2022-03 SA#95-e SP-220050 0067 1 F Update to metadata in PC5 Direct Discovery message 17.2.0 2022-03 SA#95-e SP-220050 0070 - F Removal of discovery range 17.2.0 2022-03 SA#95-e SP-220050 0072 1 F NAS message type determination 17.2.0 2022-03 SA#95-e SP-220050 0074 1 F User info in discovery message 17.2.0 2022-03 SA#95-e SP-220050 0075 1 F Handling on discovery and data associated to different L2 IDs 17.2.0 2022-03 SA#95-e SP-220050 0079 1 F Support of RAN Sharing for L2 Relay 17.2.0 2022-03 SA#95-e SP-220050 0080 1 B RSC Determination by a Layer-3 Remote UE 17.2.0 2022-03 SA#95-e SP-220050 0081 1 B Security procedures for L3 relaying 17.2.0 2022-03 SA#95-e SP-220050 0082 1 F Use of discovery Model A and Model B 17.2.0 2022-03 SA#95-e SP-220050 0086 1 F Clarification on privacy timer 17.2.0 2022-03 SA#95-e SP-220050 0087 1 F Clarification on Remote UE providing QoS Info 17.2.0 2022-03 SA#95-e SP-220354 - - - MCC implementation correction of CR0061R4 17.2.1 2022-06 SA#96 SP-220393 0088 1 F Clarify for security procedure for UE-to-Network Relaying 17.3.0 2022-06 SA#96 SP-220393 0089 1 F Adding reference point between 5G PKMF and UDM 17.3.0 2022-06 SA#96 SP-220393 0090 1 F Mobility restrictions for MCX cleanup 17.3.0 2022-06 SA#96 SP-220393 0091 1 F Clarifications on PC5 DRX operations 17.3.0 2022-06 SA#96 SP-220393 0093 1 F TAI delivery 17.3.0 2022-06 SA#96 SP-220393 0094 1 F Remove ENs on Security Parameters Provisioning for UE-NW Relay 17.3.0 2022-06 SA#96 SP-220393 0098 1 F Miscellaneous corrections and alignments 17.3.0 2022-06 SA#96 SP-220393 0099 - F Modify description in clause 4.3.9.3 17.3.0 2022-06 SA#96 SP-220393 0100 1 F Clarification on DRX handling for unicast communication procedures 17.3.0 2022-06 SA#96 SP-220713 0102 7 F AMF and AUSF selection for CP authentication and authorisation 17.3.0 2022-09 SA#97E SP-220773 0107 1 F CP and UP-based security procedures for 5G ProSe UE-to-Network Relay 17.4.0 2022-09 SA#97E SP-220773 0109 1 F Clarfication on a single L2 link between L2 remote UE and L2 U2N relay UE for supporting PDU sessions of the L2 remote UE 17.4.0 2022-09 SA#97E SP-220773 0110 1 F Clarification on PDCP SDU Types 17.4.0 2022-09 SA#97E SP-220773 0111 - F SL DRX for L2 U2N Relay 17.4.0 2022-09 SA#97E SP-220773 0114 1 F Updates to Policy/Parameter provisioning for CP authentication and authorisation 17.4.0 2022-12 SA#98E SP-221065 0118 1 F Clarifications on PC5 DRX operations 17.5.0 2022-12 SA#98E SP-221065 0119 - F Add 5G DDNMF Address in Parameter Provisioning for 5G ProSe Direct Discovery 17.5.0 2022-12 SA#98E SP-221065 0120 1 F Correction on PC5 link release indication 17.5.0 2022-12 SA#98E SP-221082 0124 4 B Layer-2 link management over PC5 reference point for U2U Relay 18.0.0 2022-12 SA#98E SP-221082 0125 2 B 5G ProSe Communication via U2U Relay 18.0.0 2022-12 SA#98E SP-221082 0126 1 B QoS handling for U2U Relay 18.0.0 2022-12 SA#98E SP-221082 0129 1 B Terms related to U2U relaying 18.0.0 2022-12 SA#98E SP-221082 0130 2 B Introduction of UE-to-UE Relay 18.0.0 2022-12 SA#98E SP-221082 0131 2 B UE-to-UE Relay Discovery 18.0.0 2022-12 SA#98E SP-221082 0132 2 B Layer-3 UE-to-UE Relay Communication 18.0.0 2022-12 SA#98E SP-221082 0135 3 B Support path switching for U2N relay 18.0.0 2022-12 SA#98E SP-221082 0139 3 B Procedures for Communication Path Switching between Two UE-to-Network Relays 18.0.0 2022-12 SA#98E SP-221082 0144 3 B 5G ProSe UE-to-UE Relay reference architecture 18.0.0 2022-12 SA#98E SP-221082 0148 3 B 5G ProSe UE-to-UE Relay reselection 18.0.0 2022-12 SA#98E SP-221082 0150 3 B UE-to-UE Relay with Integrated Discovery 18.0.0 2022-12 SA#98E SP-221082 0155 5 B 5.2.X 5G ProSe UE-to-UE Relay Discovery 18.0.0 2023-03 SA#99 SP-230036 0157 - A Removal of ProSe policy request during registration procedure 18.1.0 2023-03 SA#99 SP-230036 0159 - A Dedicated DNN for 5G ProSe L3 UE-to-Network Relay connectivity without N3IWF 18.1.0 2023-03 SA#99 SP-230047 0161 1 B 5G ProSe Layer-3 UE-to-UE Relay Communication for Non-IP Traffic 18.1.0 2023-03 SA#99 SP-230047 0162 5 B Introducing 5G ProSe ph2 function for KI#7 (Support of Emergency for UE-to-Network Relaying) 18.1.0 2023-03 SA#99 SP-230081 0164 - B IPv6 prefix delegation in 5GS 18.1.0 2023-03 SA#99 SP-230047 0168 1 B Authorization information about multi-path transmission for L2 Remote UE 18.1.0 2023-03 SA#99 SP-230047 0169 13 B Path switching between PC5 path and Uu path 18.1.0 2023-03 SA#99 SP-230047 0170 1 B RSC for UE-to-UE relaying 18.1.0 2023-03 SA#99 SP-230047 0172 1 B Layer-2 link management for 5G ProSe UE-to-UE Relay 18.1.0 2023-03 SA#99 SP-230047 0173 1 C Update for 5G ProSe UE-to-UE Relay Communication with integrated Discovery 18.1.0 2023-03 SA#99 SP-230047 0174 1 B Identifiers for 5G ProSe UE-to-UE Relay Discovery 18.1.0 2023-03 SA#99 SP-230047 0175 1 B Identifiers for Discovery integrated into PC5 unicast link establishment 18.1.0 2023-03 SA#99 SP-230047 0177 1 B Path switching between direct and indirect path for Layer-2 UE-to-Network Relay 18.1.0 2023-03 SA#99 SP-230047 0180 1 C Update on path switching between different U2N relays 18.1.0 2023-03 SA#99 SP-230036 0185 1 A Default configuration for ProSe Policy/Parameter 18.1.0 2023-03 SA#99 SP-230047 0186 - B Updates to U2U relay link management 18.1.0 2023-03 SA#99 SP-230047 0195 1 B Protocol Stacks for 5G ProSe UE-to-UE Relay 18.1.0 2023-03 SA#99 SP-230047 0196 3 B 5G ProSe Remote UE traffic handling for multipath transmission via Layer-3 UE-to-Network Relay 18.1.0 2023-03 SA#99 SP-230047 0201 4 B Update on UE-to-UE Relay reselection 18.1.0 2023-03 SA#99 SP-230048 0202 1 B Support of UE-to-UE Relay operation during ProSe Direct Discovery 18.1.0 2023-03 SA#99 SP-230048 0205 1 B Authorization and Provisioning for 5G ProSe UE-to-UE Relay 18.1.0 2023-03 SA#99 SP-230048 0208 1 B Link Management over PC5 reference point for 5G ProSe UE-to-UE Relay 18.1.0 2023-03 SA#99 SP-230036 0211 1 A Alignment on Remote User ID for L3 U2N Relay w/o N3IWF 18.1.0 2023-03 SA#99 SP-230048 0212 1 B IP address allocation for communication with a 5G ProSe Layer-3 UE-to-UE Relay 18.1.0 2023-03 SA#99 SP-230036 0214 1 A Clarification of out-of-coverage operation_R18 18.1.0 2023-03 SA#99 SP-230048 0215 1 F Clarification of out-of-coverage operation for U2U Relays 18.1.0 2023-03 SA#99 SP-230048 0216 2 B Support of multi-path transmission for U2N Relay (KI#5): structure for high level description and procedures 18.1.0 2023-03 SA#99 SP-230048 0218 2 C Link sharing for UE-to-UE Relay with Integrated Discovery 18.1.0 2023-03 SA#99 SP-230048 0224 1 B General description of 5G ProSe UE-to-UE Relay 18.1.0 2023-03 SA#99 SP-230048 0225 1 B Principles for applying parameters for 5G ProSe UE-to-UE Relay 18.1.0 2023-03 SA#99 SP-230048 0226 1 F Correction on Procedure for 5G ProSe UE-to-UE Relay Discovery with Model A 18.1.0 2023-03 SA#99 SP-230048 0227 1 F Clarification on Path switching between PC5 path and Uu path 18.1.0 2023-06 SA#100 SP-230449 0141 10 B Support of Public Warning Notification Relaying by 5G ProSe UE-to-Network Relay 18.2.0 2023-06 SA#100 SP-230448 0235 1 A Correction to the way that security function is described 18.2.0 2023-06 SA#100 SP-230449 0236 4 F Update to 5G ProSe Layer-3 UE-to-UE Relay Communication for Ethernet Traffic 18.2.0 2023-06 SA#100 SP-230449 0237 1 F KI#5 Resolve EN for authorization of multi-path via Uu and via L3 U2N Relay 18.2.0 2023-06 SA#100 SP-230449 0238 1 F KI#5 Resolve EN for term of multi-path via Uu and via U2N Relay 18.2.0 2023-06 SA#100 SP-230449 0240 1 F ENs resolution for path switching between PC5 path and Uu path 18.2.0 2023-06 SA#100 SP-230449 0242 1 B Resolve EN on parameter provisioning for U2U Relay communication with integrated discovery 18.2.0 2023-06 SA#100 SP-230449 0243 1 B Update of U2U Relay Communication with integrated Discovery procedure 18.2.0 2023-06 SA#100 SP-230449 0248 - F Provisioning for traffic type of L3 U2U Relay 18.2.0 2023-06 SA#100 SP-230449 0249 1 F Emergency Priority Handling for 5G ProSe Layer-3 Relay 18.2.0 2023-06 SA#100 SP-230449 0250 1 F Indication of Support for Emergency Relaying 18.2.0 2023-06 SA#100 SP-230449 0252 1 F Emergency service via N3IWF 18.2.0 2023-06 SA#100 SP-230449 0253 1 F Alignment of policy for U2U and Direct Discovery and Communication 18.2.0 2023-06 SA#100 SP-230449 0255 2 F Clarification of multi-path communication 18.2.0 2023-06 SA#100 SP-230449 0256 3 B Update of U2U Relay discovery to support negotiated Relay reselection 18.2.0 2023-06 SA#100 SP-230449 0259 3 F Update on emergency service over U2N Relay 18.2.0 2023-06 SA#100 SP-230449 0261 - B U2U relay capabilities and subscription 18.2.0 2023-06 SA#100 SP-230449 0264 3 B KI#7_IP address allocation by Layer 3 Relay UE for emergency service 18.2.0 2023-06 SA#100 SP-230448 0266 1 A Catch all entry for discovery 18.2.0 2023-06 SA#100 SP-230450 0270 - B MA PDU Session in multi-path transmission for L3 U2N Relay with N3IWF 18.2.0 2023-06 SA#100 SP-230450 0272 1 B Clarification on 5G ProSe UE-to-Network Relay Reselection and Path Switching 18.2.0 2023-06 SA#100 SP-230450 0273 1 F Clarification on AF-based Service Parameter Provisioning 18.2.0 2023-06 SA#100 SP-230450 0276 1 F PLMN selection for L2 remote UE for emergency service 18.2.0 2023-06 SA#100 SP-230450 0277 3 F DNN for emergency service 18.2.0 2023-06 SA#100 SP-230450 0279 1 B Link Modification Procedure with L3 UE-to-UE Relay 18.2.0 2023-06 SA#100 SP-230450 0286 1 F Clarification of 5G ProSe UE-to-UE Relay reselection 18.2.0 2023-06 SA#100 SP-230450 0288 2 F Layer-3 U2U Relay link release and maintenance procedures 18.2.0 2023-06 SA#100 SP-230450 0292 2 F Clarification on QoS handling for 5G ProSe Layer-3 UE-to-UE Relay 18.2.0 2023-06 SA#100 SP-230450 0302 2 F L2 Remote UE RRC Establishment Cause 18.2.0 2023-06 SA#100 SP-230450 0303 - F Use of emergency RSC 18.2.0 2023-06 SA#100 SP-230450 0304 - F Adding new PQIs to support path switching between PC5 and Uu 18.2.0 2023-09 SA#101 SP-230840 0306 1 F ProSe Authorization info for Layer-2 U2U Relay operation 18.3.0 2023-09 SA#101 SP-230832 0311 1 A Reference point alignment with TS33.503 18.3.0 2023-09 SA#101 SP-230840 0313 2 F Clarification on 5G ProSe UE-to-UE Relay Discovery with Model A 18.3.0 2023-09 SA#101 SP-230840 0315 2 F Modification on Relay Discovery Additional Information Message 18.3.0 2023-09 SA#101 SP-230840 0322 2 F Clarification on 5G ProSe UE-to-UE Relay Discovery 18.3.0 2023-09 SA#101 SP-230840 0329 2 F U2U relay authorization updates 18.3.0 2023-09 SA#101 SP-230840 0334 1 F Clarification on RSC usage during relay discovery and relay reselection 18.3.0 2023-09 SA#101 SP-230840 0338 - F Clarifications on U2U Relay reselection relay discovery 18.3.0 2023-09 SA#101 SP-230840 0348 1 F Corrections on procedures for 5G ProSe UE-to-UE Relay Discovery 18.3.0 2023-12 SA#102 SP-231247 0321 6 F Corrections to UE-to-UE Relay Discovery 18.4.0 2023-12 SA#102 SP-231247 0330 3 F U2U relay features complement 18.4.0 2023-12 SA#102 SP-231247 0331 3 F Multi-path communication complement 18.4.0 2023-12 SA#102 SP-231247 0335 3 F Clarifications on U2U Relay and message handling 18.4.0 2023-12 SA#102 SP-231247 0336 3 F Clarifications on Relay discovery for emergency service 18.4.0 2023-12 SA#102 SP-231247 0341 4 F Relay UE requirement to forward PWS messages 18.4.0 2023-12 SA#102 SP-231247 0350 - F Clarification on Layer-2 link management on UE-to-UE Relay 18.4.0 2023-12 SA#102 SP-231247 0352 3 F Update Terminologies 18.4.0 2023-12 SA#102 SP-231247 0355 1 F Correction on Layer-2 U2U Relay Communication with integrated Discovery 18.4.0 2023-12 SA#102 SP-231247 0356 1 F Correction on Layer-3 U2U Relay link identifier update procedure 18.4.0 2023-12 SA#102 SP-231247 0358 1 F Removal of ENs having RAN dependency 18.4.0 2023-12 SA#102 SP-231247 0359 1 F Support for U2U Relay for UEs in limited service state 18.4.0 2023-12 SA#102 SP-231247 0362 - F Correction on link-local IPv6 address in DCA message 18.4.0 2023-12 SA#102 SP-231247 0364 1 F Issue on U2U relay reselection triggered by PC5 RLF or PC5 link release 18.4.0 2023-12 SA#102 SP-231248 0369 1 F Fixing reference and editorial errors 18.4.0 2023-12 SA#102 SP-231247 0375 2 F Clarification on RSC and Target Info matching 18.4.0 2023-12 SA#102 SP-231247 0376 2 F Correction on relay_Indication 18.4.0 2023-12 SA#102 SP-231247 0377 1 F Resolve the EN on PC5 Security Used for Emergency Services 18.4.0 2023-12 SA#102 SP-231247 0381 1 F Parameter update for Link Modification with L3 U2U Relay 18.4.0 2023-12 SA#102 SP-231247 0382 2 F Correction on UE-to-UE Relay discovery procedures 18.4.0 2023-12 SA#102 SP-231247 0401 2 F Rejection of L3 U2U Connection Setup when Ethernet MAC address conflict is detected 18.4.0 2024-03 SA#103 SP-240088 0339 3 F Clarification on IPv6 only for policy control and session binding for L3 N3IWF Relay 18.5.0 2024-03 SA#103 SP-240088 0340 2 F Clarification on how path type is selected when switching between U2N relays 18.5.0 2024-03 SA#103 SP-240115 0370 2 F Clarification of Relay Service Code used by UEs from different PLMNs 18.5.0 2024-03 SA#103 SP-240088 0402 1 F Clarification on Cell Reporting in multi-path L2 U2N case 18.5.0 2024-03 SA#103 SP-240088 0404 4 F Correction on Layer-2 ID for UE-to-UE Relay Discovery 18.5.0 2024-03 SA#103 SP-240088 0409 1 F Update on UE-to-UE Relay Discovery and Link Establishment/Modification for alignment with SA3 18.5.0 2024-03 SA#103 SP-240088 0410 1 F Update on U2U Identifiers and Candidate U2U Relay Discovery for alignment with SA3 18.5.0 2024-03 SA#103 SP-240088 0416 1 F Alignment with RAN for path switching 18.5.0 2024-03 SA#103 SP-240088 0418 - F EN removal for L2 U2U QoS handling 18.5.0 2024-03 SA#103 SP-240088 0420 1 F Updates to default L2 ID usage for discovery message 18.5.0 2024-03 SA#103 SP-240088 0422 1 F Update policy parameter provisioning for U2U relay 18.5.0 2024-03 SA#103 SP-240088 0423 3 F Update procedure for 5G ProSe UE-to-UE Relay Discovery with Model A 18.5.0 2024-03 SA#103 SP-240088 0424 1 F Clarifications on Layer-2 IDs used in UE-to-UE Relay link establishment procedure 18.5.0 2024-03 SA#103 SP-240088 0426 - F ENs Removal for Layer-2 UE-to-UE Relay 18.5.0 2024-03 SA#103 SP-240115 0429 2 F Clarification of Direct Discovery 18.5.0 2024-03 SA#103 SP-240088 0430 1 F RAN alignment for SL DRX 18.5.0 2024-03 SA#103 SP-240088 0431 2 F Security aspects alignment for U2U relay 18.5.0 2024-03 SA#103 SP-240088 0432 2 F Clarification on multi-path communication via Uu and via 5G ProSe UE-to-Network Relay 18.5.0 2024-03 SA#103 SP-240088 0433 2 F Update on 5G ProSe Layer-2 U2U Relay Link Establishment 18.5.0 2024-04 SA#103 - - - - Implementation Correction of CR0404r4, in clause 5.8.4.2 18.5.1 2024-06 SA#104 SP-240588 0435 - F Clarification on triggering PC5 connection setup procedure via same U2U Relay 18.6.0 2024-06 SA#104 SP-240588 0443 1 F Alignment with stage 3 specification on End UE user info and Direct discovery set 18.6.0 2024-06 SA#104 SP-240607 0436 5 B ProSe support for NPNs 19.0.0 2024-09 SA#105 SP-241263 0444 1 B Authorization and Provisioning for 5G ProSe multi-hop Relays 19.1.0 2024-09 SA#105 SP-241263 0445 1 B Enhancement of 5G ProSe Capability for multi-hop Relays 19.1.0 2024-09 SA#105 SP-241263 0448 1 B Functional Entities enhancements for 5G ProSe multi-hop Relays 19.1.0 2024-09 SA#105 SP-241263 0450 2 B Update on ProSe U2U Multihop Relay for non-IP PDU 19.1.0 2024-09 SA#105 SP-241263 0451 3 B Support ProSe U2N Multihop Relay 19.1.0 2024-09 SA#105 SP-241263 0453 1 B Subscription Data for multi hop U2N and U2U 19.1.0 2024-09 SA#105 SP-241263 0458 2 B 5G ProSe multi-hop UE-to-Network Relay Discovery Model A 19.1.0 2024-09 SA#105 SP-241263 0459 2 B 5G ProSe multi-hop UE-to-Network Relay connection management 19.1.0 2024-09 SA#105 SP-241263 0460 3 B 5G ProSe Multi-hop UE-to-UE Relay for IP PDU type 19.1.0 2024-09 SA#105 SP-241271 0461 - F Clarification on path switching 19.1.0 2024-09 SA#105 SP-241263 0468 2 B Scope, terms, reference architecture and functional entities for 5G ProSe Multi-hop 19.1.0 2024-09 SA#105 SP-241255 0473 1 A Clarification on 5G ProSe U2U Communication with integrated Discovery 19.1.0 2024-09 SA#105 SP-241255 0475 1 A Update on Unicast link profile for UE-to-UE Relay 19.1.0 2024-09 SA#105 SP-241255 0479 1 A Clarification for end-to-end PC5 link management for L2 U2U Relay 19.1.0 2024-12 SA#106 SP-241483 0484 3 F Clarification on the diffusion of DNS information via MANET 19.2.0 2024-12 SA#106 SP-241483 0488 2 B Update for multihop L3 U2U relay reselection 19.2.0 2024-12 SA#106 SP-241483 0489 2 B QoS Handling for multi hop U2N without N3IWF 19.2.0 2024-12 SA#106 SP-241483 0495 1 F Corrections to remove EN for multi-hop UE-to-UE Relay of IP PDU type 19.2.0 2024-12 SA#106 SP-241483 0496 1 F Corrections for 5G ProSe multi-hop UE-to-Network Relay operations 19.2.0 2024-12 SA#106 SP-241483 0497 1 B Update on multihop ProSe U2N Relay Discovery with model B 19.2.0 2024-12 SA#106 SP-241483 0499 2 F Corrections on the Multi-hop U2N Relay IP address allocation 19.2.0 2024-12 SA#106 SP-241483 0503 2 F Update on Multihop U2N Relay with Model B Discovery 19.2.0 2024-12 SA#106 SP-241483 0505 1 B Update on QoS handling for Multihop U2U Relay 19.2.0 2024-12 SA#106 SP-241483 0508 1 B Identifiers for 5G ProSe Multi-hop UE-to-UE Relay for non-IP PDU type 19.2.0 2024-12 SA#106 SP-241483 0509 1 F Correction of Identifiers for 5G ProSe Multi-hop UE-to-UE Relay for IP PDU type 19.2.0 2024-12 SA#106 SP-241483 0518 2 C Multi-hop UE-to-Network Model B Update 19.2.0 2025-03 SA#107 SP-250039 0490 2 F Adding Path Failure Detection for Relay Reselection 19.3.0 2025-03 SA#107 SP-250039 0491 2 F Introduction of multi-hop in the specification 19.3.0 2025-03 SA#107 SP-250039 0492 2 F Expansion of 5G ProSe Layer-3 UE-to-UE Relay functionality 19.3.0 2025-03 SA#107 SP-250039 0513 2 F Update on multi-hop U2N Relay Discovery with Model A 19.3.0 2025-03 SA#107 SP-250039 0519 1 D Editorial corrections 19.3.0 2025-03 SA#107 SP-250032 0521 - A Clarification on DNS query during Layer-2 link establishment via 5G ProSe Layer-3 UE-to-UE Relay 19.3.0 2025-03 SA#107 SP-250039 0522 - F Clarification on triggering the diffusion of DNS information via MANET when End UE is disconnected 19.3.0 2025-03 SA#107 SP-250039 0523 1 F Clarification on Multi-hop Relay Reselection 19.3.0 2025-03 SA#107 SP-250039 0524 1 F Update on Multihop U2U Relay for non-IP type PDU 19.3.0 2025-03 SA#107 SP-250039 0525 1 F Update on Discovery of U2U Multihop Relay for IP PDU 19.3.0 2025-03 SA#107 SP-250039 0527 1 F Correction of UE-to-Network Model B Discovery 19.3.0 2025-03 SA#107 SP-250039 0528 - F Update on multihop ProSe U2N Relay with model B discovery 19.3.0 2025-03 SA#107 SP-250039 0529 - F Update on multihop U2U Relay reselection procedure for non-IP type 19.3.0 2025-03 SA#107 SP-250039 0530 1 F Update on multihop ProSe U2N Relay Discovery 19.3.0 2025-03 SA#107 SP-250039 0531 1 F Update on multihop ProSe U2U Relay for non-IP type PDU 19.3.0 2025-03 SA#107 SP-250039 0532 1 F Corrections on multi-hop U2N Relay discovery with Model A procedure 19.3.0 2025-03 SA#107 SP-250039 0535 - F Authorization information for Layer-2 multi-hop U2N relaying to NG-RAN 19.3.0 2025-03 SA#107 SP-250039 0539 1 F Procedures for ProSe Multihop U2U Relay reselection for Non-IP 19.3.0 2025-03 SA#107 SP-250039 0540 1 F Correction on ProSe Multihop U2N Relay reselection for Model B 19.3.0
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
1 Scope
|
The present document defines the enhancements to Stage 2 system architecture, procedure and flows, Policy and Charging Control for the 5G System defined in TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] in order to support wireline access network and Fixed Wireless Access. The specifications defined in TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] apply to the wireline access network and Fixed Wireless Access.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G system, Stage 2".
[4] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System".
[5] BBF TR-124 issue 5: "Functional Requirements for Broadband Residential Gateway Devices".
[6] BBF TR-101 issue 2: "Migration to Ethernet-Based Broadband Aggregation".
[7] BBF TR-178 issue 1: "Multi-service Broadband Network Architecture and Nodal Requirements".
[8] CableLabs DOCSIS MULPI: "Data-Over-Cable Service Interface Specifications DOCSIS 3.1, MAC and Upper Layer Protocols Interface Specification".
[9] BBF TR-456 issue 2: "AGF Functional Requirements".
[10] BBF WT-457: "FMIF Functional Requirements".
NOTE: Technical Report of BBF WT-457 will be TR-457 which will be available when finalized by BBF.
[11] 3GPP TS 33.501: "Security architecture and procedures for 5G System".
[12] BBF TR-177 Issue 1 Corrigendum 1: "IPv6 in the context of TR-101".
[13] IETF RFC 6788: "The Line-Identification Option".
[14] 3GPP TS 23.003: "Numbering, Addressing and Identification".
[15] Void.
[16] IETF RFC 6603: "Prefix Exclude Option for DHCPv6-based Prefix Delegation".
[17] Void.
[18] BBF TR-069: "CPE WAN Management Protocol".
[19] BBF TR-369: "User Services Platform (USP)".
[20] IETF RFC 3046: "DHCP Relay Agent Information Option".
[21] IETF RFC 4604: "Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific Multicast".
[22] 3GPP TR 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[23] 3GPP TS 38.413: "NG RAN; NG Application Protocol (NGAP)".
[24] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[25] 3GPP TS 22.011: "Service accessibility".
[26] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[27] CableLabs WR-TR-5WWC-ARCH: "5G Wireless Wireline Converged Core Architecture".
[28] IETF RFC 3376: "Internet Group Management Protocol, Version 3".
[29] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS)".
[30] BBF TR-198: "DQS:DQM systems functional architecture and requirements".
[31] 3GPP TS 23.203: "Policy and charging control architecture".
[32] 3GPP TS 33.126: "Lawful Interception Requirements".
[33] IETF RFC 2236: "Internet Group Management Protocol, Version 2".
[34] IETF RFC 4861: "Neighbor Discovery for IP version 6 (IPv6)".
[35] IETF RFC 1112: "Internet Group Management Protocol".
[36] IETF RFC 2710: "Multicast Listener Discovery Version for IPv6".
[37] IETF RFC 2010: "Operational Criteria for Root Name Servers".
[38] BBF TR-470: "5G FMC architecture".
[39] 3GPP TS 29.519: "Policy Data, Application Data and Structured Data for exposure".
[40] 3GPP TS 23.041: "Public Warning System".
[41] IEEE Publication (2017): "Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)". https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/tutorials/eui.pdf.
[42] 3GPP TS 29.413: "Application of the NG Application Protocol (NGAP) to non-3GPP access".
[43] Void.
[44] 3GPP TS 24.502: "Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks".
[45] 3GPP TS 23.402: " Architecture enhancements for non-3GPP accesses".
[46] BBF TR-181: "Device Data Model for TR-069".
[47] IETF RFC 8415: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".
[48] IETF RFC 9330: "Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture".
[49] IETF RFC 9331: "Explicit Congestion Notification (ECN) Protocol for Very Low Queuing Delay (L4S)".
[50] IETF RFC 9332: "Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)".
[51] IETF RFC 6040: " Tunnelling of Explicit Congestion Notification".
[52] IETF RFC 9599: "Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP".
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
3 Definitions and abbreviations
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 23.501 [2] , TS 23.502 [3] and TS 23.503 [4] apply. A term defined in TS 23.501 [2], TS 23.502 [3] or TS 23.503 [4] takes precedence over the definition of the same term, if any, in any other specifications.
RG Level Wireline Access Characteristics: Wireline access technology specific QoS information corresponding to a specific wireline access subscription, which is provided by the AMF to the W-AGF at RG registration.
Wireline access Control Plane protocol (W-CP): Protocol used to transport AS and NAS signalling between the 5G-RG and the W-AGF over the Y4 reference point. W-CP is specified by BBF and CableLabs. There is no assumption that W-CP refers to only a single protocol or only a specific protocol layer.
Wireline access User Plane protocol (W-UP): Protocol used to carry PDU Session user plane traffic between the 5G-RG and the W-AGF over the Y4 reference point. W-UP is specified by BBF and CableLabs. There is no assumption that W-UP refers to only a single protocol or only a specific protocol layer.
Legacy Wireline access Control Plane protocol (L-W-CP): L-W-CP is a legacy control plane protocol between the FN-RG and W-AGF. L-W-CP is specified by BBF and CableLabs. There is no assumption that L-W-CP refers to only a single protocol or only a specific protocol layer.
Legacy Wireline access User Plane protocol (L-W-UP): L-W-UP is a legacy user plane protocol between the FN-RG and W-AGF. W-UP is specified by BBF and CableLabs. There is no assumption that L-W-UP refers to only a single protocol or only a specific protocol layer.
Authenticable Non-3GPP (AUN3) device: A device that does not support NAS signalling, is connected to 5GC via a RG and can be authenticated by 5GC over the RG.
5GS specifications do not support a device using the same subscription to access 5GS as a UE and as an AUN3 device.
Non-Authenticable Non-3GPP (NAUN3) device: A device that does not support NAS signalling, is connected to 5GC via a RG and for which authentication with 5GC is not supported.
NOTE 1: AUN3 and NAUN3 device can connect to RG through WLAN (collocated or not collocated with the RG) and/or wired Ethernet connections.
NOTE 2: A device can operate as a UE over NG-RAN and as a AUN3 or NAUN3 via a RG, if the device implements UE functionality.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] apply. An abbreviation defined in TS 23.501 [2], TS 23.502 [3] or TS 23.503 [4] takes precedence over the same abbreviation, if any, in any other specifications.
5G-RG 5G Residential Gateway
5G-BRG 5G Broadband Residential Gateway
5G-CRG 5G Cable Residential Gateway
ACS Auto-Configuration Server
FN-RG Fixed Network RG
FN-BRG Fixed Network Broadband RG
FN-CRG Fixed Network Cable RG
FWA Fixed Wireless Access
IGMP Internet Group Management Protocol
L-W-CP Legacy Wireless access Control Plane Protocol
L-W-UP Legacy Wireless access User Plane Protocol
MLD Multicast Listener Discovery
RG Residential Gateway
RG-LWAC RG Level Wireline Access Characteristics
SNPN Stand-alone Non Public Network
USP User Services Platform
W-5GAN Wireline 5G Access Network
W-5GCAN Wireline 5G Cable Access Network
W-5GBAN Wireline BBF Access Network
W-CP Wireline access Control Plane protocol
W-UP Wireline access User Plane protocol
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4 High level features
|
This clause specifies high level description equivalent to TS 23.501 [2].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.1 General
|
The roaming support for W-5GAN access is not specified in this release.
The usage of Trusted or Untrusted access to 5GC by a 5G-RG or by a FN RG is not applicable.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.2 Network Access Control
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.2.0 General
|
This clause specifies the delta related to network access control defined in TS 23.501 [2] clause 5.2.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.2.1 Network selection
|
In the case of 5G-RG or FN-RG connected via W-5GAN the PLMN selection specification defined in TS 22.011 [25] and in TS 23.122 [26] and the SNPN selection specification defined in TS 24.502 [44] is not applicable. The HPLMN is implicitly selected by wired physical connectivity between 5G-RG or FN-RG and W-AGF.
NOTE 1: The 5G-RG or FN-RG can only connect to a single physical wired access W-5GAN to a W-AGF configured at line provisioning by the operator, in addition no PLMN information is advertised by AS protocols in W-5GAN, since the Network selection feature is not supported.
The roaming scenario is not supported in this Release of the specification.
In the case of 5G-RG connected via FWA TS 23.501 [2] clause 5.2.2 applies with the following difference:
- The PLMN selection defined in TS 22.011 [25] and in TS 23.122 [26] applies with the UE replaced by 5G-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.2.2 Identification and authentication
|
In the case of 5G-RG connected via W-5GAN or FWA, the specification defined in TS 23.501 [2] clause 5.2.3 applies with the following difference:
- UE is replaced by 5G-RG.
In the case of FN-RG connected via W-5GAN, the specification defined in TS 23.501 [2] clause 5.2.3 applies with the following differences:
- UE is replaced by FN-RG.
- The W-AGF provides the NAS signalling connection to the 5GC on behalf of the FN-RG.
- The W-5GAN may authenticate the FN-BRG per BBF specification BBF TR-456 [9] and WT-457 [10]. The W-5GAN may authenticate the FN-CRG per CableLabs DOCSIS MULPI [8].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.2.3 Authorisation
|
In the case of 5G-RG connected via W-5GAN or FWA, the specification defined in TS 23.501 [2] clause 5.2.4 applies with the following differences:
- UE is replaced by 5G-RG.
In the case of FN-RG connected via W-5GAN, the specification defined in TS 23.501 [2] clause 5.2.4 applies with the following differences:
- UE is replaced by FN-RG.
- W-AGF performs the UE Registration procedure on behalf of the FN-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.2.4 Access control and barring
|
In the case of 5G-RG or FN-RG connected via W-5GAN the Access Control and Barring defined in TS 23.501 [2] clause 5.2.5 is not applicable.
In the case of 5G-RG connected via FWA the specification defined in TS 23.501 [2] clause 5.2.5 applies with the following difference:
- UE is replaced by 5G-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.2.5 Policy control
|
Policy control is specified in clause 9.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.2.6 Lawful Interception
|
In the case of 5G-RG connected via FWA the specification defined in TS 23.501 [2] clause 5.2.7 applies with the following difference:
- UE is replaced by 5G-RG.
In the case of 5G-RG connected via W-5GAN, the definition and functionality of Lawful Interception defined in TS 33.126 [32] applies with the following difference:
- UE is replaced by 5G-RG.
In the case of FN-RG connected via W-5GAN, the definition and functionality of Lawful Interception defined in TS 33.126 [32] applies with the following difference:
- UE is replaced by FN-RG, with e.g. the difference that FN-RG may not have a globally unique PEI (as described in clause 4.7.7) and does not hold any 3GPP-based subscriber credentials or subscriber identity information.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.3 Registration and Connection Management
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.3.1 Registration management
|
Registration management when 5G-RG or FN-RG is connected to 5GC via wireline access is described in TS 23.501 [2] clause 5.5.1.
Registration management when 5G-RG is connected to 5GC via NG RAN access is described in TS 23.501 [2], clause 5.3.2.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.3.2 Connection management
|
Connection management when 5G-RG or FN-RG is connected to 5GC via wireline access is described in clause 5.5.2 of TS 23.501 [2].
Connection management when 5G-RG is connected to 5GC via NG RAN access is described in clause 5.3.3 of TS 23.501 [2].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.3.3 Mobility Restrictions
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.3.3.1 General
|
Mobility Restrictions restrict service access of an 5G-RG depending on RG location.
For a 5G-RG connecting over NG-RAN, the Mobility Restriction functionality as described in clause 5.3.4.1 of TS 23.501 [2] applies.
For an 5G-RG connecting over wireline access, the Mobility Restriction functionality is described in this clause.
Mobility restrictions do not apply to scenarios with FN-BRG.
NOTE 1: Since access to 5GC for FN-BRG subscriptions are identified by a SUPI determined from the GLI as described in clause 4.7.3 and clause 4.7.8. Such subscriptions are by definition restricted to a specific location.
NOTE 2: For FN-CRG subscriptions, HFC Node ID is used to identify the location of FN-CRG, thus service area restrictions for the FN-CRG can be identified by an HFC_Node ID, or by a list of HFC_Node ID.
Mobility Restrictions for wireline access consists of Forbidden Area and Service Area Restrictions, as described in the following clauses.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.3.3.2 Management of Forbidden Area in wireline access
|
In a Forbidden Area, the 5G-RG, based on subscription, is not permitted by the 5GC to initiate any communication with the 5GC for this PLMN or SNPN.
The UDM stores the Forbidden Area for wireline access in the same way as for 3GPP access, with the following differences:
- For subscriptions for 5G-BRG, GLI is used to describe the Forbidden Area.
- For subscriptions for 5G-CRG and FN-CRG, HFC Node IDs are used to describe the Forbidden Area (instead of TA).
- The Forbidden Area in UDM can be encoded as a "allow list" indicating the non-forbidden area. In this case all GLI or HFC_Node ID values not included in the list are considered forbidden.
NOTE: The use of "allow list" is to ensure an efficient Forbidden Area definition if only a small set of GLI / HFC Node ID values are not forbidden.
Forbidden Area is enforced by AMF, based on subscription data and the location information received from W-AGF. The AMF rejects a Registration Request from a 5G-RG or the W-AGF acting on behalf of a FN-CRG in a Forbidden Area with a suitable cause code. The 5G-RG behaviour depends on the network response (cause code from AMF) that informs the RG that communication is forbidden.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.3.3.3 Management of Service Area Restrictions in wireline access
|
The subscription data in the UDM for a 5G-BRG includes a Service Area Restriction which may contain either Allowed or Non-Allowed Areas specified by using explicit GLI(s) and/or other geographical information (e.g., longitude/latitude, zip code, etc.).
The subscription data in the UDM for a 5G-CRG and FN-CRG includes a Service Area Restriction which may contain either Allowed or Non-Allowed Areas specified by using explicit HFC Node IDs and/or other geographical information (e.g., longitude/latitude, zip code, etc.).
The geographical information used to specify allowed or non-allowed area is only managed in the network, and the network will map it to a list of GLI(s) or HFC Node IDs before sending Service Area Restriction information to the PCF.
The UDM stores the Service Area Restrictions for the 5G-RG or FN-CRG as part of the subscription data. The PCF in the serving network may (e.g. due to varying conditions such as 5G-RG's location, time and date) further adjust Service Area Restrictions of a 5G-RG, either by expanding an allowed area or by reducing a non-allowed area. The UDM and the PCF may update the Service Area Restrictions of a 5G-RG or a FN-CRG at any time.
During registration, if the Service Area Restrictions of the 5G-RG or FN-CRG is not present in the AMF, the AMF fetches from the UDM the Service Area Restrictions of the 5G-RG or FN-CRG that may be further adjusted by the PCF. The serving AMF shall enforce the Service Area Restrictions of a 5G-RG and a FN-CRG. The AMF receives the location information (GLI, HFC Node IDs) where the RG is connected from the W-AGF via N2.
The network does not send any Allowed Area or Non-Allowed Area to the 5G-RG for wireline access. If the 5G-RG initiates communication in an Allowed Area, the network accepts the communication as allowed by the subscription. If the 5G-RG initiates Service Request or SM signalling in a Non-Allowed Area, the AMF rejects the request with a suitable cause code indicating that the 5G-RG/W-AGF should not retry Service Request and SM signalling while being connected to the same line.
Upon change of serving AMF due to mobility, the old AMF may provide the new AMF with the Service Area Restrictions of the 5G-RG that may be further adjusted by the PCF.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.4 Session management
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.4.0 General
|
This clause specifies the delta related to session management defined in TS 23.501 [2] clause 5.6.
The LADN service defined in clause 5.6.5 in TS 23.501 [2] does not apply for RG connected to 5GC via wireline access.
When handling DHCP signalling coming from a wireline BBF access, the SMF (as well as an external DHCP server used by SMF) shall support the DHCP signalling as described in in BBF TR-456 [9].
NOTE: As described in clause 5.6.14 of TS 23.501 [2], to enable Framed Routes for a PDU Session, SMF can take the UPF capabilities for Framed Routes into account when selecting a UPF for a PDU Session.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.4.1 Session management for 5G-RG
|
Session management of 5G-RG connected to 5GC via wireline access follows the principle defined in TS 23.501 [2] clause 5.6 with the following difference:
- UE is replaced by 5G-RG.
- 5G-RG is connected to 5GC via wireline RAT type instead of 3GPP access.
- ECN marking for L4S in 5G-RG in UL, controlled via N1 signalling (i.e. Indication of ECN marking for L4S for an L4S enabled QoS Flow(s)) and applies to mapping between L4S-enabled QoS rule(s) and L4S enabled W-UP resource(s).
NOTE: The mapping between L4S-enabled QoS rule(s) and L4S enabled W-UP resource(s) is up to implementation.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.4.2 Session management for FN-RG
|
Session management of FN-RG follows the principle defined in TS 23.501 [2] clause 5.6 with the follow difference:
- UE is replaced by W-AGF
- FN-RG is connected to 5GC via wireline access instead of 3GPP access.
- Secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session is applicable neither to FN-RG nor to N5GC devices.
- For FN-BRG, only SSC modes 1 or 2 can be used, depending on the type of FN-BRG as described in TR‑456 [9] and WT-457 [10].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.5 QoS model
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.5.0 General overview
|
The QoS model of TS 23.501 [2] clause 5.7 is applicable to the W-5GAN scenario, with the difference that the W-AGF acts as an Access Network (AN).
The principle for classification and marking of User Plane traffic and mapping of QoS flows to W-UP resources is illustrated in Figure 4.5-1.
Figure 4.5-1: The principle for classification and User Plane marking for QoS Flows and mapping to W-UP resources for a PDU Session
When the W-AGF receives N2 requests related with PDU Session resources, the W-AGF maps the QoS profile(s) received from the 5GC to W-UP level QoS.
When the 5G-RG receives NAS message related with PDU Session QoS, the 5G-RG maps the QoS rule(s) received in NAS to W-UP level QoS.
One W-UP resource can be used as the default W-UP resource. There shall be one and only one Default W-UP resource per PDU session. The 5G-RG shall send all QoS Flows to this W-UP resource for which there is no mapping information to a specific W-UP resource.
Handling of UL traffic by the 5G-RG:
- When the 5G-RG transmits an UL PDU, the 5G-RG shall determine the QFI associated with the UL PDU (by using the QoS rules of the PDU Session), it shall encapsulate the UL PDU inside an access layer dependent W-UP packet and shall forward the W-UP packet to W-AGF via the W-UP resource associated with this QFI.
Handling of DL traffic by W-AGF:
- When the W-AGF receives a DL PDU via N3, it identifies of the PDU Session and optionally the QFI in order to determine the W-UP resource to use for sending the DL PDU to the 5G-RG. The W-AGF may include also in the W-UP header the Reflective QoS Indicator (RQI), which shall be used by the 5G-RG to enable reflective QoS.
The W-AGF will map 5QI received from the 5GC into access-specific QoS parameters relevant to the wireline access network. The mapping of 5QI to W-5GBAN QoS parameters is specified by the BBF for W-5GBAN in [9]. The mapping of 5QI to W-5GCAN QoS parameters is specified for W-5GCAN in CableLabs WR-TR-5WWC-ARCH [27].
QFI or other QoS parameters are carried via W-UP to the 5G-CRG as specified in CableLabs WR-TR-5WWC-ARCH [27].
The QFI and RQI are carried via W-UP to 5G-RG as specified in BBF TR-456 [9].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.5.1 Wireline access specific 5G QoS parameters
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.5.1.0 Overview
|
The 5G QoS parameters specified in clause 5.7.2 of TS 23.501 [2] are applicable to wireline access network, with the following differences:
- The parameters defined in clause 4.5.1.2 are applicable for the wireline access network related PDU sessions.
- UE-AMBR is not applicable to wireline access. The AMF should not provide the subscribed UE-AMBR to the W-AGF.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.5.1.1 Void
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.5.1.2 RG Level Wireline Access Characteristics
|
The wireline access networks may exhibit QoS control mechanisms and related thresholds, such as QoS class specific maximum bit rates, which the W-AGF needs to be aware of, in order to provide appropriate mapping of the QoS characteristics of the 5G QoS flows to the wireline technology specific QoS parameters.
These wireline access characteristics are considered to be relevant for a specific wireline access subscription, and correspond to RG level QoS information in the 5GC.
While the wireline access characteristics are important for implementing the end to end QoS mechanisms, across the 5G-RG/FN-RG, the W-5GAN and the 5GC, they only need to be acted on in the 5G-RG/FN-RG and the W-5GAN.
In the case of 5G-RG serving the AUN3 devices, the RG Level Wireline Access Characteristics stored in 5G-RG's subscription includes a maximum bit rate for the aggregated traffic of the 5G-RG and of the AUN3 devices served by this 5G-RG.
In order to support the W-AGF in implementing the mapping between 5G QoS parameters and wireline access specific parameters, the AMF may provide the RG Level Wireline Access Characteristics (RG-LWAC) to the W-AGF at the time of the RG registration. When the UDM notifies the AMF of the updated RG-LWAC via Nudm_SDM_Notification service, the AMF may update the RG-LWAC to the W-AGF via NGAP UE Context Modification procedure.
Given that the 5GC does not act on these parameters, their structure is out of scope in 3GPP specifications and they are handled as a transparent data container. BBF and CableLabs may define the content and structure of this container for their own use.
The UE subscription data parameters RG Level Wireline Access Characteristics are defined in clause 8.1.1.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.5.2 QoS model applied to FN-RG
|
The FN-RG does not support 3GPP signalling and therefore, mapping and interworking between 5G QoS and the wireline access network resources is managed by the W-AGF on behalf of the FN-RG.
The mapping of W-5GAN resources and 5GC QoS is configured in the W-AGF for the FN-CRG is specified by CableLabs. Resource management within the W-5GAN for the FN-CRG is specified by CableLabs.
The mapping of W-5GAN resources and 5GC QoS is configured in the W-AGF for the FN-BRG is specified by BBF. Resource management within the W-5GAN for the FN-BRG is specified by BBF.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.5.3 Differentiated QoS for devices behind 5G-RG
|
During PDU session establishment and PDU session modification, if the SMF provides the 5G-RG with QoS flow descriptions, the SMF may additionally signal Non-3GPP QoS Assistance Information (N3QAI) for each QoS flow to the 5G-RG). Based on the N3QAI together with QoS rule information, the 5G-RG may reserve resources in the non-3GPP network behind the 5G-RG (e.g. home LAN network). N3QAI consists of the following QoS information: QoS characteristics, GFBR/MFBR, Maximum Packet Loss Rate, ARP and Periodicity (if available at the SMF).
NOTE 1: How 5G-RG uses the Non-3GPP QoS Assistance Information to enforce QoS in the non-3GPP network is outside the scope of 3GPP.
NOTE 2: Transferring information like Periodicity to the 5G-RG is not meant to support TSC/TSN like flows but to support consumer real time applications like XR (extended Reality, etc.).
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.6 User Plane management
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.6.1 General
|
The management of the user plane follows the description in clause 5.8 of TS 23.501 [2] with additional specification described below in this clause.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.6.2 IP address allocation
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.6.2.1 General
|
IP address allocation is performed as described in TS 23.501 [2] clause 5.8.2.2, with the differences and additions described in this clause.
Stateless IPv6 Address Autoconfiguration applies with the differences described in clause 4.6.2.4.
In addition to the IP address management features described in TS 23.501 [2] clause 5.8.2.2 the 5GC network functions and RG support the following mechanisms:
a. IPv6 address allocation using DHCPv6 may be supported for allocating individual /128 IPv6 address(es) for a PDU Session. The details of IPv6 address allocation using DHCPv6 are described in clause 4.6.2.2.
b. IPv6 Prefix Delegation using DHCPv6 may be supported for allocating additional IPv6 prefixes for a PDU Session. The details of Prefix Delegation are described in clause 4.6.2.3.
The mechanisms in a. and b. above are only applicable for IPv6 and IPv4v6 PDU Session types.
The requested IPv6 address or set of IPv6 Prefixes may be (as defined in TS 23.501 [2] clause 5.8.2.2.1):
- allocated from a local pool in the SMF or
- obtained from the UPF. In that case the SMF shall interact with the UPF via N4 procedures to obtain a suitable IP address/Prefix, or
- obtained from an external server.
When obtaining the IP address from the UPF, the SMF provides the UPF with the necessary information allowing the UPF to derive the proper IP address (e.g. the network instance, IP version, size of the IP address or Prefix the UPF is to allocate).
The SMF may also provide IP configuration parameters (e.g. MTU value) to the 5G-RG, as described in clause 5.6.10 of TS 23.501 [2].
NOTE: In order to provide an IP MTU value that is specifically suitable for W-5GAN without considering N3 in case of combined W-AGF/UPF, the SMF can e.g. be configured with such MTU for a given DNN and/or for a given slice whether the DNN and/or the slice only serves wireline access and a UPF combined with the W-AGF has been selected for the PDU Session.
In this clause, unless specified otherwise, the RG may correspond either to a 5G RG or to a FN RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.6.2.2 IPv6 Address Allocation using DHCPv6
|
Optionally, and instead of using Stateless IPv6 Address Autoconfiguration, individual 128-bit IPv6 address(es) may be assigned to a PDU Session.
In this case, after PDU Session Establishment, the SMF sends a Router Advertisement message (solicited or unsolicited) towards the RG. The SMF shall set the Managed Address Configuration Flag (M-flag) in the Router Advertisement messages to indicate towards the RG that IPv6 Address allocation using DHCPv6 is available, as described in RFC 4861 [34]. In that case the IPv6 address of the RG is allocated using DHCPv6 Identity Association for Non-temporary Addresses (IA_NA) and mechanisms defined in RFC 8415 [47].
The SMF may receive a Router Solicitation message, soliciting a Router Advertisement message.
When using DHCPv6 address allocation, a prefix (e.g. /64) may be allocated for the PDU Session at PDU Session Establishment from which the /128 addresses are selected. The SMF determines the size of the prefix for a PDU Session to a specific DNN and S-NSSAI based on subscription data and local configuration. The individual /128 address(es) allocated to the RG as part of DHCP IA_NA procedure are then selected from the prefix allocated to the PDU Session. For statically assigned prefix, the subscription data in UDM for a DNN and S-NSSAI includes the prefix. Alternatively, individual 128-bit address(es) are allocated for the PDU Session without allocating a prefix to the PDU Session and provided to the RG as part of DHCP IA_NA procedure.
When a prefix is allocated to the PDU Session, the SMF provides the prefix to the PCF instead of each /128 address. When individual /128 address(es) are allocated without allocating a prefix to the PDU Session, the SMF provides the /128 bits address(es) to PCF. Whether the SMF allocates a prefix for the PDU Session or individual 128-bit addresses is transparent to the RG and W-5GAN.
If Prefix Delegation (as described in clause 4.6.2.3) is also supported, a SMF may receive both DHCP options for IA_NA and IA_PD together in a single DHCPv6 message. An SMF may provide a reply to both IA_NA and IA_PD in the same message or alternatively process the DHCPv6 IA_NA before the DHCPv6 IA_PD.
The SMF may receive multiple different IA_NA related DHCP requests within the same PDU Session.
NOTE: This is applicable if the RG acts as a DHCP relay for devices behind the RG.
When IPv6 Address Allocation using DHCPv6 is used, 5GC does not support IPv6 multi-homing for enabling SSC mode 3 and PDU Sessions with multiple PDU Session Anchors.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.6.2.3 IPv6 Prefix Delegation via DHCPv6
|
In addition to what is the specified in clause 5.8.2.2.4 of TS 23.501 [2], there is following difference:
- UE is replaced by 5G-RG and FN-RG.
- For IPv6 stateless IPv6 address autoconfiguration or IPv6 address allocation using DHCPv6, the SMF determines the maximum size of the prefix that may be allocated for the PDU Session based on subscription data and local configuration.
- If IPv6 address allocation using DHCPv6 is used, the DHCPv6 message may include a request for a delegated prefix (IA_PD) together with a request for an IPv6 address (IA_NA). Alternatively, a delegated prefix may be requested after an IPv6 address has been assigned using IA_NA.
- If the DHCPv6 request indicates support for prefix exclusion via the OPTION_PD_EXCLUDE option code in an OPTION_ORO option and if the SMF accepts this option, the SMF delegates a prefix excluding the default prefix with help of OPTION_PD_EXCLUDE. Prefix exclusion procedures shall follow IETF RFC 6603 [16].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.6.2.4 The procedure of Stateless IPv6 Address Autoconfiguration
|
Stateless IPv6 Address Autoconfiguration applies as described in clause 5.8.2.2.3 of TS 23.501 [2] with the differences described below.
When the W-AGF is serving an FN-RG, the W-AGF may include in the PDU Session Establishment Request an interface identifier of the FN-RG IPv6 link-local address associated with the PDU Session. If the SMF receives an interface identifier in the PDU Session Establishment Request message, the SMF provides this interface identifier value as the UE interface identifier in the PDU Session Establishment Accept message. To ensure that the link-local address used by the FN-RG does not collide with the link-local address of the SMF in this case, the SMF selectes a different link-local address for use as the SMF link local address for the PDU Session. If the PDU Session Establishment Request message does not contain an interface identifier, the SMF selects interface identifier for the UE, and SMF link-local address, as described in clause 5.8.2.2.3 of TS 23.501 [2].
NOTE 1: An FN-RGs is configuring its IPv6 link local address based on its MAC address and is not able to use an interface identifier selected by SMF as described in clause 5.8.2.2.3 of TS 23.501 [2].
In case of wireline access, independent of whether SMF received an interface identifier in the PDU Session Establishment Request message or not, the SMF includes the SMF link local address in the PDU Session Establishment Accept message.
NOTE 2: The SMF link local address is needed by the W-AGF to support procedures towards the FN-RG defined in BBF TR-456 [9].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.6.3 Packet Detection Rule
|
PDR used to support PDU Sessions for RG follow the specifications in TS 23.501 [2] clause 5.8.2.11.3 with the clarifications and additions shown below.
For PDU Session used for IPTV service, (see also clause 4.6.6):
- Packets Filter Set support Packet Filters for IGMP, including IGMPv2 specified in RFC 2236 [33], IGMPv3 specified in RFC 4604 [21], for MLDv1 specified in RFC 2710 [36] and MLDv2 specified in RFC 4604 [21]. The PDR may also contain IP Multicast addressing information that may refer to ranges of IP multicast addresses. Such IP Multicast addressing information is not part of the PDI. The packets filters for IGMPv1 defined in RFC 1112 [35] are not supported.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.6.4 Forwarding Action Rule
|
FAR used to support PDU Sessions for RG follow the specifications in TS 23.501 [2] clause 5.8.2.11.6 with the clarifications and additions and difference shown below.
For PDU Sessions used for IPTV service (see also clause 4.6.6):
- Following additional "Action" values are used to support IPTV service:
- "IP Multicast Accept" indicates whether in the case of IGMP and MLD Membership Report message to accept the multicast join and add the PDU Session to the requested multicast group distribution. This may also imply acting as an IP Multicast Router as described in clause 7.7.1.1
NOTE 1: The IGMP "Join message" and MLD "Join message" are generic terms used in this document to indicate the request of a host to join a multicast group which can express via IGMP and MLD Report message (e.g. Membership Report) or via Join message.
NOTE 2: In this specification the generic term IGMP refers to both IGMPv2 and IGMPv3 unless specifically defined. The term MLD refers to both MLDv1 and MLDV2 unless specifically defined.
- "IP Multicast Accept" indicates that when UPF detects the IGMPv3 Leave message or a MLD Done message via the PDU Session, the UPF needs also to ensure that the PDU Session is removed from the requested multicast group distribution.
- "IP Multicast Deny" indicates that the UPF shall not accept the corresponding IGMP and MLD Membership Report message to join a multicast group.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.6.5 Usage Reporting Rule
|
URR used to support PDU Sessions for RG follow the specifications in TS 23.501 [2] clause 5.8.2.11.5 with the clarifications and additions shown below:
For PDU Sessions used for IPTV service (see also clause 4.6.6), an URR may indicate a Reporting trigger (defined in TS 23.501 [2] clause 5.8.2.11.5) with a value Reporting Trigger set to "IGMP reporting" for IGMP or set to "MLD reporting" for MLD where the UPF is to report to the SMF when
- it adds a PDU session to the DL replication tree associated with an IP Multicast flow;
- it removes a PDU session from the DL replication tree associated with an IP Multicast flow.
The corresponding notification shall contain the (Source IP address of the DL multicast flow, Destination IP address of the DL multicast flow).
NOTE: The corresponding notification can be used by the SMF to report the information to the PCF and/or to CHF.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.6.6 Usage of N4 to support IPTV
|
The SMF sends to the UPF acting as PSA N4 rules such as PDR, FAR related to IP Multicast traffic allowed for the PDU Session of a 5G-RG. IP Multicast traffic allowed for the PDU Session corresponds to IPTV services allowed for the user. IP Multicast Addressing information identifies such traffic. In the case Source Specific Multicast is configured to be used on the PDU Session, IP Multicast Addressing information refers to both IP Multicast address and Source IP address.
The SMF may need to take into account UPF capability to support the features described in this clause when selecting an UPF to serve a PDU Session. For IPv6 PDU session IPTV services will be based on MLD , for IPV4 PDU session on IGMP.
N4 rules for IP Multicast traffic related to IPTV service may correspond to:
- Rules related with UL IGMP or MLD traffic:
- a PDR identifying IGMP signalling or MLD together with IP Multicast Addressing information identifying a set of IP multicast groups;
NOTE 1: The IP Multicast Addressing information may correspond to ranges of IP Multicast addresses
- a FAR with:
- an "IP Multicast Accept" action in order to request the UPF to accept UE requests to join the corresponding IP multicast group(s); or
- an "IP Multicast Deny" action in order to request the UPF to deny UE requests to join the corresponding IP multicast group(s);
- possibly a URR with a Reporting Trigger set to "IGMP reporting" for IGMP or set to "MLD reporting" for MLD.;
- Rules related with DL IP Multicast traffic:
- a PDR identifying IP Multicast Addressing information (DL IP Multicast traffic);
NOTE 2: The IP Multicast Addressing information may correspond to ranges of IP Multicast addresses
- a FAR asking to add outer header = GTP-u tunnel related with the PDU Session of the 5G RG;
- a QER indicating the QoS to use towards the 5G-RG for the IP Multicast traffic that has been replicated.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.7 Identifiers
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.7.1 General
|
As described in TS 23.501 [2], each subscriber in the 5G System shall be allocated one 5G Subscription Permanent Identifier (SUPI) for use within the 3GPP system. As described in TS 23.501 [2], each FN-RG or 5G-RG accessing the 5G System shall be assigned a Permanent Equipment Identifier (PEI).
The clauses below describe specific aspects for supporting 5G-RG and FN-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.7.2 SUPI and SUCI for 5G-BRG support
|
For PLMNs, the SUPI for a 5G-BRG shall contain an IMSI, as described in clause 5.9.2 of TS 23.501 [2]. The SUPI for accessing SNPN is defined in clause 4.16.1.
The SUCI provided by the 5G-BRG to the network contains the concealed SUPI, as described in TS 33.501 [11].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.7.3 SUPI and SUCI for FN-BRG support
|
The SUPI for an FN-BRG subscription shall, based on operator configuration, either contain an IMSI or a GLI as defined in clause 4.7.8. A SUPI containing a GLI takes the form of a NAI whose user part is the GLI and whose realm part is an identifier of the operator owning the subscription.
The SUCI provided by the W-AGF to the 5GC for FN-BRG always corresponds to a SUPI containing a GLI. This SUCI acts as pseudonym of the SUPI and the UDM performs a mapping to the actual SUPI that, depending on operator configuration, contains either an IMSI or the same GLI that was provided in the SUCI.
As described in TS 23.003 [14], the SUCI also contains an identifier of the Home network, i.e. the identifier of the operator owning the subscription.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.7.4 SUPI and SUCI for 5G-CRG and FN-CRG support
|
The SUPI for a FN-CRG subscription shall, based on operator configuration, contain either an IMSI, as described in clause 5.9.2 of TS 23.501 [2], or a GCI (Global Cable identifier defined in clause 4.7.9).
The SUPI for a 5G-CRG subscription shall, based on operator configuration, contain either an IMSI, as described in clause 5.9.2 of TS 23.501 [2], or a GCI (Global Cable identifier defined in clause 4.7.9).
For PLMNs, only 5G-CRG whose SUPI corresponds to an IMSI may use 3GPP access to connect to 5GC. The SUPI for accessing SNPN is defined in clause 4.16.1.
A SUPI containing a GCI takes the form of a NAI where the user part is the GCI and the realm part is an identifier of the operator managing the subscription.
NOTE 1: The realm part used to identify the operator managing the subscription can differ depending on whether the wireline access network belongs to a PLMN or SNPN. The NAI format for SUPI containing GCI for PLMN and SNPN is defined in TS 23.003 [14].
The SUCI provided by the 5G-CRG to the network contains the concealed SUPI, as described in TS 33.501 [11].
The SUCI provided to the network for FN-CRG support always corresponds to a SUPI containing a GCI. This SUCI acts as pseudonym of the SUPI and the UDM performs a mapping to the SUPI that, depending on operator configuration, contains either an IMSI or the same GCI than in the SUCI.
As described in TS 23.003 [14], for both cases where the SUCI contains an IMSI or contains a GCI, the SUCI contains an identifier of the Home network i.e. an identifier of the operator managing the subscription.
NOTE 2: If the SUCI contains an IMSI, the identifier of the operator managing the subscription is carried in the MCC/MNC part of the IMSI as defined in TS 23.003 [14].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.7.5 Line ID
|
The Line ID is defined in BBF Specifications, see BBF TR-470 [38].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.7.6 HFC identifier
|
The HFC_Identifier may contain a cable modem MAC address or an overall HFC account identifier, as defined by CableLabs in DOCSIS MULPI [8].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.7.7 PEI
|
If the 5G-RG (i.e. 5G-BRG and 5G-CRG) supports at least one 3GPP access technology (i.e. NG-RAN, E-UTRAN), the 5G-RG must be allocated a Permanent Equipment Identifier (PEI) in the IMEI or IMEISV format, as described in TS 23.501 [2]. The 5G-RG shall present this PEI to the network independent of access technology used by the 5G-RG (3GPP access technology or W-5GAN access technology).
If the 5G-BRG supports only W-5GAN access, the PEI shall contain the 5G-BRG MAC address.
If the 5G-CRG supports only W-5GAN access, the PEI shall contain the cable modem MAC address.
For FN-RG (i.e. FN-BRG and FN-CRG), the W-AGF shall provide a PEI containing:
- The FN-RG MAC address: this shall be used by the W-AGF when it is known by configuration that the MAC address received by the W-AGF is unique (no other entity can use the same MAC address) and corresponds to the permanent MAC address configured on the RG by the manufacturer.
NOTE 1: This assumes that the W-AGF can see the actual permanent MAC address of the FN-RG and not the MAC address of any intermediate entity (e.g. DSLAM).
- The MAC address received by the W-AGF, together with an indication provided by the W-AGF that this address cannot be used as an Equipment identifier of the FN-RG: this shall be used by the W-AGF when the conditions to provide a PEI containing the FN-RG MAC address are not met.
NOTE 2: This is to support the case of legacy deployments for FN RG where either multiple FN RG can share the same MAC address or where the MAC address received by the W-AGF is not that of the FN RG but the MAC address of an intermediate entity between the FN RG and the W-AGF.
NOTE 3: When the PEI contains an indication that the MAC address cannot be used as an Equipment identifier of the FN-RG, the PEI cannot be trusted for regulatory purpose but it can be stored in CDR and used for troubleshooting.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.7.8 Global Line Identifier
|
For usage with 5GC, a Global Line Identifier (GLI) is specified in order to define a globally unique identifier of the line connecting the RG to the network. In this release an RG is associated with a unique GLI.
For FN BRG, the GLI is used to build a SUCI. For FN-BRG the GLI may be used to build a SUPI. See clause 4.7.3. For all types of RG, the GLI is used as User Location Information on wireline access.
The GLI contains an identifier of the Line ID source and the Line ID value. The identifier of the Line ID source ensures the unicity of the GLI while the Line ID may not be unique in some deployments. The identifier of the Line ID source and Line ID are administered by the W-AGF operator.
The Global Line Identifier is a variable length identifier encoded as defined in TS 23.003 [14] and in BBF TR‑470 [38].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.7.9 Global Cable Identifier
|
For usage with 5GC, a Global Cable Identifier (GCI) is specified in order to define a globally unique identifier of the line connecting the CRG to the network. In this release an RG is associated with a unique GCI.
The GCI contains the HFC_Identifier which is defined in CableLabs WR-TR-5WWC-ARCH [27].
For FN CRG, the GCI is used to build a SUCI. For FN CRG the GCI may be used to build a SUPI. See clause 4.7.4. For all types of CRG the HFC Node ID is used to build User Location Information on Cable access.
The identifier of the HFC Node ID and the HFC_Identifier are administered by the W-AGF operator.
The Global Cable Identifier is a variable length identifier encoded as defined in TS 23.003 [14] and CableLabs WR‑TR‑5WWC‑ARCH [27].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.7.10 RAT types dedicated for Wireline access
|
The AMF, as described in TS 23.501 [2] clause 5.3.2.3, determines the RAT Type for Wireline access, taking into account the Global W-AGF Node ID and possibly ULI information provided by the W-AGF. The RAT Type may allow to distinguish between Wireline, Wireline-Cable access andWireline-BBF access.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.7.11 SUPI and SUCI for N5GC device or AUN3 device support
|
The SUPI for non-5G capable (N5GC) device or AUN3 device connecting via CRG shall contain a network-specific identifier. A SUPI containing a network-specific identifier takes the form of a Network Access Identifier (NAI) as defined in TS 23.003 [14].
The SUCI provided by the W-AGF to the AMF is derived from the EAP-Identity message received from the N5GC device or AUN3 device, as defined in TS 33.501 [11]. The format of this SUCI is defined in TS 23.003 [14].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.8 Security aspects
|
TS 23.501 [2] clause 5.10 applies to the FN-CRG with the following deltas:
- Mutual authentication of the FN-CRG and the wireline access network is completed as specified by CableLabs DOCSIS MULPI [8]. The successful completion of the authentication of the FN-CRG is conveyed by the W-AGF serving the FN-CRG to the AMF.
- UE is replaced by W-AGF on behalf of the FN-CRG for the balance of TS 23.501 [2] clause 5.10 and clauses.
- See TS 33.501 [11] for additional requirements
TS 23.501 [2] clause 5.10 applies to the 5G-CRG with the following deltas:
- The UE is replaced by the 5G-CRG
- Signalling security aspects between the 5G-CRG and the W-AGF are specified by CableLabs in WR-TR-5WWC-ARCH [27].
- See TS 33.501 [11] for additional requirements
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.9 Support of specific services
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.9.0 General
|
This clause specifies high level definition of services specific for WWC scenario.
PWS functionality as described in TS 23.041 [40] is not supported for Wireline access but may be supported by RG(s) connected over 3GPP access.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.9.1 IPTV
|
IPTV is defined as multimedia services such as television/video/ audio/text/graphics/data delivered over IP-based networks managed to support the required level of QoS/QoE, security, interactivity and reliability. STB obtains IPTV service via RG, including 5G-RG and FN-RG, which are connected to 5GC.
The procedures to support IPTV is specified in clause 7.7.1.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.10 UE behind 5G-RG and FN-RG
|
An RG connecting via W-5GAN or NG-RAN access towards 5GC can provide connectivity for a UE behind the RG to access an N3IWF or TNGF. It is assumed that the UE is 5GC capable, i.e. supports untrusted non-3GPP access and/or trusted non-3GPP access. This allows the RG, W-5GAN and the RG's connectivity via 5GC to together act as untrusted/trusted N3GPP access to support UEs behind the RG.
When FN-RG/5G-RG is serving a UE, the control and user plane packets of the UE is transported using a FN-RG/5G-RG IP PDU session and then from PSA UPF of that PDU session to an N3IWF or TNGF. A single FN-RG/5G-RG IP PDU session can be used to serve multiple UEs.
Figure 4.10-1 shows the non-roaming architecture for a UE, behind a 5G-RG, accessing the 5GC via TNGF where the combination of 5G-RG, W-5GAN and UPF serving the 5G-RG is acting as a trusted Non-3GPP access network.
Figure 4.10-2a shows the non-roaming architecture for a UE, behind a FN-RG, accessing the 5GC via N3IWF.
Figure 4.10-2b shows the non-roaming architecture for a UE, behind a 5G-RG, accessing the 5GC via N3IWF.
Annex A shows the non-roaming architecture for a UE, behind a FN-RG/5G-RG, accessing the 5GC via N3IWF where the combination of FN-RG/5G-RG, W-5GAN and UPF serving the 5G-RG is acting as an untrusted Non-3GPP access network.
NOTE 1: FN-RG and W-5GAN acting as trusted Non-3GPP access is not considered in this specification as it is assumed that FN-RG is not 5G capable and therefore it does not support Ta reference point.
Figure 4.10-1: Non-roaming architecture for UE behind 5G-RG using trusted N3GPP access
The 5G-RG can be connected to 5GC via W-5GAN, NG-RAN or via both accesses. The UE can be connected to 5GC via trusted non-3GPP access with 5G-RG acting as TNAP, NG-RAN or via both accesses.
Figure 4.10-2a: Architecture for UE behind FN-RG using untrusted N3GPP access
Figure 4.10-2b: Architecture for UE behind 5G-RG using untrusted N3GPP access
The FN-RG can only be connected to 5GC via W-5GAN. The 5G-RG can be connected to 5GC via W-5GAN, NG-RAN or via both accesses. The UE can be connected to 5GC via untrusted non-3GPP access with FN-RG/5G-RG acting as WLAN access point, NG-RAN or via both accesses.
The TNGF and Ta reference point are defined in TS 23.501 [2]. In addition to the requirements described in TS 23.501 [2], the Ta reference point should be able to carry the TNAP ID to the TNGF.
NOTE 2: The reference architecture in figure 4.10-1/4.10-2a/4.10-2b only shows the architecture and the network functions directly connected to W-5GAN or TNGF/N3IWF, and other parts of the architecture are the same as defined in clause 4.2 of TS 23.501 [2].
NOTE 3: The reference architecture in figure 4.10-1 supports service based interfaces for AMF, SMF and other NFs not represented in the figure.
NOTE 4: The two N2 instances in Figure 4.10-1/4.10-2b apply to a single AMF for a 5G-RG which is simultaneously connected to the same 5G Core Network over 3GPP access and W-5GAN.
NOTE 5: For trusted non-3GPP access, UE connects to the overlay 5G network using the trusted non-3GPP access approach. In addition to being connected to the underlay 5G network, the 5G-RG also acts as TNAP with respect to the TNGF in the overlay network i.e. it has an established Ta reference point with the TNGF.
NOTE 6: Support for QoS differentiation can be achieved in a similar way as it is handled when a UE connects to a PLMN via SNPN (as defined in clauses 5.30.2.7 and D.7 of TS 23.501 [2]). Also differentiated charging, both in the RG's PLMN and in the UE's PLMN, can be achieved based on existing mechanisms. This is further described in Annex B.
Support of NSWO for 3GPP UE behind an RG is specified in clause 4.10d.
A 5G-RG acting as a TNAP shall provide its TNAP ID. to the TNGF and the TNGF provides this TNAP ID as part of ULI (User Location Information) sent to the 5GC; this information is propagated to the PCF that may use it to determine PCC rules depending on whether an UE is using a 5G-RG as a host or as a guest.
NOTE 7: QoS and charging differentiation based on user location (e.g. home or guest users) can be applied when the user is connected via a TNGF reached over a 5G-RG. The PCF may use the TNAP ID, which is available to it as a part of ULI. For example, if the TNAP ID is included in the UE's policy control subscription information the UE is considered a home user. Alternatively, the PCF may use TNAP ID provided by an AF using the Service Specific parameter provisioning as defined in clause 9.8.
4.10a Non-5G capable device behind 5G-CRG and FN-CRG
For isolated 5G networks (i.e. roaming is not considered) with wireline access, non-5G capable (N5GC) devices connecting via W-5GAN can be authenticated by the 5GC using EAP based authentication method(s) as defined in TS 33.501 [11]. The following call flow describes the overall registration procedure of such a device.
Roaming is not supported for N5GC devices.
The usage of N5GC device correspond to a subscription record in UDM/UDR that is separate from that of the CRG.
Figure 4.10a-1: 5GC registration of Non-5GC device
1. The W-AGF registers the FN-CRG to 5GC as specified in clause 7.2.1.3 or the 5G-CRG registers to 5GC as specified in clause 7.2.1.1.
2. The CRG is configured as L2 bridge mode and forwards any L2 frame to W-AGF. 802.1x authentication may be triggered. This can be done either by N5GC device sending a EAPOL-start frame to W-AGF or W-AGF receives a frame from an unknown MAC address.
How the CRG is configured to work in L2 bridge mode and how the W-AGF is triggered to apply procedures for N5GC devices is defined in CableLabs WR-TR-5WWC-ARCH [27].
The N5GC device send an EAP-Resp/Indentity including its Network Access Identifier (NAI) in the form of username@realm.
3. W-AGF, on behalf of the N5GC device, sends a NAS Registration Request message to AMF with a device capability indicator that the device is non-5G capable. For this purpose, the W-AGF creates a NAS Registration Request message containing a SUCI. The W-AGF constructs the SUCI from the NAI received within EAP-Identity from the N5GC device as defined in TS 33.501 [11].
Over N2 there is a separate NGAP connection per N5GC device served by the W-AGF.
When it provides (over N2) ULI to be associated with a N5GC device, the W-AGF builds the N5GC's ULI using the GCI (see clause 4.7.9) of the CRG connecting the N5GC device.
NOTE: How the W-AGF determines the CRG connecting a N5GC device is specified in CableLabs WR-TR-5WWC-ARCH [27].
4. AMF selects a suitable AUSF as specified in TS 23.501 [2] clause 6.3.4.
5. EAP based authentication defined in TS 33.501 [11] is performed between the AUSF and N5GC device.
Once the N5GC device has been authenticated, the AUSF provides relevant security related information to the AMF. AUSF shall return the SUPI (this SUPI corresponds to a NAI that contains the username of the N5GC device and a realm as defined in TS 33.501 [11]) to AMF only after the authentication is successful.
NOTE: Each N5GC device is registered to 5GC with its own unique SUPI.
6. The AMF performs other registration procedures as required (see TS 23.502 [3] clause 4.2.2.2.2).
When providing a PEI for a N5GC device, the W-AGF shall provide a PEI containing the MAC address of the N5GC device. The W-AGF may, based on operator policy, encode the MAC address of the N5GC device using the IEEE Extended Unique Identifier EUI-64 format (see IEE Publication [41]).
7. The AMF sends Registration Accept message to W-AGF.
Once the registration procedure is completed, the W-AGF requests the establishment of a PDU Session on behalf of the N5GC device. Only one PDU session per N5GC device is supported. The procedure is the same as the PDU Session establishment procedure specified in clause 7.3.4 with the difference as below:
After successful registration, PDU Session establishment/modification/release procedure specified in clause 7.3.4, 7.3.6, and 7.3.7 apply with the difference as below:
- FN-RG is replaced by N5GC device.
The W-AGF shall request the release of the NGAP connection for each N5GC device served by a CRG whose NGAP connection has been released.
5G-CRG behaves as FN-CRG (i.e. L2 bridge mode) when handling N5GC devices.
4.10b Differentiated services for NAUN3 devices behind 5G-RG
NAUN3 devices cannot be authenticated by 5GC but may e.g. be locally authenticated by the 5G-RG using e.g. pre-shared secret. Differentiated services (QoS, network slicing) may be provided for NAUN3 devices as defined in this clause.
"Connectivity Group IDs" may be defined on the 5G-RG where each Connectivity Group ID corresponds to a separate physical or virtual port on the 5G-RG. These ports could, for example, refer to separate physical ethernet ports and/or to separate WLAN SSIDs and/or to a separate VLAN. The devices that connect to a certain logical port are considered part of the same Connectivity Group ID. How this configuration on the 5G-RG is done is out of scope of this specification.
Each Connectivity Group ID is then mapped to a separate PDU Session that is established by the 5G-RG based on the procedures defined in clause 7. The overall architecture is illustrated in Figure-4.10b-1.
Figure 4.10b-1: Example scenario for NAUN3 devices behind 5G-RG based on connectivity groups
The 5G-RG is configured with the (virtual) port information (e.g. VLANs and SSIDs) based on TR-69 [18], TR-360 and TR-181 [46]. URSP rules can be provided to the 5G-RG to indicate how to map Connectivity Group ID to the parameters of the PDU Session used to carry the traffic of corresponding devices e.g. DNN, S-NSSAI, etc.
NOTE: In addition, the mapping between a "virtual port" and DNN/S-NSSAI can be configured via TR-69 [18]/TR-181 [46].
Whether and how the NAUN3 devices are configured to use a specific SSID or connect to a certain Ethernet port on the 5G-RG is out of scope of this specification.
Differentiation of charging and QoS may be provided via PCC rules (for different service flows) related with dedicated PDU Sessions for NAUN3 devices. Isolation of devices using a specific Connectivity Group ID into a specific network slice, i.e. with separate S-NSSAI may also be provided.
4.10c Authenticable Non-3GPP devices behind 5G-RG
This clause defines the support of AUN3 devices, i.e. Authenticable Non-3GPP devices (AUN3) as defined in clause 3.1, behind a 5G-RG. This clause applies only to 5G-RG connected via wireline access.
Figure 4.10c-1 shows the architecture for support of AUN3 device.
Figure 4.10c-1: AUN3 device behind 5G-RG
Differentiated services for AUN3 devices behind 5G-RG are provided as specified below:
- Each AUN3 device has its own UDM/UDR subscription data including its own SUPI and policy control subscription data.
- The interface between 5G-RG and AUN3 devices is out of scope of 3GPP.
- In order to serve the AUN3 device in 5GC, a 5G-RG issues a NAS register and handles RM and CM related signalling on behalf of an AUN3 device that it is requesting to be served and relays EAP signalling between the AUN3 device and the 5GC.
- A 5G-RG serving an AUN3 device establishes a single PDU Session on behalf on this AUN3 device.
- The AMF and the 5G-RG maintain a separate NAS connection per AUN3 device. This includes maintaining a GUTI and NAS (RM, CM, etc.) context per AUN3 device. As described in TS 33.501 [11], NAS security (encryption, integrity protection) is not used for AUN3 device.
- A 5G-RG shall be connected to the 5GC (be in RM-REGISTERED and CM-CONNECTED mode) over Wireline access to serve an AUN3 device: the 5G-RG shall not issue a NAS register or service request on behalf of an AUN3 device if it is itself not registered and connected to the 5GC.
- The operator configures the access restrictions in the subscription data of all AUN3-capable subscriptions to not allow them to connect to 5GS via 3GPP access.
- The 5G-RG is configured with URSP for each AUN3 devices it serves. The UE PCF selected by the AMF at the registration of an AUN3 device sends this URSP to 5G-RG via the AMF and the NAS connection of the AUN3 device.
- The AUN3 devices and the 5G-RG belong to the same PLMN.
- A 5G-RG uses default values, which are the same for all AUN3 devices it serves, to populate the parameters in the Registration Request message built on behalf of an AUN3 device. For example, the 5G-RG issues the Registration Request with no S-NSSAI and the AMF selects the default S-NSSAI in the subscription of the AUN3 device.
- There shall be a separate N2 connection per AUN3 device that is in state CM-CONNECTED.
- The W-AGF shall determine that a W-CP connection is for an AUN3 device and apply corresponding policies. The W-AGF indicates to the AMF when an N2 connection relates to an AUN3 device.
NOTE 1: How the W-AGF determines the W-CP connection is for an AUN3 device is defined by BBF and CableLabs.
- The same W-AGF shall serve a 5G-RG and all AUN3 devices connected via this 5G-RG.
- The W-CP and W-UP protocols shall be able to manage multiple connections for different subscribers (the 5G-RG itself and the different AUN3 devices) between the same pair of 5G-RG and W-AGF. In particular, W-CP needs to be able to differentiate NAS messages related to a 5G-RG and to each different AUN3 device served by this 5G-RG and W-UP needs to distinguish between user plane packets for a 5G-RG and user plane packets for each different AUN3 device served by this 5G-RG.
- When the registration of an AUN3 device has successfully completed, the 5G-RG establishes a PDU Session on behalf of the AUN3 device. This PDU Session is handled by 5GC as part of the AUN3 subscription and is associated with the SUPI of AUN3 device. An AUN3 device can at a given time only use a single PDU Session. The parameters to establish this PDU session are based on the URSP (if any) for the AUN3 device.
- Different QoS parameters may apply to PDU sessions of different AUN3 devices.
- Roaming is not applicable to subscriptions for AUN3 devices.
- The RG Level Wireline Access Characteristics sent to the W-AGF for a 5G-RG may contain a maximum bit rate for the aggregated traffic of the 5G-RG and of the AUN3 devices served by this 5G-RG. The W-AGF uses this information to limit the maximum bit rate of the aggregated user plane traffic of the 5G-RG and of the AUN3 devices served by this 5G-RG.
NOTE 2: The coding of the maximum bit rate in RG Level Wireline Access Characteristics is defined by BBF and CableLabs specifications.
- If a W-AGF detects that a 5G-RG is unreachable, then the W-AGF triggers the N2 UE context release. The W-AGF identifies if there exists any AUN3 device connected to the 5G-RG through the W-AGF. For each identified AUN3 device, the W-AGF invokes step 5 and 6 of Figure 7.2.8.3-1 which releases the PDU sessions of these AUN3 devices.
- The Registration Management of AUN3 devices follows clause 5.5.1 of TS 23.501 [2] for Registration Management related with non-3GPP access networks.
4.10d Support of NSWO for 3GPP UE behind a RG
NSWO as defined in clauses 4.2.15 and 5.42 of TS 23.501 [2] may be supported for UE(s) connected via a 5G-RG, and/or for UE(s) connected via a FN-RG.
When this feature is supported, the RG and the W-5GAN need to support the WLAN Access functionality defined in clauses 4.2.15 and 5.42 of TS 23.501 [2]. The WLAN Access functionality includes the support of the SWa' interface to NSWOF. The SWa' support in Wireline access network has no impact on 3GPP specifications.
NOTE: W-5GAN specifications and deployments can ensure that a AAA proxy is used to support SWa' interface with NSWOF(s) on behalf of RG(s). This can be used for FN-RG that do not support SWa'. This AAA proxy does not need to support the functionalities of a 3GPP AAA proxy defined in TS 23.402 [45].
When NSWO applies, the user plane traffic of the UE is not traversing the UE's 5GC.
The specification of functionalities to support NSWO in the wireline access network is out of 3GPP scope including specifications on how the offloaded traffic is carried in W-5GAN and bypass the 5GC of the UE.
The UE can also connect to 5GC using 5GS credentials as defined in clause 5.42 of TS 23.501 [2].
A 5G RG shall not issue authentication request over SWa' for the UE if it is itself not registered to 5GC.
4.10e Differentiated QoS for non-3GPP devices behind 5G-RG
This clause defines the support for identifying the traffic of individual non-3GPP devices behind a 5G-RG and providing them differentiated QoS.
Clause 5.52 of TS 23.501 [2] applies to the 5G-RG with the following deltas:
- The UE is replaced by 5G-RG.
The overall architecture is illustrated in Figure 4.10e-1. Non-3GPP devices associated with the same PDU Session can be further differentiated using their Non-3GPP Device Identifiers. This is further described in Annex C.
Figure 4.10e-1: Example scenario for mapping traffic of individual non-3GPP devices behind 5G-RG to a PDU Session
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.11 Fixed Wireless Access
|
For the 5G-RG connected to 5GC via NG-RAN the specifications defined TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] applies with the following modification:
- The UE corresponds to the 5G-RG.
- The 5G-RG may support LTE access connected to EPC and EPC interworking as defined in TS 23.501 [2], clause 5.17. This is controlled by SMF Selection Subscription data defined in Table 5.2.3.3.1-1 of TS 23.502 [3].
- The configuration of 5G-RG via ACS server based on TR-069 [18] and TR-369 [19] is specified clause 9.6.
- The Home Routing roaming is supported for 5G-RG connected via NG RAN in this release.
- 5G Multi-Operator Core Network (5G MOCN) is supported for 5G-RG connected via NG RAN as defined in clause 5.18 of TS 23.501 [2]
- The LBO roaming for 5G-RG connected via NG RAN is not specified in this release.
- The LADN service defined in clause 5.6.5 in TS 23.501 [2] applies to the 5G-RG connected to 5GC via 3GPP access. The specification in clause 5.6.5 in TS 23.501 [2] applies via 5G-RG replacing UE with the following difference:
- UE Configuration Update procedure is referred to the procedures in clause 7.2.3.1.
NOTE 1: HR roaming over 3GPP access is defined for 5G_RG but in some countries it can not apply due to local regulations.
- If the 5G-RG is registered via both 3GPP access and W-5GAN, and the AMF has received W-AGF identities from the AGF, the AMF may provide the W-AGF identities to the SMF also when AMF forwards N1 SM container sent by the 5G-RG via 3GPP access.
NOTE 2: If the SMF receives the W-AGF information also in case of 5G-RG sending a PDU Session Establishment via 3GPP access, based on operator configuration, the SMF can take this into account for selecting a UPF collocated with the W-AGF.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.12 Hybrid Access
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.12.1 General
|
This clause specifies the support of Hybrid Access considering both the support of PDU session and MA PDU session.
Hybrid Access applies to a 5G-RG capable of connecting to both NG-RAN and to W-5GAN. Hybrid Access also applies to a 5G-RG capable of connecting to W-5GAN/5GC and E-UTRAN/EPC using EPC interworking architecture. Hybrid Access does not apply to FN-RG.
The following Hybrid Access scenarios are supported with single-access PDU sessions:
- Hybrid Access using PDU session carried only on a single access, either NG-RAN or W-5GAN, but that cannot be simultaneously on both accesses. Such PDU Session can be handed over between NG-RAN and W-5GAN using procedures described in clause 4.9.2 of TS 23.502 [3], but with UE replaced by 5G-RG and N3IWF replaced by W-5GAN.
- Hybrid Access using single access connectivity for 5G-RG supporting LTE/EPC and EPC interworking. In that case mobility between W-5GAN/5GS and E-UTRAN/EPC is handled using interworking procedures described in clause 4.11.3 of TS 23.502 [3], but with UE replaced by 5G-RG and N3IWF replaced by W-5GAN.
The following Hybrid Access scenarios are supported with multi-access connectivity:
-- Hybrid Access with Multi-Access PDU Session connectivity over NG-RAN and W-5GAN and operator-controlled traffic steering. This scenario is further detailed in clause 4.12.2.
- Hybrid Access with simultaneous multi-access connectivity to LTE/EPC and W-5GAN/5GS using EPC interworking. This scenario is further detailed in clause 4.12.3.
In this Release of the specification, a RG that supports MA PDU Sessions and LTE/EPC access as described in clause 4.12.2, shall also support MA PDU using LTE/EPC as 3GPP access as defined in clause 4.12.3.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.12.2 Hybrid Access with Multi-Access PDU Session connectivity over NG-RAN and W-5GAN
|
This clause applies to the case where multi-access PDU Session connectivity via NG-RAN and W-5GAN is supported in the 5G-RG and network. The Hybrid Access architecture of 5G-RG is defined in TS 23.501 [2] in Figure 4.2.8.4-1. This scenario uses the ATSSS solution described in clause 5.33 of the Release 16 version of TS 23.501 [2], with the following difference:
- UE is replaced by 5G-RG.
- Non-3GPP access(es) is specifically referred to wireline access.
The Release 17, ATSSS functionalities defined in TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] are not supported, except for the feature described in clause 4.12.3.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.12.3 Hybrid Access with multi-access connectivity over E-UTRAN/EPC and W-5GAN
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.12.3.1 General
|
This clause applies to the case where multi-access connectivity via both EPC and 5GC is supported in the 5G-RG and network. In this case, multi-access connectivity using ATSSS via both EPC and 5GC may be provided as described in this clause.
For a 5G-RG, a Multi-Access PDU Session may use user-plane resources of an associated PDN Connection on 3GPP access in EPC. This enables a scenario where a MA PDU Session can simultaneously be associated with user-plane resources on 3GPP access network connected to EPC and W-5GAN connected to 5GC. Such a PDN Connection in EPS would thus be associated with multi-access capability in 5G-RG and PGW-C+SMF.
The feature is supported as defined in clause 5.32 of TS 23.501 [2] (Release 17) and TS 23.502 [3] (Release 17) with following differences:
- UE is replaced by 5G-RG.
- 5G-RG is connected to 5GC via a non-3GPP access corresponding to W-5GAN.
- MA PDU Sessions of Ethernet PDU Session type where the 3GPP access corresponds to E-UTRAN/EPC are not applicable for 5G-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.12.3.2 Void
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.12.3.3 Void
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.13 Support of FN-RG
|
FN-RG is a legacy type of residential gateway that does not support N1 signalling and is not 5GC capable. The architecture to support FN-RG is depicted in clause 4.2.8.4 in TS 23.501 [2]. Support for FN-RG connectivity to 5GC is provided by means of W-AGF supporting 5G functionality on behalf of the FN-RG, e.g. UE NAS registration and session management functionality. In particular, the W-AGF supports the following functionality on behalf of the FN-RG:
- Has access to configuration information, as defined in BBF TR-456 [9], WT-457 [10] and CableLabs WR-TR-5WWC-ARCH [27], to be able to serve FN-RGs and to construct AS and NAS messages.
- Acting as end-point of N1 towards AMF, including maintaining CM and RM states and related dynamic information received from 5GC. This also includes support of URSP.
- Mapping between Y5 towards FN-RG and N1/N2 towards 5GC as well as mapping between a Y5 user plane connection and a PDU Session user plane tunnel on N3.
Authentication of FN-RG may be done by the W-AGF, as defined by BBF and Cablelabs. The W-AGF provides an indication on N2 that the FN-RG has been authenticated. The W-AGF also provides a SUCI or a 5G-GUTI as described in TS 23.501 [2].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.