s4-sgsn suspend-resume feature...username:123456789012345 accesstype:sgsn networktype:ip...

S4-SGSN Suspend-Resume Feature

This chapter describes the S4-SGSN Suspend/Resume feature.

• Feature Description, on page 1• How it Works, on page 2• Configuring the S4-SGSN Suspend/Resume Feature, on page 12• Monitoring and Troubleshooting the S4-SGSN Suspend/Resume Feature, on page 12

Feature DescriptionThe S4-SGSN Suspend/Resume feature provides support for suspend/resume procedures from the BSS anda peer S4-SGSN.

When a UE is in a 2G coverage area wants to make a circuit switched voice call but the Class A mode ofoperation is not supported by the network, then the packet switched data session (PDP contexts) must besuspended before the voice call can be made. In this case, the BSS sends a Suspend Request to the SGSN. Ifthe UE is already attached at that SGSN then the suspend request is handled via an intra-SGSN suspend/resumeprocedure. If the UE is not attached at the SGSN then the Suspend Request is forwarded to a peer SGSN/MMEthroughGTPv2 and an inter-SGSN/SGSN-MME suspend procedure occurs. Once the UE completes the voicecall, either the BSS sends a resume request to resume the suspended PDPs or the UE directly sends a RoutingArea Update Request (RAU) in 2G which will be treated as an implicit resume.

The ability for a GPRS user to access circuit-switched services depends on the subscription held, the networkcapabilities, and the MS capabilities.

Suspension of GPRS ServicesThe MS sends a request to the network for the suspension of GPRS services when the MS or the networklimitations make it unable to communicate on GPRS channels in one or more of the following scenarios:

1. A GPRS-attached MS enters dedicated mode and the support of the Class A mode of operation is notpossible (for example, the MS only supports DTM and the network only supports independent CS andPS).

2. During CS connection, the MS performs a handover from Iu mode to A/Gb mode, and the MS or thenetwork limitations make it unable to support CS/PS mode of operation, (for example, an MS in CS/PSmode of operation in Iu mode during a CS connection reverts to class-Bmode of operation in A/Gbmode).

3. When an MS in class A mode of operation is handed over to a cell where the support of Class A mode ofoperation is not possible (for example, a DTMmobile station entering a cell that does not support DTM).

S4-SGSN Suspend-Resume Feature1

Relationships to Other FeaturesOne of the following configurations must exist on the SGSN for the Suspend Resume feature to work properlyon the S4-SGSN:

• 2G SGSN Service + S4-SGSN Support• 3G SGSN Service + S4-SGSN Support• 2G SGSN Service + 3G SGSN Service + S4-SGSN Support

Configuration procedures for the above deployments are available in this guide.

How it Works

S4-SGSN Suspend-Resume FeatureWhen a UE wants to make or receive a voice call via a GERAN circuit switched domain, and if the UE/BSSdoesn't support DTM mode, then the BSS sends a Suspend Request to the SGSN to suspend any packet datatransmission. This suspend request can be received on the same SGSNwhere a subscriber is already attached,or it can be received on an SGSN where the subscriber is not yet attached.

SGSN where subscriber is attached: The SGSN initiates an intra-SGSN suspend procedure and will haveto suspend the data transmission all the way up to the PGW by sending a Suspend Request to the SGW/PGW.When the UE completes the CS call, it will resume the packet transmission. The BSS will send a Resumerequest in this case.

SGSN where subscriber is not yet attached: The SGSN initiates an inter-SGSN suspend procedure bysending a GTPv2 / GTPv1 Suspend Request to the peer SGSN/MME. The peer node will suspend the datatransmission. When the UE completes the CS call, it may directly send a Routing Area Update request to the2G SGSN to handover the packet switched contexts. The 2G SGSN will do a Context Request / ContextResponse / Context Ack procedure with the peer node and will send a Create Session Request (if SGWrelocation occurs) or a Modify Bearer Request (if no SGW relocation occurs) to the SGW. TheModify BearerRequest at the PGW will be treated as an implicit Resume.

LimitationsThe following are the known limitations for the S4-SGSN Suspend/Resume feature:

1. If a suspend request aborts an ongoing RAU triggered SGW relocation, the Create Session Request willbe aborted and the PDN will be cleaned up. This is to avoid complexities in the state machine. If thesystem retained PDP, the system would have to recreate the tunnel towards the old SGW to PGW beforesending the Suspend Notification. This would delay the Suspend procedure.

2. A Suspend Request from the default SGSN in a pool to the SGSN serving the NRI of the given PTMSIis not possible via the S16 interface due to a standards limitation. R10 specifications don't have a hopcounter and UDP source port IEs in the Suspend Notification message and hence this limitation. This iscorrected in R11 specifications. TheS4-SGSN will support this call flow only in later releases.

3. HSS initiated modification will be queued, if the Suspend preempts an HSS initiated modification whilepending for an Update Bearer Request from the PGW. The queued procedure will be restarted in asubsequent procedure (RAU / Resume). Queued information will not be transferred to another RAT type,if a subsequent procedure changes the RAT type.


S4-SGSN Suspend-Resume FeatureRelationships to Other Features

4. ASuspend Acknowledge with rejected cause will not be sent to the peer SGSN/MMEwhen an inter-SGSNSuspend procedure is preempted by procedures such as RAU, Context Request, and Detach Request atthe old SGSN. SuspendAcknowledge is not sent because it is very complex on the PMM-side to distinguishbetween two procedures as the PMM has the same state for both the inter-SGSN Suspend procedure andthe inter-SGSN RAU procedure.

Call FlowsThis section includes various diagrams that illustrate the Suspend/Resume call flow procedures, and theinterface selection logic.

Intra-SGSN Suspend Procedure with Resume as the Subsequent ProcedureThe intra-SGSN Suspend procedure with Resume as the subsequent procedure is illustrated in the followingdiagram.

• When a 2G SGSN receives a Suspend Request from the BSS and if the subscriber is already attached tothe 2G SGSN, the PDPs shall be suspended. The SGSN then sends a Suspend Notification to the SGW,which subsequently is sent to the PGW to stop all data transmissions on non-GBR bearers.

• When a 2G SGSN receives a ResumeRequest from the BSS, and if the subscriber that is already suspendedis attached to the 2G SGSN, the PDPs are resumed. The SGSN then sends a Resume Notification to theSGW, which subsequently is sent to the PGW to resume all data transmissions on non-GBR bearers.


S4-SGSN Suspend-Resume FeatureCall Flows

Figure 1: Intra-SGSN Suspend Procedure with Resume as Subsequent Procedure

Intra-SGSN Suspend with Resume Procedure with Intra-RAU as Subsequent ProcedureAn Intra-SGSN Suspend procedure call flowwith an Intra-SGSNRAU procedure as the subsequent procedureis shown in the following illustration.

• If there is no SGW change for the RAU request, then the 2G-SGSN sends a Resume Notification to theSGW and the SGW then sends a Resume Notification to the PGW to resume all data transmissions.

• If there is a SGW change for the RAU request, then the 2G-SGSN sends a Create Session request to theSGW and the SGW sends a Modify Bearer Request to the PGW to resume all data transmissions.


S4-SGSN Suspend-Resume FeatureIntra-SGSN Suspend with Resume Procedure with Intra-RAU as Subsequent Procedure

Figure 2: Intra-SGSN Suspend Procedure with Intra-RAU as Subsequent Procedure

Inter-SGSN Suspend and Resume Procedure with Peer S4-SGSN/MMEThe procedure for a new SGSN Suspend Request and Resume procedure with a peer S4-SGSN/MME is shownin the following diagram.

• When an S4-SGSN receives a Suspend Request from the BSS and if the subscriber is not attached to the2G SGSN, the S4-SGSN will send a Suspend Notification to the peer S4-SGSN/MME.

• The new SGSNRAU is the Resume procedure after a new SGSN Suspend procedure has been completed.The SGSN sends a Create Session Request / Modify Bearer Request to the SGW which subsequently issent to the PGW to resume all data transmissions on non-GBR bearers.

• When the Gn-SGSN receives a Suspend Request from the BSS and if the subscriber is not attached tothe 2G SGSN, it sends a Suspend Notification to the peer Gn-SGSN / S4-SGSN/MME.


S4-SGSN Suspend-Resume FeatureInter-SGSN Suspend and Resume Procedure with Peer S4-SGSN/MME

Figure 3: Inter-SGSN Suspend and Resume Procedure with Peer S4-SGSN/MME

New Inter-SGSN Suspend and Resume Procedure from BSS to 2G Gn-SGSNA new SGSN Suspend Request from the BSS to a 2G Gn-SGSN is shown in the following illustration.

• The newSGSNRAU is the Resume procedure after the newSGSNSuspend procedure has been completed.The Gn-SGSN sends an Update PDP Context Request to the GGSN which subsequently is sent to PGWto resume all data transmissions on non-GBR bearers.

• When the S4-SGSN receives a Suspend Request from the BSS and if the subscriber is not attached tothe 2G SGSN and the peer is a Gn-SGSN, it sends a Context Request with Suspend header (GTPv1Suspend Request) to the peer Gn-SGSN.


S4-SGSN Suspend-Resume FeatureNew Inter-SGSN Suspend and Resume Procedure from BSS to 2G Gn-SGSN

Figure 4: New Inter-SGSN Suspend and Resume Procedure from BSS to 2G Gn-SGSN

New SGSN Suspend and Resume Procedure with Peer Gn-SGSN as Old SGSNThe new SGSNSuspend procedure with a peer Gn-SGSN as the old SGSN is shown in the following illustration.

• The new SGSN RAU is the Resume procedure after the new SGSN Suspend procedure is completed.The SGSN sends a Create Session Request / Modify Bearer Request to the SGW which subsequently issent to the PGW to resume all data transmissions on non-GBR bearers.


S4-SGSN Suspend-Resume FeatureNew SGSN Suspend and Resume Procedure with Peer Gn-SGSN as Old SGSN

Figure 5: New SGSN Suspend and Resume Procedure with Peer Gn-SGSN as Old SGSN

Interface Selection Logic for Inter-SGSN Suspend (New SGSN) ProcedureInterface selection logic to find the peer address during the Inter SGSN Suspend (New SGSN Suspend)procedure is explained in the flowing flow chart.


S4-SGSN Suspend-Resume FeatureInterface Selection Logic for Inter-SGSN Suspend (New SGSN) Procedure

Figure 6: Interface Selection Logic for Inter-SGSN Suspend (New Suspend) Procedure


S4-SGSN Suspend-Resume FeatureInterface Selection Logic for Inter-SGSN Suspend (New SGSN) Procedure

Intra-SGSN Inter-System Suspend and Resume ProcedureThe intra-SGSN Inter-System Suspend and Resume procedure is shown in the following illustration. In thiscase, the BSS sends a Suspend Request to the 2G part of the SGSN. The 2G SGSN will internally send therequest to the 3G S4-SGSN where the PDPs are anchored. The PDP contexts are then suspended by 3GS4-SGSN as shown in the diagram.

The RAU is the Resume procedure after the 2G-3G Inter-System Intra-SGSN Suspend procedure is completed.The SGSN sends a Create Session Request / Modify Bearer Request / Resume Notification to the SGWwhichsubsequently is sent to PGW to resume all data transmissions on non-GBR bearers.

Figure 7: Intra-SGSN Inter-System Suspend and Resume Procedure

Inter-SGSN Inter-System Suspend and Resume ProcedureThe inter-SGSN inter-system Suspend and Resume procedure is shown in the following illustration. Thisdescribes the scenario when the suspend message is received in an SGSN that is different from the SGSNcurrently handling the packet data transmission and would be valid for at least the following cases:


S4-SGSN Suspend-Resume FeatureIntra-SGSN Inter-System Suspend and Resume Procedure

• MS performs inter-system handover from Iu mode to A/Gb mode during CS connection and the SGSNhandling the A/Gb mode cell is different from the SGSN handling the Iu mode cell, (that is. the 2G and3G SGSNs are separated).

The RAU is the Resume procedure after the 2G-3G Inter-System Inter-SGSNSuspend procedure has completed.The SGSN sends a Create Session Request / Modify Bearer Request to the SGW which subsequently is sentto PGW to resume all data transmissions on non-GBR bearers.

• If there is no SGW change for the RAU request, then the 2G-SGSN sends a Modify bearer request tothe SGW. The SGW then sends a MBR all the way up to the PGW if the RAT type / Serving networkchanges. Otherwise it will send the Resume Request to the PGW to resume all data transmissions.

• If there is a SGW change for the RAU request, then the 2G-SGSN sends a Create Session Request to theSGW and the SGW sends a Modify Bearer Request to the PGW to resume all data transmissions.

Figure 8: Suspend and Resume Procedure for Inter-SGSN Inter-System Suspend and Resume


S4-SGSN Suspend-Resume FeatureInter-SGSN Inter-System Suspend and Resume Procedure

Standards ComplianceThe Suspend/Resume feature on the S4-SGSN complies with the following standards:

• 3GPP TS 23.060 version 10.11.0 Release 10 - section 16.2.1 3rd Generation Partnership Project TechnicalSpecification Group Services and System Aspects General Packet Radio Service (GPRS) Servicedescription Stage 2 (Release 10)

• 3GPP TS 29.274 version 10.7.0 Release 10 - section 7.4 3rd Generation Partnership Project TechnicalSpecification Group Core Network and Terminals 3GPP Evolved Packet System (EPS) Evolved GeneralPacket Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C) Stage 3 (Release 10)

• 3GPP TS 23.272 version 10.11.0 Release 10 - section 6.7 (No PSHOSupport) 3rd Generation PartnershipProject Technical Specification Group Services and System Aspects Circuit Switched (CS) fallback inEvolved Packet System (EPS) Stage 2 (Release 10)

Configuring the S4-SGSN Suspend/Resume FeatureNo configuration is required to enable the S4-SGSN Suspend/Resume Feature.

MonitoringandTroubleshootingtheS4-SGSNSuspend/ResumeFeature

This section provides information on the show commands and bulk statistics available to support theSuspend/Resume feature.

S4-SGSN Suspend and Resume Feature Show CommandsThis section provides information regarding show commands available in support of the S4-SGSNSuspend/Resume feature.

show subscriber gprs-only full allIf the state field in the output of this command reads Suspended, it indicates that a subscriber has been movedfrom the Ready state to the Suspended state in 2G. Once this state change occurs, operators can use the showbssgp statistics and show egtpc statistics commands to view information on whether the Suspend procedurewas successful or not.Username: 123456789012345Access Type: sgsn Network Type: IPAccess Tech: GPRS GERANcallid: 00004e25 msid: 262090426000193state: Suspendedconnect time: Mon Jun 17 02:27:40 2013 call duration: 00h00m14sidle time: 00h00m14sUser Location (RAI): 26209-4369-19 Cell Global Identity: 3IMEI(SV): n/a

If the state field in the output of this command reads Ready, it indicates that a subscriber has moved from theSuspended state to the Ready state in 2G. For example:


S4-SGSN Suspend-Resume FeatureStandards Compliance

Username: 123456789012345Access Type: sgsn Network Type: IPAccess Tech: GPRS GERANcallid: 00004e25 msid: 262090426000193state: Readyconnect time: Mon Jun 17 02:27:40 2013 call duration: 00h00m14sidle time: 00h00m14sUser Location (RAI): 26209-4369-19 Cell Global Identity: 3IMEI(SV): n/a

show subscriber sgsn-only full allIf the state field in the output of this command reads Idle, it indicates that a subscriber has moved from theConnected state to the Idle state in 3G. For example:Username: 123456789012345Access Type: sgsn Network Type: IPAccess Tech: GPRS GERANcallid: 00004e25 msid: 262090426000193state: Readyconnect time: Mon Jun 17 02:24:05 2013 call duration: 00h00m23sidle time: 00h00m12sUser Location (RAI): 26209-4660-18 Service Area Code : 1202Serving PLMN: 26209IMEI(SV): n/a Equipment Status

If the state field in the output of this command reads Idle, it indicates that a subscriber has moved from theConnected state to the Idle state in 3G. For example:Username: 123456789012345Access Type: sgsn Network Type: IPAccess Tech: GPRS GERANcallid: 00004e25 msid: 262090426000193state: Connectedconnect time: Mon Jun 17 02:24:05 2013 call duration: 00h00m23sidle time: 00h00m12sUser Location (RAI): 26209-4660-18 Service Area Code : 1202Serving PLMN: 26209IMEI(SV): n/a Equipment Status

show bssgp statistics verboseThe output of this command tracks the number of BSSGP messages (BSS Suspend procedure) transmittedand received at the SGSN. It does not track the number messages between the BSS and the peer S4-SGSN orpeer MME. The show egtpc statistics command is used to track EGTPC messages transmitted and receivedbetween the SGSN and a peer S4-SGSN or peer MME. Operators can check number of suspend ack messagesreceived to identify successful suspend procedures. The number of suspend nackmessages indicate unsuccessfulsuspend procedures.

Table 1: show bssgp statistics verbose Command Output

suspend messages received:

Intra-Sgsn suspend message received:

Inter-Sgsn suspend message received:

Inter-System suspend message received:


S4-SGSN Suspend-Resume Featureshow subscriber sgsn-only full all

suspend ack messages transmitted:

Intra-Sgsn suspend ack message transmitted:

Inter-Sgsn suspend ack message transmitted:

Inter-System suspend ack message transmitted:

suspend nack messages transmitted:

Intra-Sgsn suspend nack message transmitted:

Inter-Sgsn suspend nack message transmitted:

Inter-System suspend nack message transmitted:

resume messages received:

resume ack messages transmitted:

resume nack messages transmitted:

show egtpc statisticsThe output of this command tracks the number of Suspend EGTPC messages transmitted and received fromor to a peer SGSN/MME or S-GW. The output also tracks the number of Resume EGTPCmessages transmittedto S-GW.

Detailed descriptions of these counters are available in the Statistics and Counters Reference.


S4-SGSN Suspend-Resume Featureshow egtpc statistics

Table 2: show egtpc statistics Command Output for S4-SGSN Suspend/Resume Feature

CS Fallback Messages:

Suspend Notification:

Initial TX: Initial RX:

Retrans TX Discarded:

No Rsp RX:

Suspend Acknowledge:

Initial TX:

Initial RX:

Discarded:

Resume Notification

Initial TX:

Initial RX:

Retrans TX:

Discarded:

No Rsp RX

Resume Acknowledge:

Initial TX:

Initial RX:

Discarded:

show egtpc statistics verboseThe output of this command tracks the number of denied Suspend notification recived and transmittedprocedures.

• Suspend Notification Denied TX means Suspend notification was denied due to any of errors listed inthe table that follows.

• Suspend Notification Denied RX means a Suspend notification was received incorrectly from the peerS4-SGSN.

Detailed descriptions of these counters are available in the Statistics and Counters Reference.

Table 3: show egtpc statistics verbose Command Output for S4-SGSN Suspend/Resume Feature

Suspend Notification Denied

Suspend Notification Denied RXSuspend Notification Denied TX

Context not existent:Context not existent:

Invalid message format:Invalid message format:


S4-SGSN Suspend-Resume Featureshow egtpc statistics verbose

Version not supported:Version not supported:

Invalid length:Invalid length:

Service not supported:Service not supported:

Mandatory IE incorrect:Mandatory IE incorrect:

Mandatory IE missing:Mandatory IE missing:

System failure:System failure:

No resources available:No resources available:

Semantic error in TFT:Semantic error in TFT:

Syntactic error in TFT:Syntactic error in TFT:

Semantic error in Pkt Fltr:Semantic error in Pkt Fltr:

Syntactic error in Pkt Fltr:Syntactic error in Pkt Fltr:

Missing or unknown APNMissing or unknown APN

GRE key not found:GRE key not found:

Reallocation failure:Reallocation failure:

Denied in RAT:Denied in RAT:

Pref. PDN type unsupported:Pref. PDN type unsupported:

All dynamic addr occupied:All dynamic addr occupied:

UE ctx w/o TFT activated:UE ctx w/o TFT activated:

Prot type not supported:Prot type not supported:

UE not responding:UE not responding:

UE refuses:UE refuses:

Service denied:Service denied:

Unable to page UE:Unable to page UE:

No Memory:No Memory:

User Auth Failed:User Auth Failed:

Apn Access Denied:Apn Access Denied:

Request Rejected:Request Rejected:

Semantic error in TAD:Semantic error in TAD:

Syntactic error in TAD:Syntactic error in TAD:



Collision with Nw init Req:Collision with Nw init Req:

UE page unable due to Susp:UE page unable due to Susp:

Conditional IE missing:Conditional IE missing:

Apn Restr Type Incompatible:Apn Restr Type Incompatible:

Invalid len Piggybacked msg:Invalid len Piggybacked msg:

Invalid remote Peer reply:Invalid remote Peer reply:

PTMSI signature mismatch:PTMSI signature mismatch:

IMSI not Known:IMSI not Known:

Peer not responding:Peer not responding:

Data Fwding not supported:Data Fwding not supported:

Fallback to GTPV1:Fallback to GTPV1:

Invalid Peer:Invalid Peer:

Temp Rej due to HO in prog:Temp Rej due to HO in prog:

Unknown:Unknown:

Resume Notification Denied

Resume Notification Denied RXResume Notification Denied TX

Context not existent:Context not existent:

Invalid message format:Invalid message format:

Version not supported:Version not supported:

Invalid length:Invalid length:

Service not supported:Service not supported:

Mandatory IE incorrect:Mandatory IE incorrect:

Mandatory IE missing:Mandatory IE missing:

System failure:System failure:

No resources available:No resources available:

Semantic error in TFT:Semantic error in TFT:

Syntactic error in TFT:Syntactic error in TFT:

Semantic error in Pkt Fltr:Semantic error in Pkt Fltr:

Syntactic error in Pkt Fltr:Syntactic error in Pkt Fltr:



Missing or unknown APNMissing or unknown APN

GRE key not found:GRE key not found:

Reallocation failure:Reallocation failure:

Denied in RAT:Denied in RAT:

Pref. PDN type unsupported:Pref. PDN type unsupported:

All dynamic addr occupied:All dynamic addr occupied:

UE ctx w/o TFT activated:UE ctx w/o TFT activated:

Prot type not supported:Prot type not supported:

UE not responding:UE not responding:

UE refuses:UE refuses:

Service denied:Service denied:

Unable to page UE:Unable to page UE:

No Memory:No Memory:

User Auth Failed:User Auth Failed:

Apn Access Denied:Apn Access Denied:

Request Rejected:Request Rejected:

Semantic error in TAD:Semantic error in TAD:

Syntactic error in TAD:Syntactic error in TAD:

Collision with Nw init Req:Collision with Nw init Req:

UE page unable due to Susp:UE page unable due to Susp:

Conditional IE missing:Conditional IE missing:

Apn Restr Type Incompatible:Apn Restr Type Incompatible:

Invalid len Piggybacked msg:Invalid len Piggybacked msg:

Invalid remote Peer reply:Invalid remote Peer reply:

PTMSI signature mismatch:PTMSI signature mismatch:

IMSI not Known:IMSI not Known:

Peer not responding:Peer not responding:

Data Fwding not supported:Data Fwding not supported:

Fallback to GTPV1:Fallback to GTPV1:



Invalid Peer:Invalid Peer:

Temp Rej due to HO in prog:Temp Rej due to HO in prog:

Unknown:Unknown:

show sgtpc statistics verboseThe output of this comnand tracks the number of SGSN Context Request transmitted and received messagetransmitted from the peer Gn-SGSN. It also tracks the number of SGSNContext Responsemessages transmittedand received from a peer Gn-SGSN.

Table 4: show sgtpc statistics Command Output for S4-SGSN Suspend/Resume Feature

SGSN Context Request:

Total SGSN-Ctx-Req RX:Total SGSN-Ctx-Req TX:

Initial SGSN-Ctx-Req RX:Initial SGSN-Ctx-Req TX:

SGSN-Ctx-Req-RX(V1):SGSN-Ctx-Req-TX(V1):

Suspend-Req-Hdr-RX:Suspend-Req-Hdr-TX:

SGSN-Ctx-Req-RX(V0):SGSN-Ctx-Req-TX(V0):

Retrans SGSN-Ctx-Req RX:Retrans SGSN-Ctx-Req TX:

Ret-SGSN-Ctx-Req-RX(V1):Ret-SGSN-Ctx-Req-TX(V1):

Ret-Suspend-Req-Header-TX:

Ret-SGSN-Ctx-Req-RX(V0):Ret-SGSN-Ctx-Req-TX(V0):

SGSN Context Response:

Total SGSN-Ctx-Rsp RX:Total SGSN-Ctx-Rsp TX:

Denied RX:Denied TX:

Suspend-Rsp-Hdr-Rx:Suspend-Rsp-Hdr-TX:

Accepted RX:Accepted TX:

Initial SGSN-Ctx-Rsp RX:Initial SGSN-Ctx-Rsp TX:

SGSN-Ctx-Rsp-RX(V1):SGSN-Ctx-Rsp-TX(V1):

Suspend-Rsp-Hdr-RX:Suspend-Rsp-Hdr-TX:

SGSN-Ctx-Rsp-RX(V0):SGSN-Ctx-Rsp-TX(V0):

Retrans SGSN-Ctx-Rsp RX:Retrans SGSN-Ctx-Rsp TX:

Ret-SGSN-Ctx-Rsp-RX(V1):Ret-SGSN-Ctx-Rsp-TX(V1):


S4-SGSN Suspend-Resume Featureshow sgtpc statistics verbose

Ret-SGSN-Ctx-Rsp-RX(V0):Ret-SGSN-Ctx-Rsp-TX(V0):

Decode Failure RX:

S4-SGSN Suspend and Resume Feature Bulk StatisticsThe following statistics are included in various bulk statistics schema in support of the Suspend/Resumefeature:

• SGSN Schema:

• 2G-attach-fail-suspend-received• 2G-attach-fail-comb-suspend-received

For descriptions of these variables, see the SGSN Schema Statistics section in the Statistics and CountersReference.

• GPRS Schema

• bssgp-suspend-msg-rcvd• bssgp-suspend-ack-msg-sent• bssgp-suspend-nack-msg-sent• bssgp-resume-msg-rcvd• bssgp-resume-ack-msg-sent• bssgp-resume-nack-msg-sent

For descriptions of these variables, see GPRS Schema Statistics in the Statistics and Counters Reference.

• EGTPC Schema:

• csfb-sent-suspendnotf• csfb-sent-retranssuspendnotf• csfb-recv-suspendnotf• csfb-recv-suspendnotfDiscard• csfb-recv-suspendnotfNorsp• csfb-recv-retranssuspendnotf• csfb-sent-suspendack• csfb-sent-suspendackaccept• csfb-sent-suspendackdenied• csfb-recv-suspendack• csfb-recv-suspendackDiscard• csfb-recv-suspendackaccept• csfb-recv-suspenddenied• csfb-sent-resumenotf• csfb-sent-retransresumenotf• csfb-sent-resumeack• csfb-sent-resumeackaccept• csfb-sent-resumeackdenied• csfb-recv-resumeack• csfb-recv-resumeackDiscard


S4-SGSN Suspend-Resume FeatureS4-SGSN Suspend and Resume Feature Bulk Statistics

• csfb-recv-resumeackaccept• csfb-recv-resumedenied

For descriptions of these variables, see EGTPC Schema Statistics in the Statistics and Counters Reference.

• SGTP Schema:

• sgtpc-sgsn-ctxt-req-v1-tx• sgtpc-sgsn-ctxt-req-v1-rx• sgtpc-sgsn-ctxt-req-accept-tx• sgtpc-sgsn-ctxt-req-accept-rx• sgtpc-sgsn-ctxt-req-accept-v1-tx• sgtpc-sgsn-ctxt-req-accept-v1-rx• sgtpc-sgsn-ctxt-req-denied-tx• sgtpc-sgsn-ctxt-req-denied-rx• sgtpc-sgsn-ctxt-ack-accept-tx• sgtpc-sgsn-ctxt-ack-accept-rx• sgtpc-sgsn-ctxt-ack-accept-v1-tx• sgtpc-sgsn-ctxt-ack-accept-v1_rx• sgtpc-sgsn-ctxt-ack-denied-tx

For descriptions of these variables, see SGTP Schema Statistics in the Statistics and Counters Reference.





S4-SGSN Suspend-Resume FeatureFeature DescriptionSuspension of GPRS ServicesRelationships to Other Features

How it WorksS4-SGSN Suspend-Resume FeatureLimitationsCall FlowsIntra-SGSN Suspend Procedure with Resume as the Subsequent ProcedureIntra-SGSN Suspend with Resume Procedure with Intra-RAU as Subsequent ProcedureInter-SGSN Suspend and Resume Procedure with Peer S4-SGSN/MMENew Inter-SGSN Suspend and Resume Procedure from BSS to 2G Gn-SGSNNew SGSN Suspend and Resume Procedure with Peer Gn-SGSN as Old SGSNInterface Selection Logic for Inter-SGSN Suspend (New SGSN) ProcedureIntra-SGSN Inter-System Suspend and Resume ProcedureInter-SGSN Inter-System Suspend and Resume Procedure

Standards Compliance

Configuring the S4-SGSN Suspend/Resume FeatureMonitoring and Troubleshooting the S4-SGSN Suspend/Resume FeatureS4-SGSN Suspend and Resume Feature Show Commandsshow subscriber gprs-only full allshow subscriber sgsn-only full allshow bssgp statistics verboseshow egtpc statisticsshow egtpc statistics verboseshow sgtpc statistics verbose

S4-SGSN Suspend and Resume Feature Bulk Statistics

s4-sgsn suspend-resume feature...username:123456789012345 accesstype:sgsn networktype:ip...

Documents