hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.3.4 Restoration Procedure for Intermediate UPF Restart
| The SMF will receive the UPF recovery time stamps in PFCP heartbeat requests/responses.
After an Intermediate UPF restart, the PFCP association between the SMF(s) and the Intermediate UPF has to be re-established.
The restoration of the PFCP sessions may start immediately after the PFCP association setup procedure:
... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.3.5 Restoration Procedure for Intermediate UPF Failure without Restart
| Procedures for Intermediate UPF failure without restart are implementation specific.
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.4 SMF Restoration Procedures
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.4.1 General
| When a SMF fails, all its PDU session contexts and PFCP associations affected by the failure may become invalid and may be deleted.
When the SMF that fails is deployed as part of an SMF set, the PDU session contexts that were served by that SMF are maintained by the SMF set. The MPAS and SSET procedures specified for ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.4.2 Restoration Procedure for SMF Restart
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.4.2.1 General
| During or immediately after a SMF Restart, the SMF shall place local SMF-C Recovery Time Stamp value in all Heartbeat Request/Response messages.
The UPF will receive the SMF recovery time stamps in PFCP heartbeat requests/responses.
When a UPF detects that a peer PFCP entity in the SMF has restarted (as specified in ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.4.2.2 Restart of an SMF in a SMF Set
| During or immediately after the restart of an SMF in an SMF set, using the MPAS or SSET procedure specified for SMF set in clause 5.22 of 3GPP TS 29.244 [4], the SMF shall not modify the local SMF Recovery Time Stamp value in its Heartbeat Request/Response messages.
Accordingly, the UPF does not detect that the peer P... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.4.3 Restoration Procedure for SMF Failure without Restart
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.4.3.1 General
| When a UPF detects that a peer PFCP entity in the SMF is not reachable for a preconfigured time, and the MPAS or SSET procedure specified for SMF set in clause 5.22 of 3GPP TS 29.244 [4]) are not used, the UPF shall delete all the session contexts affected by the peer PFCP entity failure that it may have stored.
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.4.3.2 Failure of an SMF in a SMF set
| When the MPAS or SSET procedure specified for SMF set in clause 5.22 of 3GPP TS 29.244 [4]) is used, when the UPF detects that a peer PFCP entity in an SMF is not responsive for a preconfigured time, or upon being instructed by SMF(s) of the SMF set to move PFCP sessions, the UPF shall move the PFCP sessions (other tha... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.5 N4 path failure
| If the N4 path to the UPF is down, the SMF should handle this as an UPF Failure without Restart, see clause 4.3.3.
If the N4 path to the SMF is down, the UPF should handle this as a SMF Failure without Restart, see clause 4.4.3.
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.6 Partial failure handling over N4
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.6.1 General
| The SMF and UPF may support the partial failure handling feature over N4. If so, they shall support the requirements specified in this clause.
This feature enables to clean up PFCP sessions optimally in the peer PFCP node (i.e. SMF or UPF), when a hardware or software failure affects a significant number of PFCP sessi... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.6.2 Procedures
| The SMF and the UPF may each assign one FQ-CSID to a PFCP session during the PFCP session establishment, by signalling the SMF FQ-CSID in the PFCP Session Establishment Request or the UPF FQ-CSID in the PFCP Session Establishment Response, as shown in Figure 4.6.2-1.
Figure 4.6.2-1 : PFCP Session Establishment proce... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.7 Restoration of PFCP sessions associated with a specific FQ-CISD, Group ID or SMF IP Address
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.7.1 General
| To reduce signalling latency and achieve a better load balancing among SMFs in a SMF Set when it is deployed, an SMF in a SMF Set and a UPF may support the procedures specified in this clause. These procedures enable an SMF from the same set to request UPF to move PFCP sessions associated with certain FQ-CSIDs (when pa... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.7.2 Allocation of Group Id or FQ-CSID to a PFCP session
| To optimize the resource utilization for PFCP session(s), e.g. to meet different traffic requirements for different APNs/DNNs and/or DCNs/Network Slices, and also to facilitate moving a (sub)set of PDN connections/PFCP sessions among an SMF set, e.g. for a partial or complete SMF failure or a scale-in operation, an SMF... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.7.3 Restoration of PFCP sessions associated with an FQ-CSID, Group ID or SMF IP Address
| When there is a need to change the SMF controlling certain PFCP sessions, e.g. when a partial or complete failure takes place, the SMF (either the SMF serving the PFCP sessions or another SMF in the same Set taking over the control of the PFCP sessions) may send a PFCP Session Set Modification Request message to the UP... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5 Restoration Procedures related to the User Plane Interfaces N3 and N9
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.1 General
| This clause specifies the procedures supported in the 5G System to detect and handle failures affecting the user plane interfaces N3 and N9
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.2 User Plane Failure Detection
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.2.1 Loss of GTP-U contexts
| A GTP-U entity may lose its GTP-U contexts upon a failure or restart.
When a GTP-U node receives a G-PDU for which no corresponding GTP-U tunnel exists, the GTP-U node shall discard the G-PDU and return a GTP-U Error Indication to the sending node, as specified in clause 7.3.1 of 3GPP TS 29.281 [3].
The receipt of a ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.2.2 User Plane Path Failure
| A GTP-U entity may detect a user plane path failure by using GTP-U Echo Request and Echo Response messages, as specified in clause 20.3.1 of 3GPP TS 23.007 [2].
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.3 Restoration Procedures upon Loss of GTP-U contexts
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.3.1 General
| The following clauses specify the behaviour of the different network entities when receiving a GTP-U Error Indication.
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.3.2 Procedure for GTP-U Error Indication received from 5G-AN
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.3.2.1 Principles
|
Figure 5.3.2.1-1: GTP-U Error Indication from 5G-AN
1. The user plane connection of an existing PDU session is activated. Downlink G-PDUs are sent towards the 5G-AN.
2. The 5G-AN returns a GTP-U Error Indication if it does not have a corresponding GTP-U context (see clause 5.2).
3. Upon receipt of a GTP-U Error In... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.3.3 Procedure for GTP-U Error Indication received from UPF
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.3.3.1 GTP-U Error Indication received by 5G-AN
| Upon receipt of a GTP-U Error Indication, the 5G-AN shall proceed as follows:
- if the GTP-U Error Indication was received from an UPF over a NG-U tunnel that is not an indirect forwarding tunnel, the 5G-AN shall initiate a PDU Session Resource Notify procedure and release immediately the resources of the PDU session ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.3.3.2 GTP-U Error Indication received by another UPF
| Upon receipt of a GTP-U Error Indication, the UPF shall identify the related PFCP session and send an Error Indication Report to the SMF, as specified in clause 5.10 of 3GPP TS 29.244 [4].
Upon receipt of an Error Indication Report from the UPF, the SMF shall identify the PDU session for which the Error Indication is ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.4 Restoration Procedures upon User Plane Path Failure
| Upon detecting a GTP-U user plane path failure as specified in clause 5.2.2, the UPF shall report the user plane path failure to the SMF, by sending a PFCP Node Report Request (see 3GPP TS 29.244 [4]) including a User Plane Path Failure Report with the IP address of the remote GTP-U peer(s) towards which a failure has ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 5.5 Reporting of a Peer GTP-U Entity Restart
| To reduce massive amount of N4 signalling to report the receiving of GTP-U Error Indication messages and to perform subsequent PFCP Session Modification for PFCP sessions affected by the peer GTP-U restart, a user plane function (UPF) and a control plane function (SMF) may optionally support reporting of a peer GTP-U e... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6 Restoration Procedures related to Service-Based Interfaces
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.1 General
| A NF may detect a failure or a restart of a peer NF or NF service using the NRF as specified in clause 6.2.
A NF may also detect a restart of a peer NF or NF service by receiving recovery time information in signalling exchanged with that peer NF or NF service.
When NF (Service) Set is deployed in the network as spec... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.2 NF (NF Service) Failure and Restart Detection using the NRF
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.2.1 General
| This clause describes optional procedures that may be supported by NFs to detect the failure or restart of a NF or a NF service using the NRF.
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.2.2 NF (NF Service) Failure
| Figure 6.2.2-1 describes a NF failure scenario and how other NFs can be notified of this failure.
Figure 6.2.2-1: NF Failure Detection and Notification
1. NF A subscribes to the NRF to receive notifications of changes of the NF B Profile, as specified in 3GPP TS 29.510 [7].
2. A NF failure occurs at NF B.
3. The ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.2.3 NF (NF Service) Restart
| Figure 6.2.3-1 describes a NF restart scenario and how other NFs can be notified of this restart.
Figure 6.2.3-1: NF Restart Detection and Notification
1. NF B (or OAM) registers NF B Profile to the NRF. The NF B Profile may include the recoveryTime attribute, if a restart of NF B results in losing contexts.
NF ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 2 NF A subscribes to the NRF to receive notifications of changes of the NF B Profile.
| 3. A NF B service restarts.
4. If contexts are lost during the service restart, NF B (or OAM) updates the recoveryTime of the corresponding NF Service in the NRF. NF B (or OAM) shall update the recoveryTime attribute of the NF Service Set, NF Instance or NF Set to which the NF Service Instance pertains to, when the wh... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.3 NF Service Producer Restart Detection using direct signalling between NFs
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.3.1 General
| This clause describes an optional procedure that may be supported by NFs to detect the restart of a peer NF service using direct signalling between NFs.
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.3.2 NF Service Producer Restart
| Figure 6.3.2-1 describes a NF Service restart scenario of an NF Service Producer and how the NF Service Consumer can detect this restart.
Figure 6.3.2-1: NF Service Producer Restart Detection
1. NF A (NF Service Consumer) requests to create a resource in the NF B (NF Service Producer).
2. If the request is accepte... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.4 NF Service Consumer Restart Detection using direct signalling between NFs
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.4.1 General
| This clause describes an optional procedure that may be supported by NFs to detect the restart of a peer NF Service Consumer by NF Service Producer using direct signalling between NFs.
When NF (Service) Set is deployed in the network as specified in clause 5.21.3 and 6.3.1.0 of 3GPP TS 23.501[9], an NF Service Consume... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.4.2 NF Service Consumer Restart
| Figure 6.4.2-1 describes a NF Service Consumer restart scenario and how the NF Service Producer can detect this restart.
Figure 6.4.2-1: NF Service Consumer Restart Detection
1. NF A (NF Service Consumer) requests to create a resource in the NF B (NF Service Producer). If NF A implements the procedure specified in ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.5 NF Service Producer Instance Reselection
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.5.1 General
| An NF Instance of an NF Service Producer may expose several service instances of the same NF Service (e.g., an UDM instance may expose several service instances of the "Nudm_SubscriberDataManagement" service).
An NF Service Consumer may discover, while an SCP shall be able to discover, via NRF Nnrf_NFDiscovery service... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.5.2 NF Service Instance Reselection when a (Routing) Binding Indication is available
| When using the Binding procedures specified in clause 6.12 of 3GPP TS 29.500 [10], Binding Indications and Routing Binding Indications include the Binding level and one or more Binding entity IDs representing all NF service instances that are capable to serve service requests targeting the resource, i.e. that share the... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.5.3 NF Service Instance Reselection when a (Routing) Binding Indication is not available
| If a formerly selected NF Service Instance becomes unavailable, the NF Service Consumer may, while the SCP shall be able to select a different instance of a same NF Service in:
- the same NF Instance, if the NF Instance indicates in its NF Profile that it supports the capability to persist their resources in shared st... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.6 NF Service Consumer Instance Reselection
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.6.1 General
| When NF (Service) Set is deployed in the network as specified in clauses 5.21.3 and 6.3.1.0 of 3GPP TS 23.501[9], an NF Service Consumer in an NF (Service) Set may create a session context for callback (corresponding to the resource context in the NF Service Producer) when invoking a NF Service and the session context ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.6.2 NF Service Consumer Instance Reselection when a (Routing) Binding Indication is available
| When using the Binding procedures specified in clause 6.12 of 3GPP TS 29.500 [10], Binding Indications and Routing Binding Indications include the Binding level and one or more Binding entity IDs representing all NF service consumer instances that are capable to receive the notifications or callback requests targeting ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.6.3 NF Service Consumer Instance Reselection when a (Routing) Binding Indication is not available
| When the target NF Service Consumer becomes unavailable, the NF Service Producer may, while the SCP shall be able to select a different instance of the Service Consumer which is capable to receive the notifications or callback requests targeting the session context for callback (corresponding to the resource context in... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.7 Restoration of Profiles related to UDR
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.7.1 General
| This clause describes an optional procedure that may be supported by UDR, UDR consumers (i.e. UDM, PCF, and NEF), and UDM consumers (e.g. AMF, SMF, SMSF, AUSF, NEF…) to re-synchronize profiles in UDR to those in UDR consumers and UDM consumers. When UDR detects corruption, loss, or inconsistency in temporary data store... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.7.2 Procedure
| Figure 6.7.2-1 describes the procedure for restoration of profiles related to UDR.
Figure 6.7.2-1: Restoration of Profiles related to UDR
0. UDR consumers and UDM consumers define callbackUri for data restoration notification in the NF profile registered in NRF.
1. UDR consumers store temporary data in UDR. The ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.7.3 UDR Restoration during Subscriber Data Migration
| During operation of a PLMN, it is a common task to have to re-allocate subscriber's data records across subscriber servers/databases, due to multiple reasons such as, e.g., subscriber re-distribution, network re-dimensioning / scaling-out, replacement / swap of legacy databases (e.g. 4G UDC systems), etc.
The migratio... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.7.3.1 AUSF subscriber re-allocation
| If the AUSF assigned to a UE is modified (i.e. the subscriber in the AUSF is re-allocated to another AUSF), the SEAF (AMF) shall be informed that the primary authentication when required shall be performed towards the newly allocated AUSF for each corresponding UE.
The UDM sends the data restoration notification to th... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.7.4 AMF indication of AMF Data Restoration resynchronization is initiated
| If the AMF has initiated resynchronization for a UE, the AMF may provide an indication to the SMF(s) with established PDU Session(s) to allow that, if this UE was expected to be resynchronized (as a result of the reception of the Data Restoration notification to perform resynchronization directly from the UDM), the SMF... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.8 Restoration Procedures for Home Routed PDU Sessions or PDU sessions with an I-SMF
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.8.1 General
| This clause specifies requirements in the AMF, the V/I-SMF and the (H-)SMF to restore Home Routed PDU Sessions or PDU sessions with an I-SMF.
During a PDU session establishment and update procedure, the V/I-SMF or the (H-)SMF shall:
- set the "Peer NF SET based Reselection"(PSETR) feature bit in the SupportedFeatures... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.8.2 V-SMF failure
| When the H-SMF detects the failure of the V-SMF, it shall retrieve all PDU sessions associated with the failed V-SMF and perform the following procedure for those PDU sessions:
- if the H-SMF supports the PSETR feature:
- if the V-SMF supports the DLSET feature, the H-SMF shall keep the PDU session and should reselec... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 6.8.3 H-SMF failure
| When the V-SMF detects the failure of the H-SMF, it shall retrieve all PDU sessions associated with the failed H-SMF and perform the following procedure for those PDU sessions:
- if the V-SMF does not support the PSETR feature, the V-SMF may release the affected PDU sessions towards the AMF and UE, and may request the... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 7 Restoration Procedures related to Public Warning System (PWS)
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 7.1 General
| This clause specifies the procedures supported in the 5G System to handle failures affecting Public Warning System (PWS). The stage 2 architecture and procedures for PWS are specified in 3GPP TS 23.041 [8].
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 7.2 PWS operation failure in NG-RAN
| The NG-RAN shall report that on-going PWS operation for one or more cells of the NG-RAN has failed by sending a PWS Failure Indication as specified in 3GPP TS 23.041 [8].
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 7.3 PWS operation restart in NG-RAN
| After a NG-RAN (i.e. gNB or ng-eNB) has restarted, it shall delete all its warning message data. If the warning message service is operational in one or more cell(s) of the NG-RAN, the NG-RAN shall send a PWS Restart Indication message, which shall include the identity of the NG-RAN, the identity of the restarted cell(... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8 Restoration Procedures for MBS
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.1 General
| This clause specifies the procedures supported in the 5G System to detect and handle failures affecting any network entity involved in the delivery of broadcast and/or multicast service.
8.1A N4mb Failure and Restart Detection
Across PFCP based interfaces, an MB-SMF and MB-UPF shall utilize the PFCP Heartbeat Request... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.2 Restoration procedures for MB-UPF failure with or without restart
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.2.1 General
| When an MB-UPF fails, all its PFCP session contexts of the MBS sessions and all its PFCP associations affected by the failure may be lost.
The MB-SMF and MB-UPF may support the procedures specified in this clause to restore the multicast and broadcast MBS sessions affected by the failure.
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.2.2 Restoration Procedure for MB-UPF Restart
| The MB-UPF should ensure that:
- when multicast transport is used on N3mb and/or N19mb, any N3mb and/or N19mb Low Layer Source Specific Multicast (LL SSM) addresses used by the MB-UPF before the MB-UPF restart are not immediately reused after the MB-UPF restart; and
- when unicast transport is used on N6mb and/or Nmb... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.2.3 Restoration Procedure for MB-UPF failure without Restart
| Upon detecting that an MB-UPF fails without restart, the MB-SMF may restore the MBS sessions that were served by the failed MB-UPF by selecting an alternative MB-UPF and by restoring the PFCP sessions of the MBS sessions in the alternative MB-UPF, following PFCP requirements for establishing an N4mb PFCP session as spe... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.3 Restoration procedures for NG-RAN failure with or without restart
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.3.1 General
| When an NG-RAN fails with or without restart, all its MBS session contexts may be lost, causing the interruption in the delivery of MBS data over the radio interface.
Restoration procedures for NG-RAN failure with or without restart are optional to support.
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.3.2 Broadcast MBS session restoration Procedure for NG-RAN failure with restart
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.3.2.1 General
| MBS sessions affected by an NG-RAN failure with restart may be restored by the AMF as specified in clause 8.3.2.2 or by the MB-SMF as specified in clause 8.3.2.3.
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.3.2.2 Broadcast MBS session restoration by AMF
| The procedure specified in this clause may be supported to restore a broadcast MBS session affected by an NG-RAN restart.
The AMF handling a broadcast MBS session is responsible for restoring the MBS session in a restarted NG-RAN, as shown in Figure 8.3.2.2-1.
NOTE 1: An NG-RAN restart is transparent to the MB-SMF (i... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.3.2.3 Broadcast MBS session restoration by MB-SMF
| The procedure specified in this clause may be supported to restore a Broadcast MBS session affected by an NG-RAN restart.
When the AMF detects an NG-RAN restart, or a (new) NG-RAN is deployed to serve a TAI that is part of the MBS session service area, e.g. using NG Setup Request message, as specified in 3GPP TS 38.41... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.3.2.4 Selecting an alternative AMF for a Broadcast MBS Session at AMF failure
| When the AMF selected by the MB-SMF to start a Broadcast MBS Session fails without restart, to support the restoration procedure to restore an Broadcast MBS Session in a restarted NG-RAN as specified in 8.3.2.2 and 8.3.2.3, another AMF in the same AMF set needs to be selected to become the serving AMF for this broadcas... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.3.3 Broadcast MBS session restoration Procedure for NG-RAN failure without restart
| The procedure specified in this clause may be supported to restore a Broadcast MBS session affected by an NG-RAN failure without restart.
When the AMF detects NG-RAN failure without restart, e.g. using SCTP path failure detection mechanism, it shall report such event to the MB-SMF for each of MBS session(s) affected b... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.3.4 Multicast MBS session restoration Procedure for NG-RAN failure with or without restart
| The procedure specified in this clause may be supported to restore a Multicast MBS session affected by an NG-RAN failure with or without restart.
When a UPF detects the NG-RAN failure with or without restart using Echo Request and Echo Response message which is sent towards the IP address in the DL F-TEID allocated by... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.4 Restoration procedures for AMF failure
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.4.1 Multicast MBS session (de)activation or update after an AMF failure
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.4.1.1 General
| Different NG-RAN nodes may establish shared delivery for the same MBS session via different AMFs of a same AMF set. During the shared delivery establishment:
- each AMF involved in the establishment of shared delivery stores in its multicast MBS session context the RAN-ID of the NG-RAN nodes that have established shar... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.4.1.2 N2 MBS session request distribution with list of NG RAN Node IDs provided by MB-SMF to AMF
| During the shared delivery establishment procedure (see clause 7.2.1.4 of 3GPP TS 23.247 [12]), the MB-SMF stores, for each AMF involved in the establishment of shared delivery, the list of NG-RAN Node IDs having shared delivery established through the AMF.
The MB-SMF may then send any multicast MBS session activation... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.5 Broadcast MBS session restoration Procedure for N3mb path failure
| The procedure specified in this clause may be supported to restore a Broadcast MBS session affected by an N3mb path failure when unicast transport is used over the N3mb interface.
When the procedure is supported, when the MB-UPF detects and reports an N3mb path failure towards the MB-SMF, the MB-SMF may initiate the B... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 8.6 Multicast MBS session restoration Procedure for N3mb path failure
| The procedure specified in this clause may be supported to restore a multicast MBS session affected by an N3mb path failure when unicast transport is used over the N3mb interface.
When the procedure is supported, when the MB-UPF detects and reports an N3mb path failure towards the MB-SMF, the MB-SMF may initiate the M... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 9 Restoration Procedures for Network Timing Synchronization Status Monitoring
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 9.1 General
| This clause specifies the procedures supported in the 5G System to restore network timing synchronization status monitoring upon a failure affecting the AMF, NG-RAN or TSCTSF. The stage 2 procedures for network timing synchronization status monitoring are specified in clause 4.15.9.5 of 3GPP TS 23.502 [3].
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 9.2 AMF failure with or without restart
| When an AMF instance fails with or without restart, the subscriptions for non-UE specific N2 information that were created at this AMF instance before the AMF failure are lost.
The TSCTSF may detect the failure of the AMF instance with or without restart by using the procedures defined in clauses 6.2 and 6.3.
Upon se... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 9.3 NG-RAN failure with or without restart
| When an NG-RAN node fails with or without restart, the subscriptions for TSS information reporting that were created at the NG-RAN node before the NG-RAN failure are lost.
Upon detecting that an NG-RAN node fails with or without restart, the AMF shall notify the TSCSTFs subscribed to TSS information reporting about th... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 9.4 TSCTSF failure with or without restart
| The procedure specified in this clause is optional to support.
NOTE 1: The procedure specified in this clause is not needed for deployments where the TSCSTF supports resiliency across TSCTSF instances. If the TSCTSF instance is deployed within an TSCTSF set, the failure with or without restart of a TSCSTF instance is ... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 1 Scope | The present document defines the Stage 2 architecture, procedures and services to support service based short message service (SMS) in 5G system (5GS). |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 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.
- Fo... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 3 Definitions of terms and abbreviations | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 3.1 Terms | For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
alert‑SC: service element provided by a GSM/UMTS/EPS/5GS PLMN to inform an SC which has pr... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
GPSI Generic Public Subscription Identifier
MNPF Mobile Number Po... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 4 Architecture to support SBI-based SMS | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 4.1 Architecture to support SBI-based SMS | Figure 4.1-1 shows the non-roaming architecture to support SBI-based SMS.
Figure 4.1-1: Non-roaming architecture for SBI-based SMS
Figure 4.1-2a, Figure 4.1-2b Figure 4.1-2c and Figure 4.1-2d depict the non-roaming architecture to support SBI-based SMS, using the reference point representation showing how various netwo... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.