bsc-sgsn interface specification bss gprs protocol (bssgp)

Nokia Siemens Networks GSM/EDGE BSS, rel. RG20(BSS), operating documentation, issue 02

Reference

BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP)

DN9983079

Issue 10-0Approval Date 2010-08-11

Confidential

2 DN9983079Issue 10-0

BSC-SGSN Interface Specification BSS GPRS Proto-col (BSSGP)

Id:0900d805807c46a8Confidential

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright Nokia Siemens Networks 2010. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Span-nung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverlet-zungen und Sachschden fhren.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.

DN9983079Issue 10-0

3



Table of contentsThis document has 75 pages.

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

1 BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) descrip-tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.1 Position of BSSGP within the protocol stack on the Gb interface . . . . . 101.2 Primitive parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.2.1 BSSGP Virtual Connection Identifier (BVCI) . . . . . . . . . . . . . . . . . . . . . 111.2.2 Link Selector Parameter (LSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2.3 Network Service Entity Identifier (NSEI) . . . . . . . . . . . . . . . . . . . . . . . . 121.3 BSSGP procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3.1 Downlink Unitdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3.2 Uplink Unitdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3.3 RA Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.3.4 Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.3.5 Radio Access Capability Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.3.6 Radio Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.3.7 Suspend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.3.8 Resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.3.9 Flush-LL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.3.10 Flow Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.3.11 BVC Blocking and Unblocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.3.12 BVC Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231.3.13 Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241.3.14 RIM procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.3.14.1 RAN Information Request procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . 251.3.14.2 RAN Information Send procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.3.14.3 RAN Information Application Error procedure . . . . . . . . . . . . . . . . . . . . 281.3.14.4 RAN Information Error procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.3.14.5 Abnormal conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.4 General protocol error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311.5 BSSGP protocol data units (PDUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321.5.1 DL-UNITDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321.5.2 UL-UNITDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321.5.3 RA-CAPABILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.5.4 PAGING-PS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.5.5 PAGING-CS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341.5.6 RA-CAPABILITY-UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341.5.7 RA-CAPABILITY-UPDATE-ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351.5.8 RADIO-STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351.5.9 SUSPEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351.5.10 SUSPEND-ACK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361.5.11 SUSPEND-NACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361.5.12 RESUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361.5.13 RESUME-ACK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371.5.14 RESUME-NACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4 DN9983079Issue 10-0



1.5.15 FLUSH-LL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371.5.16 FLUSH-LL-ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381.5.17 LLC-DISCARDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381.5.18 FLOW-CONTROL-BVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381.5.19 FLOW-CONTROL-BVC-ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391.5.20 FLOW-CONTROL-MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391.5.21 FLOW-CONTROL-MS-ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401.5.22 BVC-BLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401.5.23 BVC-BLOCK-ACK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401.5.24 BVC-UNBLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401.5.25 BVC-UNBLOCK-ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411.5.26 BVC-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411.5.27 BVC-RESET-ACK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411.5.28 STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421.5.29 SGSN-INVOKE-TRACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421.5.30 RAN-INFORMATION-REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431.5.31 RAN-INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431.5.32 RAN-INFORMATION-ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431.5.33 RAN-INFORMATION-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441.5.34 RAN-INFORMATION-APPLICATION-ERROR. . . . . . . . . . . . . . . . . . . . 441.6 BSSGP information elements (IEs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441.6.1 IEI codings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451.6.2 Alignment Octets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481.6.3 Bmax Default MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481.6.4 BSS Area Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481.6.5 Bucket Leak Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491.6.6 BVC Bucket Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491.6.7 BVCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491.6.8 BVC Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501.6.9 Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501.6.10 Cell Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521.6.11 Channel Needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521.6.12 DRX Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521.6.13 eMLPP Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531.6.14 Flush Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531.6.15 IMSI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531.6.16 LLC PDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531.6.17 LLC Frames Discarded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541.6.18 Location Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541.6.19 Mobile Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541.6.20 MS Bucket Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551.6.21 MS Radio Access Capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551.6.22 OMC Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551.6.23 PDU In Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551.6.24 PDU Lifetime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551.6.25 PDU Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561.6.26 QoS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

DN9983079Issue 10-0

5



1.6.27 Radio Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581.6.28 RA-Cap-UPD-Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591.6.29 Routing Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591.6.30 R_default_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591.6.31 Suspend Reference Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601.6.32 Tag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601.6.33 Temporary Logical Link Identity (TLLI) . . . . . . . . . . . . . . . . . . . . . . . . . 601.6.34 TMSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601.6.35 Trace Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601.6.36 Trace Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611.6.37 Transaction Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611.6.38 Trigger Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611.6.39 Number Of Octets Affected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611.6.40 LSA Identifier List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621.6.41 LSA Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621.6.42 Packet Flow Identifier (PFI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621.6.43 Aggregate BSS QoS Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621.6.44 Feature Bitmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621.6.45 Bucket Full Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641.6.46 Service UTRAN CCO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641.6.47 NSEI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651.6.48 RIM Application Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651.6.49 RIM Sequence Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651.6.50 RAN-INFORMATION-REQUEST Application Container . . . . . . . . . . . . 661.6.51 RAN-INFORMATION Application Container . . . . . . . . . . . . . . . . . . . . . 661.6.52 RIM PDU Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671.6.53 Global CN-Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681.6.54 RIM Routing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681.6.55 RIM Protocol Version Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701.6.56 Application Error Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701.6.57 RAN-INFORMATION-REQUEST RIM container . . . . . . . . . . . . . . . . . . 711.6.58 RAN-INFORMATION RIM container . . . . . . . . . . . . . . . . . . . . . . . . . . . 721.6.59 RAN-INFORMATION-APPLICATION-ERROR RIM Container . . . . . . . 721.6.60 RAN-INFORMATION-ACK-RIM container. . . . . . . . . . . . . . . . . . . . . . . 731.6.61 RAN-INFORMATION-ERROR RIM Container. . . . . . . . . . . . . . . . . . . . 731.6.62 Extended Feature Bitmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741.6.63 Flow Control Granularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741.6.64 Subscriber Profile ID for RAT/Frequency priority. . . . . . . . . . . . . . . . . . 741.7 List of system variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

6 DN9983079Issue 10-0



List of figuresFigure 1 The protocol stack on the Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . 10Figure 2 DL Unitdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 3 UL Unitdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 4 RA Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 5 Paging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 6 Radio Access Capability Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 7 Radio Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 8 Suspend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 9 Flush LL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 10 BVC Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 11 BVC Blocking and Unblocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 12 BVC Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 13 RAN Information Request/Single report Procedure . . . . . . . . . . . . . . . . 25Figure 14 RAN Information Request/Multiple Report Procedure . . . . . . . . . . . . . . 26Figure 15 RAN Information Request/Stop Procedure . . . . . . . . . . . . . . . . . . . . . . . 27Figure 16 Acknowledged RAN Information Send procedure . . . . . . . . . . . . . . . . . 27Figure 17 RAN Information Application Error procedure. . . . . . . . . . . . . . . . . . . . . 28Figure 18 RAN Information Error procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

DN9983079Issue 10-0

7



List of tablesTable 1 BSSGP PDU, BVCI, and functional entity mapping . . . . . . . . . . . . . . . 11Table 2 BSSGP timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Table 3 BSSGP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

8 DN9983079Issue 10-0



DN9983079Issue 10-0

9


Summary of changes

Id:0900d805807c46aaConfidential

Summary of changesChanges between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Changes made between issues 10 and 9The BSS-SGSN Interface, BSS GPRS Protocol, specification baseline has been updated from 3GPP TS 48.018, version 7.10.0 to 3GPP TS 48.018, version 8.2.0.

Changes made between issues 9-0 and 8-0The BSS-SGSN Interface, BSS GPRS Protocol, specification baseline has been updated from 3GPP TS 48.018, version 6.11.0 to 3GPP TS 48.018, version 7.10.0 Rel-7.

Changes made between issues 8-0 and 7-0The BSS-SGSN Interface, BSS GPRS Protocol, specification baseline has been updated from 3GPP TS 48.018, version 5.11.0 to 3GPP TS 48.018, version 6.11.0 Rel-6.

Changes made between issues 7-0 and 6-0References to PFC procedures have been removed.

The BSS-SGSN Interface, BSS GPRS Protocol, specification baseline has been updated from 3GPP TS 48.018, version 4.5.0 to 3GPP TS 48.018, version 5.11.0.

Section on RIM procedures has been deleted.

Subsection Paging in section BSSGP procedures has been modified to include other optional parameters.

A new row at the very end of the table under section PAGING-CS has been added to include Global CN-Id b) information.

10 DN9983079Issue 10-0


Id:0900d805807cc588Confidential

BSC-SGSN Interface Specification BSS GPRS Proto-col (BSSGP) description

1 BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) descriptionThis 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 8.2.0, Rel-8. This document describes the BSS GPRS Protocol (BSSGP) implementation for controlling of GSM packet data services in the BSC SW release S15. 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 8.2.0, Rel-8. Any exceptions to this general rule 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 Rec-ommendation

This description is general and used for all customers.

1.1 Position of BSSGP within the protocol stack on the Gb interfaceGb 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 sub-network 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

Network service control is responsible for virtual circuit management and GPRS-specific addressing, which maps cells to virtual connections.

The BSSGP is a layer 3 protocol for delivering data packets and associated control infor-mation. The BSSGP also includes procedures, for example, for downlink flow control, paging, and virtual circuit management.

LLC

BSSGP

NS

L1

SGSN

NSMAC

L1

BSC

RELAY

RLC BSSGP

Gb

DN9983079Issue 10-0

11




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.

NOTE 1: SGSN may initiate paging of a mobile station (MS) in READY mobility man-agement state at an indication of a lower layer failure. In this case the BVCI = PTP may be used.

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-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

RAN-INFORMATION-REQUEST / RAN-INFORMA-TION / RAN-INFORMATION-ACK / RAN-INFOR-MATION-ERROR / RAN-INFORMATION-APPLICATION-ERROR

SIGNALLING

Table 1 BSSGP PDU, BVCI, and functional entity mapping

12 DN9983079Issue 10-0




NOTE 2: If the SGSN initiates circuit-switched paging of an MS in READY mobility man-agement state, the BVCI is PTP. If the MS is in STANDBY state, the BVCI is SIGNAL-LING.

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 signifi-cance 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

1.3.1 Downlink Unitdata

Figure 2 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 Param-

DL-UNITDATA

BSC SGSN

BSSGP BSSGP

DN9983079Issue 10-0

13




eters 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 DLUNITDATA 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 nego-tiated. 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. PFI is not used as the Nokia Siemens Networks BSC does not support Packet Flow Contexts (PFC).

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 inter-face.

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 prioritisation of downlink LLC-PDUs on the radio interface.

Two transmission modes on the radio interface are possible: acknowledged (using RLC/MAC ARQ functionality) and unacknowledged (using RLC/MAC unitdata function-ality) 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 proce-dure 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.

14 DN9983079Issue 10-0




1.3.2 Uplink Unitdata

Figure 3 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.

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 DL-UNITDATA for the TLLI (indicated in the UL-UNITDATA) is sent.

UL-UNITDATA

BSC SGSN

BSSGP BSSGP

DN9983079Issue 10-0

15




1.3.3 RA Capability

Figure 4 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.

1.3.4 Paging

Figure 5 Paging

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)

RA-CAPABILITY

BSC SGSN

BSSGP BSSGP

PAGING-PS

PAGING-CS

or

BSC SGSN

BSSGP BSSGP

16 DN9983079Issue 10-0




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 iden-tified 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.

1.3.5 Radio Access Capability Update

Figure 6 Radio Access Capability Update

The BSC may request the MS's current radio access capability and/or its 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 RACAPABILITY-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 conditionsIf 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.

BSC SGSN

BSSGP

RA-CAPABILITY-UPDATE

BSSGP

RA-CAPABILITY-UPDATE-ACK

DN9983079Issue 10-0

17




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.

1.3.6 Radio Status

Figure 7 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 excep-tion condition, that is, the radio cause value.

BSC SGSN

BSSGP

RADIO-STATUS

BSSGP

18 DN9983079Issue 10-0




1.3.7 Suspend

Figure 8 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 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 conditionsIf 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 pro-cedure and the TgbSuspend timer.

1.3.8 ResumeWhen 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

BSC SGSN

BSSGP

SUSPEND

BSSGP

SUSPEND-ACK

SUSPEND-NACK

or

DN9983079Issue 10-0

19




Routing Area of the MS Suspend Reference NumberThe 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 indi-cates 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 conditionsIf 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.

1.3.9 Flush-LL

Figure 9 Flush LL

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. 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 BVCIs belong to different PCUs but to the same RA and the new and the old BVCI belong to the same NSE (Packet Control Unit (PCU2) Pooling is in use) DL LLC PDUs are not transferred.

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.

FLUSH-LL

FLUSH-LL-ACK

BSC SGSN

BSSGP BSSGP

20 DN9983079Issue 10-0




The FLUSH-LL-ACK PDU also contains the Number of octets affected field that indi-cates the number of deleted or transferred data octets.

Abnormal conditionsIf 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.

1.3.10 Flow Control

Figure 10 BVC Flow Control

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 effi-ciently.

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 follow-ing 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 valueThis is only used if the Current Bucket Level (CBL) is negotiated. However, the Nokia Siemens Networks BSC does not support this functionality.

BSC SGSN

BSSGP

FLOW-CONTROL-BVC

BSSGP

FLOW-CONTROL-BVC-ACK

DN9983079Issue 10-0

21




BVC Measurement (optional): average queuing delay for the BSCThe 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.

The FLOW-CONTROL-MS PDU which the BSC sends to the SGSN contains the follow-ing 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 valueThis is only used if the Current Bucket Level (CBL) is negotiated. However, the Nokia Siemens Networks 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 accom-modated within the BSC buffer for a given BVC or an MS.

Abnormal conditionsIf 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

The BSC initiates the BVC blocking to remove a BVC from GPRS data use.

BSC SGSN

BSSGP

BVC-BLOCK

BSSGP

BVC-BLOCK-ACK

BVC-UNBLOCK

BVC-UNBLOCK-ACK

22 DN9983079Issue 10-0




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. 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 conditionsIf 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 BVCBlockRe-tries 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 proce-dure 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.

DN9983079Issue 10-0

23




If the BSC receives a BVC-BLOCK-ACK PDU or a BVC-UNBLOCK-ACK PDU for the signalling BVC, it ignores the PDU.

1.3.12 BVC Reset

Figure 12 BVC Reset

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 resetIn 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 Bitmap but not the Cell id element.

BSC SGSN

BSSGP

BVC-RESET

BSSGP

BVC-RESET-ACK

24 DN9983079Issue 10-0




The Feature Bitmap is 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 Bitmap with its own Feature Bitmap.

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 resetWhen 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 pro-cedure 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 conditionsIf the associated network service is not operational, the BVC-RESET procedure is post-poned 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 BVCResetRe-tries 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 TraceThe 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.

DN9983079Issue 10-0

25




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 RIM procedures

1.3.14.1 RAN Information Request procedureRAN 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 procedureRAN-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 con-taining the Information Elements PDU type, Destination Cell Identifier, Source Cell Iden-tifier 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 Con-trolling 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 Nokia Siemens Networks 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

26 DN9983079Issue 10-0




as serving BSC, i.e. it may receive and serve RAN-INFORMATION-REQUEST/Single Report for NACC application.

RAN Information Request / Multiple Report procedureRAN-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-INFORMA-TION-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.

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 Nokia Siemens Networks BSC restarts the pro-cedure once in T(RIR) expiry.

RAN Information Request / Stop procedureRAN-INFORMATION-REQUEST/Stop is used to stop event driven multiple reports.

DN9983079Issue 10-0

27




Figure 15 RAN Information Request/Stop Procedure

In RAN-INFORMATION REQUEST/Stop procedure the Controlling BSC, RNC or eNB sends RAN-INFORMATION-REQUEST/Stop PDU to Serving BSC containing the Infor-mation 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 proce-dure ends.

When Controlling BSC, RNC or eNB receives the response from Serving BSC, Control-ling BSC, RNC or eNB 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/Stop procedure.

The Nokia Siemens Networks BSC acting as controlling BSC does not control the recep-tion 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.14.2 RAN Information Send procedureRAN 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

28 DN9983079Issue 10-0




If multiple reporting has been subscribed for a given RIM association, the RAN Informa-tion 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 Con-tainer. Acknowledgement for the PDU may or may not be requested. If acknowledge-ment was requested serving BSC starts timer T(RI) after the sending.

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-INFOR-MATION-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 deac-tivated 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 pro-cedure 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 Nokia Siemens Networks BSC acting as serving BSC never requests acknowledge-ment for the RAN-INFORMATION/Multiple Report PDU. The Nokia Siemens Networks BSC acting as serving BSC requests acknowledgement for the RAN-INFORMA-TION/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.14.3 RAN Information Application Error procedureThe 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 appli-cation 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

DN9983079Issue 10-0

29




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.

The Nokia Siemens Networks BSC never acts as controlling BCS in this procedure, i.e. it never sends RAN-INFORMATION-APPLICATION-ERROR PDU. Though Nokia Siemens Networks BSC does not take any other action on received RAN-INFORMA-TION-APPLICATION-ERROR PDU but if acknowledgement was requested serving BSC sends RAN-INFORMATION-ACK PDU to the controlling BSC, RNC or eNB.

1.3.14.4 RAN Information Error procedureThe 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.14.5 Abnormal conditionsIf 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 dis-carded and a STATUS PDU with the appropriate cause value "Unknown Destination address" shall be sent back to the SGSN.

30 DN9983079Issue 10-0




If the RIM container included in a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICA-TION-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.

If the PDU Type Extension field in the RIM PDU Indications IE included in the RIM con-tainer of a RAN-INFORMATION-REQUEST PDU does not indicate "RAN-INFORMA-TION-REQUEST/Multiple Report", "RAN-INFORMATION-REQUEST/Stop" or "RAN-INFORMATION-REQUEST/Single Report", the serving BSC shall send a RAN-INFOR-MATION-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 con-tainer 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-INFORMA-TION-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.

DN9983079Issue 10-0

31




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-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 "Invalid mandatory information" back to the originating BSC and discard the received PDU.

If a syntactical error is detected in a mandatory IE included in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSC shall discard the received PDU without further action.

If an unexpected conditional Information Element is received in the RIM container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMA-TION-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 "Unexpected Conditional IE" back to the originating BSC and discard the received PDU.

If an unexpected conditional Information Element is received in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSC shall discard the received PDU without further action.

The receiving BSC may accept RIM containers that include information elements that do not appear to be in the correct sequence. However, Nokia Siemens Networks 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 Nokia Siemens Networks BSC, shall regard the RIM container as containing unex-pected 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 "Seman-tically 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 handlingThe 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

32 DN9983079Issue 10-0




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

1.5.1 DL-UNITDATAThis 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.

a) The field is present only if there is valid MS Radio Access Capability information known by the SGSN.b) Not used.c) Not used as the packet flow context feature has ever been negotiated.d) The LLC-PDU Length Indicator may be zero.

1.5.2 UL-UNITDATAThis PDU transfers the LLC-PDU of an MS and its associated radio interface information on the Gb interface.

PDU type: UL-UNITDATA.

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 Capability a)

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 c) PFI O TLV 3

LSA Information b) LSA Information O TLV 7-?

Service UTRAN CCO Service UTRAN CCO O TLV 3

Alignment octets Alignment octets O TLV 25

Subscriber Profile ID for RAT/Frequency priority b)

Subscriber Profile ID for RAT/Frequency priority

O TLV 3

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

DN9983079Issue 10-0

33




Direction: BSC to SGSN.

a) Not used as the packet flow context feature has ever been negotiated.

b) Not used.

c) The LLC-PDU Length Indicator may be zero.

1.5.3 RA-CAPABILITYThis PDU informs the BSC of the new Radio Access Capability of an MS.

PDU type: RA-CAPABILITY.


1.5.4 PAGING-PSThis PDU indicates that a BSC initiates the packet paging procedure for an MS within a group of cells.

PDU type: PAGING PS.




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

LSA Identifier List b) LSA Identifier List O TLV 3-?

Alignment octets Alignment octets O TLV 2-5

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



TLLI TLLI M TLV 6

MS Radio Access Capability MS Radio Access Capabil-ity

M TLV 7-?

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

34 DN9983079Issue 10-0




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-CSThis PDU indicates that a BSC initiates a circuit-switched paging procedure for an MS within a group of cells.

PDU type: PAGING CS.


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-UPDATEThis PDU requests that the SGSN sends the MS's current Radio Access capability or IMSI to the BSC.

PDU type: RA-CAPABILITY-UPDATE.


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




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

Global CN-Id b) Global CN-Id O TLV 7

DN9983079Issue 10-0

35




1.5.7 RA-CAPABILITY-UPDATE-ACKThis PDU provides the BSC with the MS's current Radio Access capability and IMSI.

PDU type: RA-CAPABILITY-UPDATE-ACK.


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-STATUSThis PDU indicates that an exception condition related to the radio interface has occurred.

PDU type: RADIO-STATUS

Direction: BSC to SGSN

a) Only one of the conditional IEs is present. TLLI is always used by the BSC.

1.5.9 SUSPENDThis PDU indicates that an MS wants to suspend its GPRS service.

Information element Type/Reference Presence Format Length


TLLI TLLI M TLV 6

Tag Tag M TLV 3

Information element Type/Reference Presence Format Length


TLLI TLLI M TLV 6

Tag Tag M TLV 3

IMSI a) IMSI C TLV 510

RA-Cap-UPD-Cause

RA-Cap-UPD-Cause

M TLV 3

MS radio Access Capability a)

MS Radio Access Capability

C TLV 7?



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

36 DN9983079Issue 10-0




PDU type: SUSPEND.


1.5.10 SUSPEND-ACKThis PDU positively acknowledges the reception of a SUSPEND PDU for an MS.

PDU type: SUSPEND-ACK.


1.5.11 SUSPEND-NACKThis PDU negatively acknowledges the reception of a SUSPEND PDU for an MS.

PDU type: SUSPEND-NACK.


1.5.12 RESUMEThis PDU indicates that an MS wishes to resume its GPRS service.

PDU type: RESUME.




TLLI TLLI M TLV 6

Routing Area Routing Area M TLV 8



TLLI TLLI M TLV 6


Suspend Reference Number Suspend Reference Number

M TLV 3



TLLI TLLI M TLV 6


Cause Cause O TLV 3



TLLI TLLI M TLV 6


DN9983079Issue 10-0

37




1.5.13 RESUME-ACKThis PDU acknowledges the reception of a RESUME PDU for an MS.

PDU type: RESUME-ACK.


1.5.14 RESUME-NACKThis PDU negatively acknowledges the reception of a RESUME PDU for an MS.

PDU type: RESUME-NACK.


1.5.15 FLUSH-LLThis PDU informs a BSC that an MS has moved from one cell to another.

PDU type: FLUSH-LL.


a) Not supported.

Suspend Reference Number Suspend Reference Number M TLV 3




TLLI TLLI M TLV 6




TLLI TLLI M TLV 6


Cause Cause O TLV 3



TLLI TLLI M TLV 6

BVCI (old) BVCI M TLV 4

BVCI (new) BVCI O TLV 4

NSEI (new) a) NSEI O TLV 4

38 DN9983079Issue 10-0




1.5.16 FLUSH-LL-ACKThis 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


a) BVCI (new) is included only if Flush action indicated that LLC-PDUs are transferred.b) Not supported.

1.5.17 LLC-DISCARDEDThis 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.


a) Not used as the PFC Flow Control feature has ever been negotiated.

1.5.18 FLOW-CONTROL-BVCThis 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.




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



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 affected

M TLV 5

PFI a) PFI O TLV 3

DN9983079Issue 10-0

39




a) Not used

1.5.19 FLOW-CONTROL-BVC-ACKThis 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.


1.5.20 FLOW-CONTROL-MSThis 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.


a) Not used.



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



Tag Tag M TLV 3



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

40 DN9983079Issue 10-0




1.5.21 FLOW-CONTROL-MS-ACKThis 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.


1.5.22 BVC-BLOCKThis PDU indicates that the contained BVC is blocked at the recipient entity.

PDU type: