Power Parameters changes

GSM/EDGE BSS, Rel. RG30(BSS), Operating Documentation, Issue 02

Feature description

BSS09006: GPRS System Feature Description

DN7036138

Issue 4-2Approval Date 2011-08-24

Confidential

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their compo-nents.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Siemens Networks for any additional information.

2 DN7036138


Id:0900d8058089e65dConfidential

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 2011. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the Legal, Safety and Environmental Information part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal, Safety and Environmental Information dieses Dokuments oder dieses Dokumentations-satzes.

DN7036138 3



Table of contentsThis document has 131 pages.

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

1 GPRS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.1 GPRS data transfer protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.2 Optimised GPRS Radio Resource Management. . . . . . . . . . . . . . . . . . 161.3 Frame Relay and Gb Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.4 GPRS in Nokia Siemens Networks Base Stations. . . . . . . . . . . . . . . . . 21

2 Software related to GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.1 Extended Uplink TBF Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.2 GPRS Coding Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.3 Link Adaptation for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.4 Priority Class Based Quality of Service (QoS). . . . . . . . . . . . . . . . . . . . 272.5 System Level Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3 System impact of GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.2 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.3 Impact on transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.4 Impact on BSS performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.5 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.5.1 BSC MMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.5.2 BTS MMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.5.3 BSC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.5.4 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.5.5 Measurements and counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.6 Impact on Network Switching Subsystem (NSS) . . . . . . . . . . . . . . . . . . 463.7 Impact on NetAct products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.8 Impact on mobile terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.9 Impact on interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.10 Interworking with other features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4 System impact of GPRS related software . . . . . . . . . . . . . . . . . . . . . . . 554.1 System impact of Extended Uplink TBF Mode . . . . . . . . . . . . . . . . . . . 554.1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.1.2 Impact on transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.1.3 Impact on BSS performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.1.4 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.1.5 Impact on Network Switching Subsystem (NSS) . . . . . . . . . . . . . . . . . . 574.1.6 Impact on NetAct products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.1.7 Impact on mobile terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.1.8 Impact on interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.1.9 Interworking with other features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.2 System impact of Priority Class based Quality of Service . . . . . . . . . . . 594.2.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.2.2 Impact on transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

4 DN7036138



4.2.3 Impact on BSS performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.2.4 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.2.5 Impact on Network Switching Subsystem (NSS) . . . . . . . . . . . . . . . . . . 624.2.6 Impact on NetAct products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.2.7 Impact on mobile terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.2.8 Impact on interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.2.9 Interworking with other features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.3 System impact of System Level Trace . . . . . . . . . . . . . . . . . . . . . . . . . . 644.3.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.3.2 Impact on transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.3.3 Impact on BSS performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.3.4 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.3.5 Impact on Network Switching Subsystem (NSS) . . . . . . . . . . . . . . . . . . 694.3.6 Impact on NetAct products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694.3.7 Impact on mobile terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704.3.8 Impact on interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704.3.9 Interworking with other features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

5 Requirements for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.1 Packet Control Unit (PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.2 Gb interface functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.3 Additional GPRS hardware needed in BSCi and BSC2i. . . . . . . . . . . . . 775.4 Additional hardware needed for GPRS support over Packet Abis interface

77

6 Radio network management for GPRS. . . . . . . . . . . . . . . . . . . . . . . . . . 796.1 Routing Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796.2 PCU selection algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

7 Gb interface configuration and state management . . . . . . . . . . . . . . . . . 827.1 Protocol stack of the Gb interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827.2 Load sharing function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837.3 NS-VC management function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847.4 BVC management function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877.5 Recovery in restart and switchover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

8 Radio resource management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918.1 Territory method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918.2 Circuit switched traffic channel allocation in GPRS territory . . . . . . . . . . 988.3 BTS selection for packet traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998.4 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998.5 Channel allocation and scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008.6 Quality Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068.7 MS Multislot Power Reduction (PCU2) . . . . . . . . . . . . . . . . . . . . . . . . . 1078.8 Error situations in GPRS connections. . . . . . . . . . . . . . . . . . . . . . . . . . 109

9 GPRS radio connection control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119.1 Radio channel usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119.2 Data Transfer Protocols and Connections . . . . . . . . . . . . . . . . . . . . . . 1129.3 Paging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

DN7036138 5



9.4 Mobile terminated TBF (GPRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1149.5 Mobile originated TBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169.6 Suspend and resume GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189.7 Flush . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1199.8 Cell selection and re-selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209.9 Traffic administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209.10 Coding scheme selection in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229.11 Power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299.12 MS Radio Access Capability update . . . . . . . . . . . . . . . . . . . . . . . . . . 129

10 Implementing GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13110.1 Implementing GPRS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

6 DN7036138



List of figuresFigure 1 GPRS network seen by another data network . . . . . . . . . . . . . . . . . . . . 12Figure 2 GPRS architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 3 Transmission plane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 4 Transmission and reception data flow . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 5 GPRS DCH dedicated channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 6 Example of a GPRS capable cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 7 Air interface traffic management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 8 BSC - SGSN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 9 Gb logical structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 10 Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 11 Example of transmission turns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Figure 12 Trace activation/deactivation and report generation . . . . . . . . . . . . . . . . 29Figure 13 Architecture of the GPRS network and related network elements . . . . . 30Figure 14 PCU connections to BTS and SGSN when Frame Relay is used . . . . . 73Figure 15 Protocol stack of the Gb interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Figure 16 Gb interface between the BSC and SGSN when Frame Relay (FR) is used

77Figure 17 Relationship of Routing Areas and PCUs . . . . . . . . . . . . . . . . . . . . . . . . 79Figure 18 The protocol stack on the Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . 82Figure 19 Territory method in BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Figure 20 GPRS territory upgrade when a timeslot is cleared for GPRS use with an

intra cell handover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Figure 21 Dynamic Allocation MAC mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Figure 22 Extended Dynamic Allocation MAC mode . . . . . . . . . . . . . . . . . . . . . . 105Figure 23 Uplink power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

DN7036138 7



List of tablesTable 1 GPRS Coding Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Table 2 Required additional or alternative hardware or firmware . . . . . . . . . . . 24Table 3 Required software by network elements . . . . . . . . . . . . . . . . . . . . . . . . 24Table 4 Required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Table 5 Impact of GPRS on BSC units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Table 6 Counters of Packet Control Unit Measurement related to GPRS . . . . . 41Table 7 Counters of RLC Blocks per TRX Measurement . . . . . . . . . . . . . . . . . 42Table 8 Counters of Frame Relay Measurement . . . . . . . . . . . . . . . . . . . . . . . . 42Table 9 Counters of Coding Scheme Measurement . . . . . . . . . . . . . . . . . . . . . 44Table 10 Counters of Quality of Service Measurement related to GPRS . . . . . . 45Table 11 Counters of GPRS RX Level and Quality Measurement . . . . . . . . . . . 45Table 12 Counters of PCU Utilization Measurement . . . . . . . . . . . . . . . . . . . . . . 46Table 13 Required additional or alternative hardware or firmware. . . . . . . . . . . . 55Table 14 Required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Table 15 Impact of Extended Uplink TBF Mode on BSC units . . . . . . . . . . . . . . 56Table 16 Counters of 72 Packet Control Unit Measurement . . . . . . . . . . . . . . . . 57Table 17 Required additional or alternative hardware or firmware . . . . . . . . . . . 59Table 18 Required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Table 19 Impact of Priority Class based Quality of Service on BSC units . . . . . . 60Table 20 Radio network parameters for Priority Based Scheduling . . . . . . . . . . 61Table 21 Counters of Quality of Service Measurement . . . . . . . . . . . . . . . . . . . . 62Table 22 Required additional or alternative hardware or firmware . . . . . . . . . . . 64Table 23 Required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Table 24 Impact of System Level Trace on BSC units . . . . . . . . . . . . . . . . . . . . 65Table 25 Counters of TBF Observation for GPRS Trace . . . . . . . . . . . . . . . . . . . 65Table 26 Counters of GPRS Cell Re-Selection Report . . . . . . . . . . . . . . . . . . . . 67Table 27 Counters of GPRS RX Level and Quality Report . . . . . . . . . . . . . . . . . 68Table 28 CS and MCS codecs in the initial coding scheme and new MCS fields 69Table 29 Nokia Siemens Networks GSM/EDGE PCU product family . . . . . . . . . 71Table 30 PCUs in BSC product variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Table 31 PCU maximum connectivity per logical PCU . . . . . . . . . . . . . . . . . . . . 72Table 32 NS-VC operational states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Table 33 NS-VC reset cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Table 34 BVC operational states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Table 35 BVC blocking cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Table 36 BVC reset cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Table 37 Defining the margin of idle TCH/Fs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Table 38 Defining the margin of idle TCHs, % . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Table 39 GMSK Mean BEP Limit for UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Table 40 RX Quality Limit for UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Table 41 Supported Network Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . 113

8 DN7036138



DN7036138 9

BSS09006: GPRS System Feature Description Summary of changes

Id:0900d8058089e64fConfidential

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

Changes made between issues 4-2 and 4-1Section Additional GPRS territory downgrade under chapter Radio resource manage-ment is updated.

Changes made between issues 4-1 and 4-0Section Interworking with other features under chapter System impact of GPRS is updated.

Changes made between issues 4-0 and 3-2Information on Packet Abis feature updated throughout the document.

Changes made between issues 3-2 and 3-1Information on Flexi Multiradio and BTSplus support have been added.

Information regarding the feature BSS21238 Merged P-&E-GSM900 has been updated in section Interworking with other features in the chapter System impact of GPRS.

10 DN7036138


Id:0900d8058078e154Confidential

GPRS

1 GPRSGeneral Packet Radio Service (GPRS) provides packet data radio access for GSM mobile phones. It upgrades GSM data services to allow an interface with Local Area Networks (LANs), Wide Area Networks (WANs) and the Internet.GPRS makes the radio interface usage more efficient:

GPRS enables a fast method for reserving radio channels GPRS uses the same resources with circuit switched connection by sharing the

overhead capacity GPRS provides immediate connectivity and high throughput.On a general level, GPRS connections use the resources only for a short period of time when sending or receiving data:

in a circuit-switched system, the line is occupied even when no data is transferred in a packet-switched system, the resources are released so they can be used by

other subscribers.

GPRS is therefore well adapted to the bursty nature of data applications. GPRS has minimal effects on the handling of circuit switched calls, but the interoperability of existing circuit switched functionalities needs to be taken into account.

GPRS uses statistical multiplexing instead of static time division multiplexing: when the user is ready to receive new data, the terminal sends a request, and resources are again reserved only for the duration of transmitting the request and initiating a second data transfer. The data to be transferred is encapsulated into short packets with a header containing the originating and destination address. No pre-set time slots are used. Instead, network capacity is allocated when needed and released when not needed.

GPRS offers a very flexible range of bitrates, from less than 100 bit/s to over 100 kbit/s. Applications that need less than one time slot benefit from GPRS's ability to share one time slot among several users. Moreover, the high bitrates that GPRS provides by using multiple time slots give short response times, even if a lot of data is transmitted.

The main functions of the BSC with GPRS are to:

manage GPRS-specific radio network configuration control access to GPRS radio resources share radio resources between GPRS and circuit switched use handle signalling between the MS, BTS and Serving GPRS Support Node (SGSN) transfer GPRS data.BSC operational software includes support for GPRS coding schemes CS-1 and CS-2. Support for coding schemes CS-3 and CS-4 is an application software product that requires PCU2 and, Dynamic Abis or Packet Abis.

GPRS is licence key controlled. For more information, see Licence Management in BSC.

Benefits of GPRSGPRS offers the following additional benefits for the operators/end users:

resources are used more efficiently, thus there is less idle time circuit switched traffic is prioritised, but quality is guaranteed by reserving time slots

for GPRS traffic only new services, application, and businesses for the operators

DN7036138 11

BSS09006: GPRS System Feature Description GPRS


fast connection set-up for end users high bit rate in data bursts possibility of being charged only for transferred data generally, any service that can be run on top of IP protocols (the UDP or TCP trans-

fer) is supported by the Nokia Siemens Networks GPRS solution (taking into account data rate and delay requirements).

An investment in the GPRS infrastructure is an investment in future services. GPRS paves the way and is already part of the third generation (3G) network infrastructure. Migration to 3G comprises deployment of the new WCDMA radio interface served by the GSM and GPRS core networks. Many of the 3G services are based on IP, and the GPRS Core network is the key step of introducing the IP service platform into the present GSM networks.

When migrating to 3G services, preserving the Core Network investments is a top prior-ity. Introducing UMTS will complement the GSM network not replace it.

Required network changesNokia Siemens Networks offers a total end-to-end General Packet Radio Service (GPRS) solution including the GPRS core, network management, and charging gateway with high capacity, scalability, and carrier class availability. As a part of the GPRS solu-tion, the Nokia Siemens Networks BSS offers GPRS support in the BSS with powerful radio resource management algorithms, optimised BSS network topology, and trans-mission solutions to ensure an optimal investment to operators and high capacity and quality service for end users.

While the current GSM system was originally designed with an emphasis on voice ses-sions, the main objective of the GPRS is to offer access to standard data networks such as LAN using the TCP/IP protocol. These networks consider the GPRS to be a normal subnetwork, as seen in the figure below. A gateway in the GPRS network acts as a router and hides GPRS-specific features from the external data network. WAP (Wireless Application Protocol) based services see the GPRS as one carrier (UDP). Wireless Markup Language (WML) based services in the GPRS can be accessed using the standard WAP gateways. The WAP is essential in creating applications that are 'use-able' in the mobile environment (for example, small screen display, low data rates).

12 DN7036138



GPRS

Figure 1 GPRS network seen by another data network

GPRS is the first GSM Phase 2+ service that requires major changes in the network infrastructure. In addition to the current GSM entities, GPRS is based on a number of new network elements:

Serving GPRS Support Nodes (SGSN) GPRS backbone Legal Interception Gateway (LIG).

Figure 2 GPRS architecture

Along with the new network elements, the following functions are needed:

GPRS-specific mobility management Network management capable of handling the GPRS-specific elements A new radio interface for packet traffic

DN7036138 13



New security features for the GPRS backbone and a new ciphering algorithm New MAP and GPRS-specific signalling.Related topics in GPRS System Feature Description

Extended Uplink TBF Mode GPRS Coding Schemes Link Adaptation for GPRS Priority Class Based Quality of Service (QoS) System Level Trace System impact of GPRS System impact of Extended Uplink TBF Mode System impact of Priority Class based Quality of Service System impact of System Level Trace Requirements for GPRS Radio network management for GPRS Gb interface configuration and state management Radio resource management GPRS radio connection control Implementing GPRS overviewOther related topicsDescriptions

BSS21228: Downlink Dual Carrier BSS20088: Dual Transfer Mode BSS10045: Dynamic Abis BSS20094: Extended Cell for GPRS/EDGE BSS20089: Extended Dynamic Allocation BSS10103: Gb over IP BSS20084: High Multislot Classes BSS20394: Inter-System Network-Controlled Cell Re-selection BSS20086: Multipoint Gb Interface BSS115006: Network-Assisted Cell Change BSS11112: Network-Controlled Cell Re-selection BSS20106: Packet Control Unit (PCU2) Pooling BSS21440: Packet Abis over TDM BSS21454: Packet Abis over Ethernet BSS21443: Packet TRS for UltraSite/BTSplus BSS30395: Packet Abis Delay Measurement BSS21503: FlexiPacket Radio Connectivity BSS20083: Inter-BSC NACC BSS21045: Inter System NACC BSS21355: Inter System NACC for LTEInstructions

Activating and testing BSS9006: GPRSReference

14 DN7036138



GPRS

EA - Adjacent Cell Handling EE - Base Station Controller Parameter Handling in BSC EG - GSM Timer and BSC Parameter Handling EQ - Base Transceiver Station Handling in BSC ER - Transceiver Handling ES - Abis Interface Configuration EU - Power Control Parameter Handling FX - Gb Interface Handling PCU2 Service Terminal Commands 25 TBF Observation for GPRS Trace 27 GPRS Cell Re-selection Report 28 GPRS RX Level and Quality Report 72 Packet Control Unit Measurement 73 RLC Blocks per TRX Measurement 74 Frame Relay Measurement 76 Dynamic Abis Measurement 79 Coding Scheme Measurement 90 Quality of Service Measurement 95 GPRS Cell Re-selection Measurement 96 GPRS RX Level and Quality Measurement 98 Gb Over IP Measurement 105 PS DTM Measurement 106 CS DTM Measurement 110 PCU Utilisation Measurement 123 Packet Abis BTS measurement 124 Packet Abis Traffic measurement 125 Packet Abis SCTP measurement 126 Packet Abis Delay measurement 127 Packet Abis Congestion Control measurement BSS Radio Network Parameter Dictionary PAFILE Timer and Parameter List PRFILE and FIFILE Parameter List

DN7036138 15



1.1 GPRS data transfer protocols

Figure 3 Transmission plane

The GSM RF is the normal GSM physical radio layer. The Radio Link Control (RLC) function offers a reliable radio link to the upper layers. The Medium Access Control (MAC) function handles the channel allocation and the multiplexing, that is, the use of physical layer functions. The RLC and the MAC together form the OSI Layer 2 protocol for the Um interface. The Logical Link Control (LLC) layer offers a secure and reliable logical link between the MS and the SGSN to upper layers and is independent of the lower layers. The LLC layer has two transfer modes, the acknowledged and unacknowl-edged. The LLC conveys signalling, SMS, and SNDCP packets. The Subnetwork Dependent Convergence Protocol (SNDCP) is a mapping and compression function between the network layer and lower layers. It also performs segmentation, re-assem-bly, and multiplexing.

The Base Station System GPRS Protocol (BSSGP) transfers control information and data between a BSS and an SGSN. The Network Services relays the BSSGP packets over the Gb interface and has load sharing and redundancy on top of Frame Relay. The L1bis is a vendor-dependent OSI Layer 1 protocol. The Relay function relays LLC PDUs (Protocol Data Units) between the LLC and BSSGP.

The Packet Control Unit is responsible for the following GPRS MAC and RLC layer func-tions as defined in 3GPP TS 43.064:

LLC layer PDU segmentation into RLC blocks for downlink transmission LLC layer PDU re-assembly from RLC blocks for uplink transmission PDCH scheduling functions for the uplink and downlink data transfers PDCH uplink ARQ functions, including RLC block ack/nack PDCH downlink ARQ function, including buffering and retransmission of RLC blocks Channel access control functions, for example, access requests and grants Radio channel management functions, for example, power control, congestion

control, broadcast control information, etc. The Channel Codec Unit (CCU) takes care of the channel coding functions,

including FEC and interleaving Radio channel measurement functions, including received quality level, received

signal level, and information related to timing advance measurements.

For more information on the PCU, see Packet Control Unit (PCU).

16 DN7036138



GPRS

The Network Protocol Data Units (N-PDU) are segmented into the Subnetwork Protocol Data Units (SN-PDU) by the Subnetwork Dependent Convergence (SNDC) protocol, and SN-PDUs are encapsulated into one or several LLC frames. LLC frames are of variable length. The maximum size of the LLC frame is 1600 octets minus GP protocol control information. See 3GPP TS 23.060 for information on SNDC and LLC. The details on SNDC can be found in 3GPP TS 44.065 and the details on LLC in 3GPP TS 44.064. LLC frames are segmented into RLC Data Blocks. In the RLC/MAC layer, a selective ARQ protocol (including block numbering) between the MS and the network provides retransmission of erroneous RLC Data Blocks. When a complete LLC frame is success-fully transferred across the RLC layer, it is forwarded to the LLC layer.

Figure 4 Transmission and reception data flow

1.2 Optimised GPRS Radio Resource ManagementThe Nokia Siemens Networks BSS offers dynamic algorithms and parameters to optimise the use of radio resources. A dynamic and flexible GPRS radio resource man-agement is important in effective usage of the Air interface capacity to ensure maximum and secure data throughput. The limited radio resources must be used effectively.

The figure below introduces the dedicated GPRS DCH channels:

DN7036138 17



Figure 5 GPRS DCH dedicated channels

GPRS packets are sent uni-directionally; uplink and downlink are separate resources. An MS can also have a bi-directional connection while using GPRS, by having simulta-neous uplink and downlink packet transfers. A Temporary Block Flow (TBF) is made for every new data flow. One or more packet data traffic channels (PDTCHs) are allocated for the TBF. The TBF is used to send RLC/MAC blocks carrying one or more LLC PCUs. The TBF reservations of PDTCHs are released when all the RLC/MAC blocks have been sent successfully.

Basically all TBFs have the same priority, that is, all users and all applications get the same service level. The needs of different applications differ and mechanisms to have separate service levels are required. ETSI specifications define QoS functionality which gives the possibility to differentiate TBFs by delay, throughput and priority. Priority Based Scheduling is introduced as a first step towards QoS. With Priority Based Sched-uling the operator can give users different priorities so that higher priority users will get better service than lower priority users. There will be no extra blocking to any user, only the experienced service quality changes.

Packet Associated Control Channel (PACCH) conveys signalling information related to a given MS. The PACCH is a bi-directional channel and is located in the PDCH. It trans-mits signalling in both directions although data is transmitted (PDTCH) only in the assigned direction.

Multiple mobile stations (MSs) can share one PDTCH, but the PDTCH is dedicated to one MS (TBF) at a time. This means that the PDTCH is reserved for multiple TBFs, but one TBF is receiving or sending at a time. All the GPRS TBFs allocated to a PDTCH are served equally or based on the Priority Based Scheduling feature described in section 2.4. The number of TSLs allocated for a multislot MS is determined by the mobile's mul-tislot capability and network resources. Reallocations are done when the transfer mode is changed between uni-directional (only uplink or downlink data transfer) and bi-direc-tional (simultaneous uplink and downlink data transfer).

All the full rate or dual rate traffic channels are GPRS capable. With the GPRS solution, the operator can define dynamically multiple parameters related to network configura-tion, such as:

GPRS capacity cell by cell and TRX by TRX GPRS only traffic channels (Dedicated GPRS capacity)

18 DN7036138



GPRS

Default amount of GPRS capable traffic channels (Default GPRS capacity) and Whether BCCH TRX or non-BCCH TRX is preferred for GPRS.The adjustable parameters help the network planners to control and optimise GPRS radio resources.

Figure 6 Example of a GPRS capable cell

The BSS is upgraded with enhanced RLC/MAC protocols and TRAU for the radio and Abis interfaces. Circuit Switched (CS) traffic has priority over Packet Switched (PS) traffic. In a CS congestion situation, the CS may use the Default GPRS traffic channels, but Dedicated GPRS traffic channels are reserved to carry PS traffic.

The default GPRS capacity determines the number of traffic channels (TCHs), which are always switched to the PCU when allowed by CS traffic load. With these TCHs, the operator can supply the need for fast GPRS channel reservations for the first data packets. During peak GPRS traffic periods, additional channels are switched to GPRS use, if the CS traffic load allows it.

Figure 7 Air interface traffic management

Dedicated, default, and additional GPRS TCHs form a GPRS pool consisting of consec-utive radio interface timeslots. When the GPRS pool is upgraded, intra-cell handovers of CS connections may be needed to allow for the selection of consecutive timeslots for GPRS use. New CS connections may be allocated to a TCH in the GPRS pool only when all the TCHs not belonging to the GPRS pool are occupied.

IUO super reuse frequencies are not used for GPRS traffic, but the feature itself can be used to release resources for GPRS usage. In cells where Base Band Frequency Hopping is in use, TSL 0 is not used for GPRS traffic.

TRX 1

TRX 2

BCCH

DefaultGPRS Capacity

DedicatedGPRS

Capacity

AdditionalGPRS

Capacity

Territory border moves based onCircuit Switched and GPRS traffic load

GPRSTerritory

CircuitSwitchedTerritory

MaxGPRS

Capacity

DN7036138 19



When Extended Cell for GPRS/EDGE application software is used, the Extended Cell GPRS channels (EGTCH) in Extended TRX (E-TRX) are reserved only for fixed GPRS traffic and dynamic GPRS radio resource management is not used for them at all. For more information, see Extended Cell for GPRS/EDGE.

1.3 Frame Relay and Gb InterfaceGb is the interface between a BSC and an SGSN. It is implemented using either Frame Relay or IP. For more information on Gb over IP, see Gb over IP. Frame Relay can be either point-to-point (PCUSGSN), or there can be a Frame Relay network located between the BSC and SGSN. The protocol stack comprises BSSGB, NS, and L1. Frame Relay as stated in standards is a part of the Network Service (NS) layer. On top of the physical layer in the Gb-interface, the direct point-to-point Frame Relay connections or intermediate Frame Relay network can be used. The physical layer is implemented as one or several PCM-E1 lines with G.703 interface. The FR network will be comprised of third-party off-the-shelf products. The following figure displays examples of Gb interface transmission solutions:

Figure 8 BSC - SGSN interface

In the first solution (1) spare capacity of Ater and A interfaces is used for the Gb. The Gb timeslots are transparently through connected in the TCSM and in the MSC. If free capacity exists, it is best to multiplex all Gb traffic to the same physical link to achieve possible transmission savings. In many cases, the SGSN will be located in the MSC site, and thus the multiplexing has to take place there as well. Normal cross-connect equip-ment, for example, Nokia Siemens Networks DN2 can be used for that purpose.

The second solution (2) represents any transmission network that provides a point-to-point connection between the BSC and the SGSN. In the third solution (3) Frame Relay network is used. The Gb interface allows the exchange of signalling information and user data. The Gb interface allows many users to be multiplexed over the same physical resources.

At least one timeslot of 64 kbps is needed for each activated PCU bearer. One PCU1 can handle a maximum of 64 BTSs and 128 TRXs. One PCU2-D/PCU2-U can handle a maximum of 128 BTSs and 256 TRXs. One PCU2-E can handle a maximum of 384

20 DN7036138



GPRS

BTSs and 1024 TRXs. This capacity cannot be shared with other cells connected to other PCUs in the BSC so there is no pooling. The PCU has to be installed into every BCSU for redundancy reasons, but the FR bearer has to be connected only to the active ones. Considering the transmission protection, it also needs to be decided whether two Frame Relay bearers are needed for each PCU using different ETs (external 2Ms) or if the transmission is protected with cross connection equipment.

It is possible to multiplex more than one Gb interface directly to the SGSN, or multiplex them on the A interface towards the MSC and cross-connect them to the SGSN from there. The 2M carrying the Gb timeslots can be one of the BSC's existing ETs, or an ET can be dedicated to the Gb interface.

The Gb interface allows the exchange of signalling information and user data. It also allows many users to be multiplexed over the same physical resources. The logical structure of the point-to-point Gb interface is presented in the following figure:

Figure 9 Gb logical structure

In the BSC, each PCU represents one Network Service Entity with own Identifier (NSEI). Each PCU can have one to four (ffs) FR bearer channels. The Access Rate of a FR Bearer Channel can be configured in 64kbit steps. Each Bearer channel carries one to four Network Service Virtual Connections (NS-VC). Each BTS has a BSSGP Virtual Connection of its own. The NSE takes care of the multiplexing of BSSGP Virtual Con-nections into the NS Virtual Connections and load sharing between the different NS Virtual Connections (= Bearer Channels).

The following figure displays the Gb protocol layers:

Figure 10 Gb interface

DN7036138 21



1.4 GPRS in Nokia Siemens Networks Base StationsRadio resources are allocated by the BSC (PCU). The BCCH/CCCH is scheduled by the BTS; messages are routed via TRXSIG link between the BTS and BSC. GPRS data itself is transparent to the BTS; routed via TCH channels in Abis.

The CCU (Channel Coding Unit) in the BTS DSP performs channel coding for the fol-lowing rates:

CS-1 (Channel Coding Scheme 1) - 9.05 kbps CS-2 (Channel Coding Scheme 2) - 13.4 kbps CS-3 (Channel Coding Scheme 3) - 15.6 kbps CS-4 (Channel Coding Scheme 4) - 21.4 kbps In Packet Transfer Mode, the MS will use the continuous timing advance update proce-dure. The procedure is carried out on all PDCH timeslots. The mapping in time of these logical channels is defined by a multi-frame structure. It consists of 52 TDMA frames, divided into 12 blocks (of four frames) and four idle frames.

22 DN7036138


Id:0900d8058077eaf4Confidential

Software related to GPRS

2 Software related to GPRS

2.1 Extended Uplink TBF ModeWith Extended Uplink TBF Mode the uplink TBF may be maintained during temporary inactive periods, where the mobile station has no data to send. Without Extended Uplink TBF Mode a new uplink TBF has to be established after every inactive period.

When both the MS and the network support Extended Uplink TBF Mode, the release of the uplink TBF can be delayed even if the MS occasionally has nothing to transmit. Right after the MS has new data to send, the same uplink TBF can be used and data trans-mission can be reactivated.

Extended Uplink TBF Mode requires 3GPP Rel. 4 GERAN feature package 1 mobile stations.

Benefits of the Nokia Siemens Networks solution

With Extended UL TBF Mode the UL TBF release can be delayed in order to make it possible to establish the following downlink TBF using Packet Associated Control Channel (PACCH). Using PACCH enables faster TBF establishment compared to using CCCH.

Extended UL TBF Mode allows the mobile station to continue the data transfer if it gets more data to send when the countdown procedure has begun. Without Extended UL TBF Mode, the release of the current TBF is required and a new one is established, causing more delay and signalling load.

Extended UL TBF Mode is effective in preventing the breaks in data transfer. Occa-sional short breaks in data transmission do not delay the activation of a new Uplink TBF, which increases the perceived service quality by the end user, for example, in speech delivery in PoC.

Extended UL TBF Mode saves capacity, because it decreases the number of random access procedures during and after an active stream, when a TBF is needed for the other direction.

Related topics

Activating and Testing BSS11151: Extended Uplink TBF Mode

DN7036138 23


Id:0900d8058077eadbConfidential

2.2 GPRS Coding SchemesGPRS provides four coding schemes, from CS-1 to CS-4, offering data rates from 9.05 to 21.4 kbit/s per channel. By using PCU1 and 16 kbit/s Abis links, it is possible to support CS-1 and CS-2.

Coding schemes CS-1-CS-4 can be used in unacknowledged RLC mode with PCU2. With PCU-1, coding scheme CS-1 is always used in unacknowledged RLC mode.

In acknowledged mode, RLC data blocks are acknowledged, and both CS-1 and CS-2 are supported. Each TBF can use either a fixed coding scheme (CS-1 or CS-2), or Link Adaptation (LA). The link adaptation algorithm is based on the RLC BLER (Block Error Rate). Retransmitted RLC data blocks must be sent with the same coding as was used initially.

Coding Schemes CS-3 and CS-4Before the introduction of Abis transportation bandwidth saving features like Dynamic Abis and Packet Abis, only CS-1 and CS-2 GPRS coding schemes were supported because of Abis frame restrictions. Support for GPRS coding schemes CS-3 and CS-4 requires PCU2 and either Dynamic Abis or Packet Abis.

CS1 and CS2 offer data rates of 8.0 and 12.0 kbps per timeslot. With the rates of 14.4 and 20.0 kbps, CS-3 and CS-4 provide a considerable gain in data rates for GPRS mobile stations not supporting EGPRS (the mandatory RLC header octets are excluded from the data rate values).

CS-3 and CS-4 can boost GPRS throughput bit rates by a maximum of 60% compared to CS-1 & CS-2. With average real network conditions (average C/I value distribution) a throughput increase of 0-30% can be achieved depending on the networks C/I values.

Coding Schemes CS-3 and CS-4 can be used in both GPRS and EGPRS territories. For hardware requirements, see section Requirements.

RequirementsThe hardware and software requirements of Coding Schemes CS-3 and CS-4 are spec-ified in the tables below.

Coding Schemes CS-3 and CS-4 are an application software product and require a valid licence in the BSC. All GPRS-capable mobile stations support CS-3 and CS-4.

Coding Scheme Coding Rate (kbps)

Payload (bits) per RLC

block(RLC header bits excluded)

Payload rate (kbps)

CS1 9.05 160 8.0

CS2 13.4 240 12.0

CS3 15.6 288 14.4

CS4 21.4 400 20.0

Table 1 GPRS Coding Schemes

24 DN7036138



User interfaceBTS MMI

Coding Schemes CS-3 and CS-4 cannot be managed with BTS MMI.

BSC MMI

The following MML commands are used to handle Coding Schemes CS-3 and CS-4:

Base Transceiver Station Handling in BSC: EQV, EQOBSC radio network object parameters

The following parameters are introduced due to Coding Schemes CS-3 and CS-4:

coding schemes CS3 and CS4 enabled (CS34) DL coding scheme in acknowledged mode (DCSA) UL coding scheme in acknowledged mode (UCSA) DL coding scheme in unacknowledged mode (DCSU)

Network element Hardware/firmware required

BSC PCU2

ETP (required when Packet Abis feature is in use)

BTS The BaseBand hardware of the BTS must support Dynamic Abis. EDGE capable TRXs are required.

TCSM No requirements

SGSN No requirements

Table 2 Required additional or alternative hardware or firmware

Network element Software release required

BSC S15

BTSplus BTSs BRG1

Flexi Multiradio BTSs EX3.1

Flexi EDGE BTSs EX4

UltraSite EDGE BTSs CX8.0

MetroSite EDGE BTSs CXM8.0

Talk-family BTSs Not supported

MSC/HLR Not applicable

SGSN Not applicable

NetAct OSS5.2 CD Set 3

Table 3 Required software by network elements

DN7036138 25



UL coding scheme in unacknowledged mode (UCSU) adaptive LA algorithm (ALA)Due to a new Link Adaptation algorithm the following existing parameters are no longer relevant when CS-3 and CS-4 is used:

coding scheme no hop (COD) coding scheme hop (CODH)For more information on radio network parameters, see BSS Radio Network Parameter Dictionary.

PRFILE parameters

The values of the following MS-specific flow control parameters must be increased due to CS-3 and CS-4:

FC_MS_B_MAX_DEF FC_MS_R_DEF FC_R_TSL.For more information on PRFILE parameters, see PRFILE and FIFILE Parameter List.

Alarms

The following new alarm is introduced due to Coding Schemes CS-3 and CS-4:

3273 GPRS/EDGE TERRITORY FAILUREFor more information, see Diagnosis Reports (3700-3999).

Measurements and counters

Two new object values are added to the 79 Coding Scheme Measurement due to Coding Schemes CS-3 and CS-4. No new counters are needed.

Interworking with other featuresCS-3 and CS-4 do not fit into one 16kbit/s Abis/PCU channel and require the use of Dynamic Abis or Packet Abis and EDGE TRXs.

Related topics

Activating and testing BSS11088: Coding Schemes CS-3 and CS-4 79 Coding Scheme Measurement

26 DN7036138


Id:0900d805807de268Confidential

2.3 Link Adaptation for GPRSFrom BSS11.5 onwards, there are two GPRS Link Adaptation algorithms, the use of which depends on the PCU type (PCU1 or PCU2).

Although the Coding Schemes CS-3 and CS-4 are licence-based, the LA algorithm is provided with PCU2.

Link Adaptation algorithm for PCU1The GPRS Link Adaptation (LA) algorithm selects the optimum channel coding scheme (CS-1 or CS-2) for a particular RLC connection and is based on detecting the occurred RLC block errors and calculating the block error rate (BLER).

The BSC level parameters coding scheme no hop (COD) and coding scheme hop (CODH) define whether a fixed CS value (CS-1 or CS-2) is used or if the coding scheme changes dynamically according to the LA algorithm. When the LA algorithm is deployed, the initial CS value at the beginning of a TBF is CS-2.

Regardless of the parameter values, CS-1 is always used in unacknowledged RLC mode.

Link Adaptation algorithm for PCU2A new Link Adaptation algorithm is introduced with PCU2, which replaces the previous GPRS LA algorithm and covers the following coding schemes:

CS-1 and CS-2 if CS-3 and CS-4 support is disabled in the territory in question CS-1, CS-2, CS-3, and CS-4 if CS-3 and CS-4 support is enabled in the territory in

question

The following BTS-level parameters define, whether a fixed CS value (CS-1 - CS4) is used or if the coding scheme changes dynamically according to the LA algorithm. The parameters can also be used to define the initial CS value at the beginning of a TBF:

DL coding scheme in acknowledged mode (DCSA) UL coding scheme in acknowledged mode (UCSA) DL coding scheme in unacknowledged mode (DCSU) UL coding scheme in unacknowledged mode (UCSU) adaptive LA algorithm (ALA)For more information on radio network parameters, see BSS Radio Network Parameter Dictionary.

The LA algorithm measures the signal quality for each TBF in terms of the received signal quality (RXQUAL). RXQUAL is measured for each received RLC block, which makes it a more accurate estimate than BLER.

If the adaptive LA algorithm is enabled, then the PCU determines the average BLER value separately for each RXQUAL and CS combination by continuously collecting sta-tistics from all the connections in the territory in question. Based on the estimates, the LA algorithm determines which coding scheme will give the best performance. If the adaptive LA algorithm is disabled, then the statistics is not collected but the initial values in the LA tables are used when the LA algorithm selects the optimal CS.

The new LA algorithm can be used in both RLC acknowledged and unacknowledged modes in both uplink and downlink direction.

DN7036138 27


Id:0900d80580590b3eConfidential

2.4 Priority Class Based Quality of Service (QoS)With Priority Based Scheduling, an operator can give users different priorities. Higher priority users will get better service than lower priority users. There will be no extra blocking to any user, only the experienced service quality changes.

The concept of Priority Class is based on a combination of the GPRS Delay class and GPRS Precedence class values. Packets will be evenly scattered within the (E)GPRS territory between different time slots. After that packets with a higher priority are sent before packets that have a lower priority.

Mobile-specific flow control is part of the QoS solution in the PCU. It works together with the SGSN to provide a steady data flow to the mobile from the network. It is also an effective countermeasure against buffer overflows in the PCU. Mobile-specific flow control is performed for every MS that has a downlink TBF. There is no uplink flow control.

The PCU receives the QoS (Precedence class) information to be used in DL TBFs from the SGSN in a DL unitdata PDU.

In case of UL TBF, the MS informs its radio priority in a PACKET CHANNEL REQUEST (PCR) or a PACKET RESOURCE REQUEST (PRR), and this is used for UL QoS. Exceptions to this rule are one phase access and single block requests; in these cases the PCU always uses Best Effort priority.

Priority Class Based Quality of service is an operating software in the BSC and is always active in an active PCU. The subscriber priority must be defined in the HLR once Priority Class Based QoS is taken into use.

Priority based scheduling algorithmThe description below covers the PCU1 implementation; PCU2 implementation emulates this operation closely.

The priority based scheduling algorithm hands out radio resources according to the latest service time and scheduling step size of the TBFs. Each TBF allocated to a timeslot has a timeslot-specific latest service time, before which the TBF should get a chance to use the radio resource. In each scheduling round, the TBF with the lowest service time is selected. After the TBF has sent a radio block, its latest service time is incremented by a predefined scheduling step size. The higher the scheduling step size, the less often the TBF is selected and given a transmission turn.

In BSS9 (GPRS Release 1) the scheduling steps of all TBFs are set to the same constant value. In the BSS10.5 release the step sizes depend on the priority class of the TBF: each priority class has its own scheduling step size that can be adjusted by the operator. There are 4 QoS classes for uplink and 3 QoS classes for downlink. Each service class is given a fair amount of radio time. The best effort customers are an exception to the rule and are only given a small share of the radio interface.

The allocation process is designed to ensure that better priority TBFs are not gathered into the same radio timeslot. TBFs in the same time slot that have the same QoS get an equal share of air time. However, equal air time does not provide equal data rates for the TBFs in the same time slot, it only guarantees that inside a QoS group the air time is divided equally and that a higher QoS class gets more air time.

28 DN7036138


Id:0900d80580590b3eConfidential

Figure 11 Example of transmission turns

DN7036138 29


Id:0900d805807de9a7Confidential

2.5 System Level TraceSystem Level Trace is an operating software, which extends the current GSM tracing to the GPRS service. GSM tracing is available in the network elements of the GSM network to trace circuit switched calls.

System Level Trace enables customer administration and network management to trace activities of various entities (IMSIs and IMEIs), which result in events occurring in the PLMN. The trace facility is a useful maintenance aid and development tool, which can be used during system testing. In particular, it may be used in conjunction with test-MSs to ascertain the digital cell 'footprint', the network integrity, and also the network quality of service as perceived by the PLMN. The network management can use the facility, for example, in connection with a customer complaint, a suspected equipment malfunction or if authorities request for a subscriber trace for example in an emergency situation.

The ETSI specifies the tracing facility for GSM, where it refers both to subscriber tracing (activated using IMSI) and equipment tracing (activated using IMEI). The subscriber tracing can be defined for a certain subscriber in the HLR or in a specific SGSN. Equip-ment tracing can be defined in the SGSN.

Figure 12 Trace activation/deactivation and report generation

The trace is already implemented in the GSM network, but introduction of GPRS-service adds new network elements to the GSM network (GGSN, SGSN) and changes old prin-ciples. Therefore, new tracing facilities are needed.

In order to get full advantage of System Level Trace, it must be implemented in all main network elements of the GPRS network: the SGSN, GGSN, BSC, MSC/HLR, and OSS. The figure GPRS network and related network elements presents the overall picture of GPRS trace and shows all the network elements that can send trace reports to NetAct. GPRS trace is activated by OSS. The HLR, SGSN, GGSN, and BSS send trace records to OSS when an invoking event occurs.

30 DN7036138



Figure 13 Architecture of the GPRS network and related network elements

Trace from an operator's viewpointIn the SGSN trace, three different scenarios can be identified from an operator's point of view:

HPLMN operator traces its own IMSI within the HPLMNWhen an operator wishes to trace a GPRS subscriber in its own (home) network, the trace is first activated in the HLR. If a subscriber is not roaming outside the HPLMN and he/she is represented as a register in the HLR, the HLR activates the trace in a specified SGSN. Otherwise, the HLR waits until the subscriber becomes active in HPLMN before it activates a trace in the SGSN.

HPLMN operator tracing a foreign roaming subscriber (IMSI) within its own HPLMNWhen an operator wants to trace a foreign subscriber, the trace is activated directly via MMI commands to all SGSNs in an operator's network. The trace of a subscriber is in a state of active pending until an invoking event occurs. The amount of active trace cases can be limited.

HPLMN operator tracing equipment (IMEI).When an operator wants to trace equipment, the trace is activated directly via MMI commands to all SGSNs in operator's network. The trace of equipment is in a state of active pending until an invoking event occurs. The amount of active trace cases can be limited.

The tracing of roaming IMSIs and the exchange of data is subject to bilateral agree-ments, and the request to trace a particular IMSI comes through administrative chan-nels. The HPLMN operator can use the HLR parameters to define whether the trace settings are sent to the VPLMN.

System Level Trace in BSCThe SGSN invokes the trace by sending a BSSGP SGSN-INVOKE-TRACE (3GPP TS 48.018) message to the BSS when SGSN trace becomes active or when SGSN receives a trace request. When the BSC receives this message it starts tracing. The BSS does not send an acknowledgement of the BSSGP message to the SGSN. In case of a handover between BSCs, the tracing is deactivated in the source BSC side and acti-vated in the target BSC side by an SGSN-INVOKE-TRACE message from SGSN.

DN7036138 31



The System Level Trace for GPRS in the BSC is implemented as three different obser-vation types:

TBF Observation for GPRS Trace GPRS Cell Re-Selection Report GPRS RX Level and Quality ReportThese observations cannot, however, be started or stopped by MML commands or from the NMS. The trace as a whole is handled only by the SGSN-INVOKE-TRACE messages from the SGSN. If you attempt to start these observations (without trace) from NetAct, the BSC replies with an error status.

The BSC sends the generated trace reports to NetAct. Trace reports are also stored in observation files on the BSC's disk.

TBF Observation for GPRS Trace

A TBF report is created when a subscriber performs actions causing an allocation of TBF in BSS during tracing. There is one report per each allocated TBF, so simultaneous TBF allocations produce multiple reports. TBF release completes the report, which is then ready for post-processing.

During TBF allocation, TBF Observation for GPRS Trace records resource consumption by the user and call quality related transactions. In addition to TBF allocation and release, recorded events include TBF reallocations, MCS changes and MS Flow Control changes.

For further information, see 25 TBF Observation for GPRS Trace.

GPRS Cell Re-selection Report

GPRS Cell Re-selection is a trace report for GPRS trace. It contains information about NCCR triggering, NACC usage and possible failures.

The report is closed and sent further to NetAct when flush is received from the SGSN, the MS returns to source cell by Packet Cell Change failure, or NCCR context is released in the PCU.

For further information, see 27 GPRS Cell Re-selection Report.

GPRS RX Level and Quality Report

GPRS RX Level and Quality Report is a report type needed to periodically record serving and neighbour cell measurements and quality data. The report contains the fol-lowing information:

downlink RX level of serving cell and neighbour cells from packet (enhanced) mea-surement report

downlink RX quality class or BEP values from (EGPRS) PACKET DOWNLINK ACKNOWLEDGEMENT message

uplink RX level and quality from BTS measurements.For further information, see 28 GPRS RX Level and Quality Report.

32 DN7036138


Id:0900d8058080d196Confidential

System impact of GPRS

3 System impact of GPRSThe system impact of BSS09006: GPRS is specified in the sections below. For an over-view, see GPRS.

For implementation instructions, see Implementing GPRS overview.

GPRS is licence key controlled.

3.1 RequirementsThe following network elements and functions are required to implement GPRS:

Serving GPRS Support Nodes (SGSN) Gateway GPRS Support Nodes (GGSN) GPRS backbone Point-to-multipoint Service Centre (PTM SC) Lawful Interception Gateway (LIG) Charging Gateway (CG) Gb interface between the BSC and SGSN Packet Control Unit (PCU) A new plug-in unit Exchange Terminal for Packet transport (ETP) is required when

Packet Abis feature is in use. GPRS-specific mobility management, where the location of the MS is handled sep-

arately by the SGSN and by the MSC/VLR even if some cooperation exists the network management must be capable of handling the GPRS-specific elements new security features for the GPRS backbone a new ciphering algorithm a new radio interface (Um) for packet data traffic new MAP and GPRS-specific signalling. Additionally, coding schemes CS-3 & CS-4 require EDGE-capable TRXs (EDGE

hardware and attached to EDAP). If Packet Abis is used, EDAP configuration is pro-hibited.

For the full use of GPRS all these need to be taken into consideration. The radio inter-face and GPRS signalling are relevant to the functioning of the BSC.

Software requirements


BSC S15

BTSplus BTSs BRG1

Flexi Multiradio BTSs EX3.1

Flexi EDGE BTSs EX4

UltraSite EDGE BTSs CX8.0

MetroSite EDGE BTSs CXM8.0

Talk-family BTSs No requirements

Table 4 Required software

DN7036138 33

BSS09006: GPRS System Feature Description System impact of GPRS


Frequency band supportThe BSC supports GPRS on the following frequency bands:

GSM 800 PGSM 900 EGSM 900 GSM 1800 GSM 1900

3.2 Restrictions If Baseband hopping is employed in a BTS, radio timeslot 0 of any TRX in the BTS

will not be used for GPRS. BTS testing cannot be executed on the packet control channel. Network operation mode III is not supported. In PCU1 Coding Scheme CS-1 is always used in unacknowledged RLC mode. In

acknowledged RLC mode, the Link Adaptation algorithm uses both CS-1 and CS-2. In PCU2, because of CS-3 & CS-4 implementation, there is a new Link Adaptation algorithm that uses all the Coding Schemes in both unacknowledged and in acknowledged RLC mode.

Paging reorganisation is not supported. When legacy Abis is used, the master and slave channels must be cross-connected

in the same way; the EDAP and the TRXs tied to it shall use a single PCM line. If they use different PCM lines, transmission delay between the lines may differ. This may cause a timing difference with the result that synchronisation between the master and slave channels is not successful. This restriction is not applicable if Packet Abis feature is in use as EDAPis prohibited to be configured with Packet Abis feature.

GPRS territory can be defined to each BTS object separately. GPRS and EGPRS territories cannot both be defined to a BTS object at the same time.

TRXs inside a BTS object must have common capabilities. An exception to this is that EDGE-capable and non-EDGE-capable TRXs can be configured to the same BTS object, if EGPRS or CS-3 & CS-4 is enabled in the BTS.In this case, GPRS must be disabled in the non-EDGE/non-CS3 & CS4-capable TRXs, and these TRXs cannot be attached to EDAP. An EDGE/CS3 & CS4-capable TRX has EDGE hardware and is added to EDAP. A non-EDGE/non-CS3 & CS4-capable TRX has no EDGE hardware or it is not added to EDAP.When Packet Abis is use, EDAP configuration is prohibited. You have to create or modify a GPRS enabled (GTRX=Y) TRX. The TRX shall be EDGE capable, that is, it has EDGE HW.

MSC/HLR M15.0

SGSN SG8

NetAct OSS5.2 CD Set 3


Table 4 Required software (Cont.)

34 DN7036138




To get BCCH recovery to work correctly, it is recommended that the operator takes the following conditions into account, when unlocked EDGE and non-EDGE-capable TRXs or unlocked CS3 & CS4 and non-CS3 & CS4-capable TRXs exist in the same EGPRS or CS-3 & CS-4 enabled BTS: If a BCCH TRX is EDGE hardware-capable, added to EDAP, and it has the

GTRX parameter set to Y, then all unlocked TRXs, which are added to EDAP, are EDGE hardware-capable, and have GTRX set to Y, should be marked Preferred BCCHs.

If a BCCH TRX is non EDGE/non-CS3 & CS4-capable, and has the parameter GTRX set to N, then all non-EDGE/non-CS3 & CS4-capable unlocked TRXs, which have GTRX set to N, should be marked Preferred BCCHs.

For information on restrictions when baseband hopping is used, see EDGE BTSs and hopping in System impact of EDGE in EDGE System Feature Description.

g Note that in legacy Abis, a TRX is an EDGE-capable TRX if the TRX has EDGE HW and it is added to the DAP. In case of Packet Abis, a TRX is considered an EDGE-capable TRX if it has only EDGE HW.

For a description on TRX creation or modification to use Packet Abis, see Creating or modifying packet abis TRX in Activating and Testing BSS10083: EGPRS.For a description of Packet Abis, see BSS21454: Packet Abis over Ethernet and BSS21440: Packet Abis over TDM.

The BSS does not restrict the use of 8PSK modulation on TSL7 of the BCCH TRX, using the highest output power. The maximum output power is 2dB lower than with GMSK. This is fully compliant with 3GPP Rel 5.

PCU1 does not support CS3 & CS4, Extended Dynamic Allocation (EDA), High Multislot Classes (HMC) or Dual Transfer Mode (DTM).

For restrictions related to Dynamic Abis, see Dynamic Abis. For restrictions related to Packet Abis, see feature description documents

BSS21440: Packet Abis over TDM OR BSS21454: Packet Abis over Ethernet.

3.3 Impact on transmissionPacket Abis feature facilitates packet switched based transmission between the BTS and the BSC. It also facilitates support for GPRS coding schemes CS-3 and CS-4 without dynamic abis configuration. DAP configuration is prohibited with Packet Abis. The feature BSS21440 Packet Abis over TDM enables the transport of Abis informa-tion using native IP over Time Division Multiplexed (TDM) networks. For more informa-tion, see BSS21440: Packet Abis over TDM. The feature BSS21454 Packet Abis over Ethernet enables the transport of Abis information using native IP over Ethernet net-works. For more information, seeBSS21454: Packet Abis over Ethernet.

3.4 Impact on BSS performanceOMU signallingNo impact.

TRX signallingNo impact.

DN7036138 35



Impact on BSC units

Impact on BTS unitsNo impact.

3.5 User interface

3.5.1 BSC MMIThe following command groups and MML commands are used to handle GPRS:

Base Station Controller Parameter Handling in BSC: EE GSM Timer and BSC Parameter Handling: EG Base Transceiver Station Handling in BSC: EQ Transceiver Handling: ER Power Control Parameter Handling: EU Gb Interface Handling: FX Licence and Feature Handling: W7 Parameter Handling: WOFor more information on the command groups and commands, see MML Commands under Reference/Commands in the PDF view.

3.5.2 BTS MMIGPRS cannot be managed with BTS MMl.

3.5.3 BSC parameters

Base Transceiver Station parameters

GPRS non BCCH layer rxlev upper limit (GPU) GPRS non BCCH layer rxlev lower limit (GPL)

BSC unit Impact

OMU No impact

MCMU No impact

BCSU No impact

PCU The PCU controls the GPRS radio resources and acts as the key unit in the following procedures:

GPRS radio resource allocation and management GPRS radio connection establishment and manage-

ment data transfer coding scheme selection PCU statistics.

TCSM No impact

Table 5 Impact of GPRS on BSC units

36 DN7036138




direct GPRS access BTS (DIRE) max GPRS capacity (CMAX) GPRS rxlev access min (GRXP) GPRS MS txpwr max CCH (GTXP1) GPRS MS txpwr max CCH 1x00 (GTXP2) priority class (PRC) HCS threshold (HCS) RA reselect hysteresis (RRH) routing area code (RAC) GPRS enabled (GENA) network service entity identifier (NSEI) default GPRS capacity (CDEF) dedicated GPRS capacity (CDED) prefer BCCH frequency GPRS (BFG) transport type (TRAT) coding schemes CS3 and CS4 enabled (CS34) BTS downlink throughput factor for CS1-CS4 (TFD) (PCU2) BTS uplink throughput factor for CS1-CS4 (TFU) (PCU2) quality control GPRS DL RLC ack throughput threshold (QGDRT) quality control GPRS UL RLC ack throughput threshold (QGURT) DL adaption probability threshold (DLA) UL adaption probability threshold (ULA) DL BLER crosspoint for CS selection no hop (DLB) UL BLER crosspoint for CS selection no hop (ULB) DL BLER crosspoint for CS selection hop (DLBH) UL BLER crosspoint for CS selection hop (ULBH) coding scheme no hop (COD) (PCU1) coding scheme hop (CODH) (PCU1) DL coding scheme in acknowledged mode (DCSA) (PCU2) UL coding scheme in acknowledged mode (UCSA) (PCU2) DL coding scheme in unacknowledged mode (DCSU) (PCU2) UL coding scheme in unacknowledged mode (UCSU) (PCU2) adaptive LA algorithm (ALA) (PCU2) EGPRS inactivity alarm weekdays (EAW) EGPRS inactivity alarm start time (EAS) EGPRS inactivity alarm end time (EAE) Adjacent Cell parameters

adjacent GPRS enabled (AGENA) HCS signal level threshold (HCS) GPRS temporary offset (GTEO) GPRS penalty time (GPET)Gb Interface Handling parameters

data link connection identifier (DLCI) committed information rate (CIR) network service virtual connection identifier (NSVCI)

DN7036138 37



network service virtual connection name (NAME) network service entity identifier (NSEI) bearer channel identifier (BCI) bearer channel name (BCN)Gb Interface Handling parameters (IP)

network service virtual link identifier (NSVLI) network service virtual connection name (NAME) network service entity identifier (NSEI) BCSU logical index (BCSU) PCU logical index (PCU) local UDP port number (LPNBR) remote IP address (RIP) remote host name (RHOST) remote UDP port number (RPNBR) preconfigured SGSN IP endpoint (PRE) remote data weight (RDW) remote signalling weight (RSW) packet service entity identifier (PSEI)Power Control Handling parameters

binary representation ALPHA (ALPHA) binary representation TAU (GAMMA) idle mode signal strength filter period (IFP) transfer mode signal strength filter period (TFP)TRX Handling parameters

GPRS enabled TRX (GTRX) dynamic abis pool ID (DAP)Base Station Controller parameters

GPRS territory update guard time (GTUGT) maximum number of DL TBF (MNDL) maximum number of UL TBF (MNUL) CS TCH allocate RTSL0 (CTR) CS TCH allocation calculation (CTC) PFC unack BLER limit for SDU error ratio 1 (UBL1) (PCU2) PFC ack BLER limit for transfer delay 1 (ABL1) (PCU2) QC NCCR action trigger threshold (QCATN) (applicable if NCCR is acti-

vated) QC reallocation action trigger threshold (QCATR) free TSL for CS downgrade (CSD) free TSL for CS upgrade (CSU) EGPRS inactivity criteria (EGIC) events per hour for EGPRS inactivity alarm (IEPH) supervision period length for EGPRS inactivity alarm (SPL) mean BEP limit MS multislot pwr prof 0 with 2 UL TSL (BL02)

38 DN7036138




mean BEP limit MS multislot pwr prof 0 with 3 UL TSL (BL03) mean BEP limit MS multislot pwr prof 0 with 4 UL TSL (BL04) mean BEP limit MS multislot pwr prof 1 with 2 UL TSL (BL12) mean BEP limit MS multislot pwr prof 1 with 3 UL TSL (BL13) mean BEP limit MS multislot pwr prof 1 with 4 UL TSL (BL14) mean BEP limit MS multislot pwr prof 2 with 3 UL TSL (BL23) mean BEP limit MS multislot pwr prof 2 with 4 UL TSL (BL24) RX quality limit MS multislot pwr prof 0 with 2 UL TSL (RL02) RX quality limit MS multislot pwr prof 0 with 3 UL TSL (RL03) RX quality limit MS multislot pwr prof 0 with 4 UL TSL (RL04) RX quality limit MS multislot pwr prof 1 with 2 UL TSL (RL12) RX quality limit MS multislot pwr prof 1 with 3 UL TSL (RL13) RX quality limit MS multislot pwr prof 1 with 4 UL TSL (RL14) RX quality limit MS multislot pwr prof 2 with 3 UL TSL (RL23) RX quality limit MS multislot pwr prof 2 with 4 UL TSL (RL24)For more information on radio network parameters, see BSS Radio Network Parameter Dictionary.

PAFILE parametersThese parameters have no Q3 interface and are stored in PAFILE, not BSDATA:

DRX TIMER MAX MSC RELEASE SGSN RELEASEFor more information on PAFILE parameters, see PAFILE Timer and Parameter List.

PRFILE parametersThe following parameters are related to Gb interface configuration and state manage-ment, the PCU, and the MAC and RLC protocols (Abis interface):

TNS_BLOCK TSNS_PROV TNS_RESET TNS_TEST TNS_ALIVE SNS_ADD_RETRIES SNS_CONFIG_RETRIES SNS_CHANGEWEIGHTS_RETRIES SNS_DELETE_RETRIES SNS_SIZE_RETRIES NS_BLOCK_RETRIES NS_UNBLOCK_RETRIES NS_ALIVE_RETRIES NS_RESET_RETRIES TGB_BLOCK TGB_RESET TGB_SUSPEND BVC_BLOCK_RETRIES

DN7036138 39



BVC_UNBLOCK_RETRIES BVC_RESET_RETRIES SUSPEND_RETRIES TGB_RESUME RESUME_RETRIES RAC_UPDATE_RETRIES TGB_RAC_UPDATE RAC_UPDATE_RETRIES FC_B_MAX_TSL FC_B_MAX_TSL_EGPRS FC_MS_B_MAX_DEF FC_MS_R_DEF FC_MS_R_MIN FC_R_DIF_TRG_LIMIT FC_R_TSL GPRS_DOWNLINK_PENALTY GPRS_DOWNLINK_THRESHOLD GPRS_UPLINK_PENALTY GPRS_UPLINK_THRESHOLD MEMORY_OUT_FLAG_SUM PRE_EMPTIVE_TRANSMISSIO TBF_LOAD_GUARD_THRSHLD TBF_SIGNAL_GRD_THRSHLD TERRIT_BALANCE_THRSHLD TERRIT_UPD_GTIME_GPRS UPLNK_RX_LEV_FRG_FACTOR DL_TBF_RELEASE_DELAY UL_TBF_RELEASE_DELAY UL_TBF_REL_DELAY_EXT UL_TBF_SCHED_RATE_EXT (PCU1) POLLING_INTERVAL (PCU2, replaces UL_TBF_SCHED_RATE_EXT) CHA_CONC_UL_FAVOR_DIR CHA_CONC_DL_FAVOR_DIR GPRS_UL_MUX_DEC_FACTOR (PCU2) BACKGROUND_ARP_1 BACKGROUND_ARP_2 BACKGROUND_ARP_3The following parameters are related to alarm 0125 PCU PROCESSOR LOAD HIGH.

PCU_LOAD_NOTIF_LIMIT SUSPEND_PCU_LOAD_NOTIFFor more information on PRFILE parameters, see PRFILE and FIFILE Parameter List.

3.5.4 AlarmsThis section lists the main GPRS-related alarms. Keep in mind that several other alarms may also be generated with the use of GPRS.

40 DN7036138




0125 PCU PROCESSOR LOAD HIGH 0136 PCU CONNECTIVITY EXCEEDED 2114 FR VIRTUAL CONNECTION FAILED 2115 FR USER LINK INTEGRITY VERIFICATION FAILED 2188 FR ACCESS DATA UPDATING FAILED 2189 COMMUNICATION FAILURE BETWEEN FR TERMINAL AND FRCMAN 3019 NETWORK SERVICE ENTITY UNAVAILABLE 3020 NETWORK SERVICE VIRTUAL CONNECTION UNAVAILABLE 3021 NETWORK SERVICE VIRTUAL CONNECTION UNBLOCK PROCEDURE

FAILED 3022 NETWORK SERVICE VIRTUAL CONNECTION BLOCK PROCEDURE

FAILED 3023 NETWORK SERVICE VIRTUAL CONNECTION RESET PROCEDURE

FAILED 3024 NETWORK SERVICE ENTITY CONFIGURATION MISMATCH 3025 NETWORK SERVICE VIRTUAL CONNECTION TEST PROCEDURE

FAILED 3026 NETWORK SERVICE VIRTUAL CONNECTION PROTOCOL ERROR 3027 UPLINK CONGESTION ON THE NETWORK SERVICE VIRTUAL CONNEC-

TION 3028 NETWORK SERVICE VIRTUAL CONNECTION IDENTIFIER UNKNOWN 3029 BSSGP VIRTUAL CONNECTION UNBLOCK PROCEDURE FAILED 3030 BSSGP VIRTUAL CONNECTION BLOCK PROCEDURE FAILED 3031 BSSGP VIRTUAL CONNECTION RESET PROCEDURE FAILED 3032 BSSGP VIRTUAL CONNECTION PROTOCOL ERROR 3033 UNKNOWN ROUTING AREA OR LOCATION AREA DURING PAGING 3068 EGPRS DYNAMIC ABIS POOL FAILURE 3073 FAULTY PCUPCM TIMESLOTS IN PCU 3164 PCU PROCESSOR OVERLOAD ALARM 3209 SUB NETWORK SERVICE SIZE PROCEDURE FAILED 3210 SUB NETWORK SERVICE CONFIGURATION PROCEDURE FAILED 3211 LAST REMOTE IP DATA ENDPOINT DELETED 3261 FAILURE IN UPDATING BSC SPECIFIC PARAMETERS TO PCU 3273 GPRS/EDGE TERRITORY FAILURE 3324 FAILURE IN UPDATING CONFIGURATION DATA TO PCU 3415 GPRS/EDGE IS VERY HIGH IN PCU OF PSE 3523 PCU2-ETP SERIAL LINK FAILURE 3524 PCU2-ETP ETHERNET LINK FAILUE 3525 ETP CONFIGURATION FAILURE 3537 ETP OVERLOAD CONDITION 3571 PROTECTING ETP CONFIGURATION FAILED 7624 CS U-PLANE CONNECTION FAILURE 7625 PS U-PLANE CONNECTION FAILURE 7724 CONFLICT BETWEEN BSS RADIO NETWORK DATABASE AND CALL

CONTROL 7725 TRAFFIC CHANNEL ACTIVATION FAILURE 7730 CONFIGURATION OF BCF FAILED

DN7036138 41



7738 BTS WITH NO TRANSACTIONS 7769 FAILURE IN UPDATING CELL SPECIFIC PARAMETERS TO PCU 7789 NO (E)GPRS TRANSACTIONS IN BTS 7798 HDLC PCM FAILURE 7799 HDLC LINK FAILUREFor more information on alarms, see Notices (0-999), Failure Printouts (2000-3999) and Base Station Alarms (7000-7999).

3.5.5 Measurements and countersThe following measurements are related to GPRS:

72 Packet Control Unit Measurement 73 RLC Blocks per TRX Measurement 74 Frame Relay Measurement 76 Dynamic Abis Measurement

For counters of 76 Dynamic Abis Measurement, see System impact of Dynamic Abis.

79 Coding Scheme Measurement 90 Quality of Service Measurement 95 GPRS Cell Re-selection Measurement

For counters of 95 GPRS Cell Re-selection Measurement, see System impact of Network Controlled Re-selection.

96 GPRS RX Level and Quality Measurement 98 Gb Over IP Measurement

For counters of 98 Gb over IP Measurement, see System impact of Gb over IP. 105 PS DTM Measurement

For counters of 105 PS DTM Measurement, see System impact of Dual Transfer Mode.

106 CS DTM Measurement For counters of 106 CS DTM Measurement, see System impact of Dual Transfer

Mode. 110 PCU Utilisation Measurement 123 Packet Abis BTS measurement 124 Packet Abis Traffic measurement 125 Packet Abis SCTP measurement 126 Packet Abis Delay measurement 127 Packet Abis Congestion Control measurement72 Packet Control Unit Measurement

Name Number

RLC DATA BLOCKS UL CS1 072062

RLC DATA BLOCKS DL CS1 072063

RLC DATA BLOCKS UL CS2 072064

Table 6 Counters of Packet Control Unit Measurement related to GPRS

42 DN7036138




For more information, see 72 Packet Control Unit Measurement.

73 RLC Blocks per TRX Measurement

For more information, see 73 RLC Blocks per TRX Measurement.

74 Frame Relay Measurement

RLC DATA BLOCKS DL CS2 072065

RETRA RLC DATA BLOCKS DL CS1 072068

RETRA RLC DATA BLOCKS DL CS2 072069

BAD FRAME IND UL CS1 072070

BAD FRAME IND UL CS2 072071

RETRA DATA BLOCKS UL CS1 072173

RETRA DATA BLOCKS UL CS2 072174

WEIGHTED DL TSL ALLOC GPRS NUMERATOR 072195

WEIGHTED DL TSL ALLOC GPRS DENOMINATOR 072196

RLC RETRANSMITTED DL CS1 DUE OTHER THAN NACK 072222

RLC RETRANSMITTED DL CS2 DUE OTHER THAN NACK 072223

DL CS1 DATA FOR DUMMY LLC 072224

IGNORED RLC DATA BLOCKS UL DUE TO BSN CS1 072225

IGNORED RLC DATA BLOCKS UL DUE TO BSN CS2 072226

1-PHASE UL GPRS TBF ESTABLISHMENT REQUESTS 072227

1-PHASE UL GPRS TBF SUCCESSFUL ESTABLISHMENTS 072229

Name Number

UR DL RLC MAC BLOCKS 073000

RETRANS DL RLC MAC BLOCKS 073001

SCHED UNUSED RADIO BLOCKS 073002

DL RLC MAC BLOCKS 073003

Table 7 Counters of RLC Blocks per TRX Measurement

Name Number

FRMS WRONG CHECK SEQ ERR 074000

FRMS WRONG DLCI 074001

OTHER FRAME ERROR 074002

T391 TIMEOUT 074003

Table 8 Counters of Frame Relay Measurement

Name Number

Table 6 Counters of Packet Control Unit Measurement related to GPRS (Cont.)

DN7036138 43



STAT MSG WRONG SEND SEQ NBR 074004

STAT MSG WRONG REC SEQ NBR 074005

BEAR CHANGED UNOPER 074006

BEAR RET OPER 074007

STAT MSG UNKNOWN PVC 074008

STAT MSG SENT TOO OFTEN 074009

TIME BEAR UNOPERATIONAL 074010

DLCI 1 ID 074011

DLCI 1 SENT FRMS 074012

DLCI 1 KBYTES SENT 074013

DLCI 1 REC FRMS 074014

DLCI 1 KBYTES REC FRMS 074015

DLCI 1 DISC SENT FRMS 074016

DLCI 1 BYTES DISC SENT FRMS 074017

DLCI 1 DISC REC FRMS 074018

DLCI 1 BYTES DISC REC FRMS 074019

DLCI 1 STAT ACT TO INACT 074020

DLCI 1 INACTIVITY TIME 074021

DLCI 1 DISC UL NS UDATA 074022

DLCI 5 ID 074059












DLCI 6 ID 074071





Name Number

Table 8 Counters of Frame Relay Measurement (Cont.)

44 DN7036138




For more information, see 74 Frame Relay Measurement.

79 Coding Scheme Measurement








: :

DLCI 16 ID 074191












Name Number

NUMBER OF DL RLC BLOCKS IN ACKNOWLEDGED MODE 079000

NUMBER OF DL RLC BLOCKS IN UNACKNOWLEDGED MODE

079001

NUMBER OF UL RLC BLOCKS IN ACKNOWLEDGED MODE 079002

NUMBER OF UL RLC BLOCKS IN UNACKNOWLEDGED MODE

079003

NUMBER OF BAD RLC DATA BLOCKS WITH VALID HEADER UL UNACK MODE

079004

NUMBER OF BAD RLC DATA BLOCKS WITH BAD HEADER UL UNACK MODE

079005

NUMBER OF BAD RLC DATA BLOCKS WITH VALID HEADER UL ACK MODE

079006

Table 9 Counters of Coding Scheme Measurement

Name Number

Table 8 Counters of Frame Relay Measurement (Cont.)

DN7036138 45



For more information, see 79 Coding Scheme Measurement.

90 Quality of Service Measurement

For more information, see 90 Quality of Service Measurement.

96 GPRS RX Level and Quality M

Power Parameters changes

Documents

Transcript of Power Parameters changes