0% found this document useful (0 votes)
69 views10 pages

Design Note

This document describes software changes needed in a Base Station Controller (BSC) to implement internal handover procedures according to 3G mobile telecommunications specifications. Key changes include supporting a new incoming handover flag, handling a list of cells rejected by mobile stations and an associated timer, including synchronization indication in handover commands, and enabling half-rate traffic channels. Impacts to the BSC software components BSSAP and RFMGT are covered, as well as changes to the system database. Internal handover between full- and half-rate channels is also addressed.

Uploaded by

Duc Nguyen
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
69 views10 pages

Design Note

This document describes software changes needed in a Base Station Controller (BSC) to implement internal handover procedures according to 3G mobile telecommunications specifications. Key changes include supporting a new incoming handover flag, handling a list of cells rejected by mobile stations and an associated timer, including synchronization indication in handover commands, and enabling half-rate traffic channels. Impacts to the BSC software components BSSAP and RFMGT are covered, as well as changes to the system database. Internal handover between full- and half-rate channels is also addressed.

Uploaded by

Duc Nguyen
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

DESIGN NOTE

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . REFERENCED DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LIST OF ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 GENERAL DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 EN_IC_HO Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 T7 Timer Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 MS_CELL_REJ_LIST and TMS_CELL_REJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4 Assumption of No Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5 Availability of HalfRate TCHs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Sync Indication in the Construction of Handover Command messages . . . . . . . . . . . . . 2.7 8k bits/s Submultiplexing on the Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8 Internal Handover between HR and FR channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 BSC SOFTWARE IMPACTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 BSSAP IMPACTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1 New States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2 New Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.3 Modified Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.4 New Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.5 New Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.6 New Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 RFMGT IMPACTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1 New States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2 New Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.3 Modified Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.4 New Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.5 New Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 DATABASE IMPACTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 03 02 01 960426 951020 950508 DATE CHANGE NOTE MCD/TD/SA MCD/TD/BDC/VH323 S.di Giorgio AMCF E.Blanckaert BELL S.di Giorgio AMCF K.V.d.bossche BELL APPRAISAL AUTHORITY DNINTERNAL_HANDOVER RELEASE 4 2 3 3 4 5 5 6 6 6 6 6 6 6 6 6 7 7 7 7 7 7 8 8 10 10 10 10 10 10 10

MCD/TD/BDC/ VH323 S.Das Gupta BELL S.Das Gupta BELL ORIGINATOR

1AA 00014 0004 (9007) A4 ALICE 03.10

ED

ED

03 214 73056 ADAA DS 1 / 10

MCD

1AA 00014 0004 (9007) A4 ALICE 03.10

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

ED
Table 1. Determination of Channel Rate to send to TCHRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

MCD

LIST OF FIGURES AND TABLES

03

214 73056 ADAA DS

2 / 10

HISTORY
Version Ed.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Prop. 01 01 01

Date 06/01/95 06/02/95 17/03/95

Author S.Das Gupta S.Das Gupta S.Das Gupta

Comments First Draft Incorporates decisions from R4TLD341 Incorporates decisions R4TLD342. L1 approved from

4.0.0.0 4.0.0.1 4.0.1.0

00a 00b 00c

4.1.0.0

01

01

08/05/95

S.Das Gupta

Incorporates comments (by mail, from Paris) on previous version. L2 approved. Changes due to introduction halfrate TCH added. Changes due to review of 20/06/95 (see R4TLD344) Includes changes due to comments by mail. Level2 approved. 2117. CRQs/1533,1544 &

4.1.0.1

02

01

29/05/95

S.Das Gupta

4.1.0.2

02

02

28/06/95

S.Das Gupta

4.1.1.0 4.2.0.0

02 02

03 04

18/08/95 20/10/95

S. Das Gupta S. Das Gupta

4.3.0.0

03

01

26/05/96

M.Baughan

CRQs/1662, 1663, 1664, 1694 & 1903.

REFERENCED DOCUMENTS
[ 1 ] INTERNAL HANDOVER 3BK11202 0056 DSZZA [ 2 ] EXTERNAL HANDOVER 3BK 11202 0057 DSZZA [ 3 ] DN_EXTERNAL_HANDOVER 214 73057 ADAA DS [ 4 ] CIPHERING PROCEDURE 3BK 11202 0054 DSZZA [ 5 ] TELECOM_ABBREVIATIONS 214 95524 ADAA DS [ 6 ] DEDICATED RADIO RESOURCE CONTROL 3BK 11202 0066 DSZZA [ 7 ] DNNORMAL_ASSIGNMENT 215 06720 ADAA DS

1AA 00014 0004 (9007) A4 ALICE 03.10

ED

03 214 73056 ADAA DS 3 / 10

MCD

[ 8 ] DNDEDICATED_RADIO_RESOURCE_CONTROL 214 73065 ADAA DS


All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

[ 9 ] Changes required in the Alcatel BSS for its interworking with the faulty Motorola MS SYS/081 [ 10 ]European digital cellular telecommunications system (Phase 2); Recommended infrastructure measures to overcome specific Phase 1 Mobile Station (MS) faults GSM 09.94 [ 11 ] TFD 8.7A Optimised submultiplexing scheme for Half Rate channels on the Abis interface (8k bits/s submultiplexing) 3BK 10204 0105 DRZZA [ 12 ]STR BSC ARCHITECTURE (PARTS 1 & 2) 214 95521 ADAA DS [ 13 ]STR SDD TEL ARCHITECTURE 215 15697 ADAA DS

LIST OF ABBREVIATIONS
The meaning of abbreviations used in this document may be found in [5].

1AA 00014 0004 (9007) A4 ALICE 03.10

ED

03 214 73056 ADAA DS 4 / 10

MCD

1 INTRODUCTION 1.1 SCOPE


This Design Note describes the changes required in the BSC implementation of the Internal Handover procedure in going from Release3 to Release4. The following changes related to the features listed below apply equally to external handover as well : Enable incoming handover flag (EN_IC_HO) List of cells rejected by the MS (MS_CELL_REJ_LIST), and associated timer (T_MS_CELL_REJ) Synchronisation Indication information in Handover Command messages 8k bits/s Submultiplexing on the Abis interface. So, while brief descriptions have been provided here, the full description of the new features and impacts (for handover in general) is to be found in the design notes for external handover [3] and dedicated radio resource control [8]. Changes required to support Int HO in a dualrate environment are also described here. Some of these changes are dependant on the contents of [7]. The following additional changes related to the features below also apply to internal handover : Internal handover between FR and HR traffic channels. The impacts of CRQs/1533, 1544, 1648, 1662, 1663, 1664, 1694, 1903 and 2117 have also been taken into account.

1AA 00014 0004 (9007) A4 ALICE 03.10

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

ED

03 214 73056 ADAA DS 5 / 10

MCD

2 GENERAL DESCRIPTION
The following changes are identified in [1] and [2] : the new flag EN_IC_HO; changed functionality for the T7 timer; the new entities MS_CELL_REJ_LIST and TMS_CELL_REJ [2] ; use of halfrate TCHs; and a different way of interpreting No Encryption not allowed. These features have an impact on the BSC implementation of the handover procedure.

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

2.1 EN_IC_HO Flag


The new flag EN_IC_HO is defined on a percell (BTS) basis, and is used to enable or disable incoming handovers.

2.2 T7 Timer Functionality


The functionality of the T7 timer in Rel4 (as defined in [2]) is completely different from earlier releases. However, as far as Int HO is concerned, there is strictly speaking no impact. The changes due to this feature are described in [2] and [6].

2.3 MS_CELL_REJ_LIST and TMS_CELL_REJ


For details on these features see [2,3].

2.4 Assumption of No Encryption


An unencrypted channel shall not be allocated and used if the MSC has not allowed the use of No Encryption in the Permitted Algorithms, or has not specified No encryption required in the Algorithm Identifier [4].

2.5 Availability of HalfRate TCHs


A BTS that implements HR TCHs will have all its FUs upgraded for dualrate capability. The availability of HR TCHs in any cell will be indicated by a flag HR_ENABLED defined on a percell basis.

2.6 Sync Indication in the Construction of Handover Command messages


The Synchronisation Indication OIE is to be always included in the 04.08 Handover Command sent to Phase 1 mobiles to be compliant with GSM 09.94 (this change is required for interworking with faulty Phase 1 Motorola mobiles). Refer to R4 CRQs/1533, 1543, 1544, 1648 & 2117 and to [ 9 ] and [ 10 ].

2.7 8k bits/s Submultiplexing on the Abis interface


On the Abis interface dynamic SM may be used for traffic channels, where a FR connection uses always a 16k bits/s channel, whereas a HR connection uses a 8k bits/s channel which then leaves the other remaining 8k bits/s free for another HR connection. Refer to R4 CRQ/1694 and to [ 11 ], [ 12 ] and [ 13 ].

2.8 Internal Handover between HR and FR channels


1AA 00014 0004 (9007) A4 ALICE 03.10

When an Internal handover between HR and FR channels there is now no need for an indication of the TCH rate in the CHANNEL MODE OIE within the Assignment/Handover Command messages because this information is also contained within the CHANNEL DESCRIPTION MIE. Refer to R4 CRQs/1662, 1663, 1664 and 1903.

ED

03 214 73056 ADAA DS 6 / 10

MCD

3 BSC SOFTWARE IMPACTS


The BSC software will be affected by the changes mentioned before. Only those features that affect the BSSAP and RFMGT modules and the DataBase are discussed here in any detail. There are major impacts on TCHRM, but those changes are described in [8].

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

3.1 BSSAP IMPACTS


3.1.1 New States No new states are required. 3.1.2 New Messages No new messages are required. 3.1.3 Modified Messages No messages are required to be modified. 3.1.4 New Parameters A new online modifiable O&M parameter HR_ENABLED (HalfRate Enabled, [1]) has been defined for this release. This flag has the effect of enabling the support of HR traffic channel speech connections when set to True, and is defined on a percell basis. A new online modifiable O&M parameter EN_IC_HO (Enable Incoming Handovers, [1]) has been defined for this release. This flag has the effect of barring incoming handovers when set to false, and is defined on a percell basis. To support the use of halfrate voice channels, two new parameters have been introduced. Each of these are defined on a perconnection basis. They are described here briefly for completeness, full details can be found in [7]. The values of these parameters are set up when the call is first established, and are not changed thereafter. 3.1.4.1 HalfRate This parameter (defined on a perconnection basis) indicates the disposition of the MS to the availability of halfrate channels, and is a CHILL set consisting of the following elements : E_HR_PROHIBITED E_HR_MANDATORY E_HR_NOT_PREFD E_HR_PREFERRED 3.1.4.2 ChangePermitted This is a BOOLEAN parameter (defined on a perconnection basis) that indicates whether the channel rate may be changed during the lifetime of the call. The value of this parameter is defined for all connections associated with a traffic channel and to which a dualrate mobile is attached.

1AA 00014 0004 (9007) A4 ALICE 03.10

ED

03 214 73056 ADAA DS 7 / 10

MCD

3.1.5 New Timers No new timers are required. However, note that the timer T7 has completely changed functionality.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

3.1.6 New Actions 3.1.6.1 EN_IC_HO Flag When selecting a (internal) cell as candidate for handover, BSSAP should first check its EN_IC_HO flag. No handover to the cell may be executed if the flag is set to false (except in the case of an intracell hand over). Any other checks on the candidate cell should be performed only after ascertaining that incoming handovers to the cell are permitted. 3.1.6.2 T7 Timer Functions. If the timer T7 is found to be running when a handover alarm arrives, any potential handover will be forced to be external. 3.1.6.3 NO_ENCRYPTION Not Allowed. An unencrypted channel shall not be allocated and used (under any circumstance) if the MSC has specified that NO_ENCRYPTION shall not be used. A cell that does not support a compatible algorithm is not a candidate for handover. 3.1.6.4 Filtering of Handover Alarms (MS_CELL_REJ_LIST & TMS_CELL_REJ) A full description of this feature and the associated entities can be found in [2,3]. Also see the Open Points section. The functionality of the candidate cells filter has to be augmented to support Halfrate TCHs. This additional filtering is necessary to remove from the candidate cells list those neighbouring cells that can not support a Channel Rate compatible to the currently assigned TCH and the capabilities of the MS. 3.1.6.5 TCH Selection To select a new TCH, BSSAP sends the 0170_SEL_CHAN message to TCHRM. The value used for Channel Rate (in the B_CH_TYPE field of this message) must retain as far as possible the flexibility of choice of channel type specified when the call was originally set up. The following table illustrates how Channel Rate should be determined for any given connection. For more details see [7] and [8]. This is applicable for both intercell and intracell handover. Value of HalfRate Value of ChangePermitted * * TRUE FALSE FALSE TRUE value of ZB_CH_USAGE * * * E_TS_US_FR E_TS_US_HRx * ChannelRate sent to TCHRM 8 9 10 8 9 11

E_HR_PROHIBITED E_HR_MANDATORY E_HR_NOT_PREFD E_HR_NOT_PREFD E_HR_NOT_PREFD


1AA 00014 0004 (9007) A4 ALICE 03.10

E_HR_PREFERRED

ED

03 214 73056 ADAA DS 8 / 10

MCD

Value of HalfRate

Value of ChangePermitted FALSE FALSE

value of ZB_CH_USAGE E_TS_US_FR E_TS_US_HRx

ChannelRate sent to TCHRM 8 9

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

E_HR_PREFERRED E_HR_PREFERRED

N.B.

* means Dont care, and E_TS_US_HRx means (E_TS_US_HR0 or E_TS_US_HR1)

Table 1. Determination of Channel Rate to send to TCHRM Before the 0170_SEL_CH message is sent, the value of the field ZB_TEMP_CH_MODE (in the connection buffer should be reset to 0. This acts as a special indication to the code in procedure Q_8160_TREAT_TCH_DCH_ACT_ACK (with modifications as described in [7]), and causes it to deduce the new (and possibly different) Channel Mode for the new TCH and store it in the ZB_TEMP_CH_MODE field (of the connection buffer). For more details see [7]. 3.1.6.6 Construction of Handover Command Message A new requirement that stems from GSM ETR 09.94 (as reported in R4 CRQs/1533, 1543, 1544 and 1648) is the logic used to determine when the OIE Synchronization Indication should be included in the 04.08 Handover Command message. Quoting from the CRQs : For Phase1 MS, the OIE is always included. For Phase2 MS, it is only included in case of synchronous handover. The format (version) of the OIE used is that specified for GSM Phase2 (irrespective of the MS phase). 3.1.6.7 Construction of Handover Performed Message In earlier releases, the Chosen Channel field in the Handover Performed message (to the MSC) was coded to indicate either SDCCH or fullrate TCH (values 1 and 8 respectively) only. With the introduction of halfrate capability, it should be possible to return a third value (10) to indicate the choice of a halfrate TCH. The required changes will have to be located in the procedure Q_XXXX_COPY_CHOSEN_CH, and are detailed in [7]. 3.1.6.8 Internal Handover between HR and FR channels When an Internal handover between HR and FR channels there is now no need for an indication of the TCH rate in the CHANNEL MODE OIE within the Assignment/Handover Command messages. This is because the FR or HR rate indication is also contained within the CHANNEL DESCRIPTION MIE of the Assignment/Handover Command messages and therefore there is no need to duplicate the same information in the CHANNEL MODE OIE. Therefore the CHANNEL MODE OIE may be omitted from the Assignment/Handover Command messages during nonDirected Retry Internal handovers between channels of the same mode (SDCCH>SDCCH and TCHanyrate>TCHanyrate Internal handover).

1AA 00014 0004 (9007) A4 ALICE 03.10

ED

03 214 73056 ADAA DS 9 / 10

MCD

3.2 RFMGT IMPACTS


3.2.1 New States No new states are required. 3.2.2 New Messages The new message 0944_CH_ RES_REQ is sent from RFMGT to the DH_TCU to request the reservation of an Abis traffic channel. For further details of this message refer to references [ 12 ] and [ 13 ]. Field B_RTS_NBR_USG in message 0944_CH_ RES_REQ indicates to the DHTCU if the speech connection is HR0, HR1 or FR useage. 3.2.3 Modified Messages No messages are required to be modified. 3.2.4 New Parameters No new parameters are required. 3.2.5 New Actions During the channel selection/reservation/activation sequence of events, message 0944_CH_ RES_REQ is sent from RFMGT to the DH_TCU to request the reservation of an Abis traffic channel. The required useage of the traffic channel is contained in field B_RTS_NBR_USG and this indicates to the DH_TCU if the speech connection is HR0, HR1 or FR. When an ESTABLISH INDICATION or ASSIGN/HANDOVER COMPLETE message is subsequently received on a new TCH, the switchthrough connection through the switch depends on the FR / HR requirements of the connection, and may dynamically change on a per call basis. If an ASSIGNMENT/HANDOVER FAILURE message is received then need to make the switchback for the TCH, and this also will depend on the FR / HR requirements of the connection. When the new channel is established after a successful Internal Handover, the FACCH Handler in RFMGT sends the 0176_CNT_SP_PATH message to the DH_TCU to start the connection of a path in the DSN. The TCU_DH then makes the appropriate switchthrough the DSN from the Abis to the A interfaces. The establishment of the new channel occurs when RFMGT in the Target BSC receives either an ESTABLISH INDICATION on the Abis interface, or if this message is missing then an ASSIGNMENT COMPLETE (intracell handover) or HANDOVER COMPLETE (intercell handover) message is received.

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

3.3 DATABASE IMPACTS


The new flag EN_IC_HO should be stored in the DATABASE on a percell basis. For more details see [ 3 ]. The new flag HR_ENABLED is stored in the DATABASE on a percell basis in domain D_HR_EN within relation R_CELL_IN.

1AA 00014 0004 (9007) A4 ALICE 03.10

END OF DOCUMENT

ED

03 214 73056 ADAA DS 10 / 10

MCD

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy