You are on page 1of 73

BSC-SGSN Interface Specification

BSS GPRS Protocol (BSSGP)


dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
1 (73)
2003330
Nokia BSC S10.5 ED, Vers. 2, Product
Documentation
The information in this documentation is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia's customers only for the purposes of the agreement under which the documentation
is submitted, and no part of it may be reproduced or transmitted in any form or means without the
prior written permission of Nokia. The documentation has been prepared to be used by
professional and properly trained personnel, and the customer assumes full responsibility when
using it. Nokia welcomes customer comments as part of the process of continuous development
and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products cannot be considered binding but
shall be defined in the agreement made between Nokia and the customer. However, Nokia has
made all reasonable efforts to ensure that the instructions contained in the documentation are
adequate and free of material errors and omissions. Nokia will, if necessary, explain issues
which may not be covered by the documentation.
Nokia's liability for any errors in the documentation is limited to the documentary correction of
errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL
(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or the
information in it.
This documentation and the product it describes are considered protected by copyright
according to the applicable laws.
NOKIA logo is a registered trademark of Nokia Corporation.
Other product names mentioned in this documentation may be trademarks of their respective
companies, and they are mentioned for identification purposes only.
Copyright Nokia Corporation 2003. All rights reserved.
2 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
Contents
Contents 3
List of tables 6
List of figures 7
Summary of changes 9
1 BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
description 11
1.1 Position of BSSGP within the protocol stack on the Gb-interface 11
1.2 Primitive parameters 12
1.2.1 BSSGP Virtual Connection Identifier (BVCI) 12
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 18
1.3.4 Paging 18
1.3.5 Radio Access Capability Update 19
1.3.6 Radio Status 20
1.3.7 Suspend 21
1.3.8 Resume 22
1.3.9 Flush-LL 22
1.3.10 Flow Control 23
1.3.11 BVC Blocking and Unblocking 25
1.3.12 BVC Reset 27
1.3.13 Trace 29
1.4 General Protocol Error Handling 30
1.5 BSSGP Protocol Data Units (PDUs) 30
1.5.1 DL-UNITDATA 31
1.5.2 UL-UNITDATA 32
1.5.3 RA-CAPABILITY 33
1.5.4 PTM-UNITDATA 33
1.5.5 PAGING-PS 33
1.5.6 PAGING-CS 34
1.5.7 RA-CAPABILITY-UPDATE 35
1.5.8 RA-CAPABILITY-UPDATE-ACK 36
1.5.9 RADIO STATUS 36
1.5.10 SUSPEND 36
1.5.11 SUSPEND-ACK 37
1.5.12 SUSPEND-NACK 38
1.5.13 RESUME 38
1.5.14 RESUME-ACK 38
1.5.15 RESUME-NACK 39
1.5.16 FLUSH-LL 39
1.5.17 FLUSH-LL-ACK 39
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
3 (73)
Contents
1.5.18 LLC-DISCARDED 40
1.5.19 FLOW-CONTROL-BVC 41
1.5.20 FLOW-CONTROL-BVC-ACK 41
1.5.21 FLOW-CONTROL-MS 42
1.5.22 FLOW-CONTROL-MS-ACK 43
1.5.23 BVC-BLOCK 43
1.5.24 BVC-BLOCK-ACK 44
1.5.25 BVC-UNBLOCK 44
1.5.26 BVC-UNBLOCK-ACK 45
1.5.27 BVC-RESET 45
1.5.28 BVC-RESET-ACK 46
1.5.29 STATUS 47
1.5.30 SGSN-INVOKE-TRACE 48
1.6 BSSGP Information Elements (IEs) 48
1.6.1 IEI Codings 49
1.6.2 Alignment Octets 51
1.6.3 Bmax Default MS 51
1.6.4 BSS Area Indication 52
1.6.5 Bucket Leak Rate 52
1.6.6 BVC Bucket Size 53
1.6.7 BVCI 53
1.6.8 BVC Measurement 54
1.6.9 Cause 54
1.6.10 Cell Identifier 55
1.6.11 Channel Needed 56
1.6.12 DRX Parameters 56
1.6.13 eMLPP Priority 57
1.6.14 Feature Bitmap 57
1.6.15 Flush Action 58
1.6.16 IMSI 59
1.6.17 LLC PDU 59
1.6.18 LLC Frames Discarded 59
1.6.19 Location Area 60
1.6.20 Mobile Id 60
1.6.21 MS Bucket Size 61
1.6.22 MS Radio Access Capability 61
1.6.23 OMC Id 62
1.6.24 PDU In Error 62
1.6.25 PDU Lifetime 62
1.6.26 PDU Type 63
1.6.27 Priority 65
1.6.28 QoS Profile 65
1.6.29 Radio Cause 66
1.6.30 RA-Cap-Upd-Cause 67
1.6.31 Routing Area 67
1.6.32 R Default MS 68
1.6.33 Suspend Reference Number 68
1.6.34 Tag 69
1.6.35 Temporary Logical Link Identity (TLLI) 69
1.6.36 TMSI 69
1.6.37 Trace Reference 70
4 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
1.6.38 Trace Type 70
1.6.39 TransactionId 71
1.6.40 Trigger Id 71
1.6.41 Number Of Octets Affected 71
1.6.42 LSA Identifier List 72
1.6.43 LSA Information 72
1.7 List of system variables 72
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
5 (73)
Contents
List of tables
Table 1. BSSGP PDU, BVCI, and functional entity mapping 13
Table 2. BSSGP timers 72
Table 3. BSSGP parameters 73
6 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
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 18
Figure 5. Paging 18
Figure 6. Radio Status 20
Figure 7. Suspend 21
Figure 8. Flush LL 22
Figure 9. BVC blo 23
Figure 10. BVC blocking and unblocking 25
Figure 11. BVC reset 27
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
7 (73)
List of figures
8 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes made between issues 4 and 3
All information related to Gb over IP-feature has been removed.
Chapter Uplink unit data
Reference to precedence corrected: precedence contains Radio Priority class
received from MS.
Chapter BSSGP Information Elements (IEs) , section Feature Bitmap
The semantics in Table "CBL bit" coding have been corrected.
Changes made between issues 3a and 3
Note! 3a-0 and 3-0 are not real parallel issues since there has been content
changes between them: The version number of the standard 08.18 has been
changed from 8.8.0 to 8.9.0.
Changes made between issues 3 and 2
The version number of the standard 08.18 has been changed from 8.8.0 to 8.9.0.
Grammar corrections made. Nommification changes: links to the overview
added.
A new CR: the support for Zero Length Unitdata, GP-000561 added.
1. 3.1. Resource Distribution function is supported
2. 5.29 BVCI is included into STATUS-PDU also when BVCI was unknown.
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
9 (73)
Summary of changes
10 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
1 BSC-SGSN Interface Specification BSS
GPRS Protocol (BSSGP) description
This interface description deals with the GSM Recommendation GSM 08.18,
BSS-SGSN Interface, BSS GPRS Protocol, version 8.9.0. It describes the BSS
GPRS Protocol (BSSGP) implementation for control of GSM packet data
services in the BSC SW release S10.5 and defines what is supported in the BSC-
SGSN interface from the BSC point of view.
As a general rule, the GSM Recommendation is implemented. Generally all
primitives and parameters received without a protocol error have to be processed
as defined in GSM 08.18, BSS-SGSN Interface, BSS GPRS Protocol, version
8.9.0. Any exceptions to this general rule are mentioned in this document.
Explanations of the remarks in this interface document:
not supported Feature is not implemented
not used Primitive or parameter is not implemented
compliant, supported or no remark
Feature 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 in two: Sub-network Service and Network Service Control. The Sub-
network Service is Frame Relay.
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
11 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
Figure 1. The protocol stack on the Gb-interface
Network Service Control is responsible for virtual circuit management and GPRS
specific addressing, which maps cells to virtual connections.
BSSGP is a layer 3 protocol for delivering data packets and associated control
information. BSSGP also includes procedures for for example downlink flow
control, paging, and virtual circuit management.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.2 Primitive parameters
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.2.1 BSSGP Virtual Connection Identifier (BVCI)
BVCs are communication paths between peer BSSGPs. Each BVC is supported
by one NSE. Each BVC is identified by means of a BVCI which has end-to-end
significance across the Gb interface. Each BVC is unique between two peer
Network Service entities.
Within the BSS a cell is identified uniquely by a BVCI.
The BVCI value 0000 hex is used for signalling and the value 0001 hex is
reserved for PTM. All other values are used for cell identifiers.
LLC
BSSGP
NS
L1
SGSN
NS MAC
L1
BSS
RELAY
RLC
BSSGP
Gb
12 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
Table 1. BSSGP PDU, BVCI, and functional entity mapping
BSSGP PDUs Mapping of BVCI to 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-
UPDATE-ACK
PTP
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-
ACK
PTP
FLOW-CONTROL-MS / FLOW-CONTROL-MS-
ACK
PTP
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
NOTE 1: SGSN may initiate paging of an MS in READY mobility management
state at an indication of a lower layer failure. In this case, the BVCI = PTP may be
used.
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
13 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
NOTE 2: If the SGSN initiates circuit-switched paging of an MS in READY
mobility management state, the BVCI = PTP. If the MS is in STANDBY state, the
BVCI = SIGNALLING.
NOTE 3: The setting of the BVCI is dependent on the context within which the
STATUS PDU was generated.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.2.2 Link Selector Parameter (LSP)
All BSSGP UNITDATA PDUs related to an MS are passed to 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.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.2.3 Network Service Entity Identifier (NSEI)
NSE identifies a group of NS-VCs in the BSC. The NSEI is used by the BSC to
determine the NS-VCs which provide service to a BVC. At the BSSGP level the
NSEI has only local significance at each end of the Gb interface.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.3 BSSGP procedures
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
14 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
1.3.1 Downlink Unitdata
Figure 2. DL Unitdata
When initiating a downlink datapacket transmission from an SGSN to an MS, the
SGSN 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 is to be 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 which is used to locate the existing context of an MS. Subsequent
uplink data transfers for this MS reference the current TLLI and not the old TLLI.
If SGSN has a valid IMSI for the TLLI, the SGSN includes it in the PDU. Also if
the SGSN has a valid DRX Parameters for the TLLI, the SGSN includes it 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.
MS Radio Access Capability (MS RAC) defines the radio capabilities of the ME.
It is provided if available in SGSN.
QoS Profile defines the (peak) bit rate, the type of BSSGP SDU (signalling or
data), the type of LLC, the precedence class, and the transmission mode to be
used when transmitting the LLC-PDU across the radio interface.
Only Best Effort coding within bit rate coding is supported. If other bit rate
codings are used, the Best Effort service is provided.
Precedence is used for prioritizing downlink LLC-PDUs.
BSC SGSN
BSSGP
DL-UNITDATA
BSSGP
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
15 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
Two transmission modes across the radio interface are possible: acknowledged
(using RLC/MAC ARQ functionality) and unacknowledged (using RLC/MAC
unitdata functionality) transmission modes.
Two types of BSSGP SDUs are distinguished through the QoS Profile: layer 3
signalling and data BSSGP SDUs. Not used by the BSC.
The type of LLC indicates whether the SDU contains a LLC ACK or SACK
command/response frame type or not. Not used by the BSC.
PDU Lifetime defines the remaining time period in which the PDU is considered
valid within the BSS. If the PDU is held for a period exceeding the "PDU
Lifetime", the PDU is locally discarded by the BSC.
Priority is not used and it is ignored when received by the BSC.
LSA Information is not used and it is ignored when received by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.3.2 Uplink Unitdata
Figure 3. UL Unitdata
When initiating an uplink datapacket transmission from an MS to an SGSN, the
BSC 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.
BSC SGSN
BSSGP
UL-UNITDATA
BSSGP
16 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
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.
QoS indicates the QoS profile used in the LLC-PDU's transmission from the MS
across the radio interface.
QoS Profile defines the (peak) bit rate, the type of BSSGP SDU (signalling or
data), the type of LLC, the precedence class, and the transmission mode to be
used when transmitting the LLC-PDU across the radio interface.
The peak bit rate is always set as Best Effort. Precedence contains Radio Priority
class received from MS in PACKET CHANNEL REQUEST message.
Two transmission modes across the radio interface are possible; acknowledged
(using RLC/MAC ARQ functionality) and unacknowledged (using RLC/MAC
unitdata functionality) transmission modes.
The type of the BSSGP SDU, layer 3 signalling or data, and the type of LLC
frame, SACK, ACK, or not, are not meaningful on the uplink and are ignored by
the SGSN.
The BSC includes also the cell identifier of the cell upon which the LLC-PDU
was received.
LSA Identifier List is not included by the BSC.
Nokia BSS does not sent BSSGP DL-UNITDATA PDU with LLC-PDU Length
Indicator set to 0.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
17 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
1.3.3 RA-Capability
Figure 4. RA Capability
The SGSN stores the current radio access capability of an MS (which 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 new information.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.3.4 Paging
Figure 5. Paging
BSC SGSN
BSSGP
RA-CAPABILITY
BSSGP
BSC SGSN
BSSGP
PAGING-PS
BSSGP
PAGING-CS
or
18 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
When the SGSN initiates paging procedure for GPRS services, it sends one or
more PAGING PS PDUs to the BSC. When instructed by an MSC/VLR to
initiate 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 approriate time.
The SGSN indicates the MS's IMSI and DRX Parameters (optional in PAGING
PS), which enables the BSC to derive the paging population number, and also
QoS in case of ps-paging.
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 on the
BSS within one location area, all cells on the BSS within one routing area, and
one BVCI, that is 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 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 includes also optionally one or both of the following
parameters: Channel Needed and eMLPP-Priority. The Channel Needed and
eMLPP-Priority information is handled transparently by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.3.5 Radio Access Capability Update
Not supported by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
19 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
1.3.6 Radio Status
Figure 6. Radio Status
BSS and MS radio interface communication may not be successfully completed
as requested if the MS goes out of coverage and is lost. This condition is signalled
by setting the Radio Cause value to "radio contact lost with MS".
Attempts to communicate between an MS and an SGSN via this cell should be
suspended or abandoned. The SGSN should stop sending LLC-PDUs to the cell
for the MS.
An exception indication contains the TLLI of the MS and an indication of the
exception condition, that is the Radio Cause value.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
BSC SGSN
BSSGP
RADIO-STATUS
BSSGP
20 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
1.3.7 Suspend
Figure 7. Suspend
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 SUSPEND PDU is acknowledged with a SUSPEND-ACK PDU by the
SGSN. The SUSPEND-ACK PDU contains the TLLI and the Routing Area of
the MS and the Suspend Reference Number.
Paging is typically stopped by the SGSN for a suspended mobile.
On receipt of the SUSPEND-ACK PDU, the BSC stops the TgbSuspend timer.
Abnormal conditions
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 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 containing a cause value "Unknown MS" is returned.
The BSC stops the SUSPEND procedure and the TgbSuspend timer.
BSC SGSN
BSSGP
SUSPEND
BSSGP
SUSPEND-ACK
SUSPEND-NACK
or
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
21 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.3.8 Resume
Not supported by the BSC. Resume of GPRS services relies on Routing Area
Update Requests sent by the MS. The BSC does not monitor the CS channel
release and thus it does not generate a resume message to the SGSN.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.3.9 Flush-LL
Figure 8. Flush LL
The SGSN sends a FLUSH-LL PDU to the BSC to ensure that 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 and the BVCI (old)
indicates the cell. All buffered LLC-PDUs in the cell 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 BVCI (old) and the
BVCI (new) are served by the same NSE and belong to the same RA.
BSC SGSN
BSSGP
FLUSH-LL
BSSGP
FLUSH-LL-ACK
22 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
A FLUSH-LL-ACK acknowledgement is sent back to the SGSN. The Flush
action parameter indicates whether LLC-PDUs were deleted in the BSC or
transferred to the new cell. If flush action indicates a transfer, the new BVCI is
included.
The number of affected data octets is also included.
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.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.3.10 Flow Control
Figure 9. BVC blo
The flow control mechanism is based on the following model:
.
There is a downlink buffer in the BSC for each cell, as identified by a
BVCI in the Gb interface
.
The transfer of BSSGP UNITDATA PDUs for an MS from SGSN is
controlled by the BSC by indicating both BVC specific and MS specific
buffer sizes and buffer leak rates to the SGSN
BSC SGSN
BSSGP
FLOW-CONTROL-BVC
BSSGP
FLOW-CONTROL-BVC-ACK
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
23 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
.
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 signalling
A FLOW-CONTROL-BVC PDU for a BVC is sent after every BVC-RESET in
order to start the downlink BSSGP data transfer. The TgbFlow timer is started.
FLOW-CONTROL-MS PDUs for a TLLI are sent only when a downlink TBF
exists for the TLLI.
The BVC level flow control parameters sent by the BSC to the SGSN consist of
the following information:
.
BVC Bucket Size: the data buffer size per cell for downlink LLC frames
.
Bucket Leak Rate: the throughput per cell for downlink LLC frames
.
Bmax Default MS: the data buffer size per MS for downlink LLC frames
.
R Default MS: the throughput per MS for downlink LLC frames
.
BVC Measurement is not used by the BSC
The MS level flow control parameters sent by the BSC to the SGSN consist of the
following information:
.
The TLLI identifying the MS
.
MS Bucket Size: the data buffer size for downlink LLC frames for this MS
.
Bucket Leak Rate: the throughput for downlink LLC frames for this MS
For each FLOW-CONTROL PDU received by an SGSN, a confirmation is
always sent across the Gb interface. The confimation uses the Tag that was
received in the FLOW-CONTROL PDU and set by the BSC to associate the
response with the request. When receiving flow control requests from the BSC,
the SGSN modifies its downlink transmission as instructed within 100ms. The
SGSN never transmits more data than what can be accomodated within the BSC
buffer for a BVC.
The next FLOW-CONTROL PDU, either BVC or MS specific, is sent to the
SGSN after the TgbFlow has expired if a criteria for controlling either BVC or
MS flow exists or if the GPRS configuration changes in the BSC affect the cell
buffer size or leak rate. Flow control indications allow the SGSN to locally
control its transmission output on the SGSN to the BSC direction.
24 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
When receiving no confirmation to a FLOW-CONTROL PDU and the reason for
flow control still exists, another FLOW-CONTROL PDU is triggered without
waiting for the expiration of the TgbFlow timer. If no reason for flow control
exists, no FLOW-CONTROL PDU is triggered.
The lifetime values of LLC frames are monitored by the BSC. If the lifetime
expires before the PDU can be sent, the PDU is deleted. The local deletion is
signalled to the SGSN by an LLC-DISCARDED PDU.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.3.11 BVC Blocking and Unblocking
Figure 10. BVC blocking and unblocking
BVC blocking is initiated by the BSC to remove a BVC from GPRS data use.
The BSC blocks a BVC after:
.
a BVC deletion via an O&M disable for the GPRS enabling/disabling
parameter of a cell. The cause is "O&M intervention"
.
an O&M disable for a cell or BCF. The cause is "O&M intervention"
.
an O&M disable for the last GPRS supporting TRX in a cell. The cause is
"O&M intervention"
BSC SGSN
BSSGP
BVC-BLOCK
BSSGP
BVC-BLOCK-ACK
BVC-UNBLOCK
BVC-UNBLOCK-ACK
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
25 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
.
a block of the last NS-VC of the NSE serving the BVC; related BVCs are
implicitly blocked, no indication is sent to the peer BSSGP
.
an SGSN initiated BVC-RESET procedure, if necessary. The cause is
"BVCI-blocked"
.
a cell level fault, e.g in the beginning of site reset, BTS reset or TRX reset.
The cause is "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 receiving a BVC-BLOCK PDU, the SGSN marks the indicated BVC as
blocked and stops transmitting traffic 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 receiving the BVC-BLOCK-ACK PDU, the BSC stops the TgbBlock
timer. Further incoming traffic on the blocked BVC is discarded by the BSC and
a STATUS PDU is returned on the signalling BVC with cause value indicating
"BVCI-blocked". The STATUS PDU indicates the BVCI of the BVC in which
the error was detected.
BVC unblocking is only used when an unexpected BVC-BLOCK-ACK PDU is
received by the BSC relating to a BVC that is locally unblocked. In such a case
the BVC is unblocked with the BVC-UNBLOCK PDU (see Abnormal
conditions).
The signalling BVC is never blocked or unblocked.
Abnormal conditions:
If an unexpected BVC-BLOCK-ACK PDU is received by the BSC relating to a
locally blocked BVC, the BVC-BLOCK-ACK PDU is ignored. If the BVC-
BLOCK-ACK PDU is related to a locally unblocked BVC, then the BVC is
unblocked with the BVC-UNBLOCK PDU.
If an unexpected BVC-UNBLOCK-ACK PDU is received by the BSC relating to
a locally unblocked BVC, the BVC-UNBLOCK-ACK PDU is ignored. If the
BVC-UNBLOCK-ACK PDU is related to a locally blocked BVC, the BVC is
blocked with the BVC-BLOCK PDU.
26 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
If a BVC-BLOCK-ACK PDU is not received for a BVC-BLOCK PDU within
TgbBlock seconds, the BVC blocking procedure is repeated a maximum of
BVCBlockRetries times. After BVCBlockRetries attempts the BVC remains
blocked and the procedure is stopped.
If a BVC-UNBLOCK-ACK PDU is not received for a BVC-UNBLOCK PDU
within TgbBlock seconds, the BVC unblocking procedure is repeated a
maximum of BVCUnblockRetries times. After BVCUnblockRetries attempts the
BVC remains blocked and the procedure is stopped.
If a BVC-BLOCK-ACK is awaited while a BVC-RESET PDU is received for the
signalling BVC, the signalling BVC reset procedure is handled first, after which
the BVC block procedure is resumed.
If a BVC-BLOCK-ACK PDU or BVC-UNBLOCK-ACK PDU is received for the
signalling BVC, the PDU is ignored.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.3.12 BVC Reset
Figure 11. BVC reset
BVC reset is initiated by the BSC to bring a BVC into GPRS data use. BVC reset
is used instead of the BVC unblock because of the dynamic configuration of
BVCs in the SGSN.
BSC resets a BVC after:
BSC SGSN
BSSGP
BVC-RESET
BSSGP
BVC-RESET-ACK
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
27 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
.
a BVC creation via an O&M enable for the GPRS enabling/disabling
parameter of a cell. The cause is "O&M intervention"
.
an O&M enable for a cell or BCF. The cause is "O&M intervention"
.
an O&M enable for the first GPRS supporting TRX in a cell. The cause is
"O&M intervention"
.
an unblock of the first NS-VC of the NSE serving the BVC (signalling
BVC is reset first, then the rest). The cause is "Network service
transmission capacity modified from zero kbps to greater than zero kbps"
.
a cell restart, e.g. after the site, BTS or TRX reset, when the restarted
object is up. The cause is "Equipment failure"
BSC initiated BVC reset:
In 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 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, but not the Cell id element. The Feature Bitmap is sent to identify the
optional features that can be supported by the network service entity. Currently
Feature Bitmap element includes bit for Packet Flow Context Procedures, which
is always coded as not supported (valid also in BVC-RESET-ACK).
After completion of the signalling BVC reset, the related PTP BVCs are reset and
a flow control procedure is triggered 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.
28 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
SGSN initiated BVC reset:
On receiving a BVC-RESET PDU for a PTP BVC, the BSC 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 accepted 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.
On receiving a BVC-RESET PDU for a signalling BVC, all UNITDATA PDU
traffic is stopped on the PTP BVCs of the NSE. After completion of the signalling
BVC reset, the related PTP BVCs are reset and a flow control procedure is
triggered 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 again operational.
If a BVC-RESET-ACK PDU is not received for a BVC-RESET PDU within
TgbReset seconds, the BVC-RESET procedure is repeated a maximum of
BVCResetRetries times. After BVCResetRetries 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 instead, indicating the same
BVCI, it is interpreted 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 is ignored.
If the BSC receives a BVC-RESET PDU for a BVCI which is unknown, a
STATUS PDU is returned, including the BVCI and a cause value "BVCI
unknown".
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
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 trace is invoked by
the SGSN by sending a SGSN-INVOKE-TRACE PDU to the BSC. The SGSN-
INVOKE-TRACE PDU is not acknowledged.
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
29 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
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. Other fields on
Trace Type are ignored by BSC.
Mobile Id indicates the MS relating to trace. SGSN includes it in the PDU in
order to activate or deactivate a trace.
OMCId, if present, indicates the OMC which the record is destined to.
Trigger Id and TransactionId are not used by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.4 General Protocol Error Handling
See General Protocol Error Handling in BSC-SGSN Interface Specification,
Network Service Protocol (NS). In addition, any type of BSSGP PDU received
for a feature that is not negotiated is discarded and a STATUS PDU ( cause "PDU
not compatible with the feature set") is sent
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 further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
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 .
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
30 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
1.5.1 DL-UNITDATA
This PDU is sent to the BSS to transfer a LLC-PDU across the radio interface to
an MS.
PDU type: DL-UNITDATA
Direction: SGSN to BSS
Information element Type / Reference Presence Format Length

PDU type PDU type M V 1

TLLI (current) TLLI M V 4
QoS Profile a) QoS Profile M V 3

PDU Lifetime PDU Lifetime M TLV 4
MS Radio Access
Capability b)
MS Radio AccessCapability C TLV 6-32
Priority c) Priority O TLV 3
DRX Parameters DRX Parameters O TLV 4
IMSI IMSI O TLV 5 -10
TLLI (old)
TLLI O TLV 6
PFI d) PFI O TLV 3
Alignment octets Alignment octets O TLV 2-5
LSA Information e) LSA Information O TLV 7 - ?
LLC-PDU LLC-PDU M TLV 3-?
a) Best Effort peak bit rate is supported.
b) The field is present only if there is valid MS Radio Access Capability
information known by the SGSN.
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
31 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
c) Not used.
d) Not used.
e) Not used.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.2 UL-UNITDATA
This PDU transfers the LLC-PDU of an MS and its associated radio interface
information across the Gb-interface.
PDU type: UL-UNITDATA
Direction: BSS to SGSN
Information element Type / Reference Presence Format Length

PDU type PDU type M V 1

TLLI TLLI M V 4
QoS Profile QoS Profile M V 3

Cell Identifier Cell Identifier M TLV 10
PFI a) PFI O TLV 3
Alignment octets Alignment octets O TLV 2-5
LSA Identifier List b) LSA Identifier List O TLV 3 - ?
LLC-PDU LLC-PDU M TLV 3-?
a) Not used.
b) Not used.
32 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.3 RA-CAPABILITY
This PDU informs the BSS of the new Radio Access Capability of an MS.
PDU type: RA-CAPABILITY
Direction: SGSN to BSS
Information element Type / Reference Presence Format Length

PDU type PDU type M V 1

TLLI TLLI M TLV 6
MS Radio Access Capability MS Radio AccessCapability M TLV 6-32
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.4 PTM-UNITDATA
GPRS phase 2 feature; not supported by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.5 PAGING-PS
This PDU indicates that a BSS initiates the packet paging procedure for an MS
within a group of cells.
PDU type: PAGING PS
Direction: SGSN to BSS
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
33 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

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 c) ABQP O TLV 3-?
QoS Profile d) QoS Profile M TLV 5
P-TMSI TMSI O TLV 6
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 supported.
c) Not supported.
d) Not supported.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.6 PAGING-CS
This PDU indicates that a BSS initiates a circuit-switched paging procedure for
an MS within a group of cells.
34 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
PDU type: PAGING CS
Direction: SGSN to BSS
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

IMSI IMSI M TLV 5 -10
DRX Parameters DRX Parameters M 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
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
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.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.7 RA-CAPABILITY-UPDATE
Not supported by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
35 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
1.5.8 RA-CAPABILITY-UPDATE-ACK
Not supported by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.9 RADIO STATUS
This PDU indicates that an exception condition related to the radio interface has
occurred.
PDU type: RADIO-STATUS
Direction: BSS to SGSN
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

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.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.10 SUSPEND
This PDU indicates that an MS wants to suspend its GPRS service.
PDU type: SUSPEND
Direction: BSS to SGSN
36 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

TLLI TLLI M TLV 6
Routing Area Routing Area M TLV 8
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.11 SUSPEND-ACK
This PDU positively acknowledges the reception of a SUSPEND PDU for an
MS.
PDU type: SUSPEND-ACK
Direction: SGSN to BSS
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

TLLI TLLI M TLV 6
Routing Area Routing Area M TLV 8
Suspend Reference Number Suspend ReferenceNumber M TLV 3
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
37 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
1.5.12 SUSPEND-NACK
This PDU negatively acknowledges the reception of a SUSPEND PDU for an
MS.
PDU type: SUSPEND-NACK
Direction: SGSN to BSS
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

TLLI TLLI M TLV 6
Routing Area Routing Area M TLV 8
Cause Cause O TLV 3
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.13 RESUME
Not supported by the BSC. Resume relies on Routing Area Update requests sent
by the MS. See BSSGP procedures, Resume .
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.14 RESUME-ACK
Not supported by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
38 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
1.5.15 RESUME-NACK
Not supported by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.16 FLUSH-LL
This PDU informs a BSS that an MS has moved from one cell to another.
PDU type: FLUSH-LL
Direction: SGSN to BSS
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

TLLI TLLI M TLV 6
BVCI (old) BVCI M TLV 4
BVCI (new) BVCI O TLV 4
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.17 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
Direction: BSS to SGSN
Information elements Type / Reference Presence Format Length

dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
39 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
Information elements Type / Reference Presence Format Length
PDU type PDU type M V 1

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 octetsaffected M TLV 5
a) BVCI (new) is included only if Flush action indicated that LLC-PDUs are
transferred.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.18 LLC-DISCARDED
This PDU indicates that a number of buffered LLC-PDUs in a cell for an MS
have been deleted inside the BSS.
PDU type: LLC-DISCARDED
Direction: BSS to SGSN
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

TLLI TLLI M TLV 6
LLC FramesDiscarded LLC Frames Discarded M TLV 3
BVCI BVCI M TLV 4
Number of octets deleted Number of octetsaffected M TLV 5
40 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.19 FLOW-CONTROL-BVC
This PDU informs the flow control mechanism at an SGSN of the status of a
BVC's maximum acceptable SGSN to BSS throughput on the Gb interface.
PDU type: FLOW-CONTROL-BVC
Direction: BSS to SGSN
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

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
BVC Measurement a) BVC Measurement O TLV 4
a) Not used by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.20 FLOW-CONTROL-BVC-ACK
This PDU informs the flow control mechanism at the BSS that the SGSN has
received the FLOW-CONTROL-BVC PDU indicated by the Tag.
PDU type: FLOW-CONTROL-BVC-ACK
Direction: SGSN to BSS
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
41 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

Tag Tag M TLV 3
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.21 FLOW-CONTROL-MS
This PDU informs the flow control mechanism at the SGSN of the status of an
MS's maximum acceptable SGSN to BSS throughput on the Gb interface.
PDU type: FLOW-CONTROL-MS
Direction: BSS to SGSN
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

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
a) Not used.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
42 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
1.5.22 FLOW-CONTROL-MS-ACK
This PDU informs the flow control mechanism at the BSS that the SGSN has
received the FLOW-CONTROL-MS PDU indicated by the TLLI and the Tag.
PDU type: FLOW-CONTROL-MS-ACK
Direction: SGSN to BSS
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

TLLI TLLI M TLV 6
Tag Tag M TLV 3
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.23 BVC-BLOCK
This PDU indicates that the contained BVC shall be blocked at the recipient
entity.
PDU type: BVC-BLOCK
Direction: BSS to SGSN
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

BVCI BVCI M TLV 4
Cause Cause M TLV 3
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
43 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
Typical cause values are O&M intervention and Equipment failure.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.24 BVC-BLOCK-ACK
This PDU acknowledges that a BVC has been blocked.
PDU type: BVC-BLOCK-ACK
Direction: SGSN to BSS
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

BVCI BVCI M TLV 4
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.25 BVC-UNBLOCK
This PDU indicates that the identified BVC shall be unblocked at the recipient
entity.
PDU type: BVC-UNBLOCK
Direction: BSS to SGSN
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

BVCI BVCI M TLV 4
44 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.26 BVC-UNBLOCK-ACK
This PDU acknowledges that a BVC has been unblocked.
PDU type: BVC-UNBLOCK-ACK
Direction: SGSN to BSS
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

BVCI BVCI M TLV 4
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.27 BVC-RESET
This PDU indicates that BVC initialisation is required.
PDU type: BVC-RESET
Direction: SGSN to BSS, BSS to SGSN
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

BVCI BVCI M TLV 4
Cause Cause M TLV 3
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
45 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
Information elements Type / Reference Presence Format Length
Cell Identifier a) Cell Identifier C TLV 10
Feature Bitmap b) Feature Bitmap O TLV 3
Typical cause values are: O&M intervention, Equipment failure and Network
service transmission capacity modified from zero kbps to greater than zero kbps.
a) Always included by 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 optional features are available
over the NSE.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.28 BVC-RESET-ACK
This PDU indicates that BVC recovery procedures have been executed.
PDU type: BVC-RESET-ACK
Direction: BSS to SGSN, SGSN to BSS
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

BVCI BVCI M TLV 4
Cell Identifier a) Cell Identifier C TLV 10
Feature Bitmap b) Feature Bitmap O TLV 3
a) Always included by the BSC in the case of a PTP BVC. Not included in the
case of a signalling BVC.
46 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
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 optional features are available
over the NSE.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.5.29 STATUS
This PDU indicates that an exception condition occurred.
PDU type: STATUS
Direction: SGSN to BSS, BSS to SGSN
Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

Cause Cause M TLV 3
BVCI a) BVCI C TLV 4
PDU In Error b) PDU In Error O TLV 3-?
a) The "BVCI" IE is only included when the "Cause" IE is set to the following
value:
1) "BVCI-blocked"
2) BVCI Unknown
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.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
47 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
1.5.30 SGSN-INVOKE-TRACE
This PDU indicates that the BSS begins the production of a trace record for an
MS.
PDU type: SGSN-INVOKE-TRACE
Direction: SGSN to BSS
IEI Information elements Type / Reference Presence Format Length

PDU type PDU type M V 1

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
TransactionId a) TransactionId O TLV 4
a) Not used by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6 BSSGP Information Elements (IEs)
For the general structure of information elements, for example length indicator
codings, see Network Service Control Information Elements (IEs) .
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
48 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
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
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
49 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
IEI coding IEI Types
x15 PDU In Error
x16 PDU Lifetime
x17 Priority
x18 QoS Profile
x19 Radio Cause
x1a RA-Cap-UPD-Cause
x1b Routing Area
x1c R_default_MS
x1d Suspend Reference Number
x1e Tag
x1f TLLI
x20 TMSI
x21 Trace Reference
x22 Trace Type
x23 TransactionId
x24 Trigger Id
x25 Number of octets affected
x26 LSA Identifier List
x27 LSA Information
x28 Packet Flow Identifier
x29 Packet Flow Timer
x3a Aggregate BSS QoS Profile (ABQP)
x3b Feature Bitmap

RESERVED All values not explicitly shown are reserved for future use and shall be
treated by the recipient as an unknown IEI
50 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.2 Alignment Octets
The Alignment Octets are used to align a subsequent IEI onto a 32 bit boundary.
The element coding is:
Table 11.2: Alignment octets IE
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 from 0 to 3 spare octets are present.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.3 Bmax Default MS
This information element indicates the default bucket size (Bmax) in octets for an
MS. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3-4 Bmax
The Bmax field is coded as Bmax in BVC Bucket Size IE.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
51 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
1.6.4 BSS Area Indication
This element is used to indicate that the paging is done in all the cells within the
BSS. The element coding is:
8 7 6 5 4 3 2 1
octet 1 IEI
octet 2,2a Length Indicator
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 shall not be specified. The BSC ignores the value of this
octet, that is only IEI coding is meaningful for the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
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:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
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, starting from 0 x 100 bits/sec until 65535 x 100 bits/sec (6
Mbps).
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
52 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
1.6.6 BVC Bucket Size
This information element indicates the maximum bucket size (Bmax) in octets for
a BVC. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
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, starting from 0 x 100 octets until 65535 x 100 octets (6
Mbytes).
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.7 BVCI
The BVCI identifies a BVC. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3-4 Unstructured value a)
a) BSS codes as: octet 3 = most significant octet of the BVCI
octet 4 = least significant octet of the BVCI
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
53 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
1.6.8 BVC Measurement
Not supported by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.9 Cause
The Cause information element indicates the reason for an exception condition.
The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3 Cause value
Cause value semantics of coding

Hexadecimal
All values not listed below shall be 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
54 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
Cause value semantics of coding
x08 O & M intervention
x09 BVCI-blocked

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 - reserved for future use
x28 PDU not compatible with the feature set

For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.10 Cell Identifier
This information element uniquely identifies one cell. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octets 3-8 Octets 3-8 contain the value part (starting with octet 2) of the
Routing Area Identification IE defined in GSM 04.08, Mobile Radio
Interface, Layer 3 specification, version 8.0.0, not including IEI
a)
Octets 9-10 Octets 9-10 contain the value part (starting with octet 2) of the Cell
Identity IE defined in 3. GSM 04.08, Mobile Radio Interface, Layer
3 specification, version 8.0.0, not including IEI
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
55 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
a) MNC contains 3 digits as defined in T1P1.5/98-227R1, CR about 3 digit MNC
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.11 Channel Needed
This information element is coded as defined in GSM 09.18, Gs Interface, Layer
3 specification, version 8.0.0. It is relevant to circuit-switched paging requests.
The element coding is:
8 7 6 5 4 3 2 1
octet 1 IEI
octet 2,2a Length Indicator
octet 3 Rest of element coded as the value part of the Channel Needed
PDU defined in GSM 09.18, Gs Interface, Layer 3 specification,
version 8.0.0, not including IEI and length indicator
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.12 DRX Parameters
This information element contains MS specific DRX information. The element
coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3-n Rest of element coded as the value part defined in GSM 04.08,
Mobile Radio Interface, Layer 3 specification, version 8.0.0, not
including IEI and length indicator
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
56 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
1.6.13 eMLPP Priority
This element indicates the eMLPP-Priority of a PDU. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3 Rest of element coded as the value part of the eMLPP-Priority IE
defined in GSM 08.08, MSC-BSS Interface, Layer 3 specification,
version 8.1.0, not including IEI and length indicator
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.14 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 2,2a Length Indicator
octet 3 Spare CBL PFC
"PFC bit" coding
Coding Semantic
0 Packet Flow Context Procedures not supported
1 Packet Flow Context Procedures supported
PFC bit is always coded as 0.
"CBL bit" coding
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
57 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
coding semantic
0 Current Bucket Level Procedures not supported
1 Current Bucket Level Procedures supported
CBL bit is always coded as 0.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.15 Flush Action
The Flush action information element indicates to the SGSN the action taken by
the BSS in response to the flush request. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
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 shall
be treated by the recipient as an unknown IEI
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
58 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
1.6.16 IMSI
This information element contains the International Mobile Subscriber Identity.
The element coding is:
8 7 6 5 4 3 2 1
octet 1 IEI
octet 2,2a Length Indicator
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 GSM 04.08, Mobile
Radio Interface, Layer 3 specification, version 8.0.0, not including
IEI and length indicator
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.17 LLC PDU
This information element contains an LLC-PDU. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3 LLC-PDU (first part)
Octet n LLC-PDU (last part)
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.18 LLC Frames Discarded
This element describes the number of LLC frames that have been discarded inside
a BSS. The element coding is:
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
59 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
8 7 6 5 4 3 2 1
octet 1 IEI
octet 2,2a Length Indicator
octet 3 Number of frames discarded (in hexadecimal)
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.19 Location Area
This element uniquely identifies one Location Area. The element coding is:
8 7 6 5 4 3 2 1
octet 1 IEI
octet 2,2a Length Indicator
octets 3-7 Octets 3-7 contain the value part (starting with octet 2) of the
Location Area Identification IE defined in GSM 04.08, Mobile
Radio Interface, Layer 3 specification, version 8.0.0, not including
IEI a)
The coding of octet 2 is a binary number indicating the Length of the remaining
element.
a) MNC contains 3 digits as defined in T1P1.5/98-227R1, CR about 3 digit
MNC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.20 Mobile Id
The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
60 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
8 7 6 5 4 3 2 1
Octet 2,2a Length Indicator
Octet 3-n Octets 3-n contain either the IMSI, IMEISV or IMEI coded as the
value part (starting with octet 3) of the Mobile Identity IE defined
GSM 04.08, Mobile Radio Interface, Layer 3 specification, version
8.0.0, not including IEI and length indicator
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.21 MS Bucket Size
This information element indicates a MS's bucket size (Bmax). The element
coding is:
8 7 6 5 4 3 2 1
octet 1 IEI
octet 2,2a Length Indicator
octet 3-4 Bmax
The Bmax field is coded as in section BVC Bucket Size/Bmax.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.22 MS Radio Access Capability
This information element contains the capabilities of the ME. The element coding
is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3-14 Rest of element coded as the value part defined in GSM 24.008,
not including IEI and octet length indicator.
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
61 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.23 OMC Id
The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3-22 For the OMC identity, see GSM 12.20, Base Station System
Management Information, version 4.2.0
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.24 PDU In Error
The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3-? Erroneous BSSGP PDU
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.25 PDU Lifetime
This information element describes the PDU Lifetime for a PDU inside the BSS.
The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
62 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
8 7 6 5 4 3 2 1
Octet 2,2a Length Indicator
Octet 3-4 Delay Value
The Delay Value field is coded as a 16-bit integer value in units of 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".
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.26 PDU Type
The first octet of a BSSGP PDU contains the PDU type IE. The length of the
PDU type IE is one octet.
PDU type coding PDU Types

(Hexadecimal)
x00 - DL-UNITDATA
x01 - UL-UNITDATA
x02 - RA-CAPABILITY
x03 - PTM-UNITDATA

x06 - PAGING PS
x07 - PAGING CS
x08 - RA-CAPABILITY-UPDATE
x09 - RA-CAPABILITY-UPDATE-ACK
x0a - RADIO-STATUS
x0b - SUSPEND
x0c - SUSPEND-ACK
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
63 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
PDU type coding PDU Types
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
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

RESERVED all values not explicitly shown are reserved for future use
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
64 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
1.6.27 Priority
Not used by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.28 QoS Profile
This information element describes the QoS Profile associated with a PDU. The
element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3-4 Peak bit rate provided by the network, coded as the value part in
Bucket Leak Rate IE a)
Octet 5 SPARE C/R T A Precedence
a) The bit rate 0 (zero) means "best effort" in this IE, supported by BSC. Other bit
rates are not supported.
"Precedence" is coded as shown below:
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.
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
65 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
"A-bit" is coded as shown below:
coding semantic
0 Radio interface uses RLC/MAC ARQ functionality
1 Radio interface uses RLC/MAC-UNITDATA functionality
"T-bit" is coded as shown below:
coding semantic
0 The PDU contains signalling (e.g. related to GMM)
1 The PDU contains data
"C/R-bit" is coded as shown below:
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
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.29 Radio Cause
This information element indicates the reason for an exception condition on the
radio interface. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3 Radio Cause value
66 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
radio cause value semantics of coding

(Hexadecimal)
x00 Radio contact lost with the MS
x01 a) Radio link quality insufficient to continue communication
x02 a) cell-reselection ordered
All values not explicitly listed are reserved. If received, they
shall be handled as "radio contact lost with the MS".
a) Not used by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.30 RA-Cap-Upd-Cause
Not used by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.31 Routing Area
This element uniquely identifies one routing area. The element coding is:
8 7 6 5 4 3 2 1
octet 1 IEI
octet 2,2a Length Indicator
octets 3-8 Octets 3-8 contain the value part (starting with octet 2) of the
Routing Area Identification IE defined in GSM 04.08, Mobile Radio
Interface, Layer 3 specification, version 8.0.0, not including IEI
a)
The coding of octet 2 is a binary number indicating the Length of the remaining
element.
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
67 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
a) MNC contains 3 digits as defined in T1P1.5/98-227R1, CR about 3 digit
MNC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.32 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:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3-4 R_default_MS value
The R_default_MS field is coded as the R Value in Bucket Leak Rate IE.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.33 Suspend Reference Number
The Suspend Reference Number information element contains an unformatted
reference number for each suspend/resume transaction. The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3 Suspend Reference Number
The Suspend Reference Number is an unformatted 8 bit field.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
68 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
1.6.34 Tag
This information element is used to correlate request and response PDUs. The
element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3 Unstructured value
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.35 Temporary Logical Link Identity (TLLI)
The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3-6 Rest of element coded as the value part of the TLLI IE in GSM
04.08, Mobile Radio Interface, Layer 3 specification, version 8.0.0,
not including IEI
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.36 TMSI
The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
69 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
Octet 3-6 Rest of element coded as the value part of the TMSI/P-TMSI IE in
GSM 04.08, Mobile Radio Interface, Layer 3 specification, version
8.0.0, not including IEI
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.37 Trace Reference
This element provides a trace reference number allocated by the triggering entity.
The element coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3-4 Trace Reference
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.38 Trace Type
This element provides the type of trace information to be recorded. The element
coding is:
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3 MSC/BSS Trace Type (specified in GSM 12.08, Subscriber and
Equipment Trace, version 5.1.0)
The MSC/BSS Trace Type field consists of the following components.
70 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
8 7 6 5 4 3 2 1
Priority
Indication
For future
expansion
(Set to 0)
BSS Record
Type
MSC Record Type Invoking Event
BSS Record Type field is supported by BSC. From the field BSC uses record
types "Basic" and "No BSS Trace" (see below). Other fields are ignored.
Bits Record Type
6 5
0 0 Basic
0 1 Handover
1 0 Radio
1 1 No BSS Trace
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.39 TransactionId
Not used by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.40 Trigger Id
Not used by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.41 Number Of Octets Affected
This information element indicates for an MS the number of octets transferred or
deleted by the BSS. The element coding is:
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
71 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2,2a Length Indicator
Octet 3-5 number of octets transferred or deleted
The number of octets transferred or deleted by the BSS may be higher than the
maximum Bmax value (6553500). The SGSN handles any value higher than
6553500 as the Bmax value.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.42 LSA Identifier List
Not used by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.6.43 LSA Information
Not used by the BSC.
For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
1.7 List of system variables
Table 2. BSSGP timers
Timer name Value range/
default
notes relation to other timers
TgbBlock 1 - 30s/3s Guards the (un)blocking
procedures
None
TgbReset 1 - 120s/3s Guards the reset procedure None
72 (73) # Nokia Corporation
Nokia Proprietary and Confidential
dn9983079
Issue 4-0 en
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)
Table 2. BSSGP timers (cont.)
Timer name Value range/
default
notes relation to other timers
TgbSuspend 0.1 - 10s/3s Guards the suspend
procedure
None
TgbFlow 1s BSSGP flow control
supervision timer
None

Table 3. BSSGP parameters
Counter name Value range/
default
notes relation to other
parameters
BVCBlockRetries 1 - 100/3 None none
BVCUnblockRetries 1 - 100/3 None none
BVCResetRetries 1 - 100/3 none none
SuspendRetries 1 - 100/3 none none

For further information on BSC-SGSN Interface, refer to BSC-SGSN Interface
Specification BSS GPRS Protocol (BSSGP) description .
dn9983079
Issue 4-0 en
# Nokia Corporation
Nokia Proprietary and Confidential
73 (73)
BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) description