hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.4.1 General | If the 5GS supports Emergency Services, the support is indicated to UE via the Registration Accept message on per-TA-list and per-RAT basis, as described in TS 23.501 [2].
If the 5GS supports Emergency Services Fallback, the support is indicated to UE via the Registration Accept message on per-TA-list and per-RAT basis... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.4.2 Emergency Services Fallback | The call flow in Figure 4.13.4.2-1 describes the procedure for emergency services fallback.
Figure 4.13.4.2-1: Emergency Services Fallback
1. UE camps on E-UTRA or NR cell in the 5GS (in either CM-IDLE or CM-CONNECTED state).
2. UE has a pending IMS emergency session request (e.g. voice) from the upper layers.
3. If th... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.5 Location Services procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.5.0 General | Location Service procedures are defined in TS 23.273 [51]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.5.1 5GC-NI-LR Procedure | Location Service procedures are defined in TS 23.273 [51]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.5.2 5GC-MT-LR Procedure without UDM Query | Location Service procedures are defined in TS 23.273 [51]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.5.3 5GC-MT-LR Procedure | Location Service procedures are defined in TS 23.273 [51]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.5.4 UE Assisted and UE Based Positioning Procedure | Location Service procedures are defined in TS 23.273 [51]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.5.5 Network Assisted Positioning Procedure | Location Service procedures are defined in TS 23.273 [51]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.5.6 Obtaining Non-UE Associated Network Assistance Data | Location Service procedures are defined in TS 23.273 [51]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.5.7 Location continuity for Handover of an Emergency session from NG-RAN | Location Service procedures are defined in TS 23.273 [51]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.6 Support of IMS Voice | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.6.1 EPS fallback for IMS voice | Figure 4.13.6.1-1 describes the EPS fallback procedure for IMS voice.
When the UE is served by the 5G System, the UE has one or more ongoing PDU Sessions each including one or more QoS Flows. The serving PLMN AMF has sent an indication towards the UE during the Registration procedure that IMS voice over PS session is s... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.6.2 Inter RAT Fallback in 5GC for IMS voice | Figure 4.13.6.2-1 describes the RAT fallback procedure in 5GC for IMS voice.
When the UE is served by the 5GC, the UE has one or more ongoing PDU Sessions each including one or more QoS Flows. The serving PLMN AMF has sent an indication towards the UE during the Registration procedure that IMS voice over PS session is ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.6.3 Transfer of PDU session used for IMS voice from non-3GPP access to 5GS | Figure 4.13.6.3-1: Transfer of PDU session used for IMS voice from non-3GPP access to 5GS
When the UE has an ongoing IMS voice session via non-3GPP access using ePDG or N3IWF and the session is transferred to NG-RAN, depending on the selected RAT in 5GS (NR or E-UTRA) and the support of EPS/inter-RAT fallback in NG-RAN... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.7 MSISDN-less MO SMS | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.7.1 General | The Nnef_MSISDN-less_MO_SMS service is used by the NEF to send the MSISDN-less MO SMS to the AF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.7.2 The procedure of MSISDN-less MO SMS Service | Figure 4.13.7.2-1: MSISDN-less MO SMS procedure via Nnef
1. The UE uses SMS over NAS procedures in clause 4.13.3 to send an SMS to the AF.
The service centre address points to the SMS-SC which contains the function described in this procedure, the destination SME address is set to short/long code of the AF and the Appl... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.8 Support of 5G LAN-type service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.8.1 Support of 5G VN group management | The information of 5G VN group is provided by the AF to the NEF and is stored in the UDR, by using the NEF service operations information flow procedure described in clause 4.15.6.2. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.8.2 Support of 5G VN group communication | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.8.2.1 General | This clause specifies the procedures for 5G VN group communication. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.8.2.2 group-level N4 session management procedures | The SMF shall create an group-level N4 session on the UPF for a 5G VN group when N19-based forwarding is applied. The group-level N4 Session management procedures enable the SMF to create, update or delete the group-level N4 Session, e.g. add or delete N4 rules, allocate or release the N19 tunnel resources.
In the case... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.14 Support for Dual Connectivity | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.14.1 RAN Initiated QoS Flow Mobility | This procedure is used to transfer QoS Flows to and from Secondary RAN Node. During this procedure, the SMF and UPF are never re-allocated. The UPF referred in this clause 4.14.1 is the UPF which terminates N3 interface in the 5GC. The presence of IP connectivity between the UPF and the Master RAN node, as well as betw... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15 Network Exposure | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.1 General | The network capability exposure comprises
- Exposure of network events externally as well as internally towards core network NFs;
- Exposure of provisioning capability towards external functions;
- Exposure of policy and charging capabilities towards external functions;
- Exposure of core network internal capabilities ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.2 External Exposure of Network Capabilities | The Network Exposure Function (NEF) supports external exposure of capabilities of network functions. External exposure can be categorized as Monitoring capability, Provisioning capability, Policy/Charging capability, network status reporting capability, Analytics reporting capability and Member UE selection assistance ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3 Event Exposure using NEF | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.1 Monitoring Events | The Monitoring Events feature is intended for monitoring of specific events in 3GPP system and making such monitoring events information reported via the NEF. It is comprised of means that allow NFs in 5GS for configuring the specific events, the event detection and the event reporting to the requested party.
To suppor... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2 Information flows | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.1 AMF service operations information flow | The procedure is used by the NF to subscribe to notifications and to explicitly cancel a previous subscription. Cancelling is done by sending Namf_EventExposure_UnSubscribe request identifying Subscription Correlation ID. The notification steps 3 and 4 are not applicable in cancellation case.
Figure 4.15.3.2.1-1: Namf_... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.2 UDM service operations information flow | The procedure is used by the NEF to subscribe to event notifications, to modify group-based subscriptions to event notifications, including removal or addition of certain UEs in a UE group and to explicitly cancel a previous subscription (see clause 4.15.1). Cancelling is done by sending Nudm_EventExposure_Unsubscribe ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.3 NEF service operations information flow | The procedure is used by the AF to subscribe to event notifications, to modify group-based subscriptions to event notification and to explicitly cancel a previous subscription (see clause 4.15.1). Cancelling is done by sending Nnef_EventExposure_Unsubscribe request identifying the subscription to cancel with Subscripti... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.4 Exposure with bulk subscription | Based on operator configuration NEF may perform bulk subscription with the NFs that provides necessary services. This feature is controlled by local policies of the NEF that control which events (set of Event ID(s)) and UE(s) are target of a bulk subscription.
When the NEF performs bulk subscription (subscribes for any... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.5 Information flow for downlink data delivery status with SMF buffering | The procedure is used if the SMF requests the UPF to forward downlink data packets that are subject of extended buffering in the SMF. The procedure describes a mechanism for the Application Function to subscribe downlink data delivery status notifications. The downlink data delivery status notifications relates to high... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.6 GMLC service operations information flow | The procedure is used by the NF to subscribe to notifications and to explicitly cancel a previous subscription. The GMLC service operations information flow is defined in clause 6.1.2 and clause 6.3 of TS 23.273 [51]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.7 Information flow for Availability after DDN Failure with SMF buffering | The procedure is used if the SMF requests the UPF to forward packets that are subject of buffering in the SMF. The procedure describes a mechanism for the Application Function to subscribe to notifications about availability after downlink data notification failure. The Availability after Downlink Data Notification fai... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.8 Information flow for downlink data delivery status with UPF buffering | The procedure is used if the SMF requests the UPF to buffer packets. The procedure describes a mechanism for the Application Function to subscribe to notifications about downlink data delivery status. The downlink data delivery status notifications relates to high latency communication, see also clauses 4.24.2 and 4.2.... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.9 Information flow for Availability after DDN Failure with UPF buffering | The procedure is used if the SMF requests the UPF to buffer packets. The procedure describes a mechanism for the Application Function to subscribe to notifications about availability after DDN failure.
Cancelling is done by sending Nnef_EventExposure_Unsubscribe request identifying the subscription to cancel with Subsc... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.10 Number of UEs and PDU Sessions per network slice notification procedure | 4.15.3.2.10.1 Reported value(s) aggregated at NEF
This procedure depicts the case of an AF subscribing to receive the registered number of UEs, or the number of PDU sessions in a specific S-NSSAI. The procedure handles the case when there is a single NSACF in the PLMN responsible for the S-NSSAI (single Service Area) o... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.11 Network-initiated explicit event notification subscription cancel procedure | The procedure is used by the UDM to delete an event notification subscription (see clause 4.15.1).
Figure 4.15.3.2.11-1: Network-initiated event subscription removal procedure
0. An event notification subscription procedure according to clause 4.15.3.2.2 or clause 4.15.3.2.2 has already executed successfully.
1-1a. If ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.12 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.2.13 Handling AF requests when the UE is identified via UE addressing information | An AF may request, via the NEF, the Event Exposure (as defined in clause 4.15.3) or the parameter provisioning (as defined in clause 4.15.6) targeting an individual UE, identifying the target UE by providing UE addressing information.
In this case the 5GC first needs to retrieve a UE Identifier based on:
- the UE addre... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.3.3 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4 Core Network Internal Event Exposure | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4.1 General | The exposure of events internally within the 5GC NFs is explained in the following clauses. Only the event notifications that are independent of the ongoing system procedure are specified in this clause. For the event notifications that are part of the system procedure, see the system procedure descriptions under claus... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4.2 Exposure of Mobility Events from AMF | The AMF invokes the Namf_EventExposure_Notify to provide mobility related events to NF consumers that have subscribed for the events by invoking Namf_EventExposure_Subscribe, in the following scenarios listed below and after Namf_EventExposure_Subscribe service operation.
- During Registration procedure, Inter NG-RAN n... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4.3 Exposure of Communication trends from SMF | During Session Management procedures, the SMF may store and update the UE access behaviour trends specified in Table 4.15.4.3-1 and the UE communication trends specified in Table 4.15.4.3-2. Each metrics is updated incrementally, e.g. using exponential moving average. This information is exposed to consumer NFs (e.g. N... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4.4 Internal Event Exposure Subscription/Unsubscription via UDM | This clause describes an indirect method of event exposure subscription in AMF and SMF via UDM for a UE or group of UEs. This can be used after the removal of UE context in the AMF including event exposure subscriptions, or the creation of new UE context in AMF or SMF. In this case, the UDM is responsible for (re)creat... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4.5 Exposure of Events from UPF for UPF Data Collection | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4.5.1 General | This clause contains the detailed description and the procedures for how the UPF event exposure service (see clause 5.2.26.2) is used for UPF data collection.
The list of NF consumer which may receive UPF event notifications is defined in clause 5.8.2.17 of TS 23.501 [2].
To get exposure data from UPF, NF consumer may ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4.5.2 Information flow for subscription to UPF event exposure service for certain UE(s) via SMF | Figure 4.15.4.5.2-1: Subscription to UPF event exposure service for certain UE(s) via SMF
In the case of a group of UEs, the UPF event consumer (e.g. NWDAF) first issues an Nnrf_NFDiscovery_Request service operation to find the UDM providing the target Group ID and gets the NF profile of the UDM serves this group. Then... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4.5.3 Information flow for UPF event exposure service for any UE | Figure 4.15.4.5.3-1: UPF Information Exposure to the UPF event consumer (e.g. NWDAF) of any UE scenario
1. (For the case when the UPF event consumer is NWDAF) The analytics consumer sends a request to the NWDAF for analytics on any UE. The analytics consumer provides the value "any UE" in the Target of Analytics Report... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4.5.4 Information flow for subscription via SMF to UPF event exposure service related with AOI | Figure 4.15.4.5.4-1: Subscription to UPF event exposure service for AOI via SMF
If the subscription is related to AOI, the UPF event consumer (e.g. NWDAF) firstly get the UE list which includes the UE(s) located in the AOI from the AMF(s), then subscribe to UPF via SMF as described in clause 4.15.4.5.2. If the UPF even... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4.5.5 Information flow for direct subscription to UPF event exposure service for certain UE using UE's IP address | Figure 4.15.4.5.5-1: Subscription to UPF event exposure service for certain UE(s) directly using UE's IP address
In the case, UPF event consumer (e.g. AF (when in trusted domain) or NEF) is aware of the UE IP address and the UPF Event ID(s) that are to be subscribed meets the criteria for direct subscription to UPF as ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4.5.6 Information flow for subscription to UPF event exposure service via SMF during UPF relocation and PDU Session release | Figure 4.15.4.5.6-1: Subscription to UPF event exposure service via SMF during UPF relocation and PDU Session release
This information flow is used in the scenario of UPF relocation, e.g. the source UPF is I-UPF or L-PSA which is relocated in SSC mode 1, or the source UPF is PSA UPF which is relocated in SSC mode 3. Th... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.4.5.7 Information flow for subscription directly to UPF event exposure service during N4 session release | Figure 4.15.4.5.7-1: Subscription directly to UPF event exposure service during N4 session release
When the UPF event consumer targets a specific UE, the procedure is as follows:
1. If the subscribed UPF events allows to directly subscribe to UPF (as defined in clause 5.8.2.17 of TS 23.501 [2]), steps 1-2 as described ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.5 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6 External Parameter Provisioning | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.1 General | Provisioning capability allows an external party to provision the information, such as expected UE behaviour and service specific parameters or the 5G VN group information to 5G network functions. In the case of provisioning the expected UE behavioural information, the expected UE behavioural information consists of in... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.2 NEF service operations information flow | Figure 4.15.6.2-1: Nnef_ParameterProvision_Create / Nnef_ParameterProvision_Update / Nnef_ParameterProvision_Delete request/response operations
0. NF subscribes to UDM notifications of UE and/or Group Subscription data updates. In the UDM subscription, the NF may request to be notified about expected UE behaviour param... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.3 Expected UE Behaviour parameters | These Expected UE Behaviour parameters characterise the foreseen behaviour of a UE or a group of UEs. Sets of these parameters may be provided via the NEF to be stored as part of the subscriber data. Each parameter within the Expected UE Behaviour shall have an associated validity time. The validity time indicates when... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.4 Set a chargeable party at AF session setup | Figure 4.15.6.4-1: Set the chargeable party at AF session set-up
1. When setting up the connection between an ASP sponsoring a session and the UE, the ASP may communicate with the AF to request to become the chargeable party for the session to be set up by sending a Nnef_ChargeableParty_Create request message (AF Ident... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.5 Change the chargeable party during the session | Figure 4.15.6.5-1: Change the chargeable party during the session
1. For the ongoing AF session, the AF may send a Nnef_ChargeableParty_Update request message (AF Identifier, Transaction Reference ID, Sponsoring Status, Background Data Transfer Reference ID) to the NEF. The Sponsoring Status indicates whether sponsorin... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.6 Setting up an AF session with required QoS procedure | Figure 4.15.6.6-1: Setting up an AF session with required QoS procedure
1. The AF sends a request to reserve resources for an AF session using Nnef_AFsessionWithQoS_Create request message (UE address, AF Identifier, Flow description information or External Application Identifier, QoS Reference or individual QoS paramet... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.7 Service specific parameter provisioning | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.7.1 General | This clause describes the procedures for enabling the AF to provide service specific parameters to 5G system via NEF.
The AF may issue requests on behalf of applications not owned by the PLMN serving the UE.
NOTE 1: In the case of architecture without CAPIF support, the AF is locally configured with the API termination... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.7.2 Service specific parameter provisioning by AF to HPLMN | Figure 4.15.6.7.2-1 shows procedure for service specific parameter provisioning. The AF uses Nnef_ServiceParameter service to provide the service specific parameters to the HPLMN and the UE. In the roaming case, PCF is replaced by H-PCF, the AMF interacts with the V-PCF which interacts with H-PCF.
Figure 4.15.6.7.2-1: ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.7.3 Service specific parameter provisioning by AF to VPLMN | Figure 4.15.6.7.3-1 shows procedure for service specific parameter provisioning by the AF to VPLMN.
Figure 4.15.6.7.3-1: Service specific information provisioning by AF to VPLMN
0a. Same as in step 0a of Figure 4.15.6.7.2-1.
0b-0c. The V-PCF may request to V-UDR on changes in UE policy information and H-PCF may subscri... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.8 Set a policy for a future AF session | Figure 4.15.6.8-1: Set a policy for a future AF session
1. The AF previously negotiated policy for background data transfer using the Procedure for future background data transfer as described in clause 4.16.7.2.
2. The AF requests that the previously negotiated policy for background data transfer be applied to a group... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.9 Procedures for AF-triggered dynamically changing access and mobility management policies | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.9.1 General | Access and mobility management policies may be modified due to several inputs including the AF as described in clause 4.16.2. Clause 4.15.6.9 describes the procedures for triggering such modifications in scenarios belonging to "case B" of clause 4.16.2.0 that are initiated by the AF.
The following cases can be distingu... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.9.2 Processing AF requests to influence access and mobility management policies targeting an individual UE | This procedure is used for individual UEs when the request shall be applied independently of conditions related to the application traffic. Depending on the AF deployment (see clause 6.2.10 of TS 23.501 [2]), the AF may interact with NFs of the Core Network either directly or via the NEF. The procedure for the direct c... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.9.3 Processing AF requests to influence access and mobility management policies | With this procedure, the AF can provide its request to influence access and mobility management policies (for one or multiple UEs) at any time.
Figure 4.15.6.9.3-1: Handling an AF request to influence access and mobility management policies Policy
This procedure concerns non-roaming scenarios, i.e. to cases where the i... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.10 Application guidance for URSP determination | This clause describes the procedures to allow an AF to provide guidance for URSP determination to 5G system via NEF. The AF may belong to the operator or to an external party. The PCF may be in the Home PLMN, as it is the PCF that determines the URSP for the UE, or in the VPLMN and then the Application guidance for URS... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.11 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.12 Parameter Provisioning when the UE is identified via UE addressing information | Handling of Parameter Provisioning requests targeting an individual UE when the UE is identified via UE addressing information is described in clause 4.15.3.2.13. Once this has taken place, the Parameter Provisioning as described in other (sub)clauses of clause 4.15.6 may apply. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.13 Multi-member AF session with required QoS | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.13.1 General Descriptions | This clause describes the procedure to request QoS and to perform QoS monitoring for the traffic flows for the communication between an AF and a set of UEs, identified by the list of UE address(es). For every UE in the set, this list contains the IP address and the port number that are used by the UE for the communicat... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.13.2 Procedures for Creating a Multi-member AF session with required QoS | Figure 4.15.6.13.2-1: Procedures for creating a Multi-member AF session with required QoS
1. The AF sends a request to reserve resources for the traffic flows for the communication between a set of UEs and an AF, using Nnef_AFsessionWithQoS_Create request message (a list of UE addresses, AF Identifier, Flow description... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.13.3 Procedure for updating a Multi-member AF session with required QoS | Figure 4.15.6.13.3-1: Procedure for updating a Multi-member AF session with required QoS
1. The AF which controls the Multi-member AF Session with required QoS invokes the Nnef_AFSessionWithQoS_Update Request to update the list of UE addresses and/or to update the QoS and/or to update the QoS monitoring and/or to updat... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.13.4 Procedure for Revoking a Multi-member AF session with required QoS | Figure 4.15.6.13.4-1: Procedure for revoking a Multi-member AF session with required QoS
1. The AF sends a request to revoke the allocated resources for the traffic flows for the communication between a set of UEs and an AF, using Nnef_AFsessionWithQoS_Revoke request message (Transaction Reference ID).
2. The NEF autho... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.14 Procedures for AF requested QoS for a UE or group of UEs not identified by a UE address | Figure 4.15.6.14-1: Procedure for AF requested QoS for a UE or group of UEs not identified by a UE address
0. When a new PDU Session is established, based on local configuration associated with the DNN/S-NSSAI, the PCF determines if the PDU Session needs involvement of TSCTSF. If the TSCTSF is used the PCF invokes Npcf... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.6.15 Provisioning of Non-3GPP Device Identifier Information | This clause describes the procedures to allow an AF to provision QoS information for the non-3GPP device(s) (as defined in clause 5.52 of TS 23.501 [2]) that require differentiated QoS treatment for a UE subscription to the 5G system via NEF. The AF may belong to the operator or to an external party.
To provision QoS i... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.7 Network status reporting | This clause contains the detailed description and the procedures for the network status reporting capability.
An AF may request for being notified about the network status, in a specific geographical area or for a specific UE.
The following methods are supported:
- The AF requests to be informed, one-time, about the ne... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.8 Event exposure controlled by a DCCF | A DCCF can coordinate the subscriptions and notifications to event exposure in Network Functions. This is further described in TS 23.288 [50]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.9 Time Synchronization exposure | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.9.1 General | Time synchronization exposure allows an AF to configure time synchronization in 5GS. For (g)PTP operation, the Time synchronization service allows an AF to subscribe to the UE and 5GC capabilities and availability for time synchronization service (as described in clause 4.15.9.2), to configure the (g)PTP instance in 5G... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.9.2 Exposure of UE availability for Time Synchronization service | The procedure is used by the AF to subscribe to notifications and to explicitly cancel a previous subscription for UE availability for time synchronization service. Cancelling is done by sending Nnef_TimeSynchronization_CapsUnsubscribe request identifying the subscription to cancel with Subscription Correlation ID.
Fig... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.9.3 Time Synchronization activation, modification and deactivation | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.9.3.1 General | This procedure can be used by the AF to activate, modify or deactivate the (g)PTP instances in 5GS.
The AF may activate the time synchronization service using the Nnef_TimeSynchronization_ConfigCreate service operation. The service operation creates a time synchronization configuration based on the service parameters a... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.9.3.2 Time synchronization service activation | Figure 4.15.9.3.2-1: Time synchronization service activation
1. The AF creates a time synchronization service configuration for a PTP instance by invoking Nnef_TimeSynchronization_ConfigCreate service operation. The request includes the parameters as described in Table 4.15.9.3-1. The request contains a Subscription Co... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.9.3.3 Time synchronization service modification | Figure 4.15.9.3.3-1: Time synchronization service modification
1. To update an existing time synchronization service configuration of the PTP instance, the AF invokes a Nnef_TimeSynchronization_ConfigUpdate service operation providing the corresponding PTP instance reference.
2. The NEF invokes the Ntsctsf_TimeSynchron... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.9.3.4 Time synchronization service deactivation | Figure 4.15.9.3.4-1: Time synchronization service deactivation
1. To remove an existing time synchronization service configuration of the PTP instance, the AF invokes a Nnef_TimeSynchronization_ConfigDelete service operation providing the corresponding PTP instance reference.
2. The NEF invokes the Ntsctsf_TimeSynchron... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.9.4 Procedures for management of 5G access stratum time distribution | The AF can use the procedure to activate, update or delete the 5G access stratum time distribution for one UE or a group of UEs.
The AF may query the status of the 5G access stratum time distribution using Nnef_ASTI_Get service operation. The Nnef_ASTI_Create and Nnef_ASTI_Update request may contain the parameters as d... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.9.5 Procedures for subscription and management of network timing synchronization status monitoring | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.9.5.1 Network timing synchronization status | Figure 4.15.9.5.1-1: Procedure for TSCTSF subscription to RAN and/or UPF/NW-TT timing synchronization status
0. The AF requests creation or modification of ASTI or PTP based time synchronization service as described in clauses 4.15.9.4 and 4.15.9.3 including clock quality detail level and clock quality acceptance crite... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.9.5.2 5G access stratum time distribution status reporting to the UE | Figure 4.15.9.5.2-1: Procedure for reporting RAN timing synchronization status to subscribed UE
1. Creation or update of ASTI or PTP based time synchronization service (AF requested ASTI or PTP based time synchronization service is described in clauses 4.15.9.4 and 4.15.9.3; subscription based ASTI is described in clau... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.15.10 AF specific UE ID retrieval | This clause contains the detailed description and the procedures for the AF specific UE ID retrieval. The AF specific UE Identifier is represented by the External Identifier as defined in TS 23.003 [33].
NOTE 1: After retrieving AF specific UE ID, the AF can invoke NEF provided services (e.g. location monitoring).
NOTE... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.