hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.1.3.4 Paging response for CS fallback | The network may initiate the paging procedure for CS services when the MS is IMSI attached for CS services via EMM combined procedures, as described in 3GPP TS 24.301 [120].
At reception of an indication of paging for CS services from EMM, the MS shall stop timer T3246, if it is running. The MM sublayer in the MS reque... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.1.4 Abnormal cases | The behaviour upon abnormal events is described together with the relevant RR procedure or MM common procedure.
In addition, the following abnormal events can be identified:
a) Indication that a CS fallback to GERAN or UTRAN has failed
If EMM indicates that the CS fallback to GERAN or UTRAN failed, the MM sublayer shal... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.1.5 MM connection establishment for emergency calls | A MM connection for an emergency call may be established in all states of the mobility management sublayer which allow MM connection establishment for a normal originating call. In addition, establishment may be attempted in all service states where a cell is selected (see subclause 4.2.2) but not in the MM CONNECTION ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.1.6 Call re-establishment | The re-establishment procedure allows a MS to resume a connection in progress after a radio link failure, possibly in a new cell and possibly in a new location area. The conditions in which to attempt call re-establishment or not depend on the call control state, see subclause 5.5.4 and, whether or not a cell allowing ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.1.6.1 Call re-establishment, initiation by the mobile station | NOTE: The network is unable to initiate call re-establishment.
If at least one request to re-establish an MM connection is received from a CM entity as a response to the indication that the MM connection is interrupted (see subclause 4.5.2.3.) the mobile station initiates the call re-establishment procedure. If several... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.1.6.2 Abnormal cases | Mobile station side:
a) Random access failure or RR connection establishment failure
If the mobile station detects a random access failure or RR connection establishment failure during the re-establishment of an MM connection, the re-establishment is aborted and all MM connections are released.
b) RR connection failure... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.1.7 Forced release during MO MM connection establishment | If the mobile station's CM layer initiated the MM connection establishment but the CM layer wishes to abort the establishment prior to the completion of the establishment phase, the mobile station shall send a CM SERVICE ABORT message any time after the completion of the RR connection and not after the first CM message... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.1.8 MM connection establishment due to SRVCC or vSRVCC handover | An MM connection can be established locally in the MS due to an SRVCC or vSRVCC handover (see 3GPP TS 23.216 [126]), i.e. without dedicated MM signalling. That is the case when the MS has:
- a voice media stream carried over the PS domain that is handed over to the CS domain in A/Gb mode or Iu mode via SRVCC;
- a voice... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.1.9 MM connection establishment due to Dual Radio Voice Call Continuity (DRVCC) access transfer | The MM Connection establishment procedures for a dual radio voice call continuity (DRVCC) access transfer follow the procedures described in subclause 4.5.1.1 with the following additions:
Upon request from the upper layers to set up a DRVCC call, the MS shall initiate the MM connection establishment and send a CM SERV... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.2 MM connection information transfer phase | After the MM connection has been established, it can be used by the CM sublayer entity for information transfer. According to the protocol architecture described in 3GPP TS 24.007 [20], each CM entity will have its own MM connection. These different MM connections are identified by the protocol discriminator PD and, ad... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.2.1 Sending CM messages | A CM sublayer entity, after having been advised that a MM connection has been established, can request the transfer of CM messages. The CM messages passed to the MM sublayer are then sent to the other side of the interface with the PD and TI set according to the source entity. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.2.2 Receiving CM messages | Upon receiving a CM message, the MM sublayer will distribute it to the relevant CM entity according to the PD value and TI value. However, if the received CM message is the first for the MM connection (identified by PD and TI), the MM sublayer will in addition indicate to the CM entity that a new MM connection has been... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.2.3 Abnormal cases | RR connection failure:
If the RR connection failure occurs during a RR or MM common procedure, the consequent actions are described together with that procedure.
In other cases, the following applies:
- Mobile station:
The MM sublayer shall indicate to all CM entities associated with active MM connections that the MM c... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.3 MM connection release | An established MM connection can be released by the local CM entity. The release of the CM connection will then be done locally in the MM sublayer, i.e. no MM message are sent over the radio interface for this purpose. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.3.1 Release of associated RR connection | If all MM connections are released by their CM entities, and no RRLP procedure (see 3GPP TS 44.031 [23b]) and no LCS procedure over RRC (see 3GPP TS 25.331 [23c]) is ongoing, the mobile station shall set timer T3240 and enter the state WAIT FOR NETWORK COMMAND, expecting the release of the RR connection.
If all MM conn... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.5.3.2 Uplink release in a voice group call | (Only applicable for mobile stations supporting VGCS talking:)
If a mobile station which is in the MM sublayer state MM CONNECTION ACTIVE (GROUP TRANSMIT MODE) receives a request from the GCC sublayer to perform an uplink release, the MM sublayer requests the RR sublayer to perform an uplink release procedure and enter... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.6 Receiving a MM STATUS message by a MM entity. | If the MM entity of the mobile station receives a MM STATUS message no state transition and no specific action shall be taken as seen from the radio interface, i.e. local actions are possible.
With the exceptions described for the responses to the CM SERVICE PROMPT message, the actions to be taken on receiving a MM STA... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7 Elementary mobility management procedures for GPRS services | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1 General | This subclause describes the basic functions offered by the mobility management (GMM) sublayer at the radio interface (reference point Um/UU). The functionality is described in terms of timers and procedures. During GMM procedures, procedures of CM layer services via the PS domain, e.g. SM, SMS, and SS, are suspended. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.1 Lower layer failure | The lower layers shall indicate a logical link failure or an RR sublayer failure or an RRC sublayer failure to the GMM sublayer. The failure indicates an error that cannot be corrected by the lower layers. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.2 Ciphering of messages (A/Gb mode only) | If ciphering is to be applied on a GMM context, all GMM messages shall be ciphered except the following messages:
-- ATTACH REQUEST;
-- ATTACH REJECT;
-- AUTHENTICATION AND CIPHERING REQUEST;
-- AUTHENTICATION AND CIPHERING RESPONSE;
-- AUTHENTICATION AND CIPHERING FAILURE;
-- AUTHENTICATION AND CIPHERING REJECT;
-- ID... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.3 P-TMSI signature | The network may assign a P-TMSI signature to an MS in an attach, routing area update, or P-TMSI reallocation procedure. Only in combination with a valid P-TMSI, this P-TMSI signature is used by the MS for authentication and identification purposes in the subsequent attach, routing area update or detach procedure. If th... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.4 Radio resource sublayer address handling | In A/Gb mode, while a packet TMSI (P-TMSI) is used in the GMM sublayer for identification of an MS, a temporary logical link identity (TLLI) is used for addressing purposes at the RR sublayer.
In Iu mode a Radio Network Temporary Identity (RNTI) identifies a user between the MS and the UTRAN or GERAN. The relationship ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.4.1 Radio resource sublayer address handling (A/Gb mode only) | This subclause describes how the RR addressing is managed by GMM. For the detailed coding of the different TLLI types and how a TLLI can be derived from a P-TMSI, see 3GPP TS 23.003 [10].
If the MS is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368 [135] or 3GPP TS 31.102 [112] and is entering a new PLMN... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.5 P-TMSI handling | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.5.1 P-TMSI handling in A/Gb mode | If a new P-TMSI is assigned by the network the MS and the network shall handle the old and the new P-TMSI as follows:
Upon receipt of a GMM message containing a new P-TMSI the MS shall consider the new P-TMSI and new RAI and also the old P-TMSI and old RAI as valid in order to react to paging requests and downlink tran... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.5.2 P-TMSI handling in Iu mode | If a new P-TMSI is assigned by the network the MS and the network shall handle the old and the new P-TMSI as follows:
Upon receipt of a GMM message containing a new P-TMSI the MS shall consider the new P-TMSI and new RAI as valid. Old P-TMSI and old RAI are regarded as invalid.
The network shall consider the old P-TMSI... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.5.3 Void | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.5.4 Void | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.6 Change of network mode of operation | In the following tables below the abbreviations 'A/Gb mode I' and 'A/Gb mode II' are used for network operation mode I and II in A/Gb mode.
In the following tables below the abbreviations 'Iu mode I' and 'Iu mode II' are used for network operation modes I and II in Iu mode. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.6.1 Change of network mode of operation in A/Gb mode (A/Gb mode only) | Whenever an MS moves to a new RA, the procedures executed by the MS depend on the network mode of operation in the old and new routing area.
In case the MS is in state GMM REGISTERED or GMM ROUTING AREA UPDATING INITIATED and is in operation mode A or B, the MS shall execute according to table 4.7.1.6.1-1:
Table 4.7.1.... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.6.2 Change of network mode of operation in Iu mode (Iu mode only) | Whenever an MS moves to a new RA, the procedures executed by the MS depend on the network mode of operation in the old and new routing area.
In case the MS is in state GMM-REGISTERED or GMM-ROUTING-AREA-UPDATING-INITIATED and is in operation mode A, the MS shall execute:
Table 4.7.1.6.4/3GPP TS 24.008: Mode A
Network o... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.6.3 Change of network mode of operation at Iu mode to A/Gb mode inter-system change | Whenever an MS moves to a new RA supporting the A/Gb mode radio interface, the procedures executed by the MS depend on the network mode of operation in the old and new routing area.
In case the MS is in state GMM-REGISTERED or GMM-ROUTING-AREA-UPDATING-INITIATED and is in operation mode:
a) A in Iu mode, an MS that cha... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.6.4 Change of network mode of operation at A/Gb mode to Iu mode inter-system change | Whenever an MS moves to a new RA supporting the Iu mode radio interface, the procedures executed by the MS depend on the network mode of operation in the old and new routing area.
In case the MS is in state GMM-REGISTERED or GMM-ROUTING-AREA-UPDATING-INITIATED and is in operation mode:
a) A or B in A/Gb mode, the MS sh... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.7 Intersystem change between A/Gb mode and Iu mode | For the Iu mode to A/Gb mode and A/Gb mode to Iu mode intersystem change the following cases can be distinguished:
a) Intersystem change between cells belonging to different RA's:
The procedures executed by the MS depends on the network mode of operation in the old and new RA. If a change of the network operation mode ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.8 List of forbidden PLMNs for GPRS service | The Mobile Equipment shall contain a list of "forbidden PLMNs for GPRS service". This lists shall be erased when the MS is switched off or when the SIM/USIM is removed or upon the expiry of the timer T3245 as described in subclause 4.1.1.6. The PLMN identification received on the BCCH shall be added to the list wheneve... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.9 Release of the PS signalling connection (Iu mode only) | In Iu mode, to allow the network to release the PS signalling connection (see 3GPP TS 25.331 [23c] and 3GPP TS 44.118 [111]) the MS:
a) shall start the timer T3340 if the MS receives any of the reject cause values #11, #12, #13, #15 or #25;
b) shall start the timer T3340 if the network indicates "no follow-on proceed" ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.1.10 Handling of 3GPP PS data off | An MS, which supports 3GPP PS data off (see 3GPP TS 23.060 [74]), can be configured with up to two lists of 3GPP PS data off exempt services as specified in 3GPP TS 24.368 [135] or in the EF3GPPPSDATAOFF USIM file as specified in 3GPP TS 31.102 [112]:
- a list of 3GPP PS data off exempt services to be used in the HPLMN... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2 GPRS Mobility management timers and UMTS PS signalling connection control | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.1 READY timer behaviour | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.1.1 READY timer behaviour (A/Gb mode only) | The READY timer, T3314 is used in the MS and in the network per each assigned P-TMSI to control the cell updating procedure.
When the READY timer is running or has been deactivated the MS shall perform cell update each time a new cell is selected (see 3GPP TS 43.022 [82]). If a routing area border is crossed, a routing... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.1.2 Handling of READY timer in the MS in Iu mode and S1 mode | The READY timer is not applicable for Iu mode in S1 mode.
Upon completion of a successful GPRS attach or routing area updating procedure in Iu mode, the MS shall stop the READY timer, if running.
Upon completion of a successful EPS attach or tracking area updating procedure, the MS shall stop the READY timer, if runnin... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.2 Periodic routing area updating | The periodic routing area updating procedure is used to periodically notify the availability of the MS to the network. The procedure is controlled in the MS by timer T3312. The value of timer T3312 is sent by the network to the MS in the messages ATTACH ACCEPT and ROUTING AREA UPDATE ACCEPT. The value of timer T3312 sh... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.3 PMM-IDLE mode and PMM-CONNECTED mode (Iu mode only) | An MS shall enter PMM-CONNECTED mode when a PS signalling connection for packet switched domain is established between the MS and the network. The MS shall not perform periodic routing area update in PMM-CONNECTED mode.
An MS shall enter PMM-IDLE mode when the PS signalling connection for packet switched domain between... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.4 Handling of Force to standby in Iu mode (Iu mode only) | Force to standby is not applicable for Iu mode.
The network shall always indicate Force to standby not indicated in the Force to standby information element.
The Force to standby information element shall be ignored by the MS. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.5 RA Update procedure for Signalling Connection Re-establishment (Iu mode only) | When the MS receives an indication from the lower layers that the RRC connection has been released with cause "Directed signalling connection re-establishment", see 3GPP TS 25.331 [23c] and 3GPP TS 44.118 [111], then the MS shall enter PMM-IDLE mode and initiate immediately a normal routing area update procedure (the u... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.6 Cell Update triggered by low layers | A Cell Update may be requested by the low layers, see 3GPP TS 44.060 [76]. In this case the Cell Update shall be performed even if the READY timer is not running. If both the network and the MS support the Cell Notification, then the MS shall use the LLC NULL frame to perform the Cell Update. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.7 Handling of timer T3302 | The value of timer T3302 can be sent by the network to the MS in the ATTACH ACCEPT message, ROUTING AREA UPDATE ACCEPT message, ATTACH REJECT message, and ROUTING AREA UPDATE REJECT message. The MS shall apply this value, if the value is different from "deactivated" in the routing area registered by the MS, until a new... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.8 Handling of timer T3324 (A/Gb mode, Iu mode and S1 mode) | An MS supporting PSM may request the network to assign a value for T3324 by including a requested timer value in:
- the ATTACH REQUEST or ROUTING AREA UPDATE REQUEST message (in A/Gb mode and Iu mode ); or
- the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message (in S1 mode).
The value of timer T3324 can be sent by... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.9 Power saving mode | The MS can request the use of power saving mode (PSM) during an attach or routing area updating procedures (see 3GPP TS 23.682 [133A] and 3GPP TS 23.060 [74]). The MS shall not request the use of PSM during:
- an attach for emergency bearer services procedure;
- a routing area updating procedure for initiating a PDN co... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.10 Extended idle-mode DRX cycle | The MS can request the use of extended idle mode DRX cycle (eDRX) during an attach or routing area updating procedure by including the extended DRX parameters IE (see 3GPP TS 23.682 [11A] and 3GPP TS 23.060 [74]). The MS shall not request the use of eDRX during:
- an attach for emergency bearer services procedure; or
-... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.11 Interaction between power saving mode and extended idle mode DRX cycle | The MS can request the use of both PSM and eDRX during an attach or routing area update procedure but it is up to the network to decide to enable none, one of them or both (see 3GPP TS 23.682 [133A] and 3GPP TS 23.060 [74]).
If the network accepts the use of both PSM (see subclause 4.7.2.9) and eDRX (see subclause 4.7.... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.2.12 Extended coverage for GSM | The MS can support and use the extended coverage in GSM for IoT (EC-GSM-IoT) feature (see 3GPP TS 43.064 [159]). A GPRS MS using EC-GSM-IoT may operate in MS operation mode C only. If the MS uses one of the four coverage classes of EC-GSM-IoT as defined in 3GPP TS 43.064 [159], the MS shall calculate the value of the a... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3 GPRS attach procedure | The GPRS attach procedure is used for the following purposes:
- normal GPRS attach, performed by the MS to IMSI attach for GPRS services only. The normal GPRS attach procedure shall be used:
- by GPRS MSs in MS operation mode C, independent of the network operation mode;
- by GPRS MSs in MS operation modes A or B if th... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.1 GPRS attach procedure for GPRS services | The GPRS attach procedure is a GMM procedure used by GPRS MSs to IMSI attach for GPRS services. The procedure is also used by GPRS MSs to IMSI or IMEI attach for emergency bearer services.
The attach type information element shall indicate "GPRS attach". For an MS attaching for emergency bearer services the attach type... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.1.1 GPRS attach procedure initiation | In state GMM-DEREGISTERED, the MS initiates the GPRS attach procedure by sending an ATTACH REQUEST message to the network, starts timer T3310 and enters state GMM-REGISTERED-INITIATED. If timer T3302 is currently running, the MS shall stop timer T3302. If timer T3311 is currently running, the MS shall stop timer T3311.... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.1.2 GMM common procedure initiation | If the network receives an ATTACH REQUEST message containing the P-TMSI type IE and the Mobile identity IE with type of identity indicating "TMSI/P-TMSI/M-TMSI", and the network does not follow the use of the most significant bit of the LAC as specified in 3GPP TS 23.003 [10] subclause 2.8.2.2.2, the network shall use ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.1.3 GPRS attach accepted by the network | During an attach for emergency bearer services, if not restricted by local regulations, the network shall not check for mobility and access restrictions, regional restrictions, subscription restrictions, or perform CSG access control when processing the ATTACH REQUEST message. The network shall not apply subscribed APN... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.1.4 GPRS attach not accepted by the network | If the attach request cannot be accepted by the network, an ATTACH REJECT message is transferred to the MS. The MS receiving the ATTACH REJECT message containing a reject cause other than GMM cause value #25 or the message is integrity protected, shall stop the timer T3310 and for all causes except #7, #12, #14, #15, #... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.1.5 Abnormal cases in the MS | The following abnormal cases can be identified:
a) Access barred because of access class control, EAB or ACDC
The GPRS attach procedure shall not be started. The MS stays in the current serving cell and applies normal cell reselection process. The GPRS attach procedure is started as soon as possible, i.e. when access i... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.1.6 Abnormal cases on the network side | The following abnormal cases can be identified:
a) Lower layer failure
If a low layer failure occurs before the message ATTACH COMPLETE has been received from the MS and a new P-TMSI (or a new P-TMSI and a new P-TMSI signature) has been assigned, the network shall consider both the old and new P-TMSI each with its corr... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.2 Combined GPRS attach procedure for GPRS and non-GPRS services | The combined GPRS attach procedure is a GMM procedure used by a GPRS MS operating in MS operation modes A or B for IMSI attach for GPRS and non-GPRS services if the network operates in network operation mode I.
If a GPRS MS operating in MS operation modes A or B is already attached for non-GPRS services by use of the M... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.2.1 Combined GPRS attach procedure initiation | If the MS is in GMM state GMM-DEREGISTERED and in MM state MM IDLE, the MS initiates the combined GPRS attach procedure by sending an ATTACH REQUEST message to the network, starts timer T3310 and enters state GMM-REGISTERED-INITIATED and MM LOCATION UPDATING PENDING. If timer T3302 is currently running, the MS shall st... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.2.2 GMM Common procedure initiation | The network may initiate GMM common procedures, e.g. the GMM identification and GMM authentication and ciphering procedure, depending on the received information such as IMSI, CKSN, old RAI, P-TMSI and P-TMSI signature. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.2.3 Combined GPRS attach accepted by the network | Depending on the value of the attach result IE received in the ATTACH ACCEPT message, two different cases can be distinguished:
Case 1) The attach result IE value indicates "combined GPRS attach": IMSI attach for GPRS and non-GPRS services have been successful.
Case 2) The attach result IE value indicates "GPRS only": ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.2.4 Combined GPRS attach not accepted by the network | If the attach request can neither be accepted by the network for GPRS nor for non-GPRS services, an ATTACH REJECT message is transferred to the MS. The MS receiving the ATTACH REJECT message containing a reject cause other than GMM cause value #25 or the message is integrity protected, shall stop the timer T3310, and f... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.2.5 Abnormal cases in the MS | The MS shall proceed as follows:
1) If the combined attach was successful for GPRS services only and the ATTACH ACCEPT message contained a cause value not treated in subclause 4.7.3.2.3.2 or the GMM Cause IE is not included in the message, the MS shall proceed as follows:
a) The MS shall stop timer T3310 if still runni... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.3.2.6 Abnormal cases on the network side | The abnormal cases specified in subclause 4.7.3.1.6 apply. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4 GPRS detach procedure | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4.0 General | The GPRS detach procedure is used:
- to detach the IMSI for GPRS services only. Independent of the network operation mode, this procedure is used by all kind of GPRS MSs;
- as a combined GPRS detach procedure used by GPRS MSs operating in MS operation mode A or B to detach the IMSI for GPRS and non-GPRS services or for... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4.1 MS initiated GPRS detach procedure | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4.1.1 MS initiated GPRS detach procedure initiation | The GPRS detach procedure is initiated by the MS by sending a DETACH REQUEST message. The detach type information element may indicate "GPRS detach with switching off", "GPRS detach without switching off", "IMSI detach", "GPRS/IMSI detach with switching off" or "GPRS/IMSI detach without switching off".
If the MS has a ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4.1.2 MS initiated GPRS detach procedure completion for GPRS services only | When the DETACH REQUEST message is received by the network, the network shall send a DETACH ACCEPT message to the MS, if the detach type IE value indicates that the detach request has not been sent due to switching off. If switching off was indicated, the procedure is completed when the network receives the DETACH REQU... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4.1.3 MS initiated combined GPRS detach procedure completion | When the DETACH REQUEST message is received by the network, a DETACH ACCEPT message shall be sent to the MS, if the detach type IE value indicates that the detach request has not been sent due to switching off. Depending on the value of the detach type IE the following applies:
GPRS/IMSI detach:
The MS is marked as ina... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4.1.4 Abnormal cases in the MS | The following abnormal cases can be identified:
a) T3321 time-out
On the first expiry of the timer, the MS shall retransmit the DETACH REQUEST message and shall reset and restart timer T3321. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3321, the GPRS detach procedure shall be aborted,... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4.1.5 Abnormal cases on the network side | The following abnormal cases can be identified:
a) Detach request received in a CSG cell for which the MS has no valid CSG subscription
If the MS initiates a detach procedure in a CSG cell the CSG ID of which is not valid for the MS and the detach procedure is not due to "switch off", the network shall proceed as follo... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4.2 Network initiated GPRS detach procedure | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4.2.1 Network initiated GPRS detach procedure initiation | The network initiates the GPRS detach procedure by sending a DETACH REQUEST message to the MS. The DETACH REQUEST message shall include a detach type IE. In addition, the network may include a cause IE to specify the reason for the detach request. The network shall start timer T3322. If the detach type IE indicates "re... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4.2.2 Network initiated GPRS detach procedure completion by the MS | When receiving the DETACH REQUEST message and the detach type indicates "re-attach required", the MS shall deactivate the PDP context(s), the MBMS context(s) and deactivate the logical link(s), if any. The MS shall stop the timer T3346, if it is running. The MS shall also stop timer(s) T3396, if it is running. The MS s... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4.2.3 Network initiated GPRS detach procedure completion by the network | The network shall, upon receipt of the DETACH ACCEPT message, stop timer T3322. If the detach type IE included in the DETACH REQUEST message indicates "IMSI detach", or "re-attach not required" and the cause code is #2 "IMSI unknown in HLR", the network shall not change the current GMM state; otherwise the network shal... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.4.2.4 Abnormal cases on the network side | The following abnormal cases can be identified:
a) T3322 time-out
On the first expiry of the timer, the network shall retransmit the DETACH REQUEST message and shall start timer T3322. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3322, the GPRS detach procedure shall be aborted. If the... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5 Routing area updating procedure | This procedure is used for:
- normal routing area updating to update the registration of the actual routing area of an MS in the network. This procedure is used by GPRS MSs in MS operation mode C and by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS and non-GPRS services if the network operates i... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.1 Normal and periodic routing area updating procedure | Periodic routing area updating is used to periodically notify the availability of the MS to the network. The value of the update type IE in the ROUTING AREA UPDATE REQUEST message shall indicate "periodic updating". The procedure is controlled in the MS by timer T3312. When timer T3312 expires, the periodic routing are... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.1.1 Normal and periodic routing area updating procedure initiation | To initiate the normal routing area updating procedure, the MS sends the message ROUTING AREA UPDATE REQUEST to the network, starts timer T3330 and changes to state GMM-ROUTING-AREA-UPDATING-INITIATED. If timer T3302 is currently running, the MS shall stop timer T3302. If timer T3311 is currently running, the MS shall ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.1.2 GMM Common procedure initiation | If the network receives a ROUTING AREA UPDATE REQUEST message containing the P-TMSI type IE, and the network does not follow the use of the most significant bit of the <LAC> to distinguish the node type as specified in 3GPP TS 23.003 [10] subclause 2.8.2.2.2, the network shall use the P-TMSI type IE to determine whethe... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.1.3 Normal and periodic routing area updating procedure accepted by the network | If the routing area updating request has been accepted by the network, a ROUTING AREA UPDATE ACCEPT message shall be sent to the MS. The network may assign a new P-TMSI and/or a new P-TMSI signature for the MS. If a new P-TMSI and/or P-TMSI signature have been assigned to the MS, it/they shall be included in the ROUTIN... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.1.4 Normal and periodic routing area updating procedure not accepted by the network | If the routing area updating cannot be accepted, the network sends a ROUTING AREA UPDATE REJECT message to the MS. An MS, which receives a ROUTING AREA UPDATE REJECT message with a reject cause other than GMM cause value #25 or the message is integrity protected, shall stop the timer T3330. If a ROUTING AREA UPDATE REJ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.1.5 Abnormal cases in the MS | The following abnormal cases can be identified:
a) Access barred because of access class control, EAB or ACDC
If the routing area updating procedure is started in response to a paging request from the network, access class barring, EAB or ACDC is not applicable.
The routing area updating procedure shall not be started.... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.1.6 Abnormal cases on the network side | The following abnormal cases can be identified:
a) If a lower layer failure occurs before the message ROUTING AREA UPDATE COMPLETE has been received from the MS and a P-TMSI and/or PTMSI signature has been assigned, the network shall abort the procedure and shall consider both, the old and new P-TMSI and the correspond... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.2 Combined routing area updating procedure | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.2.0 General | Within a combined routing area updating procedure the messages ROUTING AREA UPDATE ACCEPT and ROUTING AREA UPDATE COMPLETE carry information for the routing area updating and the location area updating. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.2.1 Combined routing area updating procedure initiation | The combined routing area updating procedure is initiated only by a GPRS MS operating in MS operation modes A or B, if the MS is in state GMM-REGISTERED and MM-IDLE, and if the network operates in network operation mode I:
- when a GPRS MS that is IMSI attached for GPRS and non-GPRS services detects a change of the rou... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.2.2 GMM Common procedure initiation | The network may initiate GMM common procedures, e.g. the GMM authentication and ciphering procedure. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.2.3 Combined routing area updating procedure accepted by the network | Depending on the value of the update result IE received in the ROUTING AREA UPDATE ACCEPT message, two different cases can be distinguished:
Case 1) The update result IE value indicates "combined RA/LA": Routing and location area updating is successful;
Case 2) The update result IE value indicates "RA only": Routing ar... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.2.4 Combined routing area updating not accepted by the network | If the combined routing area updating cannot be accepted, the network sends a ROUTING AREA UPDATE REJECT message to the MS. An MS that receives a ROUTING AREA UPDATE REJECT message containing a reject cause other than GMM cause value #25 or the message is integrity protected, shall stop the timer T3330, and shall enter... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.2.5 Abnormal cases in the MS | The MS shall proceed as follows:
1) If the combined routing area update was successful for GPRS services only and the ROUTING AREA UPDATE ACCEPT message contained a cause value not treated in subclause 4.7.5.2.3.2 or the GMM Cause IE is not included in the message, the MS shall proceed as follows:
a) The MS shall stop ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.5.2.6 Abnormal cases on the network side | The abnormal cases specified in subclause 4.7.5.1.6 apply. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.6 P-TMSI reallocation procedure | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.6.0 General | A temporary mobile station identity for GPRS services, the Packet-TMSI (P-TMSI), is used for identification within the radio interface signalling procedures. The structure of the P-TMSI is specified in 3GPP TS 23.003 [10]. The P-TMSI has significance only within a routing area. Outside the routing area the P-TMSI has t... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.7.6.1 P-TMSI reallocation initiation by the network | The network shall initiate the P-TMSI reallocation procedure by sending a P-TMSI REALLOCATION COMMAND message to the MS and shall start the timer T3350.
The P-TMSI REALLOCATION COMMAND message shall contain a new combination of P-TMSI, RAI and optionally a P-TMSI signature or a DCN-ID or both allocated by the network.
... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.