GSM/EDGE BSS, Rel. RG30(BSS), Operating Documentation, Issue 03
Feature description
BSS21238: Merged P- & E-GSM900 DN0935434 Issue 01 Approval Date 2010-06-09 Confidential
Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We w ould like to encourage you as our customer s and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environment al Policy or any of the environm ental services we offer, please contact us at Nokia Siemens Networks for any additional information.
BSS21238: Merged P- & E-GSM900
The information in this document i s subject to change without notice and descri bes only the product defined in the introduction of this documentation. This documentation is in tended for the use of Nokia Siemens Networks c ustomers 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 pr ofessional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the pr ocess 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 so ftware 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 m aterial errors and omissions. N okia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whi ch 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 B UT 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 DOCUM ENT OR THE INFORMATION IN IT. This documentation and the product it desc ribes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © Nokia Siemens Networks 2010. All rights reserved
f
Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may i nstall, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is pr ovided 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 können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen. Installation, Betrieb, Wartung und sonstige Handhabung des Pr oduktes darf nur durch geschultes und qualifiziertes Personal unter Be achtung der anwendbaren Sicherheitsanforderungen erfolgen. Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentationssatzes.
2
Id:0900d8058068aaf9 Confidential
DN0935434
BSS21238: Merged P- & E-GSM900
Table of contents This document has 17 pages.
DN0935434
1
Introduction to the feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2
Benefits for the operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 3.1 3.2
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Software requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4 4.1 4.1.1
Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Functional overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Channel and Frequency allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1.2 4.2
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Functional split. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5
System impacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.1 5.2
Relations to other features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Impacts on interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6
User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1 6.2
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 MML commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7
Activating and configuring the feature . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1 7.2 7.3
Activating and configuring the feature . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Testing the feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Deactivating the feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 0 – Z. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Id:0900d8058068aaf9 Confidential
3
BSS21238: Merged P- & E-GSM900
List of tables
4
Table 1
Software requirements for different network elements . . . . . . . . . . . . . . 7
Table 2
Parameter for Merged P- & E-GSM900 . . . . . . . . . . . . . . . . . . . . . . . . . 11
Id:0900d8058068aaf9 Confidential
DN0935434
BSS21238: Merged P- & E-GSM900
Introduction to the feature
1 Introduction to the feature The feature BSS21238: “Merged P- & E-GSM900” replaces the approaches before the release RG10(BSS) related to usage of the primary and extended freque ncy bands in a GSM 900 network. By combining the two frequency bands into one, this feature removes the restrictions associated with the enhancements for the combined usage of primary and extended bands in the software releases before the release RG10(BSS). The usage of PGSM 900 and EGSM 900 frequencies with out restraints is the characteristic of this feature. This feature is a software product controlled by licensing and can be enabled or disabled for a segment. It is supported on all types of BTSs.
DN0935434
Id:0900d8058068aacd Confidential
5
Benefits for the operator
BSS21238: Merged P- & E-GSM900
2 Benefits for the operator Merging PGSM 900 and EGSM 900 into an undivided GSM 900 frequency band improves the spectral efficiency and the general operability of the network. With this feature, the PGSM 900 and EGSM 900 frequencies are handled equally. The channel allocation becomes more efficient as all the GSM 900 resources are available as one pool. This feature removes the former restrictions related to the combined use of EGSM 900 and PGSM 900 in a segment.
6
Id:0900d8058068aad0 Confidential
DN0935434
BSS21238: Merged P- & E-GSM900
Requirements
3 Requirements The feature “Merged P- & E-GSM900” requires the support of primary and extended GSM 900 frequency bands by network elements.
3.1
Software requirements The software versions required for the network entities are listed in the table below. Network element
BSC
S14EP5.1
NetAct
OSS5.2 CD set 3
Table 1
3.2
Required software release
Software requirements for different network elements
Hardware requirements Mobile stations supporting operations on both the PGSM 900 and the EGSM 900 frequency bands are required.
DN0935434
Id:0900d8058068aad3 Confidential
7
Functional description
BSS21238: Merged P- & E-GSM900
4 Functional description This chapter describes the functional aspects of the feature “Merged P- & E-GSM900”.
4.1
Functional overview The feature “Merged P- & E-GSM900” supersedes the earlier enhancements made for combining PGSM 900 and EGSM 900 frequencies in a segment or BTS. This feature enables the following functionalities in a PGSM 900 - EGSM 900 BTS when the BCCH carrier is on PGSM 900 frequency band. •
•
•
•
•
•
•
•
A TRX can have both RF hopping and GPRS/EDGE. Enabling the base band hopping. Enabling the super reuse of frequencies. Allowing of the DFCA hopping. Allowing the configuration of static SDCCH resources in EGSM 900 TRXs apart from PGSM 900 TRXs. Enabling the dynamic reconfiguration of SDCCH resources in EGSM 900 TRXs. Allowing the FACCH setup in EGSM 900 TRXs also. Enabling the BSC to support the use of high speed circuit switched data.
This feature makes it possible to use and combine PGSM 900 and E GSM 900 resources in any BTS of the segment irre spective of the frequency band the BCCH of the segment is present (the possible BCCH frequency bands being PGSM 900, E GSM 900 and GSM 1800). The following is an example scenario of this feature operation. Consider a segment with three BTSs, a PGSM 90 0 - EGSM 900 BCCH BTS with BCCH on PGSM 900, a BTS with an EGSM 900 and a GSM 1800 BTS. The GPRS/EDGE is in use for the EGSM 900 TRX in the BCCH BTS and in the EGSM 900 BTS. With the feature “Merged P- & E-GSM900” enabled in the segment, the channel allocation for both circuit switched and packet switched services happens from any GSM 900 BTS of the segment even if the BCCH is on the PGSM 900 band. The GPRS and RF hopping can be activated for EGSM 900 TRXs of the BCCH BTS also. The BTS with GSM 1800 band also needs to be locked during the feature activation and deactivation. This feature results in merging of PGSM 900 and EGSM 900 frequencies into one single band of frequencies. Since PGSM 900 and EGSM 900frequencies are considered as one frequency band, intra segment handovers due to traffic load (the level defined based on the parameter BTSLoadInSEG has been exceeded) are not requested between PGSM 900 and EGSM 900 bands when these are configured as separate BTS objects in the segment. When the parameter merged pgsm and egsm enabled is enabled, the ARFCN 0 and ARFCN 1 are marked as the adjacent frequencies for DFCA modile allocation (MA) frequency list
4.1.1
Channel and Frequency allocation In the software releases before the release RG10(BSS), if the BCCH carrier of a BTS with PGSM 900 and EGSM 900 is on a PGSM 900 frequency, the initial channel allocation for immediate assignment for circuit switched and packet switched services is limited to PGSM 900 frequencies. Also, the cell allocation frequency list (CA) is limited
8
Id:0900d8058068aadc Confidential
DN0935434
BSS21238: Merged P- & E-GSM900
Functional description
to PGSM 900 frequencies. A common CA frequency list is used when the BCCH is on EGSM 900. For the release RG10(BSS) and onwards also, above scenario is true if the feature is not enabled in a segment. With this feature, the channel allocation for immediate assignment includes all GSM 900 frequencies regardless of the BCCH band. A common CA frequency list is used for the PGSM 900 and EGSM 900 frequencies regardless of which band the BCCH carrier is operating on. With this feature, the BSC allows both the PGSM 900 and the EGSM 900 frequencies when creating or modifying an MA frequency list or a DFCA MA frequency list.
4.1.2
Restrictions This feature does not support the mobile stations which supported only PGSM 900 frequencies. The maximum number of available GSM 90 0 frequencies in a segment with PGSM 900 and EGSM 900 bands is limited to 16 (17 if ARCFN 0 is included).
4.2
Functional split The feature “Merged P- & E-GSM900” affects the following network elements. BSC
This feature is activated in the BSC. When this feature is in use in the BSC, it can be enabled or disabled for any segment in that BSC.
DN0935434
Id:0900d8058068aadc Confidential
9
System impacts
BSS21238: Merged P- & E-GSM900
5 System impacts This chapter details the impacts caused by this feature on the system and other features.
5.1
Relations to other features The “Merged P- & E-GSM900” feature completes the functionality of common BCCH control feature for the two frequency bands and replaces the enhancing features listed below. •
•
•
•
•
•
BSS20712 “BCCH on EGSM in PGSM/EGSM segment” allows using common BCCH on an EGSM 900 BTS in a segment with PGSM 900 and EGSM 900. BSS20826 “BCCH on EGSM in combined PGSM-EGSM usage” allows using the PGSM 900 and EGSM 900 frequencies in a BTS object of the segment when the BCCH frequency is on EGSM 900. BSS21010 “BCCH on PGSM 900 in a PGSM 900 - EGSM 900” allows the combined usage of PGSM 900 and EGSM 90 0 frequencies in a BTS with the BCCH on PGSM 900. BSS21165 “Single MA list for EGSM and PGSM“ allows RF hopping using an MA list with both PGSM 900 and EGSM 900 frequencies. BSS21025 “Full pre-emption support in a PGSM 900 - EGSM 900 BTS with BCCH on PGSM 900”. BSS21026 “GPRS/EDGE support for PGSM-EGSM BTS” allows the GPRS/EDGE use on both the frequency bands in a PGSM 900 - EGSM 900 BTS.
Even if the feature “Merged P- & E-GSM900” is active in a segment, separate PGSM 900 and EGSM 900 BTS objects can be configured in that segment. The traditional options for the common BCCH control are needed when the segment has PGSM 900 and EGSM 900 resources as separate BTS objects.
5.2
Impacts on interfaces This feature does not impact any interfaces.
10
Id:0900d8058068aadf Confidential
DN0935434
BSS21238: Merged P- & E-GSM900
User interface
6 User interface This chapter is divided into the following sections:
6.1
•
“Parameters”
•
“MML commands”
Parameters The following table shows the parameters implemented for the feature “Merged P- & EGSM900”. The parameters are subject to change.
Name
Object
Merged PGSM and EGSM enabled ( MPE)
SEG
Description
With this parameter it is possible to use PGSM 900 and EGSM 900 resources as a unified band of frequencies in the cell.
Range
N (Merged PGSM and EGSM is disabled)
Default value
N
Y (Merged PGSM and EGSM is enabled) Table 2
Parameter for Merged P- & E-GSM900 The above parameter can be configured via the MML interface. Q3 commands do not support this parameter. In a segment that includes several BTS objects and both PGSM 900 and EGSM 900 frequencies, the following traditional PRFILE parameters related to the common BCCH control are required, even if this feature is enabled for that segment. •
6.2
COMMON_BCCH_GSM900
•
COMMON_BCCH_EGSM900
•
SEGMENT_USAGE
MML commands The following MML commands are used to handle this feature. •
•
DN0935434
The EQM command for accessing the parameter merged PGSM and EGSM enabled (MPE) in a segment under the BSC. The MML output command EQO for displaying the parameter merged PGSM and EGSM enabled (MPE ).
Id:0900d8058068aae8 Confidential
11
Activating and configuring the feature
BSS21238: Merged P- & E-GSM900
7 Activating and configuring the feature This chapter provides the procedures to operate the feature “Merged PGSM 900 and EGSM 900”.
7.1
Activating and configuring the feature For segment configuration with several BTSs, following are the prerequisites: •
The COMMON_BCCH_GSM900 attribute is set to TRUE.
•
The COMMON_BCCH_EGSM900 attribute is set to TRUE.
•
The SEGMENT_USAGE attribute is set to TRUE.
Check whether the license is installed in the BSC
Enter the following command to verify if the license of this feature is installed: ZW7I:LIC,FULL:LIC=;;
Activate the feature in the BSC
Enter the following command to change the state of the feature to “ON”: ZW7M:FEA=1530:ON;
Lock all the BTSs in the segment for which the feature is b eing activated
Enter the following command to lock the BTS: ZEQS:BTS=:L:;
Enable the feature for the segm ent
Enter the following command to modify the segment specific parameter Merged PGSM and EGSM enabled to Y: ZEQM:BTS=:MPE=Y;
When common BCCH control is in use, enter the following command: ZEQM:SEG=:MPE=Y;
Enable GPRS/EDGE in the TRXs
Enter the following command to enable the GPRS/EDGE for any TRX of the segment. ZERM:BTS=,TRX=:GTRX=Y;
g
Steps 5 to 8 are in order to utilize the full benefit of the feature. These are not mandatory for activation of the feature.
Create a mobile allocation frequency list
Enter the following command to create a mobile allocation (MA) list including PGSM 900 and EGSM 900 frequencies. ZEBE:,:FREQ=;
12
Id:0900d8058068aaf1 Confidential
DN0935434
BSS21238: Merged P- & E-GSM900
Activating and configuring the feature
Attach the mobile allocation frequency list to the GSM 900 BTS
Enter the following command to attach t he MA list to the GSM 900 BTS of the segment. ZEQA:BTS=:MAL=,MO=,MS=;
Turn RF hopping on for the GSM 900 BTS
Enter the following command to turn the RF hopping on for the GSM 900 BTS of the segment. ZEQE:BTS=:HOP=RF;
Unlock the BTSs of the segment
Enter the following command to unlock the BTS: ZEQS:BTS=:U:;
g
Unlock all the BTSs which were locked in Step 3.
End
7.2
Testing the feature Following are the prerequisites to test this feature: •
1 base station controller (BSC) with the license of the feature installed.
•
One BTS with both PGSM 900 TRX and EGSM 900 TRX with the feature enabled.
•
BCCH TRX is on PGSM 900.
•
RF hopping with an MA frequency list of both GPSM900 and EGSM9 00 frequencies
•
GPRS/EDGE enabled in the TRXs of the BTS
•
3 MSs (MS1,MS2 and MS3) which support PGSM 90 0 and EGSM 900 frequencies.
•
Web server.
•
NetAct (optional)
Set the TRX priority in TCH allocation to the non BCCH TRX (EQM)
Enter the following command to make sure that both PGSM 900 and EGSM 900 frequencies will be used for the speech call: ZEQM:BTS=:TRP=2;
Set the GPRS territory in the hopping TRX (EQV)
Enter the following command to make sure that both PGSM 900 and EGSM 900 frequencies will be used for the PS traffic: ZEQV:BTS=:BFG=2;
DN0935434
Id:0900d8058068aaf1 Confidential
13
Activating and configuring the feature
BSS21238: Merged P- & E-GSM900
Create measurements for voice and data calls (TPM)
Enter the following command: For circuit switched call: ZTPM:MEASUR,TRAFFIC:,,
