hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.1 Restart of the HLR/HSS | The periodic backup of HLR/HSS data to non-volatile storage is mandatory.
When an HLR/HSS restarts after failure it shall perform the following actions for the subscriber data records that have been affected by the HLR/HSS fault:
- reload all data from the non-volatile back-up;
- reset all "MS Purged" flags;
- mark eac... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2 Procedures During Restoration | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2.1 Mobile terminated call | If the VLR receives a "Process Access Request" request in response to a "Page" or "Search for MS" operation, after successful authentication, if required, it checks the indicator "Location Information Confirmed in HLR". If this indicates "Not Confirmed" the VLR triggers an "Update Location" to the HLR as described in c... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2.2 Mobile Originated Activity for CS | When the VLR receives a request from an MS (MS originated call, mobile originated Short Message, call-independent supplementary service activity or location registration request) whose IMSI record is marked "Location Information Not Confirmed in HLR", it will perform an "Update Location" to the HLR as described in clau... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2.3 Mobile Originated Activity for ProSe | When the ProSe Function receives a request for ProSe Service from a UE whose associated context is marked as "Subscriber Data Not Confirmed by HSS", it shall initiate a "ProSe Subscriber Information Retrieval" request to the HSS as described in the 3GPP TS 29.344 [34].
When the HSS receives a "ProSe Subscriber Informat... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2.4 Procedures in the SGSN | Upon receipt of a HLR/HSS reset, the SGSN shall mark each relevant MM contexts as invalid and shall set the Non-GPRS Alert Flag (NGAF) if an SGSN - MSC/VLR association exists. After detection of any activity (either signalling or data) from a marked MS or any other implementation dependent trigger for a marked MS in PM... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2.5 Procedures in the MME | Upon receipt of a HSS reset, the MME shall mark each relevant MM contexts as invalid and shall set Non-EPS Alert Flag (NEAF) if an MME - MSC/VLR association exists. After detection of any activity (either signalling or data) from a marked UE or any other implementation dependent trigger for a marked UE in ECM-CONNECTED... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2.6 Mobile Originated Activity for V2X | When the V2X Control Function receives a request for V2X Service from a UE whose associated context is marked as "Subscriber Data Not Confirmed by HSS", it shall initiate a "V2X Subscriber Information Retrieval" request to the HSS as described in the 3GPP TS 29.388 [41].
When the HSS receives a "V2X Subscriber Informat... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 6 Periodic location updating | The time taken to confirm the location of an MS after location register failure is governed by the frequency with which the MS establishes radio contact with the network. The location information for an MS which remains silent for a long time will remain doubtful for a long time.
A method of reducing this time is to re... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 7 Periodic routeing area updating | All GPRS-attached MSs, except MSs in class-B mode of operation engaged in CS communication, shall perform periodic RA updates. For MSs that are both IMSI-attached and GPRS-attached, the periodic updates depend on whether the Gs interface is installed or not:
- If the Gs interface is installed, periodic RA updates shall... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 8 Stand-alone operation of the VLR | In a 2G authentication regime, triplets, regardless of its nature (generated in a 2G AuC or derived from quintuplets in a 3G VLR or a 3G HLR), may be reused when no unused authentication triplets are available in the VLR for an IMSI record. It is an operator option to define how many times an authentication triplet may... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 9 Stand-alone operation of the SGSN | In a 2G authentication regime, triplets, regardless of their nature (generated in a 2G AuC or derived from quintuplets in a 3G SGSN or a 3G HLR), may be reused when no unused authentication triplets are available in the SGSN for an IMSI record. It is an operator option to define how many times an authentication triplet... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10 Restoration of data in the GGSN | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10.0 GGSN failure | When a GGSN fails, all its PDP contexts affected by the failure become invalid and may be deleted. GGSN storage of subscriber data is volatile.
When the GGSN receives a GTP‑U PDU for which no PDP context exists, it shall discard the GTP‑U PDU and return a a GTP error indication to the originating node (the SGSN or, if ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10.1 Restart of the GGSN | After a GGSN restart, all the PDP contexts, the MBMS UE contexts, and the MBMS Bearer contexts stored in the GGSN and affected by the restart become invalid and may be deleted.
When the SGSN detects a restart in a GGSN (see clause 18 "GTP-C based restart procedures") with which it has one or more PDP contexts activated... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10.2 Restoration Procedures | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10.2.0 General | The GGSN will receive the SGSN restart counters in GTPv1 echo response from the SGSN. When a GGSN detects that a peer SGSN has restarted it shall delete all PDP context(s), MBMS UE context(s), MBMS Bearer context(s) associated with the peer node that failed as well as freeing any internal GGSN resources associated with... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10.2.1 Mobile terminated transmission | When the GGSN receives a mobile terminated PDU for which no valid PDP context exists the GGSN discards the received PDU and may also return an appropriate Error message depending on the protocol used. No further actions are performed by the GGSN. Alternatively, if the GGSN has static PDP information about the PDP addre... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10.2.2 Mobile originated transmission | When the GGSN receives a tunnel PDU for which no PDP context exists it discards the tunnel PDU and sends an Error indication message to the originating SGSN. The SGSN deactivates the PDP context and sends an Error indication to the MS. The MS may then re-activate the PDP context. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11 Restoration of data in the SGSN | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.0 SGSN Failure | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.0.1 Gn/Gp SGSN failure | When an SGSN fails, it deletes all MM and PDP contexts affected by the failure. SGSN storage of subscriber data is volatile. Based on configuration data, the SGSN may send a Reset message to each of its associated VLRs. If a Reset message is sent, the VLR may mark all associations containing the restarted SGSN as unrel... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.0.2 SGSN Failure using S4 | When the SGSN receives a GTP‑U PDU from the Serving GW for which no Bearer context exists, it shall discard the GTP‑U PDU and send a GTP error indication to the originating Serving GW.
When the SGSN receives a GTP‑U PDU from the MBMS GW for which no MBMS Point to Point Bearer context exists, it shall discard the GTP‑U ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.1 Restart of the SGSN | After an SGSN restart, the SGSN deletes all MM, PDP, MBMS UE, and MBMS Bearer contexts affected by the restart.
When the GGSN detects a restart in an SGSN (see clause 18 "GTP-C based restart procedures") with which it has PDP context(s) activated and/or MBMS UE context(s), it shall delete all these PDP context(s) and/o... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2 Restoration Procedures | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2.1 Mobile terminated user data transmission | When a Gn-SGSN receives a tunnel PDU for which no PDP context or MBMS Bearer Context exists it discards the tunnel PDU and sends an Error indication message to the originating GGSN.
An S4-SGSN and an SGW supporting the optional network triggered service restoration procedure shall behave as specified in clause 25. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2.2 Mobile terminated services requested by the MSC/VLR | When the SGSN receives a request for CS paging from an MSC/VLR for an IMSI unknown by the SGSN, if the "SGSN-Reset" indicator is set to "true", the SGSN sends the paging request with the location information provided by the VLR. If no such location information is provided, the SGSN should page for the MS in all the rou... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2.3 Mobile terminated SMS over GPRS | a) Send Routing Information for MT SMS (SMS-GMSC -> HLR):
The HLR returns the SGSN number as for normal operation.
b) Send Information for MT SMS:
- When the SGSN receives a mobile terminated SMS for an unknown MM context for the MS, or if the SGSN indicator "Subscriber Data Confirmed by HLR" is marked "Not Confirmed" ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2.4 Mobile originated Routeing Area Updating or Attach | For attach, where the MS is unknown in the SGSN (i.e. the SGSN has no MM context for the MS) the SGSN creates an MM context for the MS and sets the indicators "Location Information Confirmed in HLR", "Subscriber Data Confirmed by HLR", "Location Information Confirmed by CSS" and "Subscriber Data Confirmed by CSS" to "N... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2.5 Mobile originated LLC frame | If an SGSN receives an LLC frame for which no MM context exists in the SGSN, and if the LLC frame does not contain an Attach Request or a Routeing Area Update Request signalling message, then the LLC frame shall be discarded. The MS may determine that the network is not responding and attempt to re-attach or eventually... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2.6 Mobile originated Service Request | For service request, where the MS is unknown in the SGSN (i.e. the SGSN has no MM context for the MS), the SGSN shall reject the service request with an appropriate cause. In order to remain GPRS-attached, the MS shall then perform a new GPRS attach and should (re‑)activate its PDP contexts.
If the SGSN has an MM conte... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.3 Use of TLLI | After the SGSN has restarted but before the next authenticated radio contact the P‑TMSI and TLLI known by the MS are invalid, as the P-TMSI was allocated before the SGSN restarted. The SGSN may request the MS to identify itself with the IMSI in order to make a relationship between the IMSI and the received old TLLI. Th... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.4 VLR associations | All associations with VLRs affected by the restart of an SGSN are marked as unreliable and may be deleted. Based on configuration data, Reset messages may be sent on the Gs-interface to the VLRs served by the SGSN. If Reset messages are sent, the VLRs may mark all associations with the SGSN as unreliable by setting the... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.5 Restart of a peer node | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.5.1 SGW failure | When an SGSN detects that a peer SGW has failed with or without restart (relying on restart counter as specified in clause 18 "GTP-C based restart procedures" or implementation e.g. preconfigured path failure timer) it shall either:
- as a default delete all PDN connection table data/MM bearer contexts associated with ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.5.2 MBMS-GW failure | The behaviour of an SGSN when it detects that a peer MBMS GW has restarted is described in clause 17A.1. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 12 Restoration of Data in an SMLC (GSM only) | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 12.1 Restart of an SMLC | When an SMLC restarts after a failure, it performs the following actions for those of its associated LMUs whose records have been affected by the fault:
- Reload all administered LMU data from non-volatile back-up;
- Reinitialize other temporary data for each LMU to indicate no ongoing measurement or diagnostic activit... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 12.2 Data Restoration for a Specific LMU | An SMLC may restore data for a specific LMU when the data in the SMLC or LMU is considered unreliable (e.g. if there is no communication between the SMLC and LMU for a long time or if messages received by the SMLC are inconsistent with the LMU state kept by the SMLC). To restore data for a specific LMU, the SMLC shall ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 13 Restoration of Data in an LMU (GSM only) | When an LMU restarts following a failure, it shall reinitialize all data concerning LCS measurement and O&M tasks to indicate that no tasks ordered by an SMLC are active. A Type A LMU shall then perform an "IMSI Attach". A Type A LMU shall then open a signalling connection to its controlling SMLC as described in 3GPP T... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14 Restoration of data in the MME | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1 Restart of the MME | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1.1 Restoration Procedures | After an MME restart, the MME shall delete all MM Bearer contexts affected by the restart that it may have stored.
When the MBMS GW detects a restart in an MME (see clause 18 "GTP-C based restart procedures") with which it has at least one MBMS Bearer context, the MBMS-GW should re-establish the active MBMS bearer serv... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1.2 Mobile originated Tracking Area Updating or E-UTRAN Attach | For attach, where the UE is unknown in the MME (i.e. the MME has no MM context for the UE) the MME shall create an MM context for the UE and shall set the indicators "Location Information Confirmed in HSS", "Subscriber Data Confirmed by HSS", "Location Information Confirmed by CSS" and "Subscriber Data Confirmed by CSS... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1.3 Mobile terminated services requested by the MSC/VLR | An MME and a VLR supporting mobile terminated CS service delivery via an alternative MME in MME pool shall behave as specified in clause 26.
When the MME receives a request for CS paging from an MSC/VLR for an IMSI unknown by the MME, if the "MME-Reset" indicator is set to "true", the MME sends the paging request with ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1.4 Mobile terminated user data transmission | An MME and an SGW supporting the optional network triggered service restoration procedure shall behave as specified in clause 25. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1.5 Mobile originated Service Request | For service request, where the UE is unknown in the MME (i.e. the MME has no MM context for the UE), the MME shall reject the service request with an appropriate cause. In order to remain attached, the UE shall then perform a new attach and should (re‑)activate its EPS Bearer contexts.
If the MME has an MM context for ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1.6 Mobile Terminated NIDD procedure | During the Mobile Terminated NIDD procedure, if the SCEF receives a MT-Data-Answer from the MME/SGSN with a failure cause that UE cannot be found, the SCEF shall delete all the bearer contexts of this UE and may notify the Operation and Maintenance network element.
NOTE: After that, if the SCEF receives a following NID... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.2 VLR associations | All associations with VLRs affected by the restart of an MME are marked as unreliable and may be deleted. Based on configuration data, Reset messages may be sent on the SGs interface to the VLRs served by the MME. If Reset messages are sent, the VLRs may mark all associations with the MME as unreliable by setting the r... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.3 Partial Failure Handling at MME | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.3.1 General | See Clause 23. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.3.2 Procedures during PDN Connection Establishment | If the MME supports the feature, the following procedures apply.
During a PDN connection establishment, the MME shall provide one MME FQ-CSID containing exactly one CSID for that particular PDN connection to the SGW in the S11 Create Session Request. The MME shall store the Node-ID and CSID values from the FQ-CSID prov... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.3.3 Procedures during MME Partial Failure | If the MME supports the feature the following procedures apply.
When an MME detects that it has undergone a partial failure, it shall verify that one or more corresponding CSID(s) are present for the component(s) undergoing a partial fault. If there is no such CSID, then the following does not apply. When one or more C... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.3.4 Procedures during a Peer's Partial Failure | If the MME supports the feature, the following procedures apply.
When an MME receives a GTPv2 Delete PDN Connection Set Request message from an SGW, the MME shall retrieve all the PDN connections corresponding to each of the FQ-CSID(s) present in the message. The MME shall delete all the retrieved PDN connections and t... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.3.5 Procedures during PDN Connection Removal or Modification | If an MME and an SGW support the feature, the following procedures apply.
During an S11 procedure, impacting an existing PDN connection removal or modification the following apply:
1) If the SGW is being relocated then the MME shall clear the currently stored SGW FQ‑CSID .
2) If an MME relocation occurs (for example, T... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 15 Restoration of data in GERAN/UTRAN | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 15.1 BSS Failure (A/Gb mode) | When a BSS fails, all its BSS contexts affected by the failure become invalid and shall be deleted. BSS storage of data is volatile. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 15.2 RNC/BSC Failure (Iu mode) | When an RNC/BSC fails, all its RNC/BSC contexts affected by the failure become invalid and shall be deleted. RNC/BSC storage of data is volatile. An SGSN that recognises unavailability of an RNC/BSC or receives a Reset from an RNC/BSC, shall locally release the RABs for all affected PDP contexts.
Any affected PDP conte... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 15.3 RNC/BSC Failure (Iu mode) using S4 | When an RNC/BSC fails, all its RNC/BSC contexts affected by the failure become invalid and shall be deleted. RNC/BSC storage of data is volatile. An SGSN that recognises unavailability of an RNC/BSC or receives a Reset from an RNC/BSC, shall locally release the RABs for all affected PDP contexts. If ISR is activated or... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 15.4 Other RNC functionality for MBMS restoration | The RNC should accept an MBMS Session Start Request received for an ongoing MBMS session (i.e. with the same TMGI)
- from the same or a different SGSN than the SGSN that currently controls the MBMS session, if the message contains the "MBMS session re-establishment indication" flag; or
- from the SGSN that currently co... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 15.5 Iu path failure using S4 | Upon detection of an Iu path failure (i.e. no more SCTP association in service),
- the RNC shall release all the MBMS services affected by the Iu path failure either immediately or after a pre-configured time period if the corresponding MBMS bearer contexts are not re-established via any S4-SGSN;
- the S4-SGSN shall ma... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 16 Restoration of data in the SGW | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 16.1 Restart of the SGW | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 16.1.0 SGW Failure | When a SGW fails, all its Bearer contexts affected by the failure become invalid and may be deleted. SGW storage of subscriber data is volatile.
When the SGW receives a GTP‑U PDU for which no Bearer context exists, it shall discard the GTP‑U PDU and return a GTP error indication to the originating node (the PGW, the eN... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 16.1.1 Restoration Procedures | After an SGW restart, the SGW shall delete all MM Bearer contexts affected by the restart that it may have stored.
During or immediately after an SGW Restart the SGW shall place local SGW restart counter value in all GTPv2 Echo requests/responses messages and PMIPv6 heartbeat responses the SGW sends.
16.1a Restart of t... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 16.2 Partial Failure Handling at SGW | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 16.2.1 General | See Clause 23.
In addition, the following applies. If an SGW, which supports the feature receives Delete PDN Connection Set Request/Reply messages from MME or the PGW it shall forward the messages to the appropriate peer.
If the SGW does not support the feature then partial failure handling does not apply to that speci... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 16.2.2 Procedures during PDN Connection Establishment | If the SGW supports the feature, the following procedures apply.
During a PDN connection establishment, the SGW shall provide one SGW FQ-CSID for that particular PDN connection to the PGW. Similarly, the SGW shall provide one SGW FQ-CSID for that particular PDN connection to the MME if the MME supports partial failure ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 16.2.3 Procedures during SGW Partial Failure | If the SGW supports the feature, the following procedures apply.
When an SGW detects that it has undergone a partial failure, it shall verify that one or more corresponding CSID(s) are present for the component undergoing a partial fault. If there is no such CSID, then the following does not apply. When one or more CSI... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 16.2.4 Procedures during a Peer's Partial Failure | If the SGW supports the feature, the following procedures apply.
When an SGW receives a S11 GTPv2 Delete PDN Connection Set Request message from an MME, the SGW shall retrieve all the PDN connections corresponding to each of the FQ-CSID(s) present in the message. The SGW shall send a S5/S8 GTPv2 Delete PDN Connection S... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 16.2.5 Procedures during PDN Connection Removal or Modification | Only if the SGW supports the feature, the following procedures apply.
During a S11 or an S5/S8 procedure, impacting an existing PDN connection removal or modification the following apply:
1) If the MME is being relocated then the SGW shall clear the currently stored MME FQ‑CSID value (if any).
2) For inter MME and intr... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 17 Restoration of data in the PGW | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 17.1 Restart of the PGW | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 17.1.0 PGW Failure | When a PGW fails, all its Bearer contexts affected by the failure become invalid and may be deleted. PGW storage of subscriber data is volatile.
When the PGW receives a GTP‑U PDU for which no Bearer context exists, it shall discard the GTP‑U PDU and return a GTP error indication to the originating node i.e. the SGW/ePD... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 17.1.1 Restoration Procedures | After a PGW restart, the PGW shall delete all MM Bearer contexts affected by the restart that it may have stored.
During or immediately after a PGW Restart, the PGW shall place this PGW restart counter value in all GTPv2 echo requests/responses and PMIPv6 heartbeat responses the PGW sends.
17.1a Restart of the PGW-C
17... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 17.2 Partial Failure Handling at PGW | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 17.2.1 General | See Clause 23. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 17.2.2 Procedures during PDN Connection Establishment | If the PGW supports the feature, the following procedures apply.
During a PDN connection establishment, the PGW shall provide one FQ-CSID containing exactly one CSID for that particular PDN connection to the SGW, the ePDG or the TWAN. The PGW shall store the FQ-CSID provided by the SGW and the MME in the PDN Connection... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 17.2.3 Procedures during PGW Partial Failure | If the PGW supports the feature, the following procedures apply.
When a PGW detects that it has undergone a partial failure, it shall verify that one or more corresponding CSID(s) are present for the component(s) undergoing a partial fault. If there is no such CSID, then the following does not apply. When one or more C... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 17.2.4 Procedures during a Peer's Partial Failure | If the PGW supports the feature, the following procedures apply.
When a PGW receives a GTPv2 Delete PDN Connection Set Request (or PMIPv6 Binding Revocation Indication with G bit set) message from an SGW, an ePDG or a TWAN, the PGW shall retrieve all the PDN connections corresponding to each of the FQ-CSIDs present in ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 17.2.5 Procedures during PDN Connection Removal or Modification | If the PGW supports the feature, the following procedures apply.
During a S5/S8 procedure, impacting an existing PDN connection Removal or Modification the following apply:
1) If an SGW is being relocated then the PGW shall clear the currently stored MME and SGW FQ‑CSID values.
2) If the SGW includes a SGW FQ-CSID in t... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 18 GTP-C based restart procedures | Across GTP-C based interfaces an SGSN, GGSN, MME, SGW, PGW, TWAN, ePDG and HRPD Access Node utilize either GTPv1-C or GTPv2-C Echo Request and Echo Response messages or GTP-C messages containing the Recovery Information Element to detect and handle a restart.
A GTP-C entity shall maintain two Restart counters:
- in vol... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 19 PMIPv6 based restart procedures | Across PMIPv6 based interfaces, SGW, PGW, TWAN and ePDG utilize PMIPv6 Heartbeat mechanism for node restart detection as specified in 3GPP TS 29.275 [16].
A PMIPv6 entity shall maintain two restart counters:
- in volatile memory a remote restart counter of a peer with which the entity is in contact;
- in non-volatile m... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20 Path management procedures | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.1 General | This clause specifies path management procedures for GTP-C based, PMIP and PFCP based interfaces.
For GTP based interfaces, Echo Request / Response procedure is used. The usage depends on the GTP-C version in the following way:
- GTPv1-C entity may periodically send an Echo Request message as specified in 3GPP TS 29.06... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2 Signalling path failure detection and handling | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.1 General | GTP-C entities shall support detection of path failure by using Echo Request / Echo Response messages in the following way. A peer's IP address specific counter shall be reset each time an Echo Response message is received from that peer's IP address and incremented when the T3-RESPONSE timer expires for an Echo Reques... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.2 SGW functionality | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.2.1 S11/S4 path failure | It is optional for the SGW to maintain the S5/S8 bearer contexts when the SGW detects a path failure to the MME/S4-SGSN (see clause 20.2.1). However upon detecting a path failure to the MME/S4-SGSN, an SGW that supports the network triggered service restoration procedure (see clause 25) should maintain the S5/S8 bearer... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.2.2 S5 path failure | The SGW may support the PGW triggered SGW restoration for an S5 path failure. If so, then the SGW should support the PGW Restart Notification procedure. After detecting a path failure to the PGW, the SGW may delete all the PDN connections affected by the path failure and should also send a PGW Restart Notification mess... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.3 MBMS GW functionality | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.3.1 Sm path failure | The MBMS GW may be provisioned with the list (or a sublist) of the MMEs pertaining to the MME pool.
NOTE 1: The MBMS GW expects only one MME of the MME pool in BM-SC requests received across the SGmb interface.
Upon detecting an Sm path failure, the MBMS GW should maintain the MBMS bearer contexts associated with the p... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.3.2 Sn path failure | The MBMS GW may be provisioned with the list (or a sub list) of the SGSNs belonging to the SGSN pool.
NOTE: The MBMS GW expects only one SGSN of the SGSN pool in BM-SC requests received across the SGmb interface.
An MBMS GW and SGSN shall handle Sn path failure similar to the Sm path failure as described in clause 20.2... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.3.3 SGmb path failure | In deployments without a Diameter Agent between the BM-SC and the MBMS GW, the MBMS GW shall detect an SGmb path failure using either:
- mechanisms as specified in the Diameter Base Protocol (e.g. transport connection failure, BM-SC peer not responding, Diameter Device-Watchdog-Request and Device-Watchdog-Answer messag... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.4 MME functionality | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.4.1 Sm path failure | Upon detecting an Sm path failure, the MME should maintain the MBMS bearer contexts associated with the peer's MBMS GW IP address during an operator configurable maximum path failure duration.
The MME should behave as specified for the case of an MBMS GW restart (see clause 17A.1) if the Sm path to the MBMS GW is down ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.4.2 S5 path failure | The MME may support invoking the PGW triggered SGW restoration (see clause 27.2.3) upon receiving a PGW Downlink Triggering Notification message when the S11 path for the related UE is still available (see clause 20.2.1). If so, upon receiving a PGW Downlink Triggering Notification while the S11 path for the related UE... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.5 SGSN functionality | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.5.1 Sn path failure | Upon detecting an Sn path failure, the S4-SGSN should maintain the MBMS bearer contexts associated with the peer's MBMS GW IP address during an operator configurable maximum path failure duration.
The S4-SGSN should behave as specified for the case of an MBMS GW restart (see clause 17A.1) if the Sn path to the MBMS GW ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.5.2 S5 path failure | The S4-SGSN may support invoking the PGW triggered SGW restoration (see clause 27.2.3) upon receiving a PGW Downlink Triggering Notification and the S4 path of the related UE is still available (see clause 20.2.1). If so, S4-SGSN shall proceed as defined for the MME in clause 20.2.4.2, with the following modification:
... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.