Академический Документы
Профессиональный Документы
Культура Документы
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted in
any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given as is and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,
DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT
NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of
Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners,
and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2009. All rights reserved.
Contents
Contents 3
List of tables 4
List of tables
Changes in content
The 3GPP release has been upgraded from Release 5 to Release 7 in all
the references to the 3GPP TS 24.008 Mobile radio interface Layer 3
specification; Core network protocols; Stage 3. The change is the effect of
the new feature SG02198 HSPA+.
Changes in documentation
The Attach Request and Routing Area Update Request are only received
from the MS to the SGSN which means that the SGSN cannot send any
information elements related to these messages. Therefore, the remark on
the PS LCS Capability information element has been corrected to "Not
supported, ignored if received" in the following locations:
The RAB information element has been corrected to uplink data status in
Table Service Request message content of Subsection Service Request
(UMTS only) of Section Service Request procedure (UMTS only).
Changes in content
Optional RAB element has been added to Service request (UMTS only).
Changes in content
The optional 'PDP Context Status' information element has been added to
the Routing Area Update Accept message.
Changes in documentation
Tables GMM cause codes and SM cause codes have been removed
because corresponding information can be found in the SGSN Cause
Description document.
The TFT error descriptions under the PDP context modification have been
removed because the SGSN only transmits the TFT IE and does not check
its validity.
The following Sections describe the basic functions offered by the GPRS
mobility management sublayer. The functionality is described in terms of
timers and procedures. During the GPRS mobility management
procedures, the GPRS session management procedures are suspended.
The network can assign a packet temporary mobile subscriber identity (P-
TMSI) signature to a mobile station (MS) in a GPRS Attach, Routing Area
Update, or P-TMSI re-allocation procedure. In combination with a valid P-
TMSI, the P-TMSI signature is used by the MS for authentication and
identification purposes. If the MS has no valid P-TMSI, it does not use the
P-TMSI signature in the subsequent GPRS Attach, Routing Area Update
(RAU), or Detach procedure.
The P-TMSI is used for authentication and identification. If the network has
assigned a new P-TMSI, the MS and the network handle the old and the
new P-TMSI in the following way:
The network considers the old P-TMSI and the old RAI invalid as soon as
an acknowledge message (Attach Complete, Routing Area Update
Complete or P-TMSI Re-allocation Complete) is received.
The READY timer, T3314, is used in the MS and in the network for each
assigned P-TMSI to control the cell update procedure. When the READY
timer is running or deactivated, the MS performs a cell update each time a
new cell is selected. If a routing area is crossed, the MS performs a RAU
procedure instead of a cell update.
. in the MS when the GMM entity receives an indication from the lower
layers that an LLC frame has been transmitted on the radio interface
. in the network when the GMM entity receives an indication from the
lower layers that an LLC frame has been successfully received by
the network
The value of the READY timer can be negotiated between the MS and the
network using the GPRS Attach or GPRS Routing Area Update procedure.
If the negotiated READY timer value indicates that the READY timer
function is deactivated, or if the Force to standby is activated, the READY
timer always runs without expiry. If the negotiated READY timer value is
set to zero, the READY timer stops immediately.
If the network does not accept the request, it sends an Attach Reject
message to the MS.
If the Attach Accept message contains a P-TMSI, the MS uses this P-TMSI
as the new temporary identity for GPRS services. In this case, the MS
returns an Attach Complete message to the network. The MS considers
the old P-TMSI invalid as soon as an LLC frame is received with the local
TLLI derived from the new P-TMSI. The MS deletes its old P-TMSI and
stores the new one. The MS deletes its old P-TMSI signature, if available,
and stores the new one. If the message does not contain a P-TMSI
signature, the old P-TMSI signature, if available, is deleted. The network
receiving an Attach Complete message stops the T3350 timer and
considers the P-TMSI sent in the Attach Accept message valid. The
network can then initiate GMM common procedures, identification
procedure, or authentication and ciphering procedure, for example.
If the network can accept the Attach Request neither for GPRS nor for
non-GPRS services, it sends an Attach Reject message to the MS. The
message contains a network reject cause code that typically indicates one
of the following causes:
#3 Illegal MS
#6 Illegal ME
#7 GPRS services not allowed
#8 GPRS services and non-GPRS services not allowed
#11 PLMN not allowed
#12 Location area not allowed
#13 Roaming not allowed in this location area
#14 GPRS services not allowed in this PLMN
#15 No suitable cells in this location area
Attach Request
Attach Accept
If the network accepts the GPRS Attach request, it sends an Attach Accept
message to the MS. The P-TMSI signature IE assigns an identity to the
MS's GMM context. The Negotiated READY timer IE indicates a value for
the READY timer. The Allocated P-TMSI IE assigns a P-TMSI to an MS in
case of a GPRS or combined GPRS Attach. The MS identity IE assigns or
unassigns a TMSI to an MS in case of a combined GPRS Attach. The
GMM cause IE is included when the IMSI Attach for non-GPRS services is
not successful during a combined GPRS Attach procedure.
Attach Complete
Attach Reject
If the network cannot accept the Attach Request, it sends an Attach Reject
message to the MS.
.
Lower layer failure
For more information, see Section Error handling of GPRS mobility and
session management.
The GPRS Detach procedure is used for the following two purposes:
When the network receives the Detach Request message from the MS, it
sends a Detach Accept message to the MS if the Detach type IE value
indicates that the Detach Request was not sent due to switching off.
Depending on the value of the Detach type IE, the following applies:
. The MS is marked as inactive in the network for GPRS and for non-
GPRS services. The network and the MS deactivate the PDP
contexts and deactivate any logical links.
.
IMSI Detach: The MS is marked as inactive in the network for non-
GPRS services.
When the network receives the Detach Accept message, it stops the
T3322 timer. The MS is now considered detached.
If the network assigns a cause value to the Detach Request, the cause
value is one of the following:
. T3322 time-out
On the first expiry of the timer, the network retransmits the Detach
Request message and starts the T3322 timer. This retransmission is
repeated four times, that is, the GPRS Detach procedure is aborted
on the fifth expiry of the T3322 timer and the network changes to the
GMM-DEREGISTERED state.
. Lower layer failure
The network aborts the GPRS Detach procedure.
. GPRS Detach procedure collision
For more information, see Section Error handling of GPRS mobility and
session management.
The Routing Area Update procedure is used for the following cases:
The Routing Area Update procedure is always initiated by the MS. The
network can assign a P-TMSI signature to an MS in the Routing Area
Update procedure. In combination with a valid P-TMSI, the P-TMSI
signature is used by the MS for authentication and identification purposes.
The P-TMSI signatures used previously are deleted in the Routing Area
Update procedure. The value of the READY timer can be negotiated
between the MS and the network in the Routing Area Update procedure.
To initiate the Routing Area Update procedure, the MS sends the Routing
Area Update Request message to the network. This message contains the
P-TMSI signature when received within a previous Attach Accept or
Routing Area Update Accept message. The network then initiates the
GMM common procedures, for example, the authentication and ciphering
procedure.
. a P-TMSI
. Receive N-PDU Numbers
In this case the values of the Receive N-PDU Numbers valid in the MS are
included in the Routing Area Update Complete message.
#3 Illegal MS
#6 Illegal ME
#7 GPRS services not allowed
#9 MS identity cannot be derived by the network
#10 Implicitly detached
#11 PLMN not allowed
#12 Location area not allowed
#13 Roaming not allowed in this location area
#14 GPRS services not allowed in this PLMN
#15 No suitable cells in this location area
.
The update result IE value indicates 'combined RA/LA': Routing and
location area update is successful.
.
The update result IE value indicates 'RA only': Routing area update
is successful, but the location area update is not successful.
. a P-TMSI or a TMSI
. Receive N-PDU Numbers
The Receive N-PDU Numbers that are valid in the MS are included
in the Routing Area Update Complete message.
#3 Illegal MS
#6 Illegal ME
#7 GPRS services not allowed
#8 GPRS services and non-GPRS services not allowed
#9 MS identity cannot be derived by the network
#10 Implicitly detached
#11 PLMN not allowed
#12 Location area not allowed
#13 Roaming not allowed in this location area
#14 GPRS services not allowed in this PLMN
#15 No suitable cells in this location area
The combined Routing Area Update procedure continues the same way
as the normal Routing Area Update procedure but it also includes the
location area update actions:
The handling at the receipt of the Routing Area Update Accept depends on
the value received in the Update result IE as specified below. The TMSI re-
allocation can be part of the combined Routing Area Update procedure.
The allocated TMSI is then included in the Routing Area Update Accept
message together with the location area identity (LAI). In this case the
network starts the T3350 timer. The network receiving a Routing Area
Update Complete message stops the T3350 timer and considers the new
TMSI valid.
The combined GPRS Routing Area Update procedures are accepted for
GPRS services only: the description for normal Routing Area Update.
In addition, the following description for location area update applies: the
message contains a network reject cause code that typically indicates one
of the following causes:
The following abnormal cases can be identified on the network side with
normal and periodic Routing Area Updates:
Abnormal cases with combined Routing Area Update: the abnormal cases
specified with normal and periodic Routing Area Updates apply with the
exceptions for lower layer failure and T3350 time-out, in which, in addition
to the P-TMSI and P-TMSI signature, the old TMSI is considered occupied
until the MS uses the new TMSI in a subsequent message.
For more information, see Section Error handling of GPRS mobility and
session management.
attempts, the network can use the new P-TMSI for paging for an
implementation-dependent number of paging attempts. When the
network receives a response from the MS, the network considers the
new P-TMSI valid and the old P-TMSI invalid.
. Expiry of the T3350 timer
The T3350 timer supervises the P-TMSI re-allocation procedure. On
the first expiry of the T3350 timer, the network resets and restarts the
T3350 timer and retransmits the P-TMSI re-allocation Command.
This retransmission is repeated four times, that is, the network
aborts the re-allocation procedure on the fifth expiry of the T3350
timer, and follows the rules for the case described above.
. P-TMSI re-allocation and GPRS Attach procedure collision
If the network receives an Attach Request message before the
ongoing P-TMSI re-allocation procedure is completed, the network
proceeds with the GPRS Attach procedure after deleting the GMM
context.
.
P-TMSI re-allocation and an MS-initiated GPRS Detach procedure
collision
If the network receives a Detach Request message before the
ongoing P-TMSI re-allocation procedure is completed, the network
aborts the P-TMSI re-allocation procedure and progresses with the
GPRS Detach procedure.
. P-TMSI re-allocation and a Routing Area Update procedure collision
If the network receives a Routing Area Update Request message
before the ongoing P-TMSI re-allocation procedure is completed, the
network aborts the P-TMSI re-allocation procedure and progresses
with the Routing Area Update procedure. The network then performs
a new P-TMSI re-allocation during the Routing Area Update
procedure.
Note
In the GSM, the GMM layer notifies the LLC sublayer whether ciphering is
used or not, and if it is, also which algorithm and GPRS GSM ciphering key
is used.
If authentication and ciphering fails, that is, if the response is not valid, the
network checks if the MS used the P-TMSI or the IMSI for identification.
.
If the P-TMSI is used, the network can decide to initiate the
identification procedure. If the IMSI given by the MS differs from the
one that the network associated with the P-TMSI, the authentication
is restarted with the correct parameters. If the IMSI provided by the
MS is the expected one (authentication failed), the network proceeds
as described below.
. If the IMSI is used, or the network decides not to try the identification
procedure, an Authentication and Ciphering Reject message is sent
to the MS.
The security parameters for authentication and ciphering are tied together
in sets. In a GSM authentication challenge both the authentication
response parameter SRES and the GPRS GSM ciphering key Kc can be
computed from the RAND challenge parameter, given the secret key
The MS stores the GPRS ciphering key sequence number with the GPRS
GSM ciphering key (in case of a GSM authentication challenge), the
GPRS UMTS ciphering key and the GPRS UMTS integrity key (in case of
a UMTS authentication challenge), and includes the corresponding GPRS
ciphering key sequence number in the Routing Area Update Request and
Attach Request messages.
In the GSM, the network can decide to start ciphering with the stored
GPRS ciphering key if the stored GPRS ciphering key sequence number
and the one sent by the MS are the same and the previously negotiated
ciphering algorithm is known and supported in the network. When
ciphering is requested at a GPRS Attach, the authentication and ciphering
procedure is performed since the MS does not store the ciphering
algorithm at Detach.
If the GPRS ciphering key sequence number stored in the network does
not match the GPRS ciphering key sequence number received from the
MS in the Attach Request message, the network authenticates the MS.
In the GSM the MS starts ciphering after sending the Authentication and
Ciphering Response message. The network starts ciphering when a valid
Authentication and Ciphering Response is received from the MS.
In the GSM the network can decide to continue ciphering without sending
an Authentication and Ciphering Request message after receiving a
Routing Area Update Request message with a valid GPRS ciphering key
sequence number. Both the MS and the network use the latest ciphering
parameters. The network starts ciphering when sending the ciphered
Routing Area Update Accept message to the MS. The MS starts ciphering
after receiving a valid ciphered Routing Area Update Accept message
from the network.
Note
In some specifications, the term key set identifier (KSI) is used instead
of the term GPRS ciphering key sequence number.
Nokia Siemens Networks SGSN does not send the Authentication and
Ciphering Reject message since the authentication procedure is always
done as part of another GMM operation, not as a standalone operation.
For more information, see Section Error handling of GPRS mobility and
session management.
When the network receives an Identity Response, it stops the T3370 timer.
Identity Request
Identity Response
.
Lower layer failure
For more information, see Section Error handling of GPRS mobility and
session management.
GMM status
This message is sent by the MS or by the network at any time to report the
following error conditions:
GMM information
This message is sent by the network any time to send certain pieces of
information to the MS.
.
to identify the cell the MS currently selected
. to prompt the mobile to re-attach after a network failure
The network initiates the paging procedure by using P-TMSI when GMM
signalling messages or user data is pending to be sent to the MS while the
Mobile Reachable timer is running. The network can page only GPRS
mobile stations that are GMM-REGISTERED and identified by a local P-
TMSI. The network requests the RR sublayer to start paging, and starts
the T3313 timer. If the MS is not GPRS-Attached when it receives a page
for GPRS services, the MS ignores the paging. The network stops the
T3313 timer when it receives a response from the MS. When the T3313
timer expires, the network can re-initiate paging. The network starts the
READY timer when it receives a response from the MS.
The network can initiate the paging procedure for non-GPRS services
when the MS is IMSI-Attached for non-GPRS services. To initiate the
procedure, the GMM entity requests the RR sublayer to start paging for
non-GPRS services. The MS identity used for paging is the allocated TMSI
if acknowledged by the MS, otherwise it is the IMSI.
For more information, see Section Error handling of GPRS mobility and
session management.
The purpose of this procedure is to transfer the PMM mode from the PMM-
IDLE to the PMM-CONNECTED mode, and/or to assign the radio access
bearer (RAB) if PDP contexts are activated without RAB assigned. In the
latter case, the PMM mode may be either the PMM-IDLE mode or the
PMM-CONNECTED mode if the MS requires RAB re-establishment. This
procedure is used for:
.
The initiation of the CM layer service (SM or SMS, for example)
procedure from the MS in the PMM-IDLE mode.
.
The network to transfer downlink signalling.
. The uplink (in the PMM-IDLE or PMM CONNECTED mode) and
downlink (only in the PMM-IDLE mode) of user data.
After receiving a Service Request message the network may initiate GMM
common procedures, for example the GMM identification or the GMM
authentication and ciphering procedure, depending on the received
information, such as the GPRS ciphering key sequence number and the P-
TMSI.
For more information, see Section Error handling of GPRS mobility and
session management.
The Protocol Discriminator (PD) and its use are defined in 3GPP TS
24.007 Mobile radio interface signalling layer 3; General Aspects.
The message type IE and its use are defined in 3GPP TS 24.007 Mobile
radio interface signalling layer 3; General Aspects. Table 11.2 of this
specification defines the value part of the message type IE used in the
mobility management protocol and the call control protocol.
When the radio connection starts with a core network node of earlier than
3GPP R99, bit 8 is set to 0 and bit 7 is reserved for the sequence number
sent in messages from the MS. In messages sent from the network, bits 7
and 8 are coded with a '0'. When the radio connection starts with a core
network node of 3GPP R99 or later, bits 7 and 8 are reserved for the
sequence number sent in messages from the MS. In messages sent from
the network, bits 7 and 8 are coded with a '0'.
There are four GPRS Mobility Management timers on the network side:
T3322, T3350, T3360, and T3370. The table below summarises their
causes of start and stop, and the timer values.
In Nokia Siemens Networks SGSN, only the MS can initiate the PDP
context activation.
The MS initiates the establishment of the logical link for the LLC SAPI
indicated by the network with the offered QoS and selected radio priority
level if no logical link was already established for that SAPI. If the offered
QoS parameters received from the network differ from the QoS requested
by the MS, the MS either accepts the negotiated QoS or initiates the PDP
context deactivation procedure. If the LLC SAPI indicated by the network
cannot be supported by the MS, the MS initiates the PDP Context
Deactivation procedure.
# 26 Insufficient resources
# 27 Missing or unknown APN
# 28 Unknown PDP address or PDP type
# 29 User authentication failed
# 30 Activation rejected by GGSN
# 31 Activation rejected, unspecified
# 32 Service option not supported
# 33 Requested service option not subscribed
# 34 Service option temporarily out of order
# 95 - 111 Protocol errors
. Expiry of timers
On the first expiry of the T3385 timer, the network resends the
Request PDP Context Activation message, resets and restarts the
T3385 timer. This retransmission is repeated four times, that is, the
network releases the resources possibly allocated to this activation
and aborts the procedure on the fifth expiry of the T3385 timer.
Note
In general, the MS is unable to test if the PDP type, PDP address, and
APN in the Request PDP Context Activation message are the same as
those for the PDN to which the MS is attempting to activate a context.
This is because the MS could omit one or more of the parameters in the
Activate PDP Context Request message since it is relying on the
default values to be provided by the network.
.
MS-initiated PDP context activation request for an already activated
PDP context
.
If the combination of PDP type, PDP address, and APN
matches those of an already activated PDP context(s), the
network locally deactivates all existing PDP contexts that
match the combination of APN, PDP type and PDP address
without notifying the MS and proceeds with the requested PDP
context activation.
. Otherwise, if the NSAPI matches one of an already activated
PDP context(s), the network locally deactivates this PDP
context and all the PDP contexts linked to this one without
notifying the MS and proceeds with the activation of the
requested PDP context.
For more information, see Section Error handling of GPRS mobility and
session management.
In order to request a PDP context activation with the same PDP address
and APN as an already active PDP context, the MS sends an Activate
Secondary PDP Context Request message to the network. The message
contains the selected NSAPI. The MS ensures that the selected NSAPI is
not being used currently by another SM entity in the MS. The message
also includes a QoS profile, a requested LLC SAPI, and the Linked TI. The
QoS profile is the requested QoS. If present, the TFT is sent transparently
through Nokia Siemens Networks SGSN to the GGSN to enable packet
classification and policing for downlink data transfer. When the network
receives an Activate Secondary PDP Context Request, it validates the
message by verifying the TI given in the Linked TI IE to be any of the active
PDP context(s). The same GGSN address is used by Nokia Siemens
Networks SGSN for the already established PDP context(s) for that PDP
address. The network selects a radio priority level based on the negotiated
QoS and replies with an Activate Secondary PDP Context Accept
message, if the request can be accepted. If the offered QoS parameters
received from the network differ from the QoS requested by the MS, the
MS either accepts the negotiated QoS or initiates the PDP context
deactivation procedure. The MS initiates the establishment of a logical link
for the LLC SAPI indicated by the network with the offered QoS and the
selected radio priority level if no logical link is already established for that
SAPI. If the MS cannot support the LLC SAPI indicated by the network, the
MS initiates the PDP context deactivation procedure.
For more information, see Section Error handling of GPRS mobility and
session management.
Network-initiated procedure
In order to initiate the procedure, the network sends the Modify PDP
Context Request message to the MS and starts the T3386 timer. The
message contains the new QoS, the radio priority level and the LLC SAPI
that are used by the MS at the lower layers for the transmission of data
related to the PDP context. When the MS receives this message, it replies
with the Modify PDP Context Accept message if the MS accepts the new
QoS and the indicated LLC SAPI. If the MS does not accept the new QoS
or the indicated LLC SAPI, the MS initiates the PDP context deactivation
procedure for the PDP context - the reject cause IE value of the Deactivate
PDP Context Request message indicates 'QoS not accepted'. When the
network receives the Modify PDP Context Accept message, it stops the
T3386 timer. The network establishes, reconfigures or continues using the
logical link to the new QoS for the LLC SAPI indicated in the Modify PDP
Context Request message.
MS-initiated procedure
In order to initiate the procedure, the MS sends the Modify PDP Context
Request message to the network. The message can contain the requested
new QoS or the TFT and the requested LLC SAPI. When the network
receives the Modify PDP Context Request message, it can reply with the
Modify PDP Context Accept message in order to accept the context
modification. The reply message can contain the negotiated QoS and the
radio priority level based on the new QoS profile and the negotiated LLC
SAPI that is used by the logical link. When the MS receives the Modify
Note
When the MS requests the QoS modification, and the network does not
accept the MS request and is unable to provide the requested QoS, the
network maintains the QoS as previously negotiated or proposes a new
QoS. Therefore, the network does not reject the MS-initiated PDP
context modification request due to the unavailability of the required
QoS.
# 26 Insufficient resources
# 32 Service option not supported
# 41 Semantic error in the TFT operation
# 42 Syntactical error in the TFT operation
# 44 Semantic errors in packet filter(s)
# 45 Syntactical errors in packet filter(s)
# 95 - 111 Protocol errors
. Expiry of timers
On the first expiry of the T3386 timer, the network resends the
Modify PDP Context Request message, resets and restarts the
T3386 timer. This retransmission is repeated four times, that is, the
network can continue to use the previously negotiated QoS or it can
initiate the PDP context deactivation procedure on the fifth expiry of
the T3386 timer.
. Collision of MS- and network-initiated PDP context modification
procedure
The MS detects the collision of an MS- and network-initiated PDP
context modification procedure if a Modify PDP Context Request
message is received from the network after the MS sent a Modify
PDP Context Request message itself, and both messages contain
the same TI, and the MS did not receive a Modify PDP Context
Accept message from the network. The network detects a collision if
it received a Modify PDP Context Request message from the MS
with the same TI as in the Modify PDP Context Request message
sent to the MS. In case of such a collision, the network-initiated PDP
context modification takes precedence over the MS-initiated PDP
context modification. The MS internally terminates the MS-initiated
PDP context modification procedure, enters the PDP Active state
For more information, see Section Error handling of GPRS mobility and
session management.
.
Expiry of timers
On the first expiry of the T3395 timer, the network resends the
message Deactivate PDP Context Request, resets and restarts the
T3395 timer. This retransmission is repeated four times, that is, the
network erases the PDP context-related data for that MS on the fifth
expiry of the T3395 timer.
. Collision of MS- and network-initiated PDP context deactivation
requests
If the MS- and the network-initiated PDP context deactivation
requests collide, both the MS and the network replies with the
Deactivate PDP Context Accept message and stops the T3390 and
T3395 timers.
For more information, see Section Error handling of GPRS mobility and
session management.
SM Status
.
TI flag = 0 received in the new Nokia Siemens Networks SGSN
indicates to the new Nokia Siemens Networks SGSN that the MS
originated the TI
. TI flag = 1 received in the new Nokia Siemens Networks SGSN
indicates to the new Nokia Siemens Networks SGSN that the NW
originated the TI
The Message type IE and its use are defined in 3GPP TS 24.007 Mobile
radio interface signalling layer 3; General Aspects where Table 11.2 and
Figure 11.2 define the value part of the message type IE used in the
session management protocol.
There are two Session Management timers on the network side: T3386
and T3395. The table below summarises their causes of start and normal
stop, and the timer values.
3.4 Restrictions
The following GMM and SM procedures are not supported:
.
Network-requested PDP Context Activation
. Acknowledged mode data transfer is not supported in GTP. This
affects the use of the QoS parameter.
.
SGSN - MS Interface Description, Subnetwork Dependent
Convergence Protocol (SNDCP) and
. SGSN - MS Interface Description, Logical Link Control (LLC).