You are on page 1of 22

BSC3153 Nokia GSM/EDGE BSS, Rel. BSS13, BSC and TCSM, Rel. S13, Product Documentation, v.

Dynamic Abis Pool Handling

DN01444 Issue 5-0 en 19/02/2008

# Nokia Siemens Networks

1 (22)

Dynamic Abis Pool Handling

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 DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. 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 2008. All rights reserved.

2 (22)

# Nokia Siemens Networks

DN01444 Issue 5-0 en 19/02/2008

Contents

Contents
Contents 3 List of tables 4 List of figures 5 Summary of changes 7 1 2 3 Creating a dynamic Abis pool 11 Modifying a dynamic Abis pool 17 Deleting a dynamic Abis pool 21

DN01444 Issue 5-0 en 19/02/2008

# Nokia Siemens Networks

3 (22)

Dynamic Abis Pool Handling

List of tables

4 (22)

# Nokia Siemens Networks

DN01444 Issue 5-0 en 19/02/2008

List of figures

List of figures

DN01444 Issue 5-0 en 19/02/2008

# Nokia Siemens Networks

5 (22)

Dynamic Abis Pool Handling

6 (22)

# Nokia Siemens Networks

DN01444 Issue 5-0 en 19/02/2008

Summary of changes

Summary of changes

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

Changes made between issues 5-0 and 4-0


Creating a dynamic Abis pool:
.

The note on ETSI and ANSI environments has been converted to plain text. Reference to PBCCH/PCCCH has been removed. Information on the EDGE-capable TRXs in the BTSs has been updated in section Radio network limitations. The warning has been converted to a caution. The note on creating a new DAP in a PCU has been converted to plain text and moved to section Before you start. Information on Packet Control Unit (PCU2) Pooling has been added to section Before you start. The heading of step Check that you have free Abis interface PCM capacity (WUP) has been changed to Check to which ET-PCM the Abis interface has been connected (WUP). Information in that step has been updated. Step Check that the ET-PCM has space for a dynamic pool (WUP) has been added. New command and information on Packet Control Unit (PCU2) Pooling have been added to step Create the dynamic Abis pool (ESE).

DN01444 Issue 5-0 en 19/02/2008

# Nokia Siemens Networks

7 (22)

Dynamic Abis Pool Handling

Example Creating a dynamic Abis pool (Packet Control Unit (PCU2) Pooling not in use) has been updated. References to EGPRS, Extended Cell for GPRS/EDGE, Coding Schemes CS-3 and CS-4, and Packet Control Unit (PCU2) Pooling activation instructions have been added.

Modifying a dynamic Abis pool:


.

The note on ETSI and ANSI environments has been converted to plain text. The note on modifying an existing DAP of a PCU has been converted to plain text. Information on Packet Control Unit (PCU2) Pooling has been added. The commands and examples have been updated in steps Modify a dynamic Abis pool by adding timeslots to the beginning or end of the pool (ESM) and Modify a dynamic Abis pool by removing timeslots from the beginning or end of the pool (ESM). New step Modify a dynamic Abis pool by changing the PSE (ESM) has been added. An example has also been added. Information on the segments that are attached to DAP has been added to steps Modify a dynamic Abis pool by changing the BCSU and the PCU (ESM) and Modify a dynamic Abis pool by changing PSE (ESM). References to EGPRS and Packet Control Unit (PCU2) Pooling activation instructions have been added.

Deleting a dynamic Abis pool:


.

The note on ETSI and ANSI environments has been converted to plain text. The note on deleting an existing DAP of a PCU has been converted to plain text and moved to section Before you start.

Changes made between issues 4-1 and 4-0


Creating a dynamic Abis pool:
The theoretical maximum number of dynamic Abis pools in a BSC has been changed from 470 to 1600.

8 (22)

# Nokia Siemens Networks

DN01444 Issue 5-0 en 19/02/2008

Summary of changes

Changes made between issues 4-0 and 32


Some of the limitations listed at the start of Chapter 1 have been moved to the description of Dynamic Abis.

DN01444 Issue 5-0 en 19/02/2008

# Nokia Siemens Networks

9 (22)

Dynamic Abis Pool Handling

10 (22)

# Nokia Siemens Networks

DN01444 Issue 5-0 en 19/02/2008

Creating a dynamic Abis pool

Creating a dynamic Abis pool


These instructions apply to both ETSI and ANSI environments. Space is reserved from the Packet Control Unit Pulse Code Modulation (PCUPCM) serial line in the order of creation. The pools are rearranged optimally to the PCUPCM during Base Station Controller Signalling Unit (BCSU) restart, Marker and Cellular Management Unit (MCMU) restart, or BCSU switchover. You should not reserve Abis resources for pools that will not be used, as it will prevent the resources from being allocated for other traffic.

PCU limitations:
.

There can be 16 dynamic Abis pools in one logical PCU. In one logical PCU there can only be 256 Abis channels (including Default GPRS + EGPRS dynamic Abis pool (EDAP) channels). Note that the number of default GPRS channels includes EGPRS channels.

You cannot configure more than 204 EDAP channels in one logical PCU. This is because there must also be space for at least 1 EGPRS channel for every 4 EDAP channels (51 EGPRS channels + 204 EDAP channels = 255 Abis channels). The rationale for this is that a single EGPRS radio timeslot uses a maximum of 4 16kbit/s EDAP channels.

Radio network limitations:


.

The theoretical maximum number of dynamic Abis pools in a BSC is 1600. However, the practical maximum is determined by the number of PCUs in the BSC. The maximum size for a single EGPRS dynamic Abis pool (EDAP) area is 12 x 64 kbit/s PCM timeslots (48 EDAP channels per DAP).

DN01444 Issue 5-0 en 19/02/2008

# Nokia Siemens Networks

11 (22)

Dynamic Abis Pool Handling

The theoretical maximum number of transceivers (TRXs) attached to one dynamic Abis pool is 20. However, since TRXs using DAP resources must be allocated to the same Abis external PCM circuit (ET-PCM) line with EDAP, the maximum number of TRXs per DAP is less than 20. The serving PCU must be the same for all TRXs under one segment (also including possible dynamic Abis pools attached). Dynamic Abis pool + TRX signalling link + traffic channels (TCHs) must be located on the same ET-PCM. The DAP attached to the TRX, and the network service entity identifier (NSEI) serving the BTS of the TRX, have to be in the same PCU. If EGPRS or Coding Schemes CS-3 and CS-4 is enabled in a BTS, the BTS must have EDGE-capable TRXs that are connected to a DAP. The non-EDGE TRXs of that BTS must be GPRS disabled. If there are EDGE TRXs and non-EDGE TRXs in the BTS, see more specific instructions in Activating and Testing BSS10083: EGPRS and Activating and Testing BSS11088: Coding Schemes CS-3 and CS-4 under Test and activate/Data in the PDF view. If Extended Cell for GPRS/EDGE is enabled in the cell, all the TRXs in the BTSs using GPRS/EDGE in the segment must be EDGEcapable and must be attached to the DAP. The non-EDGE TRXs cannot be attached to a DAP.

Caution
Sharing the EGPRS dynamic Abis pool (EDAP) between several cabinets may damage the transceiver or transmission unit (TRU) hardware. One EDAP resource should not be shared between several base control function (BCF) cabinets.

Note
Only EDGE-capable transceivers are able to use dynamic Abis pool (DAP) resources.

For more information, see

12 (22)

# Nokia Siemens Networks

DN01444 Issue 5-0 en 19/02/2008

Creating a dynamic Abis pool

Packet Control Unit (PCU) in GPRS/EDGE System Feature Description under Feature descriptions/Data in the PDF view. Dynamic Abis Pool management in Dynamic Abis under Feature descriptions/Data in the PDF view.

Before you start When creating a new dynamic Abis pool, the BSC turns off the GPRS traffic from the logical PCU to which the new DAP is to be created. The BSC downgrades all packet switched traffic channels from the PCU and upgrades these traffic channels to packet switched use again. This short interruption ensures that the BSC can find a block of free timeslots from the PCUPCM. Creating a new DAP in a PCU causes a reallocation of digital signal processor (DSP) resources in the PCU between the new and existing DAPs and GPRS channels. It also ensures the optimised PCU DSP resource usage for each DAP connected to a specific PCU. If Packet Control Unit (PCU2) Pooling is in use and the DAP is created for a packet service entity (PSE), this kind of interruption in the GPRS traffic takes place in the PCU where the PCU selection algorithm attaches the DAP.

Note
You must configure dynamic Abis pools of the same size and the same timeslots in both the BSC and the base transceiver station (BTS).

Steps
1. Check whether you have a suitable dynamic Abis pool created (ESI). ZESI; If not, move on to the next step. 2. Check that you have a PCU card configured to a certain BCSU (WTI). You cannot create a dynamic Abis pool if there is no logical PCU configured to a BCSU. In BSC3i, a physical PCU plug-in unit is created with two separate elements (two plug-in units with their own PIU/plug-in unit indexes in MML) which can be considered as two logical PCUs.

DN01444 Issue 5-0 en 19/02/2008

# Nokia Siemens Networks

13 (22)

Dynamic Abis Pool Handling

ZWTI:<information type>:<unit identification>: <plug-in unit identification>; Now you can check from the output list if a logical PCU is configured to BCSU-0. If yes, move on to the next step. 3. Check to which ET-PCM the Abis interface has been connected (WUP). ZWUP; In the list you find several ET-PCMs configured on your system. Select a suitable ET-PCM where to create the dynamic Abis pool. 4. Check that the ET-PCM has space for a dynamic pool (WUP). ZWUP:<pcm circuit number>::CGR; You can see free timeslots in the list. 5. Create the dynamic Abis pool (ESE). ZESE:<pool id>,<circuit>,<size>,<BCSU id>,<PCU id>; or ZESE:<pool id>,<circuit>,<size>,<PSEI>; Use the second command if Packet Control Unit (PCU2) Pooling is used. Note that Packet Control Unit (PCU2) Pooling is a licencebased application software product and requires a valid licence in the BSC. For more information, see Licensing in BSC under Install and upgrade/Software in the PDF view. Example Creating a dynamic Abis pool (Packet Control Unit (PCU2) Pooling not in use)

Create a dynamic Abis pool whose pool id is 1, circuit is ET-PCM number 32, pool size is 6 timeslots starting at the fifth timeslot, BCSU index is 0 and PCU plug-in unit index is 2: ZESI; ZWTI:P:BCSU,0;

14 (22)

# Nokia Siemens Networks

DN01444 Issue 5-0 en 19/02/2008

Creating a dynamic Abis pool

ZWUP; ZWUP:32::CGR; ZESE:ID=1,CRCT=325,SIZE=6,BCSU=0,PCU=2;


Further information
.

Alarm 3068 EGPRS DYNAMIC ABIS POOL FAILURE is raised if the dynamic Abis pool creation fails for some reason. For more information on the possible causes of the failure and recovery instructions, see Failure Printouts (2000-3999) under Reference/ Alarms in the PDF view. For instructions on attaching a dynamic Abis pool to a TRX, see Activating and Testing BSS9006: GPRS under Test and activate/ Data in the PDF view.

Activating and Testing BSS10083: EGPRS under Test and activate/ Data in the PDF view Activating and Testing BSS20094: Extended Cell for GPRS/EDGE under Test and activate/Data in the PDF view Activating and Testing BSS11088: Coding Schemes CS-3 and CS-4 under Test and activate/Data in the PDF view Activating and Testing BSS20106: Packet Control Unit (PCU2) Pooling under Test and activate/Data in the PDF view

DN01444 Issue 5-0 en 19/02/2008

# Nokia Siemens Networks

15 (22)

Dynamic Abis Pool Handling

16 (22)

# Nokia Siemens Networks

DN01444 Issue 5-0 en 19/02/2008

Modifying a dynamic Abis pool

Modifying a dynamic Abis pool


These instructions apply to both ETSI and ANSI environments. You can modify the dynamic Abis pool (DAP) size or change the controlling logical packet control unit (PCU) or the packet service entity (PSE) to optimise the use of the pools and shared resources. You can change the controlling logical PCU of the DAP if you want to balance the traffic load between PCUs. When Packet Control Unit (PCU2) Pooling is in use, you can balance the traffic load between the PCUs by moving the DAP to a new PSE or with the reallocation command FXF. With the dynamic Abis measurement you can measure the peak and average usage of the dynamic Abis pool and MCS limitations and restrictions for TBF scheduling. For more information, see 76 Dynamic Abis Measurement under Reference/Counters/performance indicators/ GPRS measurements (PS) in the PDF view. Before you start When modifying the dynamic Abis pool, the BSC turns off the GPRS traffic from the logical PCU where the modified pool exists. The BSC downgrades all packet switched traffic channels from the PCU and upgrades these traffic channels to packet switched use again. This short interruption ensures that the BSC can find a block of free timeslots from the Packet Control Unit Pulse Code Modulation (PCUPCM) serial line. Modifying an existing DAP of a PCU causes a reallocation of digital signal processor (DSP) resources in the PCU between the new and existing DAPs and GPRS channels. It also ensures optimised PCU DSP resource usage for each DAP connected to a specific PCU. If Packet Control Unit (PCU2) Pooling is in use and the DAP is moved to a new PSE, this kind of interruption in the GPRS traffic takes place in the source PCU and also in the target PCU where the PCU selection algorithm attaches the DAP in the new PSE.

DN01444 Issue 5-0 en 19/02/2008

# Nokia Siemens Networks

17 (22)

Dynamic Abis Pool Handling

Note
You must configure dynamic Abis pools of the same size and the same timeslots in both the BSC and the base transceiver station (BTS).

Steps
1. To implement this step, choose one of the following alternatives: a. Modify a dynamic Abis pool by adding timeslots to the beginning or end of the pool (ESM). When adding new timeslots to the beginning or end of the dynamic Abis pool, ensure that there is enough space in the pool. ZESM:<pool id>,<new first timeslot|new last timeslot>; Example Modifying the dynamic Abis pool

Modify the dynamic Abis pool whose id is 1 and pool starting from the timeslot 3 so that you add two timeslots to the beginning of the pool: ZESM:ID=1,NFT=3; Example Modifying the dynamic Abis pool

Modify the dynamic Abis pool whose id is 1 and pool ending to the timeslot 15 so that you add five timeslots to the end of the pool: ZESM:ID=1,NLT=15; b. Modify a dynamic Abis pool by removing timeslots from the beginning or end of the pool (ESM). ZESM:<pool id>,<new first timeslot|new last timeslot>; Example Modifying the dynamic Abis pool

Modify the dynamic Abis pool whose id is 1 and pool starting from the timeslot 6 so that you remove three timeslots from the beginning of the pool:

18 (22)

# Nokia Siemens Networks

DN01444 Issue 5-0 en 19/02/2008

Modifying a dynamic Abis pool

ZESM:ID=1,NFT=6; Example Modifying the dynamic Abis pool

Modify the dynamic Abis pool whose id is 1 and pool ending to the timeslot 11 so that you remove four timeslots from the end of the pool: ZESM:ID=1,NLT=11; c. Modify a dynamic Abis pool by changing the BCSU and the PCU (ESM). All the segments that are attached to the dynamic Abis pool will be moved to the new PCU. ZESM:<pool id>,<BCSU id>,<PCU id>; Example Modify the dynamic Abis pool whose id is 1 so that you change the Base Station Control Signalling Unit (BCSU) and the logical PCU: ZESM:ID=1,BCSU=1,PCU=4; d. Modify a dynamic Abis pool by changing the PSE (ESM). All the segments that are attached to the dynamic Abis pool will be moved to the new PSE. ZESM:<pool id>,<PSEI>; Example Modify the dynamic Abis pool whose id is 2 so that the new packet service entity is 3. ZESM:ID=2,PSEI=3;
Further information

DN01444 Issue 5-0 en 19/02/2008

# Nokia Siemens Networks

19 (22)

Dynamic Abis Pool Handling

Alarm 3068 EGPRS DYNAMIC ABIS POOL FAILURE is raised if the dynamic Abis pool creation fails for some reason. For more information on the possible causes of the failure and recovery instructions, see Failure Printouts (2000-3999) under Reference/ Alarms in the PDF view. For instructions on modifying the dynamic Abis pool information of a TRX, see Activating and Testing BSS9006: GPRS under Test and activate/Data in the PDF view.

Activating and Testing BSS10083: EGPRS under Test and activate/ Data in the PDF view Activating and Testing BSS20106: Packet Control Unit (PCU2) Pooling under Test and activate/Data in the PDF view

20 (22)

# Nokia Siemens Networks

DN01444 Issue 5-0 en 19/02/2008

Deleting a dynamic Abis pool

Deleting a dynamic Abis pool


Before you start These instructions apply to both ETSI and ANSI environments. When deleting a dynamic Abis pool (DAP), the BSC turns off the GPRS traffic from the logical packet control unit (PCU) where the deleted pool exists. The BSC downgrades all packet switched traffic channels from the PCU and upgrades these traffic channels to packet switched use again. Deleting an existing DAP of a PCU causes a reallocation of the remaining digital signal processor (DSP) resources in the PCU. This short interruption ensures optimised PCU DSP resource usage for each DAP connected to a specific PCU.

Steps
1. Check that there are no TRXs attached to the dynamic Abis pool that you want to delete (ESI). ZESI:ID=<pool id>:TRXS; You cannot delete the dynamic Abis pool if there are TRXs attached to it. Example ZESI:ID=1:TRXS; 2. Detach TRXs from the dynamic Abis pool. If there are TRXs attached to the dynamic Abis pool, detach them. For more information on detaching a dynamic Abis pool from a TRX, see Activating and Testing BSS9006: GPRS under Test and activate/Data in the PDF view. 3. Delete dynamic Abis pool(s) (ESG).

DN01444 Issue 5-0 en 19/02/2008

# Nokia Siemens Networks

21 (22)

Dynamic Abis Pool Handling

ZESG:ID=<pool id>; Example Deleting one dynamic Abis pool: ZESG:ID=1; Deleting several dynamic Abis pools: ZESG:ID=1&4&&7;
Further information

Alarm 3068 EGPRS DYNAMIC ABIS POOL FAILURE is raised if the dynamic Abis pool creation fails for some reason. For more information on the possible causes of the failure and recovery instructions, see Failure Printouts (2000-3999) under Reference/Alarms in the PDF view.

22 (22)

# Nokia Siemens Networks

DN01444 Issue 5-0 en 19/02/2008