Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.060  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   5…   5.3.8…   5.4…   5.4.2…   5.4.9…   5.6…   5.6.2   5.6.3…   5.6.3.7…   5.7…   6…   6.3…   6.5…   6.6…   6.8…   6.9…   6.9.1.3   6.9.2…   6.9.2.2…   6.9.2.2.2   6.9.2.2.3…   6.9.2.2.5…   6.9.3…   6.10…   6.12…   6.13…   6.13.1.2…   6.13.2…   6.13.2.2   6.14…   8…   8.2   9…   9.2.2…   9.2.2.2   9.2.2.3…   9.2.3…   9.2.3.2…   9.2.3.3…   9.2.4…   9.2.4.2…   9.2.5…   12…   12.5…   12.6…   12.7…   12.8…   13…   14…   15…   15.3…   16…   16.2…   A…   B…

 

16.2  Circuit-switched Services (A/Gb mode)p. 342

The ability for a GPRS user to access circuit-switched services depends on the subscription held, the network capabilities, and the MS capabilities. Interaction between GPRS and circuit-switched services is described in clause "Interactions Between SGSN and MSC/VLR".

16.2.1  Suspension of GPRS Servicesp. 342

The MS shall request the network for suspension of GPRS services when the MS or the network limitations make it unable to communicate on GPRS channels in one or more of the following scenarios:
  1. When a GPRS-attached MS enters dedicated mode and the support of Class A mode of operation is not possible (e.g. the MS only supports DTM (see TS 43.064) and the network only supports independent CS and PS).
  2. During CS connection, the MS performs handover from Iu mode to A/Gb mode, and the MS or the network limitations make it unable to support CS/PS mode of operation, e.g. an MS in CS/PS mode of operation in Iu mode during a CS connection reverts to class B mode of operation in A/Gb mode.
  3. When an MS in class A mode of operation is handed over to a cell where the support of Class A mode of operation is not possible (e.g. a DTM mobile station entering a cell not supporting DTM).
Up

16.2.1.1  Suspend and Resume procedure (A/Gb mode)p. 342

In the following procedures, when a suspended MS is resumed, the MS should either deactivate the PDP context of streaming or conversational traffic class, or the MS should modify the PDP context of streaming or conversational traffic class to reset the maximum bit rate to a proper value (see clause "RNC/BSS-Initiated PDP Context Modification Procedure").
16.2.1.1.1  Intra-SGSN Suspend and Resume procedurep. 342
The Suspend and Resume procedure for intra-SGSN is illustrated in Figure 99.
Reproduction of 3GPP TS 23.060, Fig. 99: Suspend and Resume Procedure for intra SGSN
Up
Step 1.
The MS enters dedicated mode and the MS or the network limitations make it unable to support Class A mode of operation, or during CS connection, a DTM MS performs handover from a cell supporting DTM to a cell not supporting DTM.
Step 2.
The MS sends an RR Suspend (TLLI, RAI) message to the BSS. The BSS may terminate any ongoing GPRS traffic for this TLLI.
Step 3.
The BSS sends a Suspend (TLLI, RAI) message to the SGSN, and the SGSN acknowledges by returning Suspend Ack. The BSS shall store TLLI and RAI in order to be able to request the SGSN to resume GPRS services when the MS leaves dedicated mode.
Step 4.
Eventually, the BSS may determine that the conditions for the GPRS suspension have disappeared. If the BSS is able to request the SGSN to resume GPRS services, the BSS shall send a Resume (TLLI, RAI) message to the SGSN. The SGSN acknowledges the successful outcome of the resume by returning Resume Ack.
Step 5.
If the circuit switched radio channel is to be released, the BSS sends an RR Channel Release (Resume) message to the MS. The Resume message indicates whether the BSS has successfully requested the SGSN to resume GPRS services for the MS, i.e., whether Resume Ack was received in the BSS before the RR Channel Release message was transmitted. The MS leaves dedicated mode.
Step 6.
The MS shall resume GPRS services by sending a Routeing Area Update Request message to the SGSN:
  • if the BSS did not successfully request the SGSN to resume GPRS services,
  • if the RR Channel Release message was not received before the MS left dedicated mode,
  • if the MS locally determines that the conditions for the GPRS suspension have disappeared
The Update Type depends on the mode of operation of the network in use e.g. in mode I Combined RA/LA Update is made and in mode II Routeing Area Update is made.
The full handling of suspended MSs in the BSS and the SGSN is implementation dependent. Typically, the SGSN should not page suspended MSs.
If the MS performs an inter-BSC handover while suspended, the TLLI and RAI should be transferred as BSC-to-BSC information in the Handover Required and Handover Request messages, see TS 48.008. This allows the new BSC to initiate the Resume request procedure to the SGSN. If the BSC-to-BSC information was not transferred or not understood, the MS doesn't receive an indication that resumption has been successful, and the MS shall resume GPRS services by initiating a Routeing Area Update or Combined RA/LA Updating procedure as described in step 6.
Up
16.2.1.1.2  Inter-SGSN Suspend and Resume procedurep. 343
The Suspend and Resume procedure for inter-SGSN is illustrated in Figure 100.
This describes the scenario where the old cell and the new cell are handled by different SGSN's, i.e. suspend message is received in an SGSN that is different from the SGSN currently handling the packet data transmission.
Reproduction of 3GPP TS 23.060, Fig. 100: Suspend and Resume Procedure for inter-SGSN
Up
Step 1.
During CS connection, a DTM MS performs handover from a cell supporting DTM to a cell not supporting DTM.
Step 2.
The MS sends an RR Suspend (TLLI, RAI) message to the BSS.
Step 3.
The BSS sends a Suspend (TLLI, RAI) message to the SGSN.
  • Since the SGSN that receives the Suspend message is not the one currently handling the packet data transmission, an indication to perform suspend will be sent to the old SGSN by means of a SUSPEND REQUEST message on the Gn interface. The address of the old SGSN is derived by "old RAI" received in Suspend message. If the SGSN that receives the Suspend message provides functionality for Intra Domain Connection of RAN Nodes to Multiple CN Nodes, the SGSN that receives the Suspend message from the BSS may derive the old SGSN from the old RAI and the old TLLI and send the Suspend Request message to this old SGSN. Otherwise, the SGSN that receives the Suspend message from the BSS derives the old SGSN from the old RAI. In any case the SGSN that receives the Suspend message from the BSS will derive an SGSN that it believes is the old SGSN. This derived SGSN is itself the old SGSN, or it is associated with the same pool area as the actual old SGSN and it will determine the correct old SGSN from the TLLI and relay the Suspend Request message to that actual old SGSN.
  • The Old SGSN returns a SUSPEND RESPONSE.
  • The new SGSN then returns Suspend Ack to the BSS.
Step 4.
After CS connection is terminated, the BSS may send a Resume (TLLI, RAI) message to the new SGSN, but since resume is not needed against the old SGSN, the new SGSN acknowledges the resume by Resume Nack.
(Resume is not needed against the old SGSN since the MS in this case always will perform an RA Update for updating of GPRS services when the CS connection is terminated and the MM context will be moved from the old to the new SGSN.)
Step 5.
The BSS sends an RR Channel Release message to the MS, indicating that the BSS has not successfully requested the SGSN to resume GPRS services for the MS. The MS leaves dedicated mode.
Step 6.
The MS shall resume GPRS services by sending a Routeing Area Update Request message to the SGSN. The Update Type depends on the mode of operation of the network in use e.g. in mode I Combined RA/LA Update is made and in mode II Routeing Area Update is made.
Up

16.2.1.2  Inter-System Suspend and Resume procedurep. 344

16.2.1.2.1  Intra-SGSN Suspend and Resume procedurep. 344
The Suspend and Resume procedure for intra SGSN is illustrated in Figure 101.
Reproduction of 3GPP TS 23.060, Fig. 101: Suspend and Resume Procedure for intra-SGSN
Up
Step 1.
During CS connection, the MS performs handover from Iu mode to A/Gb mode and the MS or the network limitations are unable to support CS/PS mode of operation.
Step 2.
The MS sends an RR Suspend (TLLI, RAI) message to the BSS.
Step 3.
The BSS sends a Suspend (TLLI, RAI) message to the SGSN and:
  • The SGSN may request the SRNS to stop sending downlink PDU's by the SRNS Context Request message. The SRNS then starts buffering the downlink PDUs.
  • The SRNS responds with an SRNS Context Response message.
  • The SGSN then returns Suspend Ack to the BSS.
Step 4.
After CS connection is terminated, the BSS may send a Resume (TLLI, RAI) message to the SGSN, but resume is not possible since the MS has changed the radio system, so the SGSN acknowledges the resume by Resume Nack.
Step 5.
The BSS sends an RR Channel Release message to the MS, indicating that the BSS has not successfully requested the SGSN to resume GPRS services for the MS.
Step 6.
The MS shall resume GPRS services by sending a Routeing Area Update Request message to the SGSN. The Update Type depends on the mode of operation of the network in use e.g. in mode I Combined RA/LA Update is made and in mode II Routeing Area Update is made.
Up
16.2.1.2.2  Inter-SGSN Suspend and Resume procedurep. 345
The Suspend and Resume procedure for inter SGSN is illustrated in Figure 102.
This describes the scenario when the suspend message is received in an SGSN that is different from the SGSN currently handling the packet data transmission and would be valid for at least the following cases:
  • MS performs inter-system handover from Iu mode to A/Gb mode during CS connection and the SGSN handling the A/Gb mode cell is different from the SGSN handling the Iu mode cell, i.e. the 2G and 3G SGSNs are separated.
Reproduction of 3GPP TS 23.060, Fig. 102: Suspend and Resume Procedure for inter-SGSN
Up
Step 1.
During CS connection, the MS performs handover from Iu mode to A/Gb mode, and the MS or the network limitations make it unable to support CS/PS mode of operation.
Step 2.
The MS sends an RR Suspend (TLLI, RAI) message to the BSS.
Step 3.
The BSS sends a Suspend (TLLI, RAI) message to the SGSN.
  • Since the SGSN that receives the Suspend message is not the one currently handling the packet data transmission, an indication to perform suspend will be sent to the 3G SGSN by means of a SUSPEND REQUEST message on the Gn interface. The address of the old SGSN is derived by "old RAI" received in the Suspend message. If the SGSN that receives the Suspend message provides functionality for Intra Domain Connection of RAN Nodes to Multiple CN Nodes, the SGSN that receives the Suspend message from the BSS may derive the old SGSN from the old RAI and the old TLLI and send the Suspend Request message to this old SGSN. Otherwise, the SGSN that receives the Suspend message from the BSS derives the old SGSN from the old RAI. In any case the SGSN that receives the Suspend message from the BSS will derive an SGSN that it believes is the old SGSN. This derived SGSN is itself the old SGSN, or it is associated with the same pool area as the actual old SGSN and it will determine the correct old SGSN from the TLLI and relay the Suspend Request message to that actual old SGSN.
  • The 3G SGSN may request the SRNS to stop sending downlink PDU's by the SRNS Context Request message. Upon reception of the SRNS Context Request message, the SRNS starts buffering the downlink PDUs.
  • The SRNS responds with an SRNS Context Response message.
  • The 3G SGSN return a SUSPEND RESPONSE.
  • The 2G SGSN then returns Suspend Ack to the BSS.
Step 4.
After CS connection is terminated, the BSS may send a Resume (TLLI, RAI) message to the 2G SGSN, but since resume is not needed against the 3G SGSN the 2G SGSN acknowledges the resume by Resume Nack.
(Resume is not needed in this case since the MS always will perform an RA Update for updating of GPRS services when the CS connection is terminated and the MM context will be moved from 3G to 2G SGSN.)
Step 5.
The BSS sends an RR Channel Release message to the MS, indicating that the BSS has not successfully requested the SGSN to resume GPRS services for the MS.
Step 6.
The MS shall resume GPRS services by sending a Routeing Area Update Request message to the SGSN. The Update Type depends on the mode of operation of the network in use e.g. in mode I Combined RA/LA Update is made and in mode II Routeing Area Update is made.
Up

16.2.1.3  Inter System Resume procedurep. 347

The resume procedure is only applicable in case of A/Gb mode to Iu mode handover.
16.2.1.3.1  Intra-SGSN Resume procedurep. 347
The procedure for resume of GPRS traffic at intra SGSN case is illustrated in Figure 103.
Reproduction of 3GPP TS 23.060, Fig. 103: Resume of GPRS traffic at intra SGSN
Up
Step 1.
The MS in A/Gb mode class-B mode of operation during CS connection performs handover to CS/PS mode of operation in Iu mode;
or the MS in class-A mode of operation capable of DTM performs handover during CS connection from an A/Gb mode cell not supporting DTM to an Iu mode cell.
Step 2.
The MS shall resume GPRS services, directly after the CS handover is completed, by sending a Routeing Area Update Request message to the SGSN, as described in clause "Inter System Change Procedure".
Up
16.2.1.3.2  Inter-SGSN Resume procedurep. 347
The procedure for resuming GPRS traffic at inter-SGSN case is illustrated in Figure 104.
Reproduction of 3GPP TS 23.060, Fig. 104: Resume of GPRS traffic at inter SGSN
Up
Step 1.
The MS in A/Gb mode class-B mode of operation during CS connection performs a handover to CS/PS mode of operation in Iu mode;
or the MS in class-A mode of operation capable of DTM performs a handover during CS connection from an A/Gb mode cell not supporting DTM to an Iu mode cell.
The MS shall resume GPRS services, directly after the CS handover is completed, by sending a Routeing Area Update Request message to the SGSN, as described in clause "Inter System Change Procedure".
Up

16.2.2  GPRS and Dedicated Mode Priority Handlingp. 347

An MS in class B mode of operation that communicates on GPRS radio channels when a dedicated channel is needed, shall immediately abort the GPRS communication and trigger the Suspend and Resume procedure.
Response to circuit-switched paging, non-emergency Mobile-originated circuit-switched calls, Mobile-originated SMS, and Mobile-originated supplementary services are exceptions to the above rule. In these cases, it is an implementation choice whether to immediately abort GPRS communication or to delay the dedicated mode establishment.
Up

16.3  Supplementary Servicesp. 347

For SMS over GPRS, only the invocation of Call Barring Supplementary Service is supported. The user control by using the Supplementary Service protocol is not supported over GPRS.
Other supplementary services are not defined for GPRS. Supplementary services may be available in the interworked packet data networks, but this is outside the scope of this specification.

16.4  CAMEL Servicesp. 348

CAMEL may be used for session and cost control. It may also be used for other operator-specific services. Subscription data received over Gr, as described in TS 23.078, enables CAMEL interactions. In this Release of the specification CAMEL Services are not applicable to subscriptions without MSISDN as existing messages have unresolved MSISDN references.
Up

Up   Top   ToC