b70
b70
b70
3GPP TS 29.018
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this
Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
Release 11
Keywords
GSM, UMTS, network, VLR, layer 3, GPRS
3GPP
Postal address
3GPP support office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
2013, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
All rights reserved.
UMTS is a Trade Mark of ETSI registered for the benefit of its members
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM and the GSM logo are registered and owned by the GSM Association
3GPP
Release 11
Contents
Contents....................................................................................................................................................3
Foreword...................................................................................................................................................7
Introduction...............................................................................................................................................7
1 Scope......................................................................................................................................................8
2 References..............................................................................................................................................8
2.1 Normative references.............................................................................................................................................8
2.2 Informative references...........................................................................................................................................9
3GPP
Release 11
13 HLR failure........................................................................................................................................28
13.1 General description............................................................................................................................................28
13.2 Procedures in the SGSN.....................................................................................................................................28
14 MS Information procedure.................................................................................................................28
14.1 General description............................................................................................................................................28
14.2 Procedures in the VLR.......................................................................................................................................28
14.3 Procedures in the SGSN.....................................................................................................................................29
15 MM information procedure................................................................................................................29
15.1 General description............................................................................................................................................29
15.2 Procedures in the VLR.......................................................................................................................................29
15.3 Procedures in the SGSN.....................................................................................................................................29
3GPP
Release 11
17.1.2.1 Gs Cause.......................................................................................................................................................32
17.1.3 BSSAP+-ALERT-REQUEST message..........................................................................................................32
17.1.4 BSSAP+-DOWNLINK-TUNNEL-REQUEST message................................................................................32
17.1.5 BSSAP+-GPRS-DETACH-ACK message.....................................................................................................33
17.1.6 BSSAP+-GPRS-DETACH-INDICATION message......................................................................................33
17.1.6.1 Cell global identity (A/Gb mode only)........................................................................................................33
17.1.6.2 Service area identification (Iu mode only)...................................................................................................33
17.1.7 BSSAP+-IMSI-DETACH-ACK message.......................................................................................................33
17.1.8 BSSAP+-IMSI-DETACH-INDICATION message........................................................................................34
17.1.8.1 Cell global identity (A/Gb mode only)........................................................................................................34
17.1.8.2 Location information age.............................................................................................................................34
17.1.8.3 Service area identification (Iu mode only)...................................................................................................34
17.1.9 BSSAP+-LOCATION-UPDATE-ACCEPT message....................................................................................34
17.1.9.1 New TMSI, or IMSI.....................................................................................................................................35
17.1.10 BSSAP+-LOCATION-UPDATE-REJECT message...................................................................................35
17.1.10.1 Message definition.....................................................................................................................................35
17.1.10.2 Location area identifier..............................................................................................................................35
17.1.11 BSSAP+-LOCATION-UPDATE-REQUEST message................................................................................35
17.1.11.1 Old location area identifier.........................................................................................................................36
17.1.11.2 New cell global identity.............................................................................................................................36
17.1.11.3 TMSI status................................................................................................................................................36
17.1.11.4 Mobile station classmark............................................................................................................................36
17.1.11.5 New service area identification..................................................................................................................36
17.1.11.6 IMEISV......................................................................................................................................................36
17.1.11.7 TMSI based NRI container........................................................................................................................36
17.1.11.8 Selected CN operator.................................................................................................................................36
17.1.12 BSSAP+-MM-INFORMATION-REQUEST...............................................................................................36
17.1.12.1 MM information.........................................................................................................................................37
17.1.13 BSSAP+-MOBILE-STATUS message.........................................................................................................37
17.1.13.1 IMSI 37
17.1.14 BSSAP+-MS-ACTIVITY-INDICATION message......................................................................................37
17.1.14.1 Cell global identity (A/Gb mode only)......................................................................................................37
17.1.14.2 Service area identification (Iu mode only).................................................................................................37
17.1.15 BSSAP+-MS-INFORMATION-REQUEST message..................................................................................37
17.1.16 BSSAP+-MS-INFORMATION-RESPONSE message................................................................................38
17.1.16.1 IMEI 38
17.1.16.2 IMIESV......................................................................................................................................................38
17.1.16.3 Cell global identity (A/Gb mode only)......................................................................................................38
17.1.16.4 Location information age...........................................................................................................................38
17.1.16.5 Mobile station state....................................................................................................................................38
17.1.16.6 TMSI 38
17.1.16.7 Service area identification (Iu mode only).................................................................................................39
17.1.17 BSSAP+-MS-UNREACHABLE message....................................................................................................39
17.1.17.1 Gs Cause.....................................................................................................................................................39
17.1.18 BSSAP+-PAGING-REJECT message..........................................................................................................39
17.1.19 BSSAP+-PAGING-REQUEST message......................................................................................................39
17.1.19.1 TMSI 40
17.1.19.2 Location area identifier..............................................................................................................................40
17.1.19.3 Channel needed..........................................................................................................................................40
17.1.19.4 eMLPP priority...........................................................................................................................................40
17.1.19.5 Global CN-Id..............................................................................................................................................40
17.1.20 BSSAP+-RESET-ACK message..................................................................................................................40
17.1.20.1 SGSN number............................................................................................................................................41
17.1.20.2 VLR number...............................................................................................................................................41
17.1.21 BSSAP+-RESET-INDICATION message...................................................................................................41
17.1.21.1 SGSN number............................................................................................................................................41
17.1.21.2 VLR number...............................................................................................................................................41
17.1.22 BSSAP+-TMSI-REALLOCATION-COMPLETE message........................................................................41
17.1.22.1 Cell global identity (A/Gb mode only)......................................................................................................41
17.1.22.2 Service area identification (Iu mode only).................................................................................................42
17.1.23 BSSAP+-UPLINK-TUNNEL-REQUEST message.....................................................................................42
3GPP
Release 11
Annex A (informative):
Change history......................................................................................59
3GPP
Release 11
Foreword
This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
The present document specifies procedures used between the Serving GPRS Support Node (SGSN) and the Visitors
Location Register (VLR) for co-ordination between GSM circuit switched services and GSM packet data services
within the 3GPP system.
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The present document specifies or references the procedures to provide co-ordination between the GSM circuit
switched services controlled at the Visitors Location Register (VLR) and the GSM packet switched services controlled
at the Serving GPRS Support Node (SGSN). The procedures specified in the present document are intended to optimise
the use of the resources when an MS supports both GSM circuit switched services and GSM packet switched services.
3GPP
Release 11
Scope
The present document specifies or references procedures used on the Serving GPRS Support Node (SGSN) to Visitors
Location Register (VLR) interface for interoperability between GSM circuit switched services and GSM packet data
services.
The present document specifies the layer 3 messages and procedures on the Gs interface to allow coordination between
databases and to relay certain messages related to GSM circuit switched services over the GPRS subsystem.
The functional split between VLR and SGSN is defined in 3GPP TS 23.060 [8]. The required procedures between VLR
and SGSN are defined in detail in the present document.
References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[Void]
[1a]
[2]
[Void]
[3]
[Void]
[4]
[Void]
[5]
[6]
[6a]
[7]
[Void]
[8]
3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[9]
[Void]
[10]
[Void]
[11]
3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[11a]
3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[12]
3GPP TS 44.064: "Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link
Control (LLC) layer specification".
[13]
[Void]
3GPP
Release 11
[14]
3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC-BSS) interface;
Layer 3 specification".
[15]
3GPP TS 48.018: "Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS
Protocol (BSSGP)".
[16]
[Void]
[17]
[18]
[Void]
[19]
[Void]
[20]
[Void]
[21]
[Void]
[22]
[23]
[23A]
[24]
[25]
3GPP TS 32.422: "Subscriber and equipment trace; Trace control and Configuration Management
(CM)".
[26]
3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple
Core Network (CN) nodes".
[27]
3GPP TS 29.118: "Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs
interface specification".
[28]
3GPP TS 29.272: "MME and SGSN Related Interfaces Based on Diameter Protocol".
[Void]
[23B]
[Void]
[24]
[Void]
[25]
[Void]
[26]
[Void]
[27]
[Void]
[28]
[Void]
[29]
[Void]
[30]
[Void]
[31]
[Void]
[32]
[Void]
[33]
[Void]
[34]
[Void]
[35]
[Void]
[36]
[Void]
3GPP
Release 11
10
[37]
[Void]
[38]
[Void]
[39]
[Void]
[40]
[Void]
[41]
[Void]
[42]
[Void]
[43]
[Void]
[44]
[Void]
[45]
[Void]
[46]
[Void]
[47]
[Void]
[48]
[Void]
[49]
[Void]
[50]
[Void]
[51]
[Void]
[52]
[Void]
[53]
[Void]
[54]
[Void]
[55]
[Void]
[56]
[Void]
[57]
[Void]
[58]
[Void]
[59]
[Void]
[60]
[Void]
[61]
[Void]
[62]
[Void]
[63]
[Void]
[64]
[65]
[Void]
[66]
[Void]
For the purposes of the present document the definitions, symbols and abbreviations given in 3GPP TR 21.905 [1a] and
in 3GPP TS 23.060 [8] apply. Additionally the following terms and definitions of 3GPP TS 23.251 [24] apply:
Common PLMN
Gateway core network (GWCN)
3GPP
Release 11
11
Non-supporting UE
Supporting UE
The Gs interface connects the databases in the MSC/VLR and the SGSN. The procedures described in the present
document are used to co-ordinate the location information of MSs that are IMSI attached to both GPRS and non-GPRS
services. The Gs interface is also used to convey some circuit switched related procedures via the SGSN.
The basis for the interworking between a VLR and an SGSN is the existence of an association between those entities
per MS. An association consists of the SGSN storing the number of the VLR serving the MS for circuit switched
services and the VLR storing the number of the SGSN serving the MS for packet switched services. The association is
only applicable to MSs in class-A mode of operation and MSs in class-B mode of operation. The Gs association is not
applicable if the subscriber data indicates that the MS has subscription for packet only. The Gs association is also not
applicable if the MS requests only for GPRS services and "SMS-only service" and SMS service is to be provided by the
SGSN based on conditions specified in 3GPP TS 23.060 [8].
All the messages described in the present document use the SCCP class 0 connectionless service.
When the return option in SCCP is used and the sender receives an N_NOTICE indication from SCCP, the sending
entity shall report to the Operation and Maintenance system (see ITU-T Recommendation Q.714 [64]).
The behaviour of the VLR and the SGSN entities related to the Gs interface are defined by the state of the association
for an MS. Individual states per association, i.e. per MS in class-A mode of operation and MS in class-B mode of
operation, are held at both the VLR and the SGSN.
3GPP
Release 11
NOTE:
12
Receipt of a BSSAP+-RESET-INDICATION message from the SGSN may change or not the state of the
Gs interface of all the associations associated to the restarted SGSN, see subclause 12.3.
Boolean
Set to 'false' when the SGSN has received a reset indication from the VLR. The SGSN may request to the MS,
upon reception of the next routeing area update (either periodic routeing area update or combined routeing and
location area update) procedure, to re-attach to non-GPRS services if the MS is still IMSI attached to non-GPRS
services. Alternatively the SGSN may upon reception of a combined routeing and location area update request or
a periodic routeing area update from a MS that is still attached for non-GPRS service, perform immediately the
location update for non-GPRS services procedure.
EMM Combined UE Waiting Flag:
Boolean
the SGSN receives a Detach Notification indicating "Local Detach" for an MS which supports EMM
Combined procedures from the associated MME; or
the SGSN receives the request from the Serving GW for deactivating the last PDP context for an MS which
supports EMM Combined procedures.
On the fifth expiry of timer T3322 described as T3322 time-out in 3GPP TS 24.008 [11], the EMM Combined
UE Waiting Flag shall be deactivated if it is activated.
SGSN-Reset:
Boolean
Set to 'true' when the SGSN restarts after a failure. The 'SGSN-Reset' variable is unique within an SGSN and it
applies to all the MM context stored in the SGSN.
3GPP
Release 11
13
3GPP
Release 11
14
5.2.4 MS unreachable
On receipt of a BSSAP+-MS-UNREACHABLE message before the timer T5 expires, the VLR stops timer T5 and the
paging procedure for that paging request towards the SGSN is stopped. The state of the association at the VLR is not
changed.
If the MS is considered to be IMSI attached for GPRS and non-GPRS services (i.e. the association is not in
the state Gs-NULL), the SGSN shall page the MS based on the location information stored in the SGSN. If
the location area stored in the SGSN differs from the one received in the BSSAP+-PAGING-REQUEST
message, the SGSN shall use the IMSI to page the MS. If the BSSAP+-PAGING-REQUEST message does
not include the Location area identifier information element, the SGSN may set the "VLR-Reliable" MM
context variable to "false".
If the MS is marked as IMSI detached for GPRS services or IMSI (implicitly or explicitly) detached for nonGPRS services (i.e. the state of the association is Gs-NULL), the SGSN shall return a BSSAP+-PAGINGREJECT message to that VLR indicating in the Gs Cause IE the detach circumstance ('IMSI detached for
3GPP
Release 11
15
GPRS services', 'IMSI detached for non-GPRS services' or 'IMSI implicitly detached for non-GPRS
services').
-
If the MS is marked as unreachable (i.e. the PPF flag is set to 'false') the SGSN shall return a BSSAP+-MSUNREACHABLE message to that VLR indicating in the Gs Cause IE 'MS unreachable'. The state of the
association does not change at the SGSN.
b) The MS is known and the restoration indicator 'SGSN-Reset' at the SGSN is set to 'true':
-
If the BSSAP+-PAGING-REQUEST message includes the Location area identifier IE, the SGSN shall page
the MS in all the routeing areas served by the SGSN that are included in the location area indicated in the
Location area identifier IE.
If the BSSAP+-PAGING-REQUEST message does not include the Location area identifier IE, the SGSN
may page in all the routeing areas served by the SGSN that are also served by the sending VLR.
NOTE 1: The SGSN can handle the paging request as a) for the purpose of optimization if the MS is known.
c) The MS is not known and the restoration indicator 'SGSN-Reset' at the SGSN is set to 'false':
-
The SGSN shall return a BSSAP+-PAGING-REJECT message to that VLR indicating in the Gs Cause IE
'IMSI unknown'.
d) The MS is not known and the restoration indicator 'SGSN-Reset' at the SGSN is set to 'true':
-
If the VLR provides the Location area identifier IE, the SGSN shall page within the location area indicated
by the VLR. Otherwise the SGSN may page in all the routeing areas served by the SGSN that are also served
by the sending VLR.
If the SGSN accepts the paging request, the SGSN shall process the BSSAP+-PAGING-REQUEST message before
sending the message on the Gb interface. The result of the processing on the BSSAP+-PAGING-REQUEST message is
the PAGING CS message (see 3GPP TS 48.018 [15]) sent on the Gb interface.
The SGSN shall not retransmit the PAGING CS message.
If within a location area there are cells that do not support GPRS services, the SGSN shall group these cells under a
'null RA'. The SGSN will perform the paging procedure described above within both the RA(s) derived from the
location information and the 'null RA(s)' of the corresponding location area(s) (see 3GPP TS 24.008 [11]).
NOTE 2: The eMLPP priority information element relates to relative priorities within the paged MS and not to the
priority in the sending of PAGING CS messages by the BSS.
the subscriber data indicates that the MS has subscription for packet only;
the MS indicates SMS only and the HLR indicates "SMS in SGSN Support" and the SGSN supports SMS
services.
NOTE:
For the cases specified above, the registration with a VLR is not required and the SGSN does not initiate
the location update for non-GPRS services procedure.
IMSI attach for non-GPRS services if the MS is already IMSI attached for GPRS services;
IMSI attach for GPRS services indication to the VLR if the MS is already IMSI attached for non-GPRS services;
3GPP
Release 11
16
Normal Location Update procedure to the VLR if the MS is IMSI attached for both GPRS and non-GPRS
services;
The Location Update for non-GPRS services procedures in the Gs interface is always started as a consequence of a
direct action by the MS. The combined routeing area update procedure is further specified in 3GPP TS 23.060 [8] and
3GPP TS 24.008 [11].
The Location Update for non-GPRS services procedure is used by the SGSN to forward to the VLR those parts of the
combined routeing area update or IMSI attach procedure which belong to the non-GPRS services. This means that nonGPRS related requests which are included in the combined request, are sent from the SGSN to the VLR. The procedure
is also used by the SGSN to indicate to the VLR when an IMSI attach to GPRS services has been performed by an MS
that was already IMSI attached to non-GPRS services. The SGSN may also forward a BSSAP+-TMSIREALLOCATION-COMPLETE message from the MS to the VLR.
The VLR shall acknowledge the BSSAP+-LOCATION-UPDATE-REQUEST message. When the VLR processes the
request it does not perform authentication because it relies on the SGSN's security functions.
When an MS is IMSI attached for GPRS and non-GPRS services, any implicit detach timer in the VLR shall be
stopped. Instead the Paging Proceed Flag in the SGSN is used to determine the likely availability of the MS to the
network. Upon reception of the periodic Routeing Area Update message the SGSN does not report to the VLR , and the
state of the association at the SGSN is not changed. When the MS performs a detach only from the GPRS system, and
the VLR's implicit detach timer is not already running, the GPRS detach indication to the VLR shall cause the VLR's
implicit detach timer to be restarted from its initial value.
If the SGSN performs an implicit detach for both GPRS and non-GPRS traffic, then the SGSN shall indicate to the VLR
a BSSAP+-IMSI-DETACH-INDICATION message with cause 'Implicit SGSN initiated IMSI detach from GPRS and
non-GPRS service', as further described in clause 'Implicit IMSI detach from non-GPRS service procedure' (the implicit
IMSI detach message indicates that the MS is unavailable for both GPRS and non-GPRS services).
The IMSI attach for GPRS services to the VLR, when the MS is already IMSI attached for non-GPRS services, is
requested by the MS sending a combined IMSI attach for GPRS and non-GPRS services message to the SGSN, as
further specified in 3GPP TS 23.060 [8] and 3GPP TS 24.008 [11].
if the Network Access Mode (NAM) subscription data indicates that the MS has subscription for packet only
(see 3GPP TS 29.272 [28]); or
if the combined attach or routing area update procedure indicates that the MS has requested for GPRS services
and "SMS-only service" (see 3GPP TS 24.008 [11]) and the HLR indicates "SMS in SGSN Support" and the
SGSN supports SMS services.
Otherwise, the SGSN shall start the location update for non-GPRS services procedure and wait for the outcome of both
location update procedures towards the VLR and the HLR before sending the response message to the MS (see
3GPP TS 24.008 [11]).
Upon reception of the periodic Routeing Area Update message, if the EMM Combined UE Waiting Flag is 'true', the
SGSN shall perform network-initiated GPRS detach procedure with the detach type IE indicating "IMSI detach" as
specified in 3GPP TS 24.008 [11].
3GPP
Release 11
17
a Combined Routeing and Location Area Update request indicating IMSI attach;
a Combined Routeing and Location Area Update request indicating that the Location Area has changed;
a Combined Routeing and Location Area Update request if the MS Network Capability IE indicates that EMM
Combined procedures are supported by the MS;
a Combined Routeing and Location Area Update request, if the state of the association is Gs-NULL; or
a Combined Routeing and Location Area Update request when the SGSN serving the MS has changed.
If timer T6-1 is not running, the SGSN may start the Location Update for non-GPRS service procedure when it receives
from the MS:
a Combined Routeing and Location Area Update request or a periodic Routeing Area Update, if the 'VLRReliable' MM context variable for the MS is set to 'false' (see section 11.3).
For networks not supporting the feature Intra Domain Connection of RAN Nodes to Multiple CN Nodes the number
of the VLR is derived from the RAI where the MS is camping. For networks supporting the feature Intra Domain
Connection of RAN Nodes to Multiple CN Nodes, the VLR number is derived as described in 3GPP TS 23.236 [26].
The SGSN starts Timer T6-1. The BSSAP+-LOCATION-UPDATE-REQUEST message includes the Old location area
identifier. If the SGSN received the Old location area identification from the MS and the network supports S1 mode, the
SGSN includes the Old location area identification received from the MS as the Old location area identifier. If the
SGSN did not receive the Old location area identification from the MS or if the network does not support S1 mode, the
SGSN derives the Old location area identifier from the Old routing area identification received in the ROUTING AREA
UPDATING REQUEST message (see 3GPP TS 24.008 [11]). The SGSN shall also include the new Location Area
Identifier where the MS is currently camping. The new LAI is derived from the RAI.
If the VLR is configured for gateway core network (GWCN), the SGSN shall select a core network operator as
specified in 3GPP TS 23.251 [24] and proceed as follows:
-
For supporting UEs, the SGSN includes the PLMN identity of the selected core network operator in the New cell
global identity information element.
For non-supporting UEs, the SGSN includes the selected core network operator in the Selected CN operator
information element in the BSSAP+-LOCATION-UPDATE-REQUEST message, and the common PLMN in
the New cell global identity information element.
In networks supporting the feature 'Intra Domain Connection of RAN Nodes to Multiple CN Nodes'
(3GPP TS 23.236 [26]), if the TMSI based NRI container is not received from the MS, and the SGSN determines that
the serving VLR of the MS is changed, the SGSN shall include in the Old location area identifier a specific LAI value
which is not broadcasted in the network and not associated with any VLR.
NOTE 1: The SGSN determines that the serving VLR of the MS is changed when the Gs association changes from
one serving VLR to a different one, or based on implementation dependent criteria.
NOTE 2: When the VLR receives the BSSAP+-LOCATION-UPDATE-REQUEST message with the specific LAI
value, the VLR retrieves the MM context of the MS from the HLR.
In networks supporting the feature Intra Domain Connection of RAN Nodes to Multiple CN Nodes, the SGSN shall
support load re-distribution of MSs to another VLR than the current one as follows:
When the SGSN receives a periodic Routeing Area Update request or a Combined Routeing and Location Area
Update request, the SGSN shall check whether for this MS there is an association to a VLR for which load redistribution has been initiated in the SGSN by O&M. If yes, the SGSN derives the new VLR number as
3GPP
Release 11
18
described in 3GPP TS 23.236 [26]. The SGSN shall then send the BSSAP+-LOCATION-UPDATE-REQUEST
message to the new selected VLR.
The BSSAP+-LOCATION-UPDATE-REQUEST message includes the type of location update performed by the MS in
the GPRS location update type IE. If the MS has performed a combined attach request or a combined routing and
location area update request with IMSI attach, the SGSN indicates 'IMSI attach', otherwise the SGSN indicates 'Normal
location update'.
The BSSAP+-LOCATION-UPDATE-REQUEST message shall include the TMSI status if received from the MS.
The SGSN shall include the TMSI based NRI container in the BSSAP+-LOCATION-UPDATE-REQUEST message if
received from the MS.
If the SGSN supports the "Provision of UE Specific Behaviour Information to Network Entities" (see 3GPP TS 23.195
[23]), or the Automatic Device Detection (see 3GPP TS 22.101 [23A]) or the Trace for Management Based
Activation/Deactivation (see 3GPP TS 32.422 [25]),, the BSSAP+-LOCATION-UPDATE-REQUEST message shall
include the IMEISV.
If timer T6-1 is running:
If the SGSN receives from the MS:
-
a Combined Routeing and Location Area Update request with or without IMSI attach.
Then:
-
if the new LAI is the same as in the outstanding request, the SGSN shall not process this new request and shall
wait for the VLR's response to the ongoing procedure; or
if the new LAI is different but is in the same VLR as the outstanding request:
The SGSN shall start the Location Update for non-GPRS service procedure; or
if the new LAI is different, and is in a different VLR to the outstanding request:
-
any response from the previously addressed VLR to the oustanding request is ignored;
the SGSN shall start the Location Update for non-GPRS service procedure.
When the SGSN receives from the MS a Routeing Area Update request and the SGSN serving the MS has changed, the
SGSN shall stop and reset timer T6-1.
set the the MM context variable 'EMM Combined UE Waiting Flag' to 'false'; and
indicate to the MS the acceptance of the VLR to the Location Update procedure. The message to the MS
includes the Routeing Area Identity, from which the MS is able to extract the location area identity for which the
location update procedure succeeded (see 3GPP TS 24.008 [11]).
3GPP
Release 11
19
The SGSN shall wait for the outcome of the Location Update for non-GPRS service procedure towards the VLR before
sending a response to location update procedure to the MS. Any Reject cause that needs to be reported to the MS is
specified in 3GPP TS 24.008 [11].
If the VLR included the Mobile Identity IE in the BSSAP+-LOCATION-UPDATE-ACCEPT message, the SGSN shall
forward the information received to the MS. If the Mobile Identity IE contains a new TMSI it will cause the MS to
perform a TMSI reallocation procedure, while an IMSI causes the MS to deallocate its TMSI. In case a new TMSI was
allocated for the MS the SGSN shall send to the VLR the BSSAP+-TMSI-REALLOCATION-COMPLETE message
when the SGSN receives Attach Complete or the the Routeing Area Complete message from the MS.
indicate to the MS the rejection of the VLR of the Location Update procedure as specified in 3GPP TS
24.008 [11]. The Reject cause value sent by the VLR shall be forwarded to the MS.
if the state of the association to the VLR is GS-ASSOCIATED, the message shall be ignored; or
if the state of the association to the VLR is different than GS-ASSOCIATED, the message shall be treated as
a message incompatible with the protocol state of the SGSN (see clause 16.3).
If the Selected CN operator information element is not received in the BSSAP+-LOCATION-UPDATEREQUEST message and the PLMN identity included in the New cell global identity information element
identifies a core network operator, the VLR shall select the serving core network operator as specified in the
New cell global identity information element;
Otherwise, the VLR selects the serving core network operator based on local policies.
3GPP
Release 11
20
For a VLR supporting the "Provision of UE Specific Behaviour Information to Network Entities" (see 3GPP TS 23.195
[23]) the following applies:
-
The VLR shall store the IMEISV value received in the BSSAP+-LOCATION-UPDATE-REQUEST message in
the MM context for that MS.
update the association by storing the SGSN number included in the BSSAP+-LOCATION-UPDATE-REQUEST
message; and
send a BSSAP+-LOCATION-UPDATE-ACCEPT message to the sending SGSN. This message includes the
Location Area Identification received in the new Cell Global Identity IE in the previous BSSAP+-LOCATIONUPDATE-REQUEST message.
Send a BSSAP+-LOCATION-UPDATE-REJECT message to the SGSN with the appropriate reject cause as
indicated in 3GPP TS 24.008 [11] and indicate to the SGSN the Location area identifier received in the
corresponding BSSAP+-LOCATION-UPDATE-REQUEST message; and
In the BSSAP+-LOCATION-UPDATE-REQUEST the SGSN may indicate, that there is no valid TMSI
available in the MS. This information may be used by the VLR to decide whether to reallocate a new
TMSI to the MS.
Upon receipt of the BSSAP+-TMSI-REALLOCATION-COMPLETE message, the VLR stops the timer T6-2 and
considers the new TMSI as valid.
If an IMSI was sent to the MS, the VLR considers the old TMSI as deleted.
If no BSSAP+-TMSI-REALLOCATION-COMPLETE message is received by the VLR before the timer T6-2 expires,
the VLR aborts the TMSI reallocation procedure. The VLR shall consider old TMSI occupied until the new TMSI is
used in a subsequent A/Iu message, or for an implementation dependent time. The VLR may still perform the TMSI
reallocation procedure via the A or Iu-CS interface. The outcome of the TMSI reallocation procedure does not change
the state of the association. The VLR uses the IMSI or the new TMSI or, if available, the old TMSI for paging.
3GPP
Release 11
21
If the VLR receives a Location Update request or an IMSI detach indication from the MS by the A or Iu-CS
interface when the state of the association in the VLR is not Gs-NULL, the VLR shall move the state of the
association to Gs-NULL.
ii) Additional Location Update Request
If the state of the association in the VLR is in the LA-UPDATE PRESENT state and a BSSAP+-LOCATIONUPDATE-REQUEST message is received, then:
-
If the message is from the same SGSN and indicates the same New Location Area as the outstanding location
update request, then this additional BSSAP+-LOCATION-UPDATE-REQUEST message shall be ignored;
If the message is from the same SGSN but indicates a different New Location Area to the outstanding
location update request, then this additional BSSAP+-LOCATION-UPDATE-REQUEST message shall be
treated and the VLR shall not send any response to the previous BSSAP+-LOCATION-UPDATEREQUEST message; or
If the message is from a different SGSN (indicating either the same or different New Location Area) to the
outstanding location update request, then this additional BSSAP+-LOCATION-UPDATE-REQUEST
message shall be treated and the VLR shall not send any response to the previous BSSAP+-LOCATIONUPDATE-REQUEST message.
3GPP
Release 11
22
3GPP
Release 11
23
The combined Routing and Location Area Update procedure is rejected at the SGSN; or
The periodic Routing Area Update procedure is rejected at the SGSN for an MS for which a Gs association
exists.
If the SGSN receives a Detach Request from an MS and the state of the association to a VLR for that MS is not GsNULL, the SGSN shall check the detach type indicated in the message. If the MS is indicating GPRS detach the SGSN
shall send a BSSAP+-GPRS-DETACH-INDICATION message to the VLR indicating 'MS initiated IMSI detach from
GPRS service'.
If the SGSN decides to perform a network-initiated GPRS detach and the state of the association to a VLR for that MS
is not Gs-NULL, the SGSN shall send a BSSAP+-GPRS-DETACH-INDICATION message to the VLR indicating
'Network initiated IMSI detach from GPRS service'.
If the combined Routing and Location Area Update procedure or periodic Routing Area Update procedure is rejected at
the SGSN for an MS with an association state different from Gs-NULL, the SGSN shall send a BSSAP+-GPRSDETACH-INDICATION to the VLR indicating 'GPRS services not allowed'. The SGSN then sends, for example, a
Routing Area Update Reject message as specified in 3GPP TS 24.008 [11].
After the sending of the BSSAP+-GPRS-DETACH-INDICATION message, the SGSN shall move the state of the
association to Gs-NULL. The SGSN shall start timer T8 upon transmission of the BSSAP+-GPRS-DETACHINDICATION message and if timer T6-1 is running, timer T6-1 shall be stopped and reset.
3GPP
Release 11
24
3GPP
Release 11
25
If the SGSN sent a BSSAP+-IMSI-DETACH-INDICATION message for a combined IMSI and GPRS detach due to
switch off and timer T9 expires, the SGSN shall repeat the BSSAP+-IMSI-DETACH-INDICATION message a
maximum of N9 times.
ii) with no switch off
If the SGSN sent a BSSAP+-IMSI-DETACH-INDICATION message for a IMSI only detach or a combined IMSI and
GPRS detach not due to switch off and timer T9 expires, the SGSN shall repeat the BSSAP+-IMSI-DETACHINDICATION message a maximum of N9 times. If no BSSAP+-IMSI-DETACH-ACK is received after that the SGSN
shall send the confirmation of the detach to the MS.
10
3GPP
Release 11
26
11
The VLR shall move the state of the association for the MS to Gs-NULL. If the VLR does not have a signalling
connection for the MS, the VLR shall mark the MS as detached. Additionally, the VLR marks the association as
'IMSI implicitly detached for GPRS and non-GPRS services'.
3GPP
Release 11
27
request the MS to re-attach for non-GPRS services as specified in 3GPP TS 24.008 [11] and then select an
alternative VLR that is in service for the MS during the subsequent combined routeing area update procedure,
before performing the location update for non-GPRS services procedure towards the selected VLR as described
in clause 6; or
select an alternative VLR that is in service for the MS and immediately perform the location update for nonGPRS services procedure towards the selected VLR as described in clause 6.
NOTE:
12
The option to not send any BSSAP+-RESET-INDICATION message to all the VLRs connected to the
SGSN by Gs interfaces reduces subsequent paging signalling initiated by VLRs by avoiding a complete
search of the MS on the entire VLR area.
3GPP
Release 11
28
set the 'Confirmed by Radio Contact' restoration indicator to 'false' in all the associations containing the restarted
SGSN and set the state of all the Gs associations containing the restarted SGSN to the Gs-NULL state; or
keep the 'Confirmed by Radio Contact' restoration indication and the state of all the Gs associations containing
the restarted SGSN unchanged.
NOTE:
The option to not set the 'Confirmed by Radio Contact' restoration indicator to 'false' in all the
associations containing the restarted SGSN reduces subsequent paging signalling the VLR can initiate by
avoiding a complete search of the MS on the entire VLR area.
13
HLR failure
This clause decribes the SGSN behaviour towards the VLR as a consequence of an HLR reset.
14
MS Information procedure
3GPP
Release 11
29
REQUEST message to the SGSN. If the state of the association is LA-UPDATE PRESENT, the VLR shall wait until
this state is exited. The VLR starts the timer T14. The BSSAP+-MS-INFORMATION-REQUEST message specifies
the requested information parameters in the Information requested information element.
Upon receipt of a BSSAP+-MS-INFORMATION-RESPONSE the VLR shall stop timer T14. If no BSSAP+-MSINFORMATION-RESPONSE for that MS is received before the expiry of timer T14the VLR shall stop the Gs
interface MS information procedure. The VLR may perform other actions to obtain the information about the MS (e.g.
retry, or send a DTAP IDENTITY REQUEST message on the A interface).
15
MM information procedure
For the determination of the number of time zones, both CS and PS domain are taken into account.
If the network spans more than one time zone, the SGSN shall check and update the contents of the MM information
information element as follows:
3GPP
Release 11
30
if Network Daylight Saving Time has been included in the MM information, then the SGSN shall discard the
Network Daylight Saving Time;
if Local Time Zone has been included in the MM information, then the SGSN shall replace the Local Time Zone
with the Local Time Zone applicable for this MS. In addition, if the local time zone in the SGSN has been
adjusted for daylight saving time, the SGSN shall indicate this by including the value used for adjustment in
Network Daylight Saving Time IE in the MM information;
if Universal time and local time zone has been included in the MM information, then the SGSN shall replace it
with the Universal time and local time zone applicable for this MS. In addition, if the local time zone in the
SGSN has been adjusted for daylight saving time, the SGSN shall indicate this by including the value used for
adjustment in Network Daylight Saving Time IE in the MM information; and
The SGSN shall then send the resultant MM-INFORMATION message to the MS indicated.
16
16.1 General
This clause specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving
entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for
error situations they define a compatibility mechanism for future extensions of the protocol.
In this clause the following terminology is used:
-
an IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved",
or if its value part violates coding rules. However, it is not a syntactical error that an IE specifies in its Length
Indicator a greater length than defined in the relevant clause; and
a message is defined to have semantically incorrect contents if it contains information which, possibly dependant
on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part of
3GPP TS 29.018.
When a receiving entity detects the need to send a BSSAP+-MOBILE-STATUS message (see errors detailed below),
the entity shall copy the IMSI IE value (if included) of the incorrect message to the IMSI IE on the BSSAP+-MOBILESTATUS message. The message in error is also included in the BSSAP+-MOBILE-STATUS message. Both the
receiving and the sending entity shall abandon the procedure related to the incorrect message and return to the state
from where the procedure related to the incorrect message was started.
A BSSAP+-MOBILE-STATUS message shall not be sent in response to a received BSSAP+-MOBILE-STATUS
message.
Both the receiving and the sending entity shall inform the O&M entity upon sending or receiving a BSSAP+-MOBILESTATUS message.
The next clauses in this clause shall be applied in order of precedence.
3GPP
Release 11
31
If a message is received that is not defined to be received by that entity (i.e. the message is sent in the wrong direction)
it shall be treated as unknown message and the message shall be ignored. A BSSAP+-MOBILE-STATUS message with
the Gs Cause Value set to "message unknown" and the Erroneous message IE containing the received message shall be
returned.
3GPP
Release 11
17
32
This clause defines the structure of the messages that are sent between the SGSN and the VLR.
Type/Reference
Message type
18.2
IMSI
18.4.10
Presence
M
Format
V
Length
1
TLV
6-10
17.1.2.1
Type/Reference
Message type
18.2
IMSI
18.4.10
Gs Cause
18.4.7
Presence
M
Format
V
Length
1
TLV
6-10
TLV
Gs Cause
The value part which is typically sent for this information element in this message is 'IMSI unknown'.
Type/Reference
Message type
18.2
IMSI
18.4.10
Presence
M
Format
1
Length
TLV
6-10
3GPP
Release 11
33
Type/Reference
Message type
18.2
IMSI
IMSI
18.4.10
VLR number
VLR number
18.4.26
Downlink Tunnel Payload Control and Downlink Tunnel Payload Control and
Info
Info
18.4.3
Presence
M
Format
1
Length
TLV
6-10
TLV
5-11
TLV
3-223
Type/Reference
Message type
18.2
IMSI
18.4.10
Presence
M
Format
V
Length
1
TLV
6-10
17.1.6.1
Type/Reference
Message type
18.2
IMSI
18.4.10
SGSN number
18.4.22
IMSI detach from GPRS service type
18.4.11
Cell global identity
18.4.1
Service area identification
18.4.21b
Presence
M
Format
V
Length
1
TLV
6-10
TLV
5-11
TLV
TLV
10
TLV
In A/Gb mode, the SGSN shall include the Cell global identity where the mobile was in the last radio contact.
17.1.6.2
In Iu mode, the SGSN should include the Service area identification where the mobile was in the last radio contact.
3GPP
Release 11
34
Type/Reference
Message type
18.2
IMSI
18.4.10
Presence
M
Format
V
Length
1
TLV
6-10
17.1.8.1
Type/Reference
Message type
18.2
IMSI
18.4.10
SGSN number
18.4.22
IMSI detach from non-GPRS service
type 18.4.12
Cell global identity
18.4.1
Location information age
18.4.15
Service area identification
18.4.21b
Presence
M
Format
V
Length
1
TLV
6-10
TLV
5-11
TLV
TLV
10
TLV
TLV
In A/Gb mode, the SGSN shall include the Cell global identity where the mobile was in the last radio contact.
17.1.8.2
If the detach is due to implicit detach and the Cell global identity is available, then the SGSN should include the
Location information age.
17.1.8.3
In Iu mode, the SGSN should include the Service area identification where the mobile was in the last radio contact.
Type/Reference
Message type
18.2
IMSI
18.4.10
Location area identifier
18.4.14
Mobile identity
18.4.17
3GPP
Presence
M
Format
V
Length
1
TLV
6-10
TLV
TLV
6-10
Release 11
17.1.9.1
35
This information element represents the identity to be used for (and then by) the MS.
If this information element is an IMSI, then the mobile station is not allocated any TMSI (and deletes any TMSI
accordingly). If this information element is a TMSI, then the mobile station will use this TMSI as the new temporary
identity (the MS deletes its old TMSI and stores the new TMSI). If neither a TMSI nor an IMSI are included in this
information element, the old TMSI, if any available, will be kept.
Message definition
This message is sent by the VLR to the SGSN to indicate that location update or IMSI attach has failed.
Table 17.1.10/3GPP TS 29.018: BSSAP+-LOCATION-UPDATE-REJECT message content
Information Element
Message type
IMSI
Reject cause
Location area identifier
17.1.10.2
Type/Reference
Message type
18.2
IMSI
18.4.10
Reject cause
18.4.21
Location area identifier
18.4.14
Presence
M
Format
V
Length
1
TLV
6-10
TLV
TLV
Type/Reference
Message type
18.2
IMSI
18.4.10
SGSN number
18.4.22
GPRS location update type
18.4.6
Cell global identity
18.4.1
Mobile station classmark 1
18.4.18
Location area identifier
18.4.14
TMSI status
18.4.24
Service area identification
18.4.21b
IMEISV
18.4.9
TMSI based NRI container
18.4.28
Selected CN operator
18.4.29
3GPP
Presence
M
Format
V
Length
1
TLV
6-10
TLV
5-11
TLV
TLV
10
TLV
TLV
TLV
TLV
TLV
10
TLV
TLV
Release 11
17.1.11.1
36
17.1.11.2
In A/Gb mode, the cell global identity which shall be included is the one where the MS is in the current radio contact.
In Iu mode, the cell global identity which shall be included indicates where the MS is in the current location area. The
cell identity part of this information shall be ignored by the VLR.
In a shared network, the PLMN identity contained in the cell global identity shall be the PLMN identity of the selected
core network operator (see 3GPP TS 23.251 [24]).
17.1.11.3
TMSI status
This information element shall be included if the TMSI status received in the ATTACH REQUEST or ROUTING
AREA UPDATING REQUEST message from the MS indicates, that no valid TMSI is available in the MS.
17.1.11.4
This information element does not serve any useful purpose, but shall be included for reasons of compatibility with
earlier versions of the protocol. To ease interworking with old VLR equipment, the SGSN shall encode the contents of
this information element as: revision level 'GSM phase 2', 'early classmark sending supported' 'encryption algorithm
A5/1 supported', and RF power capability 'class 1'.
17.1.11.5
In Iu mode, the service area identification which should be included is the one where the MS is in the current radio
contact.
In a shared network, the PLMN identity contained in the service area identification shall be the PLMN identity of the
selected core network operator (see 3GPP TS 23.251 [24]).
17.1.11.6
IMEISV
This information element shall be included, if the SGSN supports the "Provision of UE Specific Behaviour Information
to Network Entities" or the "Automatic Device Detection", or the Trace for Management Based
Activation/Deactivation.
17.1.11.7
This information element shall be included if the TMSI based NRI container has been received in the ATTACH
REQUEST or ROUTING AREA UPDATING REQUEST message from the MS.
17.1.11.8
Selected CN operator
This information element shall be included for the non-supporting UE if the network is configured to support gateway
core network (GWCN).
17.1.12 BSSAP+-MM-INFORMATION-REQUEST
This message is sent by the VLR to the SGSN to provide the MS with subscriber specific information.
Table 17.1.12/3GPP TS 29.018: BSSAP+-MM-INFORMATION-REQUEST message content
Information Element
Message type
IMSI
MM information
Type/Reference
Message type
18.2
IMSI
18.4.10
MM information
18.4.16
3GPP
Presence
M
Format
V
Length
1
TLV
6-10
TLV
3-n
Release 11
17.1.12.1
37
MM information
17.1.13.1
Type/Reference
Message type
18.2
IMSI
18.4.10
Gs Cause
18.4.7
Erroneous message
18.4.5
Presence
M
Format
V
Length
1
TLV
6-10
TLV
TLV
3-n
IMSI
If the MS is identified by the IMSI, then this information element shall be included.
17.1.14.1
Type/Reference
Message type
18.2
IMSI
18.4.10
Cell global identity
18.4.1
Service area identification
18.4.21b
Presence
M
Format
V
Length
1
TLV
6-10
TLV
10
TLV
In A/Gb mode, the SGSN shall include the cell global identity where the MS was in the last radio contact.
17.1.14.2
In Iu mode, the SGSN should include the Service area identification where the mobile was in the last radio contact.
Type/Reference
Message type
18.2
IMSI
18.4.10
Information requested
18.4.13
3GPP
Presence
M
Format
V
Length
1
TLV
6-10
TLV
Release 11
38
17.1.16.1
Type/Reference
Message type
18.2
IMSI
18.4.10
TMSI
18.4.23
PTMSI
18.4.20
IMEI
18.4.8
IMEISV
18.4.9
Cell global identity
18.4.1
Location information age
18.4.15
Mobile station state
18.4.19
Service area identification
18.4.21b
Presence
M
Format
V
Length
1
TLV
6-10
TLV
TLV
TLV
10
TLV
10
TLV
10
TLV
TLV
TLV
IMEI
17.1.16.2
IMIESV
17.1.16.3
In A/Gb mode, cell global identity where the MS was in the last radio contact.
This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST
message and if this information is obtainable.
17.1.16.4
17.1.16.5
This information element should be included in this message, irrespective of the information requested.
17.1.16.6
TMSI
3GPP
Release 11
17.1.16.7
39
In Iu mode, service area identification where the MS was in the last radio contact.
This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST
message and if this information is obtainable.
17.1.17.1
Type/Reference
Message type
18.2
IMSI
18.4.10
Gs Cause
18.4.7
Presence
M
Format
V
Length
1
TLV
6-10
TLV
Gs Cause
The value part which is typically sent for this information element in this message is 'MS unreachable'.
Type/Reference
Message type
18.2
IMSI
18.4.10
Gs Cause
18.4.7
Presence
M
Format
V
Length
1
TLV
6-10
TLV
3GPP
Release 11
40
17.1.19.1
Type/Reference
Message type
18.2
IMSI
18.4.10
VLR number
18.4.26
TMSI
18.4.23
Location area identifier
18.4.14
Channel needed
18.4.2
eMLPP Priority
18.4.4
Global CN-Id
18.4.27
Presence
M
Format
V
Length
1
TLV
6-10
TLV
5-11
TLV
TLV
TLV
TLV
TLV
TMSI
This element is omitted in the exceptional case where the IMSI is used instead of the TMSI as a paging address at the
radio interface.
17.1.19.2
If the location area identifier is not included, then the SGSN shall page the MS in all the cells served by the VLR and
the SGSN, unless the SGSN has reliable information about the location of the MS.
17.1.19.3
Channel needed
If the Channel needed Information Element is not present, then the default value is assumed to be "any channel".
17.1.19.4
eMLPP priority
This information element may be included when the subscriber has a subscription for eMLPP.
17.1.19.5
Global CN-Id
If the network supports the Intra Domain Connection of RAN Nodes to multiple CN Nodes functionality, this
information element shall be included when MSC/VLR initiates paging by IMSI, via the Gs interface.
Type/Reference
Message type
18.2
SGSN number
18.4.22
VLR number
18.4.26
3GPP
Presence
M
Format
V
Length
1
TLV
5-11
TLV
5-11
Release 11
41
17.1.20.1
SGSN number
If the SGSN is the sending entity, then it shall indicate its address by including its SGSN number Information Element.
Otherwise (i.e. if the VLR is the sending entity), then the SGSN number Information Element shall not be included.
17.1.20.2
VLR number
If the VLR is the sending entity, then it shall indicate its address by including its VLR number Information Element.
Otherwise (i.e. if the SGSN is the sending entity), then the VLR number Information Element shall not be included.
17.1.21.1
Type/Reference
Message type
18.2
SGSN number
18.4.22
VLR number
18.4.26
Presence
M
Format
V
Length
1
TLV
5-11
TLV
5-11
SGSN number
If the SGSN is the sending entity, then it shall indicate its address by including its SGSN number Information Element.
Otherwise (i.e. if the VLR is the sending entity), then the SGSN number Information Element shall not be included.
17.1.21.2
VLR number
If the VLR is the sending entity, then it shall indicate its address by including its VLR number Information Element.
Otherwise (i.e. if the SGSN is the sending entity), then the VLR number Information Element shall not be included.
17.1.22.1
Type/Reference
Message type
18.2
IMSI
18.4.10
Cell global identity
18.4.1
Service area identification
18.4.21b
Presence
M
Format
V
Length
1
TLV
6-10
TLV
10
TLV
The SGSN shall include the cell global identity where the Mobile Station was in the last radio contact.
3GPP
Release 11
17.1.22.2
42
In Iu mode, the SGSN should include the Service area identification where the mobile was in the last radio contact.
Type/Reference
Message type
18.2
IMSI
18.4.10
SGSN number
18.4.22
Uplink Tunnel Payload Control and
Info
18.4.25
3GPP
Presence
M
Format
V
Length
1
TLV
6-10
TLV
5-11
TLV
3-223
Release 11
18
43
This clause specifies the coding of the Information Elements used in by the BSSAP+ protocol. The spare bits in the
coding of an IE shall be set to zero by the sender and shall be ignored by the receiver.
All unassigned codes (whether omitted or explicitely Unassigned in the text) shall be treated as unknown (see
clause 16).
18.1
Overview
Message type
Unassigned: treated as an unknown Message type.
BSSAP+-PAGING-REQUEST
BSSAP+-PAGING-REJECT
Unassigned: treated as an unknown Message type.
BSSAP+-DOWNLINK-TUNNEL-REQUEST
BSSAP+-UPLINK-TUNNEL-REQUEST
BSSAP+-LOCATION-UPDATE-REQUEST
BSSAP+-LOCATION-UPDATE-ACCEPT
BSSAP+-LOCATION-UPDATE-REJECT
BSSAP+-TMSI-REALLOCATION-COMPLETE
BSSAP+-ALERT-REQUEST
BSSAP+-ALERT-ACK
BSSAP+-ALERT-REJECT
BSSAP+-MS-ACTIVITY-INDICATION
BSSAP+-GPRS-DETACH-INDICATION
BSSAP+-GPRS-DETACH-ACK
BSSAP+-IMSI-DETACH-INDICATION
BSSAP+-IMSI-DETACH-ACK
BSSAP+-RESET-INDICATION
BSSAP+-RESET-ACK
BSSAP+-MS-INFORMATION-REQUEST
BSSAP+-MS-INFORMATION-RESPONSE
Unassigned: treated as an unknown Message type.
BSSAP+-MM-INFORMATION-REQUEST
BSSAP+-MOBILE-STATUS
Unassigned: treated as an unknown Message type.
BSSAP+-MS-UNREACHABLE
3GPP
Reference
18 and 16
17.1.19
17.1.18
18 and 16
17.1.4
17.1.23
17.1.11
17.1.9
17.1.10
17.1.22
17.1.3
17.1.1
17.1.2
17.1.14
17.1.6
17.1.5
17.1.8
17.1.7
17.1.21
17.1.20
17.1.15
17.1.16
18 and 16
17.1.12
17.1.13
18 and 16
17.1.17
Release 11
44
Information element
IMSI
VLR number
TMSI
Location area identifier
Channel Needed
eMLPP Priority
TMSI status
Gs cause
SGSN number
GPRS location update type
Global CN-Id
Unassigned: treated as an unknown IEI.
Mobile station classmark 1
Mobile identity
Reject cause
IMSI detach from GPRS service type
IMSI detach from non-GPRS service type
Information requested
PTMSI
IMEI
IMEISV
Unassigned: treated as an unknown IEI.
MM information
Cell Global Identity
Location information age
Mobile station state
Erroneous message
Downlink Tunnel Payload Control and Info
Uplink Tunnel Payload Control and Info
Service Area Identification
TMSI based NRI container
Unassigned: treated as an unknown IEI.
Reference
18.4.10
18.4.26
18.4.23
18.4.14
18.4.2
18.4.4
18.4.24
18.4.7
18.4.22
18.4.6
18.4.27
18 and 16
18.4.18
18.4.17
18.4.21
18.4.11
18.4.12
18.4.13
18.4.20
18.4.8
18.4.9
18 and 16
18.4.16
18.4.1
18.4.15
18.4.19
18.4.5
18.4.3
18.4.25
18.4.21b
18.4.28
18 and 16
8
7
6
5
4
3
2
1
Octet 1
IEI
Octet 2
Length indicator
Octet 3 The rest of the information element is coded as the the value part of
to
the cell global id IE defined in 3GPP TS 48.018 [15] (not including
Octet 10
3GPP TS 48.018 IEI and 3GPP TS 48.018 length indicator).
3GPP
Release 11
45
Octet 1
Octet 2
Octet 3
4
3
2
1
IEI
Length indicator
The rest of the information element is coded as the IEI part and the
value part of the Channel Needed IE defined in 3GPP TS
44.018 [11a].
8
Octet 1
Octet 2
Octet 3
Octet 4
to
Octet n
Spare
4
IEI
Length indicator
TOM Protocol Discriminator
Tunnel Priority
Tunnel payload
TOM Protocol Discriminator: Identifies the protocol using tunnelling of non-GSM signalling. For coding, see
3GPP TS 44.064 [12].
E:
Cipher Request. When set to 1 indicates that the SGSN shall cipher the payload, when
set to 0 indicates that the SGSN shall not cipher the payload.
Tunnel Priority:
Indicates the priority of the Tunnel Payload. For coding, see table 20.1: Association
between Tunnel Priority and LLC SAPs.
Octet 1
Octet 2
Octet 3
4
3
2
1
IEI
Length indicator
The rest of the information element is coded as the value part of the
eMLPP-Priority IE defined in 3GPP TS 48.008 [14] (not including
3GPP TS 48.008 IEI and 3GPP TS 48.008 length indicator).
3GPP
Release 11
46
8
7
6
5
4
3
2
1
Octet 1
IEI
Octet 2
Length indicator
Octet 3
Erroneous message including the message type.
Octet n
NOTE:
If the size of the erroneous message including the message type
exceeded 255 octets, only the first 255 octets are included.
Octet 1
Octet 2
Octet 3
4
3
IEI
Length indicator
GPRS location update type value
18.4.7 Gs cause
The purpose of the value part of the Gs Cause information element is to indicate an error to the receiving entity. This
could be a protocol data error or to indicate to the VLR the reason why a paging procedure could not be performed.
8
Octet 1
Octet 2
Octet 3
4
IEI
Length indicator
Gs Cause value
3GPP
Release 11
47
'Normal, unspecified' has the same meaning than in 3GPP TS 24.008 [11], informative Annex H (UMTS
specific cause values for call control). It is used to report a normal event, and should not be interpreted as
syntactically incorrect nor unknown if received.
18.4.8 IMEI
The IMEI is coded as a sequence of BCD digits, compressed two into each octet. The IMEI consists of 15 digits (see
3GPP TS 23.003 [5]).
8
octet 1
octet 2
octet 3
octet 4
octet 5
octet 6
octet 7
octet 8
octet 9
octet 10
4
IEI
length indicator
digit 1
digit 3
digit 5
digit 7
digit 9
digit 11
digit 13
0
0
digit 2
digit 4
digit 6
digit 8
digit 10
digit 12
digit 14
1
18.4.9 IMEISV
The IMEISV is coded as a sequence of BCD digits, compressed two into each octet. The IMEISV consists of 16 digits
(see 3GPP TS 23.003 [5]).
3GPP
Release 11
48
octet 1
octet 2
octet 3
octet 4
octet 5
octet 6
octet 7
octet 8
octet 9
octet 10
4
IEI
length indicator
digit 2
digit 4
digit 6
digit 8
digit 10
digit 12
digit 14
digit 16
digit 1
digit 3
digit 5
digit 7
digit 9
digit 11
digit 13
digit 15
18.4.10 IMSI
The IMSI is coded as a sequence of BCD digits, compressed two into each octet. This is a variable length element, and
includes a length indicator. The IMSI is defined in 3GPP TS 23.003 [5]. It shall not exceed 15 digits (see 3GPP TS
23.003 [5]).
8
Octet 1
Octet 2
Octet 3
Octet 4
Octet 4+x
IMSI digit 1
IMSI digit 3
IMSI digit i+1
4
IEI
Length indicator
* parity
0
0
IMSI digit 2
IMSI digit i
8
Octet 1
Octet 2
Octet 3
4
3
2
IEI
Length indicator
IMSI detach from GPRS service type value
3GPP
Release 11
49
Table 18.4.11/3GPP TS 29.018: IMSI detach from GPRS service type IE value part
IMSI detach from GPRS service type value (octet 3)
Bits
87654321
0 0 0 0 0 0 0 0 Interpreted as reserved in this version of the protocol
0 0 0 0 0 0 0 1 Network initiated IMSI detach from GPRS service
0 0 0 0 0 0 1 0 MS initiated IMSI detach from GPRS service
0 0 0 0 0 0 1 1 GPRS services not allowed
00000100
to
Interpreted as reserved in this version of the protocol
11111111
8
Octet 1
Octet 2
Octet 3
4
3
2
IEI
Length indicator
IMSI detach from non-GPRS service type value
8
Octet 1
Octet 2
Octet 3
4
3
IEI
Length indicator
Information requested value
3GPP
Release 11
50
NOTE:
The behaviour of the receiver in the case of a Not supported value is described in clause 14.3, Procedures
in the SGSN.
Octet 1
Octet 2
Octet 3
Octer 7
4
3
2
1
IEI
Length Indicator
The rest of the information element is coded as the value part of the
location area identifier IE defined in 3GPP TS 48.018 [15] (not
including 3GPP TS 48.018 IEI and 3GPP TS 48.018 length
indicator).
Octet 1
Octet 2
Octet 3
Octet 4
4
3
2
1
IEI
Length indicator
The rest of the IE is coded as the value part of the
AgeOfLocationInformation as specified in 3GPP TS 29.002 [17].
3GPP
Release 11
51
18.4.16 MM information
The MM information IE is a TLV IE that encapsulates the user information that the SGSN forwards to the MS.
Octet 1
Octet 2
Octet 3
Octet n
4
3
2
1
IEI
Length Indicator
User information: This field is composed of one or more of the
information elements of the MM information message as defined in
3GPP TS 24.008 [11], excluding the Protocol discriminator, Skip
indicator and Message type. This field includes the IEI and length
indicatior of the other information elements.
The International Mobile Equipment Identity together with the Software Version number (IMEISV).
Octet 1
Octet 2
Octet 3
Octet n
4
3
2
1
IEI
Length Indicator
The rest of the information element is coded as the value part of the
mobile identity IE defined in 3GPP TS 24.008 [11] (not including
3GPP TS 24.008 IEI and 3GPP TS 24.008 length indicator).
Octet 1
Octet 2
Octet 3
4
3
2
1
IEI
Length indicator
The rest of the information element is coded as the value part of the
mobile station classmark 1 IE defined in 3GPP TS 24.008 [11] (not
including 3GPP TS 24.008 IEI)
3GPP
Release 11
52
Octet 1
Octet 2
Octet 3
4
3
IEI
Length indicator
Mobile station state value
18.4.20 PTMSI
The PTMSI consists of 4 octets. It can be coded using a full hexadecimal representation (see 3GPP TS 23.003 [5]).
8
octet 1
octet 2
octet 3
octet 4
octet 5
octet 6
4
IEI
length indicator
PTMSI octet 1
PTMSI octet 2
PTMSI octet 3
PTMSI octet 4
3GPP
Release 11
53
Octet 1
Octet 2
Octet 3
4
3
2
1
IEI
Length Indicator
The rest of the information element is coded as the value part of the
reject cause IE defined in 3GPP TS 24.008 [11], not including
3GPP TS 24.008 IEI.
Octet 1
Octet 2
Octet 3
to
Octet 9
4
3
2
1
IEI
Length indicator
The rest of the information element is coded as the the value part of
the SAI IE defined in 3GPP TS 25.413 [22] (not including
3GPP TS 25.413 IEI and 3GPP TS 25.413 length indicator).
Octet 1
Octet 2
Octet 3
Octet 4
Octet n
0
digit 2
digit i+1
4
IEI
Length indicator
1
0
digit 1
digit i
18.4.23 TMSI
The TMSI consists of 4 octets. It can be coded using a full hexadecimal representation (see 3GPP TS 23.003 [5]).
8
octet 1
octet 2
octet 3
octet 4
octet 5
octet 6
4
IEI
length indicator
TMSI octet 1
TMSI octet 2
TMSI octet 3
TMSI octet 4
3GPP
Release 11
54
Octet 1
Octet 2
Octet 3
4
IEI
Length indicator
Spare
TMSI
flag
8
Octet 1
Octet 2
Octet 3
Octet 4
to
Octet n
Spare
4
IEI
Length indicator
TOM Protocol Discriminator
Tunnel Priority
Tunnel payload
TOM Protocol Discriminator: Identifies the protocol using tunnelling of non-GSM signalling. For coding, see
3GPP TS 44.064 [12].
E:
Cipher Request. When set to 1 indicates that the SGSN received the payload in
ciphered form, when set to 0 indicates that the SGSN did not receive the payload in
ciphered form.
Tunnel Priority:
Indicates the priority of the Tunnel Payload. For coding, see Table 20.1: Association
between Tunnel Priority and LLC SAPs.
3GPP
Release 11
55
0
digit 2
digit i+1
4
IEI
Length indicator
1
0
3
0
digit 1
digit i
IEI
Length indicator
PLMN-Id
Coded as octets 2 to 4 of the Location Area Identification IE,
defined in 3GPP TS 24.008 [11] (not including 3GPP TS 24.008 IEI
and LAC).
Octet 6
Octet 7
Octet 1
Octet 2
Octet 3
Octet 4
4
3
2
1
IEI
Length Indicator
The rest of the information element is coded as the value part of the
Network resource identifier container IE defined in 3GPP TS
24.008.
3GPP
Release 11
56
4
3
2
1
IEI
Length indicator
Coded as octets 2 to 4 of the Location Area Identification IE,
defined in 3GPP TS 24.008 [11] (not including 3GPP TS 24.008 IEI
and LAC).
Octet 1
Octet 2
Octet 3
Octet 5
19
19.1 Timers
This clause lists the management timers specified for the operation of the BSSAP+ protocol. All the implementation
shall support the range of values specified below. The specific value of the timers shall be under the control of the
operator.
Table 19.1/3GPP TS 29.018: Management Timers
Timer
name
T5
T6-1
T6-2
T7
T8
T9
T10
T11
T12-1
T12-2
T14
NOTE:
Default
Timer
value
range
2 s to 20 s
Granularity
100 ms
Notes
Guards the Paging
procedure at the VLR.
3GPP
Release 11
57
20
Retry value
2
2
2
2
2
2
Notes
Recommended value
Recommended value
Recommended value
Recommended value
Recommended value
Recommended value
This procedure is used to tunnel non-GSM signalling messages between an MS and a non-GSM MSC/VLR.
3GPP
Release 11
58
Upon receipt of a BSSAP+-DOWNLINK-TUNNEL-REQUEST message from a non-GSM MSC/VLR, the SGSN shall
construct a TOM Protocol Envelope by mapping the Tunnel Payload field to the Message Capsule portion of the TOM
Protocol Envelope. The TOM Protocol Header shall be constructed based on the Protocol Discriminator in the
BSSAP+-DOWNLINK-TUNNEL-REQUEST message. The SGSN shall then send the TOM Protocol Envelope to the
MS on a specific LLC SAP. That LLC SAP shall be determined by the Tunnel Priority field in the BSSAP+DOWNLINK-TUNNEL-REQUEST message. LLC ciphering shall be enabled or disabled based upon the value of the
E field in this message. If the SGSN is unable to send the TOM Protocol Envelope to the indicated MS for any reason,
including the inability to accommodate the ciphering request as indicated in the BSSAP+-DOWNLINK-TUNNELREQUEST message, then it shall send a BSSAP+-MOBILE-STATUS message to the non-GSM MSC/VLR with an
appropriate Gs Cause code.
The association between the LLC SAPs and the Tunnel Priority shall be as in the following table, where 00 is top-most
priority and 11 is lowest priority.
Table 20.1: Association between Tunnel Priority and LLC SAPs
Tunnel Priority
00
01
10
11
LLC SAP
TOM2
Not defined
TOM8
Not defined
3GPP
Release 11
59
Annex A (informative):
Change history
3GPP
Release 11
TSG CN#
60
Spec
Version
CR
New
Version
Subject
Apr 1999
CN#03
CN#4
CN#5
001
001
3.0.0
3.1.0
3.2.0
CN#5
29.018
3.1.0
002
3.2.0
CN#5
29.018
3.1.0
003
3.2.0
CN#5
29.018
3.1.0
005
3.2.0
CN#5
29.018
3.1.0
006
3.2.0
CN#5
29.018
3.1.0
004
3.2.0
CN#7
29.018
3.2.0
003r2 3.3.0
CN#7
29.018
3.2.0
007r3 3.3.0
CN#7
29.018
3.2.0
009
3.3.0
CN#9
29.018
29.018
3.3.0
3.4.0
010
3.4.0
3.4.1
CN#10
29.018
3.4.1
011
3.5.0
CN#11
29.018
3.5.0
012r1 3.6.0
CN#11
29.018
3.6.0
4.0.0
CN#13
29.018
4.0.0
014
4.1.0
CN#13
29.018
4.0.0
016
4.1.0
CN#13
29.018
4.0.0
018
4.1.0
CN#14
29.018
4.1.0
020
4.2.0
CN#14
29.018
4.1.0
023
4.2.0
CN#14
29.018
4.2.0
024r1 5.0.0
CN#14
29.018
4.2.0
025r1 5.0.0
Comment/TSG doc#/Date
Transferred to 3GPP CN1
Approved at CN#03
Approved CN#4
CR 001 were not
implemented correctly in v
3.1.0,
CR 002 were not
implemented correctly in v
3.1.0,
CR 003 were not
implemented correctly in v
3.1.0,
Approved in CN#5 as
CR001r1, NP-99268
Approved in CN#5 as
CR002, NP-99268
NP-000091
NP-000101
NP-000091
3GPP
Release 11
TSG CN#
61
Spec
Version
CR
New
Subject
Version
5.1.0
Addition of Mobile Station States for
UMTS
CN#15
29.018
5.0.0
028
CN#16
29.018
5.1.0
031
5.2.0
CN#18
29.018
5.2.0
032
5.3.0
CN#20
29.018
5.3.0
033
5.4.0
CN#21
29.018
5.4.0
038
5.5.0
CN#21
29.018
5.4.0
039
5.5.0
CN#24
29.018
5.5.0
041r2 6.0.0
CN#25
29.018
6.0.0
042r2 6.1.0
CN#27
29.018
6.1.0
043r2 6.2.0
CP-29
29.018
6.2.0
044r3 7.0.0
CP-30
29.018
7.0.0
046r3 7.1.0
CP-31
29.018
7.1.0
048
7.2.0
CP-34
29.018
7.2.0
050
7.3.0
CP-41
CP-41
29.018
29.018
7.3.0
7.3.0
CP-42
29.018
8.0.0
052
CP-43
29.018
8.1.0
0053r2 8.2.0
CP-46
29.018
8.2.0
0055r1 9.0.0
CP-46
29.018
8.2.0
0056r1 9.0.0
CP-49
29.018
9.0.0
0058r2 10.0.0
CP-49
29.018
9.0.0
0060r1 10.0.0
CP-49
29.018
9.0.0
0061r2 10.0.0
CP-49
29.018
9.0.0
0065
CP-49
29.018
9.0.0
0063r6 10.0.0
CP-50
29.018
10.0.0
0059r2 10.1.0
8.0.0
8.0.0
8.1.0
10.0.0
Comment/TSG doc#/Date
Cat A, WI=GSM/UMTS
interworking,
NP-020037/ N1-020201
03-2002
Various clean-up of wrong
Cat A, WI=TEI4,
references, as eg 24.008 instead of NP-020224/ N1-020855
44.018
06-2002
Clarification of the coding of the
Cat F, WI=IUFLEX,
Global CN-Id
NP-020571/ N1-021978
12-2002
Addition of IMEISV to BSSAP+Cat F, WI= LATE_UE,
LOCATION-UPDATE-REQUEST
NP-030283/ N1-030709
message
06-2003
Aligning IMEI in 29.018 with 23.003 Cat A, WI= TEI
NP-030405 / N1-031041
09-2003
Aligning IMEI in 29.018 with 23.003 Cat F, WI= LATE_UE
NP-030417 / N1-031120
09-2003
Addition of IMEISV to Update
Cat B, WI= TEI6, NP-040203
Location Procedure for ADD function / N1-040920
06-2004
Transfer of selected core network
Cat B, WI= NTShar, NPoperator identity across Gs interface 040375/N1-041615
09-2004
Management Based Activation
NP-050084/N1-050396, WI=
Impacts
OEM-Trace, Cat B
03-2005
SGSN Gs behaviour in VLR reset
CP-050366/C1-051202,
situations
WI=TEI7, Cat F
09-2005
Introduction of load re-distribution on CP-050557, WI=IUFLEX,
the Gs interface
Cat A, 12-2005
Paging during PS domain specific
CP-060114, WI=ACBOP,
access control
Cat A, 03-2006
Correction of paging during PS
CP-0602121, WI=ACBOP,
Domain Specific Access Control
Cat A, 11-2006
(DSAC)
Upgrade to Rel-8
09-2008
Correction of IE references in
CP-080536, WI=TEI8, Cat F,
BSSAP+ messages for IMSI
09-2008
DETACH and GPRS DETACH
Interactions between Gs and SGs
CP-080867, WI=SAESCSFB, Cat B, 12-2008
Clarifications of CSFB paging
CP-080159, WI=TEI8, Cat F,
procedure in SGSN
03-2009
Paging signalling optimization after
CP-090922, WI=TEI9, Cat B,
SGSN failure
12-2009
Paging clarifications
CP-090922, WI=TEI9, Cat F,
12-2009
SGSN State Diagram Correction
CP-100518, WI=TEI10, CAT
F, 09-2010
Length of erroneous message
CP-100518, WI=TEI10, CAT
F, 09-2010
Data Restoration and Gs Association CP-100518, WI=TEI10, CAT
Recovery
F, 09-2010
Behavior of the recipient upon receipt CP-100518, WI=TEI10, CAT
of an erroneous BSSAP+-MobileF, 09-2010
Status message
Add Timezone IE in Location Update CP-100575, WI=TEI10, CAT
Request
F, 09-2010
SGSN Failure Handling
CP-100763, WI=TEI10, CAT
F, 12-2010
3GPP
Release 11
TSG CN#
62
Spec
Version
CR
CP-50
29.018
10.0.0
New
Subject
Version
0064r2 10.1.0
VLR Failure Handling
CP-50
29.018
10.0.0
0066r3 10.1.0
CP-50
29.018
10.0.0
0069r1 10.1.0
CP-50
29.018
10.0.0
0070r3 10.1.0
CP-50
29.018
10.0.0
0071
CP-51
29.018
10.1.0
0073r1 10.2.0
CP-51
29.018
10.1.0
0074r2 10.2.0
CP-51
29.018
10.1.0
0075
10.2.0
CP-51
29.018
10.1.0
0076
10.2.0
CP-51
29.018
10.1.0
0077
10.2.0
CP-52
29.018
10.2.0
0079r1 10.3.0
CP-52
29.018
10.2.0
0081r1 10.3.0
CP-52
29.018
10.2.0
0084
CP-53
29.018
10.3.0
0080r3 10.4.0
CP-53
29.018
10.3.0
0086r1 10.4.0
CP-53
29.018
10.4.0
0082r3 11.0.0
CP-53
29.018
10.4.0
0088
CP-54
29.018
11.0.0
0092r4 11.1.0
CP-55
29.018
11.1.0
0094r1 11.2.0
CP-56
29.018
11.2.0
0100r1 11.3.0
CP-56
29.018
11.2.0
0101r3 11.3.0
CP-56
29.018
11.2.0
0105r3 11.3.0
CP-57
29.018
11.3.0
0107r2 11.4.0
CP-57
29.018
11.3.0
0112r1 11.4.0
CP-57
29.018
11.3.0
0095r7 11.4.0
CP-58
29.018
11.4.0
0113r3 11.5.0
CP-59
29.018
11.5.0
0115
CP-59
29.018
11.5.0
0116r1 11.6.0
CP-62
29.018
11.6.0
0130r3 11.7.0
10.1.0
10.3.0
11.0.0
11.6.0
Comment/TSG doc#/Date
CP-100763, WI=TEI10, CAT
F, 12-2010
CP-100763, WI=TEI10, CAT
F, 12-2010
CP-100763, WI=SAESCSFB, CAT A, 12-2010
CP-100763, WI=TEI10, CAT
F, 12-2010
CP-100763, WI=TEI10, CAT
F, 12-2010
CP-110197, WI=TEI10, CAT
F, 03-2011
CP-110197, WI=TEI10, CAT
F, 03-2011
CP-110197, WI=TEI10, CAT
F, 03-2011
CP-110197, WI=TEI10, CAT
F, 03-2011
CP-110197, WI=TEI10, CAT
F, 03-2011
CP-110464, WI=TEI10, CAT
F, 06-2011
CP-110464, WI=TEI10, CAT
F, 06-2011
3GPP