Version Policies and Configuration Requirements for IP-Based GSM-20110421-A-V1.3

GSM IP Version Policies and Configuration Requirements INTERNAL

Doc. Code Product Name GSM

Confidentiality Level

INTERNALProduct Version

GBSS9.0/12.0

Product Department

GSM/UMTS Delivery Department

Issue V1.25

GSM IP Version Policies and Configuration Requirements

2023-4-20 Huawei Confidential Page 1 of 28

Prepared byGSM/UMTS Delivery Department

Date 2010-07-01

Reviewed by Date

Reviewed by Date

Approved by Date


Huawei Technologies Co., Ltd.



Change History

DateRevision Version

Description Author

2010-07-01 V1.00 Draft completed. Ma Hongbin

2010-07-29 V1.10Recommended core network (CN) product versions and BSC versions updated.

Ma Hongbin

2010-08-06 V1.12Recommended BSC versions interconnected to the NSN in A over IP updated.

Ma Hongbin

2010-09-19 V1.15

1. Requirements for the IPCLK Server version added.

2. Descriptions of GSM HR Toc added.

Ma Hongbin

2010-12-15 V1.20

1. Recommended wireless network (WN) product versions and CN product versions updated.

2. Configuration descriptions of FR/HR AMR TrFO software parameter added.

3. Precaution/restriction description added.

4. Document panoramic view added.5. Description of interconnection of A-

over-IP products and products of other vendors added.

6. Description of A over TDM/IP dual-stack application added.

7. Document name changed.8. Link related to the workaround guide

and some comments updated.

Ma Hongbin

2010-12-20 V1.211. UMG version updated.2. Description of configuration of CN

software parameters added.Ma Hongbin

2011-3-10 V1.25

1. GBSS9.0 versions updated.2. Version requirements for GBSS12.0

added.3. Configuration requirements for

GBSS12.0 added.4. Description of GBSS9.0 key problems

updated.5. Description of GBSS12.0 key problems

added.6. Section 3.6 "GBSS 12.0 Network

Problem Avoidance Guides" added.7. List of parameters for interconnecting

CN products to the WN products added.

Guo Wei

Ma Hongbin





Contents

1 Commercial Version Policies...........................................................71.1 General Policies.................................................................................................................................................7

1.2 Version Requirements on WN............................................................................................................................7

1.3 Version Requirements on CN (Huawei)............................................................................................................8

1.4 Version Requirements for IPCLK Server (Huawei)..........................................................................................8

2 Configuration Requirements.........................................................102.1 Configuration Requirements on WN...............................................................................................................10

2.1.1 Configuration of Speech Version and Rate Set (GBSS 9.0/12.0 A over IP)...........................................10

2.1.2 BSC Software Parameter Setting (GBSS 9.0 A over IP)........................................................................10

2.1.3 BSC Software Parameter Setting (GBSS 12.0 A over IP)......................................................................13

2.2 Configuration Requirements on CN (Huawei)................................................................................................15

2.2.1 Configuring the Protocol in A over IP (Standard Protocol in A over IP)...............................................15

2.2.2 Configuring the AMR Rate Set (Standard Protocol in A over IP)..........................................................15

2.2.3 Configuring TrFO Compatible with AMR FR/HR (Standard Protocol in A over IP)............................16

2.2.4 Configuring Other Software Parameters on CN (Standard Protocol in A over IP)................................17

3 Precautions.................................................................................183.1 Upgrading GBSS 8.1 IP to GBSS 9.0 IP.........................................................................................................18

3.2 GBSS 8.1 A IP Precaution Bulletin..................................................................................................................19

3.3 GBSS 9.0 IP Precaution Bulletins and Key Problems.....................................................................................19

3.4 GBSS 12.0 IP Precaution Bulletins and Key Problems...................................................................................23

3.5 GBSS 9.0 Network Problem Avoidance Guides..............................................................................................24

3.6 GBSS 12.0 Network Problem Avoidance Guides............................................................................................24

3.7 A over IP Restrictions on Early BTS Products like BTS30 and BTS312........................................................24

3.8 TOC in GSM_HR (GBSS 9.0 A over IP)........................................................................................................24

3.9 A over IP Interworking with Competitors' Products........................................................................................25

3.10 A over TDM/A over IP Dual-Stack Mode (GBSS12.0).................................................................................25

4 Attachment.................................................................................264.1 GRAN&CN Parameter Check.........................................................................................................................26



Figures

Figure 2-1 Querying reserved parameter 3...........................................................................................................10

Figure 2-2 Configuring the protocol in A-over-IP................................................................................................12



Tables

Table 2-1 Bits 0 to 13 in reserved parameter 3........................................................................................................8

Table 2-2 Bits 14 to 15 in reserved parameter 3......................................................................................................9

Table 2-3 Bits 0 to 13 in reserved parameter 3......................................................................................................11

Table 2-4 Bit 8 in software parameter P13............................................................................................................13

Table 2-5 Bit 9 in software parameter P13............................................................................................................14

Table 3-1 GBSS 9.0 IP key problems....................................................................................................................17

Table 3-2 GBSS 9.0 IP precaution bulletins..........................................................................................................18

Table 3-3 GBSS 12.0 IP precaution bulletins and key problems..........................................................................21



1 Commercial Version Policies

1.1 General Policies1. GBSS 9.0 and later versions are required in the A over IP or Abis over IP scenario.

2. No more GBSS 8.1 releases are presented. To solve a problem, if any, with an existing IP GBSS 8.1 system, upgrade the system from GBSS 8.1 to GBSS 9.0.

3. Early BTS products like BTS30 and BTS312 have passed their end of marketing (EOM) and last order date of spare parts (LODSP). No more software is provided for those products to support new functions, such as AMR at the A over-IP interface.

4. According to the version policies of the product line, GBSS 12.0 applies to commercial delivery in only the SingleRAN mode and is restricted from the GSM-only mode. GBSS 9.0 and GBSS 13.0 are recommended for IP-based commercial delivery in the GSM-only mode.

The preceding policies have been adopted at the GSM SPDT meeting and incorporated in the Sales Strategy of GSM IP Transmission V1.0 (available at http://3ms.huawei.com/mm/docMaintain/mmMaintain.do?method=showMMDetail&f_id=GSM201009130022).

1.2 Version Requirements on WN

GBSS 9.0

BSC: BSC6900V900R011C00SPH732 and later versions

In the A over IP scenario, BSC6900V900R011C00SPH732 and later versions are recommended for interworking with NSN products. BSC versions interworking with other competitors' CN products will be released later.

GSM BTS:

Outside China: BTS3000V100R009C00SPC087 and later versions are recommended for the BTS3900. GSM BTS3000V200R009C00SPC002 and later versions are recommended for the BTS3012.


http://3ms.huawei.com/mm/docMaintain/mmMaintain.do?method=showMMDetail&f_id=GSM201009130022



After changing the Abis-over-TDM interface to the Abis-over-IPoE1 interface, the BTS3012 interworks with BSC6900V900R011C00SPH752 and later versions. BSC6900V900R011C00SPH752 is expected to be released at the end of May in 2011.

In china: BTS3000V300R009C00SPC021 and later versions are recommended for the BTS3900 and BTS3012.

SingleRAN MBTS: BTS3900V100R002C00SPC200 and later versions

In the A over IP scenario, BTS3900V100R002C00SPC310 and later versions are recommended for the SingleRAN MBTS. BTS3900V100R002C00SPC310 is expected to be released at the end of May in 2011.

GBSS 12.0

BSC: BSC6900V900R012C01SPH510 and later versions

In the A over IP scenario, BSC6900V900R012C01SPH510 and later versions are recommended for interworking with NSN products. BSC versions interworking with other competitors' CN products will be released later.

GSM BTS:

Outside China: BTS3000V100R012C00SPC042 and later versions are recommended for the BTS3900. GSM BTS3000V200R009C00SPC002 and later versions are recommended for the BTS3012.

BTS3000V100R012C00SPC042 is expected to be released in mid-April in 2011.

In china: BTS3000V300R009C00SPC021 and later versions are recommended for the BTS3900 and BTS3012.

SingleRAN MBTS: BTS3900V100R003C00SPC350 and later versions

BTS3900V100R003C00SPC350 is expected to be released in mid-April in 2011.

For more patch releases, see The Suggestion for Installation of Version and Patch of Wireless Product posted monthly at http://support.huawei.com.

In the A over IP + Abis over TDM, A over IP + Abis over IP, and A over TDM + Abis over IP scenarios, especially in the A over IP + Abis over TDM scenario, the BTS version must match the BSC version.

1.3 Version Requirements on CN (Huawei)MSC: CPCI V100R008C03SPH209 (outside China)/CPCI V100R007C05SPH209 (in China)/ATCA V200R008C03SPH209 and later versions

UMG: V200R008C03SPH110 and later versions



In the A over IP scenario, the CN version must match the WN version.

This section lists only the minimum version requirements on the CN in the A over IP scenario. When implementing an A over IP project on an existing network, check the actual version requirements on the CN against the CN project implementation procedures.

1.4 Version Requirements for IPCLK Server (Huawei)

IPCLK Server: IPCLK1000 V100R002C01SPC200 and later versions

This version applies to IPCLK1000 V1 and V2 hardware platforms.

This version supports only IEEE 1588 V2 and does not support the private IPCLK protocol.

The BTS3900 in GBSS 9.0 does not support the private IPCLK server any longer and supports only IEEE 1588 V2.

In the Abis-over-IP scenario, the IPCLK server version must match the BTS version of the BTS3900/BTS3012 in GBSS 9.0.



2 Configuration Requirements

This chapter describes only speech configuration parameters in the A over IP scenario. For transmission configurations, see the GSM Initial Configuration Guide, GBSS

Reconfiguration Guide, and BSC/BTS IP GSM Deployment Guide.

2.1 Configuration Requirements on WN

2.1.1 Configuration of Speech Version and Rate Set (GBSS 9.0/12.0 A over IP)

1. All MSCs and BSCs are configured with AMR full-rate (FR) codec set 1 (12.20 kbit/s, 7.40 kbit/s, 5.90 kbit/s, and 4.75 kbit/s) and AMR half-rate (HR) codec set 1 (7.40 kbit/s, 5.90 kbit/s, and 4.75 kbit/s). Subsets in other bitmaps are not allowed.

2. All cells are configured with the same speech version and rate set.

Command:

SET GCELLCCAMR:CELLID=0, IDTYPE=BYID, RATECTRLSW=ALG1, ACTCDSETF=4_75KBIT/S-1&5_15KBIT/S-0&5_90KBIT/S-1&6_70KBIT/S-0&7_40KBIT/S-1&7_95KBIT/S-0&10_2KBIT/S-0&12_2KBIT/S-1,…;

Speech versions are configured in cell properties, including FR (full-rate version 1), EFR (full-rate version 2), FAMR (full-rate version 3), HR (half-rate version 1), and HAMR (half-rate version 3).

Command:

SET GCELLCCACCESS:CELLID=0, IDTYPE=BYID, VOICEVER=FULL_RATE_VER1-1&FULL_RATE_VER2-1&FULL_RATE_VER3-1&HALF_RATE_VER1-1&HALF_RATE_VER2-0&HALF_RATE_VER3-1&FULL_RATE_VER5-0,…;


http://support.huawei.com/support/pages/kbcenter/view/product.do?actionFlag=searchManualTableOfContents&web_doc_id=SE0000448983&doc_type=ProductManual

http://support.huawei.com/support/pages/kbcenter/view/product.do?actionFlag=searchManualTableOfContents&web_doc_id=SE0000448983&doc_type=ProductManual


2.1.2 BSC Software Parameter Setting (GBSS 9.0 A over IP)

Internal Handover Request Message Switch

During AMR handover between FR and HR, the BSC sends the Internal Handover Request message to the MSC, informing the CN of the AMR change. The BSC controls this function by using bit 13 in reserved parameter 3. In reserved parameter 3, bits are numbered 0 to 15 from right to left.

1. To enable the function, set bit 13 in reserved parameter 3 to 0.

2. To disable the function, set bit 13 in reserved parameter 3 to 1.

Table 2-1 Bits 0 to 13 in reserved parameter 3

Reserved Parameter 3

0xFFFF

Initial JitterBuffer length (corresponding to JttTime)

Bits 0–7

[20, 40, 60, 80, 100]: initial JitterBuffer length

Other values are invalid. The default is 40.

TC ensures the correctness of this parameter.

IDRQ-compatible solution

Bit 8

1: By using the MM NULL message

0: By transmitting four consecutive IDRQ messages

IDRQTEST

Type of ID in IDRQ Bit 91: IMSI

0: IMEIIDRQTEST

Transmitting MM NULL in IDRQ?

Bit 101: Yes

0: NoIDRQTEST

Protocol version supported by Packet Assignment Command

Bit 111: R6

0: R7DTM

Bit 12

1: Sets the dynamic TRX adjustment switch dynamically to keep original processing.0: Sets the dynamic TRX adjustment switch dynamically to force call handover.

CMCC sets the dynamic TRX adjustment switch dynamically. In this case, call drop may occur and call release may become slow.

Bit 13

1: In the A over IP scenario, AMR handover occurs as specified in the protocol. If the rate set after handover is a compatible subset of the rate set before handover, the handover

This parameter is set for compatibility with TrFO on the CN in A



occurs within the BSC. Otherwise, the handover occurs with codec conversion.

0: In the A over IP scenario, AMR handover occurs with codec conversion if the rate set after handover differs from the rate set before handover.

over IP

Speech Version Selection Strategy During Handover in A over IP Scenario

The BSC controls the speech version selection strategy during intra-BSC handover by using bits 14 to 15 in reserved parameter 3.



0xFFFF Speech version selection strategy during intra-BSC handover

Bits 14–15

0: MSC strategy

1: BSC strategy

2: speech version in originating cell preferred

Value 0 is recommended. If a value beyond the allowed range is entered, the system sets the parameter to 0 automatically.

SPC720 This parameter indicates the strategy by which the BSC selects the speech version during intra-BSC handover in the A over IP scenario. If this parameter is set to MSC Strategy, the BSC selects the speech version in the speech version priority sequence carried in the MSC assignment. If this parameter is set to BSC Strategy, the BSC selects the speech version in this priority sequence: FR AMR-WB, FR AMR, EFR, FR, HR AMR, and HR. If this parameter is set to Speech version in originating cell preferred, the BSC selects the speech version in the originating cell. If the terminating cell does not support the speech version in the originating cell, the BSC selects the speech version in the speech version priority sequence carried in the MSC assignment.

When upgrading the BSC from BSC6000 to BSC6900, set this parameter in the BSC6900 according to the speech version selection switch in the BSC6000. If speech version selection is enabled in the BSC6000, set this parameter to 2 in the BSC6900. If speech version selection is disabled in the BSC6000, set this parameter to 0. When upgrading



the BSC6900 from a version earlier than BSC6900V900R11SP720 to BSC6900V900R11SP720 or a later version, set this parameter to 2.

When this parameter is set to BSC Strategy, speech quality may be improved but TrFO may be unavailable.

1. If Speech Version Selection Strategy During Intra-BSC Handover is set to MSC Strategy, the BSC selects the speech version after intra-BSC handover in the speech version priority sequence carried in the MSC assignment.

2. If Speech Version Selection Strategy During Intra-BSC Handover is set to BSC Strategy, the BSC selects the speech version after intra-BSC handover in this priority sequence: FR AMR-WB, FR AMR, EFR, FR, HR AMR, and HR. In addition, the BSC selects the AMR rate set in the following priority sequence:

FR: s1, s14, s7, s12, s6, s5, s10, s4, s9, s3, s8, s2, and s0

HR: s1, s5, s10, s4, s9, s3, s8, s2, and s0

Where s1 is the optimal configuration recommended in the protocol.

3. If Speech Version Selection Strategy During Intra-BSC Handover is set to Speech version in originating cell preferred, the BSC selects the speech version (including the rate set) in the originating cell after intra-BSC handover. If the terminating cell does not support the speech version in the originating cell, the BSC selects the speech version in the speech version priority sequence carried in the MSC assignment.

Value 0, that is, MSC Strategy, is recommended for this parameter. In the case of upgrade, however, set this parameter the same as the value before the upgrade. To query the parameter, run the following command:

LST OTHSOFTPARA: LstFormat=VERTICAL;

Run this command to query reserved parameter 3. Figure 2-1 shows a query result example.

Figure 2-1 Querying reserved parameter 3

Therefore, set bits 13 to 15 in reserved parameter 3 to 0. That is, set reserved parameter 3 to decimal 8191 (hex 0x1FFF) by using the following command:



SET OTHSOFTPARA: BSCRESERVEDPARA3=8191;

2.1.3 BSC Software Parameter Setting (GBSS 12.0 A over IP)

Internal Handover Request Message Switch

During AMR handover between FR and HR, the BSC sends the Internal Handover Request message to the MSC, informing the CN of the AMR change. The BSC controls this function by using bit 13 in reserved parameter 3. In reserved parameter 3, bits are numbered 0 to 15 from right to left.

1. To enable the function, set bit 13 in reserved parameter 3 to 0.

2. To disable the function, set bit 13 in reserved parameter 3 to 1.



0xFFFF

Initial JitterBuffer length (corresponding to JttTime)

Bits 0–7

[20, 40, 60, 80, 100]: initial JitterBuffer length

Other values are invalid. The default is 40.

TC ensures the correctness of this parameter.

IDRQ-compatible solution

Bit 8

1: By using the MM NULL message0: By transmitting four consecutive IDRQ messages

IDRQTEST

Type of ID in IDRQ Bit 91: IMSI

0: IMEIIDRQTEST

Transmitting MM NULL in IDRQ?

Bit 101: Yes

0: NoIDRQTEST

Protocol version supported by Packet Assignment Command

Bit 111: R6

0: R7DTM

Bit 12

1: Sets the dynamic TRX adjustment switch dynamically to keep original processing.

0: Sets the dynamic TRX adjustment switch dynamically to force call handover.

CMCC sets the dynamic TRX adjustment switch dynamically. In this case, call drop may occur and call release may become slow.

Bit 131: In the A over IP scenario, AMR handover occurs as specified in the protocol. If the

This parameter is set for



rate set after handover is a compatible subset of the rate set before handover, the handover occurs within the BSC. Otherwise, the handover occurs with codec conversion.

0: In the A over IP scenario, AMR handover occurs with codec conversion if the rate set after handover differs from the rate set before handover.

compatibility with TrFO on the CN in A over IP

Set reserved parameter 3 by using the following command:

SET OTHSOFTPARA: BSCRESERVEDPARA3=57343;

Speech Version Selection Strategy During Handover in A over IP Scenario

Set the speech version selection policy during intra-BSC handover by using SET AITFOTHPARA.

Run the following command to set this parameter to MSC Strategy:

SET AITFOTHPARA: CNNODEIDX=XX, SpeechVerStrategyInAss=MSC_STRATEGY;

2.2 Configuration Requirements on CN (Huawei)

2.2.1 Configuring the Protocol in A over IP (Standard Protocol in A over IP)

The A over IP interface in BSC6900V900R011 is specified in a standard 3GPP protocol. In the MSC, configure BSC Bearer Type as IPSTD (IP Type of standard).

Figure 2-1 Configuring the protocol in A over IP



2.2.2 Configuring the AMR Rate Set (Standard Protocol in A over IP)

On the CN, configure HR AMR and FR AMR as S1.

Network-supported HR AMR list = D(7400bit/s)

= F(5900bit/s)

= H(4750bit/s)

Network-supported FR AMR list = A(12200bit/s)

= D(7400bit/s)

= F(5900bit/s)

= H(4750bit/s)

Command:

MOD MGW: MGWNAME="PNHMGW01", TRNST=SCTP, HRAMRR=RATE475-1&RATE515-0&RATE590-1&RATE670-0&RATE740-1&RATE795-0, FRAMRR=RATE475-1&RATE515-0&RATE590-1&RATE670-0&RATE740-1&RATE795-0&RATE102-0&RATE122-1;

2.2.3 Configuring TrFO Compatible with AMR FR/HR (Standard Protocol in A over IP)

Switch for TrFO Compatible with AMR FR/HR (UMG)

Table 2-1 Bit 8 in software parameter P13

Software Parameter ID

Bit Change Description Service Pack

13 8 Switch for TrFO compatible with AMR FR/HR

1: Disables TrFO compatible with AMR FR/HR. This is the default.

0: Enables TrFO compatible with AMR FR/HR.

In A over IP scenario, run MOD SET to configure AMR FR codec set 1 (12.20 kbit/s, 7.40 kbit/s, 5.90 kbit/s, and 4.75 kbit/s) and AMR HR codec set 1 (7.40 kbit/s, 5.90 kbit/s, and 4.75 kbit/s).

V200R008C03SPH106



This function must match the WN version. Before enabling the function, ensure that the BSC and BTS support the function.

In the case of BSC, BSC6900V900R011C00SPH728 and later versions support this function. In the case of BTS3900, BTS3000V100R009C00SPC081 (outside China)/BTS3000V300R009C00SPC021 (released in the first quarter of 2011 in China) and later versions support this function. In the case of BTS3012, the version released in the first quarter of 2011 and later versions support this function.

If any existing BTS does not match the function, do not enable the function.

When enabling this function, disable Internal Handover Request message switch. As specified in "Internal Handover Request Message Switch" in section 2.1.2 "BSC Software Parameter Setting (GBSS 9.0 A over IP)", set bit 3 in reserved parameter 3 to 1.

Optimization Parameters for TrFO Compatible with AMR FR/HR (UMG)

This parameter applies to the following two scenarios:

Scenario 1

Assume that you set bit 9 in software parameter P13 to 0. In the A over IP scenario, during call handover from non-TrFO to TrFO, the CMU sends a rate decrease request to the VPU. The VPU then decreases the rate to the initial. Therefore, previous rate mismatch problems affecting speech quality are prevented, such as loss of frame, splitting sentences, and missing words.

MOD SFP: ID=P13, MODTYPE=BIT, BIT=9, BITVAL=0;

Table 2-1 Bit 9 in software parameter P13

Software Parameter ID

Bit

Change Description Service Pack

P13 9 Default: 1

1: Disables the function and keeps original processing.

0: Enables the function. During handover from non-TrFO to TrFO compatible with AMR FR/HR in the A over IP scenario, a rate decrease request is sent to the VPU.

V200R008C03SPH110

Scenario 2

Assume that you enable UP optimization by using SET UPPARA. In the A over IP UP scenario, if inter-cell handover occurs on a call over a gateway (due to an AMR rate change) when the calling listens to the ringback tone or intelligent tone, the VPU changes the audio playing rate. Therefore, the intermittent time is decreased and the calling is exempted from intermittent tones. The speech quality is optimized.SET UPPARA: RC2CMR=OPEN, CMR2RC=OPEN;



2.2.4 Configuring Other Software Parameters on CN (Standard Protocol in A over IP)

Configure other software parameters on the CN according to sections 2.4.3, 2.5.3, 2.7, 2.8, and 2.9 in the A over IP Reconstruction Guide available at http://support.huawei.com/support/DocView.do?doc_id=SC0000588189&doc_type=123-2.


http://support.huawei.com/support/DocView.do?doc_id=SC0000588189&doc_type=123-2


3 Precautions

3.1 Upgrading GBSS 8.1 IP to GBSS 9.0 IPTo provide the A over IP or Abis over IP interface on existing sites, upgrade the sites to BSC6900 and matching BTS versions. The procedures and key points are listed as follows:

1. Before upgrading the BSC6000 to BSC6900V900R011, check with the CN engineers whether the MSC and UMG on the CN support the standard A over IP protocol. If the CN version does not match the requirements, upgrade the CN.

2. BTS3900/BTS3012 versions earlier than BTS3900V300R008C11SPC039/BTS3012V300R008C12SPC026 have a defect. In the Abis-over-IP scenario, if the BTS interworking with the BSC6900 connects multiple calls to the network, an exception may occur on the BTS. The BTS needs to be reset at the near end. Therefore, upgrade the BTS3900/BTS3012 to BTS3900GSM V300R008C11SPC039/BTS3012V300R008C12SPC026 or a later version beforehand.

3. Upgrade the iManager M2000 to iManager M2000 V200R009.

4. Upgrade the BSC6000 to BSC6900V900R011. After the upgrade, change BSC Bearer Type to IPSTD (IP Type of standard) in the MSC.

5. On the iManager M2000, upgrade the BTS to recommended versions in one click. Before the upgrade, change the reference clock source type to internal clock (free-run) for the BTS.

6. Upgrade the IPCLK server to a recommended version.

7. Set the reference clock source type to IP_Time (IP clock) and the IP clock protocol type to PTP (IEEE 1588 V2) for the BTS.

In the Abis-over-IP scenario, upgrade the BTS3900/BTS3012 to GBSS 8.1 (as described earlier) before upgrading the BTS3900/BTS3012 to GBSS 9.0.

In the Abis-over-IP scenario, after upgrading the BTS3900/BTS3012, set the IP clock protocol type to PTP (IEEE 1588 V2) for the BTS.



3.2 GBSS 8.1 A IP Precaution BulletinSee the GSM BSC6000 Precaution Bulletin on Silence in Conversation in AMR-Enabled A over IP Scenario and Version Policies in IP-Based Scenario-20100529-A-V1[1].0.zip (available at http://support.huawei.com/support/DocView.do?doc_id=SC0000584222&doc_type=TechPost).

3.3 GBSS 9.0 IP Precaution Bulletins and Key Problems

Table 3-1 GBSS 9.0 IP key problems

No. Problem Preventive Measure

NE Faulty Version Number

Solution Version Number

1 In the A over IP scenario, UDPMUX in RTP header compression causes loss of packet in the BTS, affecting the MOS.

Disable RTP compression.

BSC6900 V900R011C00SPH735 and earlier versions

2 In the A over IP scenario, UDPMUX in RTP header compression causes data service creation failure.


BSC6900 V900R011C00SPH735 and earlier versions

V900R011C00SPH750 and later versions

3 In the IPoE1 scenario, if the LCP request received from the peer carries no MRU or an MRU equal to or greater than 1500, the BTS fails to start.

Set the MRU to less than 1500 for the peer transmission device.

BTS3900 V100R009C00SPC087 and earlier versions

V100R002C00SPC230 and earlier versions

V100R009C00SPC088 and later versions


4 In the VLAN scenario, after Abis-over-TDM changes to Abis-over-IP, the BTS fails to set up an IP link dynamically.

Set the ARP table aging time to 5 minutes or less for the peer transmission device.





5 If the change from Abis-over-TDM to Abis-over-IPoE1 is complete in hardware but incomplete in software, the TMU in the BTS3012 reports a software alarm repeatedly every about 22 minutes. Every time when the alarm is reported, the BTS3012 is reset.

Change the BTS data configurations immediately after you change the BTS hardware.

BTS3012 BSC6900V900R011C00SPH735 and earlier versions

BTS3012V200R009C00SPC002 and earlier versions

BSC6900V900R011C00SPC752 and later versions


http://support.huawei.com/support/DocView.do?doc_id=SC0000584222&doc_type=TechPost


Table 3-2 GBSS 9.0 IP precaution bulletins

No. Precaution Bulletin Number

Name Description Involved Version

Solution Version

1 SE0000467716

SingleRAN & GSM Precaution on Reference Clock Abnormal Alarms Generated on the sites which get Clock from IPCLK Server-20100726-A-V1.0

The alarm is generated in each BTS get clock from IPCLK Server, leading to a negative impact on KPIs, such as the handover KPI, and user experience.

BTS3000V300R009C00SPC010 and earlier patch releases in BTS3000V300R009C00BTS3000V200R009C00SPC002 and earlier patch releases in BTS3000V200R009C00

BTS3000V100R009C00SPC077 and earlier patch releases in BTS3000V100R009C00

BTS3012: BTS3000V200R009C00SPC015 and later versionsBTS3900: BTS3000V100R009C00SPC079 and later versions

2 SE0000455059

SingleRAN BSC6900V900R011 Precaution Bulletin on Turning Off the Global Route Switch in newly deployed BSC6900-20100514-A-V1.0

If the new BSC6900 with the FG2c, GOUc or UOIc boards, some services are unavailable. Or, services are unavailable when ports on the FG2c, GOUc or UOIc board are switched over or faulty, or the FG2c, GOUc/, or UOIc board is switched over or faulty.

Versions earlier than BSC6900V900R011C00SPC720

BSC6900V900R011C00SPC720

3 SE0000457683

SingleRAN BSC6900V900R011 Precaution Bulletin on Incoming BSC Handover Failure in AOIP Scenarios-20100527-A-V1.0

In A over IP scenarios, if the incoming BSC Handover Request carries the IMSI IE, the handover from any surrounding BSC to this BSC fails. Therefore, the call is dropped.


BSC6900V900R011C00SPC720

4 SE0000453578

SingleRAN BSC6900V900R011 Precaution Bulletin on Disruption of Parts of SCTP Links and

If the routes of two interface boards in one BSC6900 subrack have the network segment inclusion relationship, part of the SCTP links


BSC6900V900R011C00SPC710





Solution Version

IP Path-20100504-A-V1.0

carried on the route may be disrupted when the output port state of one route changes (such as port switchover, switchover or failure in the board that is carried on the port, port physical state change and etc).

5 SC0000597479

SE0000470667 SingleRAN BSC6900 Precaution Bulletin on Verifying the Validity of Network Parameters in IP-Based Mode-20100811-A-V1.0

All versions Network configuration constraints

6 SC0000612850

Precaution Bulletin on Activation Failure in Abis-over-IP BTS That Uses Non-IP Clock Source and That Does Not Apply for License for IEEE 1588 V2 Clock over IP

In the Abis-over-IPoFE scenario, whether newly deployed or transformed from the Abis-over-TDM scenario, if the BTS extracts a clock from other than the IP clock source and does not apply for the license for IEEE 1588 V2 clock over IP, the BTS may fail to be activated. The failure cause indicates such information. The clock protocol type is set to PTP (IEEE 1588 V2). The license for IEEE 1588 V2 clock over IP (per TRX), however, is disabled. The clock protocol type mismatches the license setting.


BSC6900V900R011C00SPC728

7 SE0000457684

SingleRAN BSC6900V900R011 Precaution Bulletin on the Startup Failure in the GBTS Carried on FG2a or GOUa after GBTS Reset-

In the case that the following three conditions are met:

(1) IP transport is applied on the Abis interface (Abis over IP).

Versions earlier than BSC6900V900R011C00SPH711

BSC6900V900R011C00SPH711





Solution Version

20100527-A-V1.0 (2) A static IP address is set for the GBTS, and the packets intended for the static IP address are transmitted from the FG2a/GOUa board.

(3) The active Ethernet port is on the standby board or the active and standby FG2a/GOUa boards are switched.If the GBTS is reset, it fails to start because the DHCP process fails. As a result, the GBTS services are disrupted.

This problem is related only to the GBTS. The NodeB does not have this problem.

8 SC0000576899

SingleRAN BTS3900&GSM BTS3000 GBTS Precaution Bulletin on Link Setup Failure During Static-IP-based IPoFE Transmission in VLAN Scenario -20100421-A-V1.0

If the GBTS uses a static IP address during IPoFE transmission in a VLAN, the GBTS fails to set up a link.

If the GBTS uses a DHCP-assigned IP address or carries out IPoE1 transmission, the problem does not occur.

BTS3000V300R009C00SPC001


BTS3000V300R009C00SPC011 and later versionsBTS3000V100R009C00SPC072 and later versions



3.4 GBSS 12.0 IP Precaution Bulletins and Key Problems

Table 3-1 GBSS 12.0 IP precaution bulletins and key problems

No. Problem Preventive Measure

NE Faulty Version Number

Solution Version Number

1 In the Abis-over-IPoFE VLAN scenario, if a transmission delay of more than 10 ms exists between the BTS and the BSC, the IP-based BTS may start slowly or fail to start.

Set the VLAN Property to Hybrid and the PVID to the actual VLAN ID for the peer transmission device.





2 In the A over IP scenario, UDPMUX in RTP header compression causes loss of packet in the BTS, affecting the MOS.


BSC6900 BSC6900V900R012C01SPH510 and earlier versions

3 In the A over IP scenario, UDPMUX in RTP header compression causes data service creation failure.


BSC6900 BSC6900V900R012C01SPC500 and earlier versions

BSC6900V900R012C01SPC512 and later versions

4 In the IPoE1 scenario, if the LCP request received from the peer carries no MRU or an MRU equal to or greater than 1500, the BTS fails to start.

Set the MRU to less than 1500 for the peer transmission device.



5 In the VLAN scenario, after Abis-over-TDM changes to Abis-over-IP, the BTS fails to set up an IP link dynamically.

Set the ARP table aging time to 5 minutes or less for the peer transmission device.



6 If the change from Abis-over-TDM to Abis-over-IPoE1 is complete in hardware but incomplete in software, the TMU in the BTS3012 reports a software alarm repeatedly every about 22 minutes. Every time when the alarm is reported, the BTS3012 is reset.

Change the BTS data configurations immediately after you change the BTS hardware.

BTS3012 BSC6900V900R012C01SPH510 and earlier versions




3.5 GBSS 9.0 Network Problem Avoidance Guides

See the BSC6900 GU Guide to Avoiding Network Problems (V900R011)-20110224-A-V1.5.doc (available at http://support.huawei.com/support/pages/kbcenter/view/product.do?actionFlag=detailProductSimple&web_doc_id=SE0000454366&doc_type=123-2 2).

See the Guide for Avoiding Network Problems in GSM9.0&SRAN3.0 DBS3900&BTS3900&BTS3900A-20110118-A-V1.7 (available at http://support.huawei.com/support/pages/kbcenter/view/product.do?actionFlag=detailProductSimple&web_doc_id=SE0000477371&doc_type=123-2).

3.6 GBSS 12.0 Network Problem Avoidance GuidesSee the BSC6900 GU Guide to Avoiding Network Problems (V900R012)-20110224-A-V1.2 (available at http://support.huawei.com/support/pages/kbcenter/view/product.do?actionFlag=detailProductSimple&web_doc_id=SE0000479427&doc_type=123-2).

3.7 A over IP Restrictions on Early BTS Products like BTS30 and BTS312

In early BTS products like BTS30 and BTS312, A over IP and AMR are mutually exclusive. Those products have passed their EOM and LODSP. No more functions are developed for the products. Therefore, when a customer requires IP-based transmission in an existing BTS30 or BTS312 device, guide the customer to replace the BTS with a later one.

If an existing BTS30 or BTS312 device cannot be replaced with later ones, remove AMR from the BTS and then deploy A over IP transmission in the BTS. In this case, the BTS supports only EFR, FR, and HR codec.

For details, see the GBSS9.0 GSM IP Sales Strategy of GSM IP Transmission V1.0 (available at http://3ms.huawei.com/mm/docMaintain/mmMaintain.do?method=showMMDetail&f_id=GSM201009130022).

3.8 TOC in GSM_HR (GBSS 9.0 A over IP)The draft on the A over IP solution, draft-ietf-avt-rtp-gsm-hr-03 (that will be identified as an official standard soon), changes the GSM_HR length. The TOC byte is added before the payload, identifying the frame type as speech frame, non-speech frame, or empty frame.

This function is available in BSC6900V900R011C00SPH726 and later versions. In earlier versions, this function causes a no-audio problem to an HR channel.







3.9 A over IP Interworking with Competitors' Products

1. NSN

− The interworking with NSN products is tested in a lab of Germany IOT in Düsseldorf and in a lab of China Mobile. The tested version is GBSS 12.0.

− Currently, this interworking solution finds commercial application in Turkey VDF and Sweden Telenor. In Turkey VDF, GBSS 9.0 is deployed. The site involves 10 BTS3900s under the control of one BSC. In Sweden Telenor/Tele2, SRAN5.0 is deployed. The site involves 200 BTS3900s under the control of two BSCs.

2. Ericsson

− The interworking with Ericsson products is tested in a lab of Germany IOT in Düsseldorf and in a lab of China Mobile. The tested version is GBSS 12.0.

− Currently, this interworking solution finds no commercial application.

3. ZTE

− The interworking with ZTE products is tested in a lab of China Mobile. The tested version is GBSS 12.0.

− Currently, this interworking solution finds no commercial application.

3.10 A over TDM/A over IP Dual-Stack Mode (GBSS12.0)

1. The A over TDM/A over IP dual-stack mode is available in BSC6900V900R012C01 and later versions. This function must match the CN version.

2. In Huawei CN products, the A over TDM/A over IP dual-stack mode is available in CS9.0. This version is expected to be released in the first quarter of 2011.

3. Currently, only ZTE announces that their CN products support the dual-stack mode. (No interworking test or commercial interworking solution has been carried out between ZTE CN products and Huawei BSC products). Ericsson and NSN have no clear roadmaps in terms of the dual-stack mode.

4. The A over TDM/A over IP dual-stack solution is a transient configuration for A-interface transformation. Do not use the solution for a long term.



4 Attachment

4.1 SRAN IP transmission document collection

4.2 GRAN&CN Parameter Check


Documents

Version Policies and Configuration Requirements for IP-Based GSM-20110421-A-V1.3