Vous êtes sur la page 1sur 16

Protocol Control

Last updated: January 18, 2010

The protocol stack configuration options provide you with control over the content
and execution of events in the protocol stack. These are organized by protocol layer.
The parameters listed under the following protocol layers are accessed on the front
panel by selecting the layer that contains the parameter in the Prot Control menu. For
instructions on how to access the protocol layers, see How to access Protocol Control .

Layer 1
 Downlink Corruption
 EGPRS Demodulation Type
 Test Mode Burst Timing Error Measurement
 Uplink Timing Delay

RLC/MAC
 MAC Control
 Handover Control
 Block Polling Parameters
 Temporary Block Flow (TBF) Parameters
 Retransmission MCS Switching
 Window Size
 Control Channel Setup

LLC
 BLER Frame Check Sequence
 Payload Patterns

MM/GMM
 Attach Accept
 Attach Reject
 Detach Request
 Equivalent PLMN List
 Identity Request
 Location Area Update Rejection
 Routing Area Update Rejection
 Security Information
 Detach Type Information Element
 GMM Cause Information Element

SM
 Activate PDP Context Reject
 Network Initiated PDP Context
 SM Cause Information Element

Call Control
 Alerting Duration
 Call Release State
 Emergency Service Category Value

SNDCP
 Robust Header Compression

LAPDm
 LAPDm Fill Bits

Attach Accept
The parameters associated with the Attach Accept event allow you to configure the
test set to simulate a network allowing only GPRS services. This means you can
expect an IMSI attach for both GPRS and non-GPRS services to be rejected. You may
also choose which cause value is sent to the MS in the GMM cause information
element ( GMM Cause Information Element ) with the Attach Reject message. Use
this function in parallel with protocol logging ( Protocol Logging ) to verify that the
MS behaves in a manner conforming to the standards for this situation and for each
associated GMM cause value.

The MS only sends an Attach Request in the "Idle" state. Therefore, the connection
status must be "Idle" before the Attach Accept event can be used.

Attach Reject
You may configure the test set to simulate a network rejection of any Attach Attempt.
You may choose from a variety of cause values to be sent in the GMM cause
information element ( GMM Cause Information Element ) with the attach reject
message. Use this function in parallel with protocol logging ( Protocol Logging ) to
verify that the MS behaves in a manner conforming to the standards for this situation
and for each associated GMM cause value.

The MS only sends an Attach Request in the "Idle" state. Therefore, the connection
status must be "Idle" before the Attach Accept event can be used.

Detach Request
You can initiate the Detach Request event from the test set anytime the data
connection state is "Attached". In addition, a Detach Request can also occur when the
data connection state is either "Transferring" or "PDP Active". This allows you to
observe how the mobile station responds to a detach request from a network and
determines if it complies with mobile performance specifications of 3GPP TS 04.08
Version 7.9.1. The command to send a detach request
is CALL:PPRocedure:DETach:REQuest[:IMMediate] .

There are two configurable parameters that you can set before sending a detach
request.

 GMM Cause Information Element

You can choose which cause value is sent to the mobile station in the GMM
Cause Information Element with the Detach Request.

The command to set the GMM Cause Information Elements


is CALL:PPRocedure:DETach:REQuest:GMMCause .

Note: The front panel allows you to select Custom Value as the GMM Cause
Information Element in addition to the GMM Cause Information Element
settings defined in 3GPP TS 24.008 Version 6.7.0 Section 10.5.5.14.
The Custom Value is set with the above command and is not configurable via
the front panel.

 Detach Type Information Element

You can also choose which type of detach message the test set sends the mobile
station in the Detach Type Information Element as defined in 3GPP TS 24.008
Version 6.7.0 Section 10.5.5.5.
The command to set the Detach Type Information Element
is CALL:PPRocedure:DETach:REQuest:TYPE .

Use these parameters in parallel with Protocol Logging to verify that the mobile
station behaves in a manner conforming to the standards 3GPP TS 04.08 Version
7.9.1 Section 4.7.4.2 for this situation and for each associated GMM cause value.

Identity Request
A GPRS MS has four identity values (types). These values are displayed in the
Identity Request Summary screen, in the following order:

 IMSI - International Mobile Subscriber Identity


 IMEI- International Mobile Station Equipment
 IMEISV - IMEI and the Software Version number
 TMSI - Temporary Mobile Subscriber Identity

The Identity Request Summary screen is accessed by pressing the GMM/MM ( F4 )


from the Prot Control menu (see How to access Protocol Control for instructions on
how to get to the Prot Control menu), then pressing Identity Request ( F4 ) in
the Identity Req menu. The test set displays the DUT Reported Identity that is in the
indicated by the Identity Type parameter (which can be set to any of the identity
types listed above. The default Identity Type is IMSI .

NOTE
The test set always displays a zero for the 15th digit of the IMEI. This behavior
conforms to 3GPP TS 03.03, which requires that the 15th digit (referred to as Spare
digit or Check Digit) "shall be zero, when transmitted by the MS", and 3GPP TS
02.16 which states that the "check digit is not part of the digits transmitted at IMEI
check equations".

Lab application only:

You can send a request for any one of these four identities from the test set (by
selecting the Identity Type ( F2 ), then pressing Send Identity Request ( F1 ) ) to
verify that the MS supplies the appropriate value for the identity requested. Use this
function in parallel with protocol logging ( Protocol Logging ) to verify that the MS
behaves in a manner conforming to the standards for this situation.
Additionally, you can control whether the Identity Request messages get the IMEI
during call setup by configuring the Get IMEI at Call Setup parameter. This
parameter is located in the Identity Request Setup ( F3 ) menu, which is accessed
from the Identity Req menu. The GPIB command for this parameter
is CALL:IMEI:AUTO .

The data connection state can be either "Attached" or "PDP Active" when an Identity
Request message is sent to the MS.

NOTE
The Get IMEI at Call Setup parameter is located in the Cell Parameters menu for the
E6701D lab application and the E1968A test application.

The GPIB commands associated with Identity Request are located


at CALL:PPRocedure:IDENtity .

Location Area Update Rejection


You can configure the test set to reject the Location Area Update (LAU) request from
the mobile station. This allows you to observe how the mobile station responds to
LAU Rejection from a network and determine if it complies with mobile performance
specifications of 3GPP TS 24.008 Version 6.13.0.

There are two configurable parameters that you can set before sending a LAU
Rejection.

 Location Area Update Reject State

When the Location Area Update Reject State is set to ON, the test set will
reject the LAU request from the mobile station.

The command to set the Location Area Update Reject State


is CALL:PPRocedure:LAU|LAUPdate:REJect[:STATe] .

 Location Area Update Reject Cause

You can choose which cause value is sent to the mobile station in the Location
Area Update Reject message. the reject cause can be either of the followings:
o 00000010 (#2) - IMSI Unknown
o 00000011 (#3) - Illegal MS
o 00000100 (#4) - IMSI Unknown IN VLR
o 00000101 (#5) - IMEI Not Accepted
o 00000110 (#6) - Illegal MS
o 00000111 (#7) - GPRS Services Not Allowed
o 00001000 (#8) - GPRS Services and Non-GPRS Services Not Allowed
o 00001001 (#9) - MS Identity Cannot Be Derived By the Network
o 00001010 (#10) - Implicitly Detached
o 00001011 (#11) - PLMN not allowed
o 00001100 (#12) - Location Area not allowed
o 00001101 (#13) - Roaming not allowed in LA
o 00001110 (#14) - GPRS Services Not Allowed In This PLMN
o 00001111 (#15) - No suitable cells in LA
o 00010000 (#16) - MSC Temporarily Not Reachable
o 00010001 (#17) - Network Failure
o 00010100 (#20) - MAC Failure
o 00010101 (#21) - Synch Failure
o 00010110 (#22) - Congestion
o 00010111 (#23) - GSM Authentication Unacceptable
o 00100000 (#32) - Service Option Not Supported
o 00100001 (#33) - Requested Service Option Not Subscribed
o 00100010 (#34) - Service Option Temporarily Out of Order
o 00100110 (#38) - Call Cannot Be Identified
o 00101000 (#40) - No PDP Context Activated
o 00110000 (#48) - Retry Upon Entry Into a New Call
o 01011111 (#95) - Semantically Incorrect Message
o 01100000 (#96) - Invalid Mandatory Information
o 01100001 (#97) - Message Type Non-Existent or Not Implemented
o 01100010 (#98) - Message Type Not Compatible With the Protocol State
o 01100011 (#99) - Information Element Non-Existent or Not
Implemented
o 01100100 (#100) - Conditional IE Error
o 01100101 (#101) - Message Not Compatible With the Protocol State
o 01101111 (#111) - Protocol Error, Unspecified

The front panel also allows you to select Custom Value as the Location Area
Update Reject Cause in addition to the above values. The Custom Value is set
with the GPIB command only and is not configurable via the front panel.
See GMM Cause Information Element for more information about the cause
values.
The command to set the Location Area Update Reject Cause
is CALL:PPRocedure:LAU|LAUPdate:REJect:GMMCause .

You can initiate a LAU Rejection procedure by doing the following:

 Make sure the mobile station is Attached


 Change the operating mode to Cell Off
 Press Call Setup
 Press Cell Info ( F6 )
 Press Cell Identification ( F3 )
 Change the actual Location Area Code (LAC) of the cell
 Change the operating mode to Active Cell , then when the mobile station
comes back in to register to the network. it will send the Location Area Update
Request to the test set.

Use these parameters in parallel with Protocol Logging to verify that the mobile
station behaves in a manner conforming to the standards 3GPP TS 24.008 Version
6.13.0 Section 4.4.4.7 for this situation and for each associated Location Area Update
Reject Cause value.

Routing Area Update Rejection


You can configure the test set to reject the request for Routing Area Update (RAU)
from the mobile station. This allows you to observe how the mobile station responds
to RAU Rejection from a network and determines if it complies with mobile
performance specifications of 3GPP TS 24.008 Version 6.13.0.

There are two configurable parameters that you can set before sending a RAU
Rejection.

 Routing Area Update Reject State

When the Routing Area Update Reject State is set to ON, the test set will reject
the RAU request from the mobile station.

The command to set the Routing Area Update Reject State


is CALL:PPRocedure:RAU|RAUPdate:REJect[:STATe] .

 Routing Area Update Reject Cause


You can choose which cause value is sent to the mobile station in the Routing
Area Update Reject message. You can choose the following reject causes from
the front panel:

o 00000010 (#2) - IMSI Unknown inHLR


o 00000011 (#3) - Illegal MS
o 00000011 (#4) - IMSI Unknown in VLR
o 00000011 (#5) - IMEI Not Accepted
o 00000110 (#6) - Illegal ME
o 00000111 (#7) - GPRS Services Not Allowed
o 00001000 (#8) - GPRS/Non-GPRS Services Not Allowed
o 00001001 (#9) - MS Identity Cannot Be Derived
o 00001010 (#10) - Implicitly Detached
o 00001011 (#11) - PLMN not allowed
o 00001100 (#12) - Location Area not allowed
o 00001101 (#13) - Roaming not allowed in LA
o 00001110 (#14) - GPRS Services Not Allowed In This PLMN
o 00001111 (#15) - No suitable cells in LA
o 00010000 (#16) - MSC Temporarily Not Reachable
o 00010001 (#17) - Network Failure
o 00010100 (#20) - MAC Failure
o 00010101 (#21) - Synch Failure
o 00010110 (#22) - Congestion
o 00010111 (#23) - GSM Authentication Unacceptable
o 00100000 (#32) - Service Option Not Supported
o 00100001 (#33) - Requested Service Option Not Subscribed
o 00100010 (#34) - Service Option Temporarily Out of Order
o 00100110 (#38) - Call Cannot Be Identified
o 00101000 (#40) - No PDP Context Activated
o 00110000 (#48) - Retry Upon Entry Into a New Call
o 01011111 (#95) - Semantically Incorrect Message
o 01100000 (#96) - Invalid Mandatory Information
o 01100001 (#97) - Message Type Non-Existent or Not Implemented
o 01100010 (#98) - Message Type Not Compatible With the Protocol State
o 01100011 (#99) - Information Element Non-Existent or Not
Implemented
o 01100100 (#100) - Conditional IE Error
o 01100101 (#101) - Message Not Compatible With the Protocol State
o 01101111 (#111) - Protocol Error, Unspecified
The front panel also allows you to select Custom Value as the Routing Area
Update Reject Cause in addition to the above values. The Custom Value is set
with the GPIB command only and is not configurable via the front panel.
See GMM Cause Information Element for more information about the cause
values.

The command to set the Routing Area Update Reject Cause


is CALL:PPRocedure:RAU|RAUPdate:REJect:GMMCause .

You can initiate a RAU Rejection procedure by doing the following:

 Make sure the mobile station is Attached


 Change the operating mode to Cell Off
 Press Call Setup
 Press Cell Info ( F6 )
 Press Cell Identification ( F3 )
 Change the actual Routing Area Code (RAC) of the cell
 Change the operating mode to Active Cell , then when the mobile station
comes back in to register to the network. it will send the Routing Area Update
Request to the test set.

Use these parameters in parallel with Protocol Logging to verify that the mobile
station behaves in a manner conforming to the standards 3GPP TS 24.008 Version
6.13.0 Section 4.7.5.1.4 for this situation and for each associated Routing Area Update
Reject cause value.

Activate PDP Context Reject


You may configure the test set to simulate a network rejection of an Activate PDP
Context Request from an MS. You can select from a variety of SM cause values to be
sent in the SM cause information element ( SM Cause Information Element ) with the
Activate PDP Context Reject message. Use this function in parallel with protocol
logging ( Protocol Logging ) to verify that the MS behaves in a manner conforming to
the standards for this situation and for each associated SM cause value.

The data connection state must be "Attached" to use the Activate PDP Context Reject
event.

Network Initiated PDP Context


If data requiring a PDP context is destined for an mobile staion, you can configure
whether or not the test set will initiate a PDP context negotiation procedure by setting
the Network Initiated PDP Context State.

The GPIB command to set the Network Initiated PDP Context State
is CALL:PPRocedure[:QOSProfile]:PDPContext:NINitiated[:STATe] .

Alerting Duration
The Mobile Originated Alerting Duration is used to delay the connection of a Mobile
Originated voice call. When the timer has a non-zero value, the call will remain in the
Alerting state until the timer expires, at which point, the 8960 will complete (or
release) the call.

This parameter is only applicable in the Active Cell operating mode.

The GPIB command to set the Alerting Duration


is CALL:MORiginated:ALERting:DURation .

Call Release State


The Call Release State is used to determine whether an incoming Mobile Originated
voice call is connected or released. When this parameter is set to ON , the Mobile
Originated voice call will be released when the Alerting Duration expires.

This parameter is only applicable in the Active Cell operating mode.

The GPIB command to set the Call Release State


is CALL:MORiginated:CALL:RELease[:STATe] .

Emergency Service Category Value


The Emergency Service Category Value is used to indicate which particular
emergency service is acturally required. On the front panel of the test set, under the
`DUT Information', there is a `Called Num' field. When the Mobile Originated call is
an emergency call, this field will display one of the following strings:

 Emergency Call
 Police
 Ambulance
 Marine Guard
 Mountain Rescue

This parameter is only applicable in the Active Cell operating mode.

The GPIB command to query the `Called Num'


is CALL:MS:REPorted:ONUMber[:SELected]? .

Uplink Timing Delay


In order to synchronize the various components of a complex test system, (e.g. the
fading system that comprise the test set and a signal source), it is necessary for the test
set to provide a Neighbor Cell Synchronization Trigger. This trigger generates a
signal on the test set's trigger output which can be used to align the frame start
position of the other instruments in the system with the test set. The Uplink Timing
Delay parameter allows you to specify the symbol offset prior to the first symbol of
the 0'th frame on which to fire the trigger, e.g. if 5 is chosen for this parameter, the
trigger will fire 5 symbols before the first symbol of the 0'th frame.

The GPIB command to send the neighbor cell synchronization trigger output
is CALL:TRIGger[:OUTPut]:FRAMe:SYNChronize

The GPIB command to set this parameter


is CALL:TRIGger[:OUTPut]:FRAMe:SYNChronize:OFFSet .

Detach Type Information Element


Detach Type Value Detach Type Programming
Detach Type
(decimal) (bits) Mnemonic
1 001 REQ Re-attach Required
2 010 NREQ Re-attach not Required
IMSI Detach (after VLR
3 011 IMSI
failure)

GMM Cause Information Element


GMM Cause Information Element
Cause Value (decimal) Cause Value (bits) Cause
2 00000010 IMSI Unknown
3 00000011 Illegal MS
4 00000100 IMSI UKNOWN IN VLR
GMM Cause Information Element
Cause Value (decimal) Cause Value (bits) Cause
5 00000101 IMEI NOT ACCEPTED
6 00000110 Illegal ME
7 00000111 GPRS Services Not Allowed
8 00001000 GPRS/Non-GPRS Services Not Allowed
9 00001001 MS Identity Cannot Be Derived
10 00001010 Implicitly Detached
11 00001011 PLMN Not Allowed
12 00001100 Location Area Not Allowed
13 00001101 Roaming Not Allowed In This LA
16 00010000 MSC Temporarily Not Reachable
17 00010001 Network Failure
22 00010110 Congestion
32 00100000 Service Option Not Supported
33 00100001 Requested Service Option Not Subscribed
34 00100010 Service Option Temporarily Out of Order
48 00110000 Retry Upon Entry Into A New Cell
95 01011111 Semantically Incorrect Message
96 01100000 Invalid Mandatory Information
97 01100001 Message Type Nonexistent
98 01100010 Msg Type Incompatible With Prot State
99 01100011 Information Element Nonexistent
100 01100100 Conditional IE Error
101 01100101 Msg Incompatible With Protocol State
111 01101111 Protocol Error, Unspecified

SM Cause Information Element


SM Cause Information Element
Cause Value Cause Value
Cause
(decimal) (bits)
24 00011000 MBMS Bearer Insufficient For Service
25 00011001 LLC or SNDCP Failure
26 00011010 Insufficient Resources
SM Cause Information Element
Cause Value Cause Value
Cause
(decimal) (bits)
27 00011011 Missing or Unknown APN
28 00011100 Unknown PDP Address or PDP Type
29 00011101 User Authentication Failed
30 00011110 Activation Rejected By GGSN
31 00011111 Activation Rejected, Unspecified
32 00100000 Service Option Not Supported
33 00100001 Requested Service Opt Not Subscribed
34 00100010 Service Opt Temporarily Out of Order
35 00100011 NSAPI Already Used
36 00100100 Regular Deactivation
37 00100101 QoS Not Accepted
38 00100110 Network Failure
39 00100111 Reactivation Required
40 00101000 Feature Not Supported
41 00101001 Semantic Error In the TFT Operation
42 00101010 Syntactical Error In the TFT Operation
43 00101011 Unknown PDP Context
44 00101100 Semantic Errors in Packet Filter(s)
45 00101101 Syntactical Errors in Packet Filter(s)
46 00101110 PDP Context without TFT Already Activated
47 00101111 Multicast Group Membership Timeout
81 01010001 Invalid Transaction Identifier Value
95 01011111 Semantically Incorrect Message
96 01100000 Invalid Mandatory Information
97 01100001 Msg Type Nonexistent/Not Implemented
98 01100010 Msg Type Incompatible With Protocol State
99 01100011 IE Non-existent or Not Implemented
100 01100100 Conditional IE Error
101 01100101 Msg Not Compatible With Protocol State
111 01101111 Protocol Error, Unspecified
APN Restrict Value Incompatible without PDP
112 01110000
Context
LAPDm Fill Bits
The LAPDm Fill Bits parameter allows you to set the Fill Bits for the LAPDm frames.
When the parameter is set to Fixed, the LAPDm Fill Bits are set to a fixed value -
0x2B. When the parameter is set to Random, the LAPDm Fill Bits are set to a random
value according to 3GPP TS04.06 V8.4.0.

The GPIB command to set this parameter is CALL:LAPDm:FBITs .

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 that receives a ROUTING AREA UPDATE
REJECT message stops timer T3330. The MS shall then take different actions depending
on the received reject cause value:

# 10 (Implicitly Detached) – Additional Cause Code for GMM

This cause is sent to the MS either if the network has implicitly detached the MS, e.g.
some while after the Mobile reachable timer has expired, or if the GMM context data
related to the subscription dose not exist in the SGSN e.g. because of a SGSN restart.

The MS shall change to state GMM-DEREGISTERED.NORMAL-SERVICE. The MS shall


then perform a new attach procedure. The MS should also activate PDP context(s) to
replace any previously active PDP contexts.

NOTE: In some cases, user interaction may be required and then the MS
cannot activate the PDP context(s) automatically.

Causes related to subscription options:

# 11 (PLMN Not Allowed)

This cause is sent to the MS if it requests location updating in a PLMN where the MS,
by subscription or due to operator determined barring is not allowed to operate. The
MS shall store the LAI or the PLMN identity in the appropriate forbidden list, i.e. in the
“forbidden PLMN list”. MS shall then perform a PLMN selection instead of a cell
selection.
# 12 (Location Area Not Allowed)

This cause is sent to the MS if it requests location updating in a location area where
the HPLMN determines that the MS, by subscription, is not allowed to operate. The MS
shall store the LAI or the PLMN identity in the appropriate forbidden list i.e. in the list of
“forbidden location areas for regional provision of service”.

NOTE: If cause #12 is sent to a roaming subscriber the subscriber is denied


service even if other PLMNs are available on which registration was possible.

# 13 (Roaming Not Allowed In This LA)

This cause is sent to an MS which requests location updating in a location area of a


PLMN which by subscription offers roaming to that MS but not in that Location Area.
The MS shall store the LAI or the PLMN identity in the appropriate forbidden list i.e. in
the list of “forbidden location areas for roaming”. MS shall then perform a PLMN
selection instead of a cell selection.

The MS shall delete any RAI or LAI, P-TMSI, P-TMSI signature and GPRS ciphering key
sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED
and enter the state GMM-DEREGISTERED.

If the MS is IMSI attached via MM procedures, the MS shall in addition set the update
status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering
key sequence number. The new MM state is MM IDLE.

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 stops timer T3330 and enters state MM IDLE. The MS
shall then take different actions depending on the received reject cause:

# 10 (Implicitly Detached) - Additional Cause Code for GMM

This cause is sent to the MS either if the network has implicitly detached the MS, e.g.
some while after the Mobile reachable timer has expired, or if the GMM context data
related to the subscription dose not exist in the SGSN e.g. because of a SGSN restart.

The MS shall change to state GMM-DEREGISTERED.NORMAL-SERVICE. The MS shall


then perform a new attach procedure The MS should also activate PDP context(s) to
replace any previously active PDP contexts.
NOTE: In some cases, user interaction may be required and then the MS
cannot activate the PDP context(s) automatically.

Causes related to subscription options:

# 11 (PLMN Not Allowed)

This cause is sent to the MS if it requests location updating in a PLMN where the MS,
by subscription or due to operator determined barring is not allowed to operate. The
MS shall store the LAI or the PLMN identity in the appropriate forbidden list, i.e. in the
“forbidden PLMN list”. MS shall then perform a PLMN selection instead of a cell
selection.

# 12 (Location Area Not Allowed)

This cause is sent to the MS if it requests location updating in a location area where
the HPLMN determines that the MS, by subscription, is not allowed to operate. The MS
shall store the LAI or the PLMN identity in the appropriate forbidden list i.e. in the list of
“forbidden location areas for regional provision of service”.

NOTE: If cause #12 is sent to a roaming subscriber the subscriber is denied


service even if other PLMNs are available on which registration was possible.

# 13 (Roaming Not Allowed In This Location Area)

This cause is sent to an MS which requests location updating in a location area of a


PLMN which by subscription offers roaming to that MS but not in that Location Area.
The MS shall store the LAI or the PLMN identity in the appropriate forbidden list i.e. in
the list of “forbidden location areas for roaming”. MS shall then perform a PLMN
selection instead of a cell selection.

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED and the
update status to U3 ROAMING NOT ALLOWED and enter the state GMM-
DEREGISTERED. Furthermore, it shall delete any P-TMSI, P-TMSI signature, TMSI, RAI,
LAI, ciphering key sequence number GPRS ciphering key sequence number, reset the
location update attempt counter, reset the routing area updating attempt counter and
reset the GPRS attach attempt counter.