hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.6.3 Service Request procedure
| The Service Request procedures for UE in CM-IDLE state are performed as defined in TS 23.502 [5] clause 4.2.3.2 and clause 4.2.3.3 with the following additions:
- If the UE is authorised to use ProSe services, then the AMF shall include "ProSe authorised" information in the NGAP message, indicating which of the ProSe ... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.6.4 N2 Handover procedure
| The N2 based handover procedures for UE are performed as defined in TS 23.502 [5] clause 4.9.1.3 with the following additions:
- If the UE is authorised to use ProSe services, then the target AMF shall send the "ProSe authorised" information, ProSe NR UE-PC5-AMBR and PC5 QoS parameters for ProSe to the target NG-RAN i... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.6.5 Xn Handover procedure
| The Xn based handover procedures for UE are performed as defined in TS 23.502 [5] clause 4.9.1.2 with the following additions:
- If the "ProSe authorised" information is included in the UE context, then the source NG-RAN shall include a "ProSe authorised" information, ProSe NR UE-PC5-AMBR and PC5 QoS parameters for Pr... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.6.6 Subscriber Data Update Notification to AMF
| The procedure of Subscriber Data Update Notification to AMF is performed as defined in TS 23.502 [5] clause 4.5.1 with the following additions:
- The Nudm_SDM_Notification service operation may contain the ProSe Service Authorisation or the ProSe NR UE-PC5-AMBR or any combination.
- The AMF updates the UE Context wit... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.6.7 Delivery of PC5 QoS parameters for ProSe to NG-RAN
| The UE Policy Association Establishment procedure and UE Policy Association Modification procedure, as defined in TS 23.502 [5], is used to provide the AMF with PC5 QoS parameters used by NG-RAN. When receiving the 5G ProSe Capability in Npcf_UEPolicyControl_Create Request from the AMF or when receiving the updated sub... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7 5G ProSe UE-to-UE Relay Communication
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.1 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.1.1 Layer-2 link establishment for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay
| Figure 6.7.1.1-1 shows the procedure for Layer-2 link establishment via 5G ProSe Layer-3 UE-to-UE Relay.
Figure 6.7.1.1-1: Layer-2 link establishment via 5G ProSe Layer-3 UE-to-UE Relay
1. Service authorization and provisioning are performed for source 5G ProSe Layer-3 End UE, target 5G ProSe Layer-3 End UE and 5G ... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.1.2 Link identifier update for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay
| The Link Identifier Update procedure as defined in clause 6.4.3.2 is reused between source 5G ProSe Layer-3 End UE and 5G ProSe Layer -3 UE-to-UE Relay to perform a link identifier update. When the IP address/prefix is changed, the new one is shared between source 5G ProSe Layer-3 End UE and target 5G ProSe Layer-3 End... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.1.3 Layer-2 link release for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay
| Figure 6.7.1.3-1 shows the Layer-2 link release procedure via 5G ProSe Layer-3 UE-to-UE Relay.
Figure 6.7.1.3-1: Layer-2 Link Release procedure via 5G ProSe Layer-3 UE-to-UE Relay
0. The source 5G ProSe Layer-3 End UE and the 5G ProSe Layer-3 UE-to-UE Relay and the 5G ProSe Layer-3 UE-to-UE Relay and the target 5G ... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.1.4 Layer-2 link modification for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay
| Figure 6.7.1.4-1 shows the Layer-2 link modification procedure via Layer-3 UE-to-UE Relay. This procedure is used to add/modify/remove PC5 QoS Flow(s) in the existing PC5 unicast link as described in clause 6.4.3.7.3.
Figure 6.7.1.4-1: Layer-2 link modification procedure via Layer-3 UE-to-UE Relay
0. UE-1 and UE-to... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.1.5 Layer-2 link maintenance for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay
| The Layer-2 link maintenance over the PC5 reference point procedure as described in clause 6.4.3.5 can be used for the Layer-2 link established between the source 5G ProSe Layer-3 End UE and the 5G ProSe Layer-3 UE-to-UE Relay and between the 5G ProSe Layer-3 UE-to-UE Relay and the target 5G ProSe Layer-3 End UE.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.2 5G ProSe Communication via 5G ProSe Layer-2 UE-to-UE Relay
| This procedure applies to 5G ProSe Layer-2 UE-to-UE Relay.
Figure 6.7.2-1: 5G ProSe Communication via 5G ProSe Layer-2 UE-to-UE Relay
Service authorization and provisioning has been performed for the 5G ProSe Layer-2 UE-to-UE Relay and the 5G ProSe End UEs as described in clause 6.2 before this procedure.
1. Model... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.3 5G ProSe UE-to-UE Relay Communication with integrated Discovery
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.3.1 General
| 5G ProSe Communication via 5G ProSe UE-to-UE Relay with integrated Discovery is supported.
For 5G ProSe UE-to-UE Relay Communication with integrated Discovery, when a UE allows a UE-to-UE relay to be involved in the Direct Communication Request to the other UE, the UE indicates it by including a relay_indication in th... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.3.2 Procedure for Communication via Layer-3 UE-to-UE Relay
|
Figure 6.7.3.2-1: 5G ProSe UE-to-UE Relay Communication with integrated Discovery via Layer-3 UE-to-UE Relay
0. 5G ProSe End UEs are authorized and provisioned with parameters to use the service provided by the 5G ProSe UE-to-UE Relays. 5G ProSe UE-to-UE Relays are authorized and provisioned with parameters to provi... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.3.3 Procedure for Communication via Layer-2 UE-to-UE Relay
|
Figure 6.7.3.3-1: 5G ProSe UE-to-UE Relay Communication with integrated Discovery via Layer-2 UE-to-UE Relay
0-5. It is the same as steps 0-5 of Figure 6.7.3.2-1.
6. It is the same as step 7 of Figure 6.7.3.2-1.
7. It is the same as step 10 of Figure 6.7.3.2-1.
The parameters included in the above messages are de... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.4 5G ProSe UE-to-UE Relay reselection
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.4.1 General
| After being connected to the 5G ProSe UE-to-UE Relay, the 5G ProSe End UEs may trigger the 5G ProSe UE-to-UE Relay reselection based on conditions (e.g. the measured signal strength of PC5 unicast link with the 5G ProSe UE-to-UE Relay) as specified in TS 38.300 [12]. For 5G ProSe Multi-hop Layer-3 UE-to-UE Relay for no... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.4.2 Negotiated 5G ProSe Layer-2 UE-to-UE Relay reselection
| Depicted in Figure 6.7.4.2-1 is the procedure for the negotiated 5G ProSe Layer-2 UE-to-UE Relay reselection.
Figure 6.7.4.2-1: Negotiated 5G ProSe Layer-2 UE-to-UE Relay reselection
1. A PC5 unicast link is established between the 5G ProSe End UEs via a 5G ProSe UE-to-UE Relay, based on the procedure defined in cl... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.4.3 Negotiated 5G ProSe Layer-3 UE-to-UE Relay reselection
| Depicted in Figure 6.7.4.3-1 is the procedure for the negotiated 5G ProSe Layer-3 UE-to-UE Relay reselection.
Figure 6.7.4.3-1: Negotiated 5G ProSe Layer-3 UE-to-UE Relay reselection
1. 5G ProSe End UEs have set up PC5 unicast links with a 5G ProSe UE-to-UE Relay, based on the procedure defined in clause 6.7.1.
2.... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.4.4 Negotiated 5G ProSe Multi-hop Layer-3 UE-to-UE Relay Reselection for Non-IP type PDU
| Depicted in Figure 6.7.4.4-1 is the procedure for the negotiated 5G ProSe Multi-hop Layer-3 UE-to-UE Relay reselection.
Figure 6.7.4.4.-1. Negotiated Multi-hop Layer-3 UE-to-UE Relay reselection procedure.
1. 5G ProSe End UEs have set up PC5 unicast links with one or multiple 5G ProSe UE-to-UE Relay, based on the p... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.5 5G ProSe Communication via 5G ProSe Layer-3 Multi-hop UE-to-UE Relay
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.5.1 General
| 5G ProSe Communication via 5G ProSe Layer-3 Multi-hop UE-to-UE Relay supports IP type of traffic or non-IP type of traffic, depending on the RSCs associated with the relays.
For one RSC, only one type of traffic and corresponding procedures should be used for the communication.
|
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.5.2 Communication via 5G ProSe Layer-3 Multi-hop UE-to-UE-Relays
| |
4d761cc8095b5982244110685dcb04f8 | 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.... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.7.5.2.2 Layer-2 link establishment via 5G ProSe Layer-3 Multi-hop UE-to-UE Relays (Non-IP Type)
|
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... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.8 Procedures for communication path switching between PC5 and Uu reference points
| |
4d761cc8095b5982244110685dcb04f8 | 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 Sess... |
4d761cc8095b5982244110685dcb04f8 | 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... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 6.9 Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay
| |
4d761cc8095b5982244110685dcb04f8 | 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.
|
4d761cc8095b5982244110685dcb04f8 | 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 f... |
4d761cc8095b5982244110685dcb04f8 | 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 ... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 7 Network Function Services
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 7.1 5G DDNMF Services
| |
4d761cc8095b5982244110685dcb04f8 | 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/... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 7.1.2 N5g-ddnmf_Discovery service
| |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 7.1.2.1 General
| Service description: This service enables a 5G DDNMF to manage inter-PLMN ProSe Direct Discovery operations.
|
4d761cc8095b5982244110685dcb04f8 | 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 Iden... |
4d761cc8095b5982244110685dcb04f8 | 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... |
4d761cc8095b5982244110685dcb04f8 | 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... |
4d761cc8095b5982244110685dcb04f8 | 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 E... |
4d761cc8095b5982244110685dcb04f8 | 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:... |
4d761cc8095b5982244110685dcb04f8 | 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, Appl... |
4d761cc8095b5982244110685dcb04f8 | 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 Appli... |
4d761cc8095b5982244110685dcb04f8 | 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;
- (... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 7.2 AF Services
| |
4d761cc8095b5982244110685dcb04f8 | 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
DiscoveryAuthorizati... |
4d761cc8095b5982244110685dcb04f8 | 23.304 | 7.2.2 Naf_ProSe service
| |
4d761cc8095b5982244110685dcb04f8 | 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.
|
4d761cc8095b5982244110685dcb04f8 | 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 ... |
4d761cc8095b5982244110685dcb04f8 | 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.
O... |
4d761cc8095b5982244110685dcb04f8 | 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: Resu... |
fb6d29e6a362615ca2c901270a8a42ba | 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], T... |
fb6d29e6a362615ca2c901270a8a42ba | 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.
-... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 3 Definitions and abbreviations
| |
fb6d29e6a362615ca2c901270a8a42ba | 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 Wirelin... |
fb6d29e6a362615ca2c901270a8a42ba | 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 Gatew... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4 High level features
| This clause specifies high level description equivalent to TS 23.501 [2].
|
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.2 Network Access Control
| |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 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:... |
fb6d29e6a362615ca2c901270a8a42ba | 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 i... |
fb6d29e6a362615ca2c901270a8a42ba | 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 ... |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.2.5 Policy control
| Policy control is specified in clause 9.
|
fb6d29e6a362615ca2c901270a8a42ba | 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 diffe... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.3 Registration and Connection Management
| |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 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].
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.3.3 Mobility Restrictions
| |
fb6d29e6a362615ca2c901270a8a42ba | 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 t... |
fb6d29e6a362615ca2c901270a8a42ba | 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 ... |
fb6d29e6a362615ca2c901270a8a42ba | 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 ... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.4 Session management
| |
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 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 signal... |
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.5 QoS model
| |
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.5.1 Wireline access specific 5G QoS parameters
| |
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.5.1.1 Void
| |
fb6d29e6a362615ca2c901270a8a42ba | 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 wi... |
fb6d29e6a362615ca2c901270a8a42ba | 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 managemen... |
fb6d29e6a362615ca2c901270a8a42ba | 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 ... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.6 User Plane management
| |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.6.2 IP address allocation
| |
fb6d29e6a362615ca2c901270a8a42ba | 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] ... |
fb6d29e6a362615ca2c901270a8a42ba | 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 C... |
fb6d29e6a362615ca2c901270a8a42ba | 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 PD... |
fb6d29e6a362615ca2c901270a8a42ba | 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 PD... |
fb6d29e6a362615ca2c901270a8a42ba | 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], IGM... |
fb6d29e6a362615ca2c901270a8a42ba | 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 Multica... |
fb6d29e6a362615ca2c901270a8a42ba | 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 Repor... |
fb6d29e6a362615ca2c901270a8a42ba | 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 Spe... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.7 Identifiers
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.