TMD B9pres 11oct05 CS Aspect Ed02

B9 Parameter Workshop Part 1: Circuit Switched (CS) Aspects
Presentation to T-Mobile, Bonn, 11 Oct 2005 Alcatel-PCS
All rights reserved 2005, Alcatel
Agenda
Page 2
B9 features and related parameters:

Enhanced E-GSM band handling Electromagnetic environment (EME) supervision Radio Measurement Statistics (RMS) improvements Voice Group Call Services (VGCS)
Features influencing the B9 channel allocation strategy for CS calls:

Enhanced E-GSM band handling Voice Group Call Services (VGCS) Intracell HO cause 30
TMD_B9_pres_CSpart / Oct 05
Enhanced E-GSM band handling Introduction (1/2)

Page 3
Feature goals in B9: full support of the

(E)GPRS service on the E-GSM TRXs of an E-GSM cell signaling in G1 band
Limitations in B7.2 and B8:

(E)GPRS service is not supported on G1 TRXs; Signaling is not supported on G1 TRXs; Only one GPRS MA; The frequency hopping shall be applied only to a set of G1 frequencies or to E-GSM uplink a set of P-GSM frequencies.
G1-GSM band
Band P-GSM G1-GSM ARFCN 1 .. 124 975 .. 1023, 0 Uplink Freq. (MHz) 890.2 to 915.0 880.2 to 890.0 Downlink Freq. (MHz) 935.2 to 960.0 925.2 to 935.0
P-GSM band 890 E-GSM downlink 915
880
G1-GSM band
925 935
P-GSM band 960

Enhanced E-GSM band handling Introduction (2/2)

Page 4
Characteristics of E-GSM in B9:

The (E)GPRS service is supported, without any constraint, on E-GSM TRXs; Mixing frequencies of P-GSM band and G1 band in the same FHS is supported. For Business cases 2, 3: all types of signaling channels (BCCH, CCCH, MPDCH, etc) are supported, without any constraint, on EGSM TRXs; For Business cases 1 only: the radio resource allocation strategy applied for P-GSM capable only MSs is different than that applied for E-GSM capable MSs
Expected gains in B9
Additional network capacity Decrease of the interference level in the P-GSM band by unloading the P-GSM TRXs
Enhanced E-GSM band handling Market View

Page 5
Business Case 1: P-GSM network extension with the frequencies in G1 band

The operator has mainly the frequency in the P-GSM band. Some frequencies in G1 band are added to the cells for capacity extension purpose.
In this Business Case, the old Phase 1 MS may still be in use in the network. In this presentation the Phase 1 MS is named as P-GSM capable only MS.
Business Case 2: DCS 1800 network extension with the frequencies in E-GSM band (without frequencies in the P-GSM band)
In this Business Case, all MSs used are at least Phase 2 MSs, as a consequence, they can decode G1 frequencies.
Business Case 3: : Full G1 network (without any frequency in the PGSM band) or network with mainly the frequencies in G1 band
In this Business Case, all MSs used are at least Phase 2 MSs, as a consequence, they can decode G1 frequencies.
Enhanced E-GSM band handling Functional description (1/3)

Page 6
The Enhanced E-GSM band handling" feature can work in two different modes :
Mode 1 : P-GSM capable only MSs are not supported
The mode 1 covers the Business Case 2 and 3. The allocation algorithm is linked to EGSM_RR_ALLOC_STRATEGY parameter set to Same behaviour for E-GSM capable MS (1)
Mode 2 : P-GSM capable only MS are supported

The mode 2 covers the Business Case 1. The allocation algorithm is linked to EGSM_RR_ALLOC_STRATEGY parameter set to Different behaviour for E-GSM capable MS (0)
The parameter EGSM_RR_ALLOC_STRATEGY is not modifiable at the OMC-R : to be set in the BSC CDE Table

Page 7
Mode 1: Support of E-GSM networks With this mode :

the E-GSM TRX is defined as follow:
frequencies in P-GSM band only or frequencies in G1 band only or mixing frequencies in P-GSM band and G1 band.
880
E-GSM
G1
890
P-GSM
915
G1
925 935
P-GSM
960
The (E)GPRS service is supported, without any constraint, on E-GSM TRXs. All types of signaling channels (BCCH, CCCH, MPDCH, ) are supported, without any constraint, on E-GSM TRXs. Resource allocation strategy: As the P-GSM capable only MS is not supported, there is not specific radio resource allocation strategy in the E-GSM cell. In particular, P-GSM capable only MS is not ensured to be allocated with P-GSM resources

Page 8
Mode 2: Support of P-GSM only MS in E-GSM networks

The main characteristics of this mode is as follows :
The radio resource allocation strategy applied for P-GSM capable only MSs is different than that applied for E-GSM capable MSs. From the radio resource allocation point of view, the meaning of E-GSM TRX is changed. An E-GSM TRX is re-defined as follow:
frequencies in G1 band only or mixing frequencies in P-GSM band and G1 band.
BCCH, CCCH, SDCCH and CBCH cannot be defined on E-GSM TRX E-GPRS services can be supported on E-GSM TRX The new radio resource allocation strategy is based on the hypotheses that all GSM900 (E)GPRS MSs are assumed E-GSM capable and compliant to Phase 2 of 3GPP standard.
Enhanced E-GSM band handling OMC-R parameters (1/2)

Page 9
HMI name Definition Subsystem Insta nce OMC-R access Type Def value Range Unit
EGSM_RR_ALLOC_ST RATEGY
Defines the radio resource allocation strategy used in EGSM cells.

0: Different behavior for E-GSM capable MS: The BSS handles differently E-GSM capable MS from P-GSM only capable MS in E-GSM cells. 1: Same behavior for E-GSM capable MS: The BSS handles in the same way only P-GSM capable MS as E-GSM capable MS in EGSM cells,
BSC
BSS
Displayed
Number
[0,1]
None
Enhanced E-GSM band handling OMC-R parameters (2/2)

Page 10
FREQUENCY_RANGE
This parameter indicates the frequency range of the cell.

0: PGSM (GSM 900), 1: DCS 1800, 2: EGSM, 3: DCS 1900, 4: PGSM-DCS1800, 5: EGSM-DCS1800, 6: GSM 850
BSC
cell
Changeabl e
Number
[0,6]
None
PLMN_FREQUENCY_ BANDS (BSC) PLMN_FREQUENCY_ BANDS (MFS)
Frequency bands used in the whole PLMN. Frequency bands used in the whole PLMN.
BSC MFS
BSS BSS
Virtual changeable Virtual changeable
Number Number
0 0
[0,3] [0,3]
None None
HMI name
Definition
Subsystem
Insta nce
OMC-R access
Type
Def value
Range
Unit
EN_LOAD_EGSM
Allows to take into account TCH resources of G1 TRXs for load evaluation. When enabled, the values of the parameters FREElevel_1 to FREElevel_4 need to be updated to number of TRX considered in the load computation.
BSC
BSC
changeable
Flag
[0,1]
None
Agenda
Page 11


EME supervision Introduction (1/3)

Page 12
Feature goals in B9:

detect situations where the emitted power is exceeding the maximum value pre-defined at commissioning per cell and per frequency band record over time the average power emitted at the BTS antenna output connector per cell and per frequency band (i.e. power evolution over time for each cell and per band) with the help of appropriate tools (e.g. A956 RNO) to:
provide warning report on the delta power between the average emitted power per cell and per band (EME_PWR_GSM resp. EME_PWR_DCS) and a predefined threshold (EME_PWR_MAX_GSM resp. EME_PWR_MAX_DCS) display evolution of EME_PWR_GSM and EME_PWR_DCS display the absolute BCCH power at the BTS antenna output connector provide statistics and tendencies on the emitted power for each cell (per band).

Page 13
Limitations in B8:
no information on the emitted power of the cell
Expected gains in B9:

secure the application of regulatory requirements anticipate situations that may imply a revision of the access restrictions collect raw data on the actual levels of emitted power collect more accurate values at the BTS level taking into account power control and DTX support dialogue with neighborhood and local authorities on sensitive sites with daily statistics

Page 14
EME supervision Functional description (1/4)

Page 15
Characteristics of EME supervision feature in B9:

1.) new BSS PM type is defined for EME: Type 33
restriction in the PMC configuration (for the EME type only) :
start-time value is forced to 00:00 and stop-time value is forced to 24:00 (in term of OMC local time) accumulation period is blocked to 1 hour
Storage of hourly indicators: during 1 month Storage of daily maximum power indicators: during 13 months

Page 16
2.) PM33 type data collection (description)

The mechanism is permanent in EVOLIUM TRE and between BSC/TCU and EVOLIUM BTS/TRE; it involves all EVOLIUM TREs and all TCUs connected to 1 or more EVOLIUM TREs:
every EVOLIUM TRE collects DL power data every TCU sends every 15 minutes (and in the same time) the message EME_DATA_REQ to all EVOLIUM TRE connected to it. after sending EME_DATA_REQ to a TRE, BSC/TCU starts a wait timer (EME_DATA_TIMER) to wait the EME_DATA_IND from this TRE. after reception of the message EME_DATA_REQ, each EVOLIUM TRE resets counters, prepares statistics and sends EME counters to the related TCU in the message EME_DATA_IND. if no EME_DATA_IND received from a given TRE by TCU before time out, the h counter value will be set to invalid. if EME_DATA_IND is delayed i.e. received by BSC after time out, the counter value is discarded by the BSC

Page 17
2.) continued: PM33 type data collection (visualisation of EME message flow between BSC and BTS)

Page 18
3.) Calculation of TRX average power at the antenna connector (AN output) takes into account:
Static power contribution:
TRE maximum power power leveling loss due to stages (ANy, AN) and cables between TRE output and BTS antenna output connector BS_TXPWR_MAX
Dynamic power contribution: Power control No power contribution:

DTX unused timeslots
EME supervision OMC-R parameters

Page 19
EME_PWR_MAX_ GSM
= operational parameters (no impact on the telecom part, but on O&M).
This threshold is the maximum power level than a BTS (cell) is permitted to emit at the BTS antenna output connector on the GSM bands (850 MHz and 900 MHz). It is set according to the size of the compliance boundary, i.e. the wider the compliance boundary, the higher the threshold value can be.If the power level exceeds this threshold, then there is some chance that the reference levels are no more respected beyond the compliance boundary.
Same definition as above but for DCS bands (1800MHz and 1900MHz) Supervision timer for the reception of the EME_DATA_IND message by the BSC
OMC
cell
changeable
Thresh old
9999
[1,999 9]
None
EME_PWR_MAX_ DCS EME_DATA_TIMER
OMC
cell
changeable
Thresh old timer
9999
[1,999 9] [0, 255]
None
BSC
BSC
changeable
sec
Agenda
Page 20


RMS improvements Introduction (1/2)

Page 21
The B9 feature RMS improvements is composed of 3 subfeatures. Feature goals in B9:

RMS improvements on AMR statistics (sub-feature RMS_I1, split into the sub-features RMS_I12 and RMS_I13): providing measurement of AMR codec usage in RMS, for optimisation of speech quality through AMR RMS improvements on TA statistics (sub-feature RMS_I2): providing statistic on RMS Timing advance, for optimisation of NW planning, through identification of resurgences and hot spots RMS improvements on TRX power statistics (sub-feature RFD 55/138315 RMS indicators storage enhancement): providing the maximum GMSK power used by each TRE at BTS antenna connector
RMS improvements Introduction (2/2)

Page 22
Limitations in B8, B7.2:

RMS on AMR (sub-feature RMS_I1): not supported in B7.2/B8 RMS on TA (sub-feature RMS_I2): only measurement reports trespassing a TA threshold are available (counter name PERC_TA_GT_TA_STAT), along with the max. measured TA (counter name MAX_TA) RMS on TRX power: not supported in B7.2/B8
Expected gains in B9:

monitoring the proper operation of AMR and the voice quality in a cell => help tuning the AMR parameters (definition of the codec subset, thresholds and hysteresis) monitoring the quality of the radio coverage and the geographical traffic distribution in a cell (identifying hot spot and resurgences/interference spots) knowing the exact GMSK power of each TRE
RMS improvements Functional description (1/4)

Page 23
General process for RMS (reminder):

The BTS collects the RMS measurement results, formats them into matrixes or vectors, and sends them to the BSC. The BSC forwards them to the OMC using the usual PM mechanism
Characteristics of RMS improvements feature in B9:

1.) RMS improvements on AMR statistics (sub-feature RMS_I1)
1.1) RMS_I12 : Bad Frame Indication per AMR codec in UL
First, following 2 vectors are filled by each TRE of the BTS: AMR FR UL BFI vector (TRX based) AMR HR UL BFI vector (TRX based) Next, for each vector listed above, there are 2 counters filled for RMS measurement reporting: one counter contains the coded measurement values the other counter contains the maximum value of all measurement values in the vector

Page 24
1.2) RMS_I13 : AMR codec usage compared to RXLEV

First, following 4 matrices are filled by each TRE of the BTS: AMR FR UL usage / UL_RXLEV (TRX based) AMR HR UL usage / UL_RXLEV (TRX based) AMR FR DL usage / DL_RXLEV (TRX based) AMR HR DL usage / DL_RXLEV (TRX based) Next, for each matrix listed above, there are 2 counters filled for RMS measurement reporting: one counter contains the coded measurement values, the other counter is a vector which contains the maximum values in each matrix row

Page 25
2.) RMS improvements on TA statistics (sub-feature RMS_I2)

There are 3 groups of RMS improvements on TA statistics: 2.1) Timing advance distribution (TRX based)
2 counters are filled (TRX based): one counter contains the coded measurement values for Timing advance distribution per TA band the other counter contains the maximum value of all measurement value
2.2) Average Rxlev per TA band

2 counters are filled: one with the coded measurement values for UL average Rxlev per TA band the other with the coded measurement values for DL average Rxlev per TA band
2.3) Average Rxqual per TA band

2 counters are filled: one with the coded measurement values for UL average Rxqual per TA band the other with the coded measurement values for DL average Rxqual per TA band

Page 26
3.) RMS improvements on TRX power statistics

One new counter (RMSpw3, TRX based) is defined, to get the maximum GMSK TRX power level applied at the BTS antenna output connector in dBm. The power takes into account the different BTS internal losses (cables, internal combiners) and the internal/ external leveling but it does not take into account the BS_TXPWR_MAX, attenuation required by the OMC_R.
RMS improvements OMC-R parameters (1/2)

Page 27
There are no new B9 parameters related to the subfeatures:

RMS improvements on AMR statistics (sub-features RMS_I12 and RMS_I13) RMS improvements on TRX power statistics
There are new B9 parameters related to the sub-feature:

RMS improvements on TA statistics (sub-feature RMS_I2)
RMS improvements OMC-R parameters (2/2)

Page 28
MEAS_STAT_TA_1
Upper limit of the first TA band, lower limit of the second TA band (for the RMS TA measurements) Upper limit of the 2nd TA band, lower limit of the 3rd TA band Upper limit of the 9th TA band, lower limit of the 10th TA band
BSC
BSS
Changeabl e
number
[1, 62]
bper
MEAS_STAT_TA_2
BSC
BSS
Changeabl e Changeabl e Changeabl e Changeabl e Changeabl e Changeabl e Changeabl e Changeabl e
number
13
[1, 62]
bper
MEAS_STAT_TA_3 MEAS_STAT_TA_4 MEAS_STAT_TA_5 MEAS_STAT_TA_6 MEAS_STAT_TA_7 MEAS_STAT_TA_8 MEAS_STAT_TA_9
BSC BSC BSC BSC BSC BSC BSC
BSS BSS BSS BSS BSS BSS BSS
number number number number number number number
19 25 31 37 43 49 55
[1, 62] [1, 62] [1, 62] [1, 62] [1, 62] [1, 62] [1, 62]
bper bper bper bper bper bper bper
RMS improvements RMS indicators (1/2)

Page 29
As standards RMS indicators they are not agregated day/week/month. They all are defined at TRX level and agregated on cell only
Ref. name
RMAMUFBV RMAMUHBV
Mnemonic
RMS_AMR_FR_UL_BAD RMS_AMR_HR_UL_BAD
Definition
Number of bad speech frames using any AMR FR codec in uplink Number of bad speech frames using any AMR HR codec in uplink
Formula
RMS44 RMS45
RMAMUFSM
RMS_AMR_FR_UL_RXLEV_UL
Number of speech frames using one AMR FR codec in uplink per Rxlev on the uplink path Number of speech frames using one AMR HR codec in uplink per Rxlev on the uplink path Number of speech frames using one AMR FR codec in downlink per Rxlev on the downlink path Number of speech frames using one AMR HR codec in downlink per Rxlev on the downlink path
RMS46
RMAMUHSM
RMS_AMR_HR_UL_RXLEV_UL
RMS48
RMAMDFSM
RMS_AMR_FR_DL_RXLEV_UL
RMS47
RMAMDHSM
RMS_AMR_HR_DL_RXLEV_UL
RMS49
RMS improvements RMS indicators (2/2)

Page 30
Ref. name
RMAXTAV RMTADIV
Mnemonic
RMS_RXLEVEL_TA_THRESHOL D RMS_TPR_TIMING_ADVANCE
Definition
10 TA bands: 9 thresholds + min + max The distribution of number of measurement reports for which the value of timing advance is in TA band The average value of RXLEV per TA band in uplink. The average value of RXLEV per TA band in downlink. The average value of RXQUAL per TA band in uplink. The average value of RXQUAL per TA band in downlink Maximum GMSK TRX power level applied at the BTS antenna output connector in dBm. The power takes into account the different losses (cables, internal combiners) and the internal/external leveling but it does not take into account the BS-TXPWR-MAX, attenuation required by the OMC_R..
Formula
TAB_PAR_MEAS_STAT_ _TA + min + max RMS50
RMTAULVV RMTADLVV
RMS_TPR_UL_RXLEV_TA_BAN D RMS_TPR_DL_RXLEV_TA_BAN D RMS_TPR_UL_RXQUAL_TA_BA ND RMS_TPR_DL_RXQUAL_TA_BA ND MAX_POWER_PER_TRX
RMS51 RMS52
RMTAUQUV RMTADQUV
RMS53 RMS54
RMTIBPWMN
RMSPw3
Agenda
Page 31


VGCS Introduction (1/2) - ASCI overview

Page 32
Advanced Speech Call Items (ASCI) are defined as additional supplementary services by GSM Phase 2+
ASCI features provide voice group and priority functionality
1.) Voice group services:
Voice Broadcast Service (VBS) - not implemented in B9
Typical trunked radio communication, point to multipoint, 1 speaker (MOC or MTC), many listener.
Voice Group Call Services (VGCS) - implemented in B9 as a pure SW feature

Typical trunked radio communication, point to multipoint, several dispatcher (MOC or MTC), many listener, subsequent talker.
2.) enhanced Multi-Level Precedence and Pre-emption service (eMLPP):

Precedence involves assigning a priority level to a call in combination with fast call set-up. Pre-emption involves the seizing of resources, which are in use by a call of a lower precedence, by a higher level precedence call in the absence of idle resources. Preemption can also involve the disconnection of an on-going call of lower precedence to accept an incoming call of higher precedence
VGCS
Introduction (2/2)- General concept of VGCS usage
External dispatchera One broadcast channel per cell and per group call One VGCH channel (TCH/SACCH/FACCH) may be allocated per cell and group calll Group call area A
Page 33
VGCS I: Group call area A Group ID 1 Dispatcher (external) a
GMSC
New calling subscriber (first period dedicated channel) Conference bridge Group ID 1
BTS
Group ID 1
BSC
Anchor MSC GCR
Group ID 1
BTS
Group ID 1
BSC
Distribution function
BTS
Relay MSC
Group call area B
Group Call Register (GCR) contains group call related data: - Group ID - Priority (network, subscriber) - Call setup class (fast, normal)
BTS
Group ID 2
BSC
Group ID 2
VGCS
Overview VGCS procedure involved O&M parameter

Page 34
VGCS Procedure
Name of involved new B9 parameters
Notification for mobile stations in idle mode Notifications for mobile stations in Group Receive Mode or (Dedicated) Group Transmit Mode Notifications for mobile stations in Dedicated Mode Paging into on-going VGCS call Notification Response Procedure Uplink Access Procedure Uplink Allocation Procedure (Subsequent Talker Procedure) Uplink Reply Procedure (listener detection)
NOTIF_PCH_THR EN_INBAND_NOTIF NOTIF_FACCH_OTHER_VGCS_CALL_THR EN_INBAND_NOTIF NOTIF_FACCH_PTP_CALL_THR EN_INBAND_PAGING INBAND_PAGING_THR T_NOTIF_RESPONSE_DELAY T3115 NY2 T_WAIT_UPLINK_REQUEST_ACK START_UPLINK_REPLY T_REPETITION_UPLINK_FREE T_WAIT_UPLINK_ACCESS WAIT_UPLINK_ACCESS T_REPETITION_CHANNEL_RELEASE
The VGCS Call Termination Procedures (when VGCS call is released by the calling subscriber)
VGCS OMC-R parameters (1/6)

Page 35
CS_VGCS_CHAR(0,n)
This parameter allows to characterise an handover adjacency, meaning to be used as for normal Circuit Switched transaction only, or for VGCS call only, or for both.
BSC
adj
virtual changeable
number
[0, 2]
none
EN_INBAND_NOTIF
EN_INBAND_PAGING EN_UPLINK_REPLY EN_VGCS
Flag to disable/enable the inband notification

Flag to disable/enable the inband paging Flag to disable/enable uplink reply procedure Flag to disable or enable VGCS in the cell
BSC
BSC BSC BSC
BSC
BSC BSC cell
changeable
changeable changeable changeable
flag
flag flag flag
0
0 0 0
[0, 1]
[0, 1] [0, 1] [0, 1]
none
none none none

Page 36
INBAND_PAGING_ THR
If the eMLPP priority included in the Paging message from the MSC is higher than or equal to this parameter, then the BSS shall trigger in-band paging within cells, that are identified to be paged from the PAGING message, and that have existing VGC active. Maximum number of radio timeslots that can be used by the VGCS calls in the cell.
BSC
cell
changeable
thresh old
[0, 7]
none
MAX_VGCS_TS
BSC
cell
changeable
number
[0, 127]
none
MIN_VGCS_TS
Minimum number of radio timeslots that are reserved for the VGCS calls in the cell in normal situation (point-topoint CS call can NOT use these timeslots).
If the eMLPP priority is higher than or equal to this parameter, the Notifications message shall be sent on FACCH of all other on-going VGCS call.
BSC
cell
changeable
number
[0, 31]
none
NOTIF_FACCH_OTHE R_VGCS_CALL_THR
BSC
cell
changeable
threshol d
[0, 7]
none

Page 37
NOTIF_FACCH_PTP_ CALL_THR
If the eMLPP priority is higher than or equal to this parameter, the Notifications message shall be sent on FACCH of all on-going point to point call whose MS is VGCS capable.
BSC
cell
changeable
threshol d
[0, 7]
none
NOTIF_PCH_THR
The priority threshold for notification over PCH. The BSS shall consider, for Notification/PCH, only VGCS-Calls which have a priority (eMLPP priority) not below this parameter. If more than one is selected, all these voice group calls shall be notified on PCH and all with the same frequency of occurrence.
This parameter defines the maximum number of blocks usable for NCH. Maximum number of repetitions for the VGCS UPLINK GRANT message during an uplink access procedure
BSC
cell
changeable
threshol d
[0, 7]
none
NUMBER_NCH_ BLOCKS NY2
BSC
cell
changeable
number
[1,7]
none
BSC
cell
changeable
number
[1,7]
none

Page 38
START_UPLINK_REPL Y
Maximum number of repetitions for the UPLINK FREE message (with the Uplink Access Request bit set to L) during the initial part of the uplink access procedure (i.e. before sending the first UPLINK FREE message with the Uplink Access Request bit set to H) Maximum queuing time for the VGCS Assignment Requests This timer is used for the repetition of the VGCS UPLINK GRANT message during the uplink access procedure.
BSC
cell
changeable
number
256
[1, 1024]
none
T14
BSC
BSC
changeable
Timer
[1,19]
sec
T3115
BSC
cell
changeable
Timer
200
[100, 480]
msec

Page 39
T_NOTIF_RESPONSE _ DELAY
Timer to delay the Multiple SACCH Info Modify and the VGCS_ADD_INFO to give the MS a chance to receive the immediately transmitted VGCS_ADD_INFO/FACCH and SI 6 messages
BSC
BSC
changeable
Timer
200
[100, 1000]
ms
T_REPETITION_ CHANNEL_RELEASE
T_REPETITION_UPLI NK_FREE
This parameter defines the repetition period of CHANNEL RELEASE message sent on FACCH
The UPLINK FREE messages shall be repeated as long as no uplink is granted to a mobile station. This parameter defines the repetition period. Guard timer to wait for Uplink Access. If no uplink access bursts are received at this timer expiry, the BSC releases (if EN_Uplink_ Reply is set to enabled) the voice group call channel in that cell and then provides notifications containing no channel description.
BSC
cell
changeable
Timer
200
[2100, 1000]
ms
BSC
cell
changeable
Timer
200
[20, 480]
ms
T_WAIT_UPLINK_ ACCESS
BSC
BSC
changeable
Timer
60
[3, 300]
sec

Page 40
HMI name Definition Subsystem Insta nce OMC-R access Type Def valu e Range Unit
T_WAIT_UPLINK_REQ UEST_ACK
Guard timer to wait for UPLINK REQUEST ACK or UPLINK REQUEST REJECT message from the MSC. The type AMR-HR codec used in the network The type AMR-FR codec used in the network. Maximum number of repetitions for the UPLINK FREE message (with the Uplink Access Request bit set to L) per cycle, during the non-initial part of the uplink access procedure (i.e. after sending the first UPLINK FREE message with the Uplink Access Request bit set to H). Each time the value of this counter becomes zero, the BTS send one UPLINK FREE message with the Uplink Access Request bit set to H.
BSC
BSC
changeable
Timer
500
[500, 5000]
sec
VGCS_FIX_AMR_HR_ CODEC VGCS_FIX_AMR_FR_ CODEC WAIT_UPLINK_ ACCESS
BSC BSC BSC
BSC BSC cell
changeable changeable changeable
number number number
2 1 3
[0,3] [0,7] [1, 32]
nono e nono e none
VGCS Other parameters

Page 41
HMI name
Definition
Subsystem
Insta nce
OMC-R access
Type
Def valu e
Range
Unit
N201_BTER_D
Length of information field on FACCH (Format Bter) Length of information field on SACCH (Format Bter)
BTS
BTS
None (not in DLS) None (not in DLS)
number
23
[23,23]
bytes
N201_BTER_S
BTS
BTS
number
21
[21,21]
bytes
VGCS BSC counters (1/2)

Page 42
New PM type VGCS (type 34); measured object=cell

coun ter
V01
Mnemonic
NB_PTP_CALL_P REEMPTED_VGC S AV_PARALLEL_T CH_VGCS
MAX_PARALLEL_ TCH_VGCS NB_VGC_ATTEM PTS_VGCS NB_VGC_SUCCE SS_VGCS NB_CM_SERV_R EQ_VGCS NB_VGC_RELEA SED_VGCS
Definition
Number of CS-calls (point-topoint) pre-empted for VGCChannels per cell during observation period Average number of parallel TCH in use for VGCS per cell during observation period
Maximum number of parallel TCH in use for VGCS per cell during observation period Number of VGC establishment attempts per cell during observation period Number of VGC successfully established VGC per cell during observation period Number of received CM_SERV_REQ for VGC per cell during observation period Number of released VGC per cell during observation period
cou nter
V07
Mnemonic
NB_HO_ATTEMPT S_VGCS NB_HO_SUCCESS _VGCS NB_INCOMMING_ HO_VGCS NB_OUTGOING_H O_VGCS NB_TALKER_CHA NGE_VGCS NB_VGC_BLOCKE D_VGCS NB_VGCS_NOTIFI FICATION_FACCH
Definition
Number of handover attempts for VGC-talker per cell during observation period Number of successful handover for VGC-talker per cell during observation period Number of incoming handover for VGC-talker per cell during observation period Number of outgoing handover for VGC-talker per cell during observation period Number of talker change per established VGC in this BSS during observation period Number of blocked VGC due to lack of resources per cell during observation period Number of VGC notifications sent over FACCH per cell, differentiated for paging and notification for VGCS.
V08
V021
V09
V022
V10
V03
V11
V04
V12
V05
V13
V06
VGCS BSC counters (2/2)

Page 43
New PM type VGCS (type 34); measured object=cell

cou nter
V14
Mnemonic
NB_ASS_REQ_AB LE_PREEMT_VGC S
Definition
Number of ASSIGNMENT_REQUEST able to pre-empt per cell during observation period. Note: The existing counter NB_TCH_NOR_ASS_HO_REQ _ABLE_TO_PREMPT can not be used. As a consequence, new counter is needed: only the Assignment Request for the talker (contains the Talker Flag) message will be counted.
Number of VBS/VGCS_ASSIGNMENT_RE QUEST able to pre-empt per cell during observation period VGCs queuing Number of VGCs established per cell
V15
NB_VGCS_ASS_R EQ_ABLE_PREEM PT NB_VGCS_QUEUE D NB_VGCS_ESTAB LISHED
V16 V17
Agenda
Page 44


B9 channel allocation strategy for CS calls
Influence of Enhanced E-GSM band handling (1/4)

Page 45
Radio Resource allocation strategy

CS allocation for E-GSM capable MS
1.Firstly select a radio timeslot which is E-GSM capable but NOT PS capable; 2.Secondly select a radio timeslot which is neither E-GSM capable nor PS capable; 3.Thirdly select a radio timeslot which is NOT E-GSM capable but PS capable; 4.Finally select a radio timeslot which is E-GSM capable and PS capable.
CS allocation for P-GSM capable only MS

1.Firstly select a radio timeslot which is neither E-GSM capable nor PS capable. 2.Finally select a radio timeslot which is NOT E-GSM capable but PS capable.
High
E-GSM TRX, non-PS capable
Non E-GSM TRX, non-PS capable Non E-GSM TRX, PS capable
CS allocation
Low
High
Non E-GSM TRX, non-PS capable Non E-GSM TRX, PS capable
PS allocation
Low
E-GSM TRX, PS capable
CS allocation
Low
High

Page 46
TCH allocation criteria for PS capable TRXs (TRX_PREF_MARK =0) is as follows :

PS_PREF_BCCH_TRX (Highest priority to non-BCCH TRX if PS_Pref_BCCH_TRX = Enable) HW TRE capability (G3-> G4 MP-> G4 HP) DR TRE capability (DR TRX ->FR TRX) E-GSM TRX preference (new in B9, P-GSM TRX ->E-GSM TRX ) PDCH group (smallest PDCH group -> highest PDCH group) TRX index (high TRX index -> low TRX index) TS index (high TS index -> low TS index)

Page 47
The TCH allocation criteria for non-PS capable TRXs (TRX_PREF_MARK <>0) is as follows :
E-GSM TRX preference (new in B9, E-GSM TRX -> P-GSM TRX) TRX_PREF_MARK (highest TRX_PREF_MARK -> lowest TRX_PREF_MARK) Mobile allocation (biggest MA -> lowest MA) Interference band (TS with best interference band-> TS with worst interference band) TRX index (highest index -> lowest index) TS index (highest index -> lowest index)

highest priority a lloca tion for CS tra ffic TRX with TRX_PREF_MARK< > 0 lowest priority G3 - DR - P-GSM G3 - DR - E-GSM G3 - FR - P-GSM G3 - FR - E-GSM G4 - MP - DR - P-GSM G4 - MP - DR - E-GSM TRX's with TRX_PREF_MARK= 0 G4 - MP - FR - P-GSM G4 - MP - FR - E-GSM G4 - HP - DR - P-GSM G4 - HP - DR - E-GSM G4 - HP - FR - P-GSM G4 - HP - FR - E-GSM lowest priority a lloca tion for CS tra ffic lowest priority TS 0 highest priority TS7 highest priority highest priority a lloca tion for PS tra ffic

Page 48
lowest priority a lloca tion for PS tra ffic
Agenda
Page 49


B9 channel allocation strategy for CS calls Influence of VGCS (1/5)

Page 50
1. 2. 3. 4.
In order to have the impacts as small as possible on the current implemented CS and (E)GPRS radio resource management, the following principles applies on the VGCS radio resource management: No new radio channel type from O&M point of view: A timeslot configured as TCH timeslot by O&M can be used as PDCH or as VGCS channel or standard CS TCH channel. The current radio resource management for CS and (E)GPRS on TRX basis is kept. No impact on (E)GPRS radio resource management: from the MFS point of view, there is NO difference between VGCS traffic and standard point-to-point CS traffic. The BSC CS radio resource management is modified to take into account the VGCS: a timeslot configured as TCH timeslot by O&M is considered by the BSC as a TCH timeslot reserved for VGCS and CS traffic when it is identified neither as MPDCH timeslot nor as TCH/SPDCH/VGCH timeslot

Page 51
From BSC RAM (Radio resource allocation and Management) point of view, the following types of service oriented timeslots are supported:
Pure BCCH timeslot: timeslot configured as BCC by O&M; carries common CS signalling. Pure SDCCH timeslot: timeslot configured as a CBC or SDC by O&M; can carry SDCCH traffic. Pure TCH timeslot: timeslot configured as TCH by O&M; carries only TCH traffic (applies only to inner zone of contentric cells). TCH/VGCH timeslot: timeslot configured as TCH by O&M; carries TCH or VGCH traffic. TCH/SPDCH/VGCH timeslot: timeslot configured as TCH by O&M; is dynamically allocated as TCH or as SPDCH depending on the usage of the timeslot; can carry TCH traffic, VGCH traffic or PS traffic. TCH/SDCCH timeslot: configured as SDD by O&M; is dynamically allocated as TCH or as SDCCH depending on the usage of the timeslot; can carry TCH traffic or SDCCH traffic. MPDCH timeslot: configured as TCH by O&M;can only carry common PS signalling.
From O&M side it is not possible to fix the localisation of these service oriented timeslots. Only the number of these timeslots can be configured.

Page 52
Without VGCS With VGCS
1. TRX
2. TRX
GSM 900
GSM 900
3. TRX Additional capacity for VGCS (optional)
4. TRX
not installed
GSM 900 or DCS 1800
5. TRX
not installed
Legend: the colours show the type of traffic handled by the timeslot
VGCS VGCS/CS VGCS/CS/GPRS GPRS/CS CS GPRS
TRX_PREF_MARK <> 0 TRX_PREF_MARK=0
TRX_PREF_MARK <>0
TRX_PREF_MARK <>0
Min_PDCH Max_PDCH
these TS are CS/VGCS switch-able but the VGCS these TS are has priority point-topoint CS only
Min_VGCS_TS Max_VGCS_TS

Page 53
For the radio TCH allocation on TCH/VGCH timeslots (I.e. TRX_PREF_MARK<>0) due to a VGCS request:
=>the same principles and criteria are used as for the radio TCH allocation on TCH/VGCH timeslots due to a TCH request
For the radio TCH allocation on TCH/SPDCH/VGCH timeslots (I.e. TRX_PREF_MARK=0) due to a VGCS request:
=>the same principles and criteria are used as for the radio TCH allocation on TCH/SPDCH/VGCH timeslots due to a TCH request

Page 54
Parameters in B9
MAX_VGCS_TS
Maximum number of radio timeslots that can be used by the VGCS calls in the cell. Minimum number of radio timeslots that are reserved for the VGCS calls in the cell in normal situation (point-topoint CS call can NOT use these timeslots).
BSC
cell
changeable
number
[0, 127]
none
MIN_VGCS_TS
BSC
cell
changeable
number
[0, 31]
none
B9 channel allocation strategy for CS calls Overview on next slides

Page 55
The following slides show how VGCS is taken into account by the Radio resource updating function in the Radio Allocation and Management (RAM) process for:
the evaluation of the cell load the evaluation of the number of TCH/SPDCH/VGCH timeslots than can be allocated to the MFS, the substeps being:
MAX_SPDCH_LIMIT calculation MAX_SPDCH_LIMIT TS selection
Consideration of VGCS for the PS Load evaluation (1/5)

Page 56
The BSC takes every TCH_INFO_PERIODs a sample of the current usage on TCH/VGCH, TCH/SDCCH and TCH/SPDCH/VGCH TS
NB_USED_CS_TS(k) NB_USED_PS_TS(k) NB_USED_VGCS_TS(k) NB_USED_TS(k) NB_UNUSED_TS(k)
TCH_INFO_PERIOD = 5s
At the expiry of the TCH_INFO_PERIOD timer, the timer is re-started and the following load samples are calculated:
NB_USED_CS_TS(k) NB_USED_PS_TS(k) NB_USED_VGCS_TS(k) NB_USED_TS(k) = NB_USED_CS_TS(k) + NB_USED_PS_TS(k) + NB_USED_VGCS_TS(k) NB_UNUSED_TS(k)

Page 57
NB_USED_CS_TS(k): number of available timeslots handled by the BSC and carrying CS traffic in the cell at sampling instant tk
a TS is taken into account in the evaluation of NB_USED_CS_TS(k) if:
SPDCH allocation state = not allocated Occupancy state = used (i.e. the TS is currently carrying CS traffic or is allocated as SDCCH)
NB_USED_PS_TS(k): number of available timeslots used for PS traffic in the cell at sampling instant tk
a TS is taken into account in the evaluation of NB_USED_PS_TS(k) if:
SPDCH allocation state = allocated or de-allocating Occupancy state = used
NB_USED_VGCS_TS(k): number of available timeslots handled by the BSC and carrying VGCS traffic in the cell at sampling instant tk
a TS is taken into account in the evaluation of NB_USED_VGCS_TS(k) if:
SPDCH allocation state = not allocated Occupancy state = used

Page 58
NB_UNUSED_TS(k): at the expiry of TCH_INFO_PERIOD timer, the BSC computes the number of unused timeslots at sampling instant tk
NB_UNUSED_TS(k) = NB_TS(k) NB_USED_CS_TS(k) max(NB_USED_VGCS_TS(k), MIN_VGCS_TS) max(MIN_SPDCH(k), NB_USED_PS_TS(k)) NB_TS(k): total number of TCH/VGCH, TCH/SDCCH or TCH/SPDCH/VGCH timeslots available in the cell. This parameter is recomputed every RR_ALLOC_PERIOD * TCH_INFO_PERIOD to take into account possible TRX failure MIN_SPDCH(k): minimum number of SPDCHs that are always allocated to the MFS. This parameter is re-computed every RR_ALLOC_PERIOD * TCH_INFO_PERIOD to take into account possible TRX failure

Page 59
Load evaluation:
for each cell, every RR_ALLOC_PERIOD * TCH_INFO_PERIOD, the BSC computes four averaged values through a sliding window of size LOAD_EV_PERIOD_GPRS (default value = 3):
AV_USED_CS_TS(k) =
(1/LOAD_EV_PERIOD_GPRS)*i=0 to LOAD_EV_PERIOD_GPRS -1 NB_USED_CS_TS(k-i)
AV_USED_PS_TS(k) =
(1/LOAD_EV_PERIOD_GPRS)*i=0 to LOAD_EV_PERIOD_GPRS -1 NB_USED_PS_TS(k-i)
AV_USED_VGCS_TS(k) =
(1/LOAD_EV_PERIOD_GPRS)*i=0 to LOAD_EV_PERIOD_GPRS -1 NB_USED_VGCS_TS(k-i)
AV_UNUSED_TS(k) =
(1/LOAD_EV_PERIOD_GPRS)*i=0 to LOAD_EV_PERIOD_GPRS -1 NB_UNUSED_TS(k-i)

Page 60
k-2
k-1
k+1
k+2
TCH_INFO_PERIOD = 5s NB_USED_CS_TS(k) NB_USED_PS_TS(k) NB_USED_VGCS_TS(k) NB_USED_TS(k) NB_UNUSED_TS(k)
RR_ALLOC_PERIOD * TCH_INFO_PERIOD
LOAD_EV_PERIOD = 3
AV_USED_CS_TS(k) AV_USED_PS_TS(k) AV_USED_VGCS_TS(k) AV_UNUSED_TS(k)
AV_USED_CS_TS(k+2) AV_USED_PS_TS(k+2) AV_USED_VGCS_TS(k+2) AV_UNUSED_TS(k+2)
Consideration of VGCS for the MAX_SPDCH_LIMIT calculation (1/7)

Page 61
MAX_SPDCH_LIMIT calculation:
the BSC periodically (every RR_ALLOC_PERIOD * TCH_INFO_PERIOD) computes the number of Slave PDCHs that it can provide to the MFS: MAX_SPDCH_LIMIT
MAX_PDCH_HIGH_LOAD MAX_PDCH MIN_PDCH NB_TS_DEFINED NB_TS_MPDCH NB_TS_SPDCH
O&M parameters
MIN_SPDCH MAX_SPDCH
AV_USED_CS_TS AV_USED_PS_TS AV_UNUSED_TS
NB_TS
Computation of Thresholds
MAX_SPDCH_HIGH_LOAD
Computation of MAX_SPDCH_LIMIT
MAX_SPDCH_LIMIT
Computation of CS/PS Margin
MARGIN_PRIORITY_CS MARGIN_PRIORITY_PS
THR_MARGIN_PRIORITY_CS THR_MARGIN_PRIORITY_PS
= 100 HIGH_TRAFFIC_LOAD_GPRS O&M parameter

Page 62
Calculation of MIN_SPDCH, MAX_SPDCH and MAX_SPDCH_HIGH_LOAD:

re-evaluated every RR_ALLOC_PERIOD * TCH_INFO_PERIOD to take into account TRX failures introduction of a ratio named AVAILABILITY_TS_RATIO(k), evaluated periodically every RR_ALLOC_PERIOD * TCH_INFO_PERIOD at instant tk:
= (NB_TS(k) MIN_VGCS_TS) / (NB_TS_DEFINED MIN_VGCS_TS) NB_TS_DEFINED: total number of TCH/VGCH, TCH/SDCCH or TCH/SPDCH/VGCH timeslots available in the cell if there is no TRX failure. This parameter is retrieved from the O&M configuration of the cell

Page 63
Calculation of MIN_SPDCH, MAX_SPDCH and MAX_SPDCH_HIGH_LOAD:

MAX_SPDCH(k) = RoundUp[ min(MAX_PDCH NB_TS_MPDCH, NB_TS_SPDCH) *AVAILABILITY_TS_RATIO(k) ]
NB_TS_SPDCH: total number of TCH/SPDCH/VGCH timeslots available in the cell if there is no TRX failure. This parameter is retrieved from the O&M configuration of the cell
MAX_SPDCH_HIGH_LOAD(k) = RoundUp[ min( MAX_PDCH_HIGH_LOAD NB_TS_MPDCH, NB_TS_SPDCH) * AVAILABILITY_TS_RATIO(k) ] MIN_SPDCH(k) = RoundUp[ (MIN_PDCH NB_TS_MPDCH) * AVAILABILITY_TS_RATIO(k) ]

Page 64
Margins for CS and PS traffics:

two new margins, one for CS traffic and one for PS traffic are introduced to guarantee that a certain number of timeslots are kept available for the arrival of new calls between two transmissions of the RR Allocation Indication message:
the first margin, named MARGIN_PRIORITY_CS, is dedicated to CS traffic the second margin, named MARGIN_PRIORITY_PS, is dedicated to PS traffic
these two margins are re-evaluated every RR_ALLOC_PERIOD * TCH_INFO_PERIOD, before the computation of MAX_SPDCH_LIMIT MARGIN_PRIORITY_CS(k) = (THR_MARGIN_PRIO_CS * (NB_TS(k) MAX_SPDCH_HIGH_LOAD(k)) / 100 MARGIN_PRIORITY_PS(k) = (THR_MARGIN_PRIO_PS * MAX_SPDCH_HIGH_LOAD(k)) / 100

Page 65
the basic idea to evaluate MAX_SPDCH_LIMIT is to estimate the number of unused TS and to share them between CS and PS traffic, taking into account both margins (for CS and PS traffics) defined to guarantee a certain number of TS available to serve incoming calls
MARGIN_PRIORITY_CS
AV_USED_CS_TS(k) AV_UNUSED_TS(k)
Computation of MAX_SPDCH_LIMIT_CS
MAX_SPDCH MAX_SPDCH_HIGH_LOAD
MAX_SPDCH_LIMIT_CS(k) Computation of MAX_SPDCH_LIMIT MAX_SPDCH_LIMIT_PS(k) MAX_SPDCH_LIMIT(k)
AV_USED_PS_TS(k)
Computation of MAX_SPDCH_LIMIT_PS
MIN_SPDCH MARGIN_PRIORITY_PS

Page 66
MAX_SPDCH_LIMIT_CS:
determines the maximum number of SPDCHs that can be allocated to the MFS in order to ensure that a certain number of timeslots (margin) is kept in the BSC to serve possible incoming CS requests received between two sendings of the RR Allocation Indication message MAX_SPDCH_LIMIT_CS(k) = RoundDown [ NB_TS(k) max (MIN_VGCS_TS(k) ; AV_USED_VGCS_TS(k)) AV_USED_CS(k) - MARGIN_CS(k) ] MARGIN_CS(k) = max(MARGIN_PRIORITY_CS(k), AV_UNUSED_TS(k) / 2)
MAX_SPDCH_LIMIT_PS:
determines the minimum number of SPDCHs that should be allocated to the MFS in order to ensure that a certain number of timeslots (margin) is kept in the MFS to possibly serve incoming PS requests if AV_USED_PS_TS(k) is lower or equal than MIN_SPDCH then MAX_SPDCH_LIMIT_PS(k) = MIN_SPDCH(k) else MAX_SPDCH_LIMIT_PS(k) = RoundUp (AV_USED_PS_TS(k) + MARGIN_PRIORITY_PS(k))

Page 67
it can be in the range of [MIN_SPDCH, MAX_SPDCH] its value can be either MAX_SPDCH_LIMIT_CS or MAX_SPDCH_LIMIT_PS
MAX_SPDCH MAX_SPDCH_LIMIT_CS
Zone where MAX_SPDCH_LIMIT = MIN( MAX_SPDCH, MAX_SPDCH_LIMIT_CS)
MAX_SPDCH_HIGH_LOAD Zone where MAX_SPDCH_LIMIT = MIN (MAX_SPDCH_LIMIT_PS, MAX_SPDCH_HIGH_LOAD) MAX_SPDCH_LIMIT_PS 0 MIN_SPDCH MAX_SPDCH_HIGH_LOAD MAX_SPDCH
MIN_SPDCH
Consideration of VGCS for the MAX_SPDCH_LIMIT TS selection (1/8)

Page 68
PS TS and TRX ordering:

the first step consists in ordering the PS timeslots and the PS TRX so as to obtain an ordered list of TCH/SPDCH/VGCH timeslots the ordering of the timeslots is based on the following criteria:
selection of the TRX: the TRX having the lowest rank in the TRX ranking table (refer to the slide on TRX priority) is selected first selection of the TS: once the TRX has been selected, the TCH/SPDCH/VGCH timeslots having the lowest timeslot index, i.e. located at the most left side of the TRX, is selected first

Page 69
Different PS TS zones:
MAX_SPDCH_HIGH_LOAD zone:
this zone corresponds to the MAX_SPDCH_HIGH_LOAD consecutive PS capable TS that are preferred for PS allocation in this zone, allocated TBFs cannot be pre-empted
Non pre-emptable PS zone:

this zone is always inside the MAX_SPDCH_HIGH_LOAD zone in this latter zone, we search for the rightest TS allocated to the MFS and used. Then, all the TS located at its left define the non pre-emptable PS zone inside this zone, a TS:
remains allocated to the MFS if already allocated to the MFS is allocated to the MFS if previously allocated to the BSC and unused remains allocated to the BSC if already allocated to the BSC and used

Page 70
MAX_SPDCH_LIMIT zone:
this zone corresponds to the MAX_SPDCH_LIMIT consecutive PS capable TS that are preferred for PS allocation inside this zone, a TS:
remains allocated to the MFS if already allocated to the MFS is allocated to the MFS if previously allocated to the BSC and unused remains allocated to the BSC if already allocated to the BSC and used
PS traffic zone:
this zone corresponds to the larger zone between the non pre-emptable PS zone and the MAX_SPDCH_LIMIT zone

Page 71
example: MAX_SPDCH_HIGH_LOAD = 8, MAX_SPDCH_LIMIT = 10
PS traffic zone MAX_SPDCH_LIMIT zone Non pre-emptable PS zone PS 1 PS 2 CS 3 PS 4 5 TRX2 PS 6 CS 7 8 PS 9 PS 10 CS 11 CS 12 13 TRX1 14 15 CS 16
MAX_SPDCH_HIGH_LOAD zone
example: MAX_SPDCH_HIGH_LOAD = 8, MAX_SPDCH_LIMIT = 3

PS traffic zone Non pre-emptable PS zone MAX_SPDCH_LIMIT zone PS 1 PS 2 3 CS CS PS 6 CS 7 8 CS 9 CS 10 CS 11 CS 12 13 TRX1 14 15 CS 16
4 5 TRX2
MAX_SPDCH_HIGH_LOAD zone

Page 72
Selection of the TCH/SPDCH/VGCH TS:

to be selected, the states of a TCH/SPDCH/VGCH timeslot must have the following values:
SPDCH allocation state = allocated: the timeslot is already allocated to the MFS SPDCH allocation state = not allocated and occupancy state = unused: the timeslot is allocated to the BSC but there is no CS traffic on it

Page 73
Selection of the TCH/SPDCH/VGCH TS:

the process begins with the non pre-emptable PS zone:
all the TS in this zone that can be or are allocated to the MFS are allocated to the MFS. The verification in terms of number of TS allocated to the MFS is done only when all the TS inside this zone have been handled
if at the end of the non pre-emptable PS zone, the number of selected TS for the MFS is strictly lower than MAX_SPDCH_LIMIT then the process of selection continues in the MAX_SPDCH_LIMIT zone if at the end of the MAX_SPDCH_LIMIT zone, the number of selected TS for the MFS is still lower than MAX_SPDCH_LIMIT, the process continues outside this zone until this number reaches MAX_SPDCH_LIMIT once MAX_SPDCH_LIMIT TS have been selected, all the remaining TCH/SPDCH/VGCH TS are now allocated to the BSC, even if they were previously allocated to the MFS. This means that a TS with a SPDCH allocation state set to allocated that is no more allocated to the MFS, has its SPDCH allocation state set to de-allocating

Page 74
Pre-reservation mechanism in the PS traffic zone:

in order to increase the PS capacity and limit the occurrence of holes in the SPDCHs_Allocation bitmap, each TCH/SPDCH/VGCH capable TS carrying CS traffic and located inside the PS traffic zone, has its pre-reservation state set to pre-reserved for PS. No new incoming CS call can be served on this TS, if it becomes unused once it is prereserved for PS. This is valid until the TS becomes not pre-reserved for PS again and of course still handled by the BSC the modification of the value of the pre-reservation state can only occur when the SPDCHs_Allocation bitmap is built, every TCH_INFO_PERIOD * RR_ALLOC_PERIOD seconds

Page 75
Pre-reservation mechanism in the PS traffic zone:

the following transition can be foreseen for a timeslot inside the PS traffic zone:
it goes from not pre-reserved for PS to pre-reserved for PS or remains in prereserved for PS if it is in one of the two following situations:
SPDCH allocation state = not allocated and occupancy state = used SPDCH allocation state = de-allocating
it goes from pre-reserved for PS to not pre-reserved for PS or remains in not prereserved for PS if it is in the following situation:
SPDCH allocation state = allocated
the following transition can be foreseen for a timeslot outside the PS traffic zone:
it goes from pre-reserved for PS to not pre-reserved for PS or remains in not prereserved for PS if it is in one of the following situations:
SPDCH allocation state = not allocated SPDCH allocation state = allocated SPDCH allocation state = de-allocating
Agenda
Page 76


B9 channel allocation strategy for CS calls Influence of Intracell HO cause 30 (1/4)

Page 77
Intracell HO cause 30 =>applies for CS calls in the Non pre-emptable PS zone, independent of VGCS usage:
to speed up the release of a TS carrying a CS call inside both the non preemptable PS zone and the MAX_SPDCH_LIMIT zone, the concerned CS calls in the CS zone are reallocated using an intra-cell handover (cause 30) if EN_RETURN_CS_ZONE_HO = enabled, each time MAX_SPDCH_LIMIT is calculated, the BSC shall check whether TCHs are allocated in both the MAX_SPDCH_LIMIT zone and the non pre-emptable PS zone. In this case, it shall send a Start HO (cause 30) message to the HO Preparation entity, to trigger an intracell handover, to move these TCHs into the CS zone if for any reason, the handover fails, the TCH will remain in the PS zone, until the next calculation of MAX_SPDCH_LIMIT, where a new HO could be triggered, if still needed the TS will be considered as unused only once the handover will have been successfully performed. As the pre-reservation state of such a TS is set to prereserved for PS, no new incoming CS call can be allocated on it

Page 78
PS traffic zone Non pre -emptable PS zone

BC SD PS 1 2 3 PS 4 PS 5 TRX1 MIN_SPDCH zone MAX_SPDCH_HIGH_LOAD zone MAX_SPDCH_LIMITzone MAX_SPDCH zone PS 6 PS 7 CS 8 PS 9 CS 10 11
CS traffic zone
This CS call is not candidate for the intra cell HO as it is outside the non pre -emptable PS zone PS CS CS CS 12 13 14 15 16
TRX2
Intra cell HO to move this CS call to the CS traffic zone

Page 79
PS traffic zone non pre-emptable PS zone BCC SDC 1 2 PS 3 PS 4 TRX 1 MIN_SPDCH zone PS 5 PS 6 PS 7 CS 8 PS 9 CS 10
CS traffic zone
11
PS 12 TRX 2
CS 13
CS 14
15
CS 16
this call is not a candidate for HO cause 30
MAX_SPDCH_HIGH_LOAD zone MAX_SPDCH_LIMIT zone MAX_SPDCH zone

Page 80
Parameter in B9
EN_RETURN_CS_ ZONE_HO
Flag enabling the intracell handovers allowing to move TCH from the PS zone to the CS zone of PDCH/TCH allocation
BSC
cell
changeable
flag
[0,1]
none
End of presentation
Page 81
www.alcatel.com

TMD B9pres 11oct05 CS Aspect Ed02

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

TMD B9pres 11oct05 CS Aspect Ed02

Enviado por

Direitos autorais:

Formatos disponíveis

B9 Parameter Workshop Part 1: Circuit Switched (CS) Aspects

Presentation to T-Mobile, Bonn, 11 Oct 2005 Alcatel-PCS

All rights reserved 2005, Alcatel

B9 features and related parameters:

Features influencing the B9 channel allocation strategy for CS calls:

All rights reserved 2005, Alcatel

Enhanced E-GSM band handling Introduction (1/2)

Feature goals in B9: full support of the

Limitations in B7.2 and B8:

P-GSM band 890 E-GSM downlink 915

P-GSM band 960

Enhanced E-GSM band handling Introduction (2/2)

Characteristics of E-GSM in B9:

All rights reserved 2005, Alcatel

Enhanced E-GSM band handling Market View

Business Case 1: P-GSM network extension with the frequencies in G1 band

All rights reserved 2005, Alcatel

Enhanced E-GSM band handling Functional description (1/3)

Mode 2 : P-GSM capable only MS are supported

Enhanced E-GSM band handling Functional description (2/3)

Mode 1: Support of E-GSM networks With this mode :

All rights reserved 2005, Alcatel

Enhanced E-GSM band handling Functional description (3/3)

Mode 2: Support of P-GSM only MS in E-GSM networks

All rights reserved 2005, Alcatel

Enhanced E-GSM band handling OMC-R parameters (1/2)

Defines the radio resource allocation strategy used in EGSM cells.

All rights reserved 2005, Alcatel

Enhanced E-GSM band handling OMC-R parameters (2/2)

This parameter indicates the frequency range of the cell.

PLMN_FREQUENCY_ BANDS (BSC) PLMN_FREQUENCY_ BANDS (MFS)

Virtual changeable Virtual changeable

All rights reserved 2005, Alcatel

B9 features and related parameters:

Features influencing the B9 channel allocation strategy for CS calls:

All rights reserved 2005, Alcatel

EME supervision Introduction (1/3)

Feature goals in B9:

All rights reserved 2005, Alcatel

EME supervision Introduction (2/3)

Expected gains in B9:

All rights reserved 2005, Alcatel

EME supervision Introduction (3/3)

All rights reserved 2005, Alcatel

EME supervision Functional description (1/4)

Characteristics of EME supervision feature in B9:

All rights reserved 2005, Alcatel

EME supervision Functional description (2/4)

2.) PM33 type data collection (description)

All rights reserved 2005, Alcatel

EME supervision Functional description (3/4)

All rights reserved 2005, Alcatel

EME supervision Functional description (4/4)

Dynamic power contribution: Power control No power contribution:

All rights reserved 2005, Alcatel

EME supervision OMC-R parameters

EME_PWR_MAX_ DCS EME_DATA_TIMER

Thresh old timer

[1,999 9] [0, 255]

All rights reserved 2005, Alcatel

B9 features and related parameters:

Features influencing the B9 channel allocation strategy for CS calls:

All rights reserved 2005, Alcatel