Bsc Sgsn Interface Specification Bss Gprs Protocol

Nokia Networks
GSM/EDGE BSS, Rel. GSM 16,

Operating Documentation,
Issue 02
BSC-SGSN Interface
Specification BSS GPRS
Protocol (BSSGP)
DN9983079
Issue 11-2
Approval Date 2014-04-15

BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein.
This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not
be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks
(“Agreement”) under which this document is distributed. No part of this document may be used, copied,
reproduced, modified or transmitted in any form or means without the prior written permission of Nokia
Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that
Agreement has expired or has been terminated, You may not use this document in any manner and You
are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of
the process of continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right
to change any such information and statements without notice. Nokia Solutions and Networks has made all
reasonable efforts to ensure that the content of this document is adequate and free of material errors and
omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,
Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction
of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product
will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE
LIABLE 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, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and
Networks.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners, and they are mentioned for identification purposes only.
Copyright © 2015 Nokia Solutions and Networks. All rights reserved.
f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its
products and services. We would like to encourage you as our customers and users to join us in working
towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations
for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia Solutions and Networks for any additional information.
2 DN9983079 Issue: 11-2
Table of Contents
This document has 102 pages

Summary of changes..................................................................... 9

1 BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
description....................................................................................12
1.1 Position of BSSGP within the protocol stack on the Gb interface....
12
1.2 Primitive parameters.................................................................... 13
1.2.1 BSSGP Virtual Connection Identifier (BVCI)................................ 13
1.2.2 Link Selector Parameter (LSP).................................................... 14
1.2.3 Network Service Entity Identifier (NSEI)...................................... 14
1.3 BSSGP procedures......................................................................14
1.3.1 Downlink Unitdata........................................................................ 15
1.3.2 Uplink Unitdata.............................................................................16
1.3.3 RA Capability............................................................................... 17
1.3.4 Paging.......................................................................................... 18
1.3.5 Radio Access Capability Update..................................................19
1.3.6 Radio Status.................................................................................20
1.3.7 Suspend....................................................................................... 20
1.3.8 Resume........................................................................................21
1.3.9 Flush-LL....................................................................................... 22
1.3.10 Flow Control................................................................................. 23
1.3.11 BVC Blocking and Unblocking..................................................... 24
1.3.12 BVC Reset................................................................................... 26
1.3.13 Trace............................................................................................ 27
1.3.14 Create BSS PFC.......................................................................... 28
1.3.15 Delete BSS PFC.......................................................................... 28
1.3.16 RIM procedures............................................................................29
1.3.16.1 RAN Information Request procedure........................................... 29
1.3.16.1 RAN Information Request / Single Report procedure.................. 29
1.3.16.1 RAN Information Request / Multiple Report procedure................30
1.3.16.1 RAN Information Request / Stop procedure.................................30
1.3.16.2 RAN Information Send procedure................................................ 31
1.3.16.3 RAN Information Application Error procedure..............................32
1.3.16.4 RAN Information Error procedure................................................ 33
1.3.16.5 Abnormal conditions.....................................................................33
1.4 General protocol error handling................................................... 35
1.5 BSSGP protocol data units (PDUs)..............................................35
1.5.1 DL-UNITDATA.............................................................................. 36
1.5.2 UL-UNITDATA.............................................................................. 37
1.5.3 RA-CAPABILITY...........................................................................38
1.5.4 PAGING-PS..................................................................................38
1.5.5 PAGING-CS................................................................................. 39
Issue: 11-2 DN9983079 3
1.5.6 RA-CAPABILITY-UPDATE........................................................... 39
1.5.7 RA-CAPABILITY-UPDATE-ACK...................................................40
1.5.8 RADIO-STATUS........................................................................... 40
1.5.9 SUSPEND.................................................................................... 41
1.5.10 SUSPEND-ACK........................................................................... 41
1.5.11 SUSPEND-NACK.........................................................................42
1.5.12 RESUME...................................................................................... 42
1.5.13 RESUME-ACK............................................................................. 42
1.5.14 RESUME-NACK...........................................................................43
1.5.15 FLUSH-LL.................................................................................... 43
1.5.16 FLUSH-LL-ACK............................................................................44
1.5.17 LLC-DISCARDED........................................................................ 44
1.5.18 FLOW-CONTROL-BVC................................................................45
1.5.19 FLOW-CONTROL-BVC-ACK....................................................... 45
1.5.20 FLOW-CONTROL-MS..................................................................46
1.5.21 FLOW-CONTROL-MS-ACK......................................................... 46
1.5.22 BVC-BLOCK................................................................................ 46
1.5.23 BVC-BLOCK-ACK........................................................................ 47
1.5.24 BVC-UNBLOCK........................................................................... 47
1.5.25 BVC-UNBLOCK-ACK...................................................................47
1.5.26 BVC-RESET.................................................................................48
1.5.27 BVC-RESET-ACK........................................................................ 48
1.5.28 STATUS........................................................................................49
1.5.29 SGSN-INVOKE-TRACE............................................................... 50
1.5.30 DOWNLOAD-BSS-PFC............................................................... 50
1.5.31 CREATE-BSS-PFC...................................................................... 51
1.5.32 CREATE-BSS-PCF-ACK..............................................................51
1.5.33 CREATE-BSS-PFC-NACK........................................................... 52
1.5.34 DELETE-BSS-PFC...................................................................... 52
1.5.35 DELETE-BSS-PFC-ACK.............................................................. 53
1.5.36 RAN-INFORMATION-REQUEST................................................. 53
1.5.37 RAN-INFORMATION....................................................................54
1.5.38 RAN-INFORMATION-ACK........................................................... 54
1.5.39 RAN-INFORMATION-ERROR..................................................... 55
1.5.40 RAN-INFORMATION-APPLICATION-ERROR.............................55
1.6 BSSGP information elements (IEs)..............................................55
1.6.1 IEI codings................................................................................... 56
1.6.2 Alignment Octets..........................................................................61
1.6.3 Bmax Default MS......................................................................... 61
1.6.4 BSS Area Indication..................................................................... 62
1.6.5 Bucket Leak Rate.........................................................................62
1.6.6 BVC Bucket Size..........................................................................63
1.6.7 BVCI............................................................................................. 63
1.6.8 BVC Measurement.......................................................................63
1.6.9 Cause...........................................................................................64
1.6.10 Cell Identifier................................................................................ 67
4 DN9983079 Issue: 11-2
1.6.11 Channel Needed.......................................................................... 67
1.6.12 DRX Parameters.......................................................................... 67
1.6.13 eMLPP Priority............................................................................. 68
1.6.14 Flush Action................................................................................. 68
1.6.15 IMSI.............................................................................................. 69
1.6.16 LLC PDU...................................................................................... 69
1.6.17 LLC Frames Discarded................................................................ 69
1.6.18 Location Area............................................................................... 70
1.6.19 Mobile Id.......................................................................................70
1.6.20 MS Bucket Size............................................................................70
1.6.21 MS Radio Access Capability........................................................ 71
1.6.22 OMC Id......................................................................................... 71
1.6.23 PDU In Error.................................................................................71
1.6.24 PDU Lifetime................................................................................ 71
1.6.25 PDU Type.....................................................................................72
1.6.26 Priority.......................................................................................... 74
1.6.27 QoS Profile...................................................................................74
1.6.28 Radio Cause................................................................................ 75
1.6.29 RA-Cap-UPD-Cause.................................................................... 76
1.6.30 Routing Area................................................................................ 77
1.6.31 R_default_MS.............................................................................. 77
1.6.32 Suspend Reference Number........................................................77
1.6.33 Tag............................................................................................... 78
1.6.34 Temporary Logical Link Identity (TLLI)......................................... 78
1.6.35 TMSI.............................................................................................78
1.6.36 Trace Reference...........................................................................79
1.6.37 Trace Type................................................................................... 79
1.6.38 Transaction Id...............................................................................80
1.6.39 Trigger Id...................................................................................... 80
1.6.40 Number Of Octets Affected.......................................................... 80
1.6.41 LSA Identifier List......................................................................... 80
1.6.42 LSA Information........................................................................... 80
1.6.43 Packet Flow Identifier (PFI)..........................................................81
1.6.44 Aggregate BSS QoS Profile......................................................... 81
1.6.45 Feature Bitmap.............................................................................81
1.6.46 Bucket Full Ratio.......................................................................... 83
1.6.47 Service UTRAN CCO................................................................... 83
1.6.48 NSEI............................................................................................. 84
1.6.49 RIM Application Identity............................................................... 84
1.6.50 RIM Sequence Number................................................................85
1.6.51 RAN-INFORMATION-REQUEST Application Container..............85
1.6.52 RAN-INFORMATION Application Container................................ 86
1.6.53 RIM PDU Indicators..................................................................... 87
1.6.54 Global CN-Id................................................................................ 89
1.6.55 RIM Routing Information.............................................................. 89
1.6.56 RIM Protocol Version Number......................................................90
Issue: 11-2 DN9983079 5
1.6.57 Application Error Container.......................................................... 91
1.6.58 RAN-INFORMATION-REQUEST RIM container .........................92
1.6.59 RAN-INFORMATION RIM container............................................ 93
1.6.60 RAN-INFORMATION-APPLICATION-ERROR RIM Container.... 94
1.6.61 RAN-INFORMATION-ACK-RIM container................................... 95
1.6.62 RAN-INFORMATION-ERROR RIM Container............................. 96
1.6.63 Extended Feature Bitmap............................................................ 97
1.6.64 Flow Control Granularity.............................................................. 98
1.6.65 SON Transfer Application Identity................................................ 98
1.6.66 Subscriber Profile ID for RAT/Frequency priority......................... 98
1.6.67 Redirect Attempt Flag.................................................................. 98
1.6.68 Redirection Indication...................................................................98
1.6.69 Redirection Completed.................................................................99
1.6.70 Unconfirmed send state variable................................................100
1.6.71 Service Class Indicator.............................................................. 100
1.7 List of system variables..............................................................101
6 DN9983079 Issue: 11-2
List of Figures
Figure 1 The protocol stack on the Gb interface...............................................12
Figure 2 DL Unitdata.........................................................................................15
Figure 3 UL Unitdata.........................................................................................16
Figure 4 RA Capability......................................................................................17
Figure 5 Paging................................................................................................ 18
Figure 6 Radio Access Capability Update........................................................ 19
Figure 7 Radio Status....................................................................................... 20
Figure 8 Suspend............................................................................................. 20
Figure 9 Flush LL..............................................................................................22
Figure 10 BVC Flow Control............................................................................... 23
Figure 11 BVC Blocking and Unblocking............................................................24
Figure 12 BVC Reset..........................................................................................26
Figure 13 RAN Information Request/Single report Procedure............................29
Figure 14 RAN Information Request/Multiple Report Procedure........................30
Figure 15 RAN Information Request/Stop Procedure.........................................30
Figure 16 Acknowledged RAN Information Send procedure.............................. 31
Figure 17 RAN Information Application Error procedure.................................... 32
Figure 18 RAN Information Error procedure.......................................................33
Issue: 11-2 DN9983079 7
List of Tables
Table 1 BSSGP PDU, BVCI, and functional entity mapping........................... 13
Table 2 BSSGP timers.................................................................................. 101
Table 3 BSSGP parameters.......................................................................... 101
8 DN9983079 Issue: 11-2

BSC-SGSN Interface Specification BSS GPRS Protocol Summary of changes
(BSSGP)
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes between issues 11-2 (2014/04/15, RG30 EP1(BSS)) and 11-1 (2013/08/06,
RG30 EP1(BSS))
Flush-LL (1.3.9)
• Chapter has been updated.
Changes between issues 11-1 (2013/08/06, RG30 EP1(BSS)) and 11-0 (2012/06/21,
RG30(BSS))
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description (1)
• Support for the Multi Operator Core Network (MOCN) Rel-10 has been added.
Downlink Unitdata (1.3.1)
Uplink Unitdata (1.3.2)
BVC Reset (1.3.12)
• Support of the Extended Feature Bitmap was added.
DL-UNITDATA (1.5.1)
• New information elements were added.
UL-UNITDATA (1.5.2)
BVC-RESET (1.5.26)
• The Extended Feature Bitmap is now in use.
BVC-RESET-ACK (1.5.27)
• The Extended Feature Bitmap is now in use.
CREATE-BSS-PFC (1.5.31)
CREATE-BSS-PCF-ACK (1.5.32)
IEI codings (1.6.1)
• New IEI codings were added.
PDU Type (1.6.25)
Issue: 11-2 DN9983079 9

Summary of changes BSC-SGSN Interface Specification BSS GPRS Protocol
(BSSGP)
• PDU type coding list was updated.
Priority (1.6.26)
• Information about priority IEI was added.
Redirect Attempt Flag (1.6.67)
• New chapter added.
Redirection Indication (1.6.68)
Redirection Completed (1.6.69)
Unconfirmed send state variable (1.6.70)
Changes between issues 11-0 (2012/06/01, RG30(BSS)) and 10-1 (2011/09/29,
RG20(BSS))
Create BSS PFC (1.3.15)
• Support for the Packet Flow Context Procedures has been added.
Delete BSS PFC (1.3.16)
DOWNLOAD-BSS-PFC (1.5.35)
CREATE-BSS-PFC (1.5.36)
CREATE-BSS-PCF-ACK (1.5.37)
CREATE-BSS-PFC-NACK (1.5.38)
DELETE-BSS-PFC (1.5.39)
DELETE-BSS-PFC-ACK (1.5.40)
Aggregate BSS QoS Profile (1.6.43)
• Added information on Aggregate BSS QoS Profile.
List of system variables (1.7)
10 DN9983079 Issue: 11-2

BSC-SGSN Interface Specification BSS GPRS Protocol Summary of changes
(BSSGP)
• Added information on T6 timer and BSSGP parameter DOWNLOADBSS-
PFCRETRIES to the tables BSSGP timers and BSSGP parameters respectively.
Issue: 11-2 DN9983079 11

BSC-SGSN Interface Specification BSS GPRS Protocol BSC-SGSN Interface Specification BSS GPRS Protocol
(BSSGP) description (BSSGP)
1 BSC-SGSN Interface Specification BSS GPRS

Protocol (BSSGP) description
This interface description deals with 3GPP TS 48.018, General Packet Radio Service
(GPRS); Base Station System (BSS) – Serving GPRS Support Node (SGSN); BSS
GPRS Protocol (BSSGP), version 9.3.0, Rel-9. This document describes the BSS GPRS
Protocol (BSSGP) implementation for controlling of GSM packet data services in the
BSC SW release S16. It defines what is supported in the BSC-SGSN interface from the
BSC point of view.
As a general rule, the 3GPP Standard is implemented. Generally all primitives and
parameters received without a protocol error have to be processed as defined in 3GPP
TS 48.018, version 9.3.0, Rel-9. However, as MOCN has been standardised in Rel-10,
MOCN is used as defined in 3GPP TS 48.018, version 10.6.0, Rel-10. Any exceptions to
these general rules are mentioned in this description.
Explanations of the remarks in this interface document:
not supported Functionality is not implemented
not used Primitive or parameter is not implemented
compliant, supported or no remark Functionality is implemented as defined in the
Recommendation
This description is general and used for all customers.
1.1 Position of BSSGP within the protocol stack on the

Gb interface
Gb interface has a protocol stack consisting of three layers: physical layer, network
service (NS) layer and BSSGP. The network service layer is further divided into a
subnetwork service and a network service control. The subnetwork service uses either
frame relay (FR) or User Datagram Protocol over Internet Protocol (UDP/IP).
Figure 1 The protocol stack on the Gb interface
LLC
RELAY
BSSGP
RLC BSSGP
MAC NS NS
L1 L1
Gb
BSC SGSN
Network service control is responsible for virtual circuit management and GPRS-specific
addressing, which maps cells to virtual connections.
12 DN9983079 Issue: 11-2

(BSSGP) (BSSGP) description
The BSSGP is a layer 3 protocol for delivering data packets and associated control
information. The BSSGP also includes procedures, for example, for downlink flow
control, paging, and virtual circuit management.
1.2 Primitive parameters

1.2.1 BSSGP Virtual Connection Identifier (BVCI)
BSSGP virtual connections (BVC) are communication paths between peer BSSGPs.
Each BVC is identified by a BVCI which has end-to-end significance on the Gb interface.
Each BVC is unique between two peer network service entities.
Within the BSS, a cell is identified uniquely by the BVCI.
The BVCI value 0000 hex is used for signalling and the value 0001 hex is reserved for a
point-to-multipoint (PTM) connection. All other values are used for cell identifiers. The
PTM BVCI is not supported by the BSC.
Table 1 BSSGP PDU, BVCI, and functional entity mapping
BSSGP PDUs Mapping of BVCI to a functional entity
DL-UNITDATA PTP
UL-UNITDATA PTP
RA-CAPABILITY PTP
PAGING-PS PTP or SIGNALLING (NOTE 1)
PAGING-CS PTP or SIGNALLING (NOTE 2)
RA-CAPABILITY-UPDATE / RA-CAPABILITY- PTP
UPDATE-ACK
RADIO-STATUS PTP
SUSPEND / SUSPEND-ACK / SUSPEND-NACK SIGNALLING
RESUME / RESUME-ACK / RESUME-NACK SIGNALLING
FLUSH-LL / FLUSH-LL-ACK SIGNALLING
LLC-DISCARDED SIGNALLING
FLOW-CONTROL-BVC / FLOW-CONTROL-BVC- PTP
ACK
FLOW-CONTROL-MS / FLOW-CONTROL-MS- PTP
ACK
STATUS PTP or SIGNALLING (NOTE 3)
BVC-BLOCK / BVC-BLOCK-ACK SIGNALLING
BVC-UNBLOCK / BVC-UNBLOCK-ACK SIGNALLING
BVC-RESET / BVC-RESET-ACK SIGNALLING
SGSN-INVOKE-TRACE SIGNALLING
DOWNLOAD-BSS-PFC PTP
CREATE-BSS-PFC / CREATE-BSS-PFC-ACK / PTP
CREATE-BSS-PFC-NACK
Issue: 11-2 DN9983079 13

Table 1 BSSGP PDU, BVCI, and functional entity mapping (Cont.)
BSSGP PDUs Mapping of BVCI to a functional entity
DELETE-BSS-PFC / DELETE-BSS-PFC-ACK PTP
RAN-INFORMATION-REQUEST / RAN- SIGNALLING
INFORMATION / RAN-INFORMATION-ACK / RAN-
INFORMATION-ERROR / RAN-INFORMATION-
APPLICATION-ERROR
g Note: Note 1: SGSN may initiate paging of a mobile station (MS) in READY mobility
management state at an indication of a lower layer failure. In this case the BVCI = PTP
may be used.
g Note: Note 2: If the SGSN initiates circuit-switched paging of an MS in READY mobility
management state, the BVCI is PTP. If the MS is in STANDBY state, the BVCI is
SIGNALLING.
g Note: Note 3: The setting of the BVCI depends on the context within which the
STATUS protocol data unit (PDU) was generated.
1.2.2 Link Selector Parameter (LSP)

All BSSGP UNITDATA PDUs related to an MS are passed to the NS with the same LSP.
This preserves the order of BSSGP UNITDATA PDUs, since the LSP is always mapped
to a certain network service virtual connection (NS-VC). The LSP has only local
significance at each end of the Gb interface.
Because of the load sharing function at the NS level, the SGSN is expected to receive
BSSGP PDUs on any unblocked NS-VC within the NSE.
1.2.3 Network Service Entity Identifier (NSEI)

The NSE identifies a group of NS-VCs in the BSC.
The BSC uses the NSEI to determine the NS-VCs which provide service to a BVC.
1.3 BSSGP procedures
14 DN9983079 Issue: 11-2

1.3.1 Downlink Unitdata

Figure 2 DL Unitdata
BSC SGSN
BSSGP BSSGP
DL-UNITDATA
When the SGSN initiates a downlink data packet transmission from an SGSN to an MS,
it sends a DL-UNITDATA PDU to the BSC. The PDU contains information elements to be
used by the BSC and a LLC-PDU. There is only one LLC-PDU per DL-UNITDATA PDU.
The LLC-PDU is always the last information element in the DL-UNITDATA PDU and it is
aligned on a 32 bit boundary for efficient processing.
The MS is identified with a TLLI. If a second TLLI exists in the message indicating that
the MS has recently changed its TLLI, this is considered as the old TLLI. The old TLLI is
used to locate the existing context of an MS. Subsequent uplink data transfers for this
MS reference the current TLLI instead of the old TLLI. If the SGSN has a valid IMSI for
the TLLI, the SGSN includes it in the PDU. Also if the SGSN has valid DRX parameters
for the TLLI, the SGSN includes them in the PDU. The SGSN can omit the DRX
Parameters during a DRX forbidden period to speed up the transmission of the LLC-PDU
on the radio interface.
The SGSN provides MS-specific information for the BSC within the DL¬UNITDATA
PDUs so that the RLC/MAC entity in the BSC can transmit LLC-PDUs to the MS in a
user-specific manner. This information includes the following:
• MS radio access capability (MS RAC) defines the radio capabilities of the ME. It is
provided if available in the SGSN.
• Packet flow identifier (PFI) identifies the packet flow context associated with the LLC-
PDU and it is included by the SGSN if the Packet Flow Context (PFC) is negotiated.
If the mobile station does not support the PFC or if the PFI is not known, the SGSN
uses the pre-defined PFI to indicate the QoS to be applied.
• Quality of Service (QoS) profile defines the peak bit rate, the type of the BSSGP
SDU (signalling or data), the type of the LLC frame, the precedence class, and the
transmission mode to be used when transmitting the LLC-PDU on the radio interface.
• PDU lifetime defines the remaining time period in which the PDU is considered valid
within the BSC. If the PDU is held for a period exceeding the PDU lifetime, the BSC
locally discards the PDU.
The type of the BSSGP SDU indicates whether the DL-UNITDATA PDU contains layer 3
signalling or data. These BSSGP SDU types are distinguished through the QoS profile.
The type of the LLC frame indicates whether the SDU contains a LLC ACK, a LLC SACK
command or response, or some other frame type. BSC does not use this information.
Precedence class is used for prioritization of downlink LLC-PDUs on the radio interface.
Issue: 11-2 DN9983079 15

Two transmission modes on the radio interface are possible: acknowledged (using
RLC/MAC ARQ functionality) and unacknowledged (using RLC/MAC unitdata
functionality) transmission modes.
If priority field is present, it is not used. It is ignored when the BSC receives it.
If LSA Information field is present, it is not used. It is ignored when the BSC receives it.
The BSC supports the Service UTRAN CCO (Cell Change Order) information element in
the PDU. It is relevant if the network initiated cell change order to the UTRAN procedure
is used.
When using an IP subnetwork, the resource distribution function at the SGSN may
transmit a BSSGP DL-UNITDATA PDU with an LLC-PDU length indicator set to 0. The
BSC uses this DL-UNITDATA to change the IP endpoint at the SGSN to which any future
UL-UNITDATA for the TLLI is sent. The TLLI is indicated in the DL-UNITDATA. The LLC-
PDU with a length indicator set to 0 is not sent on the radio interface.
If Subscriber Profile ID for RAT/Frequency priority Information field is present, it is not
used. It is ignored when the BSC receives it.
If the Core Network is configured to tag DL PDUs that belong to a certain signaling type
of application, like Tencent QQ, then SGSN may transmit a BSSGP DL-UNITDATA PDU
to PCU with a proprietary Service Class Indicator. If the Instant QoS Signaling feature is
enabled in BSC, then PCU takes into account the proprietary Service Class Indicator and
allocates only 1 TSL for a DL TBF if the DL LLC PDUs to be transferred are received
with this tag.
If MOCN is used the information elements Redirection Indication, Redirection
Completed, Initial LLC-PDU, and Unconfirmed send state variable may be included to
DL-UNITDATA message.
1.3.2 Uplink Unitdata

Figure 3 UL Unitdata
BSC SGSN
BSSGP BSSGP
UL-UNITDATA
When the BSC initiates an uplink data packet transmission from an MS to an SGSN, it
sends an UL-UNITDATA PDU to the SGSN. The PDU contains information elements
meaningful to higher-layer protocols in the SGSN and an LLC-PDU.
There is only one LLC-PDU per UL-UNITDATA PDU. The LLC-PDU is always the last
information element in the UL-UNITDATA PDU and is aligned on a 32 bit boundary for
efficient processing.
The MS is identified with the TLLI.
16 DN9983079 Issue: 11-2

The QoS profile indicates the QoS characteristics used in the LLC-PDU's transmission
from the MS across the radio interface.
The QoS profile defines the peak bit rate, the type of the BSSGP SDU (signalling or
data), the type of the LLC frame, the precedence class, and the transmission mode used
when transmitting the LLC-PDU on the radio interface.
The peak bit rate is always set to zero to indicate best effort.
The following transmission modes on the radio interface are possible:
• acknowledged transmission mode (using RLC/MAC ARQ functionality)
• unacknowledged transmission mode (using RLC/MAC unitdata functionality)
The type of the BSSGP SDU (layer 3 signalling or data), and the type of the LLC frame
(SACK, ACK, or not) are meaningless on the uplink and the SGSN ignores them.
Furthermore, the BSC includes the cell identifier of the cell on which the LLC-PDU was
received.
The LSA identifier list is not included.
If the Gb interface is supported using an IP subnetwork, the resource distribution function
in the BSC may transmit a BSSGP UL-UNITDATA PDU with the LLC-PDU length
indicator set to zero. The SGSN uses this UL-UNITDATA to change the IP endpoint in
the BSS to which any future for the TLLI (indicated in the UL-UNITDATA) is sent.
If MOCN is used the information elements Redirect Attempt Flag, IMSI and Unconfirmed
send state variable may be included to UL-UNITDATA message.
1.3.3 RA Capability
Figure 4 RA Capability
BSC SGSN
BSSGP BSSGP
RA-CAPABILITY
The SGSN stores the current radio access capability of an MS. It may be changed by
higher layer mobility management procedures. The current radio access capability of the
MS and the TLLI identifying the MS are conveyed to the BSC in an RA-CAPABILITY
PDU. The BSC replaces any radio access capability previously associated with the MS
with the new information.
Issue: 11-2 DN9983079 17

1.3.4 Paging
Figure 5 Paging
BSC SGSN
BSSGP BSSGP
PAGING-PS
or
PAGING-CS
When the SGSN initiates a paging procedure for the GPRS services, it sends one or
more PAGING PS PDUs to the BSC. When instructed by an MSC/VLR to initiate the
paging procedure for non-GPRS services, the SGSN sends one or more PAGING CS
PDUs to the BSC. These paging PDUs contain the information elements necessary for
the BSS to initiate paging for an MS within a group of cells. A paging PDU is used to
generate corresponding radio interface paging request message(s) to be transmitted at
the appropriate time.
The SGSN indicates the MS's IMSI and DRX parameters, which enable the BSC to
derive the paging population number (paging group). In PAGING-PS PDU there are
separate fields that can be used for QoS determination purposes.
The paging area indicates the cells within which the BSC pages the MS. The levels of
resolution within one BSS are:
• all cells within the BSS
• all cells in the BSS within one location area
• all cells in the BSS within one routing area
• one BVCI (one cell)
A routing area, a location area, or a BSS area is associated with one or more NSEIs. If
the cells, in which to page the MS, are served by several NSEIs, one paging PDU must
be sent to each of these NSEIs.
If the SGSN provides a P-TMSI in a PAGING-PS PDU, the BSC uses the P-TMSI to
address the MS. If the SGSN does not provide a P-TMSI in a PAGING-PS PDU, the
BSC uses the IMSI to address the MS.
If the SGSN provides a TLLI in a PAGING-CS PDU and the radio context identified by
the TLLI exists within the BSC, the paging request message is sent directly to the MS. If
the SGSN does not provide a TLLI in a PAGING-CS PDU or if no radio context identified
by the TLLI exists within the BSC, the BSC uses the TMSI if it is provided in the
PAGING-CS PDU. Otherwise the BSC uses the IMSI to address the MS.
The PAGING-CS PDU may also include the following optional parameters: Channel
Needed, eMLPP-Priority, and Global CN-Id. The BSC handles the Channel Needed and
eMLPP-Priority information transparently.
18 DN9983079 Issue: 11-2

1.3.5 Radio Access Capability Update

Figure 6 Radio Access Capability Update
BSC SGSN
BSSGP BSSGP
RA-CAPABILITY-UPDATE
RA-CAPABILITY-UPDATE-ACK
The BSC may request the MS's current radio access capability and/or it’s IMSI by
sending an RA-CAPABILITY-UPDATE PDU which includes the TLLI of the MS and a Tag
to the SGSN. When the BSC sends the RA¬CAPABILITY-UPDATE PDU, it starts the
timer T5.
The SGSN responds by sending an RA-CAPABILITY-UPDATE-ACK PDU which includes
the TLLI of the MS, the Tag received in the corresponding RA-CAPABILITY-UPDATE
PDU, and a RA-Cap-UPD-Cause field. If the IMSI of the MS is known, it is also included.
When the BSC receives the RA-CAPABILITY-UPDATE-ACK PDU, it stops the timer T5.
If the RA-Cap-UPD-Cause is set to OK, the MS Radio Access Capability field and the
IMSI are present. The received MS RAC, if valid, replaces any MS RACs previously
associated with the MS. If the RA-Cap-UPD-Cause is not set to OK, neither the MS
Radio Access Capability nor the IMSI are present in the RA-CAPABILITY-UPDATE-ACK
PDU.
Abnormal conditions
If the SGSN receives an RA-CAPABILITY-UPDATE PDU which includes an unknown
TLLI, it answers with an RA-CAPABILITY-UPDATE-ACK PDU which includes the RA-
Cap-UPD-Cause set to the value TLLI unknown.
If the SGSN receives an RA-CAPABILITY-UPDATE PDU which includes a known TLLI,
but there are no radio access parameters or IMSI known to the SGSN for the associated
MS, the SGSN replies to the request with an RA-CAPABILITY-UPDATE-ACK PDU in
which the RA-Cap-UPD-Cause is set to no RA capability or IMSI available.
If the BSC receives an RA-CAPABILITY-UPDATE-ACK PDU containing a Tag which is
different from the last Tag that the BSC transmitted, it ignores the reception of this PDU.
If the RA-CAPABILITY-UPDATE-ACK is not returned within T5 seconds with the same
Tag value as provided in the request, the RA-CAPABILITY-UPDATE procedure is
repeated a maximum of RA-CAPABILITY-UPDATE-RETRIES attempts. The BSC
changes the Tag value at each new retry. After the RA-CAPABILITY-UPDATE-RETRIES
unsuccessful attempts, the procedure is stopped.
Issue: 11-2 DN9983079 19

1.3.6 Radio Status

Figure 7 Radio Status
BSC SGSN
BSSGP BSSGP
RADIO-STATUS
The BSS and the MS radio interface communication is not successfully completed if the
MS goes out of coverage and is lost. In this condition the BSC sends a RADIO STATUS
PDU to the SGSN with the radio cause value radio contact lost with MS.
The RADIO STATUS PDU contains the TLLI of the MS and an indication of the exception
condition, that is, the radio cause value.
1.3.7 Suspend
Figure 8 Suspend
BSC SGSN
BSSGP BSSGP
SUSPEND
SUSPEND-ACK
or
SUSPEND-NACK
If the MS signals to the BSC that it wants its GPRS service to be suspended, the BSC
sends a SUSPEND PDU to the SGSN and starts the TgbSuspend timer. The SUSPEND
PDU contains the TLLI and the Routing Area of the MS.
The SGSN acknowledges the SUSPEND PDU with a SUSPEND-ACK PDU. The
SUSPEND-ACK PDU contains the TLLI and the Routing Area of the MS and the
Suspend Reference Number.
The SGSN typically stops the paging for a suspended mobile.
When the BSC receives the SUSPEND-ACK PDU, it stops the TgbSuspend timer.
Abnormal conditions
20 DN9983079 Issue: 11-2

If a SUSPEND-ACK PDU is not received for a SUSPEND PDU within TgbSuspend
seconds, the Suspend procedure is repeated a maximum of SuspendRetries times. After
SuspendRetries unsuccessful attempts the procedure is stopped.
If a SUSPEND-ACK PDU is received for an MS which is already suspended, the PDU is
ignored.
If a SUSPEND PDU refers to an MS which is unknown in the SGSN, a SUSPEND-NACK
PDU with the cause value Unknown MS is returned. The BSC stops the Suspend
procedure and the TgbSuspend timer.
1.3.8 Resume
When the reason for suspending the GPRS-attached MS disappears, that is, the MS
leaves the dedicated mode disconnecting itself from the MSC, the BSC either instructs
the MS to initiate the Routing Area Update procedure, or signals the SGSN to resume
the MS's GPRS service.
If the BSC internal suspend status indicates that the MS has suspended the GPRS
service and the BSC has successfully completed the Suspend procedure, the BSC
signals the SGSN to resume the MS's GPRS service.
In the Resume procedure, the BSC sends a RESUME PDU to the SGSN and starts the
TgbResume timer. The RESUME PDU includes:
• TLLI of the MS
• Routing Area of the MS
• Suspend Reference Number
The SGSN responds to the RESUME PDU with a RESUME-ACK PDU or with the
RESUME-NACK PDU.
When the BSC receives the RESUME-ACK PDU or the RESUME-NACK PDU from the
SGSN, it stops the TgbResume timer.
If the Resume procedure was started because a CS call was released, the BSC
indicates in the CHANNEL RELEASE message to the MS, whether the resumption of the
GPRS services was successfully acknowledged or not, that is, whether the SGSN sent a
RESUME-ACK PDU or the RESUME-NACK PDU to the BSC.
Abnormal conditions
If a RESUME-ACK PDU or RESUME-NACK PDU is not received for a RESUME PDU
within TgbResume seconds, the RESUME PDU procedure is repeated a maximum of
RESUME-RETRIES attempts. After RESUME-RETRIES unsuccessful attempts, the
procedure is stopped and the BSC acts as if the RESUME-NACK PDU had been
received.
If a RESUME-ACK PDU is received for an MS that is not suspended, the BSC ignores
the RESUME-ACK PDU.
Issue: 11-2 DN9983079 21

1.3.9 Flush-LL
Figure 9 Flush LL
BSC SGSN
BSSGP BSSGP
FLUSH-LL
FLUSH-LL-ACK
The SGSN sends a FLUSH-LL PDU to the BSC to ensure that the LLC-PDUs queued for
transmission at a cell for an MS are either deleted or transferred to a new cell. The
FLUSH-LL procedure is used, for example, when the MS has stopped sending data in a
given cell and has moved to another cell.
The MS's TLLI indicates which mobile's data is in question. The BVCI (old) indicates the
cell. If an optional new cell, BVCI (new), is not given, all buffered LLC-PDUs and all
contexts for the MS are deleted. If an optional new cell, BVCI (new), is given, all buffered
LLC-PDUs are transferred to the new cell, provided that both the old and the new BVCI
are served by the same NSE and belong to the same RA. If Packet Control Unit (PCU2)
Pooling is in use, then LLC-PDUs are transferred to the new cell, provided that both the
old and the new BVCI belong to the same RA and are served by the same PCU.
The BSC sends a FLUSH-LL-ACK acknowledgement back to the SGSN. The Flush
action parameter indicates whether LLC-PDUs were deleted or transferred to a new cell.
If the flush action indicates a transfer, the new BVCI is included.
The FLUSH-LL-ACK PDU also contains the Number of octets affected field that indicates
the number of deleted or transferred data octets.
Abnormal conditions
If the BSC receives a FLUSH-LL PDU for an unknown BVCI or a TLLI not associated
with the given cell, the primitive is discarded and no FLUSH-LL-ACK PDU is returned.
22 DN9983079 Issue: 11-2

1.3.10 Flow Control

Figure 10 BVC Flow Control
BSC SGSN
BSSGP BSSGP
FLOW-CONTROL-BVC
FLOW-CONTROL-BVC-ACK
The BSC uses flow control to adjust the flow of BSSGP UNITDATA PDUs to the BVC
buffer. By doing this, the BSC controls the amount of BSSGP UNITDATA PDUs in its
buffers to optimize the buffer consumption in the BSC and to use radio resources
efficiently.
The flow control mechanism is based on the following model:
• There is a downlink buffer for each cell in the BSC, as identified by a BVCI in the Gb
interface.
• The BSC controls the transfer of BSSGP UNITDATA PDUs for an MS from the
SGSN by BVC-specific and MS-specific flow control messages.
• Only downlink BSSGP UNITDATA PDU transfer to the BSC is managed via flow
control procedures. Uplink flow control is not performed.
• Flow control is not performed for BSSGP signalling.
The BSC sends a FLOW-CONTROL-BVC PDU for a BVC after every BVC-RESET to
start the downlink BSSGP data transfer. The TgbFlow timer is started.
The FLOW-CONTROL-BVC PDU that the BSC sends to the SGSN contains the
following information:
• BVC Bucket Size: data buffer size per cell for downlink LLC frames
• Bucket Leak Rate: throughput per cell for downlink LLC frames
• Bmax Default MS: data buffer size per MS for downlink LLC frames
• R_default_MS: throughput per MS for downlink LLC frames
• Bucket Full Ratio (conditional): buffer occupancy with respect to the given BVC
Bucket Size value
This is only used if the Current Bucket Level (CBL) is negotiated. However, the BSC
does not support this functionality.
• BVC Measurement (optional): average queuing delay for the BSC
The BSC sends the next FLOW-CONTROL-BVC PDU to the SGSN after the
TgbFlow timer has expired, if the criteria for controlling the BVC flow are fulfilled or if
the GPRS configuration changes in the BSC, so that the cell buffer size or leak rate
is affected. The TgbFlow timer is restarted and the procedure is repeated whenever
the TgbFlow timer expires.
The BSC performs MS-specific flow control only for mobiles having DL TBF.
Whenever the TgbFlow timer expires, the BSC sends a FLOW-CONTROL-MS PDU
for a TLLI if the criteria for controlling the corresponding MS flow are fulfilled.
Issue: 11-2 DN9983079 23

The FLOW-CONTROL-MS PDU which the BSC sends to the SGSN contains the
following information:
• TLLI that identifies the MS
• MS Bucket Size: data buffer size for downlink LLC frames for this MS
• Bucket Leak Rate: throughput for downlink LLC frames for this MS
• Bucket Full Ratio (conditional): buffer occupancy with respect to the given MS Bucket
Size value
This is only used if the Current Bucket Level (CBL) is negotiated. However, the BSC
does not support this functionality.
Flow control indications allow the SGSN to locally control its transmission output from the
SGSN to the BSC. The SGSN never transmits more data than what can be
accommodated within the BSC buffer for a given BVC or an MS.
Abnormal conditions
If the BSC detects a missing FLOW-CONTROL-ACK from the SGSN and the condition
which causes the sending of a FLOW-CONTROL PDU still remains, a new FLOW-
CONTROL PDU is transmitted. If no reason for flow control exists, no FLOW-CONTROL
PDU is triggered.
1.3.11 BVC Blocking and Unblocking

Figure 11 BVC Blocking and Unblocking
BSC SGSN
BSSGP BSSGP
BVC-BLOCK
BVC-BLOCK-ACK
BVC-UNBLOCK
BVC-UNBLOCK-ACK
The BSC initiates the BVC blocking to remove a BVC from GPRS data use.
The BSC blocks a BVC after:
• BVC deletion with an O&M, disabling the GPRS enabling/disabling parameter of a
cell with the cause value O&M intervention
• O&M disables a cell or a BCF with the cause value O&M intervention
• O&M disables the last GPRS supporting TRX in a cell with the cause value O&M
intervention
• block of the last NS-VC of the NSE that serves the BVC
Related BVCs are implicitly blocked. No indication is sent to the peer BSSGP.
24 DN9983079 Issue: 11-2

• SGSN-initiated BVC-RESET procedure, if necessary, with the cause value BVCI-
blocked
• cell level fault, for example, in the beginning of the site, BTS, or TRX reset with the
cause value Equipment failure
The BSC marks the BVC as blocked and sends a BVC-BLOCK PDU to the SGSN and
starts the TgbBlock timer. The BVC-BLOCK PDU contains the BVCI of the BVC to be
blocked and a cause element indicating the reason for blocking. All downlink UNITDATA
PDUs are discarded and no uplink UNITDATA PDUs are sent on the blocked BVC.
When the SGSN receives a BVC-BLOCK PDU, it marks the indicated BVC as blocked
and stops transmitting traffic that is addressed to this BVC. The SGSN acknowledges the
blocking of the BVC by sending a BVC-BLOCK-ACK PDU to the BSC. The BVC-BLOCK-
ACK PDU contains the BVCI received in the BVC-BLOCK PDU.
When the BSC receives the BVC-BLOCK-ACK PDU, it stops the TgbBlock timer. Further
incoming traffic on the blocked BVC is discarded and a STATUS PDU is returned on the
signalling BVC with the cause value BVCI-blocked. The STATUS PDU indicates the
BVCI of the BVC in which the error was detected.
BVC unblocking is only used when the BSC receives an unexpected BVC-BLOCK-ACK
PDU relating to a BVC that is locally unblocked. In such a case, the BVC is unblocked
with the BVC-UNBLOCK PDU. For more information, see Abnormal conditions.
The signalling BVC is never blocked or unblocked.
Abnormal conditions
If the BSC receives an unexpected BVC-BLOCK-ACK PDU relating to a locally blocked
BVC, it ignores it. If the BVC-BLOCK-ACK PDU is related to a locally unblocked BVC,
the BSC unblocks the BVC with the BVC-UNBLOCK PDU.
If the BSC receives an unexpected BVC-UNBLOCK-ACK PDU relating to a locally
unblocked BVC, it is ignored. If the BVC-UNBLOCK-ACK PDU is related to a locally
blocked BVC, the BSC blocks the BVC with the BVC-BLOCK PDU.
If the BSC does not receive a BVC-BLOCK-ACK PDU for a BVC-BLOCK PDU within
TgbBlock seconds, it repeats the BVC blocking procedure a maximum of
BVCBlockRetries times. After BVCBlockRetries unsuccessful attempts the BVC remains
blocked and the procedure is stopped.
If the BSC does not receive a BVC-UNBLOCK-ACK PDU for a BVC-UNBLOCK PDU
within TgbBlock seconds, it repeats the BVC unblocking procedure a maximum of
BVCUnblockRetries times. After BVCUnblockRetries unsuccessful attempts the
procedure is stopped.
If the BSC receives a BVC-RESET PDU for the signalling BVC while waiting for a BVC-
BLOCK-ACK, it handles the signalling BVC reset procedure first, after which the BVC
block procedure is resumed.
If the BSC receives a BVC-BLOCK-ACK PDU or a BVC-UNBLOCK-ACK PDU for the
signalling BVC, it ignores the PDU.
Issue: 11-2 DN9983079 25

1.3.12 BVC Reset

Figure 12 BVC Reset
BSC SGSN
BSSGP BSSGP
BVC-RESET
BVC-RESET-ACK
The BSC initiates a BVC reset to bring a BVC into GPRS data use. The BVC reset is
used instead of the BVC unblock because of the dynamic configuration of BVCs in the
SGSN.
The BSC resets a BVC after:
• BVC creation or modification with an O&M, enabling the GPRS enabling/disabling
parameter of a cell with the cause value O&M intervention
• O&M enables a cell or a BCF with the cause value O&M intervention
• O&M enables for the first GPRS supporting TRX in a cell with the cause value O&M
intervention
• unblock of the first NS-VC of the NSE that serves the BVC
The signalling BVC is reset first and the rest BVCs after that with the cause value
Network service transmission capacity modified from zero kbps to greater than zero
kbps.
• cell restart, for example, after the site, BTS, or TRX reset, when the restarted object
is up with the cause value Equipment failure
BSC-initiated BVC reset
In the case of a PTP BVC, the BSC sends a BVC-RESET PDU to the SGSN and starts
the TgbReset timer. The BVC-RESET PDU contains the BVCI of the BVC to be reset, a
cause element indicating the reason for reset, and the identifier of the related cell. All
downlink UNITDATA PDUs are discarded and no uplink UNITDATA PDUs are sent on
the BVC until a BVC-RESET-ACK PDU is received for the BVC.
When receiving a BVC-RESET PDU, the SGSN marks the indicated BVC as unblocked.
The SGSN acknowledges the reset of the BVC by sending a BVC-RESET-ACK PDU to
the BSC. The BVC-RESET-ACK PDU contains the BVCI received in the BVC-RESET
PDU.
When receiving the BVC-RESET-ACK PDU, the BSC marks the BVC as unblocked and
stops the TgbReset timer. A flow control procedure is triggered for the reset BVC.
In the case of a signalling BVC, the BSC first resets it. The BVC-RESET PDU contains
the BVCI of the BVC to be reset, a cause element indicating the reason for reset, and the
feature bitmaps (Feature Bitmap/Extended Feature Bitmap) but not the Cell id element.
26 DN9983079 Issue: 11-2

The feature bitmaps are sent to identify the application software that can be supported
by the network service entity. In the signalling BVC-RESET procedure both entities
locally determine the common set of application software products supported by both
NSEs. This is done by performing the bit AND operation of the received feature bitmaps
with its own feature bitmaps.
After completing the signalling BVC reset, the BSC resets the related PTP BVCs and
triggers a flow control procedure for them. All downlink UNITDATA PDUs are discarded
and no uplink UNITDATA PDUs are sent on the PTP BVCs until a BVC-RESET-ACK
PDU is received for them.
SGSN-initiated BVC reset
When the BSC receives a BVC-RESET PDU for a PTP BVC, it marks the BVC as
unblocked, provided that the BVC is not going to be blocked right after the BVC-RESET
procedure. All downlink UNITDATA PDUs are discarded and no uplink UNITDATA PDUs
are sent on the BVC until a BVC-RESET-ACK PDU is returned. A flow control procedure
is triggered for the reset and unblocked BVC.
When the BSC receives a BVC-RESET PDU for a signalling BVC it stops all UNITDATA
PDU traffic on the PTP BVCs of the NSE. After completing the signalling BVC reset, the
BSC resets the related PTP BVCs and triggers a flow control procedure for them. All
downlink UNITDATA PDUs are discarded and no uplink UNITDATA PDUs are sent on
the PTP BVCs until a BVC-RESET-ACK PDU is returned for them.
Abnormal conditions
If the associated network service is not operational, the BVC-RESET procedure is
postponed until the NS is operational again.
If the BSC does not receive a BVC-RESET-ACK PDU for a BVC-RESET PDU within
TgbReset seconds, it repeats the BVC-RESET procedure a maximum of
BVCResetRetries times. After BVCResetRetries unsuccessful attempts the BVC remains
blocked and the procedure is stopped.
If the BSC has sent a BVC-RESET PDU and is waiting for a BVC-RESET-ACK PDU in
response, but receives a BVC-RESET PDU indicating the same BVCI instead, the BSC
interprets it as a BVC-RESET-ACK PDU and the TgbReset timer is stopped. The
received BVC-RESET PDU is not acknowledged to the SGSN.
If the BSC receives an unexpected BVC-RESET-ACK PDU it ignores it.
If the BSC receives a BVC-RESET PDU for an unknown BVCI a STATUS PDU is
returned, including the BVCI and the cause value BVCI unknown.
1.3.13 Trace
The purpose of the trace invocation procedure is to inform the receiving entity that it
should begin producing a trace record on an MS. The SGSN invokes the trace by
sending an SGSN-INVOKE-TRACE PDU to the BSC. The SGSN-INVOKE-TRACE PDU
is not acknowledged.
Trace Reference provides a trace reference number allocated by the triggering entity.
Trace Type provides the type of trace information to be recorded. The BSC supports the
Basic trace (on BSS Record Type) for activating a BSS trace and No BSS Trace (on BSS
Record Type) for deactivating a BSS trace. The BSC ignores any other fields on Trace
Type.
Issue: 11-2 DN9983079 27

Mobile Id indicates the MS relating to the trace. The SGSN includes it in the PDU to
activate or deactivate a trace.
OMC Id, if present, indicates the OMC which the record is destined to. It is not used by
the BSC.
Trigger Id and Transaction Id are not used by the BSC.
1.3.14 Create BSS PFC

The Create BSS PFC procedure is used only if the packet flow context has been
negotiated.
If the BSC receives a request to transfer an uplink or downlink LLC PDU for which it
currently does not have a BSS packet flow context and the PFI does not indicate best-
effort, SMS, or signalling, the BSC sends a DOWNLOAD-BSS-PFC PDU to the SGSN
and starts the timer T6.
If the BSC does not receive a PFI from the MS, for example from a R97 or R98 MS, the
BSC does not send a DOWNLOAD-BSS-PFC PDU to the SGSN. In this case, the best-
effort QoS Profile IE is used instead.
When the SGSN receives a DOWNLOAD-BSS-PFC PDU it sends a CREATE-BSS-PFC
PDU to the BSC with a requested Aggregate BSS QoS Profile. The SGSN may include
the Service UTRAN CCO (Cell Change Order) information element in the PDU. It is
relevant if the network initiated cell change order to UTRAN procedure is used.
When the BSC receives a CREATE-BSS-PFC PDU it stops the timer T6 and responds
with a CREATE-BSS-PFC-ACK PDU, containing the negotiated Aggregate BSS QoS
Profile.
The SGSN may also initiate the Create BSS PFC procedure at any time by sending a
CREATE-BSS-PFC PDU to the BSC.
The BSC may return a CREATE-BSS-PFC-NACK with a cause element if it is unable to
create or modify the PFC.
If the BSC receives a CREATE-BSS-PFC PDU for an MS which has a BSS PFC in the
BSC, the BSC interprets this as a request to modify the existing PFC.
Abnormal conditions
If a CREATE-BSS-PFC PDU is not received for a DOWNLOAD-BSS-PFC PDU within T6
seconds, the DOWNLOAD-BSS-PFC PDU is repeated a maximum of DOWNLOAD-
BSS-PFC-RETRIES attempts. After the DOWNLOAD-BSS-PFC-RETRIES unsuccessful
attempts the procedure is stopped. If a BSS PFC is not received, the BSC handles the
traffic of that PFC according to a best-effort QoS profile.
If the BSC is unable to create the PFC, a CREATE-BSS-PFC-NACK PDU is returned
with a cause value, for example, a Cause value “PFC create failure”. The SGSN stops
the Create BSS PFC procedure.
1.3.15 Delete BSS PFC

The Delete BSS PFC procedure is used only if the packet flow context has been
negotiated.
28 DN9983079 Issue: 11-2

The SGSN may request a deletion of a PFC in BSC at any time by sending a DELETE-
BSS-PFC PDU to the BSC.
When the BSC receives the DELETE-BSS-PFC PDU, it deletes the referred PFC and
sends a DELETE-BSS-PFC-ACK PDU to the SGSN.
1.3.16 RIM procedures
1.3.16.1 RAN Information Request procedure
RAN Information Request procedure is initiated by Controlling BSC, RNC or eNB when it
either requests information or wants to stop information transfer from Serving BSC. The
RAN-INFORMATION-REQUEST PDU specifies the requested operation and the
expected information when applicable. The Controlling BSC, RNC or eNB indicates the
type of operation to Serving BSC. There can be three types of operation: Single Report,
Multiple Report and Stop.
RAN Information Request / Single Report procedure
RAN-INFORMATION-REQUEST/Single Report is used to request a single report.
Figure 13 RAN Information Request/Single report Procedure
In RAN-INFORMATION-REQUEST/Single Report procedure Controlling BSC, RNC or
eNB sends RAN-INFORMATION-REQUEST/Single Report PDU to Serving BSC
containing the Information Elements PDU type, Destination Cell Identifier, Source Cell
Identifier and RIM Container. After the sending the Controlling BSC, RNC or eNB starts
timer T(RIR).
When Serving BSC receives RAN-INFORMATION-REQUEST/Single Report PDU, it
sends the RAN-INFORMATION/Single PDU containing requested information to
Controlling BSC, RNC or eNB.
When Controlling BSC, RNC or eNB receives requested information from Source BSC it
stops T(RIR), delivers the relevant information to the application and the procedure ends.
If T(RIR) expires the controlling BSC, RNC or eNB shall as an implementation option
either inform the application that the procedure has failed or restart the RAN Information
Request/Single Report procedure.
The BSC never acts as controlling BCS in this procedure, i.e. it never sends RAN-
INFORMATION-REQUEST/Single Report, but it is capable to act as serving BSC, i.e. it
may receive and serve RAN-INFORMATION-REQUEST/Single Report for NACC
application.
Issue: 11-2 DN9983079 29

RAN Information Request / Multiple Report procedure
RAN-INFORMATION-REQUEST/Multiple Report is used to request event-driven multiple
reports.
Figure 14 RAN Information Request/Multiple Report Procedure
In RAN-INFORMATION REQUEST/Multiple Report procedure the Controlling BSC, RNC
or eNB sends RAN-INFORMATION-REQUEST/Multiple Report PDU to Serving BSC
containing the Information Elements PDU type, Destination Cell Identifier, Source Cell
Identifier and RIM Container. After the sending the Controlling BSC, RNC or eNB starts
T(RIR).
When Serving BSC receives RAN-INFORMATION-REQUEST/Multiple Report PDU, it
records the subscription and sends the RAN-INFORMATION/Initial Multiple Report PDU
containing requested information to Controlling BSC, RNC or eNB. If RAN-
INFORMATION-REQUEST/Multiple Report PDU is received for the already recorded
subscription the PDU will be discarded and the procedure ends.
When Controlling BSC, RNC or eNB receives requested information from Serving BSC it
stops T(RIR), delivers the relevant information to the application and the procedure ends.
Request/Single Report procedure. The BSC restarts the procedure once in T(RIR)
expiry.
RAN Information Request / Stop procedure
RAN-INFORMATION-REQUEST/Stop is used to stop event driven multiple reports.
Figure 15 RAN Information Request/Stop Procedure
30 DN9983079 Issue: 11-2

In RAN-INFORMATION REQUEST/Stop procedure the Controlling BSC, RNC or eNB
sends RAN-INFORMATION-REQUEST/Stop PDU to Serving BSC containing the
Information Elements PDU type, Destination Cell Identifier, Source Cell Identifier and
RIM Container. After the sending the Controlling BSC, RNC or eNB may start T(RIR).
When Serving BSC receives RAN-INFORMATION-REQUEST/Stop PDU, it removes the
subscription and sends the RAN-INFORMATION/Stop PDU containing requested
information to Controlling BSC, RNC or eNB. If RAN-INFORMATION-REQUEST/Stop
PDU is received for not-existing subscription the PDU will be discarded and the
procedure ends.
When Controlling BSC, RNC or eNB receives the response from Serving BSC,
Controlling BSC, RNC or eNB stops T(RIR), delivers the relevant information to the
application and the procedure ends.
Request/Stop procedure.
The BSC acting as controlling BSC does not control the reception of the response to a
previously transmitted RAN-INFORMATION-REQUEST PDU, i.e. timer T(RIR) is not
used and possibly received RAN-INFORMATION/Stop is not used.
1.3.16.2 RAN Information Send procedure
RAN Information Send procedure is used to transfer application information form serving
BSC to controlling BSC, RNC or eNB via the core network.
Figure 16 Acknowledged RAN Information Send procedure
If multiple reporting has been subscribed for a given RIM association, the RAN
Information Send procedure is initiated by the application in the serving BSC either to
send updated information (using the RAN-INFORMATION/Multiple Report PDU) or to
indicate that multiple reporting has been deactivated on the serving BSC side (using the
RAN-INFORMATION/End PDU).
Upon initiation serving BSC sends RAN-INFORMATION/Multiple Report or RAN-
INFORMATION/End PDU to Controlling BSC, RNC or eNB containing the Information
Elements PDU type, Destination Cell Identifier, Source Cell Identifier and RIM Container.
Acknowledgement for the PDU may or may not be requested. If acknowledgement was
requested serving BSC starts timer T(RI) after the sending.
Issue: 11-2 DN9983079 31

When Controlling BSC, RNC or eNB receives RAN-INFORMATION/Multiple Report or
RAN INFORMATION/End PDU, it delivers the relevant information to the application. If
acknowledgement was requested Controlling BSC, RNC or eNB sends RAN-
INFORMATION-ACK PDU to the serving BSC. If the RAN-INFORMATION PDU is a
RAN-INFORMATION/End, the controlling BSC shall consider that multiple reporting is
deactivated for this RIM association in the serving BSC.
When Serving BSC receives the RAN-INFORMATION-ACK PDU which matches to the
RAN-INFORMATION PDU which has initiated the procedure, it stops T(RI) and the
procedure ends.
If T(RI) expires the serving BSC shall as an implementation option either inform the
application that the procedure has failed or restart the RAN Information Send procedure.
The BSC acting as serving BSC never requests acknowledgement for the RAN-
INFORMATION/Multiple Report PDU. The BSC acting as serving BSC requests
acknowledgement for the RAN-INFORMATION/End PDU, but does not control the
reception of the acknowledgement, i.e. timer T(RI) is not used and possibly received
RAN-INFORMATION-ACK is not used.
1.3.16.3 RAN Information Application Error procedure
The RAN Information Application Error procedure is initiated by an application in the
controlling BSC, RNC or eNB to transfer application error information to the peer
application entity of the same application in the serving BSC.
Figure 17 RAN Information Application Error procedure
Upon initiation of the procedure the controlling BSC, RNC or eNB sets the PDU type
Information element, Source Cell Identifier and Destination Cell Identifier Information
elements from erroneous application container of RAN-INFORMATION PDU and RIM
Container to RAN-INFORMATION-APPLICATION-ERROR PDU and sends it to serving
BSC. Acknowledgement for the PDU may or may not be requested. If acknowledgement
was requested timer T(RIAE) is started after the sending.
When the serving BSC receives valid RAN-INFORMATION-APPLICATION-ERROR
PDU, it delivers the relevant information to the application. If acknowledgement was
requested serving BSC sends RAN-INFORMATION-ACK PDU to the controlling BSC,
RNC or eNB.
When controlling BSC, RNC or eNB receives the RAN-INFORMATION-ACK PDU which
matches to the RAN-INFORMATION-APPLICATION-ERROR PDU which has initiated
the procedure, it stops T(RIAE) and the procedure ends.
32 DN9983079 Issue: 11-2

The BSC never acts as controlling BCS in this procedure, i.e. it never sends RAN-
INFORMATION-APPLICATION-ERROR PDU. Though BSC does not take any other
action on received RAN-INFORMATION-APPLICATION-ERROR PDU but if
acknowledgement was requested serving BSC sends RAN-INFORMATION-ACK PDU to
the controlling BSC, RNC or eNB.
1.3.16.4 RAN Information Error procedure
The RAN Information error procedure is initiated by the RIM entity in the controlling BSC,
RNC or eNB or the serving BSC to transfer error information to the RIM entity in the peer
BSC, RNC or eNB.
Figure 18 RAN Information Error procedure
A BSC, RNC or eNB which receives en erroneous RIM PDU, sets the information of the
PDU type, Source Cell Identifier and Destination Cell Identifier Information elements from
the erroneous RIM PDU and RIM Container Information elements to the RAN-
INFORMATION-ERROR PDU and sends the PDU to peer BSC, RNC or eNB.
The actions to be taken upon reception of a valid RAN-INFORMATION-ERROR PDU are
an implementation-dependent option. When peer BSC, RNC or eNB receives the
erroneous RAN-INFORMATION-ERROR PDU it discards received PDU.
1.3.16.5 Abnormal conditions
If a BSC receives from an SGSN a RIM PDU with a Destination Cell Identifier IE value
which does not match the cell identifier of any of its parented cells, the PDU shall be
discarded and a STATUS PDU with the appropriate cause value "Unknown Destination
address" shall be sent back to the SGSN.
If the RIM container included in a RAN-INFORMATION PDU, RAN-INFORMATION-
REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-
APPLICATION-ERROR PDU contains an unknown value in the RIM Application Identity
IE or if the RIM application is disabled when receiving a RAN-INFORMATION-REQUEST
PDU, the BSC shall send a RIM Cause IERROR PDU with the RIM Cause IE set to
“Unknown RIM Application Identity or RIM application disabled” back to the originating
BSC and discard the received PDU.
If the RIM container included in a RAN-INFORMATION-ERROR PDU contains an
unknown value in the RIM Application Identity IE, the BSC shall discard the RIM PDU
without further action.
Issue: 11-2 DN9983079 33

If the PDU Type Extension field in the RIM PDU Indications IE included in the RIM
container of a RAN-INFORMATION-REQUEST PDU does not indicate “RAN-
INFORMATION-REQUEST/Multiple Report”, “RAN-INFORMATION-REQUEST/Stop” or
“RAN-INFORMATION-REQUEST/Single Report”, the serving BSC shall send a RAN-
INFORMATION-ERROR PDU containing the complete received PDU and with the RIM
Cause IE set to “PDU not compatible with the feature set” back to the originating BSC
and shall discard the received PDU.
If the PDU Type Extension field in the RIM PDU Indications IE included in the RIM
container of a RAN-INFORMATION PDU does not indicate “RAN-INFORMATION/Single
Report”, “RAN-INFORMATION/Multiple Report”, “RAN-INFORMATION/Initial Multiple
Report”, “RAN-INFORMATION/Stop” or “RAN-INFORMATION/End”, the serving BSC
shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU
and with the RIM Cause IE set to “PDU not compatible with the feature set” back to the
originating BSC and shall discard the received PDU.
If an expected conditional Information Element is not included in the RIM container of a
RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-
INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU, the
BSC shall send a RAN-INFORMATION-ERROR PDU containing the complete received
PDU and with the RIM Cause IE set to “Missing Conditional IE” back to the originating
BSC and discard the received PDU.
If an expected conditional Information Element is not included in the RIM container of a
RAN-INFORMATION-ERROR PDU, the BSC shall discard the received PDU without
further action.
If a mandatory Information Element is not included in the RIM container of a RAN-
INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK
PDU or RAN-INFORMATION-APPLICATION-ERROR PDU, the BSC shall send a RAN-
INFORMATION-ERROR PDU containing the complete received PDU and with the RIM
Cause IE set to “Missing Mandatory IE” back to the originating BSC and discard the
received PDU.
If a mandatory Information Element is not included in the RIM container of a RAN-
INFORMATION-ERROR PDU, the BSC shall discard the received PDU without further
action.
If a syntactical error is detected in an expected conditional Information Element included
in the RIM container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST
PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR
PDU, the BSC shall send a RAN-INFORMATION-ERROR PDU containing the complete
received PDU and with the RIM Cause IE set to “Conditional IE error” back to the
originating BSC and discard the received PDU.
If a syntactical error is detected in an expected conditional Information Element included
in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSC shall discard the
received PDU without further action.
If a syntactical error, other than unknown RIM Application Identity IE or erroneous PDU
Type Extension field mentioned above, is detected in a mandatory IE included in the RIM
container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-
PDU and with the RIM Cause IE set to “Invalid mandatory information” back to the
34 DN9983079 Issue: 11-2

If a syntactical error is detected in a mandatory IE included in the RIM container of a
further action.
If an unexpected conditional Information Element is received in the RIM container of a
RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-
PDU and with the RIM Cause IE set to “Unexpected Conditional IE” back to the
If an unexpected conditional Information Element is received in the RIM container of a
further action.
The receiving BSC may accept RIM containers that include information elements that do
not appear to be in the correct sequence. However, BSC does not accept out of
sequence information elements in RIM messages. Elements that occur more than once
in a RIM container shall be assumed to have been transmitted in the correct order.
Recipients that do not accept out of sequence information elements, as BSC, shall
regard the RIM container as containing unexpected and/or missing information elements
and follow the procedures which are defined for unexpected and/or missing information
elements.
When any IE with semantically incorrect contents is received within a RIM container, the
receiving BSC shall react according to the relevant protocol specification. If however no
such reactions are specified, the receiving BSC shall ignore that IE and treat the rest of
the RIM container. If the rest of the RIM container can no longer be handled because this
IE was ignored then the receiving BSC shall send a RAN-INFORMATION-ERROR PDU
containing the complete received PDU and with the RIM Cause IE set to “Semantically
incorrect PDU” back to the originating BSC and discard the received PDU.
If a BSC receives a RIM PDU in a case not covered by the RIM procedures, it shall
discard the RIM PDU without further action.
1.4 General protocol error handling

The BSC discards any type of BSSGP PDU received for a feature that is not negotiated
and sends a STATUS PDU with the cause value PDU not compatible with the feature
set.
The reporting of protocol errors to the peer BSSGP is done by means of the STATUS
PDU. The STATUS PDU is returned on the same BVC as the erroneous PDU was
received. If an error is detected in a received STATUS PDU, the error is not reported to
the peer BSSGP.
For more information on general protocol error handling, see
1.5 BSSGP protocol data units (PDUs)

For the general structure of PDUs, for example, octet and bit codings, see Network
service control protocol data units (PDUs) in Network Service Protocol (NS).
Issue: 11-2 DN9983079 35

1.5.1 DL-UNITDATA
This PDU is sent to the BSC to transfer a LLC-PDU on the radio interface to an MS.
PDU type: DL-UNITDATA.
Direction: SGSN to BSC.
Information element Type / Reference Presence Format Length
PDU type PDU type M V 1
TLLI (current) TLLI M V 4
QoS Profile QoS Profile M V 3
PDU Lifetime PDU Lifetime M TLV 4
MS Radio Access MS Radio Access Capability O TLV 7-?

Capability a)
Priority b) Priority O TLV 3
DRX Parameters DRX Parameters O TLV 4
IMSI IMSI O TLV 5-10
TLLI (old) TLLI O TLV 6
PFI PFI O TLV 3
LSA Information b) LSA Information O TLV 7-?
Service UTRAN CCO Service UTRAN CCO O TLV 3
Subscriber Profile ID for Subscriber Profile ID for O TLV 3

RAT/Frequency priority b) RAT/Frequency priority
Redirection Indication Redirection Indication O TLV 3
Redirection Completed IMSI O TLV 3
Unconfirmed send state Unconfirmed send state variable O TLV 4

variable
Service Class Indicatorc) Service Class Indicator O TLV 3
Alignment octets Alignment octets O TLV 2–5
LLC-PDU d) LLC-PDU M TLV 2-?
36 DN9983079 Issue: 11-2

Initial LLC-PDU LLC-PDU O TLV 2-?
a) The field is present only if there is valid MS Radio Access Capability information
known by the SGSN.
b) Not used.
c)This is a proprietary Service Class Indicator, not standardized in TS 48.018.
d) The LLC-PDU Length Indicator may be zero.
1.5.2 UL-UNITDATA
This PDU transfers the LLC-PDU of an MS and its associated radio interface information
on the Gb interface.
PDU type: UL-UNITDATA.
Direction: BSC to SGSN.
TLLI TLLI M V 4
QoS Profile QoS Profile M V 3
Cell Identifier Cell Identifier M TLV 10
PFI PFI O TLV 3
LSA Identifier List a) LSA Identifier List O TLV 3-?
Redirect Attempt Flag Redirect Attempt Flag O TLV 3
Unconfirmed send state Unconfirmed send state O TLV 4

variable variable
Alignment octets Alignment octets O TLV 2-5
LLC-PDU b) LLC-PDU M TLV 2-?
a) Not used.
b) The LLC-PDU Length Indicator may be zero.
Issue: 11-2 DN9983079 37

1.5.3 RA-CAPABILITY
This PDU informs the BSC of the new Radio Access Capability of an MS.
PDU type: RA-CAPABILITY.
TLLI TLLI M TLV 6
MS Radio Access Capability MS Radio Access M TLV 7-?

Capability
1.5.4 PAGING-PS
This PDU indicates that a BSC initiates the packet paging procedure for an MS within a
group of cells.
PDU type: PAGING PS.
Information elements Type / Reference Presence Format Length
IMSI IMSI M TLV 5-10
DRX Parameters DRX Parameters O TLV 4
BVCI a) BVCI C TLV 4
Location Area a) Location Area C TLV 7
Routing Area a) Routing Area C TLV 8
BSS Area Indication a) BSS Area Indication C TLV 3
PFI b) PFI O TLV 3
ABQP b) ABQP O TLV 13-?
QoS Profile b) QoS Profile M TLV 5
P-TMSI TMSI O TLV 6
38 DN9983079 Issue: 11-2

a) Only one of the conditional IEs is present. No repeated instances of the conditional IEs
are permissible (for example not more than one Location Area can be present).
b) Not used.
1.5.5 PAGING-CS
This PDU indicates that a BSC initiates a circuit-switched paging procedure for an MS
within a group of cells.
PDU type: PAGING CS.
IMSI IMSI M TLV 5-10
DRX Parameters DRX Parameters M TLV 4
Location Area a) Location Area C TLV 7
Routing Area a) Routing Area C TLV 8
BSS Area Indication a) BSS Area Indication C TLV 3
TLLI TLLI O TLV 6
Channel needed b) Channel needed O TLV 3
eMLPP-Priority b) eMLPP-Priority O TLV 3
TMSI b) TMSI O TLV 6
Global CN-Id b) Global CN-Id O TLV 7
a) Only one of the conditional IEs is present. No repeated instances of the conditional IEs
are permissible (for example not more than one Location Area can be present).
b) These fields shall be provided by the MSC via the Gs-Interface.
1.5.6 RA-CAPABILITY-UPDATE
This PDU requests that the SGSN sends the MS's current Radio Access capability or
IMSI to the BSC.
PDU type: RA-CAPABILITY-UPDATE.
Issue: 11-2 DN9983079 39

Information Type/Reference Presence Format Length

element
TLLI TLLI M TLV 6
Tag Tag M TLV 3
1.5.7 RA-CAPABILITY-UPDATE-ACK
This PDU provides the BSC with the MS's current Radio Access capability and IMSI.
PDU type: RA-CAPABILITY-UPDATE-ACK.
Information Type/Reference Presence Format Length

element
TLLI TLLI M TLV 6
Tag Tag M TLV 3
IMSI a) IMSI C TLV 5–10
RA-Cap-UPD- RA-Cap-UPD- M TLV 3

Cause Cause
MS radio Access MS Radio Access C TLV 7–?

Capability a) Capability
a) If RA-Cap-UPD-Cause is not set to "OK", then neither the MS Radio Access Capability
nor the IMSI shall be present. Otherwise, the IMSI will be present.
1.5.8 RADIO-STATUS
This PDU indicates that an exception condition related to the radio interface has
occurred.
PDU type: RADIO-STATUS
Direction: BSC to SGSN
40 DN9983079 Issue: 11-2

TLLI a) TLLI C TLV 6
TMSI a) TMSI C TLV 6
IMSI a) IMSI C TLV 5-10
Radio Cause Radio Cause M TLV 3
a) Only one of the conditional IEs is present. TLLI is always used by the BSC.
1.5.9 SUSPEND
This PDU indicates that an MS wants to suspend its GPRS service.
PDU type: SUSPEND.
TLLI TLLI M TLV 6
Routing Area Routing Area M TLV 8
1.5.10 SUSPEND-ACK
This PDU positively acknowledges the reception of a SUSPEND PDU for an MS.
PDU type: SUSPEND-ACK.
TLLI TLLI M TLV 6
Issue: 11-2 DN9983079 41

Suspend Reference Number Suspend Reference M TLV 3

Number
1.5.11 SUSPEND-NACK
This PDU negatively acknowledges the reception of a SUSPEND PDU for an MS.
PDU type: SUSPEND-NACK.
TLLI TLLI M TLV 6
Cause Cause O TLV 3
1.5.12 RESUME
This PDU indicates that an MS wishes to resume its GPRS service.
PDU type: RESUME.
TLLI TLLI M TLV 6
Suspend Reference Number Suspend Reference Number M TLV 3
1.5.13 RESUME-ACK
This PDU acknowledges the reception of a RESUME PDU for an MS.
PDU type: RESUME-ACK.
42 DN9983079 Issue: 11-2

TLLI TLLI M TLV 6
1.5.14 RESUME-NACK
This PDU negatively acknowledges the reception of a RESUME PDU for an MS.
PDU type: RESUME-NACK.
TLLI TLLI M TLV 6
Cause Cause O TLV 3
1.5.15 FLUSH-LL
This PDU informs a BSC that an MS has moved from one cell to another.
PDU type: FLUSH-LL.
TLLI TLLI M TLV 6
BVCI (old) BVCI M TLV 4
BVCI (new) BVCI O TLV 4
NSEI (new) a) NSEI O TLV 4
a) Not supported.
Issue: 11-2 DN9983079 43

1.5.16 FLUSH-LL-ACK
This PDU indicates that LLC-PDU(s) buffered for an MS in the old cell have been either
deleted or transferred to the new cell within the NSE.
PDU type: FLUSH-LL-ACK
TLLI TLLI M TLV 6
Flush Action Flush Action M TLV 3
BVCI (new) BVCI C a) TLV 4
Number of octets affected Number of octets affected M TLV 5
NSEI (new) NSEI C b) TLV 4
a) BVCI (new) is included only if Flush action indicated that LLC-PDUs are transferred.
b) Not supported.
1.5.17 LLC-DISCARDED
This PDU indicates that a number of buffered LLC-PDUs in a cell for an MS have been
deleted inside the BSC.
PDU type: LLC-DISCARDED.
TLLI TLLI M TLV 6
LLC Frames Discarded LLC Frames Discarded M TLV 3
BVCI BVCI M TLV 4
Number of octets deleted Number of octets M TLV 5

affected
PFI a) PFI O TLV 3
44 DN9983079 Issue: 11-2

a) Not used.
1.5.18 FLOW-CONTROL-BVC
This PDU informs the flow control mechanism in the SGSN of the status of a BVC's
maximum acceptable throughput from the SGSN to the BSC on the Gb interface.
PDU type: FLOW-CONTROL-BVC.
Tag Tag M TLV 3
BVC Bucket Size BVC Bucket Size M TLV 4
Bucket Leak Rate Bucket Leak Rate M TLV 4
Bmax default MS Bmax default MS M TLV 4
R_default_MS R_default_MS M TLV 4
Bucket Full Ratio a) Bucket Full Ratio C TLV 3
BVC Measurement BVC Measurement O TLV 4
Flow Control Granularity a) Flow Control Granularity O TLV 3
a) Not used
1.5.19 FLOW-CONTROL-BVC-ACK
This PDU informs the flow control mechanism in the BSC that the SGSN has received
the FLOW-CONTROL-BVC PDU indicated by the Tag.
PDU type: FLOW-CONTROL-BVC-ACK.
Tag Tag M TLV 3
Issue: 11-2 DN9983079 45

1.5.20 FLOW-CONTROL-MS
This PDU informs the flow control mechanism in the SGSN of the status of an MS's
maximum acceptable throughput from the SGSN to the BSC on the Gb interface.
PDU type: FLOW-CONTROL-MS.
TLLI TLLI M TLV 6
Tag Tag M TLV 3
MS Bucket Size MS Bucket Size M TLV 4
Bucket Leak rate Bucket Leak rate M TLV 4
Bucket Full Ratio a) Bucket Full Ratio C TLV 3
Flow Control Granularity a) Flow Control Granularity O TLV 3
a) Not used.
1.5.21 FLOW-CONTROL-MS-ACK
This PDU informs the flow control mechanism at the BSC that the SGSN has received
the FLOW-CONTROL-MS PDU indicated by the TLLI and the Tag.
PDU type: FLOW-CONTROL-MS-ACK.
TLLI TLLI M TLV 6
Tag Tag M TLV 3
1.5.22 BVC-BLOCK
This PDU indicates that the contained BVC is blocked at the recipient entity.
PDU type: BVC-BLOCK.
46 DN9983079 Issue: 11-2

BVCI BVCI M TLV 4
Cause Cause M TLV 3
Typical cause values are O&M intervention and Equipment failure.
1.5.23 BVC-BLOCK-ACK
This PDU acknowledges that a BVC has been blocked.
PDU type: BVC-BLOCK-ACK.
BVCI BVCI M TLV 4
1.5.24 BVC-UNBLOCK
This PDU indicates that the identified BVC is unblocked at the recipient entity.
PDU type: BVC-UNBLOCK.
BVCI BVCI M TLV 4
1.5.25 BVC-UNBLOCK-ACK
This PDU acknowledges that a BVC has been unblocked.
PDU type: BVC-UNBLOCK-ACK.
Issue: 11-2 DN9983079 47

BVCI BVCI M TLV 4
1.5.26 BVC-RESET
This PDU indicates that BVC initialization is required.
PDU type: BVC-RESET.
Direction: SGSN to BSC, BSC to SGSN.
BVCI BVCI M TLV 4
Cause Cause M TLV 3
Cell Identifier a) Cell Identifier C TLV 10
Feature Bitmap b) Feature Bitmap O TLV 3
Extended Feature Bitmap c) Extended Feature O TLV 3

Bitmap
Typical cause values are:
• O&M intervention
• Equipment failure
• Network service transmission capacity modified from zero kbps to greater than zero
kbps
a) Always included in the BSC in the case of a PTP BVC. Not included in the case of a
signalling BVC.
b) The Feature Bitmap is only sent in a BVC-RESET PDU related to the signalling BVC.
Absence of this IE implies that no application software products are available over the
NSE.
c) The Extended Feature Bitmap is only sent in a BVC-RESET PDU related to the
signalling BVC.
1.5.27 BVC-RESET-ACK
This PDU indicates that BVC recovery procedures have been executed.
48 DN9983079 Issue: 11-2

PDU type: BVC-RESET-ACK.
Direction: BSC to SGSN, SGSN to BSC.
BVCI BVCI M TLV 4
Cell Identifier a) Cell Identifier C TLV 10
Feature Bitmap b) Feature Bitmap O TLV 3
Extended Feature Bitmap c) Extended Feature O TLV 3

Bitmap
a) Always included in the BSC in the case of a PTP BVC. Not included in the case of a
signalling BVC.
b) The Feature Bitmap is only sent in a BVC-RESET-ACK PDU related to the signalling
BVC. Absence of this IE implies that no application software products are available over
the NSE.
c) The Extended Feature Bitmap is only sent in a BVC-RESET-ACK PDU related to the
signalling BVC.
1.5.28 STATUS
This PDU indicates that an exceptional condition occurred.
PDU type: STATUS.
Direction: SGSN to BSC, BSC to SGSN.
Cause Cause M TLV 3
PDU In Error b) PDU In Error O TLV 3-?
a) The BVCI IE is only included when the Cause IE is set to one of the following values:
• BVCI-blocked
• BVCI Unknown
Issue: 11-2 DN9983079 49

b) This is the whole PDU, starting with the PDU type, within which an error was detected.
This PDU may be truncated if it exceeds the information carrying capacity of the
underlying network service.
1.5.29 SGSN-INVOKE-TRACE
This PDU indicates that the BSC begins the production of a trace record for an MS.
PDU type: SGSN-INVOKE-TRACE.
Trace Type Trace Type M TLV 3
Trace Reference Trace Reference M TLV 4
Trigger Id a) Trigger Id O TLV 4-24
Mobile Id Mobile Id O TLV 3-10
OMC Id a) OMC Id O TLV 4-24
Transaction Id a) Transaction Id O TLV 4
a) Not used by the BSC.
1.5.30 DOWNLOAD-BSS-PFC
This PDU requests an SGSN to initiate a CREATE-BSS-PFC procedure.
PDU type: DOWNLOAD-BSS-PFC.
TLLI TLLI M TLV 6
PFI PFI M TLV 3
Used only if the Packet Flow Context (PFC) has been negotiated.
50 DN9983079 Issue: 11-2

1.5.31 CREATE-BSS-PFC
This PDU allows the SGSN to request the BSC to create or modify a BSS Packet Flow
Context.
PDU type: CREATE-BSS-PFC.
TLLI TLLI M TLV 6
PFI PFI M TLV 3
PFT GPRS Timer M TLV 3
ABQP ABQP M TLV 13-?
Service UTRAN CCO Service UTRAN CCO O TLV 3
MS Radio Access MS Radio Access O TLV 7-?

Capability a) Capability
Allocation/Retention Priority Priority O TLV 3

b)
T10 b) GPRS Timer C TLV 3
Inter RAT Handover Info b) Inter RAT Handover Info O TLV 3-?
E-UTRAN Inter RAT E-UTRAN Inter RAT O TLV 3-?

Handover Info b) Handover Info
Subscriber Profile ID for Subscriber Profile ID for O TLV 3

RAT/Frequency priority b) RAT/Frequency priority
a) The MS RAC IE, if received, is ignored
b) Not used
1.5.32 CREATE-BSS-PCF-ACK
This PDU allows the BSC to acknowledge a request from the SGSN for the creation or
modification of a BSS Packet Flow Context.
PDU type: CREATE-BSS-PFC-ACK.
Issue: 11-2 DN9983079 51

TLLI TLLI M TLV 6
PFI PFI M TLV 3
ABQP ABQP M TLV 13-?
Cause Cause O TLV 3
1.5.33 CREATE-BSS-PFC-NACK
This PDU allows the BSC to not acknowledge a request from the SGSN for the creation
of a BSS Packet Flow Context.
PDU type: CREATE-BSS-PFC-NACK.
TLLI TLLI M TLV 6
PFI PFI M TLV 3
Cause Cause M TLV 3
1.5.34 DELETE-BSS-PFC
This PDU allows the SGSN to request a BSC to delete a BSS Packet Flow Context.
PDU type: DELETE-BSS-PFC.
52 DN9983079 Issue: 11-2

TLLI TLLI M TLV 6
PFI PFI M TLV 3
1.5.35 DELETE-BSS-PFC-ACK
This PDU allows the BSC to acknowledge a request for the deletion of a BSS Packet
Flow Context.
PDU type: DELETE-BSS-PFC-ACK.
TLLI TLLI M TLV 6
PFI PFI M TLV 3
1.5.36 RAN-INFORMATION-REQUEST
The RAN-INFORMATION-REQUEST PDU allows a controlling BSC, RNC or eNB to
request information from serving BSC.
PDU type: RAN-INFORMATION-REQUEST.
Direction: BSS to SGSN, SGSN to BSS
Destination Cell Identifier RIM Routing Information M TLV 3-?
Source Cell Identifier RIM Routing Information M TLV 3-?
Issue: 11-2 DN9983079 53

RIM Container RAN- M TLV 3-?

INFORMATION_REQUE
ST RIM Container
1.5.37 RAN-INFORMATION
The RAN-INFORMATION PDU allows a serving BSC to send information to a controlling
BSC, RNC or eNB.
PDU type: RAN INFORMATION
RIM Container RAN- M TLV 3-?

INFORMATION_RIM
Container
1.5.38 RAN-INFORMATION-ACK
The RAN-INFORMATION-ACK PDU allows a controlling BSC, RNC or eNB to
acknowledge the reception of a RAN-INFORMATION PDU and a serving BSC to
acknowledge the reception of a RAN-INFORMATION-APPLICATION-ERROR PDU.
PDU type: RAN-INFORMATION-ACK
RIM Container RAN-INFORMATION- M TLV 3-?

ACK_RIM Container
54 DN9983079 Issue: 11-2

1.5.39 RAN-INFORMATION-ERROR
The RAN-INFORMATION-ERROR PDU allows a BSC, RNC or eNB to send an error
PDU back to an originating BSC, RNC or eNB as a response to a RAN-INFORMATION,
a RAN-INFORMATION-REQUEST, a RAN-INFORMATION-ACK or a RAN-
INFORMATION-APPLICATION-ERROR PDU.
PDU type: RAN-INFORMATION-ERROR

ERROR_RIM Container
1.5.40 RAN-INFORMATION-APPLICATION-ERROR
The RAN-INFORMATION-APPLICATION-ERROR PDU allows a controlling BSC, RNC
or eNB to inform the serving BSC about erroneous application information in a previously
received RAN-INFORMATION PDU.
PDU type: RAN-INFORMATION-APPLICATION-ERROR

APPLICATION-
ERROR_RIM Container
1.6 BSSGP information elements (IEs)

This chapter includes only the IEs defined in the TS 48.018, which has to be encoded or
decoded in the BSC. IEs are listed in IEI code order.
Issue: 11-2 DN9983079 55

For the general structure of the information elements, for example, length indicator
coding, see General structure of the information elements in TS 48.016.
1.6.1 IEI codings
IEI coding IEI Types
(hexadecimal)
x00 Alignment Octets
x01 Bmax default MS
x02 BSS Area Indication
x03 Bucket Leak Rate
x04 BVCI
x05 BVC Bucket Size
x06 BVC Measurement
x07 Cause
x08 Cell Identifier
x09 Channel needed
x0a DRX Parameters
x0b eMLPP-Priority
x0c Flush Action
x0d IMSI
x0e LLC-PDU
x0f LLC Frames Discarded
x10 Location Area
x11 Mobile Id
x12 MS Bucket Size
x13 MS Radio Access Capability
x14 OMC Id
56 DN9983079 Issue: 11-2

x15 PDU In Error
x16 PDU Lifetime
x17 Priority
x18 QoS Profile
x19 Radio Cause
x1a RA-Cap-UPD-Cause
x1b Routing Area (Term Routing Area used in the 3GPP TS 48.018.)
x1c R_default_MS
x1d Suspend Reference Number
x1e Tag
x1f TLLI
x20 TMSI
x21 Trace Reference
x22 Trace Type
x23 Transaction Id
x24 Trigger Id
x25 Number of octets affected
x26 LSA Identifier List
x27 LSA Information
x28 Packet Flow Identifier
x29 GPRS Timer a)
x3a Aggregate BSS QoS Profile (ABQP)
x3b Feature Bitmap
x3c Bucket Full Ratio
x3d Service UTRAN CCO (Cell Change Order)
Issue: 11-2 DN9983079 57

x3e NSEI
x3f RRLP APDU a)
x40 LCS QoS a)
x41 LCS Client Type a)
x42 Requested GPS Assistance Data a)
x43 Location Type a)
x44 Location Estimate a)
x45 Positioning Data a)
x46 Deciphering Keys a)
x47 LCS Priority a)
x48 LCS Cause a)
x49 LCS Capability a)
x4a RRLP Flags a)
x4b RIM Application Identity
x4c RIM Sequence number
x4d RAN-INFORMATION-REQUEST Application Container
x4e RAN-INFORMATION Application Container
x4f RIM PDU Indications
x50 This value is reserved for future use and is treated as an unknown IEI by
the recipient.
x51 This value should not be used, as it has been used in the earlier
versions of this protocol.
x52 PFC flow control parameters a)
x53 Global CN-Id
x54 RIM Routing Information
x55 RIM Protocol Version Number
58 DN9983079 Issue: 11-2

x56 Application Error Container
x57 RAN-INFORMATION-REQUEST RIM Container
x58 RAN-INFORMATION RIM Container
x59 RAN-INFORMATION-APPLICATION-ERROR RIM Container
x5a RAN-INFORMATION-ACK RIM Container
x5b RAN-INFORMATION-ERROR RIM Container
x5c TMGI a)
x5d MBMS Session Identity a)
x5e MBMS Session Duration a)
x5f MBMS Service Area Identity List a)
x60 MBMS Response a)
x61 MBMS Routing Area List a)
x62 MBMS Session Information a)
x63 MBMS Stop Cause a)
x64 Source BSS to Target BSS Transparent Container a)
x65 Target BSS to Source BSS Transparent Container a)
x66 NAS container for PS Handover a)
x67 PFCs to be set-up list a)
x68 List of set-up PFCs a)
x69 Extended Feature Bitmap
x6a Source to Target Transparent Container a)
x6b Target to Source Transparent Container a)
x6c RNC Identifier a)
x6d Page Mode a)
Issue: 11-2 DN9983079 59

x6e Container ID a)
x6f Global TFI a)
x70 IMEI a)
x71 Time to MBMS Data Transfer a)
x72 MBMS Session Repetition Number a)
x73 Inter RAT Handover Info a)
x74 PS Handover Command a)
x75 PS Handover Indications a)
x76 SI/PSI Container a)
x77 Active PFCs List a)
x78 Velocity Data a)
x79 DTM Handover Command a)
x7a CS Indication a)
x7b Requested GANSS Assistance Data a)
x7c GANSS Location Type a)
x7d GANSS Positioning Data a)
x7e Flow Control Granularity
x7f eNB Identifier a)
x80 E-UTRAN Inter RAT Handover Info a)
x81 Subscriber Profile ID for RAT/Frequency priority
x82 Request for Inter RAT Handover Info a)
x83 Reliable Inter RAT Handover Info a)
x84 SON Transfer Application Identity
x85 CSG Identifier a)
60 DN9983079 Issue: 11-2

x86 TAC a)
x87 Redirect Attempt Flag
x88 Redirection Indication
x89 Redirection Completed
x8a Unconfirmed send state variable
x8b IRAT Measurement Configuration a)
x99 Service Class Indicator b)
a) The IE may be used only in PDUs, which are not supported in the BSC. Therefore it is
not described in this document.
b) This is a proprietary Service Class Indicator, not standardized in TS 48.018.
1.6.2 Alignment Octets

The Alignment Octets information element is used to align a subsequent IEI onto a 32 bit
boundary. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator a)
Octet 3-5 Spare octet
a) The Length Indicator may indicate that spare octets from 0 to 3 are present.
1.6.3 Bmax Default MS

This information element indicates the default bucket size (Bmax) in octets for an MS.
The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Issue: 11-2 DN9983079 61

8 7 6 5 4 3 2 1
Octet 3-4 Bmax
The Bmax field is coded as Bmax in the BVC Bucket Size IE.
1.6.4 BSS Area Indication

This information element is used to indicate that the paging is done in all the cells within
the BSS. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 BSS indicator
The coding of octet 2 is a binary number indicating the Length of the remaining element.
The coding of octet 3 is not specified. The BSC ignores the value of this octet. Only IEI
coding is meaningful for the BSC.
1.6.5 Bucket Leak Rate

This information element indicates the leak rate (R) to be applied to a flow control
bucket. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 R Value (MSB)
Octet 4 R Value (LSB)
The R field is the binary encoding of the rate information expressed in 100 bits/sec
increments from 0 x 100 bits/sec to 65535 x 100 bits/sec (6 Mbps).
62 DN9983079 Issue: 11-2

1.6.6 BVC Bucket Size

This information element indicates the maximum bucket size (Bmax) in octets for a BVC.
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Bmax (MSB)
Octet 4 Bmax (LSB)
The Bmax field is the binary encoding of the bucket-size information expressed in 100
octet increments from 0 x 100 octets to 65535 x 100 octets (6 Mbytes).
1.6.7 BVCI
The BVCI information element identifies a BVC. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-4 Unstructured value a)
a) BSS codes:
• Octet 3 = most significant octet of the BVCI
• Octet 4 = least significant octet of the BVCI
1.6.8 BVC Measurement

This information element describes the average queuing delay for a BVC. The element
coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Issue: 11-2 DN9983079 63

8 7 6 5 4 3 2 1
Octet 3,4 Delay value (in centiseconds)
The Delay Value field is coded as a 16-bit integer value in units of centiseconds (one
hundredth of a second). This coding provides a range of over 10 minutes in increments
of 10 msec. As a special case, the hexadecimal value 0xFFFF (decimal 65 535) is
interpreted as infinite delay.
1.6.9 Cause
The Cause information element indicates the reason for an exception condition. The
element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Cause value
Cause value Semantics of coding
Hexadecimal
All values not listed are treated as protocol error - unspecified
x00 Processor overload
x01 Equipment failure
x02 Transit network service failure
x03 Network service transmission capacity modified from zero kbps to
greater than zero kbps
x04 Unknown MS
x05 BVCI unknown
x06 Cell traffic congestion
x07 SGSN congestion
x08 O&M intervention
64 DN9983079 Issue: 11-2

x09 BVCI-blocked
x0a PFC create failure
x0b PFC pre-empted
x0c ABQP no more supported
x20 Semantically incorrect PDU
x21 Invalid mandatory information
x22 Missing mandatory IE
x23 Missing conditional IE
x24 Unexpected conditional IE
x25 Conditional IE error
x26 PDU not compatible with the protocol state
x27 Protocol error - unspecified
x28 PDU not compatible with the feature set
x29 Requested information not available
x2a Unknown Destination address
x2b Unknown RIM Application Identity or RIM application disabled
x2c Invalid Container Unit Information
x2d PFC queuing
x2e PFC created successfully
x2f T12 expiry
x30 MS under PS Handover treatment
x31 Uplink quality
x32 Uplink strength
x33 Downlink quality
x34 Downlink strength
Issue: 11-2 DN9983079 65

x35 Distance
x36 Better cell
x37 Traffic
x38 O&M intervention
x39 MS back on old channel
x3a T13 expiry
x3b T14 expiry
x3c Not all requested PFCs created
x3d CS cause
x3e Requested ciphering and/or integrity protection algorithms not
supported
x3f Relocation failure in target system
x40 Directed Retry
x41 Time critical relocation
x42 PS Handover Target not allowed
x43 PS Handover not Supported in Target BSS or Target System
x44 Incoming relocation not supported due to PUESBINE feature
x45 DTM Handover - No CS resource
x46 DTM Handover - PS Allocation failure
x47 DTM Handover - T24 expiry
x48 DTM Handover - Invalid CS Indication IE
x49 DTM Handover - T23 expiry
x4a DTM Handover - MSC Error
x4b Invalid CSG cell
x80 to x87 Reserved for further definition of non-critical PS handover cause
values
66 DN9983079 Issue: 11-2

1.6.10 Cell Identifier

This information element uniquely identifies one cell. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octets 3-8 Octets 3-8 contain the value part (starting with octet 2) of the
Routing Area Identification IE defined in 3GPP TS 24.008, not
including 3GPP TS 24.008 IEI.
Octets 9-10 Octets 9-10 contain the value part (starting with octet 2) of the Cell
Identity IE defined in 3GPP TS 24.008, not including 3GPP TS
24.008 IEI.
1.6.11 Channel Needed

This information element is coded as defined in 3GPP TS 29.018. It is relevant to circuit-
switched paging requests. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 The rest of the element coded as the value part of the Channel
Needed PDU defined in 3GPP TS 29.018, not including 3GPP TS
29.018 IEI and 3GPP TS 29.018 length indicator.
1.6.12 DRX Parameters

This information element contains MS-specific DRX information. The element coding is
as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Issue: 11-2 DN9983079 67

8 7 6 5 4 3 2 1
Octet 3-n The rest of the element coded as the value part defined in 3GPP
TS 24.008, not including 3GPP TS 24.008 IEI and 3GPP TS
24.008 octet length indicator.
1.6.13 eMLPP Priority

This information element indicates the eMLPP-Priority of a PDU. The element coding is
as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 The rest of the element coded as the value part of the eMLPP-
Priority IE defined in 3GPP TS 48.008, not including 3GPP TS
48.008 IEI and 3GPP TS 48.008 length indicator
1.6.14 Flush Action

The Flush action information element indicates to the SGSN that the BSC has taken in
the response to the flush request. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Action value
Action value semantics of coding
Hexadecimal
x00 LLC-PDU(s) deleted
x01 LLC-PDU(s) transferred
All values not explicitly shown are reserved for future use and
treated by the recipient as an unknown IEI.
68 DN9983079 Issue: 11-2

1.6.15 IMSI
This information element contains the International Mobile Subscriber Identity. The
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-n Octets 3-n contain an IMSI coded as the value part (starting with
octet 3) of the Mobile Identity IE defined in 3GPP TS 24.008, not
including 3GPP TS 24.008 IEI and 3GPP TS 24.008 length
indicator.
1.6.16 LLC PDU

This information element contains an LLC-PDU. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 LLC-PDU (first part)
Octet n LLC-PDU (last part)
1.6.17 LLC Frames Discarded

This information element describes the number of LLC frames that have been discarded
inside a BSC. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Number of frames discarded (in hexadecimal)
Issue: 11-2 DN9983079 69

1.6.18 Location Area

This information element uniquely identifies one Location Area. The element coding is as
follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octets 3-7 Octets 3-7 contain the value part (starting with octet 2) of the
Location Area Identification IE defined in 3GPP TS 24.008, not
The coding of octet 2 is a binary number indicating the length of the remaining element.
1.6.19 Mobile Id
The information element coding of the Mobile Id is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-n Octets 3-n contain IMSI, IMEISV, or IMEI coded as the value part
(starting with octet 3) of the Mobile Identity IE defined in 3GPP TS
24.008, not including 3GPP TS 24.008 IEI and 3GPP TS 24.008
length indicator.
1.6.20 MS Bucket Size

This information element indicates an MS's bucket size (Bmax). The element coding is
as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-4 Bmax
The Bmax field is coded as in section BVC Bucket Size.
70 DN9983079 Issue: 11-2

1.6.21 MS Radio Access Capability

This information element contains the capabilities of the ME. The element coding is as
follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-? Rest of element coded as the value part defined in 3GPP TS
24.008, not including IEI and octet length indicator.
1.6.22 OMC Id
Not used by the BSC.
1.6.23 PDU In Error

The information element coding of the PDU In Error is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-? Erroneous BSSGP PDU
1.6.24 PDU Lifetime

This information element describes the PDU Lifetime for a PDU inside the BSS. The
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-4 Delay Value
Issue: 11-2 DN9983079 71

The Delay Value field is coded as a 16-bit integer value in centi-seconds (one hundredth
of a second). This coding provides a range of over 10 minutes in increments of 10 msec.
As a special case, the hexadecimal value 0xFFFF (decimal 65535) is interpreted as
infinite delay.
1.6.25 PDU Type

The first octet of a BSSGP PDU contains the PDU type IE. The length of the PDU type
IE is one octet. The element coding is as follows:
PDU type coding PDU Types
(Hexadecimal)
x00 DL-UNITDATA
x01 UL-UNITDATA
x02 RA-CAPABILITY
x06 PAGING PS
x07 PAGING CS
x08 RA-CAPABILITY-UPDATE
x09 RA-CAPABILITY-UPDATE-ACK
x0a RADIO-STATUS
x0b SUSPEND
x0c SUSPEND-ACK
x0d SUSPEND-NACK
x0e RESUME
x0f RESUME-ACK
x10 RESUME-NACK
x20 BVC-BLOCK
x21 BVC-BLOCK-ACK
x22 BVC-RESET
x23 BVC-RESET-ACK
72 DN9983079 Issue: 11-2

PDU type coding PDU Types
x24 BVC-UNBLOCK
x25 BVC-UNBLOCK-ACK
x26 FLOW-CONTROL-BVC
x27 FLOW-CONTROL-BVC-ACK
x28 FLOW-CONTROL-MS
x29 FLOW-CONTROL-MS-ACK
x2a FLUSH-LL
x2b FLUSH-LL-ACK
x2c LLC-DISCARDED
x40 SGSN-INVOKE-TRACE
x41 STATUS
0x50 DOWNLOAD-BSS-PFC
0x51 CREATE-BSS-PFC
0x52 CREATE-BSS-PFC-ACK
0x53 CREATE-BSS-PFC-NACK
0x56 DELETE-BSS-PFC
0x57 DELETE-BSS-PFC-ACK
x70 RAN-INFORMATION
x71 RAN-INFORMATION-REQUEST
x72 RAN-INFORMATION-ACK
x73 RAN-INFORMATION-ERROR
x74 RAN-INFORMATION-APPLICATION-ERROR
RESERVED All values not explicitly shown are reserved for future use.
Issue: 11-2 DN9983079 73

1.6.26 Priority
1.6.27 QoS Profile

This information element describes the QoS Profile associated with a PDU. The element
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-4 Peak bit rate provided by the network, coded as the value part in
the Bucket Leak Rate IE. a)
Octet 5 Peak Bit Rate C/R T A Precedence

Granularity
a) The bit rate 0 (zero) means best effort in this IE.
The precedence bit coding is as follows:
Coding Semantic
DL-UNITDATA UL-UNITDATA
000 High priority Radio priority 1
001 Normal priority Radio priority 2
010 Low priority Radio priority 3
011 Reserved Radio priority 4
100 Reserved Radio Priority Unknown
All values which are not allocated are reserved. All reserved values are interpreted as
value 010.
The A bit coding is as follows:
74 DN9983079 Issue: 11-2

Coding Semantic
0 Radio interface uses RLC/MAC ARQ functionality.
1 Radio interface uses RLC/MAC-UNITDATA functionality.
The T bit coding is as follows:
Coding Semantic
0 The PDU contains signalling, for example related to GMM.
1 The PDU contains data.
The C/R bit coding is as follows:
Coding Semantic
0 The PDU contains a LLC ACK or SACK command/response
frame type.
1 The PDU does not contain a LLC ACK or SACK
command/response frame type.
Peak Bit Rate Granularity field is not used. The Peak bit rate granularity is always 100
bits/s
1.6.28 Radio Cause

This information element indicates the reason for an exceptional condition on the radio
interface. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Radio Cause value
Issue: 11-2 DN9983079 75

Radio cause value Semantics of coding
(Hexadecimal)
x00 Radio contact lost with the MS
x01 Radio link quality insufficient to continue communication
x02 Cell-reselection ordered
x03 Cell reselection prepare a)
x04 Cell reselection failure a)
All values not explicitly listed are reserved. If received, they
are handled as radio contact lost with the MS.
a) As the Enhanced Radio Status feature has never been negotiated the Radio Cause
values in range of x03-x04 should if received be handled as “radio contact lost with the
MS”.
1.6.29 RA-Cap-UPD-Cause
The RA-Cap-UPD-Cause indicates the success of the RA-CAPABILITY-UPDATE
procedure or the reason of the failure. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 RA-Cap-UPD-Cause value
RA-Cap-UPD-Cause Semantics of coding

value
(Hexadecimal)
x00 OK, RA capability IE present
x01 TLLI unknown in SGSN
x02 No RA Capabilities or IMSI available for this MS
76 DN9983079 Issue: 11-2

RA-Cap-UPD-Cause Semantics of coding

value
All values not explicitly listed are reserved. If received, they are handled as
TLLI unknown in SGSN.
1.6.30 Routing Area

This information element uniquely identifies one routing area. The element coding is as
follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octets 3-8 Octets 3-8 contain the value part, starting with octet 2, of the
The coding of octet 2 is a binary number indicating the length of the remaining element.
1.6.31 R_default_MS
This information element indicates the default bucket leak rate (R) to be applied to a flow
control bucket for an MS. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-4 R_default_MS value
The R_default_MS field is coded as the R Value in Bucket Leak Rate IE.
1.6.32 Suspend Reference Number

The Suspend Reference Number information element contains an unformatted reference
number for each suspend/resume transaction. The element coding is as follows:
Issue: 11-2 DN9983079 77

8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Suspend Reference Number
The Suspend Reference Number is an unformatted 8-bit field.
1.6.33 Tag
This information element is used to correlate request and response PDUs. The element
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Unstructured value
1.6.34 Temporary Logical Link Identity (TLLI)

The element coding of this information element is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-6 The rest of the element is coded as the value part of the TLLI IE
in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI.
1.6.35 TMSI
The information element coding of TMSI is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
78 DN9983079 Issue: 11-2

8 7 6 5 4 3 2 1
Octet 3-6 The rest of the element is coded as the value part of the TMSI/P-
TMSI IE in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI.
1.6.36 Trace Reference

This information element provides a trace reference number allocated by the triggering
entity. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-4 Trace Reference
1.6.37 Trace Type

This information element provides the type of trace information to be recorded. The
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 This is coded as specified in the Technical Specification 3GPP TS
52.008.
The MSC/BSS Trace Type field consists of the following components:
8 7 6 5 4 3 2 1
Priority For future BSS Record Type MSC Record Type Invoking Event

expansion (Set
Indication
to 0)
The BSS Record Type field is supported by the BSC. The BSC uses record types Basic
and No BSS Trace from the field. Other fields are ignored.
Issue: 11-2 DN9983079 79

Bits Record Type
6 5
0 0 Basic
0 1 Handover
1 0 Radio
1 1 No BSS Trace
1.6.38 Transaction Id
1.6.39 Trigger Id
1.6.40 Number Of Octets Affected

This information element indicates the number of octets transferred or deleted by the
BSC. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-5 number of octets transferred or deleted
The number of octets transferred or deleted by the BSC may be higher than the
maximum Bmax value (6553500). The SGSN handles any value higher than 6553500 as
the Bmax value.
1.6.41 LSA Identifier List

1.6.42 LSA Information

80 DN9983079 Issue: 11-2

1.6.43 Packet Flow Identifier (PFI)

This information element indicates the Packet Flow Identifier for a BSS Packet Flow
Context. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Rest of the element coded as the value part of the Packet Flow
Identifier information element in 3GPP TS 24.008, not including
3GPP TS 24.008 IEI.
1.6.44 Aggregate BSS QoS Profile

This information element indicates the Aggregate BSS QoS Profile (ABQP) for a BSS
Packet Flow Context. The ABQP is considered to be a single parameter with multiple
data transfer attributes as defined in 3GPP TS 23.107. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Rest of element coded as the value part of the QoS information
element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI
and length indicator
1.6.45 Feature Bitmap

The Feature Bitmap information element indicates the optional features supported by the
underlying NSE. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 MBMS Enhan PFC- RIM LCS INR CBL PFC

ced FC
Radio
Status
Issue: 11-2 DN9983079 81

PFC coding:
Coding Semantic
0 Packet Flow Context Procedures not supported
1 Packet Flow Context Procedures supported
CBL coding:
Coding Semantic
0 Current Bucket Level Procedures not supported
1 Current Bucket Level Procedures supported
CBL procedures are not supported.
INR coding:
Coding Semantic
0 Inter-NSE re-routing not supported
1 Inter-NSE re-routing supported
INR is not supported.
LCS coding:
Coding Semantic
0 LCS Procedures not supported
1 LCS Procedures supported
LCS procedures are not supported.
RIM coding:
Coding Semantic
0 RAN Information Management (RIM) procedures not
supported.
1 RAN Information Management (RIM) procedures supported
82 DN9983079 Issue: 11-2

PCU2 sends always the Feature Bitmap -Information Element with the RIM bit value 1 -
RAN Information Management (RIM) procedures supported. PCU1 does not support RIM
procedures.
PFC-FC coding:
Coding Semantic
0 PFC Flow Control Procedures not supported.
1 PFC Flow Control Procedures supported.
PFC Flow Control Procedures are not supported.
Enhanced Radio Status coding:
Coding Semantic
0 Enhanced Radio Status Procedures not supported.
1 Enhanced Radio Status Procedures supported.
Enhanced Radio Status Procedures are not supported.
MBMS coding:
Coding Semantic
0 MBMS Procedures not supported
1 MBMS Procedures supported
MBMS Procedures are not supported.
1.6.46 Bucket Full Ratio

1.6.47 Service UTRAN CCO

The Service UTRAN CCO (Cell Change Order) information element indicates whether
network-initiated cell change to UTRAN or E-UTRAN should be used. It is relevant if any
of such procedures (e.g. IS-NCCR) are used. The element coding is as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Issue: 11-2 DN9983079 83

8 7 6 5 4 3 2 1
Octet 3 Spare Service E- Service UTRAN CCO

UTRAN CCO Value part
Value part
Service UTRAN Value Semantics of coding

part
000 Network initiated cell change order procedure to UTRAN should be performed
001 Network initiated cell change order procedure to UTRAN should not be performed
010 Network initiated cell change order procedure to UTRAN is not performed
111 If received, shall be interpreted as no information available and bits 4-5 valid instead a)
other values No information available
a) Service E-UTRAN CCO Value part is not used and ‘111’ as Service UTRAN CCO
value is treated as any other non-defined value.
1.6.48 NSEI
1.6.49 RIM Application Identity

Identifies the application using RIM procedures. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 RIM Application Identity
RIM Application Identity coding:
Coding Semantic
0000 0000 Reserved
84 DN9983079 Issue: 11-2

Coding Semantic
0000 0001 Network Assisted Cell Change (NACC)
0000 0010 System Information 3 (SI3)
0000 0011 MBMS data channel
0000 0100 SON Transfer
0000 0101 UTRA System Information (UTRA SI)
0000 0110 - 1111 1111 Reserved
Only Network Assisted Cell Change (NACC) is supported.
1.6.50 RIM Sequence Number

This information element defines the sequence number (RSN) allocated to a RIM PDU
by the source node. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 RIM Sequence Number (Higher order octet)
Octet 4 RIM Sequence Number
Octet 5 RIM Sequence Number
Octet 6 RIM Sequence Number (Lower order octet)
1.6.51 RAN-INFORMATION-REQUEST Application Container

The coding of the Application Container IE within the RAN-INFORMATION-REQUEST
RIM container for the NACC application is specified as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Issue: 11-2 DN9983079 85

8 7 6 5 4 3 2 1
Octet 3-10 Reporting Cell Identifier
Reporting Cell Identifier IE is encoded as the Cell Identifier.
1.6.52 RAN-INFORMATION Application Container

The coding of the Application Container IE within the RAN-INFORMATION RIM
container for the NACC application is specified as follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-10 Reporting Cell Identifier
Octet 11 Number of SI/PSI Type
Octet 12-n SI/PSI
Reporting Cell Identifier IE is encoded as the Cell Identifier.
Type indicates the type of SI/PSI messages provided by the reporting cell. The Type field
is coded as shown below:
Coding Semantic
0 SI messages as specified for BCCH (3GPP TS 44.018)
follow
1 PSI messages as specified for PBCCH (3GPP TS 44.060)
follow
Number of SI/PSI indicates the number of SI/PSI provided by the reporting cell contained
in the SI/PSI field. This number may be zero. For system information messages with
multiple instances, each instance is counted as one SI/PSI message. The Number of
SI/PSI field is coded as shown below:
Coding Semantic
000 0000 0 "SI/PSI" follows
86 DN9983079 Issue: 11-2

Coding Semantic
000 0001 1 "SI/PSI" follow
‘ “
111 1111 127 "SI/PSI" follow
SI/PSI field contains a list of either system information or packet system information
messages valid for the reporting cell. Furthermore:
• If the Type field indicates that "SI messages as specified for BCCH (3GPP TS
44.018) follow" then the SI/PSI field contains System Information message instances
encoded for BCCH as specified in 3GPP TS 44.018. Each System Information
message contains the Message type octet followed by all the IEs composing the
message payload. Each message is 21 octets long.
• If the Type field indicates that “PSI messages as specified for PBCCH (3GPP TS
44.060) follow” then the SI/PSI field contains Packet System Information message
instances encoded for PBCCH as specified in 3GPP TS 44.060. Each Packet
System Information message contains the MESSAGE_TYPE field followed by the
PSI message content. Each message is 22 octets long.
RAN-INFORMATION Application Container for the NACC Application included in the
RAN-INFORMATION/End PDU or in the RAN-INFORMATION/Stop PDU contains only
the Reporting Cell Identifier. The BSC codes the PDUs in such a way that the Length
Indicator indicates that the Reporting Cell Identifier is the last information in the IE.
However, for compatibility reasons the BSC accepts (successfully encode) also longer
IEs but just ignore rest of the information.
1.6.53 RIM PDU Indicators

This IE contains different indications used in RAN-INFORMATION-REQUEST PDU,
RAN-INFORMATION PDU or RAN-INFORMATION-APPLICATION-ERROR PDU. The
element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Reserved PDU Type Extension ACK
ACK field indicates whether the source side is requesting a RAN-INFORMATION-ACK
PDU as response to a RAN-INFORMATION or to a RAN-INFORMATION-
APPLICATION-ERROR PDU. The ACK field is not used in RAN-INFORMATION-
REQUEST PDU and shall be considered as spare. This field is coded as shown below.
Issue: 11-2 DN9983079 87

Coding Semantic
0 No ACK requested
1 ACK requested
The BSC never requests acknowledge message for RAN-INFORMATION PDU except
for RAN-INFORMATION/End PDU, but is able to send one if so requested by the (other
vendor’s) serving BSC.
PDU Type Extension field specifies the type extension of the PDU. The defined values
depend on the PDU type.
Coding of the PDU Type Extension parameter when used in RAN-INFORMATION-
REQUEST PDU:
Coding Semantic
000 RAN-INFORMATION-REQUEST/Stop PDU
001 RAN-INFORMATION-REQUEST/Single Report PDU
010 RAN-INFORMATION-REQUEST/Multiple Report PDU
011-111 Reserved
Coding of the PDU Type Extension parameter when used in RAN-INFORMATION PDU:
Coding Semantic
000 RAN-INFORMATION/Stop PDU
001 RAN-INFORMATION/Single Report PDU
010 RAN-INFORMATION/Initial Multiple Report PDU
011 RAN-INFORMATION/Multiple Report PDU
100 RAN-INFORMATION/End PDU
101-111 Reserved
Parameter is not relevant when used in RAN-INFORMATION-APPLICATION-ERROR
PDU.
88 DN9983079 Issue: 11-2

1.6.54 Global CN-Id

The Global CN-Id consists of a PLMN-Id and a CN-Id, see 3GPP TS 23.003. The value
part of the Global CN-Id is coded as defined in 3GPP TS 29.018. The CN-Id is an integer
defined by O&M. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-7 Coded as octets 3 to 7 of the Global CN-Id IE, defined in 3GPP
TS 29.018
1.6.55 RIM Routing Information

This information element uniquely identifies either a cell within a GERAN BSS, a UTRAN
RNC or an E-UTRAN eNodeB. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Spare RIM Routing Address

discriminator
Octet 4-n RIM Routing Address
The coding of RIM Routing Address discriminator is a binary number indicating which
type of address is provided in octet 4-n. The RIM Routing Address discriminator is coded
as follows:
Bits4321
0000 A Cell Identifier is used to identify a GERAN cell.
0001 A RNC Identifier is used to identify a Utran RNC.
0010 An eNB identifier is used to identify an E-UTRAN eNodeB or
HeNB
Other Reserved
Issue: 11-2 DN9983079 89

RIM Routing address coding depends on RIM Routing Address discriminator:
RIM Routing Address discriminator = 0000:
The RIM Routing Address field contains a Cell Identifier and is coded as the value part
(octet 3 to octet 10) of the Cell Identifier Information element.
The RIM Routing Address field contains a RNC identifier and it is coded as follows:
8 7 6 5 4 3 2 1
Octets 4 to 9 contain the value part (starting with octet 2) of the Octet 4-9
including 3GPP TS 24.008 IEI
RNC-ID (or Extended RNC-ID) Octet 10
RNC-ID (or Extended RNC-ID) (continued) Octet 11
The octets 10-11 contain the RNC-ID (0..4095) or the Extended RNC-ID (4096..65535) -
see 3GPP TS 25.413:
• The least significant bit of RNC-ID is octet 11 bit 1 and most significant bit is octet 10
bit 4. In the octet 10 bits 5-8 are set to “0000”.
• The least significant bit of Extended RNC-ID is octet 11 bit 1 and most significant bit
is octet 10 bit 8.
The RIM Routing Address field contains an eNB identifier and is coded as follows:
8 7 6 5 4 3 2 1
Octets 4 to 8 contain the value part (starting with octet 2) of the Octet 4-8
Tracking Area Identity IE defined in 3GPP TS 24.301, not
including 3GPP TS 24.301 IEI
Global eNB ID Octet 9-n
Octets 9-n contain the Global eNB ID (see 3GPP TS 36.413) of the eNodeB.
1.6.56 RIM Protocol Version Number

This information element defines which version number of the RIM protocol is in use in
the PDU. The element coding is:
90 DN9983079 Issue: 11-2

8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 RIM Protocol Version Number
RIM Protocol Version Number is coded as follows:
Coding Semantic
0000 0000 Reserved
0000 0001 Version 1
0000 0010-1111 1111 Reserved
If this Information Element is omitted the value “Version 1" should be assumed.
1.6.57 Application Error Container

The coding of the Application Error Container IE for the NACC application is specified as
follows:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 NACC Cause
Octet 4-n Erroneous Application Container including IEI and LI
NACC Cause field indicates the cause why the Application Error Container IE is sent.
The NACC Cause field is coded as shown below:
Coding Semantic
0000 0000 Other unspecified error
0000 0001 Syntax error in the Application Container
Issue: 11-2 DN9983079 91

Coding Semantic
0000 0010 Reporting Cell Identifier does not match with the Destination
Cell Identifier or with the Source Cell Identifier.
0000 0011 SI/PSI type error
0000 0100 Inconsistent length of a SI/PSI message
0000 0101 Inconsistent set of messages
Other values Reserved
Explanation of the codes:
• “Other unspecified error”: none of the error description below fits with the detected
error
• “Syntax error in the Application Container”: the Application Container IE is
syntactically incorrect
• “Reporting Cell Identifier does not match with the Destination Cell Identifier or with
the Source Cell Identifier”: the Reporting Cell Identifier in the Application Container
IE does not match with the Destination Cell Identifier IE value (in the case of a RAN-
INFORMATION-REQUEST PDU) or with the Source Cell Identifier IE value (in the
case of a RAN-INFORMATION PDU) of the RIM PDU
• “SI/PSI type error”: the Application Container IE contains system information
messages instead of packet system information messages or conversely
• “Inconsistent length of a SI/PSI message": the length contained in one SI/PSI
message does not fit with the content of the message
• "Inconsistent set of messages": the status of the change marks reported in the
(packet) system information message set is inconsistent
Erroneous Application Container contains the received erroneous Application container
IE.
1.6.58 RAN-INFORMATION-REQUEST RIM container

This information element defines the RIM container used in the RAN-INFORMATION-
REQUEST PDU. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-? RAN-INFORMATION-REQUEST RIM Container Contents
RAN-INFORMATION-REQUEST RIM Container Contents coding is:
92 DN9983079 Issue: 11-2

Information Elements Type Presence Format Length
RIM Application RIM Application Identity M TLV 3

Identity
RIM Sequence RIM Sequence Number M TLV 6

Number
RIM PDU Indications RIM PDU Indications M TLV 3
RIM Protocol Version RIM Protocol Version O TLV 3

Number a) Number
Application Container RAN-INFORMATION- C TLV 4-?

b) REQUEST Application
Containere
SON Transfer SON Transfer C TLV 3-?

Application Identity a) Application Identity
a) Not used.
b) The presence of the Application Container depends on the value of the RIM
Application Identity IE. Is always present for Network Assisted Cell Change (NACC)
application.
1.6.59 RAN-INFORMATION RIM container

This information element defines the RIM container used in the RAN-INFORMATION
PDU. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-? RAN-INFORMATION RIM Container Contents
RAN-INFORMATION RIM Container Contents coding is:

Identity
Issue: 11-2 DN9983079 93


Number

Number a) Number
Application Container RAN-INFORMATION- C TLV 4-?

b) REQUEST Application
Containere
Application Error Application Error C TLV n

Container c) Container

a) Not used.
b) Used if RIM Application Identity indicates the Network Assisted Cell Change (NACC)
application and no Application Error Container included.
c) Used if RIM Application Identity indicates the Network Assisted Cell Change (NACC)
application and no Application Container included.
1.6.60 RAN-INFORMATION-APPLICATION-ERROR RIM Container

APPLICATION-ERROR PDU. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-? RAN-INFORMATION-APPLICATION-ERROR RIM Container
Contents
RAN-INFORMATION-APPLICATION-ERROR RIM Container Contents coding is:
94 DN9983079 Issue: 11-2


Identity

Number

Number a) Number
Application Error Application Error M TLV n

Container Container

a) Not used.
1.6.61 RAN-INFORMATION-ACK-RIM container

ACK PDU. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-16 RAN-INFORMATION-ACK RIM Container Contents
RAN-INFORMATION-ACK RIM Container Contents coding is:

Identity

Number

Number a) Number
Issue: 11-2 DN9983079 95


a) Not used.
1.6.62 RAN-INFORMATION-ERROR RIM Container

ERROR PDU. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3-? RAN-INFORMATION-ERROR RIM Container Contents
RAN-INFORMATION-ERROR RIM Container Contents coding is:

Identity
RIM Cause a) Cause M TLV 3

Number b) Number
PDU in Error c) PDU in Error M TLV 3-?

Application Identity b) Application Identity
a) Values filled by the BSC:
• Unknown RIM application identity or RIM application disabled
• PDU not compatible with the feature set
• Missing conditional IE
• Missing mandatory IE
• Conditional IE error
• Invalid mandatory information
96 DN9983079 Issue: 11-2

• Semantically incorrect PDU
b) Not used.
c) Contains the erroneous PDU.
1.6.63 Extended Feature Bitmap

The Extended Feature Bitmap information element indicates the optional features
supported by the underlying NSE. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Spare Spare Spare Spare Spare MOCN Gigabit PS Handover

Interface
PS Handover coding:
Coding Semantic
0 Ps Handover not supported
1 PS Handover supported
PS Handover is not supported.
Gigabit Interface coding:
Coding Semantic
0 Gigabit Interface not supported
1 Gigabit Interface supported
Gigabit Interface is not supported.
Multi Operator Core Network coding:
Coding Semantic
0 Multi Operator Core Network not supported
1 Multi Operator Core Network supported
Issue: 11-2 DN9983079 97

1.6.64 Flow Control Granularity

1.6.65 SON Transfer Application Identity

1.6.66 Subscriber Profile ID for RAT/Frequency priority

1.6.67 Redirect Attempt Flag

This information element provides control information for the MOCN rerouting procedure.
It indicates that the CN shall include in the answer either Redirection Indication IE or
Redirection Completed IE.
The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Spare
1.6.68 Redirection Indication

It indicates that the CN requests rerouting by the BSS to another CN operator. The
Reroute Reject cause is given.
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Reroute Reject Cause value
Coding Semantic
0000 1011 PLMN not allowed (meaning is defined in 3GPP TS 24.008)
98 DN9983079 Issue: 11-2

Coding Semantic
0000 1100 location area not allowed (meaning is defined in 3GPP TS
24.008)
0000 1101 roaming not allowed in this location area (meaning is
defined in 3GPP TS 24.008)
0000 1110 GPRS services not allowed in this PLMN (meaning is
defined in 3GPP TS 24.008)
0000 1111 no suitable cell in location area (meaning is defined in 3GPP
TS 24.008)
0001 0000 CS/PS domain registration coordination (meaning is defined
in 3GPP TS 23.251)
0001 0001 Reserved a)
a) Even not yet standardized in TS48.018, SGSN can send the following cause value to
BSC with Redirection indication: 0001 0001 Network Failure PCU receives and
recognizes this cause value and triggers redirection procedure as with the other defined
reject cause values, when this cause value is received from SGSN.
1.6.69 Redirection Completed

It indicates that the reroute procedure is completed.The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Outcome value
Coding Semantic
0000 0001 MS is accepted
0000 0010 MS is not accepted
0000 0011 MS is already registered
Issue: 11-2 DN9983079 99

Coding Semantic
1.6.70 Unconfirmed send state variable

This IE indicates the value of the Unconfirmed send state variable.The element coding
is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 3 Spare V(U)

MSB
Ocet 4 V(U)
Octet 2 and bit 1 of octet 3 contain a number in binary representation ranging from 0 to
511. The least significant bit is bit 1 of octet 3, and the most significant bit is bit 1 of octet
2.
1.6.71 Service Class Indicator

If the Core Network is configured to tag DL PDUs that belong to a certain signaling type
of application, like Tencent QQ, then SGSN may transmit a BSSGP DL-UNITDATA PDU
to PCU with a proprietary Service Class Indicator. If the Instant QoS Signaling feature is
enabled in BSC, then PCU takes into account the proprietary Service Class Indicator and
allocates only 1 TSL for a DL TBF if the DL LLC PDUs to be transferred are received
with this tag.
• If the proprietary Service Class Indicator field value is 0x11, then PCU treats this as a
tag for the Instant QoS Signaling application.
• If the proprietary Service Class Indicator field value is other than 0x11, then PCU
ignores the field value.
8 7 6 5 4 3 2 1
Octet 1 IEI
100 DN9983079 Issue: 11-2

8 7 6 5 4 3 2 1
Octet 3 Service Class Indicator
1.7 List of system variables

Table 2 BSSGP timers
Timer name Value Notes Relation to other timers

range/default
TgbBlock (T1) 1 - 30s/3s Guards the (un)blocking None

procedures
TgbReset (T2) 1 - 120s/3s Guards the reset procedure None
TgbSuspend (T3) 0.1 - 10s/3s Guards the suspend None

procedure
TgbFlow (Flow 1s BSSGP flow control None

control variable C) supervision timer
TgbResume (T4) 0 - 10s/0.2s Guards the resume None

procedure
T5 1 - 30s/3s Guards the RA-CAPABILITY- None

UPDATE procedure
T6 0.1 – 10s/3s Guards the DOWNLOAD- None

BSS-PFC procedure
Table 3 BSSGP parameters
Counter name Value Notes Relation to other

range/default parameters
BVCBlockRetries (BVC- 1 - 100/3 None None

BLOCK-RETRIES)
BVCUnblockRetries 1 - 100/3 None None

(BVC-UNBLOCK-
RETRIES)
BVCResetRetries (BVC- 1 - 100/3 None None

RESET-RETRIES)
SuspendRetries 1 - 100/3 None None

(SUSPEND-RETRIES)
Issue: 11-2 DN9983079 101

Table 3 BSSGP parameters (Cont.)
Counter name Value Notes Relation to other

range/default parameters
RESUME-RETRIES 1 - 100/1 None None
RA-CAPABILITY- 1 - 100/3 None None

UPDATE-RETRIES
DOWNLOAD-BSS-PFC- 1 - 100/3 None None

RETRIES
102 DN9983079 Issue: 11-2

Язык

Добро пожаловать в Scribd!

Bsc Sgsn Interface Specification Bss Gprs Protocol

Загружено:

Сведения о документе

Описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Описание:

Авторское право:

Доступные форматы

Bsc Sgsn Interface Specification Bss Gprs Protocol

Загружено:

Описание:

Авторское право:

Доступные форматы

Похожие издания

Nokia Networks

GSM/EDGE BSS, Rel. GSM 16,

f Important Notice on Product Safety

Downlink Unitdata (1.3.1)

Uplink Unitdata (1.3.2)

BVC Reset (1.3.12)

IEI codings (1.6.1)

PDU Type (1.6.25)

Redirect Attempt Flag (1.6.67)

Redirection Indication (1.6.68)

Redirection Completed (1.6.69)

Unconfirmed send state variable (1.6.70)

Delete BSS PFC (1.3.16)

Aggregate BSS QoS Profile (1.6.43)

List of system variables (1.7)

1 BSC-SGSN Interface Specification BSS GPRS

1.1 Position of BSSGP within the protocol stack on the

1.2 Primitive parameters

1.2.2 Link Selector Parameter (LSP)

1.2.3 Network Service Entity Identifier (NSEI)

1.3 BSSGP procedures

1.3.1 Downlink Unitdata

1.3.2 Uplink Unitdata

1.3.5 Radio Access Capability Update

1.3.6 Radio Status

1.3.10 Flow Control

1.3.11 BVC Blocking and Unblocking

1.3.12 BVC Reset

1.3.14 Create BSS PFC

1.3.15 Delete BSS PFC

1.3.16 RIM procedures

1.3.16.1 RAN Information Request procedure

RAN Information Request / Single Report procedure

RAN Information Request / Multiple Report procedure

RAN Information Request / Stop procedure

1.3.16.2 RAN Information Send procedure

1.3.16.3 RAN Information Application Error procedure

1.3.16.4 RAN Information Error procedure

1.3.16.5 Abnormal conditions

1.4 General protocol error handling

1.5 BSSGP protocol data units (PDUs)

Information element Type / Reference Presence Format Length

PDU Lifetime PDU Lifetime M TLV 4

MS Radio Access MS Radio Access Capability O TLV 7-?

Priority b) Priority O TLV 3

DRX Parameters DRX Parameters O TLV 4

IMSI IMSI O TLV 5-10

TLLI (old) TLLI O TLV 6

PFI PFI O TLV 3

LSA Information b) LSA Information O TLV 7-?

Service UTRAN CCO Service UTRAN CCO O TLV 3

Subscriber Profile ID for Subscriber Profile ID for O TLV 3

Redirection Indication Redirection Indication O TLV 3

Redirection Completed IMSI O TLV 3

Unconfirmed send state Unconfirmed send state variable O TLV 4

Service Class Indicatorc) Service Class Indicator O TLV 3

Alignment octets Alignment octets O TLV 2–5

LLC-PDU d) LLC-PDU M TLV 2-?